Page Comparison

...

  "DataValidationConfiguration": {
    "IdentifierFields": [
      {
        "Name": "OrgLoginId",
        "Type": "String"
      }
    ],
    "CriticalFields": [
      {
        "Name": "Vessel",
        "Type": "String"
      },
      {
        "Name": "FirstName",
        "Type": "String"
      },
      {
        "Name": "LastName",
        "Type": "String"
      },
      {
        "Name": "Rank",
        "Type": "String"
      }
    ],
    "RegularFields": [
      {
        "Name": "EmailAddress",
        "Type": "EmailAddress"
      },
      {
        "Name": "DeptCode",
        "Type": "String"
      },
      {
        "Name": "Password",
        "Type": "String"
      }
    ],
  "PasswordFields": [
    {
      "Name": "Password",
      "Type": "String"
    }
   ]
  }

This activity validates all parsed user objects according to configuration and LMS specification (i.e. single choice field must have the proper value).

...

• IdentifierFields (Mandatory): used to uniquely identify a user (i.e. OrgLoginId, login email address). Currently it supports one identifier field.

• Critical field which needs data validation and would stop processing the whole user if it contained invalid data (skip user). Continue with any other users though.

• Regular fields: ‘Partial' user import mode may allow to create user with invalid regular fields. In case of 'Full’ import mode it would stop any user to be imported if there is any invalid regular field(s).

• Password fields used for password creation only.

Every field must have a Name and Type (String, DateTime, EmailAddress).

...

• IdentifierFields": "OrgLoginId"

• CriticalFields": "Rank", "Vessel", "FirstName", "LastName"

• RegularFields: "EmailAddress", "ContactEmail", “Deactivate (X)”, “UserLanguage”, “CanViewReports”, “ForcePasswordChange”, “Password“

• PasswordFields: "Password"

Password Configuration (Mandatory)

...