DataBridge Provider

AVEVA Work Tasks follows a 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. Here data source may be active directory and SQL providers.

Role entity manages users in roles.

Data bridge framework is the common framework that bridges between the entity item & the corresponding data source providers. Here each entity item will internally communicate with the Data bridge framework to know from which data source provider the entity details should be retrieved.

User Entity

User Entity makes possible to use different data source providers to be used simultaneously to extend the Meta data and provide more number of unique user stores. This provider will maintain its own Universal Provider Actor table, which will map each data source provider and allow unique user ids to be stored in the mapping table while giving a unique user id which will be further used by the rest of AVEVA Work Tasks functionality.

Role Entity

Role entity allows getting all the users based on their roles. This will again communicate with the Data bridge frame work that will get the users in Roles based on the data source provider.

All the Role information will be stored in the SKVirtualRole table along with the role name and data source provider name.

User Integration in AVEVA Work Tasks

To add users, all the user properties should be configured correctly. The configurations are done in the XML data. Here user properties are name of the user, email id, unique identifier  and other user related details.  Along with the user properties, the data source for users must be specified whether if the users are from the data base, active directory etc.

All the entity information is stored in the SKEntity and SKEntityDataSourceProvider tables.

SKEntity table stores all the user properties. These properties will be displayed in the UI for the user to query the resources.

SKEntityDataSourceProvider table stores the data source provider information for each of the entity item. Here all the user properties are defined and bounded to the user properties defined in the SkEntity table.

The VirtualActor table is used to map real user ids to virtual ids used by AVEVA Work Tasks.