Application Management
What this screen is for
Where applications live once created: drafts and published versions, loading one for editing, publishing a new version, and deleting.
Before you start
| To do this | You need |
|---|---|
| Open App Builder | the App Builder access permission |
Opening it
The Applications tab in the tab bar.
πΈ Screenshot Placeholder: The Applications tab. Mark: (1) the Drafts/Published status tabs, (2) the search box, (3) an application card, (4) the New App button.
Applications Panel
The Applications tab displays all applications you have access to, organized by status.
| Element | Description |
|---|---|
| Header | Title, description, and βNew Appβ button |
| Search Box | Filter by name, description, or tags |
| Status Tabs | Toggle between βDraftsβ and βPublishedβ views |
| Application Grid | Cards in a 3-column layout |
Application Cards
Draft cards show: name, βDraftβ badge, description, created/updated dates, version, tags, and action buttons (Edit, View, Delete).
Published cards show: name, βPublishedβ badge, description, published date, publisher, owner group, version chips, tags, and action buttons (visibility based on permissions).
Permissions
Draft applications β all actions (Edit, View, Delete) are available to the creator. Drafts are only visible to their creator.
Published applications β visible only to members of the same group as the publisher:
| User Role | Edit | View | Delete |
|---|---|---|---|
| DevOps role (Publisher) | Yes | Yes | Yes |
| DevOps role | Yes | Yes | No |
| Developer role | No | Yes | No |
Note: The Administrator role (admin) has full permissions and can edit, view, and delete all published applications.
Loading an Application for Editing
Click βEditβ on an application card. The canvas loads with all components and connections, and the header shows the app name, status, and version.
| Status | Behavior |
|---|---|
| Draft | Edit freely and save changes via βSaveβ or βSave Draftβ |
| Published | Edit and publish as a new version (βSaveβ button is disabled) |
Viewing Application Details
Click βViewβ on an application card. The App View Drawer slides in from the right, showing:
- Header with name, status, and description
- Version selector (published apps β dropdown to view different versions)
- Architecture preview (visual canvas)
- Metadata: created date, updated date, version, owner group
- Tags and detailed component configurations
Creating a New Application
- From Applications panel: Click β+ New Appβ
- From App Designer: Click the βRefreshβ button to clear the canvas
App Header
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β [App Name] [Draft/Published Badge] [Version] [Action Buttons] β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
| Button | Description | Enabled When |
|---|---|---|
| Save | Quick save for existing drafts | Has changes, is draft |
| Refresh | Clear canvas for new application | Canvas has nodes or app name is set |
| Save Draft | Open save dialog | App name is set and has nodes |
| Publish | Open publish dialog | App name is set, has nodes, has permission |
Saving as Draft
Drafts are work-in-progress applications visible only to the creator.
- Design your application and enter an App Name
- Click βSave Draftβ
- Optionally add a description and version (default:
v1.0.0) - Click βSaveβ
The application appears in your βDraftsβ tab. For subsequent edits to an existing draft, use the βSaveβ button for quick save.
Publishing
Publishing makes the application visible to your team and creates an immutable version.
Prerequisites: publish permission, an app name, at least one component on the canvas.
- Click βPublishβ
- Enter a version (required) and optionally a description
- Click βPublishβ
Published versions are locked, visible to group members, and trigger notifications.
Version format: Semantic versioning is required (e.g., v1.0.0, 1.2.3, v2.0.0-beta, 1.0.0-rc.1).
Re-publishing (New Version)
Load a published app via βEditβ, make changes, then click βPublishβ with a new version number. Previous versions remain accessible in version history. The βSaveβ button is disabled β you must publish to persist changes.
Deleting Applications
Deleting a Draft
Click the delete icon on the draft card and confirm. This is permanent and cannot be undone.
Deleting a Published Application
Only the original publisher can delete. A version selection dialog appears with options to:
- Select specific versions to delete
- Delete All to remove the entire application
If deleting versions that were run locally, the Fenwave Agent cleans up local data (containers, volumes, etc.).
Scenario
Shipping a change to an application your team already uses.
- Applications tab, Published view. Find it β search matches name, description and tags.
- Load it for editing. You are now editing a copy of a published version, not the live one; nobody sees your changes yet.
- Make the change and save as draft. Draft is the right state while you are still deciding, and it notifies nobody.
- Review what changed before publishing. Publishing creates a new version and tells the whole team β see Notifications.
- Publish. The version increments and the team is notified.
- If it was wrong, publish a corrected version rather than deleting. Deleting a published application removes it for everyone who was using it.
When it doesnβt work
| Symptom | Cause | How to check | Fix |
|---|---|---|---|
| An application is missing from the grid | The Drafts/Published toggle, or a search filter | The status tabs | Switch views; clear the search |
| You cannot delete an application | Deletion is permission-gated | Access Explorer | Ask for the permission |
| Publishing did not notify anyone | Saving a draft does not notify; only publishing does | The status badge | Publish rather than save |
| Editing a published app changed nothing live | You are editing a draft copy until you publish | The status badge | Publish the change |
Next
- Notifications β what the team sees