Updating LN Fields from the LN DA Workflows

Hi All,

I am using LN DA Purchase Order workflow which is working fine, But I have a requirement to update a text fields from the workflow.

I have tried with making that Parameter as an Input/Output but still the same is not reflecting in LN, Can anyone please help me on this.

Regards

Gaurav Gupta

Find more posts tagged with

ION Workflow

Accepted answers

All comments

Legacy Contributor

Hi Gaurav,

You're using a workflow step in your document flow, correct?

What steps have you created in your workflow? It sounds like you've provided an area for a user to enter in some input. Once that step in your workflow is completed, are you doing anything to map this value back up to the PurchaseOrder BOD?

Thanks

Legacy Contributor

Hi Mike,

Thanks for your reply, Let me explain my issue.

I am using the standard PO workflow which provided by Infor(Document Authorization WF), Now only LN PO status getting updated from the WF, But I want to update some text fields in the PO session from the WF.

Thanks

Legacy Contributor

I am in the same position: having a long (6 steps) Requisitoin workflow, I'd like to update some CDF fields to show the status of the approval process.

Did you find a way to solve this?

Thanks,

Adriaan Rijke

This conceptually wrong. The authorization wf is to review the current version of the PO and review and accept or reject it. You should not change it on the fly by updating the text field or any other field. Therefor this is not supported in standard.

Legacy Contributor

I understand your point, but I would like to be able to select all the RDAs of a particular approval step.

This makes sense because the final step gets several tenths of RDA per day. The goal if to have a printout with all the RDA to be approved.

Adriaan Rijke

What means "all the RDAs of a particular approval step"? Do you need options to filter in Mingle on the open tasks?

Legacy Contributor

The Requisitions are subject to 5 approval tasks, according to the requesting department. The last step of the sequence receives tenths per day. What I'd like to have it a CDF on the requisiton showing the actual approval step, thus letting the users have that information. This could be used to create a printout listing the requisitions "to be approved by me" directly from LN.

Legacy Contributor

Hi,

From what we can see - there are two ways to achieve Order authorization (AKA what i wish infor told us before starting requisition/purchase order approvals)

A: LN DA Functionality

This is what I think you are using now. Using the workflow definition - you can easily add fields to pass into the ION workflow, LN automatically 'locks' the order while its waiting, and updates status when it comes back. However - we have seen that its really limited - and only can return 'approved' or a 'reject reason', and not update anything useful.

B: ION Activation policy.

This is the other option that we are starting to migrate to.

TLDR: Activation Policies will reply back to the original BOD if there are any 'output' variables, and can set the Purchase Order status to 'approved', and add the user details.

Detailed:

Turn off DA - set up LN so noone (superuser only) has authorization to approve the purchase order inside LN, only submit
Set up an activation policy in LN to watch for PurchaseOrder BODs with status 'pending'
Workflow with 'input' and 'output' variables
- Put User + "Status" as an input and output - map PurchaseOrder BOD to workflow
Start your authorization workflow - set the various properties (Status / User)
On completion, the Activation policy publishes a Process.PurchaseOrder BOD back to LN with your 'output variables' to the workflow.
If you are wanting to write to a CDF - you can extend the PurchaseOrder BOD inside LN.

Hope this helps!

Adriaan Rijke

@A as explained before. DA workflow behavior in LN is to be used as a formal review. Therefor you can not change anything on the PO, otherwise it is not a review.

@B In case you turn of the DA workflow then also the submit option will be gone. The SyncPO BOD will only be published once the PO is approved. So you need to build the Submit option via extensibility and trigger the BOD from there.

Copyright © 2025 Infor. All rights reserved.