You need to create a Custom process step in the Workflow Model. This custom process step will update the asset property.https://experienceleague.adobe.com/docs/experience-manager-65/developing/extending-aem/extending-workflows/workflows-customizing-extending.html?lang=en Also, you may need to create...
https://experienceleague.adobe.com/docs/experience-manager-brand-portal/using/publish/troubleshoot-parallel-publishing.html?lang=en good article on how to troubleshoot issues related to the brand portal.
You can use BPA (https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/migration-journey/cloud-migration/best-practices-analyzer/overview-best-practices-analyzer.html?lang=en) to see if your custom code is compatible on AEM as a cloud.
You can try using https://tray.io/connectors/adobe-experience-manager-figma-integrations for integration b/w AEM and figma. Also, you can use Figma API https://www.figma.com/developers/api to pull data into AEM.
Create a HttpClient connection for API inside Sling Models, Service, or Servlet to be passed to the page based on your requirement.Refer: https://experienceleague.adobe.com/docs/experience-manager-learn/getting-started-wknd-tutorial-develop/project-archetype/component-basics.html?lang=en
It would be best if you embedded the jar as well.https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/developing/aem-project-content-package-structure.html?lang=en#embeddeds
Following are key considerations to bear in mind when transitioning to AEM in the cloud:Make sure to get rid of deprecated featuresPlan a strategy for how you will move Assets data to the AEM cloudNaming convention for folders and assets should be proper [Optional]Try to get rid of assets which ...
Checkout https://github.com/adobe/aem-core-wcm-components/blob/main/bundles/core/src/test/java/com/adobe/cq/wcm/core/components/internal/models/v1/contentfragment/ContentFragmentImplTest.java for Junit.