Hi all,
In RSA IMG v6.9.1 you (forms) can check whether a Pending CR already contains the requested changes.
You are then asked if you want to select the changes to be resubmitted or not.
Is there a way to block/prevent the user from selecting these and do not allow resubmitting the same changes over and over again?
Thank you,
Razvan
Right now there is no way to prevent/block selection on outstanding request page. But there is a setting at request form level named "Check outstanding requests", if unchecked submission will not prompt for outstanding request page.
Hi Shishir,
I am aware of the forms' setting as I mentioned in my post, but that was not my question and we do not want to disable that check/notification.
I was thinking maybe others made some customisations/workarounds to achieve not allowing to resubmit same requests, or filed this as an RFE to which we can add our support.
Thanks,
Razvan
What is the use case here?
Why would you want to block the new request?
Use case:
- User already requested Entitlement "E1".
- Because request was not fulfilled yet/pending approval, he can submit a new request for same "E1" entitlement (lets say after 10 minutes)
- Approvers will get the same request over and over again
Product is trying to avoid this by presenting the "outsanding request" notification BUT user can still tick the checkbox and submit again the same change items.
We want to block it because some users submit the same request several times. (so basically, display that notification but do not allow them to select the item for resubmitting).
Thanks
As I mentioned earlier right now there is no such setting to prevent selection on outstanding page.
As there is no way to prevent raising multiple requests, maybe you can identify in the request workflow that a similar request was raised and then reject the change request.
Or place more meaningful text in the Outstanding Requests page
Or educate the end users
Just a FYI in case you are using web services when raising requests: When using web services, if there are outstanding requests, the system will not create a new CR unless explicitly specified.
The createChangeRequest command is used to create a change request. The command allows a caller to describe the changes to submit.
The request will not be submitted if the proposed changes would create violations (unless this is specifically overridden), or there are any outstanding requests (unless this is specifically overridden), or additional information is required.
Hi Boris Lekumovich ,
Thanks for the feedback:
- some users are hard to educate and client was already instructed to modify the notification text to a more "demanding" and clear version
- we are not using webservices but we do have an approval phase in which we filter out these duplicate requests and reject/cancel them; the idea was to ask if there is something ootb or configurable and not put extra logic in workflows if not necessary
Shishir Choubey thank you for the input, but wanted to leave it a bit more opened as some smart geeks around might have had a surprise answer
Good luck and thanks for your feedback.
As I mentioned earlier right now there is no such setting to prevent selection on outstanding page.