- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-09-2020 11:14 AM
I am working on a new catalog item that has some approvals in the workflow. One of the requirements is that if it is rejected for a specific reason the requestor is notified and asked to provide additional information. If it is rejected for a different reason the the request is just closed out and the requestor is notified.
Can anyone help with a way to add to the approval task a way to add rejection reasons as a choice instead of just typing a reason in the comments. I then need to make sure that the workflow can continue if rejection reason is a then do this. If rejection reason is b then do this.
Thanks in advance!
Donald
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-09-2020 11:36 AM
This is just a brainstorm of some stuff I've seen/done in the past, someone may have a more eloquent solution to this.
If it's just for one item at the moment (which can be scaled to other items later on) it might be better to put a rejection reason variable on the catalog item itself, and only show it on RITM/SCTask or wherever it's needed. The workflow can then key off that variable and we don't have to put anything on the Approval form for this. A custom UI Action (with conditions to only show on this catalog item) can be created on the Approval form that could pop up a UI Page asking for the Rejection Reason and/or any comments they may have. This UI Page could set the variable on the associated RITM and any other fields on the approval record. The OOTB Reject UI action would need to have it's conditions altered to not show for this particular catalog item. This is coming from the perspective that the user would mainly be doing this in the desktop, as some other solutions such as showing a Modal widget would be needed for Portal.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-09-2020 11:23 AM
Will the rejection reason be across all approvals, or just approvals for this particular catalog item(s)?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-09-2020 11:29 AM
Hi Ashley,
Good question, and I'm sorry I forgot to put that important piece of information in the details. This would only be for this particular catalog item.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-09-2020 11:36 AM
This is just a brainstorm of some stuff I've seen/done in the past, someone may have a more eloquent solution to this.
If it's just for one item at the moment (which can be scaled to other items later on) it might be better to put a rejection reason variable on the catalog item itself, and only show it on RITM/SCTask or wherever it's needed. The workflow can then key off that variable and we don't have to put anything on the Approval form for this. A custom UI Action (with conditions to only show on this catalog item) can be created on the Approval form that could pop up a UI Page asking for the Rejection Reason and/or any comments they may have. This UI Page could set the variable on the associated RITM and any other fields on the approval record. The OOTB Reject UI action would need to have it's conditions altered to not show for this particular catalog item. This is coming from the perspective that the user would mainly be doing this in the desktop, as some other solutions such as showing a Modal widget would be needed for Portal.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-31-2020 03:20 PM
Thank you Ashley. I ended up going with the first option, to put the rejection reason on the catalog item.
