Meta Definition

Kevin declares the structural components in the APP-META.xml file based on the resource model of the application.

Input

• APS resource model

• User scenarios

• Information Architecture data including:

  • Application ID - unique URI that is not allowed to change in the subsequent updates

  • Application name - any short name

  • Application version - version of the cloud application

  • Icon presenting the application brand

  • License agreement - text file or URL

Development Process

Make sure the following data is declared:

• General properties using the additional input data mentioned earlier.

• Presentation components using user scenarios and additional input data. Declaration of navigation trees influence the development of the user interface.

• Services using the designed APS Resource Model. This declaration influences the development of the backend provisioning logic.

Declaration of navigation trees for the provider control panel (PCP) is considerably different from the ones for UX1. In the former case, it is based on the CP environment whereas in the latter case the UX1 is preferable. Respectively follow these documents:

• Navigation document explains navigation concepts and details for CP.

• Navigation specifics explains navigation specifics for UX1.

For example, in UX1, in addition to regular views (similar to views in CP), it is possible to declare:

• View-plugins to embed the application UI into dashboards of other applications

• Wizard views to embed into an own wizard (wizard host) or into a wizard of another application

• Wizard hosts to embed views from various applications

For each particular integration case, follow the Integration Points section.

Outcome

APP-META.xml file containing declaration of general properties, presentation objects, and services.

← Development

APS Types →