Record Revision History

Introduction

Feature(s)

Record Revision History is used to record the updating history of form data by members.

Application Scenario(s)

In the case of product management, when you modify product information, view updating details through Record Revision History to guarantee the consistency of product data.
In the case of an anonymous survey or evaluation, hide data modification records by disabling Record Revision History to reflect public opinion truthfully.

Preview

For example, in the Employee Information form, after updating the employee's information, you can view details about this update in Manage Data.

Setting Procedure

Enabling Record Revision History

Choose a form and click Edit. Go to Extension > Advanced, and then enable/disable Record Revision History.

Note:
1. Record Revision History is enabled by default.
2. After enabling it, members can view Record Revision History on the details page of one single record through permission sets and Manage Data.
3. After it is disabled, members can view Record Revision History only on the details page of one single record in Manage Data.

Viewing Record Revision History

1. View in permission sets.

After enabling Record Revision History, click the data you want to view in permission sets. On the details page, you can view data updating details in History.

2. View via Manage Data.

On the Manage Data page, click the data you want to view, go to the details page, and view data updating details in History.

Details of Record Revision History

1. Operations available to view.

Under History, you can see the following four types of operations: Create, Edit, Delete, and Recover.

In some scenarios, apart from viewing the above operation types, you can also see the trigger for the operation. Click the link that pops up and jump to the configuration page to see the trigger details.

Note:
Only on the Manage Data page can you see the trigger for the operation on the details page of one single record.

The operation type and the trigger for the operation are displayed according to the following rules:

Operation Type	Scenario Where Operation Type is Displayed	Scenario Where the Trigger is Displayed
Create	When creating form data through the following ways, you will see Create under History: Add data through APIs. Import data through Add Data Only. Add data through Custom Buttons. Add data through Automations. Add data through Sync output table data into forms in Data Factory. Add data through parent workflows.	When creating form data through the following ways, the trigger for the operation will be displayed: Add data through APIs. Import data through Add Data Only. Add data through Automations. Add data through Sync output table data into forms in Data Factory. Add data through parent workflows.
Edit	When editing form data through the following ways, you will see Edit under History: Edit one single record. Edit data in batches. Edit data through APIs. Import data through Update Data Only. Edit data through Automations. Edit data through child workflows. Edit data through plugins.	When editing form data through the following ways, the trigger for the operation will be displayed: Edit data through APIs. Import data through Update Data Only. Edit data through Automations. Edit data through child workflows. Edit data through plugins.
Delete	When deleting form data through the following ways, you will see Delete under History: Delete one single record. Delete data in batches. Delete data through APIs. Delete data through Automations.	When deleting form data through the following ways, the trigger for the operation will be displayed: Delete data through APIs. Delete data through Automations.
Restore	When recovering form data through the following ways, you will see Recover under History: Recover one single record from Data Recycle. Recover data in batches from Data Recycle.	The trigger for the operation is not available.

Note:
For data created, edited, or deleted through the following methods before Ver 6.6.0, the names of Automations and parent/child workflows are displayed as blank in the trigger for the operation.
1. Add, edit, and delete data through Automations.
2. Add data through parent workflows.
3. Edit data through child workflows.
In the above scenarios, the displayed name in the trigger for the operation is the name of Automations or parent/child workflows when adding, editing, or deleting data. That is, it will not update if the name of Automations and parent/child workflows is later modified or the configurations are deleted.

2. Field types available to view.

a. In Record Revision History, the following fields cannot be displayed:

Divider
RelatedQuery

Except for the above fields, all the other fields can be displayed and viewed in Record Revision History.

b. Support viewing subform updating details.

In Record Revision History, you can view the updated details of the subform. You can view the details if there are many updates in the subform.

Note:
If you do not have permission for a certain subform, you cannot view the details in Record Revision History.

Displaying on Mobile

In My App, select a form, click the data you want to view and enter the data detail page. Then you can view data updating details in Data Logs.