PO03655: IEG SCRIPT AND EVIDENCE ALLOW NEGATIVE NUMBERS FOR INCOME AND DEDUCTION

APAR status

• Closed as fixed if next.

Error description

• IEG script and Evidence allow for negative amount values for
  Income, Deduction, Excluded Income, Annual Income,
  IncomeDetails, IncomeDetails and Tax Exempt.
  

Local fix

• Updating IEG Scripts and Dynamic Evidence to prevent negative
  amount values
  Below guide will walk through all the steps to update Citizen
  Portal, CoC, Internal Portal scripts and Dynamic Evidence to
  prevent using negative amount values.
  Citizen Portal, CoC, Internal Portal scripts
  Previously negative amount of Income, Deduction, Excluded
  Income, Annual
  Income, and Tax Exempt were allowed.
  Solution:
  Following default IEG scripts may require validations
  (customisations are to be assessed during the update):
    HealthCarePortalScript.xml
    ChangeOfCircumstance.xml
    HealthCareCW.xml
  Validation expressions to be added inside the following
  default question-pages:
    id="ManualIncomePage1"
    id="ManualIncomePage"
    id="ManualIncomePage2"
    id="ManualIncomePage3"
   <validation
  expression="IncomeItem.incomeType!=&quot;HCIT26014&quot; or
  IncomeItem.taxExemptAmount &gt; 0">
   <message id="ManualIncome.TaxExemptAmountValidation"/>
   </validation>
    id="IncomeDeductionPage"
    id="IncomeDeductionPage1"
   <validation expression="DeductibleIncomeItem.amount &gt; 0">
   <message id="Amount.Negative"/>
   </validation>
    id="ScholarshipIncomeDetails"
    id="ScholarshipIncomeDetails1"
   <validation expression="ScholarshipIncomeItem.amount &gt;
  0">
   <message id="Amount.Negative"/>
   </validation>
    id="NAAIIncomeDetails"
    id="NAAIIncomeDetails1"
   <validation expression="NAAIIncomeItem.amount &gt; 0">
   <message id="NAAIIncomeItem.AmountValidation"/>
   </validation>
    id="ProjectedAnnualIncomePage"
    id="ProjectedAnnualIncomePage1"
   <validation
  expression="Person.isAnnualIncomeCorrect==&quot;YN1&quot; or
  ProjectedAnnualIncome.projectedIncome  &gt; 0">
   <message id="ProjectedIncome.Negative"/>
   </validation>
  Validation messages to be added to the related .properties
  files.
  e.g:
  add  Amount.Negative=Amount value must be greater than zero.  in
    HealthCarePortal_V1_Portal_IncomeDeductionPage.properties
  
  HealthCarePortal_V1_Portal_AnyIncomeDeductionPage.properties
  
  ChangeOfCircumstance_V1_LifeEvent_AnyIncomeDeductionPage.propert
  ies
    HealthCareCW_V1_Intake_IncomeDeductionPage.properties
    HealthCareCW_V1_Intake_IncomeDeductionPage1.properties
    etc.
  Dynamic Evidence
  Solution:
  Create a new version of Income, Deductions, ExcludedIncome
  evidences.
  HCR Income evidence will be used as an example
  1) Create a new Metadata_Income_%current_date%.xml with the
  same content of the current evidence version xml file and add
  this validation
  No validation Validation added
  <Attribute>
    <DataAttribute mandatory="true" name="amount" volatile="true">
      <DomainType dataType="Money"/>
    </DataAttribute>
  </Attribute> <Attribute>
    <DataAttribute mandatory="true" name="amount" volatile="true">
      <DomainType dataType="Money"/>
         <NumericOptions minValue="0.00"/>
      </DomainType>
    </DataAttribute>
  </Attribute>
  Validation added
  <Attribute>
    <DataAttribute mandatory="true" name="amount" volatile="true">
      <DomainType dataType="Money"/>
         <NumericOptions minValue="0.00"/>
      </DomainType>
    </DataAttribute>
  </Attribute>
  2) Create a new DynEvd_Income_%current_date%.properties  with
  the same content of the current evidence version properties file
  3) In APPRESOURCE.dmx copy and paste the row related to the
  current Income evidence version and change the highlighted
  attributes, pointing to the new
  DynEvd_Income_%current_date%.properties file.
  RESOURCEID must be unique.
  <row>
      <attribute name="RESOURCEID">
        <value>26719</value>
      </attribute>
      <attribute name="LOCALEIDENTIFIER">
        <value/>
      </attribute>
      <attribute name="NAME">
        <value>DynEvd_Income_%current_date%.properties</value>
      </attribute>
      <attribute name="CONTENTTYPE">
        <value>text/plain;charset=UTF-8"</value>
      </attribute>
      <attribute name="CONTENTDISPOSITION">
        <value>inline;</value>
      </attribute>
      <attribute name="CONTENT">
  
  <value>./HCR/data/initial/blob/DynEvd_Income_%current_date%.prop
  erties</value>
      </attribute>
      <attribute name="INTERNAL">
        <value>1</value>
      </attribute>
      <attribute name="LASTWRITTEN">
        <value>SYSTIME</value>
      </attribute>
      <attribute name="VERSIONNO">
        <value>1</value>
      </attribute>
      <attribute name="CATEGORY">
        <value>RS_PROP</value>
      </attribute>
  </row>
  4) In EVIDENCETYPEVERSIONDEF.dmx copy and paste the row related
  to the current Income evidence version and change the
  highlighted attributes, pointing to the new
  Metadata_Income_%current_date%.xml file.
  EVIDENCETYPEVERSIONDEFID must be unique.
  <row>
      <attribute name="EVIDENCETYPEVERSIONDEFID">
        <value>26493</value>
      </attribute>
      <attribute name="EVIDENCETYPEDEFID">
        <value>26491</value>
      </attribute>
      <attribute name="EFFECTIVEFROM">
        <value>%current_date%</value>
      </attribute>
      <attribute name="CUSTOMIND">
        <value>0</value>
      </attribute>
      <attribute name="RECORDSTATUS">
        <value>DEVRST1</value>
      </attribute>
      <attribute name="XMLMETADATA">
  
  <value>./HCR/data/initial/clob/Metadata_Income_%current_date%.xm
  l</value>
      </attribute>
      <attribute name="PROPERTIES">
        <value/>
      </attribute>
      <attribute name="VALIDATIONEDITACTIONID">
        <value/>
      </attribute>
      <attribute name="CALCATTRIBUTESEDITACTIONID">
        <value/>
      </attribute>
      <attribute name="SUMMARYEDITACTIONID">
        <value/>
      </attribute>
      <attribute name="VERSIONNO">
        <value>1</value>
      </attribute>
  </row>
  %current_date% - all above changes must have a consistent date
  value, e.g. 20140709
  

Problem summary

• IEG SCRIPT AND EVIDENCE ALLOW NEGATIVE NUMBERS FOR INCOME AND
  DEDUCTION
  

Problem conclusion

• APAR was included in release 6.0.5.6
  Please see release Notes:
  http://www-01.ibm.com/support/docview.wss?uid=swg27044445
  PO03655, HCR-6675 - HCR Scripts and Evidence allow for negative
  amounts for Income, Deductions, Excluded Income, and Annual
  Income
  
  Previously, negative amount of Income, Deductions, Excluded
  Income, Annual Income, and Tax Exempt were allowed when you
  went through the Citizen Portal, CoC, and Internal Portal
  scripts. This issue also existed when editing Income,
  Deductions, and ExcludedIncome evidences.
  Now these issues have been resolved by adding validations in
  HCR scripts and creating a new version of {{Income}},
  {{Deductions}}, {{ExcludedIncome}} evidences.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• HCR
  

Fix information

Applicable component levels

• R605 PSY

     UP