Authoring - Indicating the task transition behavior

By default, you can perform task transitions on any node of a project folder. The result, however, is that the associated data objects are moved asynchronously through the workflow. If too many objects are out of sync, the entire workflow can become confusing, especially when tasks are rejected (moved back in the flow).

To prevent this, the administrator can determine the points where task transitions can be performed. This can be indicated manually in the properties of the existing data objects and for new objects indicated in the class.

Indicating the task transition behavior manually

This approach is used to change the task transition applicability in existing data objects. In the next example, we want to enable only task transitions on the main project folder and its immediate dependants. For any data object lower than the immediate dependants, no task transitions should be possible.

Indicating the task-transition applicability in the properties

Step 1

Select the object for which you want to disable the task transition in the tree and click on the "Properties" tab on the right.

Step 2

Expand the "Workflow" section and select the "Task transition is not possible" option.

Step 3

If the object is a folder, you will have to propagate this action to its dependants.

If you click on the "Edit" tab, you will see that the transition of the task is not possible. However, the object and its dependants are still part of the workflow. The workflow tasks are still applied to these objects. You need to perform the task transition only on the parent folder. 

Task transition is not applicable

Indicating the task transition behavior in the class

To apply the task-transition possibility automatically for new objects, you need to change the class. In the next example, we do this for the "Birds" class.

Opening the Object classes window

Step 1

Pop up the menu of the "Birds" folder and select "Object classes".

The Object classes window

Step 2

Next, click on "Organize folder classes".

The Folder classes window

Step 3

Make sure the "Birds" item is selected in the list and click "Show details".

Changing the task transition behavior in a class

Step 4

Two windows will open. Select the "Folder: Bird" class in the "Added classes" list on the left window to show the class properties in the window on the right.

Step 5

Scroll down on the "Properties" window (right window) until you see the workflow section. Select the "Not applicable" task-transition option.

Repeat steps 4 and 5 to apply this action to the "Folder: FAQ" class.

Step 6

Click "Submit changes" to save and close the two windows.

Task transition will now not be possible for each new "Bird" or "FAQ" folder that is added to the "Birds" folder.

Authoring

 About HelpServer
 Starting up and logging on
 The basic working principles
 Using the content in help and documentation systems
 Formatting the content
 Searching and replacing text
 Reusing content with shares
 Navigating with hyperlinks
 Navigating with pointerpaths
 Using bookmarks and jumps
 Duplicating content with clones
 Using tables
 Including media files
 Navigating to web pages
 Using embedded chunks
 Including html code
 Navigating with menus
 Using snippets
 Spelling checking
 Using the view mode
 Creating an index
 Creating a FAQ
 Creating a glossary
 Team authoring
 Working with projects
 Setting up structured authoring
 Generating file based output
 Creating printed output
 Importing files and folders
 Loading files in the project gallery
 Converting legacy content
 Including legacy content in real time
 Transferring objects between installations
 Smartcontent
 Notification
 Feedback
 Translating
 Customizing the look and feel
 User accounts
 Security
 Working with templates
 Working with metadata
 Versioning
 Auditing
 Workflow management
 Overview
 Creating the building blocks
 Enabling the workflow
 Using the workflow
 Indicating the task transition behavior
 Applying structural workflow changes
 The workflow contributors
 The workflow notification
 Using task lists
 Annotations
 Using event exits
 Appendix A: The URL parameters
 Appendix B: The object indicators
 Appendix C: Play Javascript