Pega Upgrade Assessment: 5 Rule Conversions to Check After the Update Utilities

Pega Upgrade Assessment: Rules to Check After the Update Utilities

After a Pega upgrade, the update utilities convert many older rules automatically, but not all of them. This post lists five conversions to review in Phase 1 of an upgrade assessment: what Pega converts, what it misses, and what to do about it.

The following are the 5 focuses for Phase#1: 

1. Dynamic Select to Dropdown 
2. Autocomplete to pxAutoComplete 
3. Embedded List perspectives to Report Definitions 
4. Cascading dynamic select to pxDropdown 
5. Converting Data tables to Data types 
What pega is giving post redesign after running diverse update utilities. 
what are the missing zones after utilizing utilities? 
What we are creating from grave rationale? Will clarify individually.
 

S.No

Rule

Pega Feature

Missing after upgrade

StaidLogic-Implementation

1

Dynamic Select to Dropdown

 

If the source is Report Definition or Clipboard Page: then Pega converting Dynamic select to a dropdown

 

If the source(s) is Listview or activity, pega is failing to convert the control

-Providing feature to convert dynamic select control irrespective of the sources and replacing them with the corresponding source.

2

Autocomplete to pxAutoComplete

 

Pega converting Autocomplete control to pxAutoComplete.

Source, after conversion, is missing.

Replacing with the correct source rule.

3

Embedded List views to Report Definitions

 

Pega is not upgrading/converting Listview to report definition.

We need to do it manually.

Converting List Views to Report Definitions automatically

4

Cascading dynamic select to pxDropdown

 

Conversion is working but the source is missing for original sources in dynamic select.

If the source(s) is Listview or activity, pega is failing to convert the control

-Providing feature to convert dynamic select control irrespective of the sources and replacing them with the corresponding source.

5

Converting Data tables to Data types

 

Conversion is happening

We need to work on columns that are like BLOBs

Taking care of conversion.

1. Dynamic Select to Dropdown:

• Starting with Pega 7.1, DynamicSelect and PromptSelect controls are deprecated, however are still supported for existing applications. 

• DynamicSelect doesn't support responsiveness and read-only falling DynamicSelect controls don't show effectively. 

• Replace the DynamicSelect and PromptSelect controls with Dropdown controls (pxDropdown). 

• The Dropdown control support the accompanying sorts of sources: • 

Report definition 

Clipboard page 

Data Page 

Consequently refreshing DynamicSelect and PromptSelect controls 

1. If the source is Report Definition or Clipboard Page: 

• If your DynamicSelect control has a Report Definition or Clipboard page as a source, you can consequently refresh the DynamicSelect control to a Dropdown control 

2. Upgrading DynamicSelect and PromptSelect controls with ListView sources 

• If a DynamicSelect or PromptSelect control is designed with a ListView as a source, you can't naturally move up to a Dropdown control. Make a Dropdown control and utilize the recently made report definition as the source. 

3. Upgrading DynamicSelect and PromptSelect controls with Activity source 

• If a DynamicSelect or PromptSelect control is arranged with an Activity as a source, you can't consequently move up to a Dropdown control. 

• Instead, the framework guides you to physically change over to a Dropdown control: 

2. Autocomplete to pxAutoComplete

• The Pega 7 Platform incorporates another Autocomplete control, pxAutoComplete. The pre-Pega 7 Autocomplete control is belittled. 

Naturally supplanting Autocomplete controls 

• If a segment contains a belittled Autocomplete control, an admonition is shown, alongside an Update Controls button. 

• Click Update Controls to naturally supplant belittled controls in the segment. 

1. We need to see about the sources after the change 

3. Inserted List perspectives to Report Definitions

• Use Report Definition-sponsored Repeat Grids rather than Embedded ListViews to exploit the most recent HTML5 abilities including cross-program and cross-stage similarity, access to the most recent HTML markup, and improved execution. 

Supplant Embedded ListViews with Report Definition-supported Repeat Grids 

We have to do it physically by making a Report Definition compares to a ListView. 


4. Cascading powerful select to pxDropdown

• The falling DynamicSelect usefulness is deplored. 

• read-only falling DynamicSelects don't populate in Chrome, Firefox, Internet Explorer 10, and Internet Explorer 11. 

• Hence, there is no cross-program support. 

• Replace falling DynamicSelect controls with pxDropdown controls. 

• Dropdown list-based controls are like the deprecated falling DynamicSelect usefulness. 

• The design for falling DynamicSelect was mind-boggling, however, Dropdown controls don't require any arrangement. 

• Any change in the parameter incentive to the wellspring of a list based control naturally refreshes the list at run time. 

If the source isn't list based, at that point we should take care of the setup for pxAutoComplete 

5. Converting Data Tables to Local Data Storage

• Data Tables are deprecated in Pega 7.1, yet are supported for existing applications.

1 comment: