Contributor Data Files in Workflows Native Documents in Workflows

Using Workflows 15-3

15.5 Workflow Examples

It may be useful to use workflow functionality for any the following content items used by Site Studio: ■ Contributor Data Files in Workflows on page 15-3 ■ Native Documents in Workflows on page 15-3 ■ Images in Workflows on page 15-4 These files must contain the appropriate Site Studio metadata to be recognized as part of the Web site. You may decide to enter any one of these content types into workflow, perhaps using a custom metadata field of workflow with values that are recognizable by your organization.

15.5.1 Contributor Data Files in Workflows

Forcing a contributor data file to go through a criteria workflow is the most common workflow process for contributors to the Web site. This file represents the actual content of a web page and is therefore updated with information whenever a contributor edits the web page in Contributor. When you add a contributor data file to a workflow, you are in effect ensuring that any changes contributors make to a contribution region of a Web site go through an approval process before the changes can be posted to the live Web site.

15.5.2 Native Documents in Workflows

Adding a native document to a criteria workflow could be useful in several situations: ■ Inline dynamic conversions ■ Random dynamic conversions ■ Dynamic lists that use dynamically converted documents For native document to be converted to HTML successfully, Dynamic Converter must be installed and running on the content server. Inline Dynamic Conversions It may be useful to add a native document to a criteria workflow if you have an inline dynamic conversion where the document is included in the site layout to ensure that any changes to the native document are subject to an approval process before the document is actually included in the Web site. Random Dynamic Conversions It may be useful to add a native document to a criteria workflow if you have a random dynamic conversion in which a random dynamic converter fragment containing a query is added to the Web site to ensure that any content items checked into the content server do not become part of the site without first going through an approval process. Note: Page templates, subtemplates, region templates, and scripts do not have the opportunity for approvalrejection within workflow if they are edited with Designer. 15-4 Oracle Fusion Middleware Users Guide for Site Studio Designer For example, you could display a randomly selected quote on your Web site through dynamic conversion where every native document added with a quote is included in the site in no particular order. If you place these documents into a criteria workflow, a document is not released until it has gone through the workflow and has been approved. It is then included in the dynamic conversion results and displayed on the Web site. Dynamic Lists That Use Dynamically Converted Documents It may be useful to add a native document to a criteria workflow if you have a dynamic list that targets dynamically converted documents. This enables you to ensure that all native documents checked into the content server that match the dynamic query results go through a workflow before they are added to the dynamic list that is displayed on the Web site. This approach could be useful to display a dynamic list of press releases on your Web site that targets dynamically converted documents.

15.5.3 Images in Workflows