Betas at Collibra

Collibra uses betas to test new features and products in real customer environments.

  • Betas allow us to validate the quality, usability, and business value of the new feature or feature by:
    • Collecting user feedback during a predefined period of time.
    • Checking the usage.
    • Monitoring technical performance data.
    Based on the feedback, we can improve the product or feature to go GA successfully to the entire market.
  • Betas allow you to contribute to the evolution of new features and products, and have a significant impact on the end result, maximizing the benefit for your organization as well as your fellow data citizens.
Important 
  • Features and products that are marked as Beta are not yet finalized. They are likely to change more frequently and drastically than regular features and products. The timeline from a beta to general availability depends on the product or feature itself and on the feedback we receive.
  • The Collibra performance warranties and SLAs, including support response times and uptime guarantees do not apply to betas. Collibra also does not guarantee backward compatibility of new REST APIs of the beta feature. Finally, Collibra reserves the right to make changes to this disclaimer without prior notification.

We use different types of betas:

What is a public beta?

A public beta is a feature or product that is made available to most customers for evaluation, before its official general availability. You can enable the beta feature or product, and provide feedback to help us validate the completeness and usability. This phase helps improve the functionality of a feature or product, ensuring a smoother experience when it becomes generally available.

Collecting feedback on a public beta

The purpose of a public beta is to collect feedback about the usage, usability, user experience, feature completeness, and enterprise-grade aspects. Therefore, we may ask for feedback via in-application guides and surveys, or you can submit feedback on your own initiative through familiar channels. Unless specified differently, you can:

  • Send us questions and issues through Collibra Support.
  • Provide us with improvement ideas through the Ideation platform.

Note While we appreciate all suggestions and input, we can't guarantee the implementation of every requested feature or change.

FAQ about public betas

  • How can I participate in a public beta?
    Public betas are communicated via the Collibra release notes, via the Beta section.
    Most public betas are available for all customers within a supported region, but limitations may apply. Check the release notes or contact your CSM for more details.

  • How are public betas released?
    You have to be on the latest version of Collibra DIC, and be willing to upgrade when a new version is released. This also applies to products or features that are hosted outside the Collibra Data Intelligence Cloud platform, such as technical lineage, Edge, Workflow Designer, Collibra Data Quality & Observability.

  • Can I enable a public beta feature or product?
    Most public betas can be enabled by an administrator. For some public betas, however, this is different. Check the release notes or contact your CSM for more details.

  • Can I use public betas in my production environment?
    No, public beta code should not be used in production as it is still under development.

  • Do you provide documentation about public betas?
    Yes, we document public betas in the same way as regular features. You can recognize public beta documentation via the label (Beta).

  • How do I provide feedback about a public beta?
    Unless specified differently for the public beta, issues with a public beta feature or product can be provided through Collibra Support and suggestions for improvements can be logged via the Ideation platform.

  • What happens after the public beta?
    A public beta feature or product can remain in beta for some time, depending on the feedback we receive. Once the public beta feature or product has proven its completeness and ability to solve the problem or challenge for the user, the feature or product can become generally available.

What is a private beta?

A private beta is an upcoming feature or product that is made available to selected customers only to test and evaluate the feature or product early on. The participation in each private beta program is limited. Therefore, participating in a private beta program means participants commit to completing guided test scenarios and responding to surveys within a specific time frame. The gathered feedback allows our teams to make sure the feature or product meets the customer needs.

Collecting feedback on a private beta

If you are a participant in a private beta, we invite you to the Collibra Beta Platform. This platform is a community where participants can access the private beta program information and exchange feedback with our Product, Engineering, and UX teams.

During the private beta program, participants make time to complete test scenarios and respond to surveys available in the Platform. All ideas and improvement suggestions are also added directly on the Platform.

Note  While we appreciate all suggestions and input, we can't guarantee the implementation of every requested feature or change.

FAQ about private betas

  • How can I participate in a private beta?
    Contact your Customer Success Manager. They will provide you with information on:

    • The upcoming and ongoing private beta programs for which we are looking for participants.
    • The private beta programs of your interest and the participation requirements, such as timelines and technical requirements.

    Note We can't guarantee your participation in a private beta program because the number of participants in a private beta program is limited.

  • How are private betas released?
    You have to be on a specific version of Collibra DIC. This also applies to products or features that are hosted outside the Collibra Data Intelligence Cloud platform, such as technical lineage, Edge, Workflow Designer, Collibra Data Quality & Observability. Other requirements may also apply. Your Customer Success Manager can provide them to you.

  • Can I enable a private beta feature or product myself?
    No, only Collibra can enable private beta features and products.

  • Can I use private betas in my production environments?
    No, public beta code should not be used in production as it is still under development.

  • Do you provide documentation about private betas?
    Yes, we provide documentation via the Collibra Beta platform. The documentation is available only to the private beta participants and should not be shared.

  • How do I provide feedback about a private beta?
    All feedback on a private beta feature needs to be registered via the Collibra Beta Platform during the private beta. Hence, they should never be sent to Collibra Support.

  • What happens after the private beta program?
    A private beta program is limited in time. During the program, the involved teams follow up on the feedback. Once the program ends, any open feedback is included in an internal backlog or Ideation platform. The beta feature can then move further into a public beta or become generally available.