INC-164439 · Issue 657994
Setting added to customize using blank Map values
Resolved in Pega Version 8.5.5
After upgrade to from Pega 6 to Pega 8 some of the Map Value rules were not working. This was due to the handling for blank default values which was changed in Pega 7. In order to support backwards compatibility, a new 'when' rule has been added which allows customizing whether or not blank values are allowed for the Map value default columns. pyAllowBlankValues will default to "false".
INC-168254 · Issue 659299
Documentation updated for accents and special characters used in search
Resolved in Pega Version 8.5.5
The "Pega search API" article has been updated to reflect that the search functionality in Pega Platform does not match accented words with unaccented. For example, searching for santé and sante will retrieve different results. In addition, Domain Specific Language (DSL) includes special characters for use when searching, for example '-', '_', '!', '@'. However, the system retrieves various results depending on the way the special characters are used in the search query. If the query contains special characters that are not escaped, the system may retrieve incorrect results. For example, not escaping the slash mark in the 25/02 query may cause the system to ignore the special character.
SR-B51825 · Issue 310042
Added handling for WO lock when OAuth2 token expires
Resolved in Pega Version 7.3.1
The expiration of the OAuth2 token committed the WOs in context and caused all WOs to lose their locks and eventually end up in the SLA broken queue. To fix this, code has been added to perform the commit on a new database thread so the commit operation will be independent from the actual thread context.
SR-B57192 · Issue 315081
Performance enhancement added to optimize evaluation of 'when' calls in GetFlowData
Resolved in Pega Version 7.3.1
A lot of when conditions triggered as part of GetFlowData out-of-the-box activity were causing slowness when the Java Step (4) did its evaluation. Current screen flow navigation would evaluate all the when rules till the end of the flow to determine the flow navigation. To improve performance, an enhancement has been added to the GetFlowData activity to prepare pyFlowData page from the pyWorkPage. This will build the pyFlowData up to the current step and ignore the future steps. It will be necessary to override the PerformDefaults to pass the new parameter loadNavigationPathForBreadCrumbOnly to GetFlowData to call this new functionality.
SR-B66551 · Issue 317443
Fixed downstream question flow when upstream answer changed
Resolved in Pega Version 7.3.1
Downstream question responses were not getting reset on the form when a complex question (upstream question) response was changed. To fix this and to keep the behavior consistent, the property will be removed from both the survey embedded structure and the property mapping. BuildQuestionStream has been modified to clear the embedded answer value if the display when evaluates to false.
SR-B51204 · Issue 309685
Cassandra enhancement to retrieve multiple records and use runinparallel
Resolved in Pega Version 7.3.1
An enhancement has been added to allow the Cassandra Connector GET operation to return multiple rows by querying on clustering keys and/or secondary index. In addition, an issue with Connect-Cassandra not supporting run-in-parallel execution mode has been resolved to allow a result list from list operation to be called from pyoutputpage or primary page.
SR-B64066 · Issue 313310
Cassandra enhancement to retrieve multiple records and use runinparallel
Resolved in Pega Version 7.3.1
An enhancement has been added to allow the Cassandra Connector GET operation to return multiple rows by querying on clustering keys and/or secondary index. In addition, an issue with Connect-Cassandra not supporting run-in-parallel execution mode has been resolved to allow a result list from list operation to be called from pyoutputpage or primary page.
SR-B66961 · Issue 315458
Performance improvements for multiple operators using the same application
Resolved in Pega Version 7.3.1
Performance delays were seen due to static content being processed per each user. This was an issue where each census survey performed by a different operator ID using one of two applications produced two gen_.js files. One was generated at login, the other on submit. Because the variables in pzClientApplicationData were not static for an application, the dynamic static content was being regenerated and created for different users but for the same application. To correct this, the confirm_harness_loaded and pega.d.pyUID properties have been made dynamic so the file will not be regenerated for same application/different user.
SR-B53918 · Issue 312285
Optimistic locking on resolved case fixed for Back button use
Resolved in Pega Version 7.3.1
It was possible to perform an action on a resolved case when in screen flow, i.e. when in the middle of a screenflow of a case and the case gets resolved due to some action in another case. If Refresh was clicked from the Actions, the case was updated as Resolved-, but clicking on the Back button of the screen flow ignored the Resolved status and allowed changes to be made. The logic to check for stale data (optimistic locking) was missing on the Back button in the screen flow, and has been fixed.
SR-B56216 · Issue 313130
fr_FR pyCurrency control corrected for using USD property qualifier
Resolved in Pega Version 7.3.1
Due to an incorrect currency evaluation, a pyCurrency property qualifier with a value set as USD in the corresponding property appeared in read only mode for operators using the fr_FR locale. With default locale, "1234567.89" was displayed as "1234567.89 USD" but with fr_FR it was shown as as "1 USD". This has been fixed.