Application Builder

application builder is the starting point for building and managing applications with swimlane turbine's application builder you can create and modify fields and layouts set field level permissions and properties append applets to applications configure calculations access, build, and update workflow access reports run manual validations create export templates view revision history delete records associated with an application delete applications application builder is available to any user or administrator of turbine who has permissions set to access applications or a sub set of applications click the icons in the application builder taskbar to jump from the application builder view to workflow and reports page components the application builder page consists of these main components component description field types available fields that you use to build your application the fields support the various input data for the application records form layout the container where you modify the arrangement of fields for your application app settings settings you assign that are relevant to the entire application, such as name, description, roles, and workspaces applet display a list of available applets that you can add to your application field properties settings and properties that you assign for specific fields within the application, such as permissions, size of the field in the layout, values, and whether the field is required hidden fields a list of fields that exist within the application and available for reports and modification in workflow, but that are not visible in the record entry form you control the view of application builder look for the small keyboard icon in the lower left corner of the application click the keyboard icon to open a control panel that contains keyboard shortcuts for controlling the view of the application adjust your view settings, and then click x to close the control panel hidden fields hidden fields are fields that exist within the application and available for reports and modification in workflow, but that are not visible in the record entry form hidden fields are visible at the bottom of the application builder form layout application field limit application builder displays the number of search indexed fields currently used by the application the field counter appears in the format / fields used the counter updates automatically as fields and embedded applets are added or removed the following items count toward the configured field limit counts toward the limit does not count visible fields comments hidden fields history fields from embedded applets (each field counts individually) layout only items such as sections, html blocks, widgets, and playbook buttons when the configured field limit is reached field types that count toward the limit become unavailable if the application contains embedded applets, applet fields and correlation fields may also become unavailable saving the application displays the following validation message maximum number of fields reached you have reached the maximum number of fields for this app please delete some fields to add more remove existing fields or ask your administrator to increase the application field limit under tenant settings > system before saving the application field validation while you build out the forms for your application turbine validates the fields, looking for duplicate fields or empty fields you will see inline checks and pop up error notifications that contain additional detail about the error and how you can resolve it the pop up error notification will lead you through the process of resolving the error and will disappear once you've successfully saved the application here is an example of an inline check for a duplicate field name here is an example of a pop up error notification click the errors, and then the field(s) on the pop up notification to edit and resolve the error(s) application builder also validates the configured application field limit when saving an application if the application exceeds the configured limit, the save operation is blocked until the number of search indexed fields is reduced or the tenant field limit is increased by an administrator