Text and Rich Text
Text and Rich Text attributes capture descriptive business information. They allow users to record names, codes, comments, explanations, instructions, observations, and other contextual details needed to understand and execute a process.
Text Attribute
A Text attribute captures plain-text information. It can be configured as a single-line, multi-line, or long-text field according to the expected length and purpose of the information.
Administrators can provide a default value, prefix, suffix, validation pattern, and validation message. Renderers and editors can also control how the information is presented and entered—for example, as a masked value, email address, hyperlink, or colour value.
Use case: Controlled contact and reference information
A customer or service record may need to capture an email address, external reference number, or contact instruction. The information needs to remain readable and consistent so it can be used reliably by users and related business processes.
A Text attribute named “Customer Email Address” can use an email-oriented editor and validation pattern. If the entered value is not in the required format, the configured validation message guides the user to correct it.
Example: A user enters customer@company without a valid domain. The platform displays the configured message, such as “Enter a valid email address,” and prevents invalid contact information from being retained.
Use case: Work instructions and observations
A multi-line Text attribute named “Technician Observations” can capture concise site notes or operational comments. A long-text configuration can be used when a record requires a detailed narrative, such as a root-cause summary or investigation finding.
Rich Text Attribute
A Rich Text attribute allows users to create formatted content rather than plain text alone. It is designed for information that needs structure, visual emphasis, links, lists, or embedded images.
The demonstrated capability supports formatting such as bold, italic, underline, hyperlinks, font sizing, images, and ordered or unordered lists. This allows users to create readable business content directly within the record.
Use case: Detailed investigation or resolution notes
A quality issue, service ticket, or change request may require a clear record of the issue, investigation performed, corrective actions, and customer-facing resolution. Plain text may be difficult to read when the explanation includes multiple steps, links, images, or supporting details.
A Rich Text attribute named “Resolution Details” can capture a structured response with headings, numbered actions, hyperlinks to related material, and embedded screenshots or images.
Example: A field engineer records the issue summary, lists the actions taken, links a related knowledge-base article, and includes an image showing the completed repair. The reviewer can understand the outcome without opening separate documents.
Use case: Configurable instructions for process participants
A process owner can use a Rich Text attribute to maintain detailed guidance for a task, inspection, approval, or handover. The content can include step-by-step instructions, warnings, formatting, and reference links.