I see references in the api to "FormDesign" and we have a table in our database called "FORM_DESIGN" containing no records. What is it and where is it used?
So is there a part of maestro related to specifically to "Form Design", I can't find any documentation. Or is this something that happens behind the scenes - obviously all forms are designed.
There's documentation about it in TM core API.
The object holds info like name, version, last modified, active, etc..
I did read that documentation but nowhere does it explain what FormDesign is as a concept or why I might want to use it. Calling form.getFormDesign() on any of our production forms returns null so I'm wondering what it's purpose is if none of our forms seem to have any data for it.
Your FormDesing table on DB is empty, so you will never fetch any form design.
Most probably you have 2 different instances, one where the forms are designed, and another where the forms are imported and rendered.
FormDesing object should be in the instance where the forms are designed.
Our maestro forms are designed in the cloud using maestro at maestro.avoka.com.au so the TM instance they are attached to in the cloud would have the form design information, is that right?
Further, we then publish them from there to TM servers, test and prod that we host within our own infrastructure.
It contains metadata of Maestro forms. Not sure if db is used or only as a transient object related with the form.