SR-123809 · Issue 185686
Report schedule icon display fixed for SQL
Resolved in Pega Version 7.1.8
When disabling then re-enabling the task for a scheduled report through the report browser, the icon that indicates whether the report is scheduled will sometimes not show. That is, the report is actually scheduled, and will run at the appointed time, but there will be no icon in the report browser to show that it is scheduled. The SQL query to retrieve the list of scheduled reports was being generated incorrectly for certain databases (e.g., MS SQLServer). Therefore the rescheduled reports were omitted from the list, and no icon would be displayed for them. To resolve this, the custom getcontent activity 'pxgetRRContentForRB' has been inserted.
SR-123820 · Issue 185192
Fixed truncated custom datetime in RD
Resolved in Pega Version 7.1.8
If a report was created on work objects that used a property of type DateTime in Report definition output, custom datetime settings were truncated. This was a problem with the grid implementation where the modified GenerateGridHTML. "D" was set always to propTypeForFormatting even for DateTime. It has bene fixed.
SR-123911 · Issue 189019
Changed timing for retrieving autocomplete values after modifications
Resolved in Pega Version 7.1.8
When AutoComplete controls is used to populate Data, a wrong value was sometimes getting populated in the AutoComplete. The issue was due to the delay in change tracking request after the request is complete, causing it to take values from the server before the changes were committed. This has been corrected.
SR-123911 · Issue 192195
Changed timing for retrieving autocomplete values after modifications
Resolved in Pega Version 7.1.8
When AutoComplete controls is used to populate Data, a wrong value was sometimes getting populated in the AutoComplete. The issue was due to the delay in change tracking request after the request is complete, causing it to take values from the server before the changes were committed. This has been corrected.
SR-123960 · Issue 184251
Error message updated for report 'save as'
Resolved in Pega Version 7.1.8
The error message created when doing a 'Save As' report to a private category has been updated for clarity. Previously, the error generated was "The name you entered is not valid". This has been changed to "The name should start with letter followed by letter or digit or underscore".
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-124246 · Issue 185967
Added NPE check for empty indexed pyID properties
Resolved in Pega Version 7.1.8
Certain searches resulted in a null pointer exception that appeared to be occurring in the FTSContentExecutor class. This issue was caused by a null (empty) pyID property in the indexed instance and has been corrected by inserting handling for any NPE generated in this circumstance.