Page History

In SimpeOne, a record is the basic entity for storing and representing information. A record is a container (object). It contains filled values of attributes of the table to which it refers.The information contained in the records can have different nature and purpose. It can be user, transactional and historical data as well as configuration data and system settings. For example, there are records containing the information about version configuration.In the agent interface, you can work with a record using either form or list view.

Both users and processes can interact with any record. These interactions are represented by the CRUD (create, read, update, delete) operations.

Each operation is a separate transaction. A transaction is an ordered set of actions that moves a database from one consistent state to another. Consistent state is the expected state of up-to-date information, which is reflected in the database.

Any record has a set of fields that are filled in by the system when creating and/or updating it:

• Record ID.
• Created by, Created at, Updated by, Updated at.
• As part of table inheritance, an attribute of Record Class type intended to identify the table to which a particular record belongs.
• For configuration data records, the Policy and Application fields are mandatory.
• Unique Number is assigned to numbered table records.

In SimpleOne, you can interact with records through user interfaces as well as through various APIs (server, REST).

Create a record

When you create a record, you work with a virtual object. The record does not yet exist until it is sent to the database. When such a record is sent to the database, a transaction is started, the result of which is the appearance of a real record in the database. 

Access control rules (ACL) are triggered before a record is created and when it is required to create a virtual object. They check the user's rights to create records. Then, the fields are filled with default values, and at the time the record is sent to the database, all engines initiated by the transaction are processed. 

Depending on the access control list (ACL) settings, you can restrict access to some users or user groups to execute the CRUD operations.

Create a record

---

You can create a new record via the agent interface in several ways:

Click New 

• Click New on the list view of the

desired

• required table.
  

Click New on the

• Click New in any record form of the

desired

• required table.
  
• Click

the plus icon Image Removedin the Reference fields that refer to the desired

• Create recordin the configuration form of the required table.
  
• Click Image Added next to a reference type field related to the required table.
  
• Fill in the fields

on the previously created record form of the desired table with other values,

• of an existing record with new values and create a copy of the record.

Note

The size of the created record should not exceed 2.5 MB. To download a JSON file with the records that were cut in version 1.19.1, use the following link: https://{storage_domain}/public-attachment/0/0/archive_cut_record.json The information on cut records will also be available in the Main Log (sys_log) table To learn how to create records using the API, see the SimpleRecord or REST API articles .

Read a record

When reading a record, the user of the system is given sees the available content of the record, i.e., attributes and their values.

This operation does not trigger transactions that change the state of a record. Access control rules (ACL) determine whether the entire record, or part of its content, can be read.

Edit a record

Compared to the create operation, when you update a record, you work with a virtual temporary object. Unlike the create operation, the object is populated based on the information contained in the database. In order for information to be added to the database, an update transaction is initiated, for which everything is the same as for the creation transaction, except for creating the record in the database. 

The update operation can be subject to restrictions through access control rules (ACL). Also, the moment of sending a record to the database fulfills all the mechanisms initiated by the transaction. 

Delete a record

When deleting the record information is removed from the database, and at the time of deletion, all engines initiated by the transaction are processed. 

Edit a record

To edit a record via the agent interface, you can either change values in the fields of the record form, or use the inline editing on the list view.

Delete a record

You can delete a record via the agent interface in one of the following ways:

• In the list view of the table containing the record you need to delete:

1. 1. Select the required records using the checkboxes to the left of the list.
   2. Click Delete in the top right corner.

• Select Delete in the burger menu of the form of the record you need to delete.

Unique record ID

Each record in an instance is identified by a unique 18-character ID called sys_id. The record ID must be unique within the same table (including records in parent/child tables). The record ID value cannot be changed.

You can find the record ID in the URL address of the record. In the following example, the record ID is 158815469913225806.

https://<instance_url>/record/article/158815469913225806

You can also find the ID of the record in the ID column of the list view.