option to skip attribute mappings or to add option to Apply mapping on 'disable' SoftDelete task
Would like to see added two things,
1) The option to apply mappings 'only' when the account is SoftDeleted.
2) The option to skip a mapping should a NULL value be returned.
These would help prevent provisioning errors when the Source directory contains NULL values causing failures when creating in Active Directory.
If you happen to 'update' a field with a NULL value to an exisitng account in Active Directory, the update task will work, but should you try this during a 'Create account' task, this fails with a "ConstraintViolation-LdapErr: A value in the request is invalid".
So far, this has only been noticed to occur on the AD Description field but would be expected to occur on other AD fields too.
Having either a "Skip" mapping when a validation expression fails or adding the option: Apply mapping only during 'OutOfScope' or 'Deactivated' tasks would avoid generating failures.
We do not delete accounts but disable in AD when disabled in the Source HR directory. We then change the Description field to identify when and how this happens for IT Teams to quickly identify leavers. This allows us to managed account deactivation processes in an orderly manner, removing licences, migrating data etc.