Integration checklist
TopClass Support and the customer are expected to manage the following responsibilities.
| Area | TopClass Support | Customer |
|---|---|---|
| General requirements | - Provide two XML files to enable the customer to create Business Objects (BO) and IQAs within iMIS to allow TopClass LMS Out of the Box integrations to run. - Configure the iMIS Bridge within TopClass. - Configure iMIS SSO within TopClass (if required). | - Import the two XML files provided and verify their successful creation of required objects. - Review filters on the IQA to confirm if the correct data is being returned in the IQA, based on your business requirements. - Confirm if JIT or batch (ETL) should be used (or both). - Ensure usernames are unique. Only the following characters are allowed in TopClass usernames: letters (a-z/A-Z), digits (0-9), dot (.), underscore (_), dash (-), at (@). - Set up iMIS SSO. |
| User information (iMIS > TopClass) | - Discuss user data requirements during the functional requirements workshop to confirm what data and fields are needed. | |
| Activity information (iMIS > TopClass) | - Discuss activity data requirements to be passed to TopClass LMS. - Discuss which activities should be created in TopClass LMS and how to restrict them. | - Confirm which integrations you would like enabled. |
| Enrollment/Order information (iMIS > TopClass) | - Discuss activity data requirements to be passed to TopClass LMS. - Discuss which activities should be created in TopClass LMS and how to restrict them. | - Review filters on the IQA to confirm if the correct data is being returned in the IQA, based on your business requirements. - Confirm which integrations you would like enabled. |
NoteCustomer can add/remove filters on the IQA to make sure data is exactly what the customer wants to send; however, the display properties should not be changed without first consulting your TopClass implementation project manager, as this can break the integration.