Short Description - This best practice is intended to help Application Administrators with the type of import based on business scenario and use cases. This is mainly applicable when Saviynt provides more than one type of connector for an integration. This also talks about key tips related to import.
Detailed best practice
Import strategy Key tips for few connectors -
- Workday: Workday integration can be configured using both RAAS and SOAP mode of integration. SOAP based integration should be selected if workday tenant is large in terms of data size. The RAAS integration does not support increment import and full import will be time consuming in case of large data set.
- AWS: AWS out of box supports parallel import as customers will have hundreds of AWS accounts. AWS Connector also provides the ability to reconcile selective resources (for example only S3) instead of all resources based on Customer use cases.
- Azure AD: Using custom access Import you can bring in selected entitlement types instead of all entitlements which will speed up the import process as well
Avoid Import failures due to Data Size discrepancy :
Import fails when attributes length coming from the target source is mapped to a Saviynt attribute of smaller size. We need to make sure data size discrepancy is handled before import.
Data Transformation - Use inline processing for your data transformation needs.
Reference documentation (doc portal link) - Please refer to connector specific document in doc portal for details around the above connectors.
Impact - Key benefits - Quantitative/qualitative benefits
- Selecting the right strategy can help with smooth Import operations.
- It will avoid operation issues due to data size discrepancies.
- Helping a Application Admin choose right connector
