How to define and use "Navigation" to an LPL Form

Stan Thiemann

Context: Infor FSM & HRT process automation.

Navigation & Form.pdf

I'm attempting to apply Inbasket linkback ability that I see in RequisitionApproval to (contract) ChangeOrderApproval.  Wonder if anyone can help me understand the distinction between a Form name and a Navigation in the context of creating a linkback for a workunit (reference URLs component under initiate).  Where are Navigations defined?  I don't see it anywhere in the LPL Form Definition.

attached pdf shows
1. LPL initiating the service/process
2. Form definition
3. Inbasket Related Links screenshots

andy

Are you using a delivered Contract Change Order Approval process or a custom process (e.g. Action Request or explicitly triggered Flow)? There are a couple ways you could accomplish adding a Contract link to a workunit.

A navigation can be a page, list, form or template. You can kind of think it as building the angular route to an endpoint for the context of the current business class instance. They are defined on each business class and you can view them on the "User Interface" tab in the LPL viewer for a given business class. You can also create custom navigations in Config Console.

In the example you provided the PfiViewNavigation is a navigation defined on the Requisition business class to open the form for the current Requisition in context. The linkback function invoked in the LPL contructs that route and adds it as a PfiWorkunitFolder on the workunit instantiated by the LPL that triggers the workunit.

To accomplish adding a link to the Contract on you Change Order Approval workunits, if you are explicitly triggering a flow, you can add a linkback the same way as the example you provided. If no delivered navigation exists for the form you want to use, you can define one.

If you can't modify the underlying LPL that triggers the flow, then you can customize the IPA flow to manually add a PfiWorkunitFolder to the workunit. You will have to construct the route for the Target on the PfiWorkunitFolder, but that is pretty straight forward.