- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-21-2019 09:05 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-21-2019 09:12 PM
Hi,
you can use script actions to create server-side scripts that perform a variety of tasks,
such as modifying a configuration item (CI), or managing failed login attempts. Script actions are triggered by events only.
Script actions. Script actions are server-side JavaScript code that is executed when an event it is listening to is triggered on the specified table. Just like any other server-side script, script actions have access to all the server-side glide APIs,script includes, and other server-side resources.
you can refer below link :
https://www.youtube.com/watch?v=Zo-KT9ASLYQ
after going throw this please mark it as correct/helpfull.
Thankyou.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-21-2019 09:12 PM
Hi,
you can use script actions to create server-side scripts that perform a variety of tasks,
such as modifying a configuration item (CI), or managing failed login attempts. Script actions are triggered by events only.
Script actions. Script actions are server-side JavaScript code that is executed when an event it is listening to is triggered on the specified table. Just like any other server-side script, script actions have access to all the server-side glide APIs,script includes, and other server-side resources.
you can refer below link :
https://www.youtube.com/watch?v=Zo-KT9ASLYQ
after going throw this please mark it as correct/helpfull.
Thankyou.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-21-2019 09:23 PM
Hi keen
Script actions are used to execute any server side scripts asynchronously when an event is triggered. Here are 2 use cases that I can think
1) While performing integrations and you need to send large amount of data/records or attachments to an external system, it cannot be done synchronously as it will affect user experience. In such a scenario, you can call an event from a business rule and trigger the required script in the script action.
2) Suppose you have 200 child incidents tagged to an incident and you need to close all the child incidents when parent is closed. If you follow the Out of box approach, it will create system performance issues as the business rule is executed synchronously. In such a case you can call an event and execute the code for closing 200 child incident in a script action.
check this posthttps://community.servicenow.com/community?id=community_question&sys_id=8131ffa5db269f405ed4a851ca96...
Thanks
Please Hit like, Helpful or Correct depending on the impact of the response
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-21-2019 09:26 PM
Hi,
Script actions are triggered by events and execute server side scripts. You can execute any scripts asynchronously by calling out an event which is linked to a script action. If you need to update or process large number of records, the same can be executed in a script action.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-21-2019 09:48 PM
Hi Keen,
Script actions contain scripts which run when an event occurs like,
- Approval is cancelled
- Change is approved
- Problem is assigned etc.
It can have a condition which must be true for the script to run. These are commonly used to call a script include.
Please go through the link below for more information.
https://community.servicenow.com/community?id=community_question&sys_id=c71ccf25db9cdbc01dcaf3231f96...
Please mark it helpful/correct if you find it appropriate.
Thanks,
Piyush C.