What is the difference when we simply write a page name in step page and when we provide a (dot) .pageName in the step page?
In an activity while mentioning the step page I have observed 2 ways: one is defining the page name in page and classes and using that in step page and other is straightaway using a dot(.)before the page name in step page field and this page belongs to the same class in which we have created the activity.
This is being used in case of file listener to parse CSV files and store the records in the data type.
There is a Service File activity where we are mapping properties from the Service page to a Temp Page(which points to the data type),now this Service Page is created under MyBank-Data-FL class but has a page definition of MyBank-Data-products and the temp page that we are using to save back the data to a data type is also pointing to MyBank-Data-products so here I am not understanding how exactly pega is working?
Like in the end both the pages are pointing to MyBank-Data-products so why do we need to do mapping?
Please find attachment of the activity step and pages and the Parse Delimiter rule as well.
MyBank-Data-FL(This is the Service File Class and here one page Property named Product Page is created with page definition as MyBank-Data-Products)
Now a Temporary Page named ProductPg(Class as MyBank-Data-Products) is used to map the data from service page to data type.
Rulesstack Private Limited
IN
Hi @TanyaS58,
The difference between simply writing a page name in the "Step Page" field and providing a .pageName (with a dot) in the "Step Page" field is related to the context and structure of the clipboard where the pages reside.
Simple Page Name (e.g., Customer)
- Context: When you specify a simple page name like Customer in the Step Page field, Pega will look for a top-level page named Customer on the clipboard.
- Usage: This is used when the page is at the root level of the clipboard, directly accessible, and there’s no ambiguity or need to traverse the clipboard structure to access it.
- Example:
- If you have a top-level page called Customer on the clipboard and you specify Customer as the Step Page, the action or rule will directly operate on this page.
2. Dot Notation (.pageName, e.g., .Customer)
Hi @TanyaS58,
The difference between simply writing a page name in the "Step Page" field and providing a .pageName (with a dot) in the "Step Page" field is related to the context and structure of the clipboard where the pages reside.
Simple Page Name (e.g., Customer)
- Context: When you specify a simple page name like Customer in the Step Page field, Pega will look for a top-level page named Customer on the clipboard.
- Usage: This is used when the page is at the root level of the clipboard, directly accessible, and there’s no ambiguity or need to traverse the clipboard structure to access it.
- Example:
- If you have a top-level page called Customer on the clipboard and you specify Customer as the Step Page, the action or rule will directly operate on this page.
2. Dot Notation (.pageName, e.g., .Customer)
- Context: When you use a dot notation like .Customer, it indicates that Customer is a property or embedded page within the current step page or another parent page in context.
- Usage: This is used to reference a page that is nested within another page. The dot notation tells Pega to look for the Customer page within the current or specified parent page on the clipboard.
Regards,
Mohd Qizer Uddin
Cognizant
IN
@Mohd Qizer Uddin so bascially .CustomerPage means we are referring to a page of different context and we want to access the properties in this page's context? Is my understanding correct?
Cognizant
IN
@TanyaS58, From parse rule they are copying data to the embedded page property, in the activity they are copying the data from embedded page property to top level page, could you check further steps in the activity? after saving to top level page what happened to the embedded page property?