Skip to content

Conversation

@vijaykumar7177
Copy link
Contributor

PR Description:

Currency conversion and Masking of data in description

Pull Request Checklist

Overview

  • Put an x inside of the square brackets to check each item.
  • I have read and understood the CONTRIBUTING.md guidelines
  • My pull request has a descriptive title that accurately reflects the changes and the description has been filled in above.
  • I've included only files relevant to the changes described in the PR title and description
  • I've created a new branch in my forked repository for this contribution

Code Quality

  • My code is relevant to ServiceNow developers
  • My code snippets expand meaningfully on official ServiceNow documentation (if applicable)
  • I've disclosed use of ES2021 features (if applicable)
  • I've tested my code snippets in a ServiceNow environment (where possible)

Repository Structure Compliance

  • 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/
  • I've used appropriate sub-categories within the top-level categories
  • Each code snippet has its own folder with a descriptive name

Documentation

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

Restrictions

  • My PR does not include XML exports of ServiceNow records
  • My PR does not contain sensitive information (passwords, API keys, tokens)
  • My PR does not include changes that fall outside the described scope

Create Mask Sensitive Data in Descriptions
Automatically replaces sensitive patterns (like credit card numbers) with masked text
…escriptions to Server-Side Components/Business Rules/Mask Sensitive Data in Descript/readme.md

Mask Sensitive Data in Descriptions
Automatically replaces sensitive patterns (like credit card numbers) with masked text
Automatically replaces sensitive patterns (like credit card numbers) with masked text
Mask Sensitive Data in Description Field
Currency conversion
This script automates the conversion of an annual budget value from a selected currency to USD using exchange rates stored in the fx_rate table. It performs the following steps:

Extracts the currency code from the budget_currency field.
Validates the input amount and currency.
Checks if the currency is already USD; if so, it directly stores the amount.
Queries the fx_currency table to confirm the currency exists.
Retrieves the most recent exchange rate for both the selected currency and USD.
Calculates the converted amount using the formula:
USD Amount = (Original Amount / Source Rate) × USD Rate
Stores the result in the u_annual_budget_usd field.
Includes error handling for missing or invalid data.
@github-actions
Copy link

Thank you for your contribution. However, it doesn't comply with our contributing guidelines.

As a reminder, the general requirements (as outlined in the CONTRIBUTING.md file) are the following: follow the folder+subfolder guidelines and include a README.md file explaining what the code snippet does.

Validation errors:

Folder structure violations found:
 - Move 'Server-Side Components/Business Rules/Mask Sensitive Data in Description' under a valid folder hierarchy (Category/Subcategory/Use-Case/your-file). Files directly inside 'Server-Side Components' or its subcategories are not allowed.
 - Move 'Server-Side Components/Business Rules/Readme.md' under a valid folder hierarchy (Category/Subcategory/Use-Case/your-file). Files directly inside 'Server-Side Components' or its subcategories are not allowed.

Review your contribution against the guidelines and make the necessary adjustments. Closing this for now. Once you make additional changes, feel free to re-open this Pull Request or create a new one.

@github-actions github-actions bot closed this Oct 17, 2025
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.

1 participant