Data-Transform for properties
Data-Transform for properties
6. In the Action column of definition tab select the Update page and set target as ResultsPage.
7. In the set action nested in update page action write the target as
.pyPropertyName and set it equal to a property defined in the class you identified for creating
this data-transform eg:- pyReopenCount
8. By the end of this step you should have a screen similar to the image below
9.Right click on the action value “Update Page” and click on the option “Add Sibling Below”
10. In the newly generated action value select Update Page again and select FinalTempPage as the
target page
11. In the Action nested below the new update page Select the “Append to” action and in the Target
select “pxResults”(from drop-down)
12. In the relation next to the pxResults select the option “an existing page” and in the source column
select “ResultsPage” as the source.
17.Right click on the action value “Update Page”(bottom-most) and click on the option “Add Sibling
Below”.
18.In the Action column of definition tab select the Update page and set target as FinalTempPage
19.In the set action nested in update page action write the target as .pyClassName and set it equal to a
classname you identified for creating this data-transform eg:- PegaSample.
21.Right click on the action value “Update Page”(bottom-most) and click on the option “Add Sibling
Below”.
22. In the newly generated action value select Update Page again and select
pgAvailableProperties(Code-Pega-List) as the target page(You will get a list of options from the drop-
down)
23. In the Action nested below the new update page Select the “Append to” action and in the Target
select “pxResults”(Can be selected from the drop-down)
24. In the relation next to the pxResults select the option “an existing page” and in the source column
select “FinalTempPage” as the source.
26. Remember to add the step “Remove” to remove the results of the updated pages for the data is not
appended or overridden when the data-transform is called again.
27.Right-Click on the top-most Update-Page step and Select “Add Sibling Above” and add select
“Remove” in action tab and mention “pgAvailableProperties” in the target.
Due By
Reopen Count
31. Note that when Call Super Class data transform is checked it will also check for the data-transform
created in the super-class with the same name “pyReportEditorProperties” the properties created in
the super class will also be present in Available Columns Tab.
To add the embedded properties you need to add the details in the steps mentioned below soon after
adding the top-level property list.
3. In the Action column of definition tab select the Update page and set target as ResultsPage
4.In the set action nested in update page action write the target as .pyPropertyName and set it equal to
the Top-level property in which the embedded property is present. eg:- pyWorkParty.
5. Immediately right click on the update page step you created and select “Add Sibling Below”.
6. In the Action column of definition tab select the Update page and set target as NestedResultsPage
7.In the set action nested in update page action write the target as .pyPropertyName and set it equal to
the embedded property you identified. eg:- pyPartyIdentifier.
8. At this juncture you can distinguish whether to use the embedded scenario as a page-list or an
indexed property.
9. If you finish your embedded structure by step 7 then the embedded property is considered as a page-
list property.
10. It can be changed to an indexed property by adding another step as a sibling to the step 7 i.e.; the
pyPartyIdentifier step as per the example
11. In that set action just added write .pyBaseclass as target and set its value appropriately in the source
e.g:- PartyURI for the pyWorkParty ensemble.
12. Your Data-Transform Rule should resemble the following screen.
14. Right click on the Update-Page step of the NestedResultsPage and select the option “Add sibling
below”.
15. In the Action column of definition tab select the Update page and set target as FinalTempPage
16. In the set action nested in update page action change to update page again and set target as
ResultsPage.
17. In the Action nested below the new update page Select the “Append to” action and in the Target
select “pxResults”(to be entered manually)
18. In the relation next to the pxResults select the option “an existing page” and in the source column
select “NestedResultsPage” as the source.
21. In the Action nested below the new update page Select the “Append to” action and in the Target
select “pxResults”(to be entered manually)
22. In the relation next to the pxResults select the option “an existing page” and in the source column
select “ResultsPage” as the source.
Due By
Parties
Party ID
Reopen Count
Generally you may want to use the properties from the associations, joined classes as well
1. In already known behavior i.e.; in the “Best Bets” tab we have an icon(+) and value which reads
“More”.
2. You can avail the same facility with this data-transform by adding the details in the step below
to the data-transform you already created.
3. Right click on the step below as shown in the screen
4.After clicking on “add sibling above” In the Action column of definition tab select the Update page and
set target as MorePage
5. In the set action nested in update page action enter “.pyPropertyName” in the target and write
“More”(in the same case) in the source tab
9. In the relation next to the pxResults select the option “an existing page” and in the source column
select “MorePage” as the source.
12. You can add More without adding embedded property also. In that case your data-transform will
resemble the below-screen.
Note:- The properties brought forward by the associations, joins etc. can be customized by creating a
data-transform rule as suggested in the classes of the same.
And on right-clicking the page and opting “Show-XML” the XML structure which resembles the
screenshot shown below.