Equivalent Coral2 of /libs/granite/ui/components/coral/foundation/authorizable/autocomplete

[DEBAL_DAS]

I have created one page property named: Content Approver Group with sling:resourceType: granite/ui/components/coral/foundation/authorizable/autocomplete

This autocomplete page property named: Content Approver Group is designed to allow the content authors to pick the user group from suggested list as shown in below screenshot -

Here is node and property details associated with Content Approver Group

But I would like to implement the same in coral2. I feel if I refer Participant Step component in AEM6.2 then I will be able to  implement the same in coral2.

@kautuk_sahni ,

How can I get the AEM 6.2 quickstart jar? Please suggest.

[arunpatidar]

Hi Debal,

Can you please let us know the use case here ? Coral3/Granite are the improved version of Coral2. Why you want to go backwards.

You can try https://developer.adobe.com/experience-manager/reference-materials/6-5/granite-ui/api/jcr_root/libs/... with datasource

e.g. https://aemlab.blogspot.com/2018/08/searchfilter-touch-ui-dialog-dropdown.html 

[DEBAL_DAS]

Hi @arunpatidar ,

I saw your blog already and sure I will give a try with this.

Though we are using AEM 6.5.x, but still components are using Coral2. I can say this much only about the use case.

Initially I wanted to create an autocomplete page property with /libs/granite/ui/components/coral/foundation/authorizable/autocomplete, so that it will allow the content author to pick the user groups from suggested list.

Here is the link https://developer.adobe.com/experience-manager/reference-materials/6-5/granite-ui/api/jcr_root/libs/...

I have got the idea to use /libs/granite/ui/components/coral/foundation/authorizable/autocomplete from Participant Step component.

I agree with your point "Coral3/Granite are the improved version of Coral2." It makes my life easier to complete the design and it requires no extra development.

[arunpatidar]

AEM 6.5.x also support coral3, so there will not be any limitation if you continue using coral3 components.

[DEBAL_DAS]

I can't use both coral2 and coral3 in same component.

Most of the project specific components are using coral2.

Now I have decided to use /libs/granite/ui/components/foundation/form/userpicker.

Here is my node structure details -

Approver page property details has been shown below -