I need to be able to use the records in a Declared-Index table as either an index join or class join, obviously, Pega is preventing such usage.
The scenario is as follows:
I have a Pagelist within a Work- class that indicate who have access to this case, this is dynamic and selected and changed anytime the user desired.
A DI is created to flatten this into a corresponding table.
In the Assign-Worklist, I want to get a list of workitems that the current user have access to, based on the assignment as well as the Pagelist info (output thru a DI).
However, I am not allowed to do a Index Join to the Assign-Worklist because this is an index belonging to the Work-, not Assign-.
I am also not allowed to use this DI table as a class join to Assign-Worklist, as Pega does not allow me to map the corresponding keys from both tables.
Could anyone advise how I could use the RD to get a list of relevant workitems that a given user has access to based on the Pagelist defined above?
Using row Visibility is an option, but I hope to get the list from RD directly.
I am also trying to avoid RDB related stuff too.
Thanks and looking forward to any advice.
Give it a try and you will see the problem:
1) In the Work Class, create a PageList property
2) Do a DI for this PageList
3) Find any RD, e.g. from the Assign-Worklist, modify it to do a Declared Index Join or class join with the DI you created above, Pega will not allow that...
Note: by inspecting the data in both the Assign-Worklist and the DI classes, you will be able to see the key to be joined. Interestingly, Pega does not allow that...
Posted: 4 years ago
Posted: 30 Nov 2018 8:19 EST
Jacky Yap (yapj1)
Sr. System Architect
To add on to that, the key In the work class is pzInsKey, while its corresponding values is stored in the DI table as something like 'pzRefObjectKey'.
Doing a join on these 2 values are not allowed in Pega, for unknown reasons... that is the problem...