FAQ's

What is the priority and timeline for the three stages of branding compliance?

• Stage 1 | Primary Branding: This is our current stage and it should be updated in your next release, If that is not possible, then the release after.
• Stage 2 | Secondary Branding: Information and guidance about this stage will be provided in the upcoming months, after the Primary Branding stage is complete.
• Stage 3 | Tertiary Branding Compliance: Information and guidance about this stage will be provided in the upcoming months.

 

Can I continue using an interim logo?

Interim logos, such as ‘Micro Focus is now OpenText’ or ‘Vertica by OpenText’, should be replaced with the ‘OpenText’ logo. It is optional to add an additional text or a comment, such as ‘Micro Focus is now OpenText’.

 

Who is responsible for updating the products branding?

The designers of each product team are responsible for updating the in-product branding. Rebranding activities are scheduled against existing engagements and priorities. Note: the guidelines on this website should allow products with no designers to also implement the rebranding. All the required specifications, details, and assets to download are included in the Rebranding section with no need to use other external tools.

 

What products need to rebrand?

At a minimum, the “Stage 1” updates listed in the Product Rebranding Checklist should be made in the next major or minor release of each product. If teams can fit these updates into a release currently in process, without compromising the schedule or release requirements, then please do. If not, they should be added to the scope for the next major or minor release. If no major or minor release is planned, it is okay for the products to remain branded as Micro Focus for now. We will revisit the policy for those products on a quarterly basis.

 

What if we aren’t releasing for 6 or more months?

You don’t need to initiate a new release just to rebrand. Plan to include the rebrand for the next major or minor release. If no major or minor release is planned, it is okay for the products to remain branded as Micro Focus for now. We will revisit the policy for those products on a quarterly basis.

 

What if we can implement only part of the requirements for the current release? (e.g. All the legal, but not the visual requirements)

Don’t partially implement the requirements of Stage 1. There is no legal advantage to make the legal updates ahead of the branding. So make sure to implement the legal updates together with the minimum brand requirements.

 

Are there changes in copyright?

Yes, changes were made, please refer to our Legal section. It is recommended to regularly check our Legal text specification for any updated copyright and legal verbiage. This information is provided by our Legal department and may change occasionally. We recommend checking back at every major release or on an annual basis.

 

Does my product need to adopt the “CE v.#” information as part of the product name?

Updated: November 1, 2023

Yes, we will be adding ‘CE’ to product names, see CE Branding for more details.

 

How do I explain to customers why a product that is not cloud-native is labelled with CE for Cloud Edition? 

Added: November 1, 2023

the use of ‘CE’ (Cloud Edition) in release names 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.). 

 

Do product names and CE number need localization?

Added: November 23, 2023

No, the product name and CE number are always displayed in English, regardless of the locale.

 

Do we need to change our fonts?

No. Updating the fonts is not part of Stage 1, so you should not change any fonts right now.

 

Do we need to change URLs and installation paths that include Micro Focus references?

For this stage, there is no need to change those.

 

Do we need to change installation paths that reference HP or HPE?

Installation paths and directories that contain HP or HPE should be updated as soon as possible, however, this is not mandatory for stage 1. In such cases, it is important to include a disclaimer. The disclaimer text should be updated as followed:
‘This software was acquired on September 1, 2017 by Micro Focus and is now offered by OpenText.’
See HP/HPE disclaimer guidelines for more details.

 

Do I need to change my HP / HPE disclaimer text?

Your disclaimer should be updated as followed:
‘This software was acquired on September 1, 2017 by Micro Focus and is now offered by OpenText.’ See HP/HPE disclaimer guidelines for more details.

 

What are the guidelines for products with marketplace presence?

If your product has a presence on a marketplace, such as AWS Marketplace, please follow the marketplace guidelines.