OL Learn

Nesting COTG widgets

Is it possible to nest COTG widgets inside a table?

For instance, using the Time Sheet COTG template in Connect Designer, if I nest a table in a td isnide the table id=“worksheet_table” , then the ADD and DELETE buttons no longer work as expected.

The DELETE button completely removes the whole row even if there is no data in the table. The ADD button adds a new row but copies the previous row completely inside the first cell of the new row, the other cells of this new row are left empty.

How can I nest COTG widgets and still use the ADD and DELETE button to add\delete nested and parent rows?
Could you please provide a demo of how to achieve this. We just purchased COTG and 50 user licenses and are struggling to get this working to publish the first project. This will welp with the COVID-19 testing.

Thank you for your help.

I suggest you open a technical support ticket through our website.
A technician will be able to guide you in what you are trying to do.

That’s a pretty poor response, I am sorry to say. I have been to support who weren’t able to answer, hence I came to the forum and you are bouncing me back to support. Phil has answered part of my question in another post.

There seems to be bugs or limitations with the COTG API in that when you add a new row dynamically, you can’t nest any other element inside it and control it with DOM events scripts like click, change…etc

This is a serious limitation as in the real world, most forms will contain nested elements inside dynamic rows. Four months later, we are still unable to design the form the way we would like using COTG. Questions have been raised as the sales speech promised so much but the software lacks key features for advanced form design.

We ended up using another third party software, SurveyJS https://surveyjs.io/create-survey and were able to design and deploy our form within 2 days withe ease and no frustration and most importantly for a tiny fraction of the cost of cotg.

With COVID and the new norm, we have seen an increase in demand in the creation of web forms, proof of delivery, email as opposed to post delivery, but most importantly web forms are at the top of our demands and we can’t simply spend weeks and months developing forms that our competitors can deliver with hours for a tinier fraction of the cost of cotg. It sounds like we made a poor investment here.

I think OL need to revamp their form creation within the software.

If you could raise this as a feature request and perhaps employ some of the SurveyJS API instead of the COTG API, that would be perfect.