1. Screen
   
2. Decision
   
3. Action
   

Screen

Display elements

Text

Queries 

KioskRecords

GetRecords

CreatedRecords

Zia Insights

1. Field prediction
   
2. Competitor mentions
   
3. Churn prediction
   
4. Next best experience
   
5. Zia score
   
6. 
7. Recommendation
   
8. Similarity recommender
   
9. 
10. Best time
    

Fields

Buttons 

Note

1. You can add a maximum of 20 fields in a screen.
   
2. You can add a maximum of four buttons per screen.
   
3. The display elements and fields can be rearranged.
   

Kiosk Field 

Kiosk fields groups fields added on screens and fields generated from actions.

Action Fields

Decision   

Action

1. Field Update,
   
2. Assign Owner,
   
3. Tag < Assigning Tags or Removing Tags,
   
4. Email Notifications,
   
5. Add Note,
6. Activities < Add Task, Schedule a Call, or Add Meeting,
   
7. Create records < Predefined Configuration or Via User Input,
   
8. Convert,
   
9. Webhooks,
   
10. Functions,
    
11. Open Record,
    
12. Open Link
    

Create Records 

1. While setting up the Kiosk, select Create Record > Via User Input.
   
2. Enter Action Name, then choose the Module and Layout.
   
3. During execution, the Quick Create layout for the selected module appears.
   
4. There is an option to pre-fill frequently used field values during configuration.
   
5. Now, users can enter details directly while the Kiosk is being executed.
   
6. Note: If a user lacks Create permission for a module, this step is skipped, and related values will show as null.
   

Sequential Action

Note :

1. By default, most actions will have this option automatically enabled. Those actions for which this option needs to be manually enabled are : Activities(Tasks/Calls/Meetings), Create Record, Webhook and Functions.
   
2. If this option is not enabled, the Kiosks will be executed without waiting for actions to be completed and those action responses cannot be used in subsequent screens.
   

Add Failure Path (Optional)

Show a message while the action runs

Note : If a Kiosk is edited and components are updated or deleted, if not resynced the response for actions will not be captured.

Sequential actions with functions and webhooks

For a Function whose response you want to reuse, the sequence is:

1. Write the function so it returns a stringified JSONObject. Build it in the new Function Console so it can return a String.
   
2. Add it as an action in the kiosk and turn on Wait for completion.
   
3. In Argument Mapping, map each argument to a kiosk source with #. This is the run-time input, and it resolves dynamically when the kiosk runs.
   
4. Run the action once in Kiosk with test values to capture the response. These are one-time test values, not the run-time input, and the # picker is not used here.
   
5. In Map Response, map each returned value (result.<key>) to a CRM field, then use those fields in screens, decisions, and later actions.
   

Passing data to a function's arguments  

1. Open the function and click Add Arguments from the right panel to open Argument Mapping.
   
2. For each argument, enter the Argument name.
   
3. Click the value field and type #.
   
4. In the Add Merge Field picker, select the kiosk, select the data source [CurrentRecord, a GetRecords result, a Zia Agent, or a previous Screen] and select the field.
   
5. Repeat for each argument and click save.
   
6. Run a test execution to check if the function works and click Save and Associate.
   

response = {
    "recordId_1": "1234567890",
    "recordId_2": "9876543210"
};
return response.toString();

Test values to map the response 

To generate the fields, the kiosk needs to see a real response, so the action is run once during setup. Clicking Execute on the function action opens the Input Parameters dialog, where you enter an actual test value for each argument, for example a real record ID.

This dialog does not use the # merge-field picker. It is a different step from Argument Mapping:

