Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

INC-170551 · Issue 656559

Rule Assembly update for pxTextInput and pxDisplayText

Resolved in Pega Version 8.7

After the application restart, multiple rule assembly alerts were seen for pxTextInput and pxDisplayText . During first access, Assembly is done and container is cached in VTable; investigation showed that in this case, the Load class without the package name had a class not found issue, and then subsequent access tried to use the container from cache and assembly was not done. To prevent this, an update has been made to perform the class lookup using the package name and class name.

INC-182986 · Issue 668829

Property Rule Form refreshes after discarding changes

Resolved in Pega Version 8.7

After updating from Pega 8.2 to Pega 8.6 and migrating the properties, modifying any property rule and then discarding the change did not refresh the Property Rule Form. Investigation showed that the LOG-SYSTEM-PROPERTYOPTIMIZATION instance created during property optimization was not getting deleted when a property was deleted. As this was not getting deleted, the property was shown as optimized when adding the property back, causing confusion. This has been resolved by cleaning up the LOG-SYSTEM-PROPERTYOPTIMIZATION instance when the property is deleted and there is an optimization entry.

SR-A22794 · Issue 245278

parseXML able to map multiple values

Resolved in Pega Version 7.2.1

In order to present more information for custom use, parseXML as been updated with a new pagelist property that can map multiple attribute values.

INC-186437 · Issue 685015

Updated entity attachment extraction tokenizers

Resolved in Pega Version 8.7

After creating an entity extraction model, it was seen that one of the entities worked when there was a space after the semicolon but the detection was not working if there was no space. This has been resolved by updating the Tokenizers with extra examples to address tokenization when ":" is present between two words without any spaces.

SR-A19986 · Issue 242898

getAppHashForApplication API updated

Resolved in Pega Version 7.2.1

When logged in from an end user portal, editing a decision table and clicking on the gear icon to add a function would show the Function's headers (Example, Activity, string, etc.), but the functions list would not be loaded. This was traced to a timeout resulting from having numerous functions running on the portal combined with a configuration that returned an unowned AppHash when calling a ruleset from the production layer rather than the application layer, and has been resolved by adding logic to write out the AppHash when the appInfo is created from opening the application.

INC-168271 · Issue 640347

ADM performance improvements and duplicate inputs corrected for delayed learning records

Resolved in Pega Version 8.7

Additional work has been done to improve the performance for Adaptive Models used in multi-level decisioning, and an issue with duplicate pxCommonInputs has been resolved.

SR-A13590 · Issue 239611

Updated handling for Cyrillic usernames

Resolved in Pega Version 7.2.1

On systems where Windows user name was created in Cyrillic (ex C:\Users\?????? ????), generated word documents would be empty due to the characters in the directory name not being properly handled. The system now contains modified Silverlight code that will read the registry keys using RegOpenKeyEx, RegQueryValueEx and RegCloseKey functions of advapi32.dll as opposed to previously used RegRead function of Wscript.shell. These new registry functions are Unicode-aware. The Silverlight Prerequisites installer has also been modified to include the latest certificate.

INC-193986 · Issue 680032

Parameter logic updated for metrics activity counter

Resolved in Pega Version 8.7

An error was causing the PushCDHMetrics agent to fail. This was traced to an undefined parameter in the activity which was used as a counter, and has been resolved by replacing it with a local variable of type integer.

INC-169544 · Issue 649541

Enhancement for MaxEnt modeling data

Resolved in Pega Version 8.7

An enhancement has been added to create output for the model coefficients, the term frequency, and the inverse term frequency for use in maximum entropy modeling. For MRM processes, every Maximum Entropy (Maxent) based topic model will contain two additional stats resources. These resources can be used to validate and replicate running of topic model outside of Pega. The resources are: 1) Term Frequency file – A CSV file with all words used for training and their cumulative frequency across training set. File name format – TRAINING_DATA_TERM_FREQUENCY_< RandomNumber >.csv olumns – Word, Count 2) Coefficient file – A CSV file with all features (words, taxonomy matches and category matches) and model learnt weights for each topic across training set. File name format – MAXENT_COEFFICIENT_VALUE.csv Columns – Feature, < TopicName1 >, < TopicName2 > ,…, < TopicNameK >

SR-A22458 · Issue 243317

Plus '+' sign encoding corrected in connect-HTTP

Resolved in Pega Version 7.2.1

Using connect-http get to send an encrypted string to the external endpoint was not working due to missing encoding for the plus '+' string. The encoding has now been fixed.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us