Tray Embedded / Core Topics / Config Data / Setting Config Data

Setting Config Data

Please be sure to familiarize yourself with all sections of this page!

General use of project config data

Tray Embedded permits the use of Project Config Data.

This means that you can set Config Data which can be shared between Workflows in the same Projects and Solutions. You could then use, for example, "email-address" and "email-subject" as config data that is shared across multiple Workflows in the same Project (be sure to read the note on Avoiding Project Config Errors).

Project Config Data can be used for two main purposes:

  1. Set default values for the config data which are auto-set in all workflows. For example you wish "email-address" to be set as "" across all workflows. In this case you would set the default value as such, and set it to be hidden in the End User Config wizard so that it is set without the End User needing to know about it.

  2. Make fields available for End Users to set their own values in the End User Configuration Wizard. For example your goal might be for End Users to be able to e.g. set their own email address and over-ride the default value, specify the department they work in, or choose which Salesforce account types they are interested in. Any time you use Config Data in a workflow it will be available in the End User Configuration Wizard for an End User to set their own value, unless you set it to 'hidden' in the Solution Editor.

Creating config data

Prerequisite: Before reading this section, please be sure to look at the simple visual intro to how Config Data is managed on the Embedded Overview page here

In order to actually use Config Data in the workflow editor, you must use a JSON path in the form of $.config.<config-key> (e.g. $

When entering values into a field for any workflow step, you can create / enter config data by selecting convert to config:


You can then set the config key and default value (which can then be overwritten by the End User when they are using the Config Wizard):


This will then be visible in the properties panel:


You can also view and edit Project Config Data in the settings screen found by clicking on the settings wheel in the top-left corner of the screen:


Using config data in Projects and Solutions

When creating a Project you choose what workflows are included in the project:


In the final project creation screen you will see that all of the config set in the selected workflows is pulled in and included as Project Config:


You can subsequently add more Project Config Data in this screen if needed.

Finally, when you are turning your Project into a Solution, you can then set exactly how you present your End Users with the Config Data options in the Solution Editor:

cw configSlot

Importing config data from external sources

If you already have a piece of data about an End User stored in your own external system (for example an email address, their department etc.), it is possible to import this without having to ask them to enter the data again.

This is done by specifying that the Config Data is not visible to End Users in the Solution Editor. Full instructions for this are found on the Importing external data page.