Tip of the day

Support tickets can be submitted directly from application

Background shape

How Docy works

Learn languages online with the world's best tutors

Background shapeBackground shape

Most requested features of 2020

Orci sapiente illum id phasellus! Harum! Adipisicing ligula aperiam, litora temporibus minim, […]

Can I add videos into sidebars?

Si longus, levis. Primum divisit ineleganter; Vide, quantum, inquam, fallare, Torquate. Sed […]

Theme fails to load to WordPress

The Docly WordPress Theme fails to load into WordPress. My login information […]

Tinkety tonk old fruit victoria sponge squiffy bleeder twit the bee's knees loo David, buggered haggle pear shaped bubble and squeak.”

Mark Tony
Director of Sales and Success

Curabitur vitae dignissimos pulvinar eligendi ullamcorper, laoreet, accusantium numquam habitant quaerat minim consequatur”

Eh Jewel
Software Developer

Hendrerit laoreet incidunt molestie eum placeat, neque ridiculus? Maecenas incididunt aperiam tempora cumque quos?”

Penny Tool
Software Developer

Great Customer
Relationships start here

Publications

View All
Newsletter

Newsletter publications. Read the latest news.

Documentation

Hello and welcome to Cellosign documentation. If you are new to cellosign please check Getting

View All
Getting Started

Hello and welcome, we are happy to introduce

User Application
User Application

The user application is the user's main entry

Release management

Release management is our process to introduce new

Docy Mission

Docy is Documentation webstie for everyone, emphasizing accessibility, performance, security, and ease of use.

The Technology

Learn about the software

The Community

Learn about the people

Docy Video Tutorials

Check the current status of Docy services

Not finding the help you need?

Contact Us

The community team is here to help

Ask Everyone

Hello, what can we help you find?

Publications

Documentation

Hello and welcome to Cellosign documentation. If you are new to cellosign […]

Product Support
  • 5
  • 7
Forums for individual product support topics
Docly Theme Support
  • 12
  • 20
Get support for the Docly WordPress theme

Welcome to Docy Forum

Posts
0
Topics
0
Replies
0
Docly Theme Support

Get support for the Docly WordPress theme

Topic

Test by rubel

<span style="color: rgba(0, 0, 0, 0.8...

1
0

rrrr

rrrrr

1
0

Question about documentation levels

Hello, I would like to ask if it is poss...

0
2
User Feedback

We listed to our customers. Post your feedback in this forum.

Topic

terttdf

dfg dfgd dfgdf  fdgdf gdfgdffg dgd  fg...

1
0

psd and mue

why I can't put question mark❓ ???? ...

1
0

COGUMELOS MÁGICOS E A LEI

  <p style="text-align: center;"...

1
0

Featured Image on Mobile

Hello, The position of featured image...

0
3

Template names

Hi, I have just purchased your template...

0
0
Aprimo Theme Support
  • 8
  • 4
Get support for Aprimo WordPress theme via this forum.
Deksi Theme
  • 5
  • 3
Get support for our upcoming Deski WordPress theme via this forum.
Gullu Theme Support
  • 2
  • 1
Get support for Gullu WordPress theme via this forum.

Popular Posts

Hello, what can we help you find?

Publications

Documentation

Hello and welcome to Cellosign documentation. If you are new to cellosign […]

What are you looking for?

Search here to get answers to your questions

Table of contents

Main course contains 2 parts which cover JavaScript as a programming language and working with a browser. There are also additional series of thematic articles

More resources

App status

Stay up to date on Front’s technical systems and app stability.

New features

Learn about the latest app updates and new feature releases.

For developers

Build integrations and customize Front with powerful APIs.

Outbound: Webhooks

Field change

Estimated reading: 4 minutes 160 views

As a form is being edited by a client you are able to connect data from the form to get or validate data on remote source, such as your CRM. With field change webhook you can easily map and post fields and values from within a live form were to get an answer from your endpoint.

Why do I need this?

This webhook can be very useful when not all data can be exposed in a form but rather need to be fetched or validated as part of business process, such as verify client ID and fetch personal details:

To add field change webhook:

  1. Follow Webhook guide to add new webhook
  2. Find below details for field change body request and expected response
  3. Map fields and define when and how the data connector will act on live form. See below Setting up field change connector

Field change data request and response

Following are definitions for Body request posted from Cellosign to your API

ElementWhat it’s for?
EventObject that includes Event type: WHEF_FORM_FIELD_CHANGED and time stamp
SessionThis object includes details on the session the webhook was fired from. It includes the following elements:
1. “id”: session token
2. “reference”: aggregator ID for business process.
3. “transaction_number”: ID for transaction that can be located in cellosign UI application
4. “recipient”: in case of a workflow this will indicate the recipient id in the process and it’s convention name
5. “labels”: This is a key value object in reference to values injected to labels. See API documentation for details
clientObject that includes basic information regards the browser that webhook was fired form
changeObject that includes the field id, type and value that was triggering the request.
fieldsArray of objects, were each includes the id,type and value of fields that we need to post to the API.

Example post request

Your API can expect this API example for getting information from your API.

{
  "event": {
    "type": "WHEF_FORM_FIELD_CHANGED",
    "timestamp": "2023-06-30T13:35:51.579895"
  },
  "session": {
    "id": "UDi8E55p1O",
    "reference": "19dae31f-377c-44a4-be51-bf3e695dea9d",
    "process_id": "19dae31f-377c-44a4-be51-bf3e695dea9d",
    "process_number": 19,
    "transaction_number": 26,
    "recipient": {
      "id": 1,
      "name": "client"
    },
    "labels": {
      "CUSTOMER_TAG": "CUSTOMER_VALUE"
    }
  },
  "client": {
    "ip": "127.0.0.1",
    "user_agent": "Best browser ever",
    "device": "mobile"
  },
  "change": {
    "id": "myfield",
    "type": "text",
    "value": "new value here"
  },
  "fields": [
    {
      "id": "AccountID",
      "type": "number",
      "value": "999123456"
    },
    {
      "id": "FullName",
      "type": "text",
      "value": "Ron Jerome"
    }
  ]
}

Expected response

A successful response from the API should include array of objects, were each object includes “id” and “value” key/value pairs as in this example. Values will be injected into their corresponding id in a session.

{
  "data": [
    {
      "id": "OrderId",
      "value": "1234-45"
    },
    {
      "id": "OrderStatus",
      "value": "Open"
    }
  ]
}

Setting up field change connector

Follow these steps to apply the webhook into the template:

  1. Login to your template
  2. Select “Integrations” on the top right and then click on “Connectors”
  3. Field change connector can be applied to “LIVE” only. Click “Add Live Connector”
  4. On source, select “Webhook”
  5. On Type: select the your webhook [by alias]
  6. Turn it’s status to “Active”
  7. Define how the connector is trigerred, there are two options:
    • On button click: Select a button from the form that will fire the webhook
    • On change: Select a field from the form that on value change will fire the webhook
  8. Add mapping: Select the fields that will be posted to your API. For each field you have the option to modify it’s convention (alias), this can become handy if your API/DB has diferrent names for these fields. On the response the alias will be preserved to map it back into the form
  9. Save the connector and the template

Leave a Comment

Share this Doc

Field change

Or copy link

CONTENTS