How do we enable Touch UI in a component where we necessarily want a Classic UI dialog?

How do we enable Touch UI in a component where we necessarily want a Classic UI dialog? Is there any other way apart from dialog conversion tool?

Is there an api method to get all the page paths that reference this page? How did you do it? Did you use jcr query?

Does this solution work? ACS AEM Commons page reference provided provides the references of a resource of the current page. It doesn't provide the pages where the current page is referenced. I believe "move" method accepts the pages where the current page is reference.Please do let me know if the AC...

Probably you are checking for the value in the wrong place. The value is saved in the workitem/metadata node under the history node. The node path would look something like below:/var/workflow/instances/server0/2019-07-25/<your-workflow-name>/history/<some-unique-id>/workItem/metaDataVerified on AEM...

While creating the dialog avoid using the usual convention of naming the property as "./propName" instead name it as "propName" and the value is stored in workitem metadata under history.If you want to store the dialog field value in the payload properties instead, name your dialog field as "./jcr:c...

This is mentioned in the official adobe docs (link below). Have you tried whether this works or not?Workflow Step Reference

If you were able to make it work, could you please share the custom js?

Use Handlebars. There's no explicit api to parse json directly in sightly. Instead you can dump the json in a handlebar template which can display the json data.

Please elaborate on where to include these two lines when the components are developed using HTL.Iparsys is included in the page component to hold the footer component. The extra div is coming up in the end of the page and it appears on Publish environment as well.Awaiting your response.