List of items: |
---|
1. Sunset Sycle - Transition Highlights |
---|
Camms initially launched Sycle to integrate our products seamlessly. Over time, we have successfully incorporated Sycle's functionality directly into our native products. Now, with only a small number of clients continuing to use Sycle, we're eager to introduce key developments that will benefit all our customers.
The sunsetting of Sycle will not impact your ability to use any other Camms products or result in any data loss. Rest assured, all the features you currently enjoy in Sycle will still be available in the non-Sycle version. Below are key highlights of the Transition.
1.1 Automatic Redirection to Camms.Strategy
Users entering the Sycle URL will now be automatically redirected to Camms.Strategy. Below are the URLs for each Camms product in Camms public cloud across different regions.
Region | Environment | Camms. Strategy | Camms. Project | Camms. Risk |
AU | Test/Train | |||
Live | https:// camms.com.au/strategy/ | https:// http://camms.com.au/risk/ | ||
UK | Test/Train | |||
Live | https://camms.co.uk/strategy/ | https:// http://camms.co.uk/project/ | https:// http://camms.co.uk/risk/ |
1.2 SSO Portal Product Display
Clients using SSO with Sycle will now see all activated products directly within the SSO portal, replacing the Sycle tile.
1.3 Product-Specific Login Pages
The login page displayed will now correspond to the product URL entered by the user. Product-specific branding will be shown on the login page, replacing the Sycle branding.
1.4 Product-Specific Logos
The product logo will now be displayed within each product, replacing the Sycle logo. Clicking on the product logo will redirect you to the configured homepage within that product.
1.5 Integration of Sycle Mega Menu into Camms.Strategy
All menus previously available in the Sycle Mega Menu are now integrated into the Main Menu within Camms.Strategy. Consequently, the Sycle Mega Menu will be hidden from all products.
1.6 Direct Login via Product URLs
Users can now directly log in to any product using the provided product URLs. Upon successful authentication, you will be redirected to the configured homepage within the respective product. As a result, the default product selection option has been removed from the My Settings area.
1.7 Header Color Configuration Feature
For clients who have enabled the Header Color Configuration feature and customized their Sycle header color, your chosen color will be retained and reflected across all products. This feature remains available, and you can continue to use it as before. To configure the header color, please visit the Client Details area.
1.8 Quick Access Home Page Feature
For clients who have enabled the Quick Access Homepage feature and the users who have set it as their homepage, your Quick Access homepage in Camms.Strategy will be retained. This feature remains available, and you can continue to use it as before. To configure your homepage, please visit the My Settings area.
Additionally, the background you have configured for the Quick Access Homepage will be retained and reflected accordingly. You can change the Quick Access Homepage background via the Client Details area.
1.9 Sycle Logo Configuration Feature
For clients who have enabled the Sycle logo customization feature and customized their Sycle logo, your customized Sycle logo will be retained and reflected across all products. This feature remains available, and you can continue to use it as before. To configure the Sycle logo, please visit the Client Details area.
1.10 Migration of Permissions to Camms. Strategy
For clients who have enabled the flexible hierarchy permission structure, all permissions previously granted for the Sycle product have been retained and migrated to the Camms.Strategy product within the same role. This migration ensures that you can continue your day-to-day tasks without any interruptions. Additionally, Sycle will no longer appear in the product dropdown in the Role Management area, as all its permissions have been transferred to Camms.Strategy.
There are no changes to permissions for clients using the static permission structure.