Disable LN DA workflow on specific condition

Legacy Contributor

Hi All,

I am using LN OCM module for the Workflows, I have a requirement to disable the workflow on a particular condition.

Ex: if the purchase order type is equals to "S02" then workflow should not trigger.

Thanks

Gaurav

Find more posts tagged with

ION Connect

Accepted answers

All comments

Legacy Contributor

Hi Gaurav,

I think there is no possibility to deactivate an LN Workflow. But as workaround you could design the workflow that it is automatically approved by your condition. Means,if purchase order type is equal to "S02" then the workflow is automatically approved.

regards

Ralf

Legacy Contributor

Yes we also did like that using an empty branch in ION WF even if in other cases it is much better to drive the wf activation from the activation DLL in ocm. You can copy the standard model and link the action to a custom dll that check a cdf on order type also.

Legacy Contributor

Hi Thanks for you r reply but I am following the same approach but my concern is if we can restrict the workflow at LN level so it can not trigger the workflow.

eric-masson

Hello Gaurav,

How is the workflow being triggered? If by an activation policy, could you use a condition that would only allow the workflow to trigger if the PO <> S02? There are some nice options for combined conditions (and/or statements).

I had also been thinking about the use of the 'set parameter' activity in the workflow. That doesn't seem like an appropriate option though, compared to the condition within the activation policy.

Those are some thoughts that came to mind for me. Perhaps they will spark some ideas for you.

Legacy Contributor

Hi Stephanie,

I am using LN Document Authorization workflows which triggers from OCM and I can not see any condition which can restrict the workflow not to be trigger.

Thanks

eric-masson

Sorry, I'm not familiar with LN or for certain that I understand where the workflow is being developed from... which is ok. I was thinking that the modeling of the logic was being done through the use of ION Workflows and Activation Policies would then play a part. If that were the case, here's a quick and dirty example of what I was trying to convey (I used requisition instead of PO but I'm sure you'll get the idea). Through the use of this condition or in combination with additional conditions, I think you'd be able to accomplish what you're after.

I suspect you might be trying to tackle this from another avenue so I'm afraid I won't be much more help. Hopefully there are others on this forum that can chime in though. For my own curiosity, what does OCM represent in this context? (Again, my background is not in LN, rather it's in XA/CSI.)

Legacy Contributor

Hi Gaurav,

Requirement: We are looking to restrict WF triggering at LN level itself on Sales Orders

Did you find a way on how to skip DA WF from being triggered, we have many scenarios in SO wherein it should not be a triggering a DA WF.

I see that we can append the Check out condition for a custom filed in Object Types by copying the standard model, or is there any already tried and tested way exists to achieve this requirement.

Please share your suggestion/ideas from your DA WF implementations.

Thanks in advance !

Rajesh

Copyright © 2025 Infor. All rights reserved.