Bulk actions reduce repetition, but they also increase the consequences of a selection mistake.
Current documentation describes workflows that can operate on a single card or multiple selected cards, including documented activation processes.
Selection is the first control
Before a bulk action:
- confirm the active account context;
- define the target population;
- review the search criteria;
- verify the selected cards;
- confirm the intended result.
Treat the action as a change event
The larger the number of affected cards, the more useful it is to record:
- the purpose;
- the scope;
- the responsible person;
- the expected result;
- the date and time of the action.
Verify after the action
Do not assume a successful submission proves that the entire operational objective was achieved. Review the resulting card status or other relevant output.
Internal Link Suggestions:
/iconnectdata-card-maintenance//iconnectdata-user-permissions//iconnectdata-operations-routine/