SR-A7687 · Issue 218670
Red highlighting reinstated for required fields in repeat grids
Resolved in Pega Version 7.2
Required Field Names in a repeat grid were not turning red as expected when validation failed. This was a change from previous behavior and the highlighting has been reinstated for clarity of use.
INC-134634 · Issue 584948
FSM Mobile app correctly starts phone call after closing Google
Resolved in Pega Version 8.3.5
When two controls were configured in the FSM Mobile app, one for Get Directions and one to handle a phone call, clicking on the phone call control worked correctly when it was used first, but clicking on the Get Directions control and opening and closing Google Maps before clicking on the Phone call control caused the phone call control to not work. Investigation showed that after the Get Directions control was used, the # in the href attribute was automatically prepended with window.location. To resolve this, a check has been added that will compare the attribute with the completely formed {URL}# so that entire window.location will not be prepended.
SR-A6680 · Issue 215648
Delegated rules form displays in old manager portal
Resolved in Pega Version 7.2
The rule form was not displaying when a manager tried to open the delegated rule from the My Delegated Rules section if the rules were not currently supported under the new delegation model and an old manager portal was being used for access. To resolve this, a new 'when' condition has been added to skip the activity "pzGetDelegationDetails" call in this scenario.
INC-132771 · Issue 584963
Refresh section of MultiSelect properly handles refresh section
Resolved in Pega Version 8.3.5
On hitting tab or enter on a Multiselect control with "Post value" and "Refresh Section" enabled, focus moved to the header of the page when it refreshed. This has been resolved by updating the 'disable when' expression for "run on client" to better handle the input element used for enabling the controls.
SR-A11935 · Issue 223901
Application creation allowed without case selection
Resolved in Pega Version 7.2
When attempting to create an application based on CS 7.1.4 using the New Application Wizard with no cases selected, the application was not created and an error was displayed. This was traced to the RulesetName and rulesetversion params not being passed to the "pyPrepareFrameworkAssetsForGenerationPost" activity: those params are set only when Case Types from FW are selected. The system has now been updated to pass the RulesetName and rulesetversion params to the activity even when Case Types from FW are not selected.
SR-A7804 · Issue 218676
Rest inbound call mapping updated to determine response type
Resolved in Pega Version 7.2
When Rest service was built in the Pega application and exposed to external applications (non-Pega), the JSON request payload was not mapped to the clipboard during the input data mapping if the setting "Content-Type: application/json; charset=utf-8" was used, but did work as expected when the client calling the service used "Content-Type: application/json" and did not set charset. This error was linked to a space character missing between the given Content-Type value and charset parameter, and has been updated to avoid this issue in the future by setting the extract content-type value and excluding the charset parameter value, then determining whether the response is of text type.
INC-128880 · Issue 592817
Handling added for angle brackets in legacy Chart control
Resolved in Pega Version 8.3.5
When using Investigative Case Management, some report charts were not rendering correctly. This has been resolved by updating appendFormattedString in AbstractJsonDataGenerator.java to escape angled brackets (< and >) before appending the input.
SR-A5659 · Issue 214180
HTTP Connector Simulation properly runs for both Global and User sessions
Resolved in Pega Version 7.2
When attempting to use a simulation activity for a HTTP Connector, it worked when set to Global Session but did not appear to run when set to User Session. At run time, the list of simulation activities was picked from the pyISSimulation clipboard page. Because that page was available in the "STANDARD" thread only, the code responsible for loading the simulation activities was not able to find the correct page. This has been fixed to allow the table to properly execute the Connector simulation for both Global and User Session.
SR-A8254 · Issue 217223
Path extraction support added for REST connectors to NBAM
Resolved in Pega Version 7.2
If a system used pathinfo (containing "!") rather than requestURL, a null pointer exception was raised when attempting to access a REST service endpoint in Next-Best-Action Marketing (also called PegaMarketing) at the point when the system attempted to tokenize the "resources path". To allow for smooth operation after upgrade, code has been added to extract the necessary path information.
SR-A9233 · Issue 219215
DateTime control updated for variable month length
Resolved in Pega Version 7.2
When the datetime property was configured to use the timeframe format (i.e. 2 Days 5 Hours ago format), the value was not getting accurately calculated when the date value was more than 31 days from the current date. This was due to flawed logic in considering the length of the month (defaulting to 31 days) and has been updated to calculate the days correctly based on calendar information.