Skip to main content
Version: 1.22.3

Attachment Management

SimpleOne supports attaching files to records. See the Attachments article to learn how to upload, download and delete files attached to a record using the portal or agent interfaces. This article provides information on how to configure various aspects of the system related to attachments:

  • configure attachment actions in the interface.
  • manage attachment records.
  • parsing.
  • monitor the system logs.
  • set the system properties.
  • configure access to attachments.

Attachment in interface

Action and Image field

You can attach files to a field of Image type and a record with the attachment action. The action is displayed on forms as the paper clip icon .

The screenshot below illustrates two attachment actions on the record form:

Attachment widget

Attachments can be added via an attachment widget in the agent interface. For this, you need to use the <attachment> SimpleTag within a certain widget instance. It is unnecessary to specify the recordId, tableName attributes for the <attachment> tag located on the page with the form. Therefore, a widget template with an attachment tag will look like this:

<attachment> </attachment>


After adding a widget instance to a form of the agent interface, the standard action in the top right corner of the form will be removed:

You can add files from the clipboard to the widget directly on the form by using Ctrl+V shortcut while hovering over Drag & drop area.

Attachment record

When you upload a file, a record is created in the Attachment (sys_attachment) table. To reach these records, navigate to AttachmentsAll Attachments.

Attachment record form fields

Document recordNThis field is automatically populated with a reference to the record the file is attached to.
File nameYDisplays the file name.
File pathNDisplays the absolute file path on the server.
Size bytesNDisplays the file size in bytes.
MIME content typeYDisplays the file content type described in the MIME standard.
PublicNSelect this checkbox to make the attachment public.


Parsing attachment content is possible only if the attachment file size does not exceed 30 MB. The limit is fixed and cannot be modified. If the file is bigger than 30 MB, it will not be indexed.


The attachment parsing process is asynchronous. Within this process, the following event is implemented:

  • In the Attachments (sys_attachment) table record, the attachment content parsed from the provided file is placed. The attachment content is populated in the Content field, and the content encoding – in the Encoding field. The content encoding is automatically detected.

Attachment logging

The system logs all operations (except for reading) in the Main Log (sys_log) table. Operations related to attachments have the Source field value equal to Attachment. Navigate to System LogsMain Log to view the log.

If any errors or exceptions occur when adding an attachment, they are recorded in the Exception Log (sys_log_exception). Navigate to System LogsException Log to view these records.

See the System Audit article to learn more.

Configure attachment properties

To set up attachment properties, perform the following steps:

  1. Navigate to System PropertiesAll Properties.
  2. Find the required property record in the list and open it.
  3. Edit the Value field.
  4. Click Save or Save and exit to apply the changes.
max_files_upload_countSpecify the maximum number of files that can be uploaded.
max_file_size_uploadSpecify the maximum file size (in bytes) that can be uploaded.
allowed_upload_file_extensionSpecify the file types that are allowed for uploading. List the extensions separated by commas without spaces, for example, jpeg,png,pdf. Files of other types will be ignored. To allow all types of files, type [].

Access to attachments

The Access Control List (ACL) rules determine whether a certain user or a group can upload, download or delete files attached to a record.


Role required: security_admin.

Restrict access to attachments

  • Attachments can only be uploaded by a user with rights to create records in the Attachment (sys_attachment) table, and with rights to edit records to which they are trying to upload an attachment. To prevent a user from uploading an attachment, set up access control to one of these operations.
  • Attachments can be deleted by a user with rights to delete records from the Attachment (sys_attachment) table, and with rights to edit or delete the record from which they are trying to delete an attachment.
  • Attachments can be downloaded by a user with rights to read the Attachment (sys_attachment) table and the record to which the file is attached.
  • Copying can be done by a user with read access to the table of the record to which the original file is attached, and with edit access to the table in which the copy is being made.

You can supplement the existing access control rules for the Attachment (sys_attachment) table with new rules containing other conditions. New rules should not contradict the existing ones. To do so, complete the steps below:

  1. Navigate to System SecurityAccess Control (ACL).
  2. Click New and fill in the fields.
  3. In the Table field, select the Attachment table.
  4. Click Save or Save and exit to apply the changes.

See the ACL and Role Structure articles to learn more about access limitations.

Restrict access to fields of the Image type

Use the Access Control List (ACL) to restrict operations on Image columns for users with specific roles.

To restrict access, perform the following steps:

  1. Navigate to System SecurityAccess Control (ACL).
  2. Click New and fill in the fields.
  3. In the Column field, select the image column you need to protect.
  4. Click Save or Save and exit to apply the changes.

As a result:

  • Creating, editing, and/or reading columns in a specific table is restricted.
  • The specified rules are applied to the portal forms as well.

The table below describes the effect of the operation restrictions on an image field:

createThe field is hidden on a new record form and appears after the record is saved.
readThe field and its contents (attached files) are hidden.
writeThe field is read-only.