Each app has only one active version at a time, and that is the version users see in Custom apps.
Before you start
To use App management, you need the capabilities to manage Flows custom apps.Open App management
You open App management from the Custom apps page.1
Open the Flows workspace
Sign in to CDF > Flows workspace > Custom apps.
2
Open App management
In the top right, select the Manage apps button. If you don’t see it, your group doesn’t include the capabilities to manage apps.
Check apps and their versions
On the App management page, you see an overview of all apps in the current project.
Select Needs attention to view only apps that need action, for example, because of vulnerabilities or a lack of certification.
Select an app to see all of its versions. For each version, you see:
- Status. Whether the version is a draft, published, active, deprecated, or archived. See How version statuses connect.
- Certification status. Which signatures the version has. See Certification status.
- Vulnerabilities. The packages with vulnerabilities, their severity, whether each package is a runtime dependency or a dev dependency, and the patched package version when one is listed. A runtime dependency is a package the running app needs. A dev dependency is a package used to build the app.
- Builder signature. Whether the signature is valid, when it was created, and who created it.
Manage app versions
Every version has a status, such as draft or active. You change a version’s status with version actions. For how builders create, sign, and deploy versions, see About the Flows custom app lifecycle.How version statuses connect
The diagram shows how a version moves from one status to another, and which action moves it. A typical version moves through these statuses:- Draft. A builder deploys a new version. Users don’t see it in Custom apps.
- Published. You publish the draft, and the files are locked. Publish a Certified version. In a project with Dev status, you can publish a Builder certified version. Users still don’t see the version in Custom apps.
- Active. You activate the published version. It replaces the previous active version, which goes back to Published. Users now see this version in Custom apps.
- Deprecated. Deprecate a published version when you no longer want anyone to activate it. If that version is active, deactivate it first. Deprecating is permanent.
- Archived. Archive a draft or deprecated version to keep it for audits. You can’t activate an archived version.
Publish and activate a version
After a builder deploys a new version, it arrives as a draft. Users keep the current active version until you activate the new one.1
Find the app
On App management, search for the app. A new app shows No active version until you activate one.
2
Check the draft
Select the app, then select the draft. Check its certification status and vulnerabilities.
3
Publish the version
Select Publish.
4
Activate the version
Select Activate to replace the current active version for all users.
5
Confirm the result
In the list on App management, check that the active version is the one you activated.
Certification status
The certification status shows which signatures a version has, and that status decides where you can publish it. For how a builder gets the signatures, see Certifying a Flows custom app for production.
You can publish a Builder certified version only in a project with Dev status. In every other project, including production, you publish a Certified version. Until Cognite certifies a builder-signed version, users see a 14-day warning, except in projects with Dev status.
You can publish a Certified version in the project that the signatures cover, including production.
You activate a version only after you publish it. The builder adds a signature to a Not certified version before you can publish it. See About the Flows custom app lifecycle.
Check vulnerabilities
In the app list, vulnerability counts apply only to the active version. To check another version, select it.Severity levels
Each vulnerability has a severity that shows how much harm it could cause if someone exploited it. The severity comes from a score from 0 to 10 in the Common Vulnerability Scoring System (CVSS) v3, an industry standard for rating vulnerabilities.
Severity doesn’t tell you whether a vulnerability is easy to exploit, or whether attackers already exploit it. Look first at vulnerabilities that are known to be exploited.
Respond to vulnerabilities
- Before you activate a version, check its vulnerabilities. If it has critical or high vulnerabilities in runtime dependencies, ask the builder to fix them first.
- If the active version has critical vulnerabilities, activate a newer published version that fixes them. If there isn’t one, contact the builder. If a patched package version is listed, ask the builder to update that package and deploy a new version that you then publish and activate.
- If you need to stop users from opening an app right away, deactivate the active version. Users can’t open the app until you activate another version.
Further reading
- Custom apps — Where users open the active version.
- Building Flows custom applications — How builders create and deploy an app.
- About the Flows custom app lifecycle — Draft, published, signing, and rollback.
- Deploying Flows custom apps — Deploy a version to a CDF project.
- App management capabilities — Capabilities you need to manage Flows custom apps.
- Certifying a Flows custom app for production — Certify a version before production publish.