Question
]init[ AG
DE
Last activity: 8 Mar 2018 7:07 EST
Properties in Data-Portal
Hi,
I am building an application based on a Portal stored in Data-Portal-MyPortal. In the Portal the user should be able to type business data into text fields (which have properties defined and post-value on change active) and then click on a button which opens a case (MyCorp-MyApp-Work-Case). The main purpose of the case is to store the data that the user previously typed into the Portal.
Now I am having issues with transferring the business data from the Portal to the Case. I tried via Parameters, Pages&Classes Tab and defined the properties in the Portal on a Data-Page. Nothing seems to be capable of accessing the properties of a Portal, are they in some way designed not to do that?
Besides, what is the difference between starting my case by using pyStartCase or the actual case flow? When using the Create Work Action it seems to make no difference.
Thanks in advance
Tobias
EPAM Systems, Inc.
ES
]init[ AG
DE
Hi Asif, thanks for your Answer.
First, you want to take input from end user in the portal and transfer the value on click of button to work- class? Correct me, if my understanding is wrong.
Correct, thats what I am trying to achieve.
You can define your Page or UI property structure in "Data-" class and then create a page/pagelist(as per your business requirement) in the "Work-" class and refer the "Data-" as the definition of Page list and use it in your UI to perform or store action.
Hi Asif, thanks for your Answer.
First, you want to take input from end user in the portal and transfer the value on click of button to work- class? Correct me, if my understanding is wrong.
Correct, thats what I am trying to achieve.
You can define your Page or UI property structure in "Data-" class and then create a page/pagelist(as per your business requirement) in the "Work-" class and refer the "Data-" as the definition of Page list and use it in your UI to perform or store action.
I tried this and it fails. It appears to me that Information cant really "leave" the Portal, except from Parameters for a Report filling up a Repeat Grid in the Portals UI.
I think i confused you by mentioning all the ways I tried to get the user input from data-portal to my work class. I did not use them all at once but rather tried them over and over and none of them worked so far: Page list in work class, Data Page, Pages&Classes Tab and Parameters - all of these seem to be incapable to transfer the user input into the work class. Several colleaques of mine had a look at this problem, we will have to change our application design due to that.
Thanks for your explanation on the Topic pyStartCase. This appeared as a "problem" only because pyStartCase is the only flow being shown in the "Create work" option.
EPAM Systems, Inc.
ES
Useful additional References:-
Data and Work Class.
- https://collaborate.pega.com/discussion/what-difference-between-data-class-and-work-class
- https://collaborate.pega.com/discussion/data-class-and-work-class
"pyStartCase":-
- https://collaborate.pega.com/question/flow-create-new-work-object
- https://pdn.pega.com/community/pega-academy/question/pystartcase-default-flow (If you don't pyStartcase at all).
Review them.
Hi,
Thanks for posting on PSC.
You have two questions put up,
First, you want to take input from end user in the portal and transfer the value on click of button to work- class? Correct me, if my understanding is wrong.
And this of page structure, as you're somewhere trying to map it to data page and access(I am not clear on data page part of your question).
Let's discuss the difference and purpose of work and data class at first to understand.
Work Class - Contains the rules that describe how to process a case, such as processed, date element and user interfaces. They can be instantiated or an object could be initialised if you compare in java terms.
Data Class - Contains the rules that describe the data objects used in the application, such as a customer or collection of order items. They are like(close but not exactly) interface, it can't be instantiated though could be used as the container.
You can define your Page or UI property structure in "Data-" class and then create a page/pagelist(as per your business requirement) in the "Work-" class and refer the "Data-" as the definition of Page list and use it in your UI to perform or store action.
Hi,
Thanks for posting on PSC.
You have two questions put up,
First, you want to take input from end user in the portal and transfer the value on click of button to work- class? Correct me, if my understanding is wrong.
And this of page structure, as you're somewhere trying to map it to data page and access(I am not clear on data page part of your question).
Let's discuss the difference and purpose of work and data class at first to understand.
Work Class - Contains the rules that describe how to process a case, such as processed, date element and user interfaces. They can be instantiated or an object could be initialised if you compare in java terms.
Data Class - Contains the rules that describe the data objects used in the application, such as a customer or collection of order items. They are like(close but not exactly) interface, it can't be instantiated though could be used as the container.
You can define your Page or UI property structure in "Data-" class and then create a page/pagelist(as per your business requirement) in the "Work-" class and refer the "Data-" as the definition of Page list and use it in your UI to perform or store action.
Now let's come to the second question,
"pyStartCase" is an OOTB initial flow, though you can always alter or replace it with your own custom flow under Case rule. It's made available by Pega to assist in initiating the flow rather creating whole things from scratch as per my knowledge.
Please rectify me, if I misunderstood your requirement and led you to complete astray.
Though, if you find above explanation helpful. Kindly mark this post as answered for tracking purposes and broader Pega audience.
Regards,
Asif