AEM as a Cloud Service provides advanced networking features that allows for precise management of connections to and from AEM as a Cloud Service programs. In this article we will  learn how to set up and use flexible port egress to support external connections from AEM as a Cloud Service to externa...

1. Set Up a Lightning Out App in Salesforce Create a Lightning Out App: In Salesforce, navigate to Setup and search for Lightning Components.Develop a Lightning component that encapsulates the desired functionality.Create a Lightning application that includes this component and is marked as ltng:al...

@Niveshchandra  -  1. Validate the Dictionary Files Ensure that the dictionary files (.dic and .aff) are correctly formatted and valid.These files should comply with the Hunspell dictionary format. 2. Place Dictionary Files in an Accessible Location Instead of providing absolute paths, place the dic...

@rishabhb  - Try checking your Mockito dependencies.

@kirtikhatri  Option 1: Using AEM Workflows 1. Create a Workflow with SOAP Endpoint Navigate to Tools > Workflow > Models in the AEM UI.Create a new workflow or modify an existing one.Add the "Forms SOAP Endpoint" step to your workflow. 2. Configure the SOAP Endpoint In the Workflow Editor, click th...

@srikanthg212933  - Could you please add some more information  ?

@Mohan_BMS  -  I did implemented for one of the client sometime back. I have below notes which might help you to kickstart on the integration: 1. Embed Yammer Feeds into AEM Pages: Yammer Embed Widget: Yammer provides an embed widget that allows you to display feeds, groups, or user profiles on exte...

@iwowsoft  - Try connecting to the Adobe Helpdesk/Sales team, they might be able to help

@organicon  - It depends on which CIF Component you are using. If it's a Product Listing then you can author multiple components or let's say if it is a ProductTile component then it won't have the multifield functionality.Also can you please add more information on the issue that you are facing..

@Heena91  -  I can see the typo in the template name, not sure it can be because of that. Please try validating the template in Sites and see if you can handle components there ?