i see.. that was a silly mistake. Actually we migrated the workflow from AEM 6.0 to AEM 6.3 and seems like we had to do some authoring again to select the appropriate user/group. it looks fine after that.  But we have observed that the admin or user who is part of administrators group are getting al...

Scott, i can share the zip file (package) of the workflow i created. Can you please let me know how can i share that? i doubt if i can attach it here. But to provide more details, i can mention the dialog values below:Step 1: Add participant chooser stepTab 1Tab 2- Step 2: Add OR Split- Step 3: Add ...

Hi Scott,Yes, User K and User A both can see the notifications in their respective AEM inboxes and both can choose the next step.But according to workflow only user K should be able to work on the workflow to choose the next step and not user A.

Hi, please check the above workflow. First step is assigned to a user 'k' and the workflow is initiated by user 'a'.

just to add in this, i see the notification about the workflow in AEM inbox for both user A and User B. But if i open the page in classic UI, the sidekick has the correct information under 'Workflows' tab. the message says, that the page is subjected to workflow and there is no option to proceed. Bu...

Hi All,i have a question related to workflows. i have created a workflow that is initiated by User A. After initiation it goes to a user B. Then there is  an OR Split where user B can decide to accept or reject. Now the strange thing is that: user A after initiating the workflow, sees the workflow s...

Hi Feike, thanks for the suggestion. It makes the component unauthorable and it can considered as solution to our problem.But as Scott highlighted above, can we still consider this to be a bug? Same piece of code is behaving differently in different UI.Using resourceType='foundation/component/iparsy...

I thought so too. Classic ui works fine as it locks the dialog because of inheritance. Same should happen in touch ui as well.Thanks for the response. I will try logging this as bug.

Yes that is correct.

Our goal is to include the component along with dialog values into another page. Our comoonent 'menu' contains the navigation menus and included in the header section of the page. It is authored in index.html page and we want the same component with same values inside another page that is not a dire...