INC-217290 · Issue 721374
Added support for creating predictive models in Production
Resolved in Pega Version 8.8
While creating a new predictive model rule in Prediction studio, the case was going into broken process after selecting the template with the error message "Error loading D_ProjectList , Reason : No databases defined in properties file:/databases.properties". This was an unexpected use case for creating models in Production level, and has been resolved by updating the flows to turn off the draft mode in this scenario.
INC-217475 · Issue 719041
Corrected duplication of records in Elasticsearch
Resolved in Pega Version 8.8
After creating a dedicated index for a data class, modifying any data record for external Data/Work classes caused duplicate documents to be created in Elasticsearch. This has been resolved by updating the Reindex _id field to use the pzInsKey value instead of an auto-generated string. Once this update is in place, re-index is required to remove already created duplicates from the index directory.
INC-176785 · Issue 656077
Validation on DateTime property working for mobile
Resolved in Pega Version 8.7
A mandatory DateTime field with "Allow text entry" set to 'No' was not restricting validation when no value was provided. This was an unintended consequence of recent work done to validate input type date along with input type hidden, and has been reverted.
INC-165256 · Issue 657037
Improvements for Offer Eligibility rules loading time
Resolved in Pega Version 8.7
After opening the Proposition filter/Action rule and clicking on Add Criteria, the pxAnyPicker drop down load was taking an excessive amount of time. Performance improvements have been made by adding a precondition at step 2 to avoid data page refresh for specific scenarios when it is not required.
INC-224726 · Issue 730543
Resolved drag and drop duplicate entries
Resolved in Pega Version 8.8
Including files with Drag and Drop control was resulting in duplicate file entries. This was traced to run visibility on client being enabled by default on layout in the section pzAttachContentScreen, and has been resolved by modifying the default to be that run visibility on client is disabled on layout in this section when pyDescription is null.
INC-229423 · Issue 729987
forcemigratetriagecases added to allow check migration status query skip
Resolved in Pega Version 8.8
The IsMigrationDone query was taking around 20 seconds to run on a very large amount of data in pc_work table. To address this, a new 'when' rule pyforcemigratetriagecases has been added to allow skipping checking migration status for on-demand migration.
INC-224923 · Issue 735843
Autocomplete field loads in offline iOS
Resolved in Pega Version 8.8
After converting large data sets to the Large Data Page Structure, some data pages were working in the Android app but not in iOS when Offline Support was enabled. This was traced to the autocomplete field of type 'text' not loading correctly, and has been resolved.
INC-226156 · Issue 735745
Autocomplete field loads in offline iOS
Resolved in Pega Version 8.8
After converting large data sets to the Large Data Page Structure, some data pages were working in the Android app but not in iOS when Offline Support was enabled. This was traced to the autocomplete field of type 'text' not loading correctly, and has been resolved.
INC-232127 · Issue 741807
View history export updated for BAC
Resolved in Pega Version 8.8
A 403 error was generated when trying to click Export to Excel in view history. Investigation traced this to the Export to Excel activity not being registered with basic access control, and this has been resolved by modifying the URL formation to pass the necessary parameters to register the activity in the menu harness.
SR-D21493 · Issue 490306
Corrected revision management with decision data rules
Resolved in Pega Version 8.1.6
When a new version of a decision data rule was created in dev studio and new propositions were imported or existing ones modified, the typical behavior was for the system to also automatically create a new version of the "pyEditElement" section even if the form was not changed. If this is done from revision management, the revision automatically creates a branch in the overlay application. If the revision contains a decision data rule, the branch contains an instance of the decision data rule and also an instance of the pyeditelement section, but when the revision was submitted, the generated package only contained the decision data rule and skipped the pyeditelement rule. This was traced to the pyEditElement section of the decision data rule not getting packaged because the package flag was not set to the section, and has been resolved by fixing the withdraw and reject scenarios by modifying the package flag in pyRemoveDDRules activity.