SR-A80436 · Issue 278967
Federated Case Management GetNextWork function resolved
Resolved in Pega Version 7.3
When an operator had Work Basket configured with Federated Case Management, the Get Next Work function generated an error. This was due to the GNW settings from the operator IDs of the 'remote' systems not being correctly respected, and has been resolved.
SR-A80436 · Issue 279629
Federated Case Management GetNextWork function resolved
Resolved in Pega Version 7.3
When an operator had Work Basket configured with Federated Case Management, the Get Next Work function generated an error. This was due to the GNW settings from the operator IDs of the 'remote' systems not being correctly respected, and has been resolved.
SR-A83892 · Issue 264462
CreateOperator parameter added to HaveAttachmentSpecificAccess RUF
Resolved in Pega Version 7.3
The HaveAttachmentSpecificAccess RUF has been updated to better handle custom 'when' rules for restricting the ability to delete an attachment. To support cases where only the operator who attached the file has permission to delete it, the pxCreateOperator parameter has been added to the attachment page for use in checking whether the creator of the attachment is the current user.
SR-A86522 · Issue 272062
Event Late triggers expanded
Resolved in Pega Version 7.3
If "Limit passed deadline events" was not set to any value and the enqueue item was still in defer-save and not committed to DB, 'Event Late' was not triggered. Code has been added to properly check and trigger the late notice based on this scenario.
SR-A86522 · Issue 272065
Event Late triggers expanded
Resolved in Pega Version 7.3
If "Limit passed deadline events" was not set to any value and the enqueue item was still in defer-save and not committed to DB, 'Event Late' was not triggered. Code has been added to properly check and trigger the late notice based on this scenario.
SR-A87830 · Issue 258083
PD4ML JAR updated
Resolved in Pega Version 7.3
Metadata dates in a PDF generated with PD4ML are expected to follow ISO 8601 format "YYYY-MM-DDThh:mm:ss+##:##", with "+##:##" being the time zone adjustment based on UTC, but when the time zone was given as UTC (or a time zone with zero adjustment), PD4ML was setting the date as "YYYY-MM-DDThh:mm:ssZ00:00". This consequently generated errors with various PDF/A tools. To resolve this, the PD4ml jar has been updated.
SR-A87830 · Issue 258092
PD4ML JAR updated
Resolved in Pega Version 7.3
Metadata dates in a PDF generated with PD4ML are expected to follow ISO 8601 format "YYYY-MM-DDThh:mm:ss+##:##", with "+##:##" being the time zone adjustment based on UTC, but when the time zone was given as UTC (or a time zone with zero adjustment), PD4ML was setting the date as "YYYY-MM-DDThh:mm:ssZ00:00". This consequently generated errors with various PDF/A tools. To resolve this, the PD4ml jar has been updated.
SR-A87830 · Issue 259106
PD4ML JAR updated
Resolved in Pega Version 7.3
Metadata dates in a PDF generated with PD4ML are expected to follow ISO 8601 format "YYYY-MM-DDThh:mm:ss+##:##", with "+##:##" being the time zone adjustment based on UTC, but when the time zone was given as UTC (or a time zone with zero adjustment), PD4ML was setting the date as "YYYY-MM-DDThh:mm:ssZ00:00". This consequently generated errors with various PDF/A tools. To resolve this, the PD4ml jar has been updated.
SR-A87830 · Issue 261150
PD4ML JAR updated
Resolved in Pega Version 7.3
Metadata dates in a PDF generated with PD4ML are expected to follow ISO 8601 format "YYYY-MM-DDThh:mm:ss+##:##", with "+##:##" being the time zone adjustment based on UTC, but when the time zone was given as UTC (or a time zone with zero adjustment), PD4ML was setting the date as "YYYY-MM-DDThh:mm:ssZ00:00". This consequently generated errors with various PDF/A tools. To resolve this, the PD4ml jar has been updated.
SR-A91779 · Issue 266553
Removed repeating keyword from validation error
Resolved in Pega Version 7.3
Each validation error was causing the word "error:" to be prepended every time the autocomplete results were opened. This has been corrected with the addition of a check in the displayErrors API for harness_accessibility js.