CasparCloud - Migration

CasparCloud - Migration

CasparCloud is somewhat different to Caspar on-premise, and to move forward with this change a number of steps must be taken by the customer before proceeding. The attached fact sheet is here to help you identify these and let you know what support we can give you through this process. Without these components in place, it will cause delays. 

    • Related Articles

    • CasparCloud - User Acceptance Testing (UAT)

      UAT is the testing of CasparCloud by your users to validate that the application functionality is working as expected and that data from your on-premise system has been migrated correctly. This validation should be carried out by users who are ...

    • CasparCloud Release Notes 25-02-2022

      Release Date: 25th February 2022 Frontend: v0.1.116 Backend: v1.0.88 FIXES [CA-834] Legal Application (Client) - Improve BF56 population  Fixed: The client’s name was previously outputting as large text on the BF56 form. The document now exports the ...

    • CasparCloud Release Notes 09-11-2022

      RELEASE NOTES                          Release Date: 9th November 2022 Frontend: No update applied  Frontend: 1.6.2  Backend: 1.6.5  IMPROVEMENTS Single Sign-on (SSO) SSO in CasparCloud is implemented via OAUTH 2.0 enabling customers to use Microsoft ...

    • CasparCloud Release Notes 02-02-2023 - Hotfix

      RELEASE NOTES Release Date: 3rd February 2023 Hot Fix Backend: 1.6.9 Frontend: 1.6.5 HOT FIX [DB-131-] Automatic Reconciliation – Transaction Cancel Fixed: A bug relating to the Cancel function in the Automatic Reconciliation caused transactions to ...

    • CasparCloud Release Notes 04-04-2022

      Release Date: 4th April 2022 Frontend: v0.1.133 Backend: v1.0101​ FIXES [CD-172] Auto Rec & Expected Transactions  Fixed: previously the auto rec only showed expected transactions for clients with transactions in the uploaded bank file, the system ...