|
|
|
|
|
Applications using On-demand Communication should program defensively in the following way. If the calling application, for example, LMS, encounters a TDR for a user that it does not know about then it can choose to ignore the TDR, and perhaps log an error that such an event occurred. Generally this should not occur since the calling application will control what users get registered in OLSA via automatic user-registration or through explicit user-registration calls. An invalid procedural use case that might cause this to occur is if a user is inadvertently directly registered into OLSA, by personnel on the Skillsoft side, but not in the calling application. Again such an event should never happen but an application should program defensively as a contingency.
Another option a calling application may take is to automatically register the user with the specified userid in their system. Unfortunately in this situation there will be no other user-profile information like first name and last name to augment the registration. Such augmentation would need to be done in a separate process, if it is feasible at all.