Block Tasks - Configuration

A separate configuration file is defined for each AssetWise Community, accessible from a virtual directory. A specific task such as Add Note, can be blocked on Community A, yet allowed on Community B. Two separate virtual directories, "Novice" and "Expert", both with access to the same AssetWise Community can also be configured, each with its own set of blocked and/or added tasks. For example, the "Novice" virtual directory can block many of the AssetWise standard tasks such as Add Note, Add to Basket, Add to Folder, Explore from Here, and others, providing a limited set of tasks for the beginner.

Tasks are blocked by specifying the object Type and the Object Class Code of the Object displayed in the Content Pane. The Object Type value is a number, for example, Document = "3", Event = "94", and Item = "1". If a specific Class Code is given you can further specify whether all Child Classes are to be included.

Tip: You can use the asterisk (*) wild card in the Object Class Code to specify all classes of an object or a specific Class Code.

<blocktasks>
   </object 
      <object type="3" classCode="*" blockchildclasses="true">
          <task>dmNewRev</task>
          <task>dmCheckOut</task>
          <task>dmLock</task>
      </object>
</blocktasks>

In the configuration file, there may be one or more <object> nodes specifying each of the Object Types. For example, object type=3 represents documents, and object type=94 represents events.

In the classCode=ENG object parameter above, the tasks will be blocked only for documents with class ENG. To block tasks for all class codes, use classCode=* .

The blockchildclasses=true attribute denotes that some dm tasks will be blocked for child classes.

Note: The blockchildclasses parameter is only applicable when the class code is not = "*".