Issue Summary

If an OT has an attribute with minimum cardinality as 1, and an import is created where mapping for the attribute is non-existent, the import fails to start due to validation.

Steps to Reproduce

1. Create an OT X with OTA Y
2. Set Y minimum cardinality to 1 (make it required).
3. Create an import (any module) and map it to X.
   1. In the import mapping, do not create mapping for Y
4. Start import
5. Fails..

Expected Results

The import should start and update existing objects.

Actual Results

{
    "errorMessages": [],
    "errors": {
        "importSourceOTAttr": "Mandatory object type attribute are not mapped in the configuration (License Type)",
        "importSourceOTRequired": "At least one object type needs to be enabled in order for the import to be enabled"
    }
} 

This will usually result in an error in the UI like so:

The import of <Import Name> has failed to start
Please check your connect or try again at a later time. If problem persist, please contact support.

Workaround

Option 1: Remove the cardinality constraint for attribute.

Option 2: Set the mapping for required attribute.