Hi Kalyan,I dont think teaser component is deprecated instead its named as 'offer'. If you look at the component, Offer uses the teaser component. Try using Offer instead of Target and see if it works Regards,Lokesh

session state you would have got when getting resolver might have been stale by the time you are saving. It happens sometime when you are saving node in the Oak. So always its better to do session.refresh()  and then save()

It looks like logged in User doesnt have permission to impersonate the given userId. Have you configured the same for the logged in User in useradmin ?

OOB, participant step is a single valued and hence you cant have multiple groups or users that can be sent..Instead see if below thoughts can be used1. Create a new single group combining multiple groups in it and use that group in the participant step2. Have multiple participant step one after the ...

I dont think it would be a valid usecase !!Normally, you will have to enable the components for a template and the permissions for creating the pages using that template can be controlled using ACLs.

You will have to connect with Adobe Sales team where they will get the required consulting from Adobe.

So every step of a workflow, you have 'complete' to go fwd and 'Step Back' to basically use it as a reject where it goes to the previous step

Can you explain a bit more of your use case ?At what point you would need to reject an asset ? is it at the upload time, processing time and at the usage time...

As you are using Zen Garden component, you might have to check with the product support and see if it supports.

You can write a simple script and use Goto Step to mention where it has to start with[1] https://docs.adobe.com/docs/en/cq/5-6-1/workflows/wf-ref.html#Goto%20Step