Novell Vibe includes three predefined workflows. One is available for you to enable and use; the others are used within Vibe.
Vibe currently includes the Publish workflow, which is functional as soon as you enable it, as described in Section 11.7, Enabling Workflows.
You can use the Publish workflow in the following ways:
Publish Entries to a Landing Page: You can use the Publish workflow to publish entries to a landing page, without manually modifying the contents of the landing page.
For more information, see Section 6.8, Automatically Displaying the Newest Folder Entries on Your Landing Page.
Keep Entries Private: You can use the Publish workflow to keep entries private until you are ready to publish them for other Vibe users to read.
For example, you can associate the Publish workflow with a certain entry type in a folder (see Section 11.7.1, Enabling Workflows to Start When an Entry Is Created for more information). When you create an entry in the folder, the entry is created as Private. When you are ready for other Vibe users to view the entry, you can change the workflow status to Publish.
To transition the workflow status of an entry from Private to Publish:
Open the entry, and in the
field, select in the drop-down list.Click
.To make the workflow status of the entry Private again:
Open the entry where you want to change the workflow status.
In the Entry toolbar, click
> , then click when you are asked if you really want to stop the workflow.In the Entry toolbar, click
> , then click when you are asked if you really want to start the workflow.The workflow status of the entry is now Private.
Vibe includes two workflows that are used internally.
Vibe uses the Task workflow internally to allow all users who are assigned to a particular task to make modifications to the task, if they are not members of the workspace where the task resides.
This workflow should not be manually added to any workspace or folder.
Vibe uses the Calendar workflow internally to allow all users who are attendees in an event to make modifications to the calendar event, if they are not members of the workspace where the event resides.
This workflow should not be manually added to any workspace or folder.