Hi @airnavin30 ,  Yes it is possible. We can add link in filed description. It works fine for me. I have added anchor link navigation to google.com in field description and it works as expected.    Please do have a check if you have made any syntax error. Also, please do inspect of anchor and verify...

Hi @Luca_Lattarini , Globally disabling is possible with customisation. Article which @kautuk_sahni shared below has the steps to achieve the same. 

Hi @Luca_Lattarini , Yes it is possible.Set the below property in  cq:editConfig node of component where you do not want target option to be enabled. In your scenario add it in image component. cq:disableTargeting="true"This will disable the target option. 

 Hi @oscarr38307878 , cq.jquery.ui is the category of jquery ui.  You must have included this in your template/component as category or loaded in as embed/dependency. If you are not consuming jquery ui you can remove it. Few specific lib example widgets, or authoring ui you don't need it in publishe...

Hi Sushmitha,Please find the answer for your queries below.1. Do I have to replicate the XF i created to the Publish environment(4503) and then do Export to Adobe Target? - [V] No, publish is not a mandatory step to export the fragments into target. XF integration with target is towards author side ...

Hi @MatStyler Are you trying to download/upload the the blobs? If so, there are prerequisites to consider. Please add details on where/when are you seeing the error and what action are you trying perform? 

Hi Sushmitha, Please check the below documentation.https://docs.adobe.com/content/help/en/experience-manager-65/administering/integration/experience-fragments-target.html If you have already integrated AEM to target and connection is a success, XF integration is very simple.1. Create an XF.2. Map th...

.

Hi @sushmitha-srinivasan  Have you mapped the target configs for the XF which you're trying to export?Mapping the target config to the page should fix the export issue. Also please share the logs if you still face the issue after the configuration.  

Hi @vijays80591732 , By default, dynamic requests are not cached which is a request with query parameter.   In your case, dynamic requests are caching nothing but you have a rule in a dispatcher config to cache the request with query parameter.Please do have a check for the below rule and make you h...