SR-C65841 · Issue 425805
Added handling for cases where Microsoft Internet Explorer causes a SAXParseException
Resolved in Pega Version 8.3
Numerous SAXParseException messages were seen in the log file, and the queryString showed the pyDeleteDocumentPg being referenced. This was traced to the method used by Internet Explorer to construct an HTTP request: Microsoft Internet Explorer sends the header and body of the request in separate TCP packets, but for an unknown reason in this case the body packet goes missing. To resolve this, a toggle has been introduced which will send the pyDeleteDocumentPg request as GET if pega.u.d.GET_REQUEST_DELETEDOCUMENT is set to true in userworkform. In a normal flow without this variable, the request will pass through the normal flow.
SR-C86770 · Issue 426050
Case urgency value will not be reset when processing wait shapes
Resolved in Pega Version 8.3
When a Wait shape was configured with the ‘Users can choose to continue process’ option unchecked, the overall work object SLA urgency was overwritten to 0 when the SLA processed the Wait shape. This was due to the Wait shape using pzWaitTImer, which has all urgency values as 0. The SLA being set to 0 did not occur if ‘Users can choose to continue process’ was checked on the Wait shape because pxSystemFlow was not set to true in that case. To prevent the SLA override, a check has been added that will skip setting the urgency setting if there is a wait shape.
SR-C82453 · Issue 426075
Added handling for cases where Microsoft Internet Explorer causes a SAXParseException
Resolved in Pega Version 8.3
Numerous SAXParseException messages were seen in the log file, and the queryString showed the pyDeleteDocumentPg being referenced. This was traced to the method used by Internet Explorer to construct an HTTP request: Microsoft Internet Explorer sends the header and body of the request in separate TCP packets, but for an unknown reason in this case the body packet goes missing. To resolve this, a toggle has been introduced which will send the pyDeleteDocumentPg request as GET if pega.u.d.GET_REQUEST_DELETEDOCUMENT is set to true in userworkform. In a normal flow without this variable, the request will pass through the normal flow.
SR-C89316 · Issue 426076
Lower major ruleset versions will not be considered during design time validation
Resolved in Pega Version 8.3
After circumstancing a rule by property and withdrawing the rule in higher version, the same rule was circumstanced by template. Later after major skimming, attempting to perform a save-as of the circumstanced template rule resulted in an error stating that the circumstanced property already existed. During design time, the system validated the rule with rules from all other ruleset versions. In this corner case where a property-based circumstanced rule was withdrawn and then skimming was performed, the error occurred because it was being saved in a different major ruleset instead of into the same major ruleset. In order to better handle this condition, the system will not consider rules from lower major versions during design time validation.
SR-C79366 · Issue 426093
Corrected issue with Field Level Auditing re-adding deleted page list items
Resolved in Pega Version 8.3
Pressing a Save button that invoked the pyTrackSecurityChanges data transform caused deleted items to be added back to a page list. This was caused by pyPropertyIndex being set on the removed page in RUF-pzAddHistoryMemosForPageList, and has been corrected by removing that unneeded action.
SR-C87399 · Issue 426184
pzEditSkills activity updated for better skill matching
Resolved in Pega Version 8.3
In the pzEditSkills activity, a select skill is added to the operator. A check is made using a comparison of pyRuleName equal to pySkillLabel to see whether this skill exists in the system; if it exists it is directly added to the operator profile, and if it does not it is created and added to the operator profile. However, pyRuleName uses a short skill identifier string, for example ‘XML’ whereas pySkillLabel is the longer human readable string, for example ‘XML programming skill’. Therefore, it was possible for Pega to determine the skill did not exist and proceed to creating a new skill with pyRuleName equal to the pySkillLabel of the existing skill in the first available unlocked ruleset. In order to ensure the proper matches are made, the pzEditSkills activity step 4.1 has been modified to get the rule name instead of skill name.
SR-C88948 · Issue 426226
Command-line BIX extract properly exits with failure status if the rule is not found
Resolved in Pega Version 8.3
Running a BIX extract from the command line was returning 0 for both success and failure. This was caused by the error message in this scenario not properly setting the flag if an extract rule did not exist, and has been corrected to ensure the command exits with status code 1 if it is not able to get the list of extract rules.
SR-C86133 · Issue 426387
Logic updated to resolve Strategy Parser error using dateTimeToBigDecimal
Resolved in Pega Version 8.3
After upgrade, a Strategy run was failing with a SemanticAnalysisException error indicating "Type Mismatch in node 'ILTernaryOperation': False branch does not equal return type (DECIMAL ==> DATETIME)". Upon investigation, the issue was traced to a property set component with an expression using the "DateTime•dateTimeToBigDecimal Pega-RULES:08-01-01" function. To resolve this, the logic has been modified to set the return type of ternary node from the Java type, and to check that True and False branches match this return type as well.
SR-C89656 · Issue 426424
Case urgency value will not be reset when processing wait shapes
Resolved in Pega Version 8.3
When a Wait shape was configured with the ‘Users can choose to continue process’ option unchecked, the overall work object SLA urgency was overwritten to 0 when the SLA processed the Wait shape. This was due to the Wait shape using pzWaitTImer, which has all urgency values as 0. The SLA being set to 0 did not occur if ‘Users can choose to continue process’ was checked on the Wait shape because pxSystemFlow was not set to true in that case. To prevent the SLA override, a check has been added that will skip setting the urgency setting if there is a wait shape.
SR-C87809 · Issue 426461
Checkbox control formatting handling improved
Resolved in Pega Version 8.3
Changing the Control format of a pxCheckbox was not properly reflected in the optimized CSS during Preflight optimization. Investigation showed that the Preflight crawler for pxCheckbox was picking up the checkbox's label format and not the control format (shown in the property panel dropdown as Standard, charts, lists, and summaries). To resolve this, the crawler's handling of pxCheckbox has been updated to ensure the proper checkbox control format and associated label formats are reported out.