Create and Configure Lists in AUTOMY

AUTOMY lists bring together relevant data from a process or entity in an organized view. In addition to viewing information in rows and columns, you can configure filters, access permissions, and commands so each person can find records and perform the actions they need from the same list.

🧭 Open Lists and organize groups

From the side menu, select Lists. The page displays your lists, groups, and favorites, along with a search field to find items. To create a group or a list, select the + button at the top and choose Add group or Add list.

A group helps organize related lists. When you create one, enter its Name and Description, then select Add. Next, create the list and assign it to that group. A list also requires a name and description; the Order field determines its position within the group. Keeping related lists together can make them easier to find.

🧩 Choose the view and data source

When creating a list, choose the view that best fits the information and the task users need to perform. AUTOMY offers the following display types:

ViewWhen it may be useful
ListView records in rows and columns.
GanttDisplay project or incident information in a Gantt view.
CalendarView reservations or other date-based records in a calendar.
Task list or Task BoardPresent information as a task list or board.
CardsPresent records as cards.
MapLocate records when latitude and longitude are available.

Next, select the Data origin: Process or Dynamic entity. A process-based list retrieves requests from a process. This option may suit a moderate request volume. For high-demand processes, the functional recommendation is to store the required data in a dynamic entity and build the list from that entity; querying an entity can be faster when large amounts of information accumulate. Converting an entity to the premium type may also help when querying entities with large volumes of data.

If you choose Process, select the process that will provide the data. If you choose Dynamic entity, select the entity and, if applicable, the related process. To link entity records to process requests, the entity must include a field that stores the request ID or request name. The entity's Edit mode can be Inline editing or Form editing. A dynamic entity can be related to a process even if you do not select that relationship when creating the list.

⚙️ Configure the initial settings

Default date range determines the period displayed when the list is opened. Options include Today, Yesterday, the last 7, 15, or 30 days, the current week, month, or year, the previous month, the last 3, 6, or 12 months, a custom range, or No restriction. If the list contains many records, a limited period can reduce the amount of data loaded when it opens.

Logical operators are configured for initial filters and permissions. AND requires all combined conditions to be met; OR allows any one of them to be met. For example, use AND if a list should be limited to users who meet several permission criteria simultaneously. Use OR if meeting any one of those criteria is enough.

The Is public? option makes the list visible to all users registered in AUTOMY. If you do not enable it, you can restrict access to users, groups, positions, or areas under Access control. Review the audience before enabling a list that contains information that should not be visible to everyone.

🧱 Create and configure list fields

After creating the list, open it in the builder to define its columns and behavior. You can add fields manually or ask the AI assistant chat in the builder for help. To add a field manually, select Add, provide a display name, and choose the field type. Depending on the data source, select a form field, entity field, or internal process data. The display name can be shorter than the original field name without changing the data being retrieved.

For process-based lists, you can include request data such as process name, process group, instance name, creation date, status, applicant name and details, request ID, approval or rejection date, current step, process variables, comment count, applicant area, or progress percentage. Select only the values that are useful for the user's task.

Field propertyWhat it configures
VisibleShow or hide the column in the list.
FilterableOffer the field as a filter criterion in the list.
SearchableInclude the field in text search.
EditableFor an entity-based list, allow the field to be edited from the list.
Default sorting columnUse the field as the initial sorting column.

You do not need to enable Searchable for every column: text search checks the configured fields, and enabling too many can slow down queries. If users only need to narrow results by a specific value, enable Filterable for that field. In entity-based lists, mark Editable only for data that users should be able to change from the list; enabling an edit command does not make fields editable by itself.

You can also describe the information you want the assistant to display, such as the main data from a form. If the result needs adjustment, ask it to add, remove, or correct fields. Review the generated configuration before using it.

🎛️ Choose the available commands

