Conditions for User Mapping in Configuration Package
User Mapping
Many Unifier modules have user information as a part of setup information. When you create and export configuration package, the user information is included in the package; however, when you export, the user information will not be created in the Production environment and the import process will fail.
To prevent this, you can map the Development/Test environment users to a user in the Production environment.
Note the following conditions:
- The user mapping that you set at this point applies to the particular configuration package that you are working with.
- The names that you enter in the Destination Login Name field (Production) must exist in the destination environment.
- The system validates the user names at the time of import.
- If no user exists by that name, the import fails.
- The Destination Login Name is a text field and the system validates the character length against the existing character length limit for the field.
- You cannot map a two-source user to the same destination user.
See Also
Importing Configuration Packages
Configuration Package Report and Audit Log
Configuration Packages Import Rules
Last Published Saturday, July 13, 2024