INC-167311 · Issue 646477
Updated upgrade handling for migrating work objects
Resolved in Pega Version 8.3.6
After upgrading from Pega 6.2 to 8.3, the work migrated work objects were missing SLAs due to missed entries in the assignment tables (PC_ASSIGN_WORKLIST/ PC_ASSIGN_WORKBASKET) . The SLA was firing, but the processing failed due to the fact the runtime could not resolve a 'AddHistoryPage' library function. In this case, multiple upgrades of the application dating back to Pega 4 resulted in the runtime context containing older ruleset versions in higher ruleset versions, hiding the underlying Pega 8 version of the rule. For releases prior to Pega 7.3, Rule-Application was stored in pr4_rule and will be migrated to pr4_rule_application during upgrades. However, since Context Upgrade is run before Optimize Newly Exposed Columns, the pyDependsOnName won't always be populated. To resolve this, the system will filter based on the value in the blob rather than the exposed column so there will be a value regardless of the upgrade-from version.
SR-C62412 · Issue 402939
VBD enhancements added to assist in cleanup
Resolved in Pega Version 8.1.1
Running VBD for a long period of time will lead to accumulating partition summaries without a safe means to clean up. Enhancements have now been added to support the following:1) An API has been added to VBDService to support deletion of partitions from cache AND persistence prior to a date. This can be used as a building block for "keep last X days" functionality on a VBD dataset. 2) The Start Date will be used when loading Partition summary data when the service initially loads. Eviction logic has been implemented to remove partitions along with summary data (e.g. counts and dictionaries) for partition keys earlier than Start Date. Eviction occurs when Start Date moves ahead of partition's timestamp. If Start Date is updated backward by user and there exists data in Cassandra on these dates, then the partition summaries should be loaded into the cache. This requires a full cache reload which will be automatically triggered.
SR-B50202 · Issue 308172
Pre- and Post-processing modified to support customized circumstanced FA
Resolved in Pega Version 7.3.1
A customized out-of-the-box Flow Action called "CheckIn" was created by modifying a circumstanced version with property .pxObjClass = Rule-Admin-Product. For any Product rule, attempting checkin called this customized Flow Action as expected. However, the pre-processing activity and post-processing activity added in the circumstanced Flow Action "CheckIn" were not invoked at all; instead, the pre-processing activity and post-processing activity in the base Flow Action "CheckIn" were triggered. This was due to circumstancing not working when used with the doAction() method because it does not reset the primary page when it invokes a rule. It passes a step page for use by the rule. In order to support this customization, the function will call to tools.doActivity() with the same arguments instead of doAction(), which will force the engine to push myWorkPage as the new primary page for the duration of the call (and then pop it after the call completes). This should provide the correct context for the circumstancing to call the circumstanced purpose code.
SR-B63171 · Issue 315061
Pre- and Post-processing modified to support customized circumstanced FA
Resolved in Pega Version 7.3.1
A customized out-of-the-box Flow Action called "CheckIn" was created by modifying a circumstanced version with property .pxObjClass = Rule-Admin-Product. For any Product rule, attempting checkin called this customized Flow Action as expected. However, the pre-processing activity and post-processing activity added in the circumstanced Flow Action "CheckIn" were not invoked at all; instead, the pre-processing activity and post-processing activity in the base Flow Action "CheckIn" were triggered. This was due to circumstancing not working when used with the doAction() method because it does not reset the primary page when it invokes a rule. It passes a step page for use by the rule. In order to support this customization, the function will call to tools.doActivity() with the same arguments instead of doAction(), which will force the engine to push myWorkPage as the new primary page for the duration of the call (and then pop it after the call completes). This should provide the correct context for the circumstancing to call the circumstanced purpose code.
SR-D45698 · Issue 511090
Edit available rules now available for rules created in revision management control
Resolved in Pega Version 8.4
New rules created in a revision management context could not be removed from the overlay using the edit available rules functionality. This was caused by the delete button against all new rules being disabled due to the 'when' rule pyDisableDeleteInIncludedRules always being true for new rules created in revision management context. When new rules are created in the revision management context, the pyNewRuleInLP property will always exist and its value will be false. If a revision involving the new rule has not yet been submitted, the new rule is not displayed in the list of available rules at all. When the rule is displayed after the revision is submitted, the pyNewRuleInLP property value will always be false. In order to support the editing of rules in this scenario, the 'when' rule Data-Rule-Summary.pyDisableDeleteInIncludedRules has been updated so that instead of the "property pyNewRuleInLP exists and has value" check, there is now a "property pyNewRuleInLP is true" check.
SR-D59158 · Issue 534819
CMIS Update Request corrected for single Value List property
Resolved in Pega Version 8.3.2
After upgrade, following the process of searching Documents by connecting to CMIS and getting the results, then selecting the document, editing it, and resubmitting the document to the CMIS repository by clicking on the update button worked when passing a multi row of values to the Value list property but failed when passing a single row of value to the Value List property. An error was generated with the message "pega.pegarules.pub.services.InboundMappingException: Failed to process CMIS service 'updateProperties' ". In 7.2, updateProperties CMIS functionality uses the Apache API opencmis.commons.spi.ObjectService#updateProperties() whereas in 8.3 it is refactored to use the API opencmis.client.api.CmisObject#updateProperties() and this API allows multi-valued property to be updated with multiple values only. To resolve this, the CMIS connector has been modified to update the properties implementation such that it will pass-on the property update value to Apache OpenCMIS API as either List or Scalar based on the property definition (whether Property is configured as multi-valued or not).
SR-D59158 · Issue 534821
CMIS Update Request corrected for single Value List property
Resolved in Pega Version 8.4.1
After upgrade, following the process of searching Documents by connecting to CMIS and getting the results, then selecting the document, editing it, and resubmitting the document to the CMIS repository by clicking on the update button worked when passing a multi row of values to the Value list property but failed when passing a single row of value to the Value List property. An error was generated with the message "pega.pegarules.pub.services.InboundMappingException: Failed to process CMIS service 'updateProperties' ". In 7.2, updateProperties CMIS functionality uses the Apache API opencmis.commons.spi.ObjectService#updateProperties() whereas in 8.3 it is refactored to use the API opencmis.client.api.CmisObject#updateProperties() and this API allows multi-valued property to be updated with multiple values only. To resolve this, the CMIS connector has been modified to update the properties implementation such that it will pass-on the property update value to Apache OpenCMIS API as either List or Scalar based on the property definition (whether Property is configured as multi-valued or not).
INC-178489 · Issue 659914
Handling updated for custom attachment method
Resolved in Pega Version 8.7
When sending a correspondence using the standard SendSimpleEmail activity, choosing only one attachment from the multiple attachments in the work object by passing the pxLinkedRefTo property from the clipboard page to the AttachmentKeysToSend parameter instead of passing the value to the AttachmentCategoriesToSend parameter successfully sent the message and attached it to the work object. However, opening the correspondence attached to the work object showed the attached file as blank even though the attachment was present in the receiver’s email. Research showed that during the comparison of keys in place of pxLinkedRefTo, pzinskey was used. This caused the comparison to not register as true and the attachments display was skipped. Duplicate files were also being attached due to the previously attached files not being verified. Previous work updated the Data-Corr-Email.Show Html rule to use the pxLinkedRefTo field to find the right attachment. The URL encryption was also updated to ensure the links are functional and attachments can be downloaded. Additional work has been added to expand the use of the pxLinkedRefTo field to Show HTML called from @baseclass.
INC-202878 · Issue 713790
Handling updated for social messaging items with very large embedded images
Resolved in Pega Version 8.7.2
Job scheduler was running out of memory while handling large/multiple files, causing nodes to crash while handling Social Messaging items. Inline images were also not being sent in the ACK email. Investigation traced this to a custom job scheduler and activity used to create PDFs from email communication and send the PDFs to a third-party system. This used the standard Email Triage/PegaSocial functionality for the emails, which were stored as instances of PegaSocial-Message. The custom Job scheduler and activity then leveraged the Data Page D_pxEmailPosts to retrieve the emails in order to harvest the text from the emails. The issue occurred when a number of the emails had multiple or large embedded images in them, meaning the PegaSocial-Message instances are very large. This resulted in the node running out of memory and crashing. To resolve this, code has been added to support inline images in ACK email and the complete message from Pulse will be used instead of the original message as the email body for the ACK email.
INC-202878 · Issue 713792
Handling updated for social messaging items with very large embedded images
Resolved in Pega Version 8.6.5
Job scheduler was running out of memory while handling large/multiple files, causing nodes to crash while handling Social Messaging items. Inline images were also not being sent in the ACK email. Investigation traced this to a custom job scheduler and activity used to create PDFs from email communication and send the PDFs to a third-party system. This used the standard Email Triage/PegaSocial functionality for the emails, which were stored as instances of PegaSocial-Message. The custom Job scheduler and activity then leveraged the Data Page D_pxEmailPosts to retrieve the emails in order to harvest the text from the emails. The issue occurred when a number of the emails had multiple or large embedded images in them, meaning the PegaSocial-Message instances are very large. This resulted in the node running out of memory and crashing. To resolve this, code has been added to support inline images in ACK email and the complete message from Pulse will be used instead of the original message as the email body for the ACK email.