Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Initial request for Integration, using the Integration Request Form – 5 business days

    • Information gathering phase

    • Need will be assessed, alternative (already existing) integrations may be suggested

  • Security and Functionality Review – 14 business days

    • In the interest of protecting student data in compliance with University Policy 8060, the Office of Information Technology may review data storage, retention, and transmission, and deletion processes for third-party applications

    • To ensure interoperability with our campus technology ecosystem, the Office of Information Technology may perform a software architecture review of third-party applications

  • Testing – 6 business days

    • Integrations are run through one Canvas environment – our Canvas Test Development site.  

    • Basic functionality of the tool is tested, as well as its interactions with other parts of Canvas

  • Contract Review – 30 business days

    • This step may be optional for free services or those already under contract.

    • Integrations requiring a contract will need to meet standards set by University Policy 6030.

    • SARB Approval

  • Integration – 4 business days

    • Canvas upgrades are administered early on Wednesday mornings. The timeline for integration is contingent upon the upgrade schedule.

...

  • Vendor and tester responsiveness

  • SARB approval

  • Canvas upgrade cycle

  • Priorities for Canvas core services.

...