Better Error and Message Handling Phase 2
This enhancement will replace OIPA system error messages with user friendly error messages which helps to easily identify the reason for the error. As part V12.0 fourteen messages of APE, SRE, PAS and General type are replaced with new messages.
SRE Messages
The list of SRE messages that are replaced with new messages are as follows:
|
ERROR NUMBER |
ERROR TYPE |
EXISTING ERROR MESSAGES IN OIPA |
NEW ERROR MESSAGES IN OIPA |
|
SRE.FailedFindBusinessRuleForTransaction |
SRE |
Error.FailedFindBusinessRuleForTransaction= Failed to find BusinessRule {0} with transaction GUID "{1}". |
Failed to find BusinessRule Activity:{Transaction Name} BusinessRule:{} Policy":{PolicyNumber} Client:{Client Name} Group Customer:{Customer Number} Plan:{Plan Name} Company:{Company Name:} |
|
SRE.FailedFindRoleByRoleCodes |
SRE |
Error.FailedFindRoleByRoleCodes = Failed to find roles by RoleCode for RoleCode {0}. |
Failed to find policy role by RoleCode within DisbursementRole configuration. RoleCode:{} Activity:{} Policy:{Policy Number} Plan:{Plan Name} Company:{Company Name} |
|
SRE.FailedFindSegments |
SRE |
Error.FailedFindSegments = Could not find Segments with SegmentName: {0}. |
Segment does not exist on source Policy Segment Name:{} Activity:{Transaction Name} BusinessRule:{} Source Policy:{Policy Number} Plan:{} Company:{} |
|
SRE.InvalidSegmentToCopyBenefitSplit |
SRE |
Error.InvalidSegmentToCopyBenefitSplit = Invalid Segment Id to copy BenefitSplit: {0}. |
The System cannot copy the BenefitSplit to the Target Policy Company:{Company Name} Plan: {PlanName}Policy: {PolicyNumber} Activity: {TransactionName}Business Rule: {AttachedRuleName} Segment: {SegmentName}Source BenefitSplit TypeCode: {TypeCode} |
|
SRE.PlanNameMissing |
SRE |
Error.PlanNameMissing = Required PlanName missing |
Plan name is missing Activity:{Activity Name} BusinessRule:{} Source Policy:{Policy Number} Plan:{} Company:{} |
|
SRE.SegmentNameAndSegmantGuids |
SRE |
Error.SegmentNameAndSegmantGuids = SEGMENTNAME and SEGMENTGUIDS cannot be configured in the same <Segment> element. |
SegmentName and SegmentGuids attributes should not be defined on the same segment Segment:{Segment name} Activity:{Transaction Name} BusinessRule:{} Policy:{Policy Number} Plan:{Plan Name} Company:{Company Name} |
|
SRE.FailedOnChangeAssignAction |
SRE |
Error.FailedOnChangeAssignAction = Can not assign value to the "{0}" field in the onChange processing. |
Can not assign value to the field on the onChange processing. Company:{Company Name} Plan: {PlanName}Activity: {TransactionName} Business Rule: {AttachedRuleName}Field: {BusinessRuleFieldName} |
|
SRE.FailedOnChangeEnableFieldAction |
SRE |
Error.FailedOnChangeEnableFieldAction = Can not enable "{0}" field in the onChange processing |
Can not enable field in an onChange processing. Company:{Company Name} Plan: {PlanName}Activity: {TransactionName} Business Rule: {AttachedRuleName}Field: {BusinessRuleFieldName} |
APE Error Messages
The APE error messages that are replaced with new messages are as follows:
|
ERROR NUMBER |
ERROR TYPE |
EXISTING ERROR MESSAGES IN OIPA |
NEW ERROR MESSAGES IN OIPA |
BUSINESS RULE/APE RULE |
|
APE.FailedApe |
APE |
Error.FailedApe = An error occurred while processing business rule: {0}. |
The Business rule failed to process due to one or more errors Company:{Company Name}Plan: {PlanName}Activity: {TransactionName}Business Rule: {AttachedRuleName} |
APE Rule : Attached rules |
|
APE.FromIndexCollection |
APE |
Error.FromIndexCollection = Transaction cannot copy to fields of more than one entity |
Transaction cannot copy to fields of more than one entity Company:{Company Name}Plan: {PlanName}Activity: {TransactionName}Business Rule: {AttachedRuleName} |
APE Rule: CopyToRoleFields |
|
APE.CopySourceMustYes |
APE |
Error.CopySourceMustYes = COPYSOURCE must be Yes to copy the Segments identified in SEGMENTGUIDS. |
COPYSOURCE must be Yes to copy the Segments identified in SEGMENTGUIDS Attribute Company:{Company Name}Plan: {PlanName}Policy: {PolicyNumber}Activity: {TransactionName}Business Rule: {AttachedRuleName} |
APE Rule: CreatePolicy |
| APE.SegmentDoesNotExist | Error.SegmentDoesNotExist = The Segment does not exist on the Policy |
The Segment does not exist on the Policy Company:{Company Name}Plan: {PlanName}Policy: {PolicyNumber}Activity: {TransactionName}Business Rule: {AttachedRuleName}Segment: {Segmentname} |
APE Rule: CreatePolicy |
PAS and General Error Messages
|
ERROR NUMBER |
ERROR TYPE |
EXISTING ERROR MESSAGES IN OIPA |
NEW ERROR MESSAGES IN OIPA |
|
PAS.MissingAttribute |
PAS |
Error.MissingAttribute = Missing Required Attribute {0}. |
An Attribute is missing a required value Company:{Company Name} Plan: {PlanName} Policy: {PolicyNumber} Activity: {TransactionName} Business Rule: {AttachedRuleName} Element Name: {Element Name} Attribute: {Attributename} |
| General.FailedParseXML | General | NA | Error in XML Structure Activity: {TransactionName} or BusinessRule: {BusinessRuleName} or CopyBook: {CopyBook Name} or Segment: {Segment Name} or Requirement: {Requirement Name} or Program: {Program Name} or Agreement: {Agreement Name} Error: {Parser Message} Line No: {Line Number} |
Upgrade utility will insert the new messages in AsTranslation table and the existing errors in the AsErrorCatalog will be updated by Upgrade utility.
