Documentação

English

Português
Español

English

Português
Español

Appearance

Platform Updates ​

Page type: Operational procedure — describes the delivery and activation process for updates. This is not a version changelog.

With the goal of ensuring greater predictability, stability, and quality in deliveries, Axia adopts a standardized process for updating client environments.

Release cycle ​

Official releases of the system are made available to all clients on the last business day of each month. Each release consolidates the improvements, bug fixes, and new features developed throughout the period, ensuring an organized and predictable delivery cycle.

Adoption flow ​

Development → Internal testing → Official release (last business day of the month)
    → Available in Staging → Client validation → Activation in Production
  1. Available in staging — immediately after the release, features become accessible in the staging environment.
  2. Client validation — the client performs tests, flow validations, and impact assessments in the staging environment before authorizing deployment to production.
  3. Activation request — when the client decides to deploy the update to production, they must submit a request through the official form.
  4. Analysis and deployment — the Axia team performs the technical and operational analysis and carries out the release according to compatibility, security, and planning criteria.

Requesting feature activation ​

To activate or deploy a feature available in a release to your production environment, use the official form:

https://forms.office.com/r/4hEP7uNRAV

Only features already included in official releases can be requested through this form. To request the development of something new or outside the current scope, use the New Features process.

Why this model exists ​

This model gives each operator control over the ideal moment to adopt new features, without compromising the continuity of production services. It also ensures greater stability, traceability, and transparency in the relationship between Axia and its clients.

  • New Features — how to request features outside the contracted scope.
  • Support — channels, SLAs, and support flow.