1. Argument Mapping (with #) defines where each argument's value comes from at run time. These resolve dynamically when the kiosk runs.
   
2. Input Parameters (test values, no #) is a one-time input used only to execute the action during setup, so the kiosk can read the structure of the response.
   

Because a real execution takes place, the dialog notes that the action runs in real time and may create or duplicate data. After you enter the test values and continue, the kiosk runs the action and opens Map Response, where each value appears as a path, for example, result.status that you map to a CRM field type and a label.

Configuring a webhook  

1. Method : the HTTP method, such as POST.
   
2. URL to Notify : the endpoint the kiosk calls.
   
3. Authorization Type : General or Connection.
   
4. Header, Module Parameters, and Custom Parameters : the data sent with the request.
   
5. Body : the request payload and its type.
   

Execution limits and failures  

Example  

1. In Argument Mapping, add an argument for each value the function needs. Map record-based values such as Lead ID to CurrentRecord fields, and user-entered values to the relevant Screen fields, using # in each value field.
   
2. In the function, build the response as a JSONObject and return it as a string, for example {"status":"logged","assessmentId":"..."}.
   
3. Turn on Wait for completion and add a Failure path. If the function errors or exceeds the 10-second limit, the flow follows the Failure path to a screen that asks the user to retry.
   
4. To capture the response as fields, run the action once with test values in the Input Parameters dialog (real values, no #). The kiosk captures the response and opens Map Response, where the values appear as result.status and result.assessmentId; map each to a CRM field type and label.
   
5. At run time, on success the kiosk populates these fields. Add an Action Field on the next screen to display result.status.
   
6. To route the flow based on the value the function returned, add a Decision component that checks result.status. This is separate from the Failure path: the Failure path handles the function failing to run, while the Decision branches on the value a successful function returned
   

Troubleshooting  

1. The response fields are not generated : Confirm the function returns a stringified JSONObject, not an array, and that it was built in the new Function Console.
   
2. The response is not available on the next screen : Map the value in Map Response and reference it by its result. path, such as result.status.
   
3. The action moves to the failure path unexpectedly : Check for an execution error or a run that exceeds the 10-second limit, including socket, thread, or connection timeouts.

Learn more about Functions.

Data in kiosks

CurrentRecords    

1. The record detail view page and
   
2. The module list view page (for each record).
   

GetRecords

1. Single record output: A single record will be displayed to the user. Its field values can be used in subsequent screens, decision criteria, and actios.
   
2. Multi-record output: Multiple records will be fetched based on the criteria you've chosen.
   
1. With single selection: Though multiple records are fetched, the user will be able to select only one record. Its fields can be used everywhere that the single record output's fields are used.
   
2. With multiple selections: These allow the selection of multiple records. The selected records can be used in decision criteria or in email notification templates (In the email template builder, under Table > GetRecords).
   

CreatedRecords

Merge fields

1. GetRecords' fields (CRM record's fields)
   
2. Previous screen's field
   
3. Current record's fields
   
4. CreatedRecord's fields
   
5. A User module field (for data related to the user who's accessing a kiosk)
   
6. Organization fields
   

1. Within screens: Enable Merge from module and press # to pick the field.This allows you to do things like customize your instructions (within the text display element on a screen), display CRM field data for reference, and so on.
   
2. Email templates: When you're creating an email template, you can use merge fields to customize your notification. 

Queries  

1. Screen : Add a query to your screen to retrieve data inputted in previous screens of your Kiosk.
   
2. Decision : Add a query to your criteria component to make decisions from the data retrieved via queries in your screens. Please note that we can add queries to a criteria of a decision component only if it is retrieved in the previous screen of your Kiosk.
   

Add queries to your Kiosk Screen   

1. Click + to add an element.
   
2. Select Screen and click ADD.
   
3. Select Get data via Queries.
   
4. Click New Query.
   
5. Select a query from the list.
     
6. To add a new query, click Add Query and enter the details.
   -- Source : Choose the source from where records need to be retrieved. Either from CRM-Module or CRM-COQL. You can even add your own source.
   
   -- Information : Enter the query name; the API name will automatically be filled. Select the module and related module if needed and choose the fields.
   
   -- Criteria : Enter the criteria based on which the records need to be retrieved.
   
   -- Serializer : Serializer lets you modify your response using JavaScript to use it for further processing. Enter the serializer and click Save.
   
   -- Choose to add Advanced conditions and click Next.
   
7. Once your query is selected, click Next. On the next pop-up, Edit the query name and choose the fields to be retrieved.
   
8. Enter record preferences whether to retrieve single records or multiple records.If the user wants to retrieve a single record, then choose the fields to be displayed and click Save.
   
9. If the user wants to fetch multiple records, then they also have to choose Identifiers. Identifiers are unique fields used to identify any data fetched from multiple records.
   For instance, if a user has fetched multiple records, we can use identifiers to identify each record/ data. i.e to find out what record is used. User has to choose unique field - It can be Lead ID or S No etc.LeadID is the Identifier to fetch Leads data. Enter a selection limit, choose the identifier, choose fields to display, and click Save.
    

Add queries to your Kiosk Decision component
   

1. Click + to add an element.
   
2. Select Decision and click Add conditions based on.
   
3. Select Queries from the dropdown.
   
4. Select a Query from the drop-down, select a criteria, and click Done.
   

Queries Field Limits