During the workflow why are some attributes per mapped and others are not when configuration the initial Mapping within Quick Connect?
This is by design in the product.
The reason why are some attributes pre-mapped and others are not during the initial mapping is Quick Connect looks for similar names against the target. If the source is using a virtual attribute, it likely won't find it in the destination, however if you use something like "Description", the Quick Connect easily finds it.
,
© 2021 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy