Public Distribution
Distribute apps to anyone on Adobe Exchange.
Overview
Publicly distributed apps are available for any Adobe organization to install and can be accessed via Adobe Exchange. These apps are submitted via Adobe Developer Distribution and reviewed by Adobe. See below for configuration options and required steps to prepare your app for public distribution.
Customer configuration
Developers of publicly distributable apps can define configuration options for customers to set at install time.
Defining customer configuration options
Customer configuration can be defined via the configSchema
property.
app.config.yaml
Copied to your clipboardapplication:<application config>extensions:<extension configs>configSchema: # This is a top-level property and is global to the app and all extensionstitle: 'the title'description: 'the description'properties:- title: 'Slack Webhook'type: 'string'description: 'Please provide the webhook used by this application. Configure in slack.com'envKey: 'SLACK_WEBHOOK'
Usage
The envKey
property of a customer configuration option maps to the environment variable name in the app.
Runtime action
To use customer configuration in a Runtime action, map the envKey
value for the desired variable to the inputs of the Runtime action, then access values via params.<envKey>
in the action code.
app.config.yaml
Copied to your clipboardconfigSchema:title: 'the title'description: 'the description'properties:- title: 'enable caching'type: 'boolean'envKey: 'IS_CACHING_ENABLED' <--- Environment variable nameapplication:actions: actionsweb: web-srcruntimeManifest:packages:dx-excshell-1:license: Apache-2.0actions:generic:function: actions/generic/index.jsweb: 'yes'runtime: nodejs:16inputs:LOG_LEVEL: debugIS_CACHING_ENABLED: $IS_CACHING_ENABLED <--- Mapped environment variableannotations:require-adobe-auth: truefinal: truecode-download: true
Action code
Copied to your clipboardasync function main (params) {if (params.IS_CACHING_ENABLED) {enableCache()}}exports.main = main
Web application
To use customer configuration in the web application, values can be accessed directly via process.env.<envKey>
.
app.config.yaml
Copied to your clipboardconfigSchema:title: 'Configurable Web App'description: 'Web application that can be configured.'properties:- title: 'Frontend background color'type: stringdescription: 'Please provide the background color for your frontend'enum:- blue-400- celery-400- indigo-400envKey: FRONTEND_BACKGROUND_COLOR <--- Environment variable nameapplication:web: web-src
Component.js
Copied to your clipboard<View backgroundColor={process.env.FRONTEND_BACKGROUND_COLOR}></View>
Customer configuration types
Text field
Copied to your clipboardconfigSchema:title: 'Configure your application'description: 'Set configurable variables for this Slack application'properties:- title: 'Slack Webhook'type: 'string'description: 'Please provide the webhook used by this application. Configure in slack.com'envKey: 'SLACK_WEBHOOK'default: 'https://slack.com/webhook'
Checkbox
Copied to your clipboardconfigSchema:title: 'Configure your application'description: 'Customize this application to meet your needs.'properties:- title: 'Enable caching'description: 'Determines whether or not the app caches.'type: 'boolean'envKey: 'IS_CACHING_ENABLED'
Dropdown
Copied to your clipboardconfigSchema:title: 'Configurable Web App'description: 'Web application that can be configured.'properties:- title: 'Frontend background color'type: stringdescription: 'Please provide the background color for your frontend'enum:- blue-400- celery-400- indigo-400envKey: FRONTEND_BACKGROUND_COLOR
Secret
Secret screenshot pending bug fix
Copied to your clipboardconfigSchema:title: 'the title'description: 'the description'properties:- title: 'aws secret key'type: 'string'secret: trueenvKey: 'AWS_SECRET'
Multiple configuration options
Copied to your clipboardconfigSchema:title: 'Configurable Web App'description: 'Web application that can be configured.'properties:- title: 'Frontend background color'type: stringdescription: 'Please provide the background color for your frontend'enum:- blue-400- celery-400- indigo-400envKey: FRONTEND_BACKGROUND_COLOR- title: 'Enable caching'description: 'Determines whether or not the app caches.'type: 'boolean'envKey: 'IS_CACHING_ENABLED'- title: 'Slack Webhook'type: 'string'description: 'Please provide the webhook used by this application. Configure in slack.com'envKey: 'SLACK_WEBHOOK'default: 'https://slack.com/webhook'
Required products
Developers of publicly distributable App Builder apps can define Adobe products that are required for their apps to work properly.
See the Discover and Acquire sections of the distribution documentation for more details on how these options surface to customers.
Defining required products
Required products can be defined via the productDependencies
property.
app.config.yaml
Copied to your clipboardapplication:<application config>extensions:<extension configs>configSchema:<customer configuration>productDependencies:- code: AEPminVersion: 0.0.0maxVersion: 1.0.0
Valid products
- AEM - Experience Manager
- AAM - Audience Manager
- ANLYTC - Analytics
- CMPGN - Campaign
- TRGT - Target
- AEP - Experience Platform Services
- COMMC - Commerce Cloud
- MRKTO - Marketo Engage
- WRKFRNT - Workfront
- AAC - Advertising Cloud
- RTCDP - Real-time Customer Data Platform
- AJO - Journey Optimizer
- CJA - Customer Journey Analytics
Product version information can be found on Adobe Experience League.
Packaging for developer distribution
Once you've configured your app for public distribution, it's time to upload it to Adobe Developer Distribution. Before you do that, you will need to package it.
The aio app pack
command will verify and bundle your app. In the root of your app folder, run this command:
Copied to your clipboardaio app pack
After this command completes, you can find the app package in your app folder as: dist/app.zip
.
Continue to the Adobe Developer Distribution documentation for details on how to upload your package.
Validation
When a developer uploads a package to Adobe Developer Distribution, the following validations are performed:
app.config.yaml
- will be checked if it's in a valid format, and will show specific config errors for you to fix, if necessary
package.json
version- application version format must be
X.Y.Z
, where X, Y, and Z are non-negative integers
- application version format must be
- files to be packaged. All the files in your app folder will be packaged EXCEPT:
- files specified in
.gitignore
- files specified in
.npmignore
- any
dist
folders - any dot files (.env, .gitignore, etc)
- any OS junk files (.DS_Store, thumbs.db, etc)
- files specified in
- event registrations will be validated (if any)
Hooks
Two hooks are available to customize the packaging step:
pre-pack
- runs before packagingpost-pack
- runs after packaging
Your hook handler function will be passed two items:
appConfig
(object) - this contains the config of the current applicationartifactsFolder
(string) - this will be the location of the folder containing all the packaging artifacts that will be bundled