Bumping this... anyone able to help?

X3 comes with an standard purchase signature workflow. If you are creating a separate one, have you inactivated the standard one? Otherwise, both workflows may be triggered at the same time. 

Also, can you give more detail on how your workflow is setup? Maybe a screenshot of the workflow rules if possible. Thank you!

Hi Michael.

I've tried deactivating the existing workflows relating to purchasing to see if there was any conflict but this does not seem to be the case.

I've got a completely separate assignment rule set up for this signature workflow. Our purchasing assignment rule is ZPOHSIG and this new one is ZBPRQ.

I believe it is something to do with the actions on the workflow, but I don't know which one of those actions would be responsible for cancelling the original signature request.

This is the workflow I have set up:-

Hi Nick,

Was there a customization involved?

I see reference of object BPRQ, table BPRQ, and Data model of DMBPRQ, and I do not have them in my demo system. 

In any case, i think you may need more than one workflow setup for this. I am not sure what your signature suppose to do. But if you take a look at the standard purchase order signature workflows, you will find that there are several different workflows. POHSIG show the workflow that triggers for signature. POHSIGCAN shows the action that cancels the signature. POHSIGVAL, and POHSIGREJ shows what happens when the user approve/reject a workflow. 

I know this is not much, but I hope this information helps. 

Hi Michael

Yes, this is something I've built out. I'm comfortable setting up another workflow, but I don't know how this would work to change the AWRKHISSUI workflow history table that gets updated with the purchase orders one.

I can see there are several actions on the POHSIG/POHSIGVAL workflows however I can't see the code behind what those actions are doing when jumping through to them.

Cheers

In the standard PO signature workflow, when a PO is changed before it's signed, it triggers the DIVPOHAPP1 action. I think it maybe a good place to look into.