Date Picker throwing error "'touchUiDialogPath' property invalid or missing" | Community
Skip to main content
abhigyanswaroop
Level 2
June 12, 2018
Solved

Date Picker throwing error "'touchUiDialogPath' property invalid or missing"

  • June 12, 2018
  • 20 replies
  • 8444 views

Hi All,
We are upgrading to AEM 6.4 currently and as a part of repository restructuring  we have moved all the workflow related data to
"/conf/global/settings/workflow", during this we also moved out date picker dialog to this folder.

after moving that we are getting
error touchUiDialogPath' property invalid or missing

however, we have configured,
touchUiDialogPath to "/conf/global/settings/workflow/dialogs/schedule_publish_date_picker/cq:dialog"

which is the current location of cq:dialog for date picker.
this date picker has
resourceType : granite/ui/components/coral/foundation/form/datepicker

Can anyone please suggest if anything else is to be done in order to have date picket in workflow dialog path.

Thanks in Advance.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by smacdonald2008

See this video:

20 replies

smacdonald2008
Level 10
June 12, 2018

Does the coral/granite date picker work in a normal component dialog? That will tell us if there is something wrong with that specific resource type on your upgraded instance.

See if you can build a component dialog with that resource type as described here - Scott's Digital Community: Building Experience Manager Component using Granite/Coral Resource Types

abhigyanswaroop
Level 2
June 12, 2018

I saw it is working fine on page properties (on/off) fields.

smacdonald2008
Level 10
June 12, 2018

So its working fine in component dialogs but fails when you have a dialog with that resource type as part of a workflow?

abhigyanswaroop
Level 2
June 12, 2018

yes, it works fine on component dialog but when I am using it in workflow dialog specifying the cq:dialog path to it it gives the above error.

smacdonald2008
Level 10
June 12, 2018

I am going to test this too to see if i get the same result. I will post back my findings.

abhigyanswaroop
Level 2
June 12, 2018

Thanks smacdonald2008

smacdonald2008
Level 10
June 12, 2018

Can you show a screenshot of the workflow model where you are using this custom step?

Ratna_Kumar
Level 10
June 12, 2018

Hi,

You cannot use Touch UI resourceTypes in classic UI workflow. there is no full implementation of workflow in touch UI..So better pls use classic UI workflow but don't use touch UI resourceTypes

Also I see that you used xtype: cqinclude and you are using touch UI dialog path.

Thanks,

Ratna Kumar

abhigyanswaroop
Level 2
June 12, 2018

I think this is not correct, that how it works in case of workflow and it works fine in AEM 6.2 version.

abhigyanswaroop
Level 2
June 12, 2018

Hi smacdonald2008​,

below is my workflow model,

and custom dialog looks like,