What's Included in a Business Application Package
A business application package contains the app’s configuration, which consists of the app’s front-end with its modules and business logic, and configurable transactions and business parameters, which conform the app’s back-end, and includes external services, lambda libraries and action libraries in use within the transactions.
Important
Transactions and business parameters included in a BAP are those detected as in use. This means that:
Transactions included in a BAP are those being referenced by lambda or legacy processes. Transactions invoked using other methods will not be automatically added to a BAP.
Business parameters included in a BAP are those being used within a configurable transaction by using the Business param action node. Those referenced in native transactions or using other methods will not be automatically added to a BAP.
If you are not sure whether a transaction or business parameter will be automatically included in a BAP, you can now force their inclusion when editing or creating them. To force a transaction or business parameter within a business application package, follow these steps:
Create or edit the transaction or business parameter in your branch.
Click the Force inclusion in BAP checkbox.
For transactions, scroll to the bottom of the Settings section on the left panel.
For business parameters, scroll to the bottom of the creation or edition pop-up window.
Save the entity to confirm changes.
Transactions and business parameters that are forced within a BAP are included in the package whether they are in use or not.