Here’s what I’ve done, I created an Activity in Work class which calls another Activity in Casetype class which inside Calls another Activity. In Work class’s Activity I passed Step page as “TempPage”, which now will be the context for called activities. But when I tried to access the properties from the called class using “primary” keyword it still stores the value in “TempPage” and not RunRecordPrimaryPage. Can somebody explain why? Or Am I understanding it wrong.
First of all you cant call the activity in case type class from your respective class group activity unless if you change the class to casetype class.
I assume your case type class structure is like (A-B-WORK-Case1) and work pool class here isA-B-WORK.
Lets say you create a page(temppage) in the activity (Parent) which is there in case layer and calls the activity (child) in work pool layer with the steppage as temppage then you can refer steppage data in work layer using Primary page and once this child activity execution gets complted then it tries to executes the next steps of parent activity. In the parent activity the default primary page is runrecordprimary page if you running it as standalone.
Hi @SHANJAYSHRIM2382 ,
Primary Page Context: The Primary keyword refers to the primary page of the activity. If you pass TempPage as the step page, it will override the default Primary page, and any reference to Primary in the called activity will refer to TempPage.
When you pass TempPage as the step page, it becomes the Primary page in the called activities, so whenever you access properties using the Primary keyword in those activities, it will be manipulating properties on TempPage, not on the original RunRecordPrimaryPage.
If you need to access RunRecordPrimaryPage (e.g., pyWorkPage) in the called activities while using TempPage as the step page, you can directly reference pyWorkPage or use findPage(“pyWorkPage”) instead of using Primary
Thanks,
Mohd Qizer Uddin