Skip to content

Conversation

@Vishnu-rvk
Copy link
Contributor

PR Description: If we want to have a scenario like based on "Field1" of big list of comma separated values, We need to provide its relevant "Field2" value, Which need not to be repeated again and the key value pair is huge and often changing, In that case we can make use of decision table to fetch key value pair without interrupting any scripts and saving value in "Field2" which will get changed according to "Field1" value as it is a calculated field.

Pull Request Checklist

Overview

  • [ YES ] I have read and understood the CONTRIBUTING.md guidelines
  • [ YES ] My pull request has a descriptive title that accurately reflects the changes
  • [ YES ] I've included only files relevant to the changes described in the PR title and description
  • [ YES ] I've created a new branch in my forked repository for this contribution

Code Quality

  • [ YES ] My code is relevant to ServiceNow developers
  • [ YES ] My code snippets expand meaningfully on official ServiceNow documentation (if applicable)
  • [ YES ] I've tested my code snippets in a ServiceNow environment (where possible)

Repository Structure Compliance

  • [ YES ] I've placed my code snippet(s) in one of the required top-level categories:
    • Core ServiceNow APIs/
    • Server-Side Components/
    • Client-Side Components/
    • Modern Development/
    • Integration/
    • Specialized Areas/
  • [ YES ] I've used appropriate sub-categories within the top-level categories
  • [ YES ] Each code snippet has its own folder with a descriptive name

Documentation

  • [ YES ] I've included a README.md file for each code snippet
  • [ YES ] The README.md includes:
    • Description of the code snippet functionality
    • Usage instructions or examples
    • Any prerequisites or dependencies
    • (Optional) Screenshots or diagrams if helpful

Creating task when button is clicked with the same details added in Incident ticket.
If we want to have a scenario like based on "FieldA" of big list of comma separated values, We need to provide its relevant "FieldB" value, Which need not to be repeated again and the key value pair is huge and often changing, In that case we can make use of decision table to fetch key value pair without interrupting any scripts and saving value in "FieldB" which will get changed according to "FieldA" value as it is a calculated field.
Read me file for calculated field using decision builder
@shreyawani98
Copy link
Contributor

Hi @Vishnu-rvk

Thank you for your contribution.
Could you please remove the third file, ‘CreateTask’, as it doesn’t appear to contain any code?
If it was added intentionally for a specific purpose, please let me know.

Thanks

@Vishnu-rvk
Copy link
Contributor Author

Hi @shreyawani98, The 'CreateTask' was created as part of last year Hacktoberfest, And I'm unsure of how to remove it now, Can you please help me removing it, Thanks.

@shreyawani98
Copy link
Contributor

Hi @Vishnu-rvk

Please refer to the screenshot below for guidance.

Navigate to the Files changed section and scroll to the ‘CreateTask’ file.
Click on the three-dot icon located on the far right of the file, then select Delete from the dropdown menu.

Screenshot 2025-10-07 232711

Thanks

Copy link
Contributor

@earlduque earlduque left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I went ahead and did the changes for you. Looks great. Thank you for doing that contribution. We look forward to seeing more contributions from you.

@earlduque earlduque merged commit 08cbdc7 into ServiceNowDevProgram:main Oct 7, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants