SR-B14288 · Issue 289182
Command line BIX extract works as expected for -l option
Resolved in Pega Version 7.3
When a BIX extract was generated using rule XML of the extract rule (-I) from the command line, the manifest generated had "pxExtractIdentifier" in an unexpected format. The command line option has now been modified to generate the extract with the correct pzInsKey of the rule.
SR-B1495 · Issue 273198
Workaround to resolve HP NonStopDB column label bug
Resolved in Pega Version 7.3
Using HP Non Stop DB as an external DB with Type 4 driver caused Connect-SQL with Browse to generate the error "UNKNOWN_COLUMN_0: Column number 0 has an invalid name errors in clipboard" but still return the data. This was traced to a bug in the HP driver that caused the getColumnLabel() to be returned as empty, and the system has been updated to return the Column Name when Column Label is null or empty to overcome this.
SR-B15101 · Issue 296224
Logic added to convert UTC Date for REST clipboard mapping
Resolved in Pega Version 7.3
An error was generated while mapping UTC format Date fields to the clipboard in REST. This was traced to the DateTime properties in the JSON response not being converted to Pega-supported datetime format, and the necessary parsing logic has been added.
SR-B15138 · Issue 285032
RUF and listener updates made to support new version of Bouncy Castle
Resolved in Pega Version 7.3
Compatibility issues were found with Bouncy Castle 1.49 and newer versions of WebLogic. In order to proceed with updating Bouncy Castle to the latest version, the SendEmailMessage RUF in Pega-IntegrationEngine and Pega-Procom has been modified to adhere to the newer Bouncy Castle APIs, and the email listener has been updated. The logic related to Rule utility function compilation has been changed to only to consider the top version of a library.
SR-B154 · Issue 272522
Performance improvements for TableInformation queries
Resolved in Pega Version 7.3
System performance has been improved by caching and reusing the out-of-the-box query results used by TableInformation Cache to get the list of columns for a given table.
SR-B154 · Issue 290493
Performance improvements for TableInformation queries
Resolved in Pega Version 7.3
System performance has been improved by caching and reusing the out-of-the-box query results used by TableInformation Cache to get the list of columns for a given table.
SR-B15685 · Issue 292401
Flexibility enhancement for mobile dropdown displays
Resolved in Pega Version 7.3
As a part of an enhancement for mobile apps, a checkbox for "Allow scrolling for more results" has been introduced in the property panel of the Autocomplete. By default its value will be unchecked, implying the old behavior which limits the "Dropdown" options on autocomplete to 8 for backward compatibility. If the checkbox is used, it will honor the "Max results displayed" setting used for list based autocomplete. If the max results value is not specified, using the checkbox will cause the dropdown to show all the results.
SR-B15749 · Issue 289752
Enhancement for capturing SOAP envelope of Async SOAP Service
Resolved in Pega Version 7.3
The SOAP service request envelope has been available for service activity using the 'pxRequestor.pxReqSOAPEnvelope' property in synchronous execution mode, but that envelope was not available in asynchronous execution mode due to asynchronous execution using a different requestor. In order to support this information in asynch mode, an enhancement has been added to allow the service activity to perform a look-up for the pxReqSOAPEnvelopeinformation in the parameter page.
SR-B15880 · Issue 289450
Enable/disable of "+" icon in mobile app fixed
Resolved in Pega Version 7.3
The enabling and disabling of the "+" icon was not happening in the Mobile Hybrid app even when disabling condition were met. This has been fixed.
SR-B159 · Issue 272693
Wizard will halt if rules to be deleted are in locked rulesets
Resolved in Pega Version 7.3
After running the Connector and Metadata wizard using a WSDL metadata file and then locking the current ruleset version, running the same wizard again using the same WSDL file and selecting OverWrite in the OtherConflicts step caused the rules in the locked first ruleset to also be overwritten. To prevent this, the CompleteRuleGeneration activity will cause the wizard to halt if it encounters rules that would be deleted that are in locked rulesets. When the ruleset(s) are unlocked, the wizard will continue.