Glyue User Docs
  • What is Glyue?
  • Tutorials
    • Start Here
    • Building a Single-Step Integration
      • 1. Creating the Integration
      • 2. Calling the External System
      • 3. Running the Integration
      • 4. Crafting the Output
    • Building a Multi-System Integration
      • 1. Connecting to the Core
      • 2. Field Mapping
      • 3. Running the Integration
    • Building an Event-Driven Integration
      • 1. Setting up the Mock CRM
      • 2. Receiving Inbound Requests
      • 3. Triggering the Integration from the CRM
    • Building an Email Integration
      • 1. Create and Configure the Integration
      • 2. Input Validation
      • 3. Get Story IDs from Hacker News
      • 4. Get Story Content
      • 5. Sending the Email
      • 6. Wrapping Up
      • 7. Extra credit
        • extra_credit.json
    • Building a RESTful CRUD Web Service
      • 1. Integration Setup
      • 2. Vault Setup
      • 3. Create Web Service Endpoints
      • 4. Execute Web Service Endpoints with Vault Methods
      • 5. Vault Code Examples and Explanation
    • Building a Retrieval API against FIS CodeConnect
      • 1. Integration Setup
      • 2. Service Request Setup
      • 3. Field Mapping Setup
      • 4. Integration and Service Request Hook Setup
      • 5. Testing the Integration
      • 6. Common Errors
    • What is Pre-Mapping?
      • Before you start
      • Bookmarks
      • Source and Targets
      • Field Mapping Status
      • Field Mapping Comments
      • Summary
  • How-To Guides
    • How to Run an Integration from Glyue
    • How to Invite New Users
    • How to Create a Value Mapping Set
    • How to Build and Deploy a Custom Frontend
    • How to Migrate an Integration
    • How to Set Up Single Sign On (SSO)
      • Glyue Setup
      • JumpCloud Setup
      • Azure Setup
      • Okta Setup
      • Glyue SAML Config Reference
    • How to Install the Glyue App for Zoom Contact Center
    • How to use the Vault
  • Reference
    • Integration Builder Page
    • Integration Anatomy
    • Integration Components
      • Integration
      • Service Request
      • Field Mapping
      • Value Mapping Set
      • Value Mapping
      • Validation Rule
      • Mask
      • Integration Config
      • Integration Engine Versions
    • Integration Lifecycle
    • Special Functions
      • add_run_label
      • callint
      • debug
      • end
      • get_namespace
      • humanize
      • import_helper
      • keep
      • list_files
      • map_value
      • open_glyuefile
      • open_vault
      • Data Manipulation Utilities
      • calladapter
    • Special Variables
      • __adapter_config__
      • input
      • parentint
      • retvalue
      • run_history_id
      • Iterables
        • fitem/fidx
        • sritem/sridx
        • vritem/vridx/vrmsg
    • Adapters
      • Generic HTTP Adapter
      • Email SMTP Adapter
    • Web Service Endpoints
    • Vault Reference
  • Glyue Platform Reference
    • Banking Core Connectivity Guide
    • Authentication
    • Permissions
      • Service Accounts
      • Organizations
    • Frontends
    • Idempotency Layer
    • Integration Scheduler
    • Governance Reports
    • Arbitrary Integration Request Content Support
    • Admin Components
    • Logging
  • ETL
    • Glyue ETL Overview
    • Data Connectors
    • Workflows
    • Run History
    • Scheduler
Powered by GitBook
On this page
  • Parameters
  • integration
  • servicerequest
  • sequence
  • type
  • field
  • apply_if
  • apply_to_each
  • abort_if_not_applied_x_times
  • notes
  • Usage
  • Example:

Was this helpful?

  1. Reference
  2. Integration Components

Mask

Parameters

integration

relationship - required

Integration to apply the mask to.

servicerequest

relationship - optional

Service request to apply the mask to. Only used for types of Response.

sequence

integer - required

Order in which to apply the masks for a given input or response.

type

string - required

[Input, Response] - Specifies which inputs to mask. If type is Response, the service request field must be specified.

field

code - optional

Field to apply mask to. Field has the current context of the associated input, response or the current iterable provided by apply_to_each.

Fields can either use dot-notation or bracket notation to access nested elements

#dot notation
a.n
#bracket notation
["a"]

apply_if

boolean - optional

code field that requires a boolean output.

apply_to_each

iterable - optional

code field that should specify an iterable. apply_to_each resolves prior to apply_if. Once an apply_to_each is applied, the field now has the context of the iterable.

abort_if_not_applied_x_times

integer - required

Forces integration to abort if the mask is not applied at least this many times. If set to 0, this field will be not be applied. By default this is set to zero.

notes

Documentation field.

Usage

Masked Parameters hide the incoming response data or input data to prevent sensitive information from being displayed within internal processes.

SSN Masking

123-45-6789 -> XXXXXXXXX

Example:

Input Payload

{
    "people": [
        {
            "name": "Person 1",
            "age": 42,
            "private_info": "mask this"
        },
        {
            "name": "Person 2",
            "age": 22,
            "private_info": "mask this",
            "key:12": {
                "special": true
            }
        }
    ],
    "top:level:colon": true
}

The following masks the top:level:colon, private_info, and special fields special , in that respecitive order.

Field
abort_if_not_applied
type
apply_to_each
apply_if

["top:level:colon"]

1

INPUT

private_info

2

INPUT

people

["key:12"].special

1

INPUT

people

["key:12"]

Example exported JSON for the above masks:

PreviousValidation RuleNextIntegration Config

Last updated 1 year ago

Was this helpful?

1KB
mask_sample_integration.json