SR-B74088 · Issue 324942
Enhancement for Optimizing Packaging during full & delta sync
Resolved in Pega Version 7.3.1
As part of an enhancement for more contextual, optimistic packaging algorithm in certain conditions, packaging can be optimized based on a setting available at the case type. For example, most Field Service applications where offline capability is heavily used don't have or need the ability to instantiate or create new cases, but rather work on existing assignments routed to the agents. Some sites have the additional constraint where the case types or the flows within a case type may be large in number and dynamically created, which means the first full sync will just not be sufficient for the user to work on later created assignments. This has an adverse impact on the performance of the full sync and the first login time. The following changes have been introduced: - On delta sync - if a new work item ( of new case type which is not there during full sync packaging ) is added to work list. All the dependent rules of this new case type will be packaged and sent to HC. Added an checkbox in the case type rule "Only offline when in user's worklist" which will be visible only when "Enable Offline" is checked. - Provided a new when rule pyPackageAssignmentFlows which is set to false by default. When the true, all the case type with "Only offline when in user's worklist" will have selective flow packaging. - Create a class structure with a page group to hold full packaging and optimized packaging Application.pyOfflineCaseTypes("full") Application.pyOfflineCaseTypes("optimized") Above properties are populated in pzGetStartingFlows activity which is ran on delta sync and full sync. - Flows that are created in the case with "Only offline when in user's worklist" check are listed in pzDataSyncGetworkList which will be packaged during delta sync. The flows are listed for packaging if there is any Work Object created, flow is retrieved from the Assignment's pzInsKey key, and Flow key is built. Changes are made in the PackageRuntime.java to iterate the flow and perform packaging.
SR-C4920 · Issue 347563
Grid Header checkbox behavior modified for consistency
Resolved in Pega Version 8.1
Unexpected behavior was seen when clicking on the Checkbox present in Header: all other checkboxes changed their state (which was expected), but if the the Readonly checkbox was checked it was also changing the state the first time (which was not expected). After this first state change, the read-only checkboxes were not changing state (which is correct behavior). Previously, the behavior of Select All / CheckAll checkboxes was as follows: If the SelectAll / CheckAll checkbox is checked - Individual checkboxes are checked only when they are NOT disabled If the SelectAll / CheckAll checkbox is unchecked - Individual checkboxes are unchecked irrespective of their DISABLED state The behavior has now been changed as below: If the SelectAll / CheckAll checkbox is checked - Individual checkboxes are checked only when they are NOT disabled If the SelectAll / CheckAll checkbox is unchecked - Individual checkboxes are unchecked only when they are NOT disabled
SR-C7762 · Issue 350154
Commas removed from filter values to resolve validation errors
Resolved in Pega Version 8.1
When using a Grid layout configured in a section rule, clicking the Filter option and entering a comma separated value in the "To" field in a decimal-type column resulted in an "Invalid numeric range" option message. No error was seen if comma separated values were entered in both the "To" and "From" fields. Because the checkRangeFilter() function in ui_grid.js uses parseFloat() API to extract the decimal content entered in the search boxes, decimals after commas are ignored and validation failed due to the fields not matching. This issue has been fixed by implicitly removing any commas entered by the user.