Every change is versioned
A customer KYC workflow cannot be changed silently. Saving a workflow in Customers → Workflows requires a written reason and creates a new version recording what the workflow contained at that moment, who saved it, and when. Earlier versions are retained unchanged.
This is what lets the institution answer, months later, which checks applied to a customer type on a given date and on whose authority the policy changed. Each run OneView performs records the workflow version it used, so a recorded outcome can be read against the policy in force at the time — see Workflow runs.
The change reason
Reason for this change is a required field in the Configure panel. It accepts between 10 and 1000 characters, and the panel refuses a shorter entry with Give a reason of at least 10 characters.
Write the reason for the person who will read it in an audit, not for yourself today. A useful reason names the
decision and its authority — Board AML policy of 12 March: medium-risk individuals are re-screened quarterly —
rather than restating the change the version already records.
The reason is stored with the version and cannot be edited afterwards.
View the version history
A user needs customers:workflows:history:read. Viewing history is a separate permission from
customers:workflows:manage, so a reviewer can be given oversight of policy changes without being able to make
them.
- Open Customers → Workflows and select the customer type.
- Select Version history on the row you want to inspect.
The panel opens as Band version history and confirms the customer type it covers. It lists one row per saved version:
| Column | Contents |
|---|---|
| Version | The version number, shown as v1, v2, and so on |
| Frequency | The review frequency that version carried, or — for Onboarding |
| Checks | How many KYC checks that version covered |
| Reason | The reason entered when the version was saved |
| Changed by | The user who saved it, or Unknown if that user is no longer identifiable |
| Changed at | The date and time of the save |
Long histories are paged. Each row is displayed exactly as it was stored.
The history is read-only
Nothing in this panel can be edited, and there is no action that removes a version or restores an earlier one. A workflow is changed only by configuring it again, which adds a further version to the top of the history. To return to an earlier configuration, open Configure, reselect the checks and frequency that version used, and record why — the reversal is then itself part of the evidence rather than an erasure of it.
An unedited workflow has no history
Until an administrator saves a change, a workflow shows version 1 and its history panel shows:
No workflow versions — Saved workflow versions will appear here.
This is expected, not a fault. Version 1 is the configuration the installation started with, so there is no authored change to attribute to anyone. History begins at the first saved change, which is recorded as version 2.
If the panel instead shows Version history unavailable, the versions could not be loaded. Close and reopen it, and if it persists follow Troubleshooting.