In the builder, open Commands and select the option to edit their configuration. Enable only the actions that fit the users' work and permissions. Commands available for process-based lists include Create request, View details, Approve request, Reject, Cancel request, Void request, Complete information, Execute task, Sign document, Reassign task, Export, and mass actions such as approve, reject, cancel, or void. Availability depends on the list configuration.

View details opens a request's details from the list; other commands let users start requests or act on selected requests, depending on which commands are enabled. Mass actions apply an operation to multiple selected records; without a mass-action option, users work with individual requests. Export lets users export the data displayed in the list to Excel.

Dynamic entity lists may also provide Add entity, Edit entity, Delete entity, and entity data import commands. Before enabling editing, make sure the relevant fields have the Editable property enabled. Save the command configuration when you are done.

🔎 Apply pre-filters

Pre-filters limit which records are displayed by default so the list fits a specific need. In the builder, open Pre-Filters, select the edit option, add a filter, and choose its type. The section's logical operator determines whether all conditions must be met (AND) or any one condition is enough (OR).

Pre-filterRecords it can display
My requestsRequests created by the person viewing the list.
Instance statusRequests by status: approved, rejected, canceled, voided, or running.
Form field valueRequests matching the selected value in a form field.
Pending requestsRequests pending for the user.
Pending complete information or Pending approvalsRequests waiting for information to be completed or for approval.
Other process criteriaYou can also filter by tasks pending execution or signing, user interactions, variable value, a value related to a user, start mode, action identifier, or action type.

For example, an Instance status pre-filter can create a view focused on approved requests. A form field value filter can limit records to a selected document type. Configure the conditions the list needs without combining criteria that should work independently.

🔐 Set access control

If the list is not public, open Access control in the builder and add the people or groups who should be able to view it. You can assign access to users, user groups, positions, and areas. The operators between sections and between groups determine how conditions are combined; choose AND when all conditions must be met, or OR when any one condition is enough. Save the changes to apply the access configuration.

🧾 Review traces and publish the list

The Traces section lets you track operations performed on the list. The log includes information such as date, version, operation, user, and associated data. You can check who used a command and when; open a trace's details to review the available information about that operation, such as an export.

When you finish configuring the list, select Publish. After publication is complete, AUTOMY displays a confirmation. Then, under Data, you can view the list with its configured columns, view, and filters. A list supports up to 35 columns; the system will not allow you to add a 36th column. Keep the columns focused on information that helps people continue their work or make decisions.

💡 Tips and recommendations

  • If the list contains many records, choose an appropriate default date range to avoid loading unnecessary information when it opens.
  • Enable search only for columns users actually need to search; use filters to narrow results by specific fields.
  • Choose a view that fits the data: Calendar for dates, Gantt for projects or incidents, and Map when latitude and longitude are available.
  • Before enabling mass commands, decide whether users need to act on several selected records or work one request at a time.
  • For entity lists, limit editing to fields users should change and make sure those fields are configured as editable.

❓ Frequently asked questions

When should I use a process list versus a dynamic entity?

A process list retrieves requests from a process and may be appropriate for a moderate request volume. For high-demand processes, the recommendation is to store the required data in an entity and build the list from that entity.

You can select a related process when creating the list. The entity must have a field that stores the request ID or name to link its records to process requests.

What is the difference between a filterable and a searchable field?

A filterable field is offered as a criterion for narrowing the list. A searchable field is included in text search. Enable search only for the columns users need to avoid slower queries.

Why can't a field be edited from an entity list?

To edit data from the list, the field must have the Editable property enabled. Enabling the entity edit command does not replace this field-level setting.

What happens if the list has more than 35 columns?

A list supports up to 35 columns and does not allow a 36th column. Choose the columns that provide useful information for the task and leave out data that is not needed in that view.

With a suitable view, carefully selected fields, and access and commands aligned with the task, a list makes it easier to view information and take action in one place.

Put this into production with AUTOMY

Ready to put it into practice?

Book a demo and we will help you automate your processes with AUTOMY.

Book a meeting