Overview

This document describes the workflow of user transfers and notifications from Carnival GLADIS instances to the CSMART LMS.

User Transfer from GLADIS to CSMART

Users are transferred as often as the brands provide user data to their GLADIS instance - usually once per day. This makes sure the CSMART LMS is up to date with any GLADIS instance’s user data (minus any manual updates in GLADIS).

The user transfer from GLADIS (i.e. CCL, CMG, CUK and HAGroup) to CSMART is done via a so called replicator. The brand’s GLADIS instance pushes users to the CSMART LMS.

Every brand decides which users should be pushed by filtering the users by a set of OPF values (e.g. Rank values). The CSMART LMS imports those users (create new or update existing users).

A notification is sent when a replicator completes their work (TBD: who will receive those emails per brand?).

Replicator Email Notification Example

CCLToCsmartUserReplicator run for /Root/Carnival/CCL

Info messages:
1533 users ready for upload to 'https://csmart.marinels.com'.
1533 users successfully uploaded.

Deactivated Users Organization Login Id(s):
2-50938

Explanation

• Info messages - number of users who were transferred to the CSMART LMS

• Deactivated Users Organization Login Id(s) - if a user has been deactivated at GLADIS since the last replicator run, their OrgLoginIds are listed here. This will enable CSMART Schedulers to replace any seats already assigned to a user with a different participant.

CSMART User Import

The user data pushed by the brand’s replicators will be automatically imported into the LMS. Every time the importer is complete an import report will be sent (to a configurable set of users).

User Import Report Notification Example

CSMARTUserCsvIntegrator run for /Root/CSmart
Org Name: CSmart
Data Source: CCL-20241031_01_13_53_772_WebAPIUpload.csv
Total Users: 2053
Updated Users: 2052
Created Users: 0
Reactivated Users: 0
Deactivated Users: 0
Auto Deactivated Users: 0
Not Imported Users: 1
Overall Time (seconds): 41

Errors for not imported users:
Occurance(1) : Password couldn't be set for user, OrgLoginId: CCL-CCLTestAdmin, Message: NUMERIC - min numeric violation, must have at least 1

Errors:
Occurance(1) : DataValidationActivity: Another user is already having the same email address. EmailAddress: example1@marinels.com.
Occurance(1) : DataValidationActivity: Another user is already having the same email address. EmailAddress: example2@marinels.com.
Occurance(1) : DataValidationActivity: Another user is already having the same email address. EmailAddress: example3@marinels.com.
Occurance(1) : DataValidationActivity: Another user is already having the same email address.
Occurance(1) : Password couldn't be set for user, OrgLoginId: CCL-CCLTestAdmin, Message: NUMERIC - min numeric violation, must have at least 1

Warnings:
Occurance(1) : (MaxInvalidUsers): Threshold value exceeds, Configured Value: 0, Actual Value: 1

Debug Info:
UserCsvCollectorProcessingNote took 00h:00m:00s:034ms to complete the process.
InjectProcessingNote took 00h:00m:41s:480ms to complete the process.
DataConsistencyCheckProcessingNote took 00h:00m:00s:008ms to complete the process.
ValueMappingProcessingNote took 00h:00m:00s:003ms to complete the process.
DataSanitationProcessingNote took 00h:00m:00s:004ms to complete the process.
ReduceToOneEmailAddressProcessingNote took 00h:00m:00s:005ms to complete the process.
DataFormattingActivityNote took 00h:00m:00s:004ms to complete the process.
DataAssemblerProcessingNote took 00h:00m:00s:007ms to complete the process.
ResetFieldsToDefaultIfEmptyProcessingNote took 00h:00m:00s:028ms to complete the process.
DataValidationProcessingNote took 00h:00m:08s:042ms to complete the process.
UserPasswordProcessingNote took 00h:00m:00s:161ms to complete the process.
ThresholdProcessingNote took 00h:00m:01s:520ms to complete the process.
AutoUserDeactivationProcessingNote took 00h:00m:00s:005ms to complete the process.
UserImporterProcessingNote took 00h:00m:31s:687ms to complete the process.
PostProcessingProcessingNote took 00h:00m:00s:000ms to complete the process.

Explanation

• Data Source: CCL-20241031_01_13_53_772_WebAPIUpload.csv
  Information about which brand the data was coming from (e.g. CCL) - this will be available in 4.9.0

• Errors should be solved - the most common error is email conflicts between 2 users.

• Warnings should be solved but doesn’t have a real impact on the import.

• Debug Info is for information only - contains run times of the user importer and generally can be ignored (it would be possible to remove all debug info from the notification)

Note: No users are deactivated/deleted. Users are only created, reactivated or updated.

User Conflict Resolution

Due to users moving between brands and brand groups there is a chance that 2 different GLADIS instances will send the same user with 2 different OrgLoginId but with the same login email address. This causes a user conflict at the CSMART LMS user importer.

Any user conflict will surface as an error in the user import report notification with a message like DataValidationActivity: Another user is already having the same email address. EmailAddress: example1@marinels.com.

To resolve the conflict make sure to move the user at the CSMART LMS to the new brand:

• Lookup the conflicting user by email address in the CSMART LMS (Manage>Users)

• Update user’s OrgLoginId (CSmart Login) to match the new crew Id/employee Id and Operating Line prefix (e.g. CCL-11111>CUK-222). Also, make sure the Operating Line field is updated to the new brand (e.g. from CCL>CUK).

The next import should find the user (OrgLoginId and email address).

CSMART Scheduler User

Any CSMART LMS user will have a corresponding representation in the CSMART Scheduler. An LMS to Scheduler replicator makes sure those are in sync with each other (running every 10min).

Most information is available right away (first name, last name, date of birth,…). However, if a user needs to be moved from one brand to another, this may take up to 10min.

Participant not Found

It is possible that a user is not found when adding a participant to an event.

Please check the following to fix the issue:

• Make sure the user exists and is assigned to the correct Operating Line (OrgLoginId must prefix the brand)

• User may not exist in the CSMART LMS yet - therefore, can’t be found in the CSMART Scheduler => make sure the user exists in the CSMART LMS and wait 10 min. for the replicator to update the CSMART Scheduler

• User exists and has the proper Operating Line and OrgLoginId => wait for about 10min. to let the replicator update the CSMART Scheduler