• JSON is easy for humans to read and write in any text editor. Likewise, since any modern programming language can parse and generate JSON, this format is "programming-language agnostic."
• JSON's lightweight format is a standard to store and transport data between web servers and clients, making it ideal for ProcessMaker to exchange data quickly with third-party data sources such as Application Program Interfaces (APIs). JSON is the "modern language of the Internet."
• JSON's lightweight format is highly scalable to allow large amounts of Request data to accumulate without affecting performance.
• JSON's flexible structure allows Request data be schema-less JSON objects: unique for each Request without adhering to a specific structure.

• how data accumulates in a schema-less JSON data model after a Request starts
• how Request data can be referenced in another point in time of that Request

• Start Event: The Start Event element starts the Request for this Process.
• Task 1: Task 1 represents work for a Request participant. Louis Canera is the user assigned this Task.
• Task 2: Task 2 is assigned to a different Request participant, Jane Lowell.
• End Event: The End Event element ends the Request.

• his full name ("Louis Canera")
• his email address ("[email protected]")
• his preferred salutation ("Mister")

1. 1.

   Locate the Screen control you want to display the Request data from another control (to display that control's content).
2. 2.

   Within that control's content to display the Request data, use mustache syntax both preceding and after the Variable Name setting value of the control to get its content.

Do you know the following person by either of these attributes?

• Name: Mister Louis Canera
• Email address: [email protected]

Do you know the following person by either of these attributes?

• Name: {{ SalutationTask1 }} {{ FullNameTask1 }}
• Email address: {{ EmailAddressTask1 }}

• JSON element key name: The JSON element key name is the Variable Name setting value for a Screen control.
• JSON element value: The value of that JSON element is the information entered into each Screen control. If the JSON element is referenced in another ProcessMaker asset using mustache syntax, the value of that JSON element enters that asset. ProcessMaker assets that can reference Request data include:

  • a Screen control for a different Form Task
  • a Screen control for a Manual Task
  • a Screen for a Collection record
  • a Script​
  • a Data Connector​

• ​JSON Objects​
• ​JSON Arrays​
• ​JSON Dot Notation​
• ​JSON Data Types​

• Opening and closing curly brackets ({ and }) represent the beginning and end of the JSON object, respectively.
• A comma (,) must follow each element except the last element.
• The elements in the JSON object are indented from the curly brackets for easier legibility. The formatting and indention have no effect on how a computer script parses (reads) the JSON.

• Key name: The key name references the information in its object element. The key name is to the left of the colon (:) in each JSON object element. The JSON object element always has double quotation marks (") surrounding the key name. Key names cannot have spaces in them. In the example above, "FullNameTask1" is the key name to reference this JSON object element.

  How You Use This in ProcessMaker:

  In ProcessMaker, when you configure the settings for many Screen controls, a setting called Variable Name is required. This setting is required because the value you enter into the Variable Name setting for a control becomes the key name for that object element in the Request data. In the Request data, use the key name to reference the information in that Screen control.
• Value: The value is to the right of the colon. The value represents the information entered into the Screen control when the Task using that Screen completes. In the example above, "Louis Canera" is the element's value.

  How You Use This in ProcessMaker:

  If the element's key name is referenced in another ProcessMaker asset using mustache syntax (described in Referencing Request Data), the value of that element enters into that asset. Element values require specific syntax based on its data type. Every key name must have a corresponding value. If the element has no value, use null to mean that the element contains no value; JSON elements cannot be undefined, so null defines that element with no value. See JSON Data Types.

• ​the value corresponding with a JSON object element's key name​
• ​a specific value in a JSON array​

• Begin the JSON dot notation with data., which indicates to reference ProcessMaker Request data.
• The JSON dot notation indicates the nested location of the JSON object from which to reference the element's key name. Each nested location is separated by a period (.) to indicate each nested level. In this example, the object element from which to reference its value is not nested.
• In square brackets ([ and ]), indicate from which element key name to reference its value. Therefore, use Headquarters to reference the value corresponding with that element's key name.

• Begin the JSON dot notation with data., which indicates to reference ProcessMaker Request data.
• The JSON dot notation indicates the nested location of the JSON array from which to reference its value. Each nested location is separated by a period (.) to indicate each nested level. In this example, the array from which to reference its value is not nested.
• In square brackets ([ and ]), indicate which value in the array to reference beginning with 0. Therefore, to reference the second value in this array, use 1 in this JSON dot notation.

• Business data has multiple items: The Request data that represents that business information contains multiple items. For example, each item of that business information may have been entered into a Task's Screen or that business data was read from a third-party data source and aggregated into the Request data.
• Each item in that business data contains multiple attributes: Each item in that data contains multiple attributes that describe each item. In the Request data, each item, which is a JSON object, may contain the same object elements that describe each item of the business data.

• Opening and closing curly brackets ({ and }) represent the beginning and end of the JSON object, respectively.
• Opening and closing square brackets ([ and ]) represent the beginning and end of the JSON array, respectively.
• A comma (,) must follow each element in each JSON object except the last element. For example, "CompanyName": "Company" is an element in this JSON object.
• A comma must follow each JSON object in the array except the last object. For example, the following is the first nested JSON object in the Employees array:

• The bracket formatting and indentation are for easier legibility and have no effect on how a computer script parses (reads) the JSON.

• FirstName
• LastName
• Username
• Office
• Email
• Title
• Founder
• YearsAtCompany
• StockOptions