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 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.)
Low-code Application Development
Case Management
8.1.7 Patch Resolved Issues for Case Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| SR-D23723 | 503090 | pxGenerateExcelFile updated for handling blank dates | When using a custom template for exporting to Excel, blank DateTime property column values defaulted to the current date. To resolve this, the pxGenerateExcelFile activity has been updated to ensure that an empty date will be exported as blank and that given dates will appear in the correct datetime format. | Case Management |
| SR-D24950 | 494566 | Added explicit step page to resolve null-pointer exception with custom error message | A null pointer exception was generated during case run time harness refresh after a custom error message was inserted. This was traced to a blank step page related to the custom message, and has been resolved by adding a primary step page at step 10 of the New(Work-) activity to prevent the null-pointer exception on harness reload. | Case Management |
| SR-D42679 | 509565 | oLog.infoForced has been replaced with oLog.debug in GetAssignmentDetailsInternal to reduce excessive logging | The Rest API used by Robotics was generating excessive logging on the application server due to PzGetAssignmentDetailsInternal generating several lines of logs with each REST call. In a high volume system, this can make the logs difficult to utilize. To resolve this, oLog.infoForced has been replaced with oLog.debug. |
Case Management |
| SR-D5904 | 490489 | Discard changes dialog now showing for local actions | After having modified case data without saving and clicking on a menu entry (left menu, search, ...), the system shows a dialog box to ask the user to confirm it is ok to discard changes. However, this confirmation dialog did not work with local actions, leading users to lose their work without any warning nor any way to step back. This was traced to a difference in the dirty form check, which was not present when launching a local action from a case. An enhancement has now been added to the handleMenuAction js function in pypega_ui_harnessactions.js which will perform a dirty form check with a prompt. | Case Management |
Cloud Services
There were no 8.1.7 Resolved Issues for Cloud Services
Conversational Channels
There were no 8.1.7 Resolved Issues for Conversational Channels
Data Integration
8.1.7 Resolved Issues for Data Integration
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| SR-D18853 | 503274 | Visibility on client check removed to enable Pulse on click | When Pulse was configured on click of a icon, the comment section was not visible. Investigation showed that at the time of DOM load, pyMessage property was not available in the DOM because 'Run visibility condition on client' was checked by default. Visibility on client checks have been removed to resolve this issue. | Data Integration |
| SR-D21555 | 501107 | Resolved command line BIX/PRPCUtils creating unreachable nodes | BIX and PRPCUtils scripts were creating nodes that showed as unreachable or that were never cleared. This was traced to a code change that resulted in nodes starting as stream nodes unless given a node type or DSS settings, and has been resolved by setting the asyncExecutor/enable setting value as false in the prconfig.xml. The BIX command line JVM argument should also be set to NodeType=BIX. | Data Integration |
| SR-D25753 | 499269 | Added WebSphere Liberty Profile to BaseEnvironment.guessServerEnvironment | While trying to add a node to Decision data store nodes via Designer Studio > Decisioning > Infrastructure > Service, the error "Service DDS:** java.lang.NullPointerException" was seen, and it was not possible to add a node or save any configuration. This was caused by an incomplete profile for Websphere Liberty, causing the com.pega.pegarules.priv.context.BaseEnvironment.guessServerEnvironment() API to return 'unknown' as the answer when WLP was used. This has been fixed, and the API will return "Websphere" for Websphere liberty profile as well. | Data Integration |
| SR-D29034 | 500682 | Added support for JSON mapping of deep nested pagelist objects | An exception occurred when using a JSON data transform in the service activity to map the clipboard data to JSON on the third level of a structure formed as Pagelist-->page-->pagelist. To resolve this, support has been added for nested pagelist mapping with deep nesting of objects (configured for one sided actions) and arrays. | Data Integration |
| SR-D38931 | 507058 | Support added for Multiple Set-Cookies in Connect REST | When using a REST connector, the service returned multiple cookies as separate Set-Cookie response headers, but only the last header value received was stored when using pzResponseHeaderMap on the parameter page. In order to support this use, changes have been made to store multiple header values from Connect-REST responses. | Data Integration |
| SR-D42670 | 510185 | Force order added to inner join when running a Rules Resolution filter | After upgrade, D_getResolvedWorkStatuses was not loading properly due to a Report Definition that used a Filter by Rule Resolution option timing out on the SQL Server. When the Filter by Rule Resolution option is selected in RD, it will generate a rule resolution query with an inner join which can cause a time out on the SQL Server while it tries to find out the join order for tables with multiple joins. To resolve this, the SQL server will provide a Force order, merge inner join hint option by way of an added DSS reporting/useForceOrderHint. Additionally, reporting/useMergeHintForRRquery should be set on Pega-Reporting to set things up for using the Merge Inner join hint in the query. | Data Integration |
| SR-D45600 | 510385 | pzIsACoverageSessionActiveForThisRequestor moved to @baseclass | When logging out, the error "com.pega.pegarules.pub.generator. RuleNotFoundException: Failed to find a 'RULE-OBJ-WHEN' with the name 'PZISACOVERAGESESSIONACTIVEFORTHISREQUESTOR' that applies to 'Code-Pega-List' appeared. This was a log errors issue caused by a 'when' rule not being found due to the temporary Pega step page matching with a locally created page, causing the rule resolution of the 'when' rule to fail. To resolve this, the 'when' rule pzIsACoverageSessionActiveForThisRequestor has been moved to @baseclass. | Data Integration |
| SR-D46159 | 510973 | Reinitializing Full Text Search will shut down Elastic Search regardless of search initialization status | Pega search was only sporadically working after converting from standard sandbox-marketing to largesandbox-marketing. This was traced to the Full-Text Search initialization having failed on the app-tier node during re-initialization. As part of re-initialization, the existing node is shut down and the Elastic Search node is started. The shutdown process relied on a boolean flag which indicated if the current status of full-text search initialization was successful. In this case, ES was trying to validate all the cluster level settings, for every save of one of the cluster level settings, but could not due to topology changes in the Util Tier node. The boolean flag indicated initialization had failed so the shutdown process was not invoked, yet the system was attempting to start the second instance of an ES node on the same machine. To resolve this, the shutdown FTS code has been modified to shutdown ES regardless of the search initialization status. | Data Integration |
| SR-D50161 | 514875 | Auto poulate disabled during redux page conversion to prevent concurrent modification exception | Running a standalone data page sourced from a look up of a class was failing sporadically with a concurrent modification exception. The Data page was backed by redux pages: this meant that when the page fetched from data source was converted to redux page, it was iterating through all properties in the mContent of the page and trying to convert those to redux properties. During this process, when any auto populate property was encountered it was getting triggered and modifying the mContent, resulting in a change in iterator. As a result, when the Iterator was trying to fetch the next element, the concurrent modification exception was thrown. To resolve this issue, auto populate has been disabled during redux page conversion to avoid unnecessary problem during data page load. | Data Integration |
Decision Management
8.1.7 Resolved Issues for Decision Management
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| SR-D26976 | 507215 | Filter added to ensure correct context for proposition strategy rules | Given two applications (ex App1 and App2) hosted on the same domain where App2 was built on App1, trying to create a strategy rule in App1 and do a test run strategy using the propositional data component which internally uses App2 propositions generated the error: Failed to find a 'RULE-DECISION-DECISIONPARAMETERS' with the name 'GROUP_2'. There were 1 rules with this name in the rulebase, but none matched this request." Investigation showed the strategy was using the PropositionNoCacheUtils and PropositionTools java classes to load the propositions during run time. In these classes, the group classes were browsed from the db irrespective of the application context, causing the strategy run to fail as it was not able to access the decision data rules in other applications which shared the same SR class as the current application. To resolve this, a filter has been added to the PropositionNoCacheUtils and PropositionTools java classes to filter out the groups that are not in the current application context. | Decision Management |
| SR-D31103 | 502980 | VBD insert process updated for better retry handling | When restarting Data Flow and VBD nodes, the VBD client can encounter some exceptions indicating components in the stack are temporarily unavailable. In most cases the VBD client retries, but there are some cases where it did not and data flow failures occurred. To resolve this, the code has been updated to remove logging of the VBD cluster status during a retry, and the retry duration has been made configurable. | Decision Management |
| SR-D37163 | 505479 | Corrected Decision Data import filter behavior | After upgrade, if a Decision data import referred another component to filter out the import, it did not work. This has been corrected. | Decision Management |
| SR-D38492 | 505491 | Batching now enabled when using IH Summary shape in substrategies | Batching was not being enabled when using IH Summary shape in substrategies. This was traced to the IH_SUMMARY_CACHE field not automatically being passed to sub-strategies, and has been corrected. | Decision Management |
| SR-D39956 | 511639 | Corrected method IF use with shortcut function | After upgrade, method IF was not working as expected when used in an expression like "@if(.totalorders_120days>0,(.remakeorders_120days/.totalorders_120days)<0.3,false)". This was caused by a missed use case for the combination of an exception-generating function in combination with a shortcut function (i.e. ternary, and, or), and has been resolved. | Decision Management |
| SR-D47713 | 511972 | Corrected issue with strategy framework testing | Issues were seen in creating a dataflow to test the strategy framework shipped with the Pega Marketing product. It was not possible to use a data transform to test this strategy because it is in the shipped PegaMKTEngine ruleset. Investigation showed the value of appliedToClass was retrieved from "pyRunOnDataFlowClassName" instead of from the running strategy, and this has been resolved. | Decision Management |
Low-Code Application Development
8.1.7 Resolved Issues for Low-Code Application Development
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| SR-D35734 | 504477 | Escalation updated to ensure assignee is notified of missed deadline | The Passed Deadline SLA Actions to send email to the owner were not triggered as configured in SLA rule form. To correct that, pzMapEasyEscalationParams steps 3.4.10 and 3.4.11 have been modified to support "NotifyAssignee" for the passed deadline. | Low-code app development |
| SR-D37415 | 508969 | Parameter page update added to improve backwards compatibility for ShowTestLibraryTab | An error was observed on the first attempt to modify the 'when' rule "ShowTestLibraryTab" located in PegaProjectMgmt:08-01-01. Analysis showed the when rule (Always, Never) which was called from this rule was not found, which was an issue traced to the Rule-Obj-When function alias parameter name being changed from "strWhen" to "blockName" in the 8.1 release. Subsequent attempts to save the modified rule succeeded due to step#7 in the Embed-UserFunction.pzPopulateDropdownFBUIParameters activity upgrading the pyParameters page with the latest data. To resolve this backwards compatibility issue, the activity step#6 has been modified to upgrade the parameter name for the Rule-Obj-When function alias. | Low-code app development |
| SR-D39547 | 505859 | Check added for backwards compatibility with Case Type when rules | After upgrade, the When rules present on case type rules (used for skipping stages or showing/hiding stage-wide or case-wide actions) were not executing at run time. This was traced to the introduction of the pySkipOrAllowType property in recent versions, and was only reproducible when the ApplicationRuleset was locked and after upgrade irrespective of whether the condition for when was true or false. To resolve this and enhance backwards capability, a check has been added for the SkipOrAllowType property being empty. | Low-code app development |
| SR-D42566 | 512874 | Security improvements for ApplicationInventory and Delete Class | It was possible to call the activity "ApplicationInventory of class Rule-" by appending the activity name in the URL. To improve security, the ApplicationInventory activity and HTML rule have been removed from the system. In addition, it was possible to access the "delete class" screen and perform actions on top of it by directly appending the stream to the URL. This has been refactored so the screen will be presented only if the pzSystemOperationsAdministrator privilege is in the current access group. | Low-code app development |
Mobile
8.1.7 Resolved Issues for Mobile
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| SR-D28965 | 501859 | Repository document deletion modified for better cleanup | When using documents functionality, creating and uploading a document properly stored it, but deleting the document did not remove the associated files from storage. Whenever a document is created that has a file, instances Of Link-Attachment and Data-WorkAttach-File are also created. Previously, when the document was deleted, the associated instances and actual file were not deleted from the repositories but rather marked as Resolved-Withdrawn and hidden at the UI level. The system has now been updated so that when a document is deleted, the document attachment will also be deleted from all places like list, Tile, and document View, and reference instances like Link-Attachment and Data-WorkAttach-File instance will also be removed along with the actual file from the repository. | Mobile |
Project Delivery
8.1.7 Resolved Issues for Project Delivery
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| SR-C98068 | 483990 | Installer files updated with class loader conflict resolution assistance | When sending emails with attachments, errors were observed relating to a loader constraint violation indicating that when resolving interface method, the class loader of the current class and the class loader for the method's defining class had different Class objects for the type used in the signature. The resolution for this requires user configuration of the app server, and the following files for the install guide have been updated with the appropriate information: Deployment-guides-dita/install.ditamap Deployment-guides-dita/Content/Topics/app-server-config/creating-jdbc-driver-module-jboss-tsk.dita Deployment-guides-dita/Content/Topics/app-server-config/delegating-javax-activation-to-JRE-loader-tsk.dita |
Project Delivery |
Reporting
8.1.7 Resolved Issues for Reporting
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| SR-D18879 | 500642 | Logic update made to PrepareColors to resolve calculation ambiguity | When a Report Definition was summarized, the executed report showed a graph for multiple categories but generated the error "No data to display" if given a single category. This was traced to an ambiguity in the Java syntax of the Rule-Utility-Function pzPrepareColors that led to a NegativeArraySizeException on a customer's environment. To resolve this, parentheses have been placed around a ternary operator to ensure the correct order of operations. | Reporting |
| SR-D19299 | 511325 | Support added for calling Export to Excel directly from RD | When using Export to Excel directly from a report definition, a date column specified using pxDatetime was shown as applied date format in the resulting Excel file. The column was formatted as expected if the export was called from an activity. This was traced to the recent refactoring of Export to Excel: it was not expected that it would be called directly, but rather that it would be invoked from a report viewer ruleform. In order to support this direct use, step calls have been added to the pzRDExportWrapper activity to call pzMergeAutoGen before the engine call. This step will merge the pyModes pages from pxDateTime control. | Reporting |
| SR-D27528 | 501372 | Return from drilldown in frameless portal corrected | Drill up after drilling down on a dashboard chart in a frameless portal (such as Case Worker or Case Default) was throwing an exception. This was caused by the top-level page generated during drilldown not having pyRetainPage set to true, causing it to be removed from the clipboard by doUIAction. This has been resolved by updating runReport to set pyRetainPage if it needs to create the top-level page. | Reporting |
| SR-D32222 | 500901 | Auto-generated controls with images supported in export to Excel | When attempting to display a column as an image, changing the column format to "pxCheckbox" showed an image while running the report if the value was true, but blank values were displayed when the report was exported to Excel. Investigation showed that the value was being returned as null when a boolean value was set on a column and the option for the auto control was set to show as an image due to the formatted value being returned as an HTML element instead of a boolean value. To correct this, AutoGenReportUIField has been modified so that auto-generated controls that are shown as images are converted to text upon export to Excel. | Reporting |
| SR-D37943 | 505737 | Corrected Export to Excel after adding custom DateTime field | An issue with exporting report definition results to Excel after adding a custom date field column through the edit report option of the report in report viewer was traced to the processing of the controls backing a cell in a report when exporting to Excel. For controls like "Date Only" DateTime (non-autogenerated) control, the code was not returning a string the way it should. To resolve this, NonAutoReportUIField has been updated to always treat all Non-auto Controls as strings. | Reporting |
| SR-D42159 | 508942 | Large report pagination should use "Previous and Next only" | Some Report Definitions were getting timed out or facing gateway exceptions, primarily due to high time consumed by the DB Queries. Investigation showed the total result count process appeared to stop at the configured pyMaxRecords value as long as it was nonzero. This indicated the issue was related to changes made to fix the inaccurate behavior of the "Last" button in the responsive paginator which included removing logic that set pyMaxRecords to anything other than zero. To resolve this issue, those pagination changes have been reverted. The "Last" button should not be used when the paging mode is set to Numeric: in the case of large reports, the paging option should be set to "Previous and Next only". | Reporting |
| SR-D43179 SR-D39236 SR-D43179 |
509888 508452 509888 |
Corrected viewing of sorted drill-down spreadsheet-style summary reports | When using a report with a summarized column and the 'Do not display group headings' grouping option checked, drill down was not working when the report was primarily sorted by default on any column other than the first one. This manifested as either no results returned by the drill down report or an error message related to invalid filter values. This was traced to the unique column ordering logic for non-spreadsheet-style summary reports being applied to the drilldown of spreadsheet-style summary reports due to the logic for creating the drilldown filters using the != operator to compare the spreadsheet flag string to the string constant "true". This previously worked as expected because this string was interned in the engine, but these string internments have since been removed. To correct this, pzPopulateReport has been updated to appropriately recognize spreadhseet-style summary reports as they used to. | Reporting |
| SR-D48173 | 515341 | Resolved hang caused by cancelling report calculation | When dragging a calculation into the report editor filter area, clicking X on the cancel modal that appeared caused a JavaScript exception to occur. This exception later prevented the ability to click the "done editing" button on the report. This has been resolved by modifying the pzpega_report_rafpopup.sj -- doRefresh API to pass the correct argument to reload the section API. | Reporting |
Security
There were no 8.1.7 Resolved Issues for Security
System Administration
8.1.7 Resolved Issues for System Administration
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| SR-D20423 | 503447 | Improved upgrade handling for tables using classes with property references | After upgrade, some page property values were blank and exposed database columns did not contain the values. Investigation showed that the reference properties did not have context and hence column population was not able to determine their value. To resolve this, instead of doing column population for all the columns, the system will identify classes that have property references and that are being optimized as part of upgrade process and maintain a list of specific columns to update. | System Administration |
| SR-D20439 | 496405 | Hotfix hashmap cleanup improved | A DL installation failed with an out-of-memory error. It was observed that many CacheEntry(VersionedJdbcJarRwader.java) hashmaps were being created to store the details for each hotfix but that were then never cleared. This has been resolved by adding the finally block in CodeImportProcessImpl.java class to call the shutdown method for proper cleanup. In addition, the default command line utility (prpcUtils) has been updated to use JVM settings of Xmx 4GB and capture a heap dump if an out-of-memory error is encountered. The auto-generated prconfig.xml has also been updated to leverage its minimal startup setting which will avoid loading the conclusion cache into memory. | System Administration |
| SR-D28538 | 502059 | Corrected requestor status flag for direct map | Numerous "Unable to create requestor" alerts were logged. This was traced to an error in HttpAPI where after retrieving the requestor from the internal requestor map directly, the requestor creation status flag was not set properly. This caused last action to post that alert instead of the correct notice of "existing requestor retrieved". This has been resolved so the flag reflects the correct status. | System Administration |
| SR-D29485 | 503514 | Enhancement added to modify URL encryption for load testing | An enhancement has been added which allows conditionally modifying URL encryption for load testing. This uses the flag crypto/useportablecipherforurlencryption: if true, a portable hardcoded key is used to encrypt the URLs and if false, a dynamically generated key per thread/requestor is used to encrypt the URL. | System Administration |
| SR-D51554 | 514064 | Local UUID cache will be updated when merge event is detected | Cluster-related issues were seen in multiple production clusters. For some nodes in the cluster the Cluster Management screen showed all expected nodes with valid Node IDs displayed, and on other nodes the Cluster Management screen showed the node ID of itself, SERVER@localhost:5701. On an impacted node displaying the wrong ID, the Node Information landing page did not work and displayed the error "Unable to execute job on ." Multiple advanced agents running on nodes in the affected clusters, both with correct and incorrect IDs, also failed with a similar error "Unable to execute job on <node's job id>". This was traced to a merge performed after a split brain. To resolve this, the code has been updated to handle merge events: when the node UUID is changed as part of a split brain recovery, the local UUID cache will be updated when the merge event is detected. | System Administration |
| SR-D52969 | 514705 | Column population honors thread count of 1 | The thread count parameter in the column population activity was not being honored, causing repeated deadlocks when trying to populate columns. Investigation showed that the ExposeCols process did not honor the thread count when it was 1 (the default is 4), and this has been fixed by adding the necessary code so that if the thread count is 1, it will not run in multhreaded mode. | System Administration |
User Experience
8.1.7 Resolved Issues for User Experience
| Ticket # | Issue # | Title | Description | Product Area |
|---|---|---|---|---|
| SR-D16543 | 487946 | Thread cleanup improved for application switching to resolve skin issue | After opening a Case from the HR application and then switching to another application to open another case, the Review Harness skin control was not loading correctly. This was traced to a thread cleanup issue relating to the Portal: on application switch, the system should clean up all threads created on the current application before switching to new application, but in this case thread cleanup was not happening as expected due to conflicts in the unload event handling. This has been corrected. | User Experience |
| SR-D23174 | 499569 | Check logic added for change in datetime | After selecting a valid date in the calendar UI, clicking outside of the DateTime control caused the date to disappear when using the Microsoft Internet Explorer browser. Investigation showed that the order of events execution is different in Microsoft Internet Explorer and Google Chrome, so that by the time the getReadOnlyFormatting method was called, the data-changed attribute had already been updated to 'false'. This caused the read-only formatting to not be applied so the data-display-value was considered to be empty. To resolve this, a check has been added to better detect the change so that read-only formatting gets applied. | User Experience |
| SR-D28476 | 500889 | Corrected exceptions report appearing on user screen | When "Break on all exceptions" was enabled, the exceptions report was visible on the end user screen when using Microsoft Internet Explorer 11. This has been resolved with updates to the 'pzpega_ui_dynamiccontainer' and 'pzpega_ui_doc_tabsupport.js' files. | User Experience |
| SR-D31599 | 503201 | Table layout filter by format works for empty value | If a DateTime property with empty values in a table layout grid was filtered by format, no result was returned even though the grid had the Records for empty DateTime property. This was traced to null value filtering being done with empty values instead of a formatted null value, a difference that could produce different results depending on the control. To resolve this, the activity has been updated to support null values filtering. | User Experience |
| SR-D32525 | 505469 | Dirty check added to offer save/discard changes when closing tab | With the out-of-the-box section enabled, performing a change in the form (changing a text value, selecting a option in a dropdown, etc.) and closing the case generated an unexpected alert indicating that the case was changed and the modifications were lost. This differs from the previous behavior of showing the section pyDirtyCheckConfirm which offered the opportunity to save the work. This was a missed use case and has been resolved by updating the system to perform a check for the dirty state when closing the interaction and show a modal dialog asking the user to choose either save/discard if dirty. | User Experience |
| SR-D34214 | 511814 | API available to skip defer loading in Single Page Applications | The wait message "Loading ..." was displayed on check on defer load in Single Page Applications. The browser refresh worked as expected if 'defer load' was unchecked. This was traced to SPA not containing the handling necessary to publish the forced replace to other modules: in SPA cases, the dashboard is forcibly replaced with workobject harness, causing defer loads in dashboard to be processed in the wrong thread. To resolve this, there is now an exposed API pega.ui.DCUtil.skipDeferredLoadFrom() to skip defer loading when true in SPA. | User Experience |
| SR-D36335 | 504335 | Post Value action properly displayed in upper case after validation | After upgrade, if a property with Edit Input toUppercase was created and placed it on a section where the text input has Post Value on Change, validating the uppercased property on the clipboard resulted in the non-uppercase value displaying on the screen. This was traced to the target element with the response value not being updated with the server response for the post value action. Only the attribute value was updated, which is not shown to the user. In order to properly display the value, logic has been added to update the target element value with the response value. | User Experience |
| SR-D36970 | 504987 | Calendar icon updated to properly display the set number of years | By default, the Calendar icon showed a date range of 10 years when -/+100 was expected. This issue was traced to the existing DSS setting (pyNumberofYears under Pega-UIEngine), which enables overriding the date year range, not being honored when the pyNoOfYears property was set to -1. To honor the pyNumberofYears setting, pyNoOfYears should be 21. This has been corrected so the value will be set properly. To see custom calendar range, attached snippet should be added to UserWorkForm. To see custom calendar range, the below snippet should be added to UserWorkForm: <script> pega.u.d.overrideCalendarDefaultRange = { past: 20, future: 20 } </script> |
User Experience |
| SR-D37348 | 514841 | Added handling for placeholder in Multi-Select List Control | After adding a placeholder in Multi-Select dropdown properties to hold the default value as 'please specify' by way of a refresh section on the action tab of multi-select property, the multi-select drop was showing the 'please specify' placeholder after refreshing the section even though there was value in it. This has been resolved by adding handling to make the placeholder empty when there are values. | User Experience |
| SR-D38581 | 504777 | Removed unnecessary cross-site scripting filtering on paragraph rule | When a link was set in a paragraph rule, the target option was removed in the returned layout structure. This was traced to unnecessary cross-site scripting filtering which has now been removed. | User Experience |
| SR-D40523 | 505928 | Corrected Pega-Perf cookie adding double quotes | After upgrade, issues were seen with mashup not loading properly. In addition, a region in the environment was not able to access the developer portal. This was traced to an issue with pzPega_ui_statetracking.js, which handles adding the Pega-Perf cookie, adding a cookie with double quotes to HTTP requests. The double quotes have been removed to resolve this issue. | User Experience |
| SR-D40607 | 509392 | Empty pyIsDirty attribute will not be set to false on browser refresh | After customizing Recents to show entries based on whether the "pyIsDirty" property was false or true, it was seen that the pyIsDirty attribute was being set to false on refresh of the browser window even when the WorkObject was not open. The normal behavior of the Declare_pxRecents data page is that the pyIsDirty value is set to false when a Work Object is opened and set to true when it's modified. For other Work Objects the value will be empty. To support the customized use, the code has been modified to skip setting the property to false if the value is "". | User Experience |
| SR-D40938 | 509687 | Free form layout controls will be converted to dynamic layout | After upgrade, a a pzActionDropdown control that was inside a pyActionDropdownSection was not visible anymore. Using the pzActionDropdown control directly worked as expected. Investigation showed that pyActionDropdownSection was using Freeform layout instead of the upgraded Dynamic Layout, and that the custom control was failing to generate the markup whenever drag/copy-paste was used for the control in any layout. To resolve this, the system has been updated so it will remove the control from a free form layout and use dynamic layout instead. | User Experience |
| SR-D41984 | 510014 | Added handling to correct '&' displayed as '&' in custom tab name | When using a data transform and custom properties to set the tab title, clicking on a link containing "&" in the label opened a tab name which included "&" instead of "&". This has been resolved by modifying the handleGadgetLoad method in the pzpega_ui_dynamiccontainer file to handle the Cross Scripting FIlter and display the character. | User Experience |
| SR-D42583 | 514488 | Label of a field is correctly rendered when a section is re-used with a visiblity condition | The label of a field was not being rendered/visible when a section with a 'visible when' condition was re-used in different Page Contexts. The label was displayed correctly if 'Run visibility condition on client' was checked. As part of performance improvements made in a previous version, label generation was moved under the dlcellvisibility flag. Because of this, if a section was re-used at multiple places with different contexts and one place had visibility false and another had visibility true, the labels were not getting generated for the visible section. To resolve this, Label Generation has been moved out of dlcellVisibility to ensure label metadata will always be generated. Updated performance improvements have been made instead by way of a DSS setting (generateCellMetadata) so that when generateCellMetadata is true, the label generation will honor dlcellvisibility to generate the label metadata. | User Experience |
| SR-D42701 | 510924 | Cross-site scripting security added for Case Manager | Cross-site scripting security has been added to the Document features in the Case Manager portal. | User Experience |
| SR-D45101 SR-D43740 |
512530 514126 |
Added support for Helper Text Question Mark with visibility condition | The Helper Text Question Mark was not displaying if the control was configured with "Help icon with overlay on hover" combined with a visibility condition. This was a missed use case, and the expression visibility support for controls.changes have now been added in the pzpega_ui_DLCellTemplate.js file. | User Experience |
| SR-D45360 | 510101 | Support added for non-decimal currency notation | Previously in the pxCurrency control, the options allowed either specifying Decimal places (2 by default) or using the locale to decide decimal places when "Use currency standard" was selected (creating the default for 2 for en_US, 0 for jp_JP and 3 for ar_JO.) However, this did not account for currencies like JPY, TWD, and HUF, which do not use decimal precision. In order to support these currencies, handling has been added to formatNumaber js and pxFormatNumber for locales which do not have decimal precision in their currency. | User Experience |
| SR-D48881 SR-D26133 SR-D28898 |
514602 500723 501653 |
Corrected alignment of column header and content when fixed header is used | The tables header column was misaligned with the context columns when a fixed header was used. This has been resolved by correcting the code calculating the width of the header cells. | User Experience |
| SR-D48887 | 512947 | Read-only text inputs remain read-only after browser refresh | Read-only text inputs were changing to editable after a browser refresh. This was traced to work done to better handle a displayOnPage GET request that was sent with all of the parameters in the parameter page (data-model) that was causing a 400 Bad Request due to the browser URL length limitations. That issue was resolved by removing the parameters which are not actually required for the displayOnPage GET call during the refresh case; to resolve this issue, the readonly parameter for displayOnpage action has been restored and will be passed. | User Experience |