Precisely Enterworks

 View Only
Expand all | Collapse all

In EPX workflow, how to capture User Information when they perform certain action? Like Resubmit/Approve/Reject...

  • 1.  In EPX workflow, how to capture User Information when they perform certain action? Like Resubmit/Approve/Reject...

    Posted 06-16-2023 04:21
    • I want to capture the user action and comment when they interact in a EPX workflow into a Commentary repo.

    • To achieve this I leveraging the system level metadata information, like 'sys.workitem.initiator'. And using it to fetch user information from B_USER

    • It works very well when we have an user who is the workflow initiator, and the same user is also an approver/resubmitter, because we can retrieve who approved or resubmitted in such case from 'sys.workitem.initiator'. As sys.workitem.initiator holds user login who submitted the workflow and, same user is also performing manual activity in other manual steps

    • But the challenge arises when we have different users performing different role. For example, User U1 from Group G1 initiates the workflow, but U2 belonging to Group G2 is approving this workfitem at certain point in the workflow.

    • Here, 'U1' details can be retrieved from system metadata 'sys.workitem.initiator' , but how to retrieve information on 'U2' ? Which system property stores this user information who is acting on the same workitem in the middle of workflow?



    ------------------------------
    Bighnajit Mishra
    lululemon athletica
    ------------------------------


  • 2.  RE: In EPX workflow, how to capture User Information when they perform certain action? Like Resubmit/Approve/Reject...

    Posted 06-16-2023 10:38

    Sounds like you want to use a combination of the property %sys.workitem.previousmanualsender% and possibly the Dynamic Actor role on manual activities.

    sys.workitem.previousmanualsender will contain the login of the user who sent the last activity, so if you want to preserve it after a Manual Activity, you would need a set properties BIC immediately after the Manual Activity that takes the sys.workitem.previousmanualsender and stores it as a unique property; this is because certain automated BICs will overwrite this system property with the name of the BIC.

    Once you have that stored as a unique property, you could leverage the Dynamic Actor role to then only have a subsequent Manual Activity contain a work item for that specific user as opposed to the group.

    Here is a Precisely Tech Talk that explains Dynamic Actor and how to implement it: Link



    ------------------------------
    Matthew Hounslow
    Amplifi
    Dallas TX
    ------------------------------