Get GlideAggregate Count Flow Action #11
Merged
Conversation
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
…specified table based on input conditions, then returns the result as an integer output. It accepts a table name and an encoded query string, executes the count, and makes the value available for use in downstream flow logic. This utility is useful because many flows need to make decisions or trigger actions depending on whether records exist or how many meet a condition. By packaging this into a reusable action, it eliminates the need for repetitive scripting, reduces errors, and gives builders a straightforward way to incorporate record counts into their automation.
Contributor
|
Good job, Earl! :D |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 Flow Action uses a GlideAggregate query to count records from a specified table based on input conditions, then returns the result as an integer output. It accepts a table name and an encoded query string, executes the count, and makes the value available for use in downstream flow logic.
This utility is useful because many flows need to make decisions or trigger actions depending on whether records exist or how many meet a condition. By packaging this into a reusable action, it eliminates the need for repetitive scripting, reduces errors, and gives builders a straightforward way to incorporate record counts into their automation.
closes #4