What are some good ways to pass data between Thread Pages?
I am in a data-portal section rule inside of which is a repeating grid of class data-contact
On-click my action is to create work in a work class.
The selected data-contact instance does not get passed into the new Thread page created for the create work flow item.
You cannot pass parameters into a starter flow.
I managed to pass properties between the Thread pages via the pxRequestor page.
But I feel that this is a bit of a 'hack'.
So is there a better way to pass data between Thread pages?
Pegasystems Inc.
US
Hi Robert,
Thanks for using the Product Support Community to ask this question. Hopefully, you'll find what you are looking for or at least have a good discussion about it.
May I suggest that you rephrase your discussion header to be something like "Any ideas for passing data between thread pages?".
We've found the more specific the question is in the discussion title, the better the chance of getting a response. "Thread Pages" may not catch someone's eye, but something like I suggested above might.
You should be able to update it right in your thread, but let me know if you need help and I'd be happy to.
Thanks.
B.
unitedhealth group
US
Hi Robert,
Hope this helps,to copy data between thread pages
ClipboardPage SourcePage= tools.getRequestor().getThread(PAThreadName).getPage(SourcePageName);
ClipboardProperty Sourceprop=SourcePage.getProperty("pxResults");
PublicAPI tools1=ThreadContainer.get().getPublicAPI();
tools1.createPage(TargetPageClass,TargetPageName);
ClipboardPage Targetpage=tools1.findPage(TargetPageName);
Targetpage.putAll(SourcePage);
Thanks,
Vivek
Updated: 10 Apr 2015 6:23 EDT
Recently we had used the below code to get a thing working for a similar use case. Using the below code, we can move the page to requestor scope so that its accessible across threads under the same requestor session. We can also use the code shared by Vivek in the above comment. The challenge there would be that we would need to get the thread names before hand.
sPageName --> input page name.
-----------------------code--------------------------------------------------------------------------------
Recently we had used the below code to get a thing working for a similar use case. Using the below code, we can move the page to requestor scope so that its accessible across threads under the same requestor session. We can also use the code shared by Vivek in the above comment. The challenge there would be that we would need to get the thread names before hand.
sPageName --> input page name.
-----------------------code--------------------------------------------------------------------------------
String sPageName = "MyPageAtRequestorScope";
ClipboardPage pg = tools.findPage(sPageName,true),pg_RequestorScope = null;
// this is being done just so that we don't duplicate the data. So we remove the page from clipboard for the current thread
if ( pg != null )
{
pg.removeFromClipboard();
pg_RequestorScope = ((com.pega.pegarules.priv.context.PegaRequestor)tools.getRequestor()).createRequestorPage("@baseclass",sPageName,true);
}
if (pg != null || (pg==null&& ! bCreateOnlyIfPresent) )
{
pg_RequestorScope = ((com.pega.pegarules.priv.context.PegaRequestor)tools.getRequestor()).createRequestorPage("@baseclass",sPageName,true);
// make sure that the page you are working on is cleared out.
pg_RequestorScope.clear();
}
if (pg != null )
{
pg_RequestorScope.putAll(pg);
}
Caution needs to be taken while using this API as it is a private API as Pega has rights to change this api implementation in any PRPC release. The same code is used in CPM FW function :-
MovePageToRequestorFamilyScope