Hi. I'm unable to find the documentation for the granite pathbrowser component? I could see many of the other form releated components but unable to find anything for pathbrowser.Welcome to Granite UI’s documentation! — Granite UI 1.0 documentation

Re: Retrieve response from REST API joshuau83969408 - Adobe Experience Manager Forms

That's correct. I'll open a Daycare ticket. Unfortunately for this effort, we need to use Adobe Forms (assuming it works as expected).

Re: Retrieve response from REST API joshuau83969408 - Adobe Experience Manager Forms

lesutton1,Any further thoughts?

Re: Retrieve response from REST API joshuau83969408 - Adobe Experience Manager Forms

You could see below the guideResultObject being returned. It doesn't have the response in the data property.

Re: Retrieve response from REST API joshuau83969408 - Adobe Experience Manager Forms

Correct, when I add this console.log: console.log('guideResultObject.data: ' + guideResultObject.data);, the following prints in Chrome's console:guideResultObject.data: [object Object]

Re: Retrieve response from REST API joshuau83969408 - Adobe Experience Manager Forms

Yes. The adaptive form is invoking a Sling Servlet, which is then calling my 3rd party service. I'm looking to surface the response of the 3rd party service in my window.guideBridge.submit success callback function.

Re: Retrieve response from REST API joshuau83969408 - Adobe Experience Manager Forms

My REST service is returning JSON. Here is the response I'm logging in my Sling Servlet. I want to be able to acccess the leadId in the success callback handler.{"status":"OK","encoding":null,"data":{"leadId":"3dc2eb71-d40a-4bdd-a16d-510636098b1d"},"apiErrorList":null}

Re: Retrieve response from REST API joshuau83969408 - Adobe Experience Manager Forms

lesutton1,We are on 6.2 I'm using the submit button click rules and I have the following. Shouldn't my REST service response come back in the guideResultObject? It's null when I try logging it.window.guideBridge.submit({ validate: true, error : function (guideResultObject) { handleErrorSubmission("There was an error. Please try again later."); }, success : function (guideResultObject) { console.log('guideResultObject: ' + guideResultObject); console.dir('guideResultObject: ' + guideResultObject)...

Re: Retrieve response from REST API joshuau83969408 - Adobe Experience Manager Forms

Thanks Scott but that link looks like it's for invoking SOAP based services where as I'm invoking a REST based service.

Re: Retrieve response from REST API joshuau83969408 - Adobe Experience Manager Forms

Scott,Do Adaptive Forms not support retrieving the rest response in the guideResultObject? Also, I'm using AEM 6.2.

Retrieve response from REST API joshuau83969408 - Adobe Experience Manager Forms

When using an adaptive form, is it possible to retrieve the response from the rest service I'm invoking? My adaptive form is invoking a sling servlet which then invoked my 3rd party rest api. The rest api is returning a payload but I'm unable to access the payload when looking at the guideResultObject that is returned. Any pointers would be helpful. Thanks!

Re: Theme Preview Form Error joshuau83969408 - Adobe Experience Manager Forms

I did review that KB but it doesn't help with the issue. I'm able to create a theme just fine, but when trying to configure the theme to use a specific preview form is when the issue occurs. To create the theme I'm simply using the authoring env. to create the theme.

Re: Theme Preview Form Error joshuau83969408 - Adobe Experience Manager Forms

Thanks Kautuk! The missing library is a warning so I'm not sure if that's related to the issue at hand. Let me know if anyone else has any other thoughts.Thanks!

Re: Theme Preview Form Error joshuau83969408 - Adobe Experience Manager Forms

6.2

Theme Preview Form Error joshuau83969408 - Adobe Experience Manager Forms

Within the theme editor when I do "Configure > Preview Form" and specify a path to one of my adaptive forms I'm getting a "org.apache.sling.api.SlingException: Exception during response processing" upon saving. Any pointers as to what the issue might be would be helpful. Below is the stack trace.02.08.2017 14:50:31.365 *WARN* [206.210.17.33 [1501699830898] GET /content/dam/formsanddocuments-themes/nyl-cms-dotcom/testing123/jcr:content HTTP/1.1] com.adobe.granite.ui.clientlibs.impl.HtmlLibraryMan...

Re: IllegalStateException: This tree does not exist joshuau83969408 - Adobe Experience Manager

I take that back, adding the target-activity-authors group to the group I'm testing with did allow it to work.

Re: IllegalStateException: This tree does not exist joshuau83969408 - Adobe Experience Manager

This group of users shouldn't have administrators rights. The target documentation mentions some steps when implementing target and I tried adding the target-activity-authors group to my group but it still didn't work.https://docs.adobe.com/docs/en/aem/6-2/administer/integration/marketing-cloud/target/target-requirements.html#Securing the Activity Settings Node

Re: IllegalStateException: This tree does not exist joshuau83969408 - Adobe Experience Manager

The system user I'm using is in a group, and that group has these permissions on the /content/campaigns/cms path: read/modify/create/delete/replicate.

Re: IllegalStateException: This tree does not exist joshuau83969408 - Adobe Experience Manager

I had looked at that question but it's a bit different and unfortunately doesn't help with my issue. If I look at what permissions are assigned out of the box to the /content/campaigns folder I could see the following. Do I need to add these groups to the user I'm attempting this operation with?campaign-reader / jrc:readcampaign-remote / crx:replicate, rep:write, jcr:lockManagementcanvaspage-activate-service / jcr:readtargetservice / rep:write

Re: IllegalStateException: This tree does not exist joshuau83969408 - Adobe Experience Manager

Any thoughts?

IllegalStateException: This tree does not exist joshuau83969408 - Adobe Experience Manager

I'm working on enabling Adobe Target on our AEM site and I'm getting the following exception when trying to create a Target Activity in a given page. If I use an admin account it works fine so I'm thinking it's something permission related. I've granted permissions to the user I'm using when it fails with read/modify/create/delete/replicate to the /content/campaigns/cms path. What else am I missing to make this work?26.07.2017 12:57:34.933 *ERROR* [206.210.17.33 [1501088254928] POST /content/cam...

Re: Cloud Services and Dispatcher joshuau83969408 - Adobe Experience Manager

When I allow these two paths in my dispatcher.any everything works. Are these the expected paths to allow when enabling cloud services? I also had to enable access to /etc/cloudservices for the anonymous user on my publish instance. Is this expected? /1050 { /type "allow" /url "/etc/cloudsettings*" } /1051 { /type "allow" /url "/etc/segmentation*" }

Cloud Services and Dispatcher joshuau83969408 - Adobe Experience Manager

I've added a cloud service to my application, and a bunch of paths are returning 404's. What specific paths must I open up in dispatcher to allow this to work? Everything works fine if I access the page via the publish instance host:port.

Re: cq:EditConfig & dialog.xml joshuau83969408 - Adobe Experience Manager

Thanks for all the feedback everyone! Just to summarize and clarify to get a Touch UI component to appear in the side rail and design mode you must have the following:cq:dialog node (if the component is to be editable) [OPTIONAL]cq:editConfig [REQUIRED if you want it to appear in side rail/design mode]Note: dialog.xml also works instead of cq:editConfig but since this is specific to Classic UI the approaches above should be utilized.

Re: cq:EditConfig & dialog.xml joshuau83969408 - Adobe Experience Manager

Isn't the dialog.xml for the Classic UI and the cq:dialog is for touch ui? Why would we need a dialog.xml in this case? It will appear in the side rail with a cq:EditConfig node and no dialog.xml.

cq:EditConfig & dialog.xml joshuau83969408 - Adobe Experience Manager

When creating a new component in AEM 6.2 I noticed it doesn't appear as an available component in the side rail or in design mode until I add the cq:EditConfig node to the component. I also noticed if I add a dialog.xml node it will allow it to appear in the side rail and via design mode but my understanding is this is part of classic ui and isn't needed for touchui. Any help with clarifying this would be appreciated.Thanks!

Likes given to

User

Count

Likes from

User

Count

Guidelines