DPA SaaS considerations

DPA has specific considerations in a SaaS environment.

Considerations are indicated for each feature, and recommendations on how to approach the feature implementation in the SaaS solution.

Feature	Consideration	Recommendations
DPA site-wide key	DPA utilizes a site-wide key for all communications with desktop clients. The client and server portions of the paired keys must always match.	Service Providers can change the default public/private key pairing, as long as they change this pairing for all tenants. If the Service Provider changes the default private-public key, the new key must be distributed across all tenants. All tenants and all desktop clients of the tenants must have the same key.
DPA system administration	Configuration and downloading of Tracing is not available for Tenant Administrators.	The Service Provider should implement tracing profiles and retrieve resulting log files where necessary or directed by Verint support.
DPA Validator Capture Settings	The capture settings language list is generated by the Service Provider and sent to the tenants.	Tenant-based localization is outside the scope of DPA. It is controlled by the system and DPA inherits the settings.
Live Information Workflow	Tenants are able to remove the Live Information Feed Ability.	Service Providers can control this at their discretion. Contact Support if needed.
DPA System Configuration	UseUserFQDN Configuration key	DPA must be configured for fully qualified User Principal Name to ensure globally unique user names. This is a Service Provider-only configuration setting within the DPA System, Configuration, Default Configuration profile. The UseUserFQDN setting in the System Group configuration area must be set to Y.
Employee Profile	DPA Datasource Value	The value of any user licensed for DPA must have a User Principal Name (UPN) format as denoted by the output of windows command whoami /UPN. Multi-tenant enabled systems do not support licensing of local ( non-domain) users for DPA.
Trigger Commands	Default trigger commands provided by the installation are accessible by all tenants.	The Service Provider should remove default trigger commands from the root organization to avoid confusion. All tenants have visibility over the root organization. It is the Service Provider’s responsibility to add trigger commands at the tenant root level to allow each tenant to fully administer their own trigger commands.
DPA client side data generation (Application data, firing triggers, and so on)	A user that has Tenant ID of 0 cannot generate DPA client side data.	Users with Tenant ID of 0 can log onto the WFO or DPA Web UI. However, to maintain the integrity of tenant-specific data, they are not able to upload client side data into the database.