- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-15-2018 10:15 AM
These are 2 UI Actions that come out-of-box.
When a user clicks on the UI Action - "Request Approval" button I need the UI Action" Check Conflicts" to run and complete before the "Request Approval" UI Action can run.
The reason is simple. Our approvals are based on if there is a conflict or not, so I need to ensure the Conflict Checker ran the exact second before the approvals are going to be generated. I cannot just look to see if conflict ever ran. Conflicts are dynamic so I need to run conflict checker again because it could have been days since the BR ran the checker.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-15-2018 01:26 PM
I combined them into one. Add the Check conflict code within the current Request Approval. It will check for conflicts and if it finds one will return false otherwise continue on normally. I tried it in my personal instance and it worked but needs further testing to ensure that it meets your requirements.
-RC
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-15-2018 01:26 PM
I combined them into one. Add the Check conflict code within the current Request Approval. It will check for conflicts and if it finds one will return false otherwise continue on normally. I tried it in my personal instance and it worked but needs further testing to ensure that it meets your requirements.
-RC
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-18-2018 04:47 AM
Yes, that's exactly what I did.
Seems to be working.
I did add a save/update first in the UI Action because if the user changes any of the values in their GUI needed for the conflict logic it wouldn't be used until its saved first.
