Hi,Not sure exactly what you're hoping for but in later releases of worklfow you can find out which launcher started a workflow, if it was started by a launcher.  it is stored in the worklfow metadata with the key "launcherId".Hope this helps,Will

Hi,I am a bit confused by what you're trying to accomplish here.  You have hard coded the fact that there are two routes leaving the step in question in the workflow model.  I'm curious why you don't put the logic as to which route to follow in the route rule in the model?  That way there should be ...

Hi,I'm curious why you're interested so much in stale workflows.  A stale workflow means that a workflow in the system with a running state has metadata stored indicating that there should be a sling job executing the workflow.  A workflow shows up as stale if the sling job system reports that the j...

Hi Dave -Modifying the OOTB Dam Update Asset workflow will work just fine. When upgrading AEM at a later date you will likely lose your changes and will need to re-apply them.  Shouldn't cause much harm.Will

Hi Kanwal -There is an OSGI Service you can use called "PayloadMap".  [0]  It will permit you to quickly find out all the running worklfows for a particular payload path.Hope this helps,Will[0] http://docs.adobe.com/docs/de/aem/6-0/develop/ref/javadoc/com/adobe/granite/workflow/PayloadMap.html

Hi,I think your approach sounds fine, it should work.Another alternative you might consider is having different workflows for each site.  You can put them in different folders like this /etc/worklfow/models/sitex and have ACLs on the folder sitex that only permits users for that site to start that w...

Hi,check the method "getPayloadPath" in libs/cq/workflow/global.jsp it might give you a hint as to how to generate an url for a payload path.CQ uses something called "JcrPathBuilderManager" to turn a payload path in the repository into an url you can click on.  You should be using this in your code ...

Hi,Yes, the container workflow starts the child workflow as admin because it is started in the back-end, and not directly by the user.When you start a child process the metadata from the parent process is copied to the child process when it is started, I would add the user information you require (i...

Hi,As of CQ 5.6.0 there is a JMX bean which does purge.  You access it here [0] and it's documented here [1]As of CQ 5.6.1 you can schedule this purge to occur, see [2] If you are using an older version of CQ there is a script you can use which is outlined here [3] hope this helps,Will[0] http://loc...

Hi,It should be possible using an exclude pattern in the glob.  see here: http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manager.topic.html/forum__cpoe-all_is_thereaw.htmlWill