Configurators

Action configurators

Other offerings within the platform can contribute action configurators, which provide a custom user interface that makes it simple for the application developer to call the action in an application. An action configurator can be provided along side a contributing toolkit, but in a separate project. For example, the Workflow Services toolkit features a startProcess action that wraps a REST API.

You use an action configurator when you configure a nested action. When you select the implementation, you might see a Configure Action button. The button presents a custom UI, where you can easily select all of the required data mapping values.

View configurators

Complex views can require many properties that might be error prone and difficult to discover. As a provider of views, how do you make it easier for the application developer to configure these views?

When you create a view, you can decide which properties you want the person that is building the application to configure by associating the view with a view configurator. For example, you might configure the complex properties and the application developer might configure the properties that set the style and color.

When the application developer selects the view in the low-code designer, a UI is presented with the properties that they can configure for the view instance in the layout.

Template configurators

You can create an application template configurator to help your users when they create an application based on your template. When a user starts to create an application based on your template from Business Automation Studio, a wizard is displayed for the initial configurations. You can add one or more pages to that wizard for configurations that are specific to your application.

For more information on setting up template configurators for your applications, see Application template configurator extension .