Create an app for external content

Apps that are designed to load external content when a ViewApp starts must be able to recognize a URI. App developers also need to include a list of the Media Types that can be serviced by the app. An app's supported media types must be specified in an AppManifest.xml file. For more information about specifying media types in the AppManifest.xml file, see the AVEVA OMI Developer Guide.

Note: When there is more than one application in a Galaxy capable of servicing a specific media type, the more recent imported application will be used by the ViewApp.Users cannot select an application for a media type.

After importing the app, these Media Types will be added to an internally maintained Media Types registry. Panes will refer to this registry when trying to open External Content. The app that services the Media Type associated to the External Content will first be launched and then the external content loaded.

The overall steps in the workflow to import an app are described in the following list.

1. Create an AVEVA OMI app that recognizes a URI and supports one or more defined media types.

2. Enclose the app in an ArchestrA aaPKG file and export it to a location accessible to your development computer.

3. Open the System Platform IDE.

4. Import an app in an aaPKG file that is designed to load and display a specific type of external media.

5. Create an External Content item.

6. Edit the External Content item.

   The Media Type field of the External Content item lists the media types supported by the imported app. The External Content editor must be closed and reopened if an app containing an unrecognized media type is imported while the External Content editor is open. Reopening the External Content editor lists the new media type.