The Application Identifier. Please see https://fdc3.finos.org/docs/1.0/appd-discovery#application-identifier. By convention this should be the same as your OpenFin UUID.
If you can't use your OpenFin UUID as the appId, then instead specify your application's UUID by adding an
appUuid property to the customConfig field.
Contact email address.
Additional config.
The OpenFin FDC3 service supports the following configuration values:
appUuid: Informs the service that the application launched by this manifest will have this UUID. By
default, the service will expect the UUID of the application to match the appId. This configuration value
can be used to override this.Any additional fields will still be accessible to applications (via APIs such as findIntent), but will not have any impact on the operation of the service.
Longer description of the app.
Icons used in the app directory display. A launcher may be able to use various sizes.
Images that can be displayed as part of the app directory entry. Use these for screenshots, previews or similar. These are not the application icons - use icons for that.
The set of intents associated with this application directory entry.
An application manifest, used to launch the app. This should be a URL that points to an OpenFin JSON manifest.
The manifest type. Always 'openfin'.
The machine-readable app name, used to identify the application in various API calls to the application directory. This may well be human-readable, too. If it's not, you can provide a title, and that will be used everywhere a name needs to be rendered to a user.
Name of the publishing company, organization, or individual.
The email address to send your support requests to.
The human-readable title of the app, typically used by the launcher UI. If not provided, name is used.
A short explanatory text string. For use in tooltips shown by any UIs that display app information.
The version of the app. Please use semantic versioning.
An application in the app directory.