Entities

Application users are the most integral part of any system. The storage type used to store this user information can vary based on the Enterprise. Examples could be SQL database or Active Directory. AVEVA Work Tasks can be used to build Human centric workflow solutions. The users required to be part of this workflow solution can exist in different data stores.

A Repository contains Workflow Definitions, Queues, Calendars, Workflow execution data, and Business Activity Monitoring (BAM) data. The User Provider for the Repository is also defined while creating a Repository. Each Repository could potentially have its own user database, for example, one repository may connect to Active Directory, and the other may connect to theDatabases and others to Lightweight Directory Access Protocol (LDAP) or Active Directory Application Mode (ADAM).

The user integration needs to be outside the Repository boundary since users can span across multiple Repositories. AVEVA Work Tasks has the concept known as User Entity and Role Entity for managing users across different platforms.

User Entity manages all the information for the users across different Data sources. Data Source may be Active Directory, SQL providers, and so on. The Role Entity manages users in roles.

Data bridge framework is the common framework that bridges the entity item and the corresponding Data source providers. Each entity item will internally communicate with the Data bridge framework to know from which Data Source provider the entity details should be retrieved.