Loading...wait
The Application Dependencies workbook allows you to import dependencies in bulk.
You can map either applications directly or via interfaces.
The workbook will export any existing data.
| Sheet | Description |
| Applications | A list of composite application providers in the repository |
| Application Modules | A list of application providers in the repository |
| App Pro Interface | A list of application provider interfaces in the repository |
| Interface Exchanged | A list of information representations which are used to describe what information is flowing between applications. Note, you can map these to information views (using the implements_information_views slot) and then to data objects via the information views, if required. In Cloud/Docker you can also use the application editor to do this. |
| Application Dependencies XXYY | A list of the dependencies between composite applications and the information passed
between them. Note, you will require a separate row for each different type of information.
You can add method and timeliness or leave them blank Note: Use the correct tab to map variations, e.g. Composite Application (CA) to Application Provider (AP) is the sheet ending CAAP (CA to AP), CACA, APCA or APAP. |
| App Interface Dependencies XXYY | A list of the dependencies between composite applications that use an API, and the
information passed between them via the API. The information exchanged may differ
on either side of the API. Note, again you will require a separate row for each different
type of information. You can add method and timeliness or leave them blank. Note: Us the correct sheet to map the interface |