SR-124007 · Issue 187611
Added handling for NPEs on mobile devices
Resolved in Pega Version 7.1.8
Answering a questionnaire on a mobile device was generating the error "NullPointer in SafeURL.put()" due to the source element being a radiobutton div and not sending the request for postvalue. This was a missing condition in the initiatepost method of pega_ui_events for handling NPEs on mobile and the system has been modified to correct this.
SR-124011 · Issue 184792
Repaired Case Designer rendering for Microsoft Internet Explorer 8
Resolved in Pega Version 7.1.8
When using the Microsoft Internet Explorer 8 browser, opening a case type in Case Designer which has steps in the stages did not render the steps. This was caused by a CSS file fragment that was not picking up the proper base styles, and has been fixed.
SR-124027 · Issue 190234
BPEL rule types deprecated
Resolved in Pega Version 7.1.8
BPEL is a flow format that makes SOAP calls to other systems. Previously, Rule-Connect-BPEL and Rule-Service-BPEL were supported types not as callable rules, but as summaries of the rules involved with interacting with a particular BPEL flow. This usage originated before the advent of landing pages, and summarized the connector or service rules, respectively, that were in the system for a given BPEL-related service package. It has been found that the BPEL-specific standard in version 1.1 and higher does not carry enough information in its schema to do an import and requires limitations and post-import work to make the flows usable. In addition, BPEL import was supported only with Visio. In Pega 7 there is no Visio view for flows, so these flows cannot be viewed or edited. Therefore the following rule types have been deprecated as of this release: -------------------------------------------------- Form Hierarchy Service COM Service BPEL+D249 Connect BPEL Parse Transform Parse Transform Collection Parse Infer Attempting to use these rule types will present the following messages: -- Service BPEL: "The rule type Service BPEL is deprecated and should no longer be used. Please use Service SOAP instead." -- Connect BPEL: "The rule type Connect BPEL is deprecated and should no longer be used. Please use Connect SOAP instead."
SR-124028 · Issue 189200
BPEL rule types deprecated
Resolved in Pega Version 7.1.8
BPEL is a flow format that makes SOAP calls to other systems. Previously, Rule-Connect-BPEL and Rule-Service-BPEL were supported types not as callable rules, but as summaries of the rules involved with interacting with a particular BPEL flow. This usage originated before the advent of landing pages, and summarized the connector or service rules, respectively, that were in the system for a given BPEL-related service package. It has been found that the BPEL-specific standard in version 1.1 and higher does not carry enough information in its schema to do an import and requires limitations and post-import work to make the flows usable. In addition, BPEL import was supported only with Visio. In Pega 7 there is no Visio view for flows, so these flows cannot be viewed or edited. Therefore the following rule types have been deprecated as of this release: -------------------------------------------------- Form Hierarchy Service COM Service BPEL Connect BPEL Parse Transform Parse Transform Collection Parse Infer Attempting to use these rule types will present the following messages: -- Service BPEL: "The rule type Service BPEL is deprecated and should no longer be used. Please use Service SOAP instead." -- Connect BPEL: "The rule type Connect BPEL is deprecated and should no longer be used. Please use Connect SOAP instead."
SR-124029 · Issue 189201
BPEL rule types deprecated
Resolved in Pega Version 7.1.8
BPEL is a flow format that makes SOAP calls to other systems. Previously, Rule-Connect-BPEL and Rule-Service-BPEL were supported types not as callable rules, but as summaries of the rules involved with interacting with a particular BPEL flow. This usage originated before the advent of landing pages, and summarized the connector or service rules, respectively, that were in the system for a given BPEL-related service package. It has been found that the BPEL-specific standard in version 1.1 and higher does not carry enough information in its schema to do an import and requires limitations and post-import work to make the flows usable. In addition, BPEL import was supported only with Visio. In Pega 7 there is no Visio view for flows, so these flows cannot be viewed or edited. Therefore the following rule types have been deprecated as of this release: -------------------------------------------------- Form Hierarchy Service COM Service BPEL Connect BPEL Parse Transform Parse Transform Collection Parse Infer Attempting to use these rule types will present the following messages: -- Service BPEL: "The rule type Service BPEL is deprecated and should no longer be used. Please use Service SOAP instead." -- Connect BPEL: "The rule type Connect BPEL is deprecated and should no longer be used. Please use Connect SOAP instead."
SR-124036 · Issue 190234
BPEL rule types deprecated
Resolved in Pega Version 7.1.8
BPEL is a flow format that makes SOAP calls to other systems. Previously, Rule-Connect-BPEL and Rule-Service-BPEL were supported types not as callable rules, but as summaries of the rules involved with interacting with a particular BPEL flow. This usage originated before the advent of landing pages, and summarized the connector or service rules, respectively, that were in the system for a given BPEL-related service package. It has been found that the BPEL-specific standard in version 1.1 and higher does not carry enough information in its schema to do an import and requires limitations and post-import work to make the flows usable. In addition, BPEL import was supported only with Visio. In Pega 7 there is no Visio view for flows, so these flows cannot be viewed or edited. Therefore the following rule types have been deprecated as of this release: -------------------------------------------------- Form Hierarchy Service COM Service BPEL Connect BPEL Parse Transform Parse Transform Collection Parse Infer Attempting to use these rule types will present the following messages: -- Service BPEL: "The rule type Service BPEL is deprecated and should no longer be used. Please use Service SOAP instead." -- Connect BPEL: "The rule type Connect BPEL is deprecated and should no longer be used. Please use Connect SOAP instead."
SR-124044 · Issue 188405
Save as fixed for French localization
Resolved in Pega Version 7.1.8
Setting localization to French in the Microsoft Internet Explorer browser and attempting a property save generated a JavaScript error. The root cause of this problem was traced to the localized French string value for the English equivalent of dupPropPrompt contained the ' character, which broke the first line of code in RULE-OBJ-PROPERTY PZDUPLICATEPROPERTYMSG. This has been fixed.
SR-124054 · Issue 189568
Simulation delete timing issue resolved
Resolved in Pega Version 7.1.8
When attempting to delete a simulation, if the deletion process exceeded the system time-out or the space on the database required for undo was too small (as can occur when many simulations have been run and the simulation output table contains many millions of records), the mass deletion failed and the system became hung or returned a time-out screen which required logging out and in again. At that point it was seen that the simulation results had been removed from the list but the actual results deletion did not complete. This was caused by the simulation work item being closed first, followed by the delete of the table. In the case of a failed deletion because of any DB issue, manual intervention was required to delete the records from the table as the simulation object was no longer available. To resolve this, the sequence of steps while deleting the Batch WO from LPhas been updated to show the relevant error message in case of failures for any reason, and the work object is closed after the output table is deleted.
SR-124085 · Issue 184464
Adjusted error handling of "Prebuild Conclusions" during upgrade
Resolved in Pega Version 7.1.8
The "Prebuild Conclusions" task of an upgrade was failing with the error 'ClassNotFoundException'. This was caused by a misconfiguration in the operating environment that led to the jar file that contains the class not being on the classpath during the upgrade. There was a workaround of setting the build.conclusions=false, but a check has been inserted that will skip these error entries and continue building the remaining conclusion entries.
SR-124103 · Issue 185047
Error logging smoothed for service activities-multi threading on multiple nodes
Resolved in Pega Version 7.1.8
When an item was processed by one node and then in the process of being dequeued by the same node, other nodes attempting to access the same instance and queue received a warning message indicating the item had failed to dequeue. This message was verbose, and was filling up logs. For Advance mode Agents, when item is not found in the Queue Engine it was logging the message with "warnForced". To prevent the logging issue, the log level has been changed from 'warnForced' to 'warn'.