Skip to main content

Celonis Product Documentation

Forms

Orchestration Engine allows you to build highly customizable forms. The forms page is available in the Management Dashboard, under Orchestration Engine. On this page you can:

  • See all the forms that were created in your tenant.

  • Create a new form.

  • Create a form link.

  • Duplicate a form.

  • Remove a form.

forms.png
Prerequisites

To start working with the forms builder, you should get familiar with the basic features and the components that are used there. To learn about the solution, see the Form Building documentation.

Creating a new form

To create a new form:

  1. Navigate to Management Dashboard > Orchestration Engine > Forms.

  2. Click the Create Form button.

  3. Add the name for your new form.

  4. Choose the components that you want to have in the form. You can select from the basicadvancedlayout, and data components. Add the components by using the drag and drop feature, which allows for putting the components at any place, before or after other components.

    forms1.png

    For every component that you add, there's a detailed view with the configuration settings for this specific field in the form. You can customize your component with different values, data or conditions.

    For more details, see the Component Settings documentation.

    forms2.png
  5. To preview the form after you've added all the components, click the Preview Form button.

    forms3.png
  6. When your form is ready and you want to save it, click Save Form.

    The form will appear in the forms page list.

Editing a form

To edit an existing form, click on it in the forms list. The edit mode is opened straight away and you can apply your changes.

If you want to reorder or edit the selected components, you use the inline components settings and adjust the component to your needs.

The form builder is powered by form.io. For more details, see their Inline Component Settings documentation.

Duplicating a form

To duplicate an existing form, click the Duplicate icon.

Duplicated forms are added to the forms list and displayed with the suffix "copy" in the form's name. You can then rename them.

forms6.png
Deleting a form

To delete a form, choose the Delete icon for the selected form. You have to confirm the deletion of the form by entering its name in the confirmation window.

forms7.png
Forms localization

Forms localization makes it possible to translate your forms from the base language to other languages. You can create forms with multiple languages, with the same structure as in the original language but with corresponding fields translated.

Note

The translations should always be prepared before the magic link with the form is sent to the contact.

To set up localization for a form:

  1. Navigate to Management Dashboard > Orchestration Engine > Forms.

  2. Open the form you want to translate.

  3. To start the translation, choose the current language that you use and then click the Download button.

    This downloads myData.json file with the names of the fields. you can also use Download Template, which downloads a .JSON file without the selected language. For example:

    {
      "Text Field": "",
      "Number": "",
      "Password": "",
      "Radio": ""
    }
  4. Open the downloaded .json file and enter the translated text.

    Here's an example of an English to German translation:

    {
      "Text Field": "Textfeld",
      "Number": "Nummer",
      "Password": "Passwort",
      "Radio": "Radio"
    }
  5. Save the file.

  6. Choose Upload Translations to upload the translated .json file back to the form in Management Dashboard.

  7. Choose the translation language and add the .json file.

    translations.png
  8. Choose Save.

Your form is now available in two languages: English (in this case it's the default) and German. Both of the versions are visible in the form preview.

When the form is translated, there's a relevant lang parameter visible in the URL of the form. The parameter can also be used in the mailgun configuration of a Make scenario responsible for sending the forms.

lang_param.png