app.json is one of the json file which is used in developing AL applications, app.json file includes all the configurations regarding the app, it includes the name of the app, publisher, version and dependencies etc.
In this blog we will go through each of the property of app.json file
id: Each extension/app which is built on top of business central will have a unique app id.
name: This property represents the name of the app that we are building, here you can give the name of the extension that you are building.
publisher: Publisher is someone who owns the app, either it can be a developer or an organization which has developed the app.
version: Version of the gives us the idea of what version does the app currently have, we have to update the version for each new release/ update of the extension. This versioning can be done according to your convenience.
brief: Here you can give brief about what is your app about.
description: You can give description of your app here, what functionality does your app achieve.
privacyStatement: URL to the privacy statement for the extension.
EULA: URL to the license terms of the extension/app
help: Here you can give the link of documentation or related information regarding the extension/app.
url: This URL can be a link to an advertising page for your app, a page describing the features and additional resources other than troubleshooting and help.
logo: Here you can give the link of your logo
dependencies: When we are building the apps on top of business central that means our extension is depending on business central for symbols, in a same way we can built extensions on top of other extensions, if the extension that you are building depends on other extension then you need to mention all those extensions in dependencies.
platform: Usually when we download symbols, two type of apps will be downloaded in the file .alpackages those are system application and base application.
If you are using the objects of system applications then you need to specify the platform property.
application: Here you need to specify the base app(Business central) version.
idRanges: Each extension/app that we are building will have certain objects, for each object we need an id, the id range that we are using for this specific extension can be specified here.
resourceExposurePolicy: By using this policy you can make sure, whether some one should be able to debug, download source code, etc. This is mainly useful for security purposes.
runtime:
The version of the runtime that the project is targeting. The project can be published to a server that supports the same or a higher runtime version. The available options are:
1.0 - Business Central April 2018 Release
2.0 - Business Central Fall '18 Release
3.0 - Business Central Spring '19 Release
4.0 - Business Central 2019 release wave 2
5.0 - Business Central 2020 release wave 1
6.0 - Business Central 2020 release wave 2
6.1 - Business Central 2020 release wave 2 update 17.1
6.2 - Business Central 2020 release wave 2 update 17.2
6.3 - Business Central 2020 release wave 2 update 17.3
6.4 - Business Central 2020 release wave 2 update 17.4
7.0 - Business Central 2021 release wave 1
7.1 - Business Central 2021 release wave 1 update 18.1
7.2 - Business Central 2021 release wave 1 update 18.3
8.0 - Business Central 2021 release wave 2
8.1 - Business Central 2021 release wave 2 update 19.1
9.0 - Business Central 2022 release wave 1
9.1 - Business Central 2022 release wave 1 update 20.1
9.2 - Business Central 2022 release wave 1 update 20.4
10.0 - Business Central 2022 release wave 2
features: If your extension is targeting other localizations also, because Business Central supports multiple localizations, to translate all the captions, labels etc, you can use this features property.
Comments
Post a Comment