On this article, I will explain some addition features that are integrated within the creation of your Launch extension.
Those features are less developed in our case because they don’t require a lot of customization usually.
You can, obviously, develop these features into more advanced use-cases but this is not a must to know and develop.
Extension.json
This element is at the root of your Extension folder and contains all of your extension path and details of your extension.
In this manifest, you can change the name of your extension, its description and configuration.
It is important that this manifest is up to date before you are creating your package for the upload.
Every time that you are uploading a new version, make sure that you increase your versioning in your manifest. This will trigger the possibility to upgrade the Extension.
There is a clear description of what is possible to be configured on this file available on the Launch Developer website : https://developer.adobelaunch.com/extensions/reference/extension-manifest/
For this file, if it is not required to be modified, it is very encouraged to be checked and the documentation read.
Icon for Extension
One of the possible modification within the extension.json, is to add the path to the icon of your extension. The icon represents your graphical identity, you may want to have some thought on which design or color to use. The icon has to be on the svg format.
In order to change that, you would just need to add your path to your icon within the file :
"iconPath": "resources/icons/myIcon.svg",Turbine Free Variables
The turbine free variables are quite important as you may have noticed when we were coding the different part of our extension. These variables are available only on runtime. This means that they can be accessed in your .js files only!
Those variables provide information and utilities specific to the Launch runtime and is always available to library modules.
There is a complete description of their possibilities here : Turbine Free Variables
However we will cover the most important ones:
- turbine.getDataElementValue(name: string) : return the value of a Data Element
- turbine.getExtensionSettings() : returns the object set by your extension settings.
exchangeUrl
In the case that you are publishing a public extension, you would need to register to Adobe Exchange in order to give a proper page information about your Extension.
Within the exchangeUrl, you will give the URL of your extension’s listing on Adobe Exchange.
Core Module functionalities
Adobe reactor engines provide a list of functionalities that you are able to use within your extension. Those are some helper methods, if you would like to realize some operations, they can be handy.
Complete list is available here : Launch Core Module Functions
Here what kind of operation, they can help you realize :
- Set or Read a cookie (@adobe/reactor-cookie)
- Read queryString (@adobe/reactor-query-string)
- Read document information at runtime (@adobe/reactor-document)
- Use a promise (@adobe/reactor-promise)
You can see in the action module that I use one of the core component to display a console where you can save your comments.
I hope that this is giving you a good overview on what is available.
It is quite difficult to cover the full range of functionalities provided but it would not have been complete if I didn’t mention those functionalities.
On this series of articles, you may be interested in these topics :
| Article | Content |
| Introdcution to Adobe Launch & Extension Creation | This posts covers the basic of what you need to know in order to start with this series of articles. |
| Architecture and dependencies within modules | This posts covers the architectures and how the different modules are linked between each others |
| Global Extension Configuration | This article explains how to set up your configuration HTML file. It is the core configuration module of your extension. |
| Event type module | This article will show you how to build an event module. Every module will have a configuration part (HTML) and wrapper(JS). |
| Condition module | This article will show you how to build a condition module. |
| Action module | This post will be related to the action module and how to build it. We will also see how you can actually import some cool feature of the launch library. |
| Data Element module | This article will be developing the possibilities of the Data Element module |
| Shared module | This article will focus on the shared functionality that you can write and share with other extension developpers to used. We will also used a feature shared from Adobe Analytics to show you how to use it. |
| Other features | The other features that are related to Launch Extension. I will cover additional (and important) information there. |
| Testing your extension | How do I debug my Extension ? |
| Releasing and updating your Extension | How do I publish my Extension into Launch ? And after, how do you update it ? |