User Entity

User Entity makes possible to use different data source providers 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.

User Entity provider information will be stored in the SKEntity table. For each of this user entity, there will be unique settings that are stored in the DefinitionXml column. Along with these setting, repository name, mapping table info etc are stored. Settings for each user entity are stored in XML format. These include the user properties with details like the name of the property, its purpose, and display name. The mapping table used for storing the user information will be SKVirtualActor table. This table contains data related to user unique identifier, name, and email.

As shown in the image below, an entity can be mapped to different data source providers. For User Entity the providers mapped are called as user entity data source provider. The configuration for user entity data source provider is persisted in SKEntityDataSourceProvider table. For each of this user entity data source provider, there will be unique settings that are stored in the DefinitionXml column.