@BrianKasingli It was a custom model. The issue is now resolved. The issue was, if any of the step fails, all steps from start till before the failed step are not shown in history of workflow. Thanks!!
The same process step is working with the existing. workflow. Also, I tried using OOTB Activate process. The workflow instance history is still the same. when seen the history, the initiators are different. For thhe existing workflow the initiator is workflow-service, while for the fresh one the ini...
Hi,I am facing an issue with creating and starting workflow in aem 6.5.I tried creating a workflow model in aem 6.5.Now when I run the workflow, when i open the history in instances tab, I can just see 2 steps - first and last. I am unable to see the middle steps. It seems node transition is not wor...
@hamidk92094312@berliant We do not have any search requirement associated with this node and properties.Its just like we want to persist it on jcr and fetch the properties using sling/jcr to render the page.Will it still have any issue ?
Is there any restriction to number of properties those could be added to a node in aem 6.3?Also , is there any impact on the instance if the number of properties in a content node increases? How is the instance impacted with more number of properties.This is specific with respect to aem 6.3 version.
I have a requirement to add extra column to below properties tab of a node.By default it will have (Name,Type,Value,Protected,Mandatory,Multiple). I want one more column "test" to be added to the below list.Any pointers appreciated
The issue is now fixed. The root cause for this issue was that there is a custom ajax call made which too was trying to update the node. Hence we were getting the node already checked in exception.Thanks !!
Its a dialog participant step, with a custom dialog path as below<type jcr:primaryType="cq:Widget" allowBlank="{Boolean}false" fieldLabel="Status" name="./jcr:content/status/propName" type="select" xtype="selection">This should add the propName property in at payload path/jcr:content/...
Arun PatidarLogged in as an admin user.Also I found its throwing persistence exception for the post call to the node.*ERROR* [0:0:0:0:0:0:0:1 [1567190881753] POST <payload path> HTTP/1.1] org.apache.sling.servlets.post.impl.operations.ModifyOperation Exception during response processing.org.apache....