Any action which can have an effect on the rule checking or disclosure process in FundApps is subject to 4 considerations. This article outlines the controls FundApps has to ensure that actions are logged.

1. Is a mistake in doing the action easily preventable?

2. Is the action easily reversible?

3. Is the action visible and searchable in a narrower context?

4. Is the action logged and visible generally?

1. Reject result: FundApps will ask a user for a reason before the rejection is done. This reason/comment is visible in the UI.

2. Deactivate rule: FundApps will ask a user for a reason before deactivating the rule. This reason/comment is visible in the UI.

3. Approve rule: A single click will do this action.

4. Data override: Creating a data override is an involved process, so clicking "Save" is unlikely a mistake.

1. Reject result: A rejected result can be reactivated by clicking "Generate & Disclosure" or "Disclose", thus undoing the reject action.

2. Deactivate rule: A deactivated rule can easily be reactivated.

3. Approve rule: An approved rule version can easily be deactivated.

4. Data override: A data override can easily be deleted or deactivated.

1. Reject result: All rejected results can be filtered in the results screen:

and the audit of actions done:

2. Deactivate rule: All deactivated rules can be seen with a filter:

The record of rule deactivation is present on the Audit Trail page.

3. Approve rule: All approved rules can be seen in one place:

The history of approval and other actions is visible on the individual rule page.

4. Data override: The Last Edited On date is visible on the Data Overrides page.

All actions that modify the application or its users, along with data extraction or uploading, as well as changes affecting rule checking or disclosure processes, are logged to the audit trail (Under "Admin -> Audit Trail").