Work Views for an Organizational Entity

You can automatically create different work views of your own work list. However, if you want to create a work view of a work list belonging to an entity in an organization model, you must have the viewWorkList system action for the work list you require.

Similarly, if you want to grant another user access to a work view of a work list belonging to an entity in an organization model, then that user must have the viewWorkList system action for the work list you require them to have access to. See Work View Permissions for more information about granting permissions to work views.

You can create work views for:

  • an individual resource
  • an organizational entity such as an organization unit, group or position.

Note that:

  • When creating a work view of another organizational entity, only offered work items are displayed. These are work items that were offered to the selected organizational entity, and that still have a state of Offered.
  • When viewing a work view for an organizational entity, you will only be able to see work items that are offered directly to that entity. You cannot see the work items for other entities in that organizational entity. For example, if you have created a work view for Group1 and Group1A is also a member of Group1, you must create a separate work view for Group1A. (You must also have the viewWorkList system action for Group1A).
  • If a work view is for another organizational entity’s work list and not your own work list, then you cannot open or complete work items in that view. This is because TIBCO ActiveMatrix BPM always requires a user to process work items in their own work list. If you accessed a work item from your work view and then allocated (or pended) it to a user, it would move from your work list to the user’s own work list. This is confusing because it means a user could open a work item, only for it to disappear because it has been updated by another user. It could also be the case that you can view a work list but are not a member of the organizational entity whose work list you are viewing. In this case, you cannot open work items in that view. For example, if you have the viewWorkList system action for a group called Group1, and you create a work view for Group1, you will be able to see the work items in Group1’s work list but you will not be able to open them.

System actions are modeled in the organization model that is built in TIBCO Business Studio. See TIBCO Business Studio Process Modeling Guide.