- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-03-2020 11:20 AM
Hi,
There is an OOB event named: workflow.notification which triggers a notification when the request is rejected. We have customized notifications for rejection and do not require the OOB one.
I have checked from where this event is getting triggered and get to know that it is used in one of the "Workflow Activity Definition". As this is new for me so, before doing any changes, I want to know how I can stop this and what impact it can have on the instance.
Your help will be really appreciated.
Thanks and Regards
Suresh
Solved! Go to Solution.
- Labels:
-
Request Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2020 12:20 AM
Hi Ashutosh,
Thank you for the information.
I revisited the workflow for RITM, there I saw the OOB notification activity is used and because of which the notification was getting triggered upon rejection. I have removed the notification activity from workflow and now it is working fine.
Not required to deactivate the script action.
Thanks and Regards
Suresh

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-03-2020 01:34 PM
I agree that we should not do that.
We have specific events for specific tables as well. He asked for workflow.notification so i just was trying to explain why and how it works.
We also have approvals events business rule and approval Events Non task BR which should be looked at as well.
if (current.state.changes() && current.state=='requested') {
var event = "approval.inserted";
if (isRequest)
event = "request.approval.inserted";
else if (isSCTask)
event = "sc_task.approval.inserted";
else if (isStdChange)
event = "std_change_proposal.approval.inserted";
gs.eventQueue(event, current, gs.getUserID(), gs.getUserName());
updateTask(current, current.approver.getDisplayValue() + " requested to approve task");
}
This part of the code also tells you a lot.
Thanks,
Ashutosh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2020 12:20 AM
Hi Ashutosh,
Thank you for the information.
I revisited the workflow for RITM, there I saw the OOB notification activity is used and because of which the notification was getting triggered upon rejection. I have removed the notification activity from workflow and now it is working fine.
Not required to deactivate the script action.
Thanks and Regards
Suresh

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2020 12:29 AM
Awesome.
close this thread by marking answer as correct.
Thanks,
Ashutosh

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-03-2020 11:44 AM
Hi,
I want to add one more point that,
Before inactive the check the Notification is triggered for Request only or not. If yes then use Advance Condition of Notification to Inactive this Notification only for Request is rejected.
If not then Active is False for that notification.
Thanks,
Kunal