INC-211251 · Issue 706541
Handling added for Model level Data type empty values
Resolved in Pega Version 8.7.2
After update, the Email Intelligent Virtual Assistant™ (IVA) was not able find the proper response for the real-time incoming emails but was able to find the topic and response when running it from Dev Studio and Prediction Studio. This was due to an edge case where the model datatype page list property was present on the text analyzer rule and a page was present in it, but the property pyName which actually holds the data type (body, attachment, all) was not present in the page. This has been resolved by updating the system to add 'all' as the datatype if the pyName is blank (null or empty).
INC-216927 · Issue 714495
Conditional handling added for perceived invalid valuelist reference in design time
Resolved in Pega Version 8.7.2
After adding a value list property '.pyDateTimeValue(2)' in a section configured in the view editor, the design time error "config issue" was shown. There were no errors at run time and the application's behavior was correct. Changing the subscript of the value list property to (1) ran without an error. In this scenario, the actual usecase configuration will populate .pyDateTimeValue(2), but the view editor believed there was an error in the section because there was no reference to pyDateTimeValue(1) first. This has been resolved by conditionally changing the pyValue to a template property in design time when a perceived invalid valuelist reference is provided as property in the panel.
SR-A92086 · Issue 264769
Mashup Gadget considers DSS for access group redirectGuests
Resolved in Pega Version 7.2.2
In Mashup, the Gadget was unable to redirect to the corresponding access group based on the application name, instead always redirecting to the default access group. In order to address this immediate problem, a change has been made to add the redirectGuests attribute to the mashup html generation based on DSS setting. This will not get the access group hash only in cases when: - operating in the non-tenant environment and - the mashup configuration div claims to have set the DSS for redirectGuests as being set to false. The code itself does not verify whether the run time value of the DSS is properly set or not.
SR-A92086 · Issue 260095
Mashup Gadget considers DSS for access group redirectGuests
Resolved in Pega Version 7.2.2
In Mashup, the Gadget was unable to redirect to the corresponding access group based on the application name, instead always redirecting to the default access group. In order to address this immediate problem, a change has been made to add the redirectGuests attribute to the mashup html generation based on DSS setting. This will not get the access group hash only in cases when: - operating in the non-tenant environment and - the mashup configuration div claims to have set the DSS for redirectGuests as being set to false. The code itself does not verify whether the run time value of the DSS is properly set or not.
INC-212704 · Issue 707116
Explicit lock release added for Cassandra threads
Resolved in Pega Version 8.7.2
Customer Decision Hub was not responding for realtime request REST service calls, and thread dumps during start up were showing all HTTP request threads were stuck in CassandraSessionCache.getSession. If an error is thrown while invalidating an old Cassandra session, the system may fail to unlock the write lock. This results in subsequent threads being blocked on the session cache's ReadWriteLock when they attempt to retrieve the session from the session cache. To resolve this, an update has been made to ensure that invalidate session is wrapped in a finally block that releases the write lock and log any thrown errors.
INC-210346 · Issue 709711
Check added to ensure Job scheduler executed only once
Resolved in Pega Version 8.7.2
When Node A and Node B woke up at the same time to start executing the job scheduler, both were attempting to update the "now processing" node ID with their ID but only Node A succeeded. This caused Node B to generate a "lock already held" exception, then Node B would try to release the lock and update "now processing" node ID. If Node A released the lock before Node B tried to, then Node B updated the "now processing" nodeID and executed the scheduler, causing it to be run twice. This double-run has been resolved by adding a check for whether the job scheduler has been executed recently before starting it.
SR-A76262 · Issue 256275
Logic updated for parse SOAP to better handle similar element names
Resolved in Pega Version 7.2.2
When the path to an XML node included at least one repeating element and some other element in the path had a name which ended with the name of the repeating node, the data placed in properties by Rule-Parse-XML was potentially inaccurate. The end result is that the data that is recorded in Pega as coming from the N-th occurrence in a repeating element set might contain some data that actually comes from the 0-th occurrence or some other occurrence that is not N. To make the results accurate and consistent, the system has been updated to remove all simple text searches so the replacement of generic node names with indexed node names happens to the correct nodes, regardless of similarities between names in the path.
SR-A99969 · Issue 266109
Ruleset listing works without enabling UDFs
Resolved in Pega Version 7.2.2
All core Designer Studio features and Pega frameworks / applications are supposed to work without dependency on pr_read* UDFs, but an issue was found with attempting to list rulesets without enabling UDFs. This was due to the Designer Studio features used to list instances of a rule class performing behind the scenes filtering to exclude rules with pyMethodStatus = Internal pr Deprecated. Listing members of rule-ruleset-name then failed as this class does not have an exposed property pyMethodStatus. To fix this issue, a check has been added to decide if the rule type is rule resolved or not. If the rule is resolved, then there will be a check for pyMethodStatus exposed or not. If pyMethodStatus is not exposed, then it will fallback to old list view. In addition, a check was added to not to add filter conditions on pyMethodStatus for non-rule resolved rule types. The only exception to this is Rule-Utility-Library, i.e. even though library ruleform is non rule resolved, pyMethodStatus filter will be added.
INC-194180 · Issue 704637
GetChildcases handling updated for large numbers of cases
Resolved in Pega Version 8.7.2
When a very high number of child cases being processed contained a wait shape that was dependent on the movement of a parent case, some of the cases were moved to the next step of the flow automatically while others required a manual command to ResumeFlow. In extreme cases where many child cases were waiting, a node crash could occur. This was traced to the pzGetChildcases report having a maximum value of 500 lines, and has been resolved by increasing the maximum number of rows to retrieve to 9999 in the Data Access Tab of the pzGetChildCases report definition. In addition, the pxCheckFlowDependencies activity has been modified to perform with a higher number of cases, and DSS(MaxRecords) logic has been added to split the child cases into multiple queue items for each access group to decrease load on each thread process.
SR-A76054 · Issue 251761
Enhancement added to bulk delete ADM models
Resolved in Pega Version 7.2.2
In order to support the deletion of ADM models in bulk, an enhancement has been added to remove the unwanted models from the database provided a list of them is given as input. The new activity is pxDeleteModelsByCriteria, applying to DSMPublicAPI-ADM. The pzInsKey of this activity is: RULE-OBJ-ACTIVITY DSMPUBLICAPI-ADM PXDELETEMODELSBYCRITERIA #20160608T102848.043 GMT It has been created in ruleset Pega-DecisionArchitect:07-10-16 on 7.1.7 HFIX system vengwindb180:8282/. The usage text, explaining the activity, is as follows: "Used to delete ADM models in bulk. Models to be deleted are determined by the criteria selected by this Activity's parameters; a model is deleted if it matches all selected criteria. PLEASE NOTE: activity is not constrained by Application, only by the criteria provided as parameters. Therefore in most cases you will probably want to constrain by 'applies to' class in addition to the other criteria. Please see the tooltip / description of each parameter for more info on their usage. Integer output parameter 'NumberDeleted' returns the number of models that were successfully deleted."