COSMOS Builder - 20231122
Release Notes
Revision History
| Version | Date | Revision Author | Summary of changes |
|---|---|---|---|
| 1.0 | 22-11-2023 | Maria Keshavarz | Initial version |
| --- | --- | --- | --- |
New features
Category colours As a web builder user, using the category and group component, you will now have a background colour parameter/attributes loaded for dynamics and configurable in Cosmos. So that you can design and style the components accordingly to your needs.
As a cosmos user you are now able to select a language for your website that complements the language within the country that you are building the website in. Because a lot of campaigns are now being built & redeemed in countries that are multi lingual. For example: You can build a website in Belgium with the language French (Belgium) and another website with the language Dutch (Belgium), using the same offers in Dynamics.
Algorithm As a Cosmos user, I can now configure the "winning game" setting on the winning game configuration page. So that you can create algorithms using cosmos.
As a cosmos user you can now introduce the "wining Moment" section so that you can create algorithms using Cosmos.
As a cosmos user you can now introduce the "Weighted wins" section so that you can create algorithms using Cosmos.
As a Cosmos User you can now introduce the "redirection" section so that you can create algorithms using Cosmos.
As a consumer management user, you can now see what possible offers a consumer participant has been allocated to by the algorithm you have set up, so you can assist and administer the participation properly.
As a Cosmos user, you can now see a warning pop up when you try and delete a claim journey or a page (in the web-builder) that is linked to an algorithm set. This is so that you are aware that this may break the process and you may need to act accordingly to unlink those journeys/pages and delete them.
Tech debt
Backend improvements- hide debug info- New appsettings.json entries (all repos
When Env.VerboseErrors is set to false:
Any unexpected exception in the system that can reach the user should be caught and ambiguated to something like "Something went wrong."
Same logic should be applied to the deployment error and the state description of it
both on websites part (deployment worker/code worker) as well as cosmos side if it fails before doesn't reaching the website cluster but after creating the website deployment log / code batch
When Env.ExposeSwagger is set to false:
The web services should not expose swagger UI (swagger/index.html) nor swagger open api definitions (swagger/v1/swagger.json)
In the web builder you can now see the style code when a style has been added to text. This is important for us to be security compliant.