Manifest
Full reference of Manifest file.
Manifest is a simple JSON file that describes your App behavior and its possibilities.
To refresh the App Manifest, it has to be changed and reapplied - just like on App registration. Ergonode does not refresh it automatically.
Remember also, on refreshment, to raise the version - otherwise, changes won't be applied as described in the version restrictions description.
Contained fields:
name
A simple text describing under what name your app is visible in the Ergonode available Apps tab.
This value should allow easy identification of what your App does.
Restrictions:
has to exist and not be empty
the length of the name is limited to 30 chars and should be no less than 3 chars.
description
A simple text describing the purpose fulfilled by the App.
Restrictions:
has to exist and not be empty
the length of the name is limited to 200 chars and should be no less than 20 chars.
version
A semantic version of your manifest. It does not necessarily need to address your application version but rather the content of the Manifest file.
Restrictions:
has to exist and not be empty
when reapplying the Manifest for App update the changes may only be applied when the new version is higher than the existing ones - otherwise, changes will not take effect.
compatible
A semantic version that the current version of the Manifest is compatible with.
This allows Apps Engine to determine whether an App administrator should take action and reconfigure the App for the new needs - fill out previously not existing configuration fields etc.
So for instance if, on the App update, the compatible field is higher than the last version(i.e. compatible = 1.1.0 and last version = 1.0.0) of the App installations will be set in Configuration required status - implicating the need for action and disallowing following actions with an App.
Restrictions:
has to exist and not be empty
the value cannot be greater than the
versionfield
configuration_schema
A list of JSON schemas to allow building simple or multi-step configuration forms.
Detailed reference can be found here.
features
A list of predefined features App utilizes:
synchronization
Enables the ability to run synchronization via the App.
The synchronization is always run as delta via this feature - meaning only changes from the last synchronization will be sent to the App.
on first synchronization, all data state is being transferred to an App
on every following synchronization, the App receives only data that has changed from the previous execution
synchronization_full
Enables the ability to run full synchronization via the App.
All configured within App data is synchronized via this feature disregarding delta - which means the entire data state is transferred to the App on every synchronization.
This feature is always a secondary option in the Run synchronization split button if enabled together with synchronization.
synchronization_file_download
Claims that the App generates a file as the result of the synchronization - for the enabled feature every finished synchronization will receive a file download button within the right-hand menu as well as a Download last synchronization button in the main App menu
When this feature is enabled follow the File download endpoint reference.
synchronization_file_download_latest
This feature enables Copy feed URL button. This URL is publicly available, with no need for authorization.
When this feature is enabled follow the File download endpoint reference as for synchronization_file_download feature.
events
Events the App subscribes to. Available:
app_installed
App installed by the user in the Ergonode interface.
app_uninstalled
App uninstalled by the user in the Ergonode interface.
attribute_created
Attribute created.
Currently available only in the synchronization context.
In the synchronization context, the event also contains detailed updated payloads.
attribute_updated
Attribute updated.
Currently available only in the synchronization context.
attribute_deleted
Attribute deleted.
Currently available only in the synchronization context.
category_created
Category created.
Currently available only in the synchronization context.
In the synchronization context, the event also contains detailed updated payloads.
category_updated
Category updated.
Currently available only in the synchronization context.
category_deleted
Category deleted.
Currently available only in the synchronization context.
product_created
Product created.
Currently available only in the synchronization context.
In the synchronization context, the event also contains detailed updated payloads. It also represents the access granted event i.e. when the product is added to a segment.
product_updated
Product updated.
Currently available only in the synchronization context.
product_deleted
Product deleted.
Currently only available in the synchronization context.
In the synchronization context, it also represents the access revoked event i.e. when the product is removed from a segment.
synchronization_started
The new synchronization process started.
synchronization_ended
The synchronization process ended.
write_access
Claims that the App requires the write access to fulfill its purpose.
A user is notified of the request on App installation.
When installed the App can use Ergonode API write capabilities to manipulate the data.
Restrictions:
currently the field cannot be changed after the initial App registration
icon
Icon allows easy identification of the App within available and installed Apps.
Restrictions:
value has to be represented as a Base64 image i.e.
data:image/jpeg;base64,*value cannot be greater than 10 KB
url
Base URL under which the App is available. When not provided a host of the Manifest Url is taken as this parameter.
Restrictions:
a valid URL string
currently, the value of the field cannot be changed after the initial App registration
Example Manifest
Last updated
