why is DFF value retained when requisition is duplicated
When duplicating a purchase requisition, the DFF value is being retained
The business process has a DFF at requisition header level. This can only be applied as part of the approvals process at the header stage, where a team member who is checking the requisition can apply the DFF to value = Yes to confirm it has been checked. The requester does not have the ability to apply as it is subject to a personalisation to only render if the user has a specific role.
Approval rules were initially built around this value, but due to several instances of users duplicating a requisition the approvals then bypassed the header stage, and went straight to financial approval