DPO Radio

Workflow Packages

Overview Image

Why It Matters

Teams often need the same review across operating environments. A versioned package helps them carry the reviewed procedure and its dependencies with it.

Use the package version and dependency information when reusing a review. The receiving team can check the import before people start relying on its output.

Find the imported copy among your own workflows.

How It Works

Export a workflow or bundle

Take an eligible workflow or bundle with its version and declared dependencies.

Validate the package

Review findings for format and unresolved citations before importing.

Import a user-owned copy

Import the reviewed package into the appropriate workspace as a user-owned workflow.

Check framework and tier requirements

Verify the workspace provides the required frameworks and the person has the applicable permissions.

Find approved add-ons

Use the Add-ons catalogue alongside built-in and user workflows and review the package version.

The Difference

Graphic Image

Without Workflow Packages

Graphic Image

With Forseti Workflow Packages

IconThe receiving team must rebuild the workflow from screenshots or notes.
IconExport a workflow or bundle.
IconBroken references can surface only after someone runs the workflow.
IconValidate the package.
IconCopying settings by hand can create an untracked variant.
IconImport a user-owned copy.
IconA workflow may be shared into an environment that cannot run it.
IconCheck framework and tier requirements.
IconThe team may have no clear way to distinguish managed add-ons from local copies.
IconFind approved add-ons.

Built for Workflow Packages

Build For Image

See a package version and its required frameworks.

Build For Image

Identify a reference that blocks an import.

Build For Image

Find the imported copy among your own workflows.

Background Image

See Workflow Packages in Action

See a package version and its required frameworks.

Demo Image
Ronni K. Gothard Christiansen

Ronni K. Gothard Christiansen - Technical Privacy Engineer & CEO

Technical Compliance Expert, 32+ Years Open Source Advocate, X-BoD Open Source Matters Inc.

Or contact via

ronni@aesirx.io+84 909 500 760

Next Steps

Icon Image

Start a pilot

Start a pilot using a built-in, add-on or user-owned workflow.

Icon Image

Talk to us

Talk to us about how workflow packages fits your team's work.

Frequently Asked Questions

Yes. Packages and bundles have a version, and the import checks their format and references.

Imports create or update user-owned copies. The catalogue's built-ins remain managed by ComplianceOne.

The workflow still depends on the installed frameworks and capability checks declared for it.

The package and add-on features are available on Standard and Enterprise to people with the appropriate access.

A workflow package carries its reusable definition and supported assets. An organisation exit export is a separate request.