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.
SR-C88309 · Issue 426997
Tooltip added for data table refresh icon
Resolved in Pega Version 8.3
An enhancement has been added to provide a tooltip for the refresh icon during data table edits.
SR-C88015 · Issue 427060
Null check tuned for hotfix bulk import
Resolved in Pega Version 8.3
If a hotfix contained any changes to rules, the import failed with a null pointer exception.This was traced to a null bulk object. Investigation showed that if debug logging was enabled on ESBulkIndexerEmbedded, the system was attempting to get a value off of customBulkRequestBuilder, an object that could potentially be null but that was not subjected to a null check until after the debug statement. This has been resolved by adding a conditional within the debug statement to output a different message if the builder is null, preventing this issue from occurring.
SR-C87363 · Issue 427063
Post-merge message expanded for locked application
Resolved in Pega Version 8.3
When the Application rule required a password to update, merging a branch caused the system to display the error "Fail to complete merge - see errors below". However, no errors were displayed and the branch was merged successfully. The error was intended to indicate that when the application was locked, the branch would not be deleted after the merge. In order to clarify, this, the error message has been expanded with the following: "The application that contains this branch or branches is currently locked. Unlock the application if you would like the branch or branches to be automatically removed from your application after merge."
SR-C78674 · Issue 427065
Pages removed from pagelist while offline sync properly
Resolved in Pega Version 8.3
After removing pages from a pagelist in the mobile app while offline, the removed pages were restored and sometimes duplicated following an online sync. This was traced to deep copy parameter not deleting entries in the canAdvance API, and has been corrected.