Featured post

GetNextWork functionality in pega

What is GetNextWork in pega? Pega provided a functionality to get the most urgent assignment(task) for user to work on. This is configured o...

Pega - UpgradeAsesment-FivePoints

The following are the 5 focuses for Phase#1: 

1. Dynamic Select to Drop down 
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 subsequent to running diverse update utilities. 
what are the missing zones subsequent to 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 Drop down

 

If the source is Report Definition or Clipboard Page: then Pega converting Dynamic select to 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 with 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 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 with corresponding source.

5

Converting Data tables to Data types

 

Conversion is happening

We need to work on columns which are like BLOBs

Taking care of conversion.

1.Dynamic Select to Drop down: 

Starting with Pega 7.1, DynamicSelect and PromptSelect controls are expostulated, however are as yet upheld for existing applications. 

DynamicSelect doesn't bolster responsiveness and read-just falling DynamicSelect controls don't show effectively. 

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

The Dropdown control bolsters 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 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-upheld Repeat Grids 

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


4. Cascading powerful select to pxDropdown 

The falling DynamicSelect usefulness is deplored. 

Read-just 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 expostulated 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 rundown based control naturally refreshes the rundown at run time. 

In the event that the source isn't a rundown based, at that point we should take care the setup for pxAutoComplete 

5. Converting Data Tables to Local Data Storage 

Data Tables are expostulated in Pega 7.1, yet are bolstered for existing applications.



1 comment: