DPR Workpsace - REQ Approval changes to "No longer required" when ordering catalog item
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello,
We have a catalog item (Request new product) that behaves correctly from catalog item - Try it option
REQ Approval is trigerred with "requested" and doesnt change to "No longer required" - One up manager approval
RITM Approvals happen later
However, when same catalog item is ordered from Digital product release workspace (native view)
REQ and RITM are both created
REQ-level sysapproval_approver record is created successfully
But the REQ Approval field automatically changes from Requested -> No longer required
There is one flow to trigger approval on REQ for One-up manager and no other scripts/flows are present
And for RITM Approvals there is a seperate flow
We do have other catalog items with same REQ One-up flow getting trigerred, but only for DPR request the issue is seen.
Is this expected OOTB behavior for DPR Workspace orders?
Is there a supported way to keep REQ-level approval as "Requested"(same as other catalog items).
Thanks in advance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Monday
As per what I understood from your question, You have you own common flows to take care of approval of the request and you do not wish DPR Workspace flow to get fired.
FYI, there is a OOTB shipped subflow which fires whenever a request from DPR workspace is created (even from the 'try it' option in the recent release of DPR).
To stop it working and just relying to your own existing flow, you can disable this business rule >>
DPR auto-approve product request Its on sc_req_item table. This BR internally triggers the auto approval subflow.
Please share feedback if it resolves your issue.
