Administration Activity Audit

Archer is excited to announce the first phase of Administration Activity Audit is available in 2025.06! 

Launching the Audit Feature for Admin Activities in Archer :

 Audit Feature is now live, enabling tracking of admin-level changes related to data fields,Layout Objects, and Application Properties aimed at providing clear visibility into configuration activities and ensuring governance compliance.

 The Administration Activity Logs report includes actions performed by administrators within the Archer platform. This report captures a detailed timeline of admin interactions, enabling audit teams and system administrators to trace changes, identify trends, and troubleshoot issues more effectively.

Accessing the Report

Just like other Access Control Reports, to access this Report, Administrators must have Read right to the Administration Activity Logs report, through the role "Administration Activity Logs"

The changes can be accessed through a new Access Control Report called Administration Activity Logs. The Report highlights which property was changed, when the change was done, who changed it, what was impacted and in which application

Key Action Types Captured

The report includes the following:

 Action Types

These event types help administrators understand not just what changed, but also how and why those changes impact users and reporting.

Audit Log Columns

 Each log entry provides rich data to support granular audit capabilities:

• Initiating User: Who made the change.
• Date/Time: When the action was taken.
• Application: Where the change occurred.
• Impacted Area: The specific Field and the property name.
• Action Type: What kind of change was made. "To link to the above paragraph"
• Old Value: The original configuration (before the change).
• New Value: The updated configuration (after the change).

Filter Capabilities

 To make the process easier, the report includes the following filters:

• Date Range: Focus on a specific audit period.
• Initiated User: View actions by a particular admin.
• Action Types: Filter by creation, deletion, updates, etc.
• Application: Narrow your results to a specific application.

 These filters enable users to extract only the relevant activity, and reducing search time.

Manual Changes and Package Installations

 Whether an admin manually updates a field via the UI, or changes are introduced as part of a package installation, every action is logged.

Examples include:

• Any time that a calculated field formula was changed. 
• Deleting a field manually within the application.
• Adding a new field as part of a deployed solution package from another environment.

The Description properties in (General Information, and help) are currently excluded from tracking due to their extended text length, ensuring optimal performance and efficiency for the audit feature.

Please be aware that this report is subject to a data retention policy. By default, action log data is retained for a maximum of 3 months. After this period, the data will no longer be available for viewing.

In the case you want to save important data of a specific date before it exceeds the retention policy period, you can export the Report in any format you want from the Export option in the Report page.

What’s Coming Next?

Data Driven Events (Actions and rules) to be tracked as well.

Additional Feature Info 

In addition to accessing the report from Archer UI, the report can also be retrieved through an API endpoint.

 API Description

 Privileges:

This API requires read privileges to the Administration Activity Logs Report, which can be found under the Access Control Reports. 

URL:

localhost/Archer/api/core/system/AdministrationActivityLogsReports/FieldAdministrationActivityLogsReport/

Method:

POST 

Resources:

The resource information for the API is described in the following table.

Request body parameters:

Headers:

Pagination:

The API supports pagination. Each page returns at most 50,000 events. The page number is specified as a query parameter. 

For example, to access the first page, the query parameter should be specified as below:

URL:

localhost/Archer/api/core/system/AdministrationActivityLogsReports/FieldAdministrationActivityLogsReport?page=1

•  The URL without the page parameter always returns the first page of results.
•  The API also returns the HTTP Status code 200. 
• If the request fails, the API issues an exception and returns other HTTP Status Codes.

Example:

Request Header

Content-Type: application/json;odata.metadata=none

Authorization: Archer session-id="session token ID from login"

Accept: application/json,text/html,application/xhtml+xml,application/xml;q=.9,*/*;q=0.8

X-Http-Method-Override: GET

Request Body Example

{

"InitiatingUserId":"2",

"ActionsForDate":"2025-03-20",

"ApplicationId":"635",

"ActionType":"Field Creation"

}

Response Example:

{ 

         "InitiatingUser": "Administrator, System ",

           "ActionType": "Field Deletion",

           "ModuleId": 635,

           "ModuleName": null,

           "FieldName": null,

           "PropertyName": "Search Default",

           "NewValue": "True",

           "OldValue": "False",

           "Timestamp": "2025-03-26T16:33:25.867",

           "UserId": null

     }

Note:

The response to include one day only (the one requested in the body) for better performance.