Inline Alternative

I am using an inline command to write out two enter containers. The new requirement that I have is to write one of those at a given time based on a certain selected item. For that ofcourse Inline won't work and I have to switch to FormApi. Just wondering if I can actually write out different containers at a fixed position with in a dct like substitution for inline command functionality but based on various conditions?

Find more posts tagged with

Comments

ISCBorisB

I am using an inline command to write out two enter containers. The new requirement that I have is to write one of those at a given time based on a certain selected item. For that ofcourse Inline won't work and I have to switch to FormApi. Just wondering if I can actually write out different containers at a fixed position with in a dct like substitution for inline command functionality but based on various conditions?

You can not do that in FormAPI, not in the supported manner anyway. What you can do is to have both containers
present and toggle their (mutually exclusive?) visibility based on your condition.

It seems to me that making two different types out of that structure would be a better solution.

enthusiast

I have done the toggle with FormApi many times before but this situation demands are different. We can literally have tens of forms based on the selection criteria and since inline command doesn't work interactively I am just wondering if I can perhaps popup another dct form whose inline command is generated dynamically based on the selection of first form?

ISCBorisB

I have done the toggle with FormApi many times before but this situation demands are different. We can literally have tens of forms based on the selection criteria and since inline command doesn't work interactively I am just wondering if I can perhaps popup another dynamic dct child form when such a selection is made in the parent form?

Using FormAPI it is technically trivial to create a pop-up window with the new DC Form. URL Command is "newform", see
Interwoven® User Interface Customization Guide for details.

It won't be trivial however to *link* related DCRs and automatically maintain referential integrity on Deletes, Updates,
etc... You will have to come up with the linking strategy (like using extended attributes for example) and prohibit / enforce
certain changes when for example *parent* update requires *child* changes and so on.

From the little you've described I do not think it's worth the efforts. Your own CGI callout with the "refined for the task" GUI may be a simpler solution

enthusiast

I don't really want to link those two forms together one the child form is created and just want to be able to pop a new form based on a certain selection. The UICG manual doesn't have any example of the "newform" command.

enthusiast

Never mind I figured how to call the userform command. Is there a way to pass parameters to Inline command at the form load time?
e.g.

<inline command="/teamsite/iw-home/httpd/iw-bin/Custom/redesign/myscript.ipl <param1> <param2>"/>

Frederik

To my knowledge, those parameters would have to be fixed/literal (in the DCT).