Application Lifecycle

This article describes how applications are created, installed, updated, and removed in Flowlu, and what information is available to applications at each stage.

Lifecycle events and notifications

At this time, applications do not receive incoming webhooks or notifications for lifecycle events such as:

• installation,

• update,

• deinstallation.

Application management in the Developer Console

In the developer account, the following actions are available:

• create an application,

• edit application details,

• activate or deactivate an application,

• publish or hide an application in the Marketplace,

• delete an application,

• create a new application version,

• edit a version,

• activate or deactivate a version,

• submit a version for moderation,

• publish or hide a version via status change,

• install a version into the current account,

• install a version into another account using an install link.

Installed application behavior

After an application is installed into a Flowlu account, administrators can:

• uninstall the application,

• assign access by user roles and groups,

• change application-level settings,

• change user-level settings.

Applications can be embedded into multiple areas of the Flowlu interface, as defined in the application manifest.

Data available to the application at runtime

When an application is rendered in the interface, its endpoint receives:

• protocol type (http / https),

• account domain name (for example: my_company.flowlu.com),

• user interface language code (es, en, etc.),

• integration point type and unique integration ID (from the manifest),

• application unique identifier,

• application version number
  (for private apps, this is always 1.0.0).

Using the Flowlu JS SDK, the application can additionally:

• obtain access and refresh tokens for the current authenticated user,

• read application settings,

• read user-specific settings,

• perform API requests within the permissions declared in the manifest,

• display interface elements such as notifications, alerts, modals, side panels, and navigation actions.

Application removal (deinstallation)

When an application is removed from an account:

• application settings and user settings are deleted,

• files stored in application settings are deleted,

• webhooks registered by the application are removed,

• role and group assignments are removed,

• the application is no longer embedded in the interface.

Application deletion by the developer

When an application is deleted in the developer account, the same removal process is executed for all accounts where the application is installed.

Application updates

When an application is updated:

• the previous and new manifests are compared,

• webhooks are updated according to the new application manifest:

  • obsolete webhooks are removed,

  • new webhooks are registered if defined,

• application settings, roles, and files are preserved,

• the application stops rendering in integration points removed from the manifest,

• the application starts rendering in newly added integration points.