You can setup a DEBUG logger on the following classes to see which step in the workflow is failing:com.adobe.granite.workflow.core.WorkflowSessionImplcom.adobe.granite.workflow.core.jobIf you see an error similar to below, imagemagick is failing:10.04.2019 18:45:21.263 *ERROR* [JobHandler: /var/work...

The only recommended way is to upgrade to the latest version of AEM. Installing a bundle that is meant to be for a higher version of AEM on a lower version is not a good idea. It might work but thats not a recommended way of doing things in AEM.If you install the latest sling model bundle on AEM 6.0...

You need to use the version of AEM that provides sling model API 1.2.2 OOTB. Example: AEM 6.3.3.5 has sling model API version 1.3.8

As far as i can check this is not possible and you need to use multiple SAML configuration to achieve that. Explaination below:SAML Handler in AEM will only be activated when it receives the IDP response at <AEM_HOST>/saml_login(Assuming path variable is set to "/")saml_login is the servlet that pro...

You can track the logged in users from "http://<host>:<port>/system/console/tokenmgr" and use the tokens in custom code to persist it in the DB

I agree with Yanira's response, This is not by design.  Assets will publish when a user clicks to Activate it or activate a page with assets in it. You need to think of author and publish as two entities and offloading in only implemented on the author with no trigger/process predefined to automatic...

Ideally, the flush agent should be configured on the publisher and most of the customer do it that way.Under certain circumstances, performance gains can be made by transferring cache management from the authoring environment to a publishing instance. It will then be the publishing environment (not ...

This issue has been reported (internal reference is: CQ-103742) and is also visible in the public Oak project, under this reference OAK-5078 [0].This issue has been fixed in Oak 1.4.10, So, you can upgrade the oak version to 1.4.10 at least from [1] to resolve the issue.There is however a work-aroun...

Checking the AEM code at "com.adobe.cq.xf.impl.ExperienceFragmentsReferenceProvider"Page parentXf = getVariationParent(path, resolver);references.add(new Reference(TYPE_XF, parentXf.getTitle(), parentXf.adaptTo(Resource.class), parentXf.getLastModified().getTimeInMillis()));It looks like the issue i...

If the thirdy part DAM is AEM DAM, you can use connected DAM[2] feature of 6.5Otherwise, you need to write custom code and use Assets API[1] to perform the asset-related operation from third party server.Retrieve a folder listingCreate a folderCreate an assetUpdate asset binaryUpdate asset metadataC...