| Oracle® Fusion Middleware Content Management Guide for Oracle WebLogic Portal 10g Release 3 (10.3.4) Part Number E14230-02 |
|
|
View PDF |
| Oracle® Fusion Middleware Content Management Guide for Oracle WebLogic Portal 10g Release 3 (10.3.4) Part Number E14230-02 |
|
|
View PDF |
If you are using a WLP repository that is library services-enabled, you can enforce a workflow process when users add and publish content in the repository. WLP repositories include one default content workflow. You can create additional content workflows or customize content workflows to suit your business needs.
For example, your content workflow can dictate how extensive the review process should be before content can be published in the portal. You can also customize a content workflow so that when content is published, e-mail is sent to an administrator.
Although you can add new workflows to your repository at any time, if you want to use custom workflows, it is recommended that you create workflows for your repository before you create your content types.
Content workflows are only available in WLP repositories that are library services-enabled. For more information about library services, see Chapter 10, "Adding Content to a WLP Repository."
This chapter includes the following sections:
Section 5.3, "Adding the Content Workflow Document to the Repository"
Section 5.4, "Assigning Content Workflows to Folders, Content Types, and Content"
All content created in a library services-enabled WLP repository uses the default content workflow, unless you implement a customized workflow. The default content workflow includes Draft, Ready for Review, Rejected, Published, and Retired states, as shown in Figure 5-1. The default workflow uses delegated administration to prevent or allow users to transition content to different statuses. However, you can visitor entitlements. It is recommended that you use either delegated administration or visitor entitlements, but not both.
Figure 5-1 Default Content Workflow Diagram
Note:
The capabilities you give to a role determines how a user role participates in the content workflow. For example, if a role is not granted the proper capabilities, a user may not be able to transition content to a Published or Retired status.Users choose from available statuses when they check in content within a library services-enabled repository. Figure 5-2 shows an example of the statuses available within the default content workflow.
Figure 5-2 Changing Workflow Status when Checking In Content in the WebLogic Portal Administration Console
Each transition within the default workflow requires different administrative capabilities. For a complete review of all the available Delegated Administration capabilities for Content Management, see "Setting Delegated Administration on Content Management Resources" and "Removing and Editing Delegated Administration on Content Management Resources" in the Oracle Fusion Middleware Security Guide for Oracle WebLogic Portal.
Table 5-1 describes the default content workflow statuses and required Visitor Entitlements or Delegated Administration capabilities for transition to different statuses.
Table 5-1 Default Content Workflow
| Status | Usage Notes | Required Visitor or Delegated Administration Capabilities |
|---|---|---|
|
Draft |
The initial status for all content items. This status is also used to indicate a content item that is a work in progress and not ready for review. Items in Draft status display in the Assigned Items folder for all users whose role includes Edit and Publish capabilities. |
Publish |
|
Ready for Approval |
Marks a content item for ready for review and/or publication to the site. Content items that have the status Ready for Approval can be modified only by content administrators who have publish rights. |
Publish |
|
Published |
Content items that have this status can be accessed by portal content selectors or placeholders according to their content type property values. |
Publish |
|
Rejected |
The Rejected status is used to re-route a content item to the last known user or group to which it was assigned. |
Publish |
|
Retired |
The final status of a content item. This status indicates that a content item is no longer in use. Retired content items cannot be retrieved by a content selector or a placeholder. |
Publish |
|
Deleted |
All versions of the content item are deleted. Only administrators with Delete capabilities can delete content. After deletion content cannot be retrieved by placeholders or content selectors. |
Publish |
Content workflows are XML files that store process information. Once these files are added to your repository, you can associate their defined workflow with content. You create and add content workflows by:
Creating a content workflow document based on the content workflow XML schema. See Section 5.2.1, "Creating or Modifying a Content Workflow Document."
Add the content workflow document to your repository and give it a name. After this document is added to your repository, it is available to associate with content.
When creating content, content folders, or content types, you can associate the named content workflow with the item.
When content contributors add content that uses a content type, the content they create must move through the associated workflow, such as Draft > Ready for Review > Published > Retired.
Using roles in Delegated Administration or Visitor Entitlements, you can allow or prevent users from being able to create and modify content workflows. For detailed information about setting up roles, see "Setting Up Role-Based Authorization" in the Oracle Fusion Middleware Security Guide for Oracle WebLogic Portal.
You can customize your content workflow according to your needs. The following sections contain some examples of customized content workflows:
Section 5.2.1.1, "Guidelines for Creating or Modifying a Content Workflow Document"
Section 5.2.1.3, "Changing the Workflow to use Visitor Entitlements"
Section 5.2.1.4, "Changing the Display Names of the Content Workflow States"
Section 5.2.1.7, "Assigning Different Capabilities for Different Statuses"
Section 5.2.1.9, "Using the Default Workflow Document to Create a New Workflow"
When creating or modifying a content workflow document, keep the following in mind:
Note:
For an explanation about how content items transit through a workflow, see Section 14.1, "Understanding Assigned Items."Include an Undefined Status in a Content Workflow – Include an undefined status in your content workflows to cover situations where statuses do not match, as may happen when migrating workflows. For example, in the default content workflow, content may be designated as Ready for Approval, but in the customized workflow this status does not exist. Instead the new workflow may have two possible statuses: Public and Voting. You can define which status to set when the workflow changes. An undefined transition is indicated by using a value of –1 for the <from-status> and <to-status> elements as shown in Example 5-1.
Status ID Numbers in a Customized Workflow – All statuses within the default content workflow are assigned a number: Draft, 1; Ready for Approval, 2; Rejected, 3; Published, 4; and Retired, 5. Use these numbers with their default assignments. This is especially important for publishing content, in which case you must use the integer (int) 4. The Workflow Action class requires this number for versioning. Use integers 100 – 999 to add new status ID numbers within a customized workflow.
Write Custom Classes to Handle Content – You can write custom classes to associate with various workflow statuses. For example, you could write a class that sends e-mail to administrators when content is ready for approval. You should put any custom workflow actions in the enterprise application's class path (APP-INF/classes) or in the system class path. If the workflow actions are shared across enterprise applications, also put them in the system class path. If your classes do not use anything in content management, you can use only the system class path.
The best way to write a new class is using an EJB or Utility project in Oracle Enterprise Pack for Eclipse. Both of these methods will automatically compile and redeploy the classes as needed and you do not have to add the class to enterprise's class path. You should put any custom workflow actions should in the enterprise application's class path (APP-INF/classes). For information about creating EJB or Utility projects, see Tutorial: Building Enterprise JavaBeans and New Utility Project Wizard.
Until you create and associate custom workflows, all content within your repository (folders, content and content types) use the default workflow.
When you associate workflows with content, the following inheritance rules apply:
Any workflow applied to a folder applies to all content within that folder.
If a workflow is applied to a content type within the folder, that workflow takes precedence over the workflow applied to the folder.
If a workflow is explicitly associated with a content item, that workflow takes precedence to any workflow applied to the folder and to any workflow associated with the content type.
Note:
For content management, you need to use enterprise application-scoped visitor entitlements roles not web application-scoped visitor entitlements roles. For more information about visitor entitlement roles on portal resources, see "Setting Up Role-Based Authorization" in the Oracle Fusion Middleware Security Guide for Oracle WebLogic Portal.To use visitor entitlements instead of delegated administration, in the default Content Workflow Document, change the value of the <capabilityConstraint> elements as shown in Table 5-2. For example:
Delegation Administration: <capabilityConstraint>can_publish</capabilityConstraint>
Visitor Entitlement: <capabilityConstraint>can_vis_publish</capabilityConstraint>
Table 5-2 Delegated Administration versus Visitor Entitlement Values
| Delegated Administration | Visitor Entitlements |
|---|---|
can_create |
can_vis_create |
can_view |
can_vis_view |
can_update |
can_vis_update |
can_reject |
can_vis_reject |
can_delete |
can_vis_delete |
can_associate |
can_vis_associate |
can_publish |
can_vis_publish |
If you want change the name of the workflow status (for example, Figure 5-2), you change the value for the status ID in the default Content Workflow (Example 5-1). For example, change <status id="2" text="Ready" /> to <status id="2" text="Submitted" />.
Tip:
The default content workflow is not internationalized. If you want to create a localized content workflow, the XML elements must remain in English. The values of the elements can be in the localized language. For example, <status id = "3" text="publicado">.To remove a status, you remove the Status ID and any transitions to and from it. For example if you wanted to remove the Retired status from the default Content Workflow (Example 5-1):
Delete the <status id> for the Retired status:
<status id="5" text="Retired" />
Delete the <to-status> elements in each of the other statuses that transition to the Retired status. For example, for the transition from Draft to Retired, delete the XML shown in bold:
<transition>
<from-status id="1"/>
<to-status id="2">
<action class="com.bea.content.virtual.workflow.ReadyAction"/>
</to-status>
<to-status id="4">
<capabilityConstraint>can_publish</capabilityConstraint>
<action class="com.bea.content.virtual.workflow.PublishAction"/>
</to-status>
<to-status id="5">
<capabilityConstraint>can_publish</capabilityConstraint>
<action class="com.bea.content.virtual.workflow.RetireAction"/>
</to-status>
</transition>
Delete the Retired transition:
<transition>
<from-status id="5"/>
<to-status id="1">
<action class="com.bea.content.virtual.workflow.DraftAction"/>
</to-status>
<to-status id="2">
<action class="com.bea.content.virtual.workflow.ReadyAction"/>
</to-status>
<to-status id="4">
<capabilityConstraint>can_publish</capabilityConstraint>
<action class="com.bea.content.virtual.workflow.PublishAction"/>
</to-status>
</transition>
Tip:
Keep the default IDs (1 – 4) for the default statuses. See Section 5.2.1.1, "Guidelines for Creating or Modifying a Content Workflow Document."If you want to change a transition, you must add or remove the transition from the default Workflow Document. Table 5-3 describes the default transitions for each state.
The default workflow does not assign different capabilities for different statuses—every status transition requires can_publish. This means if you designate an article as Ready for Approval, you can also publish it. For your business needs, you may want to change the user role associated with transition from a writer to a publisher.
The capability constants are defined in the com.bea.content.manager.ContentEntitlementHelper class. For more information, see the Oracle Fusion Middleware Java API Reference for Oracle WebLogic Portal. You'll need the values of these constants if you are creating a custom workflow.
There are two ways you can create an action for a workflow:
Write a class that implements the WorkflowAction interface. For more information, see com.bea.content.virtual.workflow.WorkflowAction in the Oracle Fusion Middleware Java API Reference for Oracle WebLogic Portal.
Extend the StandardAction class to your own class. This class defines some methods called assignNodeToRoles and assignNodeToUser that you can use programatically to assign nodes to a particular roles, such as writers and publishers. For more information, see com.bea.content.virtual.workflow.StandardAction in the Oracle Fusion Middleware Java API Reference for Oracle WebLogic Portal.
The easiest way to create a new content workflow document is to use the default content workflow and save it as a new document.
Tip:
Because a workflow affects the entire repository, it is best to play it safe and copy the default workflow to a new workflow, and then apply it to one folder in the repository for testing.To create a new content workflow document by modifying an existing document:
From the main menu of the WebLogic Portal Administration Console, select Content > Content Management.
Select Manage | Repositories.
In the resources tree, click the content workflow you want to copy.
In the Workflow File section of the Details tab, click Download File and choose to Save to Disk. This saves a copy of the content workflow document in the location you specify.
Using an XML editor, make your modifications. For more information about the content workflow XML schema, see Table 5-0.
Note:
An XML editor reads the workflow schema and the schemas the schema imports. It shows you the elements and attributes that can be added to an XML document.When finished, save the content workflow with a new name.
Add the new workflow document to your repository, as described in the next section Section 5.3, "Adding the Content Workflow Document to the Repository."
Example 5-1 shows the default workflow document and Table 5-1 provides information about the content workflow XML schema.
Tip:
Become familiar with the content workflow schema before you create or modify a content workflow document.Example 5-1 Default Content Workflow Document
<?xml version="1.0" encoding="UTF-8"?>
<workflow xmlns="http://schema.workflow.virtual.content.bea.com"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://schema.workflow.virtual.content.bea.com">
<transition>
<from-status id="1"/>
<to-status id="2">
<action class="com.bea.content.virtual.workflow.ReadyAction"/>
</to-status>
<to-status id="4">
<capabilityConstraint>can_publish</capabilityConstraint>
<action class="com.bea.content.virtual.workflow.PublishAction"/>
</to-status>
<to-status id="5">
<capabilityConstraint>can_publish</capabilityConstraint>
<action class="com.bea.content.virtual.workflow.RetireAction"/>
</to-status>
</transition>
<transition>
<from-status id="2">
<capabilityConstraint>can_publish</capabilityConstraint>
</from-status>
<to-status id="3">
<capabilityConstraint>can_publish</capabilityConstraint>
<action class="com.bea.content.virtual.workflow.RejectAction"/>
</to-status>
<to-status id="4">
<capabilityConstraint>can_publish</capabilityConstraint>
<action class="com.bea.content.virtual.workflow.PublishAction"/>
</to-status>
<to-status id="5">
<capabilityConstraint>can_publish</capabilityConstraint>
<action class="com.bea.content.virtual.workflow.RetireAction"/>
</to-status>
</transition>
<transition>
<from-status id="3"/>
<to-status id="1">
<action class="com.bea.content.virtual.workflow.DraftAction"/>
</to-status>
<to-status id="2">
<action class="com.bea.content.virtual.workflow.ReadyAction"/>
</to-status>
</transition>
<transition>
<from-status id="4"/>
<to-status id="1">
<capabilityConstraint>can_publish</capabilityConstraint>
<action class="com.bea.content.virtual.workflow.DraftAction"/>
</to-status>
<to-status id="5">
<capabilityConstraint>can_publish</capabilityConstraint>
<action class="com.bea.content.virtual.workflow.RetireAction"/>
</to-status>
</transition>
<transition>
<from-status id="5"/>
<to-status id="1">
<action class="com.bea.content.virtual.workflow.DraftAction"/>
</to-status>
<to-status id="2">
<action class="com.bea.content.virtual.workflow.ReadyAction"/>
</to-status>
<to-status id="4">
<capabilityConstraint>can_publish</capabilityConstraint>
<action class="com.bea.content.virtual.workflow.PublishAction"/>
</to-status>
</transition>
<!--An undefined transition is indicated by using a value of -1 for the
from-status id. This is used when you change the workflow of a node and
the current status of the node is not a valid from-status in any of the
transitions in this workflow. -->
<transition>
<from-status id="-1"/>
<to-status id="1">
<action class="com.bea.content.virtual.workflow.DraftAction"/>
</to-status>
</transition>
<!--The numbers 1-5 are reserved for use within the default content workflow. As
a best practice, use the numbers 100-999 as status ID numbers within a customized
workflow. -->
<beginStatus id="1" />
<status id="1" text="Draft" />
<status id="2" text="Ready" />
<status id="3" text="Rejected" />
<status id="4" text="Published" />
<status id="5" text="Retired" />
</workflow>
Table 5-4 lists the XML elements of a content workflow document and the considerations for each element. Example 5-2 shows the schema itself.
Table 5-4 XML Elements of Workflow Document
| Workflow XML Element | Usage |
|---|---|
<transition> |
Indicates a workflow transition. |
<from-status> |
Indicates the status from which the transition originates. Note: If you want to include the capability to switch from one workflow to another after the content has been created, you should include an undefined Note: The corresponding |
<to-status> |
Indicates the ending status of the transition. |
<action-class> |
Indicates what action takes place within this transition. The four default action classes are:
You can also create your own custom classes. If you use your own custom class, be sure you add them to the portal enterprise application class path. and/or system class path. See Section 5.2.1.1, "Guidelines for Creating or Modifying a Content Workflow Document." |
<capabilityConstraint> |
Delegated Administration: The syntax for defining a Delegated Administration capability restraint is:
Visitor Entitlements: The syntax for defining a Visitor Entitlement capability is:
|
<roleConstraint> |
Indicates what Visitor Entitlement or Delegated Administration role is required for the transition. Be aware that this role is hard-coded in the workflow document and must be manually changed if the role name changes. |
<beginStatus> |
Indicates which status is the beginning status for new content. The number is an |
<status> |
Defines a status ID. The status ID must have both a display name and a number attributed to the status. Numbers 1 – 5 are reserved for the default workflow and cannot be redefined in custom workflows. |
Example 5-2 Workflow Schema (workflow.xsd)
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema targetNamespace="http://schema.workflow.virtual.content.bea.com" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="http://schema.workflow.virtual.content.bea.com" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:element name="workflow">
<xs:annotation>
<xs:documentation>The content workflow</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="transition" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="from-status">
<xs:complexType>
<xs:sequence>
<xs:element name="capabilityConstraint"
type="xs:string" maxOccurs="unbounded" />
<xs:element name="roleConstraint"
type="xs:string" maxOccurs="unbounded" />
</xs:sequence>
<xs:attribute name="id" type="xs:integer"
use="required"/>
</xs:complexType>
</xs:element>
<xs:element name="to-status" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="action"
maxOccurs="unbounded">
<xs:complexType>
<xs:attribute name="class"
type="xs:string" use="required"/>
</xs:complexType>
</xs:element>
<xs:element name="capabilityConstraint"
type="xs:string" maxOccurs="unbounded" />
<xs:element name="roleConstraint"
type="xs:string" maxOccurs="unbounded" />
</xs:sequence>
<xs:attribute name="id" type="xs:integer"
use="required"/>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="status" maxOccurs="unbounded">
<xs:complexType>
<xs:attribute name="id" type="xs:integer"
use="required" />
<xs:attribute name="text" type="xs:string"
use="required" />
</xs:complexType>
</xs:element>
<xs:element name="beginStatus" maxOccurs="1">
<xs:complexType>
<xs:attribute name="id" type="xs:integer"
use="required" />
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
Content workflows must reside in your repository before you can associate them with content. You do this using the Content Management section of the WebLogic Portal Administration Console.
To create a new content workflow document by modifying an existing document:
To add a content workflow to your repository:
From the main menu of the WebLogic Portal Administration Console, select Content > Content Management.
Select Manage | Repositories.
In the resources tree, select the repository to which you want to add a workflow.
In the Summary tab, click Workflows.
In the Browse Workflows section, click Add Workflow.
In the Add Workflow dialog, enter the name, description, and the XML file for the workflow.
Click Save.
Workflows can be associated with content types or folders. Workflows define the process that content contributors must follow when adding content to a repository.
Note:
If you intend to allow users to change the associated workflow for content, you must include an undefined status within the workflow document, see Section 5.2.1.1, "Guidelines for Creating or Modifying a Content Workflow Document."When a content workflow is associated with a content folder, all content within that folder follows the workflow. If content within the folder uses a content type that is also associated with a content workflow, the content type workflow overrides the folder workflow. You can also change the content workflow for an individual content item. If the content workflow is set at the content item-level, that content workflow overrides any other associated content workflow.
After you have added a content workflow to your repository, you can associate it with a content folder. You can choose to associate content workflows at the folder level, or only with content types.
To associate a content workflow with a folder within the Virtual Content Repository:
From the main menu of the WebLogic Portal Administration Console, select Content > Content Management.
Select Manage | Content.
In the resources tree, click the folder to which you want to associate a content workflow.
Click the Summary tab.
In the Summary tab under Versioning & Workflow, click Check Out.
Click Versioning & Workflow.
In the Update Workflow dialog, select a content workflow from the drop-down list, and then click Update.
Click Check In.
You can also use the Content Management APIs to assign a content workflow to a folder:
com.bea.content.federated.IWorkflowManager.setNodeWorkflow (ContentContext context, ID nodeId, ID workflowId)
For information about the API, see the Oracle Fusion Middleware Java API Reference for Oracle WebLogic Portal.
When you create a content type, you can assign a content workflow to a content type. For instructions on how create a content type, see Section 6.3, "Understanding Content Type Properties."
When a content workflow is associated with a content type, all content of that type uses that workflow. However, users can change the workflow for a particular content item, as described in the next section, Section 5.4.3, "Assigning a Content Workflow to a Content Item."
If you assign a content workflow to a content type other than the WebLogic Portal default workflow, you can use the View Assigned Workflows tab to view which content types use particular workflows. For more information, see Chapter 14, "Managing Content Workflows in Your WLP Repository."
You can also use the Content Management APIs to assign a content workflow to a content type:
com.bea.content.federated.IWorkflowManager.setTypeWorkflow (ContentContext context, ID typeId, ID workflowId)
For information about the API, seethe Oracle Fusion Middleware Java API Reference for Oracle WebLogic Portal.
When content is added to a folder, it is automatically associated with the content workflow associated with that folder or to the content type it uses. For more information, see Section 5.2.1.2, "How Content Workflows Are Inherited." However you can explicitly assign content a content workflow.
If you assign content to a different workflow than the default WebLogic Portal workflow, you can use the View Assigned Workflows tab to view which content types use which particular workflows. For more information about managing workflows, see Chapter 14, "Managing Content Workflows in Your WLP Repository."
To assign a content workflow to a content item:
From the main menu of the WebLogic Portal Administration Console, select Content > Content Management.
Select Manage | Content.
Select the Workspace View.
In the Assigned Items folder, click the content you want to edit.
In the Versioning & Workflow section of the Summary tab, click Check Out.
In the Checked-Out Items folder, select the content you want to edit.
In the Summary tab, click Versioning & Workflow.
In the Update Workflow dialog, select a content workflow to use and click Update.
If finished modifying your content, click Check In.
You can also use the Content Management APIs to assign a content workflow to a content item:
com.bea.content.federated.IWorkflowManager.setNodeWorkflow (ContentContext context, ID nodeId, ID workflowId)
For information about the API, see the Oracle Fusion Middleware Java API Reference for Oracle WebLogic Portal.
|
 Copyright © 2010, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|