SR-B67293 · Issue 316457
Autocomplete fixed for complex repeating dynamic layout
Resolved in Pega Version 7.3.1
When using a repeating dynamic layout where each of the records in it had an autocomplete field, selecting a value for any autocomplete always entered the first record's autocomplete. This was an issue with templatization that caused autocomplete to replace the step page with the context's entry handle on the client for data-attributes in cases where it sat inside a repeating structure like RDL. This has been fixed. In addition, the API pega.ui.template.DataBinder.resolveIndex() has been deprecated and the call to it has been removed.
SR-B47122 · Issue 308714
Fixed null-pointer exception for adding file to social media
Resolved in Pega Version 7.3.1
An null-pointer exception caused failure when adding a file to social media. This was traced to a missing null check in the function isRegisteredOnBeforeSubmit in the pzpega_social.js file, and has bene fixed.
SR-B53145 · Issue 317256
Back button on Survey screen works with validation
Resolved in Pega Version 7.3.1
If a Survey screen that validates a question failed that validation, the proper error was generated when the criteria did not match. However, clicking the 'Back' button on the screen caused the validation message to disappear while remaining on the current screen and not returning to the previous screen. This was due to a faulty IF condition in the setValue in SurveyAccessMethodBodyQuestion function, and has been fixed.
SR-B55628 · Issue 315581
New check added for stale clipboard data in StarDependencies
Resolved in Pega Version 7.3.1
When both pyWorkCover and pyTopCaseWork were on the clipboard, the pzStartDependencies function renamed the pyWorkCover to pyTopCaseWork and again back to pyWorkCover after calling pzStartSubCases. However, pyWorkCover had stale data due to this renaming when multiple resolve activity calls happened, leading to pxcoveredcountopen to not decrease when a child case was auto resolved. This stale data occurred due to a known issue with the milliseconds of date time property being rounded when stored in the database column of an SQL server. The resolution is to provide a new overloaded method of OpenIfStale with parameters to skip the deferred list and maintain locking strategy; this will be used in the out-of-the-box Resolve activity instead of Obj-Browse to see if the page is stale.
SR-B56088 · Issue 317045
Revised BuildQuestionPageStream to ensure proper doAction firing
Resolved in Pega Version 7.3.1
Validation was firing before reaching the question page in BuildQuestionPageStream section. This was due to the doAction being called without any check despite a conditional getstream configuration. To fix this, the BuildQuestionPageStream code has been revised to ensure doAction will not be called if the questiongroup is not the current questiongroup.
SR-B56142 · Issue 315911
Decoding support added for localized pyMessageKey
Resolved in Pega Version 7.3.1
When using FormattedText control, pyMessageKey was displaying encoded special characters in some scenarios. This was due to the InstructionsLookup control being used to show the localized value but the Pega lookup tag did not have a mode set to allow decoding. This has been resolved by adding logic to decode received localized text.
SR-B57171 · Issue 317890
pxSystemFlow populated after migration
Resolved in Pega Version 7.3.1
After a major upgrade, old cases did not have the pxSystemFlow property populated. This was due to a missing null check for the migration and has been fixed.
SR-B57192 · Issue 315081
Performance enhancement added to optimize evaluation of 'when' calls in GetFlowData
Resolved in Pega Version 7.3.1
A lot of when conditions triggered as part of GetFlowData out-of-the-box activity were causing slowness when the Java Step (4) did its evaluation. Current screen flow navigation would evaluate all the when rules till the end of the flow to determine the flow navigation. To improve performance, an enhancement has been added to the GetFlowData activity to prepare pyFlowData page from the pyWorkPage. This will build the pyFlowData up to the current step and ignore the future steps. It will be necessary to override the PerformDefaults to pass the new parameter loadNavigationPathForBreadCrumbOnly to GetFlowData to call this new functionality.
SR-B64253 · Issue 321102
pyUsage field cleared in bulk process transfer
Resolved in Pega Version 7.3.1
In Bulk Process, auto-fill of audit notes is based on the pyUsage field on the NewAssignPage. Depending on the trigger method, the property pzBulkProcessItem of either the Work class or Assign class is called. In one of the classes, there is logic to explicitly clear or not copy the pyUsage Field. However, one of them had the value persist despite this, and the behavior differed depending on whether the activity called was Assign- pzBulkProcessItem or Work- pzBulkProcessItem. This was traced to the pyUsage property not getting cleared when "Transfer" was used while processing. In order to create consistent behavior, Work-.pzBulkProcessItem has been modified to not set the value to the clipboard when pyUsage is the property name.
SR-B64439 · Issue 315381
Replaced missing Survey category field on landing page
Resolved in Pega Version 7.3.1
The Survey category field was missing on the Survey landing page even though it existed on the Survey rule form. This field was mistakenly removed from the frequently used configuration options shown on the new landing page, and has been replaced.