Released in 11.14
Internal modifications tracking - This new feature allows anyone with "support" permissions to check logs of changes made within the system (ie modification of a survey or dashboard) , along with the identification of whom these changes were made by.
This feature was implemented to provide more transparency on actions taken on the platform to ensure more security and moderation.
This feature is not available by default. If you wish to enable it, please contact your customer success representative.
How does It work?
This functionality reads all the change logs in the system, filters them, and replicates this information in the file only when something was modified, changed, created or deleted.
Detailed information is written and stored in a particular file (found in Store>System Source), this file can be visible only to persons who have permissions for this.
Where is the source found?
This file can be downloaded, access can be shared with other people, recoded variables can be applied to the file and it can be visualised in the Visual module.
Visualisation of the Data in Visual
Which information is available in the source?
|Language of the sandsiv+ interface
|Name of the Module
|If the HTTP request operation is related to a specific entity ID in MySQL, then it will be shown in this field; otherwise, it will be an empty string (if the endpoint is related to different entities or none of them, for instance, its goal is to trigger some delayed start of a background task).
|Same as above. If it is possible to determine the actual entity ID, then it will be taken; if not, the name of a particular class or function will be taken instead.
|Always an empty string.
|Human-readable name of the HTTP method: "Creation" (method POST), "Modification" (methods PATCH, PUT), or "Deletion" (method DELETE).
|Raw HTTP request body, if it is present; otherwise, an empty string.
|Raw HTTP response content, that is prepared to be sent.
|Status code of the HTTP response that will be sent (200, 204, 404, 500, etc.).
|A string representing an absolute URL of the endpoint that was requested.
|Time spent between the moment of receiving the client HTTP request (usually it's retrieving the data from the database, calculations, etc.) and before sending a response.
|Date and time in ISO 8601 format, for example, '2023-07-26T14:30:00Z'.
|ID of a user who is logged in on the UI side to make these operations or whose JWT is being used for this HTTP request.
|Username of the user mentioned above.