As Kerstin said, there is line review and header review. We have had a requirement as well on multiple clients to check the line information and either route or change the approval path based on line information. We have found that anytime you set a condition that includes line information on the header review workflow, it only looks at one line (usually the first during our testing). Therefore, you really need a line level workflow to test each line - unfortunately, that means that an approval needs to happen on every single line.
Since we didn't want that, we were able to use header workflow and policies at one client (purchase requisition expenditure reviewers) to check dimension information. For another client, we used line item workflow and a customization that approved multiple lines at a time. We had the same code in 2012 and also had to create the mobile app to do the same thing, so it made sense to go that direction.
I have heard that in the future, the multiple line approvals will be incorporated into the product, but that is not a confirmed item or included in any release information - hopefully that is the case as this is a common request.
------------------------------
Shirley Adams
Solution Architect
AKA Enterprise Solutions
New York NY
------------------------------
Original Message:
Sent: Jul 23, 2019 05:05 PM
From: Jeff Retzak
Subject: Purchase Requisition workflow
I have set one of my conditional decisions to be 'Yes or no, line.Net Amount<$5000'. It works well with a single line req, but if for example line 1 of the req is $10k and line 2 is $50.00, the purch req. will require no approval. This is bad. Has anyone else experienced this? I am hopeful I can make it work so it will catch any line that is greater than $5k.
Thanks everybody
------------------------------
Jeff Retzak
Stella and Chewys
Oak Creek WI
------------------------------