Replies

Avatar

Avatar

DarrenBiz

Avatar

DarrenBiz

DarrenBiz

13-07-2017

>> Yes, Currently test UI handles limited set of error cases but if service invocation is failing due to some reason complete details will be available in error log file.

How do you tell the difference between an error and a zero result set when you publish the form into production? The end users won't have access to the error log file. They will just think their search returned zero results. You can't tell using any of the available form APIs either so you can't handle this programmatically.

This is not a small issue - it prevents the whole FDM being used in a real live environment until we can tell the difference.

Avatar

Avatar

user2062153

Avatar

user2062153

user2062153

13-07-2017

Hi Darren,

Yes, Currently its very difficult to track if form submission or invoke service is failing and bug is logged for propagating error message from FDM to Forms and display in UI

Avatar

Avatar

ravi_ks007

Avatar

ravi_ks007

ravi_ks007

03-01-2018

Hi Darren,

Did you get any response from Adobe on the response from the service? We have started on forms now and we have similar requirements, could you please confirm on the outcome? Thanks

Avatar

Avatar

DarrenBiz

Avatar

DarrenBiz

DarrenBiz

01-02-2018

Not yet. I am going to take a look at the Beta now it is out and have a look.

Avatar

Avatar

DarrenBiz

Avatar

DarrenBiz

DarrenBiz

26-04-2018

Ok so I thought I would update this thread since I have checked out AEM Forms 6.4 Form Data Models offering. While there has been a few updates on some features including Cloud Services Configurations and Computed Properties [1], unfortunately there still doesn't seem to be a solution for handling statuses generated by erroneous FDM calls. We still have no way to tell the user if a search returned zero results or has thrown an error.

Adobe did release some info in AEM 6.3 / 6.4 on the API to execute the data calls [2], but it doesn't include a way to handle the status returned by the API call. Bit of a shame because there has been so much effort put into this feature that is still (by all accounts) unuseable for anything other than demos.

It would be helpful if Adobe could explain why returning a service status is so far down on the backlog it never made it into this release?

[1] Adobe Experience Manager Help | New features summary | AEM 6.4 Forms

[2] Adobe Experience Manager Help | API to invoke form data model service from adaptive forms

Avatar

Avatar

DarrenBiz

Avatar

DarrenBiz

DarrenBiz

26-04-2018

Edit - I just found the ApiResponse Object in the DEFAULT_SCHEMA. Nothing found on how to use it so I'll have to figure it out

1474475_pastedImage_0.png

Edit 2 - Ok it seems this is provided by the Swagger PetStore test API and not AEM Forms. Doesn't seem to be useable - Adobe?

Avatar

Avatar

jasons25523625

Avatar

jasons25523625

jasons25523625

30-08-2018

This is a worrying shortcoming of the solution. We're new to AEM Forms and REST integration will be essential and I really need to recognise success vs error responses and handle them appropriately.