CE Branding
⚠️ Please note!
This page includes guidelines and examples for heritage Micro Focus products that are now part of OpenText. They are mostly relevant for products designed using one of the hMF design languages (DS17, DS21) or built using UX Aspects / Universal libraries.
For guidelines that are more specific to heritage OpenText products, please refer to UXD’s guidelines.
ALL products, including Off-cloud products, are required to add the ‘CE CY.Q‘ convention.
- ‘CE’ represents Cloud Edition, used for marketing purposes, where ‘CY’ represents the Calendar year, and Q represents the release quarter.
- CE should only be used in the full release name, e.g: “OpenText ValueEdge CE 24.1”.
- CE is NOT part of the product name. In the example above, the product name is still “OpenText ValueEdge”.
- CE should not be used with only the Product Name or only the Version Number
How to communicate CE to our off-cloud clients?
The use of ‘CE’ is not meant to represent a current capability in the product, it is included on all OpenText products as part of the company’s branding and marketing — representative of our cloud focus. CE refers to the ongoing series of all OpenText product releases using the CY.Q version standard (e.g. 23.4, 24.1, etc.).
When to implement?
- Product teams must plan to make these updates at the earliest opportunity, as will be feasible for current development schedules and customer commitments.
- Products that have not yet adopted the full branding convention shown in the design standards below (“OpenText™ | Product Name CE 24.1”), MUST plan to adopt this convention at the earliest opportunity.
Exceptions
Updated: November 21, 2023
- Any legacy / portfolio products which were already exempt from standard naming and versioning rules are also exempt from the CE naming
- Any products in official maintenance, or that are not planning for any major or minor releases in their product roadmap.
- Hardware products
Items that must be updated with this convention include: