Version Details
The Version details page opens after selecting the BAP's starting point, which is the app and branch, and the type of compilation.
The page's toolbar displays the name of the app and branch selected, the last generation date and the user that generated the app, and the last update date with the user involved.
Validations
If Studio validates that the selected branch was never published, you will see an error message in red next to the toolbar and the Continue button will be blocked. You will not be able to continue the creation process until you generate and publish the branch and test the app.
Keep in mind that, prior to generating a package, the app needs to be tested and validated.
In the Version details page, you will also find details about the dependencies included in the BAP, divided by back and front-end dependencies.
This section details the Global transactions logic repository, which is the only transactions repository enabled in each environment, the branch used, and the date it was last updated.
Validations
If Studio validates that the transactions in use are not published, you will see a chip with the transaction pending publication message. You will not be able to continue the creation process until you publish the pending transactions, since this might mean that the transactions were not tested.
Hover over the message and click the Info icon that appears to see a list of transactions pending publication, or click the Open in new tab icon to access the transactions repository in the selected branch.
This section details all the dependencies in use within the generated BAP with the branch used and the date it was last updated.
Validations
If Studio validates that there are crossed dependencies, that is, a module or repository is being invoked more than once but pointing to different branches, you will see a chip with the cross dependency message.
Hover over the message and click the Info icon that appears to see the dependencies diagram, or click the Open in new tab icon to access the dependency in the selected branch.
To avoid generating a broken package, you will not be able to continue the creation process until you fix the crossed dependencies issue.
Click the Go to button in the toolbar to access the BAP's branch of origin.
Fix the app's dependencies so that, if a same module and repository is being used more than once, it points to the same branch.
Return to the BAP creation screen and click the refresh icon. The warning should disappear, and the Continue button should appear enabled.