Fetch Active Tasks [incident/case/workorder] for Affected User [caller/contact]#242
Merged
snamjosh merged 2 commits intoServiceNowDevProgram:mainfrom Oct 30, 2025
Conversation
|
✅ Valid PR for ActionPack Thank you for your contribution. This PR complies with the CONTRIBUTING.md. |
snamjosh
requested changes
Oct 29, 2025
Contributor
snamjosh
left a comment
There was a problem hiding this comment.
Thank you for your contribution.
However, can you try using GlideAgreegate API instead of GlideRecord for better performance?
Update your code and let me know.
Contributor
Author
|
@snamjosh |
Contributor
Author
|
@snamjosh |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This Action takes two inputs, User and Task Type (choice: Incident, Case, or Work Order).
It is performed for the affected user, for whom the task is created (the Caller in Incidents or the Contact in Cases).
Based on the selected task type, the script maps it to the corresponding table and reference field (caller_id, contact, or caller).
It then executes a query to fetch all active (non-closed, non-resolved, non-canceled) records associated with that user.
The Action returns two key outputs: