--- title: "Overview" slug: "overview-5" updated: 2026-08-11T20:49:55Z published: 2026-08-11T20:49:55Z canonical: "help.idibilling.com/overview-5" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.idibilling.com/llms.txt > Use this file to discover all available pages before exploring further. # Overview Access to configuration tools for the elements listed below is via the **CONFIGURE** option on the Workflow menu. **Show Picture** ![UG template for Help](https://cdn.us.document360.io/3f7f8ade-bcb1-4ec8-af25-0c0ad8601afb/Images/Documentation/90516.png?sv=2026-02-06&spr=https&st=2026-11-14T11%3A08%3A12Z&se=2026-11-14T12%3A08%3A12Z&sr=c&sp=r&sig=Yo8AvH1DguO27NXOBnlPMXikDyB47JCdSVnEIebQJkg%3D) | Data Lookups (Smart Data) | Let you for pull in data from a specified object. For example, you can configure a Data Lookup that gets its values from an Order attribute and populates those values as extended data for use in Conditionals and Actions. See [Data Lookups](/v1/docs/data-lookups-smart-data). | | --- | --- | | Definitions | A collection of one or more structured and linked procedures (Steps, Conditionals and Subworkflows), which together realize a business objective or policy goal. See [Business Process Definitions](/v1/docs/business-process-definitions). | | Extended Data Templates | Reusable, shared Extended Data definitions. As an alternative to specifying an ad-hoc Extended Data item which applies only to the Definition where you add it, you can link to a pre-defined Extended Data Template which can be applied wherever you choose to use it. See [Extended Data Templates](/v1/docs/extended-data-templates). | | Field Service Management | Settings for integrating with the Zinier Field Service Management application. See [Field Service Management](https://help.idibilling.com/docs/field-service-management-1) for details. | | Groups | A set of users to which a Task may be assigned. Tasks may also be assigned to individual users. See [Groups](/v1/docs/groups-1). | | Lists | A pre-configured set of data values that may be selected when specifying an Extended Data item or when configuring an Extended Data Template. The system comes with several Global (pre-defined) lists that are fixed and cannot be modified. You can also create additional custom user-defined lists. See [Lists](/v1/docs/lists-1). If you intend to use custom Lists, set them up before you configure A means for pulling in data from a specified object. For example, you can configure a Data Lookup that gets its values from an Order attribute and populates those values as extended data for use in Conditionals and Actions. Extended Data templates and/or Definitions where they will be used. | | Settings | Communications settings support sending Emails from Workflow instances. See [Settings](/v1/docs/settings-5). | | Triggers | Let you pair a system event with a configurable system action. See [Working with Triggers](/v1/docs/working-with-triggers). | | Quicklinks | Facilitate navigation between web modules and other external systems. See [Working with Quicklinks](/v1/docs/working-with-quicklinks). | | Work Order Types | Manage field service requests in the Field Service Management Solution. See See [Work Order Types](/v1/docs/work-order-types) and the [Field Service Management article](https://help.idibilling.com/knowledge-base/field-service-management/) in the IDI Knowledge Center for details. | > [!NOTE] > Note > > Lists, Extended Data and Data Lookups (Smart Data) may be used in building Business Process Definitions. For efficiency, it is recommended (but not required) that you have these elements in place and ready to use before you begin building Business Process Definitions.