<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Deepali Rathi on Medium]]></title>
        <description><![CDATA[Stories by Deepali Rathi on Medium]]></description>
        <link>https://medium.com/@drathi_10503?source=rss-894848436b99------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*X8Rq4sdvKvCM4d17r_C5AA.png</url>
            <title>Stories by Deepali Rathi on Medium</title>
            <link>https://medium.com/@drathi_10503?source=rss-894848436b99------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 23:51:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@drathi_10503/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[AEM Forms Supporting RTL Languages: Milestone in Global Accessibility]]></title>
            <link>https://medium.com/adobetech/aem-forms-supporting-rtl-languages-milestone-in-global-accessibility-60e309fa0e23?source=rss-894848436b99------2</link>
            <guid isPermaLink="false">https://medium.com/p/60e309fa0e23</guid>
            <category><![CDATA[aem-forms]]></category>
            <category><![CDATA[rtls]]></category>
            <dc:creator><![CDATA[Deepali Rathi]]></dc:creator>
            <pubDate>Thu, 28 Nov 2024 09:21:59 GMT</pubDate>
            <atom:updated>2024-11-28T09:21:59.258Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*78egNPffI5MlEB5Dp8tJLA.png" /></figure><p>In an increasingly globalized world, localization plays a pivotal role in creating inclusive digital experiences. Adobe Experience Manager (AEM) Forms has taken a significant step forward by introducing <strong>Right-to-Left (RTL)</strong> language support. This enhancement enables organisations to deliver forms in RTL languages such as Arabic, Hebrew, catering to diverse user bases and improving accessibility.</p><p>This blog delves into AEM Forms’ newly integrated RTL capabilities, covering the supported features, identified challenges, and recommended workarounds.</p><p><strong>Understanding RTL Support in AEM Forms</strong></p><p>AEM Forms allow forms to dynamically adapt their layout and content direction based on the locale. Languages such as Arabic and Hebrew, written from right to left, require specialised formatting. Without proper optimisation, web forms and interfaces may suffer from misaligned fields, incorrect text flow, and poor readability, leading to usability challenges and cultural insensitivity. AEM Forms addresses these issues by enabling RTL-compatible designs, significantly improving accessibility and user satisfaction.</p><ol><li>This feature is supported with Adaptive Form Core Components.</li></ol><p>2. This feature works on AEM Cloud as well on AEM Prem ( Core component version 1.1.40 +)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LMhe5OACUo6D6yPGpwVIYg.png" /></figure><h3><strong># Noteworthy RTL Supported Features</strong></h3><p>· <strong>Dynamic Rendering and Layouting </strong><br> Forms authored in English dynamically render in the RTL format based on the browser locale or the afAcceptLang parameter. Elements such as text fields, checkboxes, radio buttons, and labels are aligned properly for right-to-left reading, ensuring that users do not face confusion while filling out the form.</p><ul><li><strong>Error Messages and Validations (RegEx)</strong><br> Configured error messages for fields accurately reflect RTL languages, ensuring enhanced user comprehension. Validations, such as RegEx for Arabic characters, are also supported. Whether a user inputs incorrect data or misses a field, they’ll receive feedback in a manner that aligns with their language’s directional rules, enhancing clarity and usability.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t_WWL2hGrem8A2rD4hIxpw.png" /></figure><ul><li><strong>Date Formatting</strong><br> The DatePicker component supports RTL formats, translating day names (e.g., Sunday to its RTL equivalent) while preserving numerical consistency.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/708/1*Rvz9RjmCdGMDk1NOVOM28Q.png" /></figure><ul><li><strong>Themes</strong><br> Businesses can customize their form themes to match the aesthetic requirements of their brand while ensuring RTL compliance. The visual consistency is maintained, making sure that forms look polished and professional regardless of the language. The <strong>Canvas theme</strong> serves as a recommended reference for creating custom RTL-compatible themes.</li><li><strong>FDM Support for RTL Languages</strong><br> FDM (Form Data Model) supports RTL language characters such as Arabic and Hebrew, allowing for seamless data read/write operations to/from third-party APIs.</li><li>OOTB <strong>Dynamic Object Rendering (DOR)</strong> supports RTL Layout in AEM Cloud.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WRpv-ZiBQx5044BvheTmCw.png" /></figure><h3># How to Enable RTL Support in AEM Forms</h3><p>The documentation <a href="https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/forms/adaptive-forms-authoring/authoring-adaptive-forms-core-components/create-an-adaptive-form-on-forms-cs/supporting-new-language-localization-core-components">here</a> talks about the process to enable RTL support in AEM Forms in detail.</p><ol><li>Add your locale using OSGI Config — Guide Localisation Service.</li><li>Integrate client library to support the added locale ( sample client-lib is provided) .</li></ol><p>3. Translate and preview the Adaptive Form with newly added locale as explained <a href="https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/forms/adaptive-forms-authoring/authoring-adaptive-forms-core-components/create-an-adaptive-form-on-forms-cs/using-aem-translation-workflow-to-localize-adaptive-forms-core-components#:~:text=Perform%20the%20following%20steps%20to,select%20the%20Add%20Dictionary%20option.&amp;text=To%20create%20a%20translation%20project,Title%20field,%20specify%20the%20title.">here</a>. ( Add afAcceptLang=he ( eg. hebrew) to preview the hebrew translated form)</p><h3># Limitations</h3><ol><li>Header and Footer localisation is not supported . This behaviour can be achieved by using the custom components or text component inside the form container</li><li>Canvas theme is only supported OOTB, others can be customised similarly.</li><li>Email Template Support does not exist in RTL Language.</li><li>The Phone number field does not support RTL input (text entered is left-to right) which is expected behaviour as <em>“Regardless of the current language or the surrounding content, the digits in a specific number — such as “541,” a phone number, or a credit card number — always appear in the same order.” </em>Textbox component can be used as a workaround</li><li>OOTB DOR Generation in RTL Layout is supported only on AEM Cloud.</li></ol><h3># Conclusion</h3><p>With the addition of RTL language support, AEM Forms continues to push the boundaries of global digital experiences.</p><p>For organisations working with RTL languages, now is the time to explore these new capabilities and leverage them for enhanced audience engagement.</p><h3># References</h3><ol><li><a href="https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/forms/adaptive-forms-authoring/authoring-adaptive-forms-core-components/create-an-adaptive-form-on-forms-cs/supporting-new-language-localization-core-components">https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/forms/adaptive-forms-authoring/authoring-adaptive-forms-core-components/create-an-adaptive-form-on-forms-cs/supporting-new-language-localization-core-components</a></li><li>Eg of translated clientlib language(hebrew) Json - <a href="https://experienceleague.adobe.com/docs/experience-manager-cloud-service_en/assets/he.json">https://experienceleague.adobe.com/docs/experience-manager-cloud-service_en/assets/he.json</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=60e309fa0e23" width="1" height="1" alt=""><hr><p><a href="https://medium.com/adobetech/aem-forms-supporting-rtl-languages-milestone-in-global-accessibility-60e309fa0e23">AEM Forms Supporting RTL Languages: Milestone in Global Accessibility</a> was originally published in <a href="https://medium.com/adobetech">Adobe Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Adobe Workfront Integration with Microsoft Outlook]]></title>
            <link>https://medium.com/adobetech/adobe-workfront-integration-with-microsoft-outlook-ac1d44900bb5?source=rss-894848436b99------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac1d44900bb5</guid>
            <category><![CDATA[outlook]]></category>
            <category><![CDATA[workfront]]></category>
            <category><![CDATA[email]]></category>
            <category><![CDATA[mi̇crosoft]]></category>
            <dc:creator><![CDATA[Deepali Rathi]]></dc:creator>
            <pubDate>Wed, 01 Mar 2023 20:47:46 GMT</pubDate>
            <atom:updated>2023-03-01T20:47:46.412Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uafZobk93Ra8AllUBMWZEg.png" /></figure><blockquote>Adobe Workfront is a work management platform for enterprises looking to strategically prioritize, assign, and complete projects with speed, at any scale.</blockquote><p>In this blog post, we will talk about a use case where a business user wishes to initiate a request in Workfront as a response to an e-mail in Outlook inbox. Adobe Workfront Outlook add-in enables users to do so without having to leave Microsoft Outlook UI.</p><blockquote>Eg use case :</blockquote><blockquote>Joan receives email from third party agency requesting for assets for Summer Campaign . This process involves multiple stakeholders who approve the request , copywriters who analyse the campaign theme and set brief , designers and photographers who create the asset etc. Joan’s team uses Workfront for streamlining this process.</blockquote><blockquote>When Joan receives email, he wishes to initiate a request in Workfront (based on request template created in Workfront ) for his team to start working. Joan uses Outlook add-in for Workfront to initiate the request from Outlook UI</blockquote><h3>Get Workfront for Outlook</h3><p>In Outlook 365, go to Tools &gt; Get Add-ins.</p><p>Search for Workfront — Collaborative and Click on Add.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LYxm62ClkN0YB2etJqAaxA.png" /></figure><p>Once added, you will start seeing Workfront on the toolbar. (1)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R8JEXnNTSrwif6NY3CqKAA.png" /></figure><h3><strong>Connecting Workfront to Outlook</strong></h3><p>Open Outlook, and select the e-mail on which to take action and click on Workfront icon on top bar (1).</p><p>As show in the above screenshot (2) , enter the url of your Workfront instance and connects using SSO/credentials.</p><h3><strong>Create Workfront Request</strong></h3><p>Upon successful connection, clicking on Workfront icon opens a Workfront panel on the right. Panel allows one to select the list of Workfront options available like submitting a new request, adding task /issue to existing project , reply to comment etc.</p><p>Click on the Menu icon as highlighted below to view the list of Workfront options available..</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EljnObcRHpsBzvBp_Kn14g.png" /></figure><p>In our use case Joan wishes to submit a new request, so he selects <strong>Submit Request</strong>. All the Workfront <strong>request templates</strong> which are accessible to Joan will then be listed in a drop down.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*mpFfD3bXfCoJVkmjph1FGA.png" /></figure><p>He selects the required request template and template form content is auto populated with Email subject as Request title and Email body as Description.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9MN4rLOq-ViF3zq5D2xrWw.png" /></figure><p>Joan then updates/enters relevant request details .Custom form if any, associated with the selected request template can also be filled before submission eg. Custom Demo Product Form in above screenshot. As he clicks “<strong>Submit Request”</strong> button, a request is submitted in Workfront which would be visible to the approver defined for such type of requests to take further action .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0i_tTnZlaq78KKxEatZVZA.png" /></figure><p>Now as per the configuration in Workfront for selected request template , approver will get a notification to approve the request and create a project from a pre-defined project template. Automatic tasks (as defined in project template) will be assigned to respective stakeholders to start working.</p><p>Once assets are ready, Joan would be notified via e-mail and she can send them to agency.</p><p>Workfront for Outlook add-in updates email headers when a user submits a request from an email. so the next time the user opens the add-in for the same email the information about previous actions with that email are shown.</p><p>Eg. Below screenshot shows that this email was converted to a Workfront Request earlier.</p><p>On clicking the link you will be redirected to the request created in Workfront.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uQAKZ4q-PF6QNM7snLOeIQ.png" /></figure><p>Some other use cases that can be achieved using this add-on -</p><ul><li>Update an existing project, task, or issue with information from an email.</li><li>Create a Workfront request based on an email within Outlook. ( as shown above)</li><li>Add an email as a task in your My Work area.</li><li>Reply to comments via the Workfront add-in for Outlook.</li><li>Create tasks and issues from scratch, or create them from existing emails (using drag-and-drop functionality).</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac1d44900bb5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/adobetech/adobe-workfront-integration-with-microsoft-outlook-ac1d44900bb5">Adobe Workfront Integration with Microsoft Outlook</a> was originally published in <a href="https://medium.com/adobetech">Adobe Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Peek into Adobe Edge Server API]]></title>
            <link>https://medium.com/adobetech/peek-into-adobe-edge-server-api-aeeefd698668?source=rss-894848436b99------2</link>
            <guid isPermaLink="false">https://medium.com/p/aeeefd698668</guid>
            <category><![CDATA[adobe-target]]></category>
            <category><![CDATA[adobe-experience-platform]]></category>
            <category><![CDATA[personalization]]></category>
            <category><![CDATA[edge-server-api]]></category>
            <dc:creator><![CDATA[Deepali Rathi]]></dc:creator>
            <pubDate>Fri, 24 Feb 2023 20:20:56 GMT</pubDate>
            <atom:updated>2023-02-24T20:20:56.746Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tfYLGo1VxfxA5dj8lNVLUw.png" /><figcaption>Adobe Experience Platform Edge Server API</figcaption></figure><p>The Edge Server API enables server-side applications to communicate with the AEP Edge Network. Apart from Web SDK / Mobile SDK , it’s another way to communicate to Edge Network. It can utilised for various purposes, including data collection, personalization, advertising, and marketing. This API can be implemented on servers, IoT devices, set-top boxes, and other technology.</p><h3>Client-Side implementation (web/mobile SDK )</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AHT_IoKqWoYAj49IUlRl5w.png" /></figure><h3>Edge Server-Side API implementation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*phaHqy036txSM-zlFKdnZg.png" /></figure><p>Client or Server Side need not be aware of ECID being used in Adobe Experience Cloud. These applications need to maintain a single server side cookie (FPID).</p><h4>Benefits of Edge Server API</h4><ol><li>Secure : Enables sending data in authenticated manner.</li><li>Flexible: Along with Mobile/Web SDK provides another way for customers to connect with Edge Network.</li><li>Speedy: With less no of javascript ,SDK to load it’s fast with improved latency.</li><li>Omnichannel: It is independent of browser and its policies. It enables implementation on IOT Devices /Set top boxes etc.</li></ol><h3>Deconstruction of API Endpoint for Edge Server API : POST</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BXXDQLVl8nipbteTkPw7hA.png" /></figure><p>*The Edge Server API supports both authenticated and unauthenticated requests. The API endpoint depends on access type( configured in Datastream) and authentication/unauthentication requirements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0GDvnUYzJDKS2mxcJZCjaA.png" /></figure><p>**Data collection can be of two types :-</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7pp0nUtN2makYneod3TmUg.png" /></figure><p>A <a href="https://experienceleague.adobe.com/docs/experience-platform/edge/datastreams/overview.html?lang=en">Datastream</a> is the configurable part of the Edge network which include settings for which solutions will receive data (Adobe Analytics, Target, Audience Manager, Platform, Event forwarding, etc.), which datasets in AEP should receive data, and others.</p><h3>Request Header</h3><p>For authenticated calls to Edge Server API, follow the tutorial <a href="https://experienceleague.adobe.com/docs/experience-platform/landing/platform-apis/api-authentication.html?lang=en">here</a> to generate auth parameters that would be passed in call.</p><blockquote>Authorization : Bearer {TOKEN}</blockquote><blockquote>x-gw-ims-org-id : {ORG_ID}</blockquote><blockquote>x-api-key : {API_KEY}</blockquote><blockquote>Content-Type: application/json</blockquote><p>Body : (Eg snippet )</p><p>Request body is based on the schema created in AEP. FPID is a reserved namespace for first-party id.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/584/1*yRPgfjXRLJ7RVm0aZ4Nukw.png" /></figure><h3>Personalization using Edge Server-Side API</h3><p>An edge server API allows for customising of a user’s experience by delivering content or recommendations based on their preferences, behaviours or context in real-time . This approach can improve the speed and responsiveness of the personalization experience, as well as the security of sensitive user data.</p><p>Unlike WebSDK, which automatically aopplies the content returned by Target in response, in Edge server side implementation we need to process the response returned by API and send it to client for rendering.</p><p>To enable personalization using Adobe Target, we need to configure Adobe Target as service in datastream (datastream id is used in API endpoint) that ensures the Edge Server API call is also sent to Adobe Target .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aeZ9X6uLDK9mEcZDBImEQw.png" /></figure><p>Form-based/VEC activity is created in Adobe Target which contains the personalized experience and audience mapping.</p><p>Adobe Target as a response to request API returns the personalized offer for the audience qualified based on the input received from the request body i.e custom data/profile/location/behaviour attributes.</p><h3>Request object in API</h3><p>1) Send Profile attributes / Custom parameters in Edge Server API Call which are then available in target for audience creation.</p><p>Profile Attributes ( custom attributes) can be sent as below :</p><p>(When prefixed with profile , its a profile attribute or else considered as custom property by Target)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TDZisFZA52c65X5Vf8xyrg.png" /></figure><p>2) Add below query section in request which determines what content is returned by Target. Under the personalization object, schemas determines the type of content to be returned by Target. ( add all 4 when not sure of response type)</p><p>Adobe Target mbox names should be included in the decisionScopes array to return the appropriate content.</p><pre>&quot;query&quot;:{<br>   &quot;personalization&quot;:{<br>      &quot;schemas&quot;:[<br>         &quot;https://ns.adobe.com/personalization/html-content-item&quot;,<br>         &quot;https://ns.adobe.com/personalization/json-content-item&quot;,<br>         &quot;https://ns.adobe.com/personalization/redirect-item&quot;,<br>         &quot;https://ns.adobe.com/personalization/dom-action&quot;<br>      ],<br>      &quot;decisionScopes&quot;:[<br>         &quot;serverapimbox&quot;<br>      ]<br>   }<br>}</pre><ul><li>Target uses XFF (<strong>X-Forwarded-For)</strong>request header to determine the Target Audience attributes under the <strong>Geo </strong>Category. It utilizes <a href="https://www.digitalelement.com/solutions/ip-location-targeting/netacuity/">NetAcuity</a> which is a solution for global IP to location targeting .</li></ul><h3>Response</h3><p>When we call Edge Server API as explained above , response object contains the relevant activity content found under the handle object with the type as personalization:decisions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9brnY9SCVwU4kSGEhjKXog.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hvyJ2A4-h-cndWY0bVw9uQ.png" /><figcaption>Peek into response object</figcaption></figure><p>With Edge Server API lot of implementation which was automatically handled by Client (Web/Mobile SDK ) need to be implemented specifically by server side application eg. Rendering personalized content returned from response.</p><h3><strong>Why use Edge Server API?</strong></h3><p>Considering the advantages listed above like speed, security, etc., this approach is suitable for industries like finance/healthcare, which need to send sensitive customer data to AEP in a secured authenticated manner. (Configure to accept only authenticated request).</p><p>It is an alternate method for developers to send data to AEP Edge Network without Javascript / mobile SDK . Since there is no Javascript to load, it’s fast and secured with improved SEO scores.</p><p>It enables integration with IOT Devices, set top boxes or virtually any internet connected devices Eg sending data from a thermostat whenever temp is increased/decreased and do personalization magic .</p><h3>References</h3><p><a href="https://experienceleague.adobe.com/docs/experience-platform/edge-network-server-api/overview.html?lang=en">https://experienceleague.adobe.com/docs/experience-platform/edge-network-server-api/overview.html?lang=en</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aeeefd698668" width="1" height="1" alt=""><hr><p><a href="https://medium.com/adobetech/peek-into-adobe-edge-server-api-aeeefd698668">Peek into Adobe Edge Server API</a> was originally published in <a href="https://medium.com/adobetech">Adobe Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Microsoft Video Indexer — Search Videos in AEM Using Textual Content (OCR)]]></title>
            <link>https://medium.com/adobetech/microsoft-video-indexer-search-videos-in-aem-using-textual-content-ocr-19cdd40747d4?source=rss-894848436b99------2</link>
            <guid isPermaLink="false">https://medium.com/p/19cdd40747d4</guid>
            <category><![CDATA[mi̇crosoft]]></category>
            <category><![CDATA[aem]]></category>
            <category><![CDATA[assets]]></category>
            <category><![CDATA[adobe-experience-cloud]]></category>
            <category><![CDATA[videos]]></category>
            <dc:creator><![CDATA[Deepali Rathi]]></dc:creator>
            <pubDate>Tue, 31 Aug 2021 12:51:34 GMT</pubDate>
            <atom:updated>2021-08-31T12:51:34.415Z</atom:updated>
            <content:encoded><![CDATA[<h3>Microsoft Video Indexer — Search Videos in AEM Using Textual Content (OCR)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rM7UgTlHc3aUgBugg-soZA.jpeg" /></figure><p>Today, “video-first” has become a necessity for business. Organisations have valuable video assets and want to have the capability to search them.</p><p>This article talks about Microsoft Video Indexer API, which combines audio/video AI technologies into an integrated service. It builds upon media AI technologies to make it easier to extract insights from videos, power new forms of content discovery such as searching for spoken words, faces, characters, and emotions , helps recognize many of the words shown in a video, making it possible to search most on-screen text as well.</p><h4><strong>Prerequisites</strong>:</h4><p>We will use MS API to get detailed video insights and use these insights for powerful and efficient asset search in AEM.</p><p>To access MS Azure Video Indexer API , we would need to create account and obtain below key values.</p><ol><li><strong>Ocp-Apim-Subscription-Key</strong> : Subscription key which provides access to the MS video indexer API.</li></ol><p><em>Once subscribed , this key can be obtained from Video Indexer Developer Portal “</em><a href="https://api-portal.videoindexer.ai/"><em>https://api-portal.videoindexer.ai/</em></a><em>” in Products section.</em></p><p>2. <strong>Microsoft Account Id</strong> :</p><p><em>Once created , this value can be obtained from Azure Media Services | Video Indexer in Account Settings.</em></p><h4><strong>Technical flow:</strong></h4><ol><li>Upload your video from your file system to AEM .</li><li>Upload &amp; Index video from AEM to MS Azure by calling Video Indexer’s Upload API . <em>[API details in below section]</em></li></ol><p>You may use any of the below approaches :</p><p><em>a. Schedule video indexing process at predefined frequency for all video assets in a folder using Sling Scheduler in AEM.</em></p><p><em>b. On demand video indexing by initiating a Workflow .</em></p><p>Note : A public URL must be provided for the upload function to access the video file from AEM.</p><p>3. Once video is successfully uploaded and indexed fetch video insights using ‘Get Video Insights API’ .<em>[API details in below section]</em></p><p>4. Extract the necessary information (textual content) from the API Response and save the relevant information as corresponding asset’s metadata.</p><h4><strong>API details:</strong></h4><p>Each call to the MS Azure Video Indexer Operations API should be associated with an access token. Below are the two scopes we have used :-</p><p>a. Account level Access Token: Account level access tokens let you perform operations on the account level or the video level. For example, upload video, list all videos and so on.</p><p>b. Video level Access Token: Video level access tokens let you perform operations on a specific video. For example, get video insights, download. captions, get widgets, and so on.</p><ol><li><strong>Get Account Access Token.</strong> [to be later used in Upload API call]</li></ol><p>Upload Video API requires Account Level Access Token.</p><p>URL : https://api.videoindexer.ai/Auth/:location/Accounts/:accountId/AccessToken?allowEdit=true</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7sMtb42crecgAfSnUjeKzQ.png" /></figure><p>Headers : Ocp-Apim-Subscription-Key</p><p>Method : GET</p><p>Response : access token</p><p>2.<strong> Upload API Call — </strong>Upload video for indexing</p><p>URL : https://api.videoindexer.ai/:location/Accounts/:accountId/Videos?<strong>name</strong>=VideoName&amp;<strong>privacy</strong>=private&amp;<strong>fileName</strong>=VideoName&amp;<strong>accessToken</strong>=</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*veKRTrrR_TSzkaL8eD_D2w.png" /></figure><p>Method : POST</p><p>Headers : Ocp-Apim-Subscription-Key</p><p>Response :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WmZitfdheZiMLMu1gti7UQ.png" /></figure><p>Get Video Id / State from response.</p><p>Once the video is uploaded it starts indexing automatically. When the video is completely indexed, value of ‘state’ in response is “processed”.</p><p>3.<strong> Get Video Insights API </strong>-</p><p>URL : <a href="https://api.videoindexer.ai/:location/Accounts/:accountId/Videos/:videoId/Index?language=en-US&amp;accessToken=">https://api.videoindexer.ai/:location/Accounts/:accountId/Videos/:videoId/Index?language=en-US&amp;accessToken=</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XQdEfNV3QG6tEzNd2fI-9g.png" /></figure><p>Method : GET</p><p>Headers : Ocp-Apim-Subscription-Key</p><p>Sample Response Structure :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/766/1*aiae9XHAZL8c0Br4OLoBmA.png" /></figure><p>Iterate over highlighted OCR array in response and extract text from the API Response.</p><p>The extracted text in response can be formatted as per the requirement .Eg :</p><ol><li>Removing common words like pronouns which are irrelevant as per business logic (the, of, on ,in ,like ,etc) .</li><li>Discarding the text that has a confidence score below an appropriate threshold value.</li></ol><p>Once the text is extracted in the desired format,</p><ol><li>It can be stored in Asset Metadata — Enabling Video Assets to be searchable based on their text content.</li><li>A custom video component can display the extracted text as tags or content on a webpage.</li><li>Extracted text keywords can be used for automatic tagging of videos.</li><li>Extracted text keywords can be used to target right videos to right customer base.</li></ol><p>Eg. On a mobile site, if the user is Apple customer , we can display videos related to IPhone [can be identified using extracted text] and if visitor is an Android customer, we can display videos related to Android .</p><p>All MS uploaded videos can be accessed <a href="https://www.videoindexer.ai/media/library">here</a> .</p><h4>Possible use case extensions:</h4><ol><li>‘Get Video Insights API’ response recognises faces , sentiments ,keywords along with text/transcript . They can be used to identify videos containing specific people [Leadership videos], search based on sentiments .</li><li>To enable video assets search in AEM based on the people recorded in the video</li><li>The possible extracted details from video are celebrity identification , face detection, text recognition, object identification, scene segmentation, shot detection, shot classification, and keyframe extraction</li><li>Use AI algorithms to get valid and useful data from the textual content retrieved .</li></ol><p>References :</p><ol><li>Tutorial to retrieve required keys for API Authentication</li></ol><p><a href="https://docs.microsoft.com/en-us/azure/azure-video-analyzer/video-analyzer-for-media-docs/video-indexer-use-apis">Use the Azure Video Analyzer for Media (formerly Video Indexer) API - Azure Video Analyzer for Media</a></p><p>2. Sample Git Hub URL : Video Indexer Samples</p><p><a href="https://github.com/Azure-Samples/media-services-video-indexer">GitHub - Azure-Samples/media-services-video-indexer: Contains the Azure Media Services Video Indexer samples</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=19cdd40747d4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/adobetech/microsoft-video-indexer-search-videos-in-aem-using-textual-content-ocr-19cdd40747d4">Microsoft Video Indexer — Search Videos in AEM Using Textual Content (OCR)</a> was originally published in <a href="https://medium.com/adobetech">Adobe Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Post AEM Assets on Twitter]]></title>
            <link>https://medium.com/adobetech/how-to-post-aem-assets-on-twitter-ad9e51d5a2ae?source=rss-894848436b99------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad9e51d5a2ae</guid>
            <category><![CDATA[assets]]></category>
            <category><![CDATA[tweet]]></category>
            <category><![CDATA[adobe-experience-cloud]]></category>
            <category><![CDATA[adobe-experience-manager]]></category>
            <category><![CDATA[twitter]]></category>
            <dc:creator><![CDATA[Deepali Rathi]]></dc:creator>
            <pubDate>Mon, 13 Jul 2020 15:06:01 GMT</pubDate>
            <atom:updated>2020-07-15T12:58:26.864Z</atom:updated>
            <content:encoded><![CDATA[<p><em>In this post, we look at how we can programmatically create and manage Twitter campaigns from AEM assets UI.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JiX8r_wZmleQqDz04JzUWA.png" /><figcaption>AEM Assets Twitter Integration</figcaption></figure><h4><strong>The business use case</strong></h4><p>An organization creates assets using various tools like Photoshop and then syncs/uploads them into AEM. The organization wants a user friendly way to directly post these assets on its Twitter account, from AEM Assets, and manage the status of the posted tweets via likes and impressions of the tweet. This increases the reusability of the assets (hosted in AEM) on its website as well as Twitter account.</p><h4><strong>The solution</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yhs4GivJ-hy77pPgEz8YBA.gif" /></figure><p>The technical implementation of the solution for this is divided into three parts:</p><ol><li>Customize AEM Assets to provide a <strong>custom button</strong> that provides a dialog <strong>to enter status</strong> and <strong>relevant tags</strong> for the post to be submitted to Twitter.</li><li>Create a <strong>custom workflow</strong> that <strong>posts the asset</strong> on Twitter after approval by an author. This workflow will be auto-triggered on post submission (as done in step 1).</li><li>Create a <strong>custom scheduler</strong> that <strong>fetches</strong> the number of <strong>likes and impressions</strong> of all the AEM assets posted on Twitter and then saves the information in the asset metadata.</li></ol><h4><strong>Prerequisites</strong>:</h4><p>Create your <strong>Twitter app</strong> on theTwitter Developers site and make a note of your <strong>OAuth Settings</strong> that will be needed for authentication.</p><p>The following values will be required to authenticate connection to the Twitter API from AEM — <em>consumerKey , consumerSecret, accessToken, accessTokenSecret</em></p><p><strong>Reference Link :</strong></p><p><a href="https://developer.twitter.com/en/docs/basics/apps/overview">https://developer.twitter.com/en/docs/basics/apps/overview</a></p><h4><strong>Implementation Steps:</strong></h4><p>(Note : This article explains two types of assets — a) <strong>Images</strong> and b) <strong>Content Fragment</strong>).</p><p>For Content Fragment, create a Content Fragment Model that allows authoring of the image, text status, and tags of the Post.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/797/1*4-jGWhh2NMJqaWPWHmJPZw.png" /></figure><h3>Step 1</h3><p>Create a custom button called “<strong>Post to Twitter</strong>” in AEM Assets that will be available on selection of an asset<strong>.</strong></p><h4><strong>Image Assets</strong> :</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7Fjy8msCT-fku7VBXK2bkA.png" /></figure><h4><strong>How to create a “Post To Twitter” button:</strong></h4><p><em>[This overlay feature implementation is referenced from OOTB “Download Asset” option in AEM]</em>.</p><p>a) Overlay node :</p><p>/libs/dam/gui/content/assets/jcr:content/actions/selection to path /apps/dam/gui/content/assets/jcr:content/actions/selection</p><p>b) Create a node “<strong>posttotwitter</strong>” at path <strong>/apps/dam/gui/content/assets/jcr:content/actions/selection/posttotwitter </strong>with following properties:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/569/1*RUUERBAdPJZwurWBFT2WyA.png" /></figure><h3>Step 2</h3><p>Create a dialog to be opened with the click of the “Post to Twitter” button.</p><p><em>Note : This dialog will be required only in for Image assets to add status text and tags for tweet. For CF , the dialog will not be opened up and Workflow will be triggered automatically i.e Step 3.</em></p><p>The dialog provides the following options:</p><p>a) Enter a Twitter status text</p><p>b) Select Tags / Smart Tags tagged to the asset to be posted. These tags shall be used #HashTags in Twitter status as drop down.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/542/1*HENDPXvFBBWOuCSvXeikIA.png" /></figure><h4><strong>Creation of Dialog:</strong></h4><p>i) Create a child node named “<strong>granite:data”</strong> at /apps/dam/gui/content/assets/jcr:content/actions/selection/posttotwitter (created in Step 1.b) with following properties.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PxFTM6LRACvY-XIwVb6jeg.png" /></figure><p>The “href” property is used to point to the path which defines the dialog to be opened on “Post to Twitter” button click.</p><p>ii) Create a custom dialog posttwitterdialog as shown below at the path provided in the “href” property.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/542/1*HENDPXvFBBWOuCSvXeikIA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GChRD466ktfL-ZNtf1OZQA.png" /></figure><p>The sling:resourceType of the posttwitterdialog node (as shown in above image) refers to a jsp that includes dialog.jsp (refer to the code snapshot below).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/736/1*Djknhu5ZDdgDGuZo6BZNeQ.png" /></figure><p>The dialog comprises of :</p><ol><li>Textbox Field : This enables user to enter status.</li><li>Select Field : This is populated dynamically using the datasource JSP. The datasource jsp returns the tags associated with the selected asset in dropdown allowing user to select hashtags for the status from the asset tags.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mrCV3WF_otd0xZGQmj0RrA.png" /></figure><h3>Step 3</h3><p>Create a workflow as shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/428/1*tSuJ5XiuzmTS2j7kRLgZTg.png" /></figure><p>This workflow needs to be triggered programmatically on posttwitterdialog submit (call a servlet on button click and use WorkflowManager class to trigger workflow).</p><p>Once the workflow is triggered, the approver will be notified of the approval request in their inbox.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3A3bYToYcRb3cbJBROYo1Q.png" /></figure><p>Once approved, the custom Workflow process step [“Approve Request”] code will call Twitter API or connect to twitter using twitter4j java library to post the asset as a tweet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/710/1*xTuA0WrCY2pqCa2RqYnThg.png" /><figcaption>Sample Code To Call Twitter API using Twitter4J Lib</figcaption></figure><p>Once approved, the status will be updated on Twitter:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/429/1*GLMnvfuKYeu_ubpjTxzrrA.png" /></figure><p>On successful posting of the asset, a tweet id (returned by Twitter API) and asset status text will be saved in the asset metadata. This tweet id can be shown in asset properties in custom Metadata Tab.</p><h3>Step 4</h3><p>Create a custom scheduler to find all the assets in AEM (using QueryBuilder), which contains tweet Id in metadata. Now call the Twitter API to get updated metrics (Likes/Impressions) using tweet Id for all such assets and update these metrics in the asset metadata. You can find the API here: <a href="https://api.twitter.com/labs/1/tweets/metrics/private?ids=twitterid">https://api.twitter.com/labs/1/tweets/metrics/private?ids=<em>twitterid</em></a></p><p><em>Note : There are multiple ways in which these tweet metrics can be used. This article shows them in the asset metadata.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YjPJ56h2QSK8ZNmLvp0_Gw.png" /><figcaption>Tweet Metrics Saved in Asset Metadata.</figcaption></figure><h4>Some possible extensions to the above implementation :</h4><ol><li>In the article we talked mainly about Images/CF but this can be extended for other asset types like video.</li><li>Provide authors a configurable way to set the scheduler frequency to get updated metrics and provide an on demand feature to get updated metrics.</li><li>Refer to <a href="https://developer.twitter.com/en">https://developer.twitter.com/en</a> for available Twitter APIs to consume based on use case.</li></ol><p><em>This article shows how easy it is to post image and content fragment assets to a social media platform like Twitter using Oauth connections from within AEM, the same approach can be used for other social platforms alike. This in turn makes AEM a social media publishing platform from where a client can post to all its social accounts from under one roof :-)</em></p><p>Co-Author : <a href="https://medium.com/u/4d14dff33107">KM Robin</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/474/1*Gcgw2B0HTWIGIVvnB60MLw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/48/1*n4LyDruDeaxqiOIkzFi4qg.png" /><figcaption>Happy tweeting</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad9e51d5a2ae" width="1" height="1" alt=""><hr><p><a href="https://medium.com/adobetech/how-to-post-aem-assets-on-twitter-ad9e51d5a2ae">How to Post AEM Assets on Twitter</a> was originally published in <a href="https://medium.com/adobetech">Adobe Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>