Solved! Go to Solution.
Solved by bob_holland. Go to Solution.
Rikard,
Thank you for using Configurator 360.
At the present time you are not able to utilize forms.
Forms are one of the documented limitations:
http://help.autodesk.com/view/CFG360/ENU/?guid=GUID-96EA0CAA-73BB-42C2-94D8-73CC76791DC7
Rikard,
Thank you for using Configurator 360.
At the present time you are not able to utilize forms.
Forms are one of the documented limitations:
http://help.autodesk.com/view/CFG360/ENU/?guid=GUID-96EA0CAA-73BB-42C2-94D8-73CC76791DC7
Hi Bob,
I can’t find anything about Forms excepts for iLogic.. Maybe you should add a row about that you can't show a form when using an Action.
It would be a nice feature anyway in the future if you could make it work..
/Rikard
Yes indeed, it would be a nice feature. Thanks for the suggestion.
Hi Rikard,
How were you able to create a dynamic child with an Action? We typically use ETO Server and supply a design name parameter to the action to create the child. Did you have the design name (and other parameters) set in the ETO model and call an action that referenced those rule values?
We are considering creating a set of special uiProps that would be referenced by only an action. That way a form (javascript) could set those uiProp values prior to the action executing... emulating the ability to supply arguments to an action. Are you doing something like that?
Thanks,
George
Thanks for the quick reply Rikard!
We have some ideas that we are going to try and some feature requests we've submitted to C360 support that would allow us to create dynamic children via a form using the embedded UI. Our feature request is to supply a string parameter to an action call. We would put JSON in that string for the action to parse to create dynamic children with the property values we supply.
If and when we get that ability in C360 embedded UI API, then we will open source all our code that does that. Fingers crossed!