Documentation
Glossary
Item
A collective term for Applications, Portal Pages, and Automations.
Asset
A component or module.
Commit
The action of saving a new version of an item, along with a snapshot of its current state and referenced component/module versions, into the Flow Connect Hub.
Application Service Overview
This service enables users to bulk commit and deploy hub items which includes; Applications, Portal Pages, and Automations that are dependent on shared components or modules.
There are two methods of bulk committing:
Dependency Update
Identify all highest‑level dependencies of a component/module, then commit and deploy those dependencies to reflect the latest changes.
Best for:
Components/modules reused across many applications, automations, or portal pages
Fast rollout of shared asset changes
Package Update
View all items in a selected package and choose which items to commit.
Best for:
Hanlding grouped changes within a specific package
Selectively committing and deploying applications, automations, or portal pages within an application package
Dependency Update vs Package Update: Comparison
Primary driver
Selected component or module
Selected package
Asset selection required
✅ Yes
❌ No
Item source
Across packages
Single package
Ideal use case
Updating reused assets
Managing package changes
Typical item count
Variable, asset‑driven
Package‑bounded
Key Functionalities
Commit Applications and Portal Pages
Commit and Deploy Applications and Portal Pages into one or more environments
Commit and deploy Automations into one or more environments
Workflow
1. Select Organization
Choose the organization from the “Organization” list selection menu.
Then select one action:
Dependency Update – Update and commit items that depend on a selected component or module.
Package Update – Update and commit items in a selected package.
2. Select Application Package
Choose a package from the Application Libraries list selection menu.
3. Select Asset (Dependency Update Only)
Choose a component or module from the Assets list selection menu.
Assets are grouped by components and modules
4. Items to Commit
4.1 Select Items to Commit (List Multi Selection Input)
Displays items dependent on the selected asset (Dependency Update)
Displays items in the selected package (Package Update)
Items are grouped by type:
Applications
Portal Pages
Automations
For each item, the following details are shown:
Source package (Dependency Update only)
Last committed version in Dev (author and date)
Last deployed version per environment (or None)
All items are selected by default and can be deselected.
4.2 Uncommitted Items (List Presentation)
Items with changes since the last commit cannot be committed.
Displayed in a separate list
Can be exported as a CSV file
Available Actions
Back – Go back to the previous step
Export To CSV – Download the list of items uncommitted items.
Commit Only – Proceeds to the next screen with the items you want to commit.
Automations cannot be included
Warning shown if automations are selected
Commit & Deploy – Proceeds to the next screen with the items you want to commit & deploy.
5. Commit Only/Commit & Deploy
5.1 Selected Applications (List Presentation)
Displays the list of selected Application items along with the assets used by each item.
For each asset, the following information is shown:
Currently used: The asset version used by the last committed version of the item
Will be updated to: The latest committed version of the asset that the item will be updated to reference
5.2 Selected Portal Pages (List Presentation)
Displays the list of selected Portal Page items along with the assets used by each item.
For each asset, the following information is shown:
Currently used: The asset version used by the last committed version of the item
Will be updated to: The latest committed version of the asset that the item will be updated to reference
5.3 Selected Automations (List Presentation)
Displays the list of selected Automation items along with the assets used by each item.
For each asset, the following information is shown:
Currently used: The asset version used by the last committed version of the item
Will be updated to: The latest committed version of the asset that the item will be updated to reference
5.4 Items With Errors (List Presentation)
Displays a list of validated items that contain compile-time errors and therefore cannot be committed. You can click “Export To CSV” to export these items to an excel file for download.
Available Actions
Back: Go back to the previous step
Export To CSV: Download the list of items with errors.
Enter Commit Message: Proceeds to the next screen to enter a commit message for the selected items.
6. Enter Commit Message/Select Environments
6.1 Commit Message (Text Input)
Enter a commit message that will be saved when committing the selected items.
This field is required
The commit cannot proceed if this field is left empty
6.2 Select Environment (Multi-List Selection)
(Commit & Deploy only)
Select one or more environments to deploy the selected items to after the commit is completed.
At least one environment must be selected
If no environment is selected, an error message will be displayed prompting you to select at least one
This multi-list selection is shown only when the Commit & Deploy option is chosen
7. Confirmation
Selected Items (List Presentation)
Displays a final confirmation view of the items that will be:
Committed, or
Committed and deployed, depending on the selected action
The selected items are grouped by their type and include the following details:
Last committed version
Last committed date
Author of the last commit
Deployed versions (if applicable)
8. Post-Commit/Deploy Screen
Download Item Summary (File Gallery)
The final screen displays a confirmation message: “Item(s) Have Been Committed (& Deployed)”
From this screen, you can download an Item Summary Excel file containing detailed information about all items that were committed and/or deployed, including:
Item details
Previously committed versions
Previously deployed versions
New committed versions
New deployed versions
Assets used by each item and their respective versions
After reviewing or downloading the summary, you can:
Exit the application, or
Click Back to Item Selection to return to the package/dependency item selection view
Limitations
This application service has the following functional limitations:
When we commit an item with dependent assets, it will point to the latest versions of all assets used by the respective item. However, it does not commit the dependent assets themselves used by the item to a newer version automatically, when the item is committed.
Items cannot be deployed only; you can either:
Commit items, or
Commit and deploy items
Any changes made to modules that might cause a runtime error in its dependencies will not be validated in the bulk commit app. Modules will not work with the error validation process so please proceed with caution.
The application service cannot be used to resolve or fix item errors.
Items cannot be reverted to a previously committed version or roll back changes.
Automations cannot be committed only. They can only be committed and deployed
Error validation is limited to compile-time errors; runtime errors are not checked through this service.
Asset versions cannot be updated selectively; all assets of an item are updated to their latest versions together, when an item is committed.
Last updated
Was this helpful?