Pega Infinity™ includes an industry-standard patch release process to simplify and maintain high-quality releases. Several cumulative patches are released a year for each release stream. The Resolved Issues page contains information about client-reported issues that have been addressed for the specific release.
For a formatted complete set of the Resolved Issues for this release, download the PDF attachment at the bottom of this page. (Note that you must be logged in to access the attachment.)
| Ticket # | Issue # | Title | Description | |
|---|---|---|---|---|
| SR-C64192 | 421338 | Activity Run allows autocomplete control for data transform | An enhancement has been added to allow changing the control from Dropdown to Autocomplete when an activity is Run and the "apply data transform" checkbox is checked. | |
| SR-C67397 | 421638 | Added check for missing rule data when using abstract class in CSS | Including CSS optimization with abstract class in the Advanced tab of the 'Add Optimization' Screen resulted in a Null pointer exception error. This has been resolved by adding a check for missing data from a rule to make the system more resilient in its handling of a corrupt flow-action clipboard page. | |
| SR-C71221 | 427921 | Radio buttons maintain arttributes after dynamic layout table reordering | When using a table configured in a popup where each row of the table was rendered using a dynamic layout that included radio buttons within it, the radio button fields were being cleared when the rows of the table were reordered. This was caused by the radio buttons not having unique name values, and has been resolved by using the updatehandles function in the pega_ui_repeatlayout js file to set the checked attribute based on the selected value after the reorder. | |
| SR-C74054 | 422025 | Handling added for summary columns in Export to Excel | When a field has an aggregate function in Report Definition, the column alias changes and is not the same as the property name. The consequence is a mismatch between the result set column name and the property name from the property list created beforehand. This results in blank fields when using the "pxDownloadDataRecordsAsCSV" activity for Export to Excel. In order to support the export of summarized columns in Report Definition, an enhancement has been added that uses the column label as an alias for aggregate fields in the native SQL builder of the exportData API to form a map between the property name and the alias name and use it while iterating over the result set. | |
| SR-C74642 | 424006 | Data page reference properties will not be resolved if hidden | In order to improve code efficiency, in conditions where a text input field configured with a 'When' visibility condition references a property which is present in a data page, the system will skip the process of resolving the property name if the 'When' rule is evaluated as false. | |
| SR-C74648 | 422905 | Autocomplete arrow placement corrected in Right to left local mode | When using the Autocomplete control, the blue arrow was seen to have an incorrect placement/orientation in RTL mode. This was traced to the autocomplete background-image in RTL mode being the same as that for LTR, and has been resolved by adding specific background-image for RTL. |
|
| SR-C74784 | 428818 | Added file truncation to HCClient.txt to ensure data integrity | When a work object model contained more than two embedded lists, simple save corrupted the JSON in the local storage work object browser. Investigation traced the issue to using the same file without truncating its content. Because the HCClient.txt file in Rule: webwb - pzpega_mobile_settings - js was reused while displaying items in DocumentViewer, writing a smaller amount of data into it than the previous write left orphaned content in the file that corrupted the new data. To resolve this, the file content will be truncated before writing new data into it. | |
| SR-C75205 | 424476 | Invalid text entry in Date control field now returns current timestamp | Inconsistent behavior was seen between entering an invalid date in numeric vs text format. Entering an invalid date in number format resulted in the system replacing the entered value with the text “Invalid date”. Entering an invalid date in text format caused the system to retain the value and not show a validation error. This has been corrected by modifying the date/time formatting for both text and numerical input to return the timestamp in case the entered value is incorrect. | |
| SR-C75497 | 427436 | Resolved "no items for filters applied" error in column filtering | When trying to filter a column, the options did not appear on the filter and the error "No items for the filters applied" was displayed. This was due to the Declarative index join being removed on save and on run even though it was referenced in the class join filters. To resolve this, logic has been added to the pzCopyPySource activity to loop through all class joins and their filters so both sides of the filter are checked for references to a declarative index join. | |
| SR-C75566 | 420773 | Added null check to avoid DisplayCardAccountHeader rendering issue | When the out of the box section DisplayCardAccountHeader was created by View editor and then converted to full section editor, the embedded sections were empty or not seen. This was traced to the design view javascript hitting an error which caused the design view rendering to fail. To correct this, pzpega_ud_gridlayout_model has been updated to wrap the line in question with a null check and set the value to empty string if it doesn't already exist in the model. | |
| SR-C75723 | 421826 | Rollback filter query updated to handle very large classes mapped to the same history table | When rolling back the imported product file using deployment manager, the error "DatabaseException caused by prior exception: org.postgresql.util.PSQLException: ERROR: column "pzinskey" does not exist" was seen. This was traced to the rollback process picking the already processed items from the history table due to an incomplete filter query that occurred when there were more than 1000 classes mapped to same history table. This has been resolved. | |
| SR-C76412 | 425189 | Content type header removed from default inclusion in JWT token to support MS integration | In order to integrate Pega with Office365 to use the Outlook API to Send and Get messages, an access token is required as a part of Authentication process. For obtaining an access token from the Azure directory, the process is to follow the OAuth 2.0 client credentials flow which requires the generation of a JSON Web Token (JWT) with the required Header, Payload and Signature. However, because Pega adds the tag "cty": "application/json" by default, using the out-of-the-box 'Token Profile' rule to generate the JWT and pass the same in a REST call to Microsoft was resulting in a error response indicating that there was an unsupported token header. This has been resolved by removing the content type header in the JWT token. | |
| SR-C76417 | 430546 | Check added for reference function in DB2 join | In DB2, when a sub-report column contained a function that was used for a join condition in the main report, an invalid filter property error was generated while saving. This was traced to the edit validate rule checking for the data type of both of the properties used in the join, and has been resolved by adding a check to see if the join operand is of function 'reference'; if so, the system will resolve the function, check for data type property, and set it. | |
| SR-C76668 | 424444 | skipDocsRecreation option added to remove flickering during application launch | In order to avoid visible flickering resulting from a dynamic container refresh conflicting with custom code during application launch, an enhancement has been added that can be used to skip the SDM refresh functionality based on the "pega.u.d.skipDocsRecreation" JS property. This can be enabled in Userworkform. | |
| SR-C79482 | 424536 | DSS added to allow custom timeout for BIX query | The BIX query to retrieve the blob column was taking up to 60 seconds for large volume, causing timeouts. Previously, the extract defaulted to using repost pzSample which is internal/final and has a default timeout of 30 seconds. In order to avoid timeouts, the new DSS "BIX/selectQueryTimeout" has been added to allow setting a custom value. Further refinements will be made for multi-tenant environments in a future release. | |
| SR-C80129 | 421416 | Data type search adjusted to handle text query | After creating a data type and adding a class join and then delegating the data type to a user, the data type search bar in the configuration tab was not working. This was traced to the decision search filter using "=", which did not handle a text query. This has now been changed to use "Contains" to resolve this issue. | |
| SR-C80129 | 425386 | Enhancement added to hide class join warning from end user | An enhancement has been added to hide the joined class warning message at the end user portal if the section pzManageRecords is delegated to the user. This is done by by checking pxLimitedAccess on the pxThread clipboard page. | |
| SR-C80215 | 421849 | Migrated Data Flows open correctly from the data flow landing page | After upgrade, Data Flows made in an earlier version could not be opened from the data flow landing page. Instead, a generic error screen was displayed and an NPE on activity pxMigrate was logged. This was caused by a missing null pointer check, and has been corrected. | |
| SR-C80372 | 425075 | Oniine help files updated to more completely reflect SAML Authentication Rule Form fields | The online help files have been updated to reflect that the SAML Authentication Rule form has various fields including Entity Identification, Login Location, Logout protocol binding, and Artifact Resolution Service Location that support GRS syntax (=D_myDataPage). When configuring SAML it is also required to update WebSSO Service Package to point to the Access Group as the Application Access Group. | |
| SR-C80948 | 421765 | ProfileLink control updated to resolve opening issue | The profile was not opening when the Operator Profile link was clicked. This was traced to certain functions having been moved to javascript files that were not included by default in the ProfileLink control. To correct this, the control has been modified to include the needed javascript files and the appropriate references have been updated to match. | |
| SR-C81410 | 422137 | Radiobutton aria-label enhanced to retrieve localized field value | Localization code has been added to the pzpega_ui_template_radiogroup file to support using RadioButton aria-labels for Field value. | |
| SR-C81829 | 419227 | pxCoveredCountOpen value decrease corrected | When a flow reached the resolved stage (Resolved-Withdrawn), pxCoveredCountOpen was reducing the count by 2 instead of 1, eventually causing the value to go negative and prevent any further work objects from being marked as Withdrawn. Investigation showed the "Update status" activity was being called twice due to the Temporary WorkPage used to delete assignments persisting and appearing as a duplicate pyWorkPage. This caused an issue when using findPage by pzInsKey. To correct this, the "pxDeleteAssignmentsForWork" activity for Step-15 has been modified to explicitly remove the temporary WorkPage after the assignment is deleted. | |
| SR-C81855 | 421403 | Check added to format simplified Chinese date generation to match system expectations | When the browser language was set to Chinese (simplified) and a template was used for an application, an invalid date exception was generated. This was caused by a difference in handling between the moment.js function used to format the datetime, and Pega. The moment javascript formats dates with the below 6 meridiem for Chinese locales (zh-cn, zh-hk, zh-tw): 凌晨 - Early morning 早上 - morning 上午 - morning (AM) 中午 - noon 下午 - in the afternoon (PM) 晚上 - at night But the Pega server only accepts two standard meridiem i.e. 上午 - morning (AM) and 下午 - in the afternoon (PM). Due to this, using an unsupported setting resulted in an error. To resolve this, a check has been added for the Chinese locales (zh-cn, zh-hk, zh-tw) that will adjust the non-supported formats to be either 上午 - morning (AM) or 下午 - in the afternoon (PM)." |
|
| SR-C82059 SR-C68134 |
423071 423617 |
Support added for configuring key stores using prconfig or system properties | Previously, stream service only supported key store and trust store configuration using Data-Admin-Keystore instances. Unlike cluster encryption, it did not allow the configuration of key stores using prconfig or system properties. In order to align Stream service SSL configuration with the rest of the platform, support has now been added for the following system and prconfig properties: -Dpega.cluster.keyStore -Dpega.cluster.keyStorePassword -Dpega.cluster.trustStore -Dpega.cluster.trustStorePassword |
|
| SR-C82244 | 421173 | Enhancement made to allow passing of URL in actionset via the DX API | When using the action "Open URL in Window" and the option "Use Alternate Domain" to pass a URL that is in saved in a property, the name of the property was passed when using the DX API instead of the URL. To allow this use, an enhancement has been added to support storing a last submitted value and a reference so that an action set with a property reference can return a reference object with lastSavedValue and the reference name attached. | |
| SR-C82254 | 421056 | Support added for saving draft survey flows in production level 5 | With production level set to 5, creation of a survey was generating two errors: in UI, "Default survey flow creation failed", and in trace, "Update record failed: .pyDraftModeON". Because in most cases Survey authoring would be done in a system with a lower production level where users would not see any issues, the code did not include support for saving draft mode flows when the system was set to production level 5. This ability has now been added to support this use. | |
| SR-C82353 | 426014 | CorrNew loop logic updated to handle custom notifications | When CorrNew was used to configure a email smart shape in a custom notification, having a 'not available' party as the last parameter was leading to the mail not being sent. To resolve this, the 'while' loop logic has been updated to iterate over the workparties for every party role. | |
| SR-C82408 | 422327 | Repaired instance insertion for REST connection invoked via Queue | After upgrade, the REST connection invoked in an activity which in turn called OOTB ProcessQueue was not getting the response into the SYSTEM-QUEUE-EXECUTIONREQUEST-CONNECT-CREATEBOOKING instance. The right response was observed coming from other source systems in the logs, and the work object status also changing as expected. This has been resolved by exposing a DSS to revert to the old behavior of Response being present in the queueItem when a connector is queued for execution. | |
| SR-C82480 | 421487 | Column Headers properly aligned after expand/collapse of Tree Grids | When using a hierarchical table - tree grid with a configuration that included Width of content-Pixels(Fit Content), a Fixed (pixel) size grid, and Freeze Header, expanding and collapsing back the contents resulted in a misalignment of the column headers. The fixed header implementation makes use of multiple table layouts which have to kept in sync via javascript; this issue has been resolved by rewriting the fixed header implementation to call setHeadersWidth on expand/collapse of a treegrid row. | |
| SR-C82530 | 420608 | Atmosphere XSS Vulnerability fixed | Atmosphere has been updated to close a potential XSS vunerability. | |
| SR-C82549 | 422847 | Check added to getRuleNameFromInsKey to clip version name from rulseset name in the dataflow | After changes were pushed to the datasets, dataflows were failing on a DT2 environment with an error related to rule resolution and a failure to find a specific property. The dataflows did not fail on a DT1 environment. Investigation showed that if the ruleset name was empty and the ins key was used to get the rulesetname, a mismatch occurred with the returned value due to the version information being included in the name. To resolve this, when a rule name is retrieved by getRuleNameFromInsKey, the system will check if aObjClass is Rule-RuleSet-Version. If so, the version part will be trimmed. | |
| SR-C82619 | 421024 | 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). |
|
| SR-C83050 | 422977 | IE width calculation fixed for imported built-on with dymanic layout | After upgrade, the Built On input for the application screen in Designer Studio was not rendering in the IE11 browser if dynamic layout was used. This was caused by a browser-specific issue with width calculation for pzDefinition, and code has been added to handle this issue. | |
| SR-C83058 | 424154 | Assertion parse rule XML regenerated to resolve data mapping issue | The parse-xml rule(NS-366601360 • Assertion) has been regenerated to resolve an assembler issue with mapping data to properties. | |
| SR-C83468 | 424950 | Legacy multipart upload support added for very large hotfix catalogs | After a package containing 100+ hotfixes was installed, the fixes were not visible in the Hotfix Manager page even though the database status showed them as "Installed". Investigation showed that performing a system scan on the catalog upload was resulting in thread dumps while decoding the request URL due to the control used for catalog upload posting the entire content in form data rather than sending a multi-part request. To unblock this use case for catalogs with huge data, the system has been updated to perform a legacy upload where a form submit is used with content-type as "multipart/form-data" rather than sending the entire data in the request header. | |
| SR-C83615 | 424946 | Support added for hiding unwanted category reports | After upgrade, a customization used to hide unwanted out-of-the-box category reports was not working. This was due to the pyServiceLevelPerformance and pxSimulations category rules not being included as part of the pyOOTBVisibleInBrowser 'when' rule that is specified for Display in the report browser 'when' setting. These two category rules - pxSimulations and pyServiceLevelPerformance - have now been modified to reference the 'when' rule pyOOTBVisibleInBrowser so categories may be hidden as desired. | |
| SR-C83808 | 421298 | FIRST aggregate in bucketed window fixed | FIRST aggregates were not giving the correct results if used in a Sliding Time window together with an average aggregate. This was traced to an incorrect implementation of FirstAggregatorHolder.substractAggregate which used propertyIndex to get aggregate value (which was not correct in this context), and has been fixed by using the correct index in FirstAggregatorHolder class. | |
| SR-C83899 | 421068 | Alternate RD added for sub class union that will skip blob open | The screen load was taking 4 seconds or more to load when a parent case had 500+ child cases, leading to timeouts and issues with case processing. This was caused by the system performing a database open of all the child work items for building the tree: because different child items are mapped to different work tables, a single RD would not suffice for fetching all child items. This meant a work record was opened and child inskeys grouped into different groups based on table mappings, then the RD was called multiple times to fetch the details. To resolve this and avoid blob open, a report definition that performs a union on all sub classes has now been put in place. Execution is based on a parameter to avoid any backward compatibility issues. This is used by overriding the 'pyPopulateCaseContentsWrapperExtension' data transform and setting param.useOptimizedQuery to 'true' to override the database open. | |
| SR-C83915 | 421168 | Enhancement added to support property reference name for section include | When requesting the view of a section from a repeating dynamic layout where the name of the section is taken from a property, the DX API returned an error on the tracer indicating "Invalid value for aReference passed to com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.getString(String)". This has been resolved by adding an enhancement to support using a property reference for section include. | |
| SR-C84033 | 422745 | Added handling for legacy page adaptors to get all messages | If a validation message was present on the Clipboard, the front-end screen was turning blue and displaying the error "There has been an issue, please consult with administrator". This happened when getMessagesAll was called for pyWorkPage and an auto-populate property was present in the embedded pages/properties. To resolve this, cast has been removed when getting all messages and a new API has been added for legacy page adapters to get all messages. | |
| SR-C84116 | 423756 | Added container handling to make optimized grid table visible in action top | After upgrade, if the Optimize code checkbox was checked on a table and visibility was applied over grid header, the table was not visible in the UI. This scenario only happened when a grid was upgraded from non-optimized to optimized with some visibility condition added, and was caused by the system not yet supporting the visibility features in action top for an optimized grid. To resolve this at this time, the system has been updated to not honor the visibility at container for an optimized grid so the table will be visible. | |
| SR-C84135 | 424531 | Metadatatree updated to be function-scoped in UI to resolve custom tab control display issue | When switching rapidly between two custom tabs, especially clicking in and then clicking away before the busy icon could be displayed, the section containing the tab controls was intermittently refusing to display. Refreshing the browser or clicking on the Pega button made the section visible again. This was traced to the template "metadatatree" getting overlapped with subsequent template processing due to a timing issue as "metadatatree" was being maintained in the global window object. To resolve this, "metadatatree" has been updated to be function-scoped in renderUI to avoid timing issues. | |
| SR-C84167 | 422477 | Corrected issue with Field Level Auditing re-adding deleted page list items | 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-C84609 | 424884 | CustomFilter clipboard page now retained after section submit | When a Report Definition was configured to display filters using a custom section, selecting the filter property value and submitting the section resulted in the CustomFilter clipboard page being deleted automatically. In order to prevent the clipboard page from being immediately cleaned up by the doUIAction activity, a step has been added to the pzCreateCustomFilterPage activity that will set the pyRetainPage property to "true". | |
| SR-C84643 | 423855 | Logs now support RandomAccessFileAppender | Support has been added to the LogFileDownload and LogViewer HTML final rules for using RandomAccessFileAppender. This is in addition to the existing support for RollingRandomAccessFileAppender and RollingFileAppender. | |
| SR-C84788 | 422937 | Handling added to maintain custom modal template name after errors | When using a grid where each grid row had an Edit button which launched a modal dialog with a custom modal template, the post action activity of the flow action introduced error messages on a top level page (not on primary or pyWorkPage). Clicking the submit button again caused the modal dialog size to shrink and not work after that. This was traced to the second submit using the system's pyGridModalTemplate instead of the custom modal template due to the modal submit button being replaced with new markup. To resolve this, the modal launch will now use the "pega.u.d.submitModalDlgParam.modalSection" variable which will have the modal template name. In addition, a check has been added to ensure this is not passed as null. | |
| SR-C84921 | 424317 | Connection Manager uses keyring for null prconfig password | After upgrade, credentials from BIX keyring were failing when using BIX via commandline rather than prconfig. This was traced to a behavior change in the Connection Manager, and has been resolved by modifying the Connection Manager to look up the password from the keyring when given a URL configuration where the password is null in prconfig (URL connection only). | |
| SR-C84939 | 428564 | setTenantName API exposed in the rules alyer | In order to support more efficient message ingestion in a multi-tenant environment, the setTenantName API has been exposed in the rules layer. | |
| SR-C85035 | 421947 | Added getIfPresent check for Field Value parameters with pzAPICreateJsonForView | Calling pzAPICreateJsonForView was altering case values if localized field value parameters were added. This has been corrected by performing a getIfPresent and getIfString on the property pyFieldValueParams so field value parameters will not be added to the main page if they're not present. | |
| SR-C85096 | 423236 | XSS check logic updated for pyPosition | Additional logic has been added to prevent the injection of javascript into script tags while rendering Smart Tips. | |
| SR-C85312 | 424037 | Check added for custom section use in Summary report exported to Excel | Criteria were missing when Export to PDF was used for Summary reports filtered by a custom section. This was caused by the needed pyQueryTokenList not being repopulated for the export in the case of custom section use, and has been resolved by adding a summary report check in the pzIncludeCustomFilterSection section before invoking pzClearRDTempFilters function. | |
| SR-C85315 | 422729 | New Activity added to ease cleaning up Thread-level data pages | It is an expected behavior that the system will not automatically remove read-only data pages, as the decision of which pages need to be removed is system-specific. However, it was noted that an accumulation of Thread-level Data Pages may eventually cause performance degradation. In order to make it easier to clean these up, the new extension Activity "pyRemoveThreadLevelPages" has been introduced that is called from the DoUIAction activity. | |
| SR-C85614 | 427439 | BIX extract connection leak repaired | The first time that a BIX extract was run it failed with a timeout. Running it again immediately was successful. Investigation showed that if the BIX connection timed out, the connection was not being returned to the connection manager due to a failure to reset the autocommit for a connection that partially ran but was not properly closed. This has been resolved by adding handling that will return the connection to the pool and clear the map if there is an exception. Further refinements will be made for timeout issues in multi-tenant environments in a future release. | |
| SR-C85752 | 425073 | New MaxFileSize extension point added for pyMaxFileSizeViolation | A severe guardrail warning was raised when saving the activity pyMaxFileSizeViolation into a ruleset. This was traced to the CheckForWarnings Activity of Rule-Obj-Activity which checks if any activity referenced is an internal activity. Activity pyMaxFileSizeViolation was calling the internal pzGetCMMaxFileSize activity, and the warning appeared because the py activity was overridden in the application ruleset. To resolve this and add an extension point, pzGetCMMaxFileSize has been modified to a new data transform called pxGetCMMaxFileSize, which is called in pyMaxFileSizeViolation. | |
| SR-C85853 | 425288 | Currency codes updated | The list of Currency Codes has been updated with the latest ISO changes, including Venezuela and Sao Tome & Principe. | |
| SR-C86126 | 423258 | CSV import for delete date values will be formatted before row processing | In order to support using CSV import for delete purposes, date/time class keys will be formatted before processing the row. | |
| SR-C86133 | 426386 | Logic updated to resolve Strategy Parser error using dateTimeToBigDecimal | 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-C86260 | 424928 | RecordsEditor Section- Parameters for HideDelete and HideAdd held on clipboard for use | On initial load of a RecordsEditor section, the delete and add options were properly hidden from the user. After using any sort option on any column, the parameters were not persisted and the delete and add icons became visible. To resolve this, the implementation has been updated so that the pyHideDelete and pyHideAdd parameters will be read from myParamPage on the initial load and saved on a clipboard page for use. | |
| SR-C87399 | 426183 | pzEditSkills activity updated for better skill matching | 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-C87665 | 424611 | CPU time will be fetched from MBeanServer instead of the JRE application to provide consistency | The value of CPU time in the Enterprise health metrics was being given in nanoseconds instead of seconds after the IBM JRE version was upgraded by applying Websphere Application Server patches. The CPUTimer is a platform class which has logic specific to different JRE vendors; in order to provide consistent results regardless of which JRE is used, the system has been updated to always fetch the values from the MBeanServer. | |
| SR-C87881 | 427100 | Additional dropdown options exposed for RD column definitions | When using Column formatting in Report Definition ruleform, the "Negative format" option was losing its custom style after opening and submitting the "Format" popup using the magnifying glass. This was caused by the submitted popup overwriting the inherited style reference. Previously, the style ref options were hidden from the dropdown because the same UI is shown in the ruleform and the end user portals and the desire was to avoid end user confusion. In order to support developer use, pzPopulateNegativeFormat has been updated to expose the missing options in the dropdown. | |
| SR-C88236 | 428779 | Debug logging added to HTTP API for improved diagnostics | Debug loggers have been added to the HTTP API to provide more complete diagnostics for an error where users are redirected to login screen after providing valid credentials. As a workaround, restarting the node server will resolve the login issue. | |
| SR-C88309 | 426996 | Tooltip added for data table refresh icon | An enhancement has been added to provide a tooltip for the refresh icon during data table edits. | |
| SR-C89316 | 426077 | Lower major ruleset versions will not be considered during design time validation | 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-C89656 | 426423 | Case urgency value will not be reset when processing wait shapes | 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-C89675 | 428596 | Case name caption security inserted | In order to protect against the possibility of executing malicious JavaScript code by entering an appropriately modified name while adding new case type, pyCaption in menu items has been made HTMLSafe by converting JSON through the GSON library. Additional handling for Firefox has also been added to normalize tabName to properly display Recents. | |
| SR-C90261 | 428122 | Hotfix installer updated to adhere to installorder file included in the package | In order to ensure hotfixes are always installed in the proper order, the installer has been updated to iterate over a set that is ordered according to the INSTALLORDER.PEGA file included in the DL file at packaging time. | |
| SR-C91521 | 428627 | DX API updated for improved security | Modifications have been made to the DX API to improve system security. |