ambacti
Explore workflows

BACKUP AND RETENTION · Workflow idea

Keep a recent, organized copy of the processes your team depends on.

Prepare a dated backup of selected process definitions in an approved storage location and keep a clear record of the backup run. The example retains seven days of copies; an administrator should verify the files and recovery process and approve each permanent removal before older backups are deleted.

Make it yours See how it works ↓
A Roman aqueduct taking shape from architectural sketch to marble.
A little structure. A clearer outcome.
Starts with
Selected process definitions
Produces
An organized backup set with a run summary and any proposed removals awaiting administrator approval.
Category
Security

01 / The starting point

A clear request.
A useful direction.

Current process records approved by their owner for backup

“Create a dated backup, confirm its contents and accessibility, and prepare older copies for review under a seven-day retention example.”
An example request · Make it specific to your team.

02 / The work

5 tasks.
One useful outcome.

Helps teams keep recent recoverable copies of important process definitions and make backup status easier to review.

  1. Choose processes for backup

    Confirm which current process definitions are in scope and who owns them.

  2. Create a dated backup set

    Save a separate, clearly dated copy in the approved storage location and keep its contents associated with the run.

  3. Check backup completeness

    Compare the saved files with the selected processes and flag missing, empty, or unreadable copies.

  4. Review the seven-day retention window

    List copies older than the example seven-day period and check whether they are subject to a hold or recovery need.

  5. Approve removal and status sharing

    Have an administrator approve each permanent deletion and approve the exact status notice and recipients before any external message.

03 / The result

Something useful.
Something to build on.

An organized backup set with a run summary and any proposed removals awaiting administrator approval.

AmbactiWorkflow folio · 5 steps

Review and retain process backups

Security · Example outcome

The handoff

An organized backup set with a run summary and any proposed removals awaiting administrator approval.

Keep in mind

A backup may be incomplete, inaccessible, or contain sensitive settings. Restrict access to authorized administrators, test restoration using a safe sample, confirm the agreed seven-day retention rule, and require explicit approval before permanent deletion or any status message is sent externally.

04 / Make it yours

Set the brief.
Set the standard.

A few choices shape the work around your team.

Select process records and storage

Choose the approved processes, destination, and administrators permitted to access the backup copies.

Set a schedule and retention period

Choose when copies are prepared and confirm whether the example seven-day retention period fits recovery needs.

Define restore and deletion approval

Document how restoration is tested, what must be held, and who approves permanent removal.

Test complete, failed, and expired backups

Check successful copies, missing files, recovery steps, and old-copy review before relying on the process.

Put your next idea to work.

Start with your brief. Make the process your own.

Explore more workflows ↗