Resolved Issues

JavaILCompiler updated to skip a type convert when generating code for a ternary operation

A compilation error was generated when attempting to save a Data Transform with a java expression giving the ternary as boolean. In this case, the pyWorkPage.Channel was set to  @java("tools.findPage(\"TempInputAccelPage\").getProperty(\"Channel\").getMessageCount()>0") ? "" : pyWorkPage.Channel.

The system previously used EL code generation, which had a gap which allowed such expression to work. Since the system now uses IL code generation, this expression failed. In order to ensure backwards compatibility, logic has been added to  JavaILCompiler to skip a type convert when generating code for a ternary operation where the source is ILProgramText (java expression).

Updated the documentation for enabling debug logging during upgrades

The documentation regarding enabling debug logging during upgrades has been updated to reflect the following information: To enable debug logging during installs, upgrades or prpcUtils invocations: The template logging configuration for installs, upgrades and prpcUtils is located within the scripts/config directory of the Pega Platform distribution. To change what gets logged, modify the prlog4j2.xml file (refer to https://logging.apache.org/log4j/2.x/manual/configuration.html#XML). Some of the utilities involved in the install and upgrade processes use java logging. To impact what is logged by these tools, modify the deploylogging.properties file in the same directory.

Import ordering shifted to prioritize Functions and Libraries

A runtime error was seen when running DataTransform getbranchandcbsadetails. Investigation showed that when getbranchandcbsadetails was imported, the RUF it referenced was not imported beforehand. To resolve this, the import ordering has been reworked to prioritize Function and Libraries by shifting Rule-Utility-Library and Rule-Utility-Function to be after Rule-Obj-Property* in the import order.

ConvertAttachmentToPDF Activity deprecated as part of PDM removal

As the Pega Distribution Manager is no longer offered as part of the Pega application, the "ConvertAttachmentToPDF" function previously offered as part of PDM 3.3.5 is now [Withdrawn,Deprecated] from 'Pega-ProCom' & 'Pega-ProcessEngine'

Tab header value works for SSO

The Tab header value was not updated with the rule name or Work Object ID when SSO authentication was used with sub-domain URLs. This has been fixed.

Fixed incorrect number formatting application in Spanish locale

Errors were seen for fields having pxCurrency and pxNumber control when using the Spanish locale (es_CR):1. After entering an amount like 917.25 on a field which is configured to refresh section on click/on change, clicking on the field caused the decimal to move and resulted in multiplying the amount by 100 (91725.00) 2. Fields did not allow entering a comma as a decimal delimiter or were stripping the comma. This has been fixed by modifying pzGenerateTextinput assembly to not apply formatting for numbers in some specific locales.

Corrected additional Fork connector

When using a Fork decision shape configured to skip assignment conditionally, an extra connector link appeared in the screen flow. This has been fixed.

Handling added for empty queue in DeleteDeferred

The DeleteDeferred method was setting a step status fail after trying to delete a non-existent queue item. A catch block has been added which will back out if the SLA queue deletion fails.

Documentation updated to assist in fixing UnresolvedAssemblyErrors when resolving RUF rules

To address UnresolvedAssemblyErrors resolving RUF rules, the following help topics have been updated: Selecting-import-file-tsk Importing-cli-tsk Importing-cli-web-tsk To include the following cautions: * Review the archive contents to better understand which rule sets are capped and to determine the relatives risks and benefits of running uncapped rule sets. * Do not import an archive into an active runtime instance of Pega Platform because the archive can overwrite rules in use.

Flow breadcrumbs improved for temporary objects

Issues were seen with navigating a screen flow properly when the work object was temporary. The screen flow contained sections with some required properties and “Allow errors” was checked to support navigating back and forth when there were errors; clicking the breadcrumb to go back in the flow worked, but clicking Next to go forward again did not proceed to the next flow action. This was due to missing validations, and changes have been made to the Complete Assignment function to handle the errors for Temporary and Non-Temporary Cases.