SR-B13785 · Issue 284743
Added tenant ID check for batch thread in MT environment
Resolved in Pega Version 7.3
When attempting to build a Hybrid Container app in the mobile tab (landing page) in tenants, the build did not complete. The same build did work correctly in the main requestor. The issue was traced to a missing tenant ID if a secondary instance had been written to the database by a background thread, and has been resolved by explicitly checking and if necessary adding the tenant ID to PRThreadwhen using batch thread in a BuildServer client.
SR-B13785 · Issue 278965
Added tenant ID check for batch thread in MT environment
Resolved in Pega Version 7.3
When attempting to build a Hybrid Container app in the mobile tab (landing page) in tenants, the build did not complete. The same build did work correctly in the main requestor. The issue was traced to a missing tenant ID if a secondary instance had been written to the database by a background thread, and has been resolved by explicitly checking and if necessary adding the tenant ID to PRThreadwhen using batch thread in a BuildServer client.
SR-B13872 · Issue 290520
StartDependencies RUF logging updated from Error to Debug mode
Resolved in Pega Version 7.3
After calling a utility to create a child case through an activity on a parent sub-flow, updating the parent case status with the "UpdateStatus" activity logged an error message that the dependent had not been created successfully. This was an unintended side effect of a logging change made for diagnostic purposes, and has been fixed by changing the logs from Error mode to Debug mode in the pzStartDependencies RUF.
SR-B14774 · Issue 285008
Optional Process Child Case correctly sets ObjectClass
Resolved in Pega Version 7.3
When creating a Child Case from an Optional Process on the Case Type Rule, the ObjectClass of WorkPage did not update to the object class of the child case. The proper class was set when generated using an Automatic Process on the ObjClass. This has been corrected by using a performAssignmentCheck before acquiring work object.
SR-B14774 · Issue 285027
Optional Process Child Case correctly sets ObjectClass
Resolved in Pega Version 7.3
When creating a Child Case from an Optional Process on the Case Type Rule, the ObjectClass of WorkPage did not update to the object class of the child case. The proper class was set when generated using an Automatic Process on the ObjClass. This has been corrected by using a performAssignmentCheck before acquiring work object.
SR-B15604 · Issue 286328
Made InputProperty not mandatory for business logic
Resolved in Pega Version 7.3
When business logic is selected, pzToDecisionTreeExpress is selected as the routing activity for the assignment. However, errors occurred due to the mandatory parameter InputProperty property being passed as empty. To address this, the parameter will be marked as not mandatory.
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-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-B16331 · Issue 303039
Check added to WorkUnlock to ensure cover page exists
Resolved in Pega Version 7.3
An intermittent error was logged related to workunlock. This was caused by Work-.Close calling workUnlock from the param.coverPage without performing a check first to ensure that the coverPage exists and has a class. To fix this, the WorkUnlock activity has been modified to verify that the coverPage has a class before unlocking the cover object.
SR-B16331 · Issue 294717
Cover page check added to Work-Close
Resolved in Pega Version 7.3
An intermittent stack trace was being generated in Work-Close; this has been resolved by adding a check to ensure that the coverPage exists and has a class.