Attachment Attribute

An Attachment attribute enables users to upload and retain supporting files directly against a business record. It keeps evidence, documents, images, videos, and other relevant material connected to the process or record they support.

The attribute can be placed on Create, Edit, and View layouts, allowing users to upload files during record creation, while completing work, or during review. Access to uploaded files can be governed through the record’s lifecycle permissions.

Key capabilities

• Capture files in record context Attach documents, images, videos, certificates, reports, drawings, inspection evidence, or other supporting material directly to the relevant business record.

• Restrict allowed file types Administrators can configure file patterns to control which formats the attribute accepts. This ensures each field is used only for its intended purpose.

  For example:

  Attachment purpose	Allowed formats
  Site or inspection photographs	.jpg, .jpeg, .png
  Video evidence	.mp4, .mov, .avi
  Compliance or customer documents	.pdf, .docx, .xlsx
  Technical drawings	.dwg, .dxf, .pdf

• Display a validation message for unsupported files When a user selects a file that does not meet the configured pattern, the platform can show a clear message explaining what is allowed.

  Example: “Only JPG, JPEG, and PNG image files can be uploaded as inspection evidence.”

• Image preview Where image files are uploaded, the attachment can be presented as a visual preview or thumbnail in the record experience. This allows users and reviewers to quickly validate the submitted evidence without downloading every file.

• File-specific attachment fields Multiple Attachment attributes can be configured on the same record, each with a different file restriction. This separates evidence by purpose.

  Example: A field-service ticket can include:

  • Before Service Images — image files only.
  • After Service Images — image files only.
  • Service Report — PDF or DOCX files only.
  • Video Evidence — approved video formats only.

• Lifecycle-based attachment control Configure the process so users can upload or replace files only in relevant lifecycle states. For instance, technicians can upload work evidence while the ticket is In Progress, while reviewers can access it in Submitted or Closed states.

• Use with validation and workflow Attachment presence can be included in business validation. This helps ensure required evidence is available before a record progresses to review, approval, or closure.

Use case: Field-service completion evidence

A field engineer completes an on-site repair and must provide proof of work before the service ticket can be closed.

The ticket contains three attachment attributes:

• Before Service Images — accepts .jpg, .jpeg, and .png.
• After Service Images — accepts .jpg, .jpeg, and .png.
• Service Completion Report — accepts .pdf and .docx.

The engineer uploads photographs before and after the repair. Image previews allow the dispatcher or supervisor to review the evidence directly from the ticket. The engineer also uploads a signed service report.

A validation rule can prevent the ticket from moving to Closed until the required after-service images and service report are available.

Use case: Quality inspection documentation

A quality-inspection record requires several evidence types: product photographs, inspection reports, and, where applicable, a short video of the observed issue.

Separate Attachment attributes can be configured to accept only the permitted formats for each evidence type. This prevents a user from uploading an unrelated document in the image-evidence field or an unsupported file into the record.

The reviewer can use image previews to quickly inspect visual evidence and open supporting reports only when a detailed review is required.