Record and Task Forms
This section explains how forms are designed and configured in Autologyx, and how they support both Object Records and Tasks.
Forms are an important part of the user experience in Catalyst. They control how information is presented, captured, validated, and updated, whether a user is creating a new record, editing an existing one, or completing a task as part of a wider workflow.
This section is most relevant to Config Admins, analysts, and builders who need to design clear, usable forms that work well for end users and support the wider process and data model.
What you will find in this section
Formbuilder Components
Purpose: This area explains the building blocks available in the Catalyst formbuilder.
It includes guidance on the main parts of the formbuilder and the different configuration panels used to shape a form, such as layout, properties, Elements, child Object Classes, and task form fields.
The Form Builder
Purpose: This area focuses on designing effective forms, especially where users need to create new records or enter information in a structured way.
It is particularly useful when working with the Create and edit view, standalone forms, and other form experiences that need to be clear, practical, and easy for users to complete.
Using Conditional Logic in Forms
Purpose: This area explains how to make forms more dynamic by changing what the user sees or can do based on values entered elsewhere in the form.
It also covers the impact of changing or removing fields, columns, and sections that are already being used in conditional logic, which is important when maintaining forms over time.
How this section fits into the wider platform
Record and task forms sit between the platform's underlying configuration and the day-to-day user experience.
They are closely related to:
- Object Classes, which define the structure of the data being captured
- Task Templates, which define how users are asked to complete work
- Standalone Forms, which allow records to be created outside the main logged-in workspace experience
- Create and edit view, which controls how users create and edit records inside the platform
A well-designed form does more than collect information. It helps users understand what is needed, reduces mistakes, and makes the wider process easier to complete.
Suggested path
If you are new to this area, a sensible order is:
- start with Formbuilder Components to understand the building blocks available
- review The Form Builder to understand how form design works in practice
- use Using Conditional Logic in Forms when you need more dynamic behaviour or are maintaining existing form logic
Notes
INFO
This section is about how forms are built and behave in Autologyx, rather than the wider workflow or data model that sits behind them.
TIP
If you are designing a form for end users, think not only about what data is required, but also about clarity, layout, effort to complete, and how the form fits into the wider process.