Enable and Disable Security at List /List item level

A List is a storage place where a user can store groups of information that possess some common attributes. It has the provision to add new information, edit and delete existing information, and publish/unpublish the information.

In a real-time enterprise application, the user stores expense list, travel claims, leave details, employee details, product details, order details in a list structure. In a typical organization, lists store employee details, product details, and expense details. These lists contain some common attributes. For example, the product list stores information including the product name, price, manufacture date, and expiry date. The order list stores information like the order ID, order date, order item pertaining to the order.

ListItem

Each row or record of information inside a specific list can each be treated as a ListItem. These rows or records possess some common attributes. For example, each item inside a product list is called a ListItem of the product list.

List Operations

The list operations are add, edit, view, and delete. For example, add a new product, modify information about an existing product, delete a product, and publish or unpublish information about a product.

List

To provide the operations mentioned previously, AVEVA Work Tasks has the List infrastructure where you can create a list and store list information. You can perform custom operations like add, edit, view and delete for that list.

AVEVA Work Tasks has implemented the list infrastructure to manage and store lists like Process list, Repository list, Event Provider list, Workflows list, Navigation list.

Workflow List - Workflows are maintained as a list. Each workflow has a name, description, owner, version information, item status information, workflow status information and last modification information. The user can perform operations like creating a new workflow, editing the workflow using the Process Designer, viewing workflow, deleting workflow, publishing workflow, unpublishing workflow, saving workflow with different versions, disabling or enabling workflow and associating workflow with different events.

Users List - Each user has information like name, email information, department information, role and owner. The User Management maintains this information as a list and allows you to add a new user, view user information, edit user information and delete a user.

Menu List - The menus are also maintained as a list to store the information in a list infrastructure.

AVEVA Work Tasks has a new feature called Forms Designer and List Designer. The List Designer is used to create enterprise specific list, product list, orders list, customer details list, and so on. Each list can be used to render the forms specific to that list to create items inside the list.

In a enterprise specific list like Product List, which has fields such as Product ID, Manufacturing Date, Warranty Period, Price. Users can add product details, delete/update the existing details.

Security

AVEVA Work Tasks also has the Security feature in the list infrastructure. Using the Security feature, the list as well as each item inside the list can be secured to ensure, certain actions like add, edit, delete can be performed only by authorized users (users who have the rights to perform these actions).

Why List Specific Security?

The List specific security is required when you need to restrict the access to the list and the operations that can be performed on that list. The List Level security provides features that allow you to maintain and manage user privileges across the list.

The List level security allows the user to secure access to the various lists available in a Repository.

AVEVA Work Tasks defines a set of rights that can be set for users at the List Level. List level rights can be grouped as follows:

• General Rights - These rights are common across lists.

• List Specific Rights - Rights that are specific to lists. [Workflow, User list, Inbox –  Work items list]

• List Level - General Rights: A set of rights that are applicable across all lists

• The user can control the following actions across all lists:

• Can add item - Whether a user can create a new item in the list or not

• Can delete item - Whether a user can delete an item from the list or not

• Can edit item - Whether a user can edit an item in the list or not

• Can publish item - Whether a user can publish an item in the list or not

• Can unpublish item - Whether a user can unpublish an item in the list or not

• Can enable/disable - Whether a user can enable/disable an item in the list or not

• Package Item - Whether a user can add the artifact in the list to a package template or not

• Can manage security - Whether a user can manage the security of  an item in the list or not

• Can see all versions - Whether a user can see all versions of an item in the list or not

• Can view item - Whether a user can view an item in the list or not

• Can view others draft item - Whether a user can see the items that are in draft mode but owned by other users or not

• Can view pending item - Whether a user can see the pending item (for which work is in progress ) in the list or not

• Can consume item - Whether a user can consume an item in the list (it may be in lookups or any place where list items gets consumed) or not

• Show all folder - Whether a user can see all folders in the list or not

• Show only owned items - A user can see only the items that they own and cannot see the items owned by others

• Can save as next major version - Whether a user can create a next major version of an item in the list or not

• Can save as next minor version - Whether a user can create a next minor version of an item in the list or not

• Can save as next version - Whether a user can create a next version of an item in the list or not

• Can save as specific version - Whether a user can create a specific version of an item in the list or not

List Specific Rights

Each list is unique and has a different set of actions which can be performed on it. Hence every list can have a specific set of rights appropriate to it.

For example the actions that can be performed on a Workflow list are: Design, Edit, View Workflows etc, whereas the actions which can be performed on a user list are: add , edit, delete users. In the above case, the design operation is specific only to the workflow list. Hence workflow list has a specific right Can design workflow. Similarly, for every list user can define specific rights appropriate to that list.

The following rights are the Workflow List Specific Rights:

• Can design workflow - Whether a user can design the process definition of an item in the workflow list

• Can do tasks - Whether a user can do tasks like design workflow, start workflow wizard (this option is not applicable), provision now etc on an item in the workflow list

• Can view properties - Whether a user can see the properties of an item in the workflow list

• Can view Design - Whether a user can see the process definition (design) of an item in the workflow list

• Listed below are the Manage Package List Specific Rights

• Run - Whether a user can install the package or not

• Uninstall - Whether a user can uninstall the package or not

• Can Manage Security - Whether a user can manage security at list item or list level of a Manage Package List or not

• Listed below are the Package Template List Specific Rights

• Export- Whether a user can export the package template or not

• Generate -  Whether a user can generate the package template or not

• Mark as Shipped -  Whether a user can mark the package template as shipped or not

• Can Manage Security - Whether a user can manage security at list item or list level of a Package Template List or not

Process Interface Specific Rights

AVEVA Work Tasks Security also allows process interface specific rights. It offers specific rights for different process interfaces [Process Designer, Web Work items list]. These rights allow or disallow a user to access specific features of the process interfaces.

• Process Designer Specific Rights: For controlling the Process Designer menus

• Can Export - Allows or disallows a user to export a process definition

• Can Import - Allows or disallows a user to import a process definition

• Can Validate Definition - Permits a user to validate a process definition

• Can Set Work Items Fields - Permits a user to define a custom work item field etc

Rights for controlling categories, actions, and properties:

• Can View Categories - Allows or disallows a user to view and use specific categories of Activities in the Process Designer actions toolbox. The user will be able to select the categories that can be viewed or not by a particular user.

• Can View Actions - Allows or disallows user to view and use specific activities in a particular category. The user will be able to select the actions from a particular category that can be viewed and used or not by a particular user.

• Can View Properties - This will allow the user to view, use and configure different properties of an activity. The user will be able to select the properties that can be viewed and used or not by a particular user.

Web Work Items List Control Rights

Rights that are specific to the Work items list control, the rights defined for the Work items list that are applicable at the Repository level:

• Can Set Alternate Actor - Whether a user can set an alternate actor

• Can Set Preferences - Whether a user can set preferences

• Can See Queue - Whether a user can access the queue control

• Can View Resource Calendar - Whether a user can see the resource calendar

• Can View Work Item Control - Whether a user can see the work item control itself

• Calendar Control Rights

This section contains the rights related to the calendar control. The scope of these rights is the Repository level:

• Can Add Calendar - Whether a user can add a new calendar

• Can Add Calendar Workslot - Whether a user can create a new work slot in a calendar

• Can Delete Calendar - Whether a user can delete an existing calendar

• Can Delete Calendar Workslot - Whether a user can delete a work slot of a calendar

• Can See All Calendars - Whether a user can see all the existing calendars

• Can View Calendar - Whether a user can see the calendar control itself

• Queue Control Rights:

• Specific to the Queue Control, these rights are at the Repository level:

• Can View Queue - Whether a user can see the queue control itself

• Can Add New Queue - Whether a user can add a new queue

• Manage Queue - Whether a user who is not the owner of a queue can modify/delete the queue

BAM Control Security Rights

The BAM Control now comes with enhanced security features that allow business users to restrict permissions for various features in BAM. Some of the BAM rights have Repository level scope and some rights are at the List and List Item level.

• Can View Global Reports - Whether a user can view global reports. Scope –  Repository level.

• Can View Others Reports - Allows a user to view other users' reports. Scope – List Specific for List Item level.

• Can View Owned Reports - Whether users can view their owned item reports. Scope – List Specific for List Item level.

• Can View Triggered Reports - Whether users can view reports of their own triggered workflows. Scope – List Specific for List Item level.