This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Custom WorkFlow - Custom Step

Hi,

We are looking for options to incorporate a custom step in the work flow process. The custom step should connect to a database and verify the status of the person before moving on the next level approver.

We could find any options to write a custom code withing the workflow. The only options available is to choose the OOTB Approval procedure which is in turn non customizable

Any info would be of help.

Thanks

Jsmith

Parents
  • Hi Kapil,

    events initiated by the EX approval procedure are generated on the associated PersonWantsOrg (if IT Shop request) or AttestationCase (if attestation) objects. IMHO, the best example still is the combination of approval workflow Approval of AD group create requests and process VI_ESS_PersonWantsOrg create AD group mentioned earlier in this thread. 

    The first argument of the MakeDecision method (referenced as param1 in the process step definition) needs to be the UID_Person of a valid decision maker or "sa" for "system decision". As there's usually no employee entitled to decide a request at this point (ie. level that contains the EX step), "sa" is the only option you're left with.

    The third argument (decision reason) is stored alongside with the decision itself in PWODecisionHistory and might be retrieved from there.

    HTH,

     Oliver 

Reply
  • Hi Kapil,

    events initiated by the EX approval procedure are generated on the associated PersonWantsOrg (if IT Shop request) or AttestationCase (if attestation) objects. IMHO, the best example still is the combination of approval workflow Approval of AD group create requests and process VI_ESS_PersonWantsOrg create AD group mentioned earlier in this thread. 

    The first argument of the MakeDecision method (referenced as param1 in the process step definition) needs to be the UID_Person of a valid decision maker or "sa" for "system decision". As there's usually no employee entitled to decide a request at this point (ie. level that contains the EX step), "sa" is the only option you're left with.

    The third argument (decision reason) is stored alongside with the decision itself in PWODecisionHistory and might be retrieved from there.

    HTH,

     Oliver 

Children
No Data