For the managed package runtime, Adobe Experience Manager is a web deployment option for Omniscript. AEM can be useful for keeping your Omniscripts in line with your organization's designs and implementing custom elements and behaviors for use across Omniscripts presented by your AEM Instance.
This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.
- Setting Up and Configuring Adobe Experience Manager to use with Omniscript (Managed Package)
For the managed package runtime, Omniscript can be deployed to the web using Adobe Experience Manager. - Connecting Salesforce Cloud Services with Adobe Experience Manager (Managed Package)
For the managed package runtime, after setting up and configuring Adobe Experience Manager to use with Omniscript, connect AEM to Salesforce. - Adding a Local Omniscript Definition to Adobe Experience Manager (Managed Package)
For the managed package runtime, to obtain a local definition of an Omniscript and store it in Adobe Experience Manager the Omniscript JSON must be saved and stored locally before being loaded into Adobe Experience Manager. - Add Omniscript to a Page in Adobe Experience Manager (Managed Package)
For the managed package runtime, to use Omniscript as a paragraph component in Adobe Experience Manager, it is first necessary to ensure that the Omniscript page exists in Salesforce or a locally defined Omniscript has been added to Adobe Experience Manager. Once the Omniscript is confirmed in Salesforce or locally defined, you can create a page in AEM that uses Omniscript. - Reference Local Assets in Adobe Experience Manager (Managed Package)
For the managed package runtime, asset references must be made manually while building an Omniscript. Learn how to add local asset references to radio or multi-select elements. - Creating Custom Angular Templates for Adobe Experience Manager (Managed Package)
For the managed package runtime, Omniscript is built on the AngularJS framework and leverages templates to display different elements and objects. Custom templates saved in Adobe Experience Manager can be used to replace specific instances of elements to tweak how they display and add additional functionality. - Creating Custom JavaScript and CSS for Adobe Experience Manager (Managed Package)
For the managed package runtime, in Adobe Experience Manager, client-side code such as stylesheets and JavaScript are handled by a system of Client Libraries. To simplify customization, we have included a clientlib that is loaded by the Omniscript components. This removes the need for customers to create and manage custom Omniscript components manually for instance-wide customizations. This clientlib can be found at /apps/vloc/clientlibs/ooutCustom.