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
  • servicerequest
  • sequence
  • field
  • value
  • value_type
  • valuemappingset
  • include_if
  • include_for_each
  • nullable
  • message_substitution_name
  • Documentation Fields

Was this helpful?

  1. Reference
  2. Integration Components

Field Mapping

servicerequest

relationship - required

The service request that the field mapping belongs to.

sequence

integer - required

Order in which the field mappings associated with the service request will execute. Note that this does not control the order of fields in the body of the external request — field ordering is arbitrary.

field

string - required

The name of the field in the request body of the service request. Supports lazy-instantiation of intermediate fields. For example, if request body has the shape:

{
    "person": {
        "address": {
            "street": "123 main street",
            "city": "Boston"
        }
    }
}

You can specify the streetfield using person.address.street directly.

value

expression - required

value_type

string - required

Typecast to perform on non-null values. If the value is an expression, the typecast is performed on the result of the expression. Options are:

  • str — String

  • int — Integer

  • float — Floating point number

  • dict — Dictionary (also known as "Object")

Incompatible typecasting (e.g. dict('5.0')) will raise an error at runtime.

valuemappingset

relationship - optional

include_if

expression - optional

An expression to run to determine whether the field mapping should be included in the request. Must return a boolean. Defaults to Trueif left empty.

include_for_each

iterable - optional

Resolves before the include_if block.

nullable

boolean - required

Indicator for whether the value can be be null at runtime. If set to falseand a null value is encountered, the integration will stop execution with an error.

message_substitution_name

string - optional

Replaces the sritem with specified string.

Documentation Fields

  • target_record_type

  • target_field_name

  • source_record_type

  • source_field_name

  • notes

PreviousService RequestNextValue Mapping Set

Last updated 4 months ago

Was this helpful?

The value to associate with a field. Can be a literal value, a reference to value defined elsewhere in the integration, or a code expression. If the expression does not evaluate to a value, the must be used.

The to apply to the value.

Specifies an iterable. Will produce a new field mapping entry on the request for each entry in the iterable. Use and to refer to values in the iterable to differentiate the field mappings.

valuemappingset
retvalue variable
fitem
fidx