Please review the February Release Notes for details on all the new features and updates which you will have access to following the deployment.
If you have any questions or concerns, please contact your customer success manager or reach out to SpringCM Support.
REMINDER: SpringCM Production accounts will be unavailable tonight Friday, January 18th 9pm - 12am CDT for the 19.1 Product release. We apologize for any inconvenience.
[UPDATE July 19, 2018 at 016:17 CDT] We've identified the root cause of the issue and mitigated the performance degradation affecting some NA11 and NA21 accounts. If you are experiencing any issues, please contact Support.
[UPDATE July 18, 2018 at 04:15 CDT]- The SpringCM Technology Team continues to work on isolating the service availability issue for the tasks page on the NA11 and NA21 instances. It is highly recommended that users who are experiencing this issue clear their browser's cache, as this has been identified as a successful solution. Full instructions for updating your browser's cache can be located here.
[UPDATE July 18, 2018 at 08:10 CDT]- The SpringCM Technology Team continues to work on isolating the service availability issue for the tasks page on the NA11 and NA21 instances.
Jul 17, 2018 7:58:11 PM - The SpringCM Technology team is working to resolve a service availability issue on the NA11 and NA21 instances. During this time, some customers may experience the inability to open the Workflow Tasks page.
Until resolved, impacted users are advised to clear browser cache and/or switch browsers.
Please check the status of trust.springcm.com frequently for updates regarding this issue.
February 2, 2018 08:00AM CT - The workflow queues returned normal to normal at approximately 5:30pm CT on Thursday, February 1, 2018.
We have detected an abnormal increase in workflow volume that is resulting in intermittent workflow delays starting between approximately 9am and 10am CT. At present time the engineers have addressed the degradation in workflow execution and we anticipate the workflow queues to return back to normal shortly.
Our engineering team is currently investigating the root cause of the issue and will provide another update.