Use Seeded Content Workflows

You can download a QuickStartApplication package through Oracle Content and Experience and import it into Oracle Integration for simple multi-step content approval workflows to use in Oracle Content and Experience.

To download the OCE QuickStartApplication package:

  1. In Oracle Content and Experience, click Content in the side navigation and select Content Workflows from the banner menu.
  2. Click OCE QuickStartApplication to download the file.
  3. Unzip the downloaded package to access the included applications.

After downloading and unzipping the QuickStartApplication package, you must go to Oracle Integration to import an application for use with Oracle Content and Experience. Several applications are available, including one-step, two-step, and three-step content approval workflows.

After importing the application into Oracle Integration, you'll need to configure it with the Oracle Content and Experience URL and add your Oracle Content and Experience user name and password with a content administrator role to the Oracle Integration managed credentials to create a keystore. You'll use this keystore when you activate the application in Oracle Integration for use in Oracle Content and Experience.

Example Content Approval Workflows

The QuickStartApplication package has several multi-step content approval workflows that you can edit or use as-is once they are activated in Oracle Integration. Here are some example use cases:

One-Step Content Approval Workflow Example

A one-step content approval workflow is a simple workflow where an author submits a draft for review (step 1) and the reviewer can approve, reject, or request changes. If the reviewer requests changes, then the changes are made and the author re-submits to start the workflow process again.

One-Step Workflow QuickStart

Two-Step Content Approval Workflow Example with Single Change Request Option

A two-step content approval workflow adds an additional approval layer where an author submits a draft for review and the reviewer can request changes or pass it along for final approval. For example, let's say that all items must be approved by the legal department for final approval. An author can submit their draft to an editor for approval (step one), who can request changes (restarting step one) or approve it and submit it to the legal department for final approval (step 2). The legal department can then approve it, or return the item to the author and request changes, starting the process again.

Two-Step Workflow A

Two-Step Content Approval Workflow Example with Multiple Change Request Option

A two-step content approval workflow can shorten change requests by adding some complexity. For example, an author can submit their draft to an editor for approval (step one), who can request changes (restarting step one) or approve it and submit it to the legal department for final approval (step 2). By adding the option for the legal department to request changes from the editor rather than just the author, the workflow doesn't necessarily need to be re-started, potentially shortening the approval time.

Two-step Workflow B

Three-Step Content Approval Workflow Example with Single Change Request Option

A three-step content approval workflow adds an additional approval layer. For example, let's say that all items must be approved by the legal department but then final approval must come from the compliance department. An author can submit their draft to an editor for approval (step 1), who can request changes (restarting step 1) or approve it and submit it to the legal department for approval (step 2). The legal department can then return the item to the author and request changes, starting the process again, or pass it to the compliance department (step 3). The compliance department can then request changes from the author (restarting the process), or approve it.

Three-step Content Workflow A

Three-Step Content Approval Workflow Example with Multiple Change Request Option

A three-step content approval workflow can shorten change requests by adding some complexity. For example, an author can submit their draft to an editor for approval (step 1), who can request changes (restarting step 1) or approve it and submit it to the legal department for approval (step 2). The legal department can then return the item to the author for changes (restarting the process). However, by adding the option to request changes directly from the editor, the legal department doesn't have to restart the workflow, which can shorten the process. Once the legal department approves it, the item is passed to the compliance department (step 3). The compliance department can then request changes from the author (restarting the process), or shorten the process by requesting changes from either the editor or legal department, and finally, approving it.

Three-step Content Workflow B