6.7, setCollapsed(false), all DCRs, all branches?

Hello:

Short of adding the following JavaScript line manually to every datacapture.cfg file...

IWDatacapture.getItem("/myContainerPath/myContainerName").setCollapsed(false);

...In TeamSite 6.7, how do I un-collapse every DCR container or replicant by default?

Find more posts tagged with

Comments

brvhrt

use default=0 attribute in your DCT(s) for your replicants and or containers

ss_01.jpg

ss_02.jpg

Ambuj

Hello:

Short of adding the following JavaScript line manually to every datacapture.cfg file...

IWDatacapture.getItem("/myContainerPath/myContainerName").setCollapsed(false);

...In TeamSite 6.7, how do I un-collapse every DCR container or replicant by default?

What do you mean by un-collapse??

Can you post a screen shot as what you want to achieve?

tejul

Edit your application_custom.xml and set as follows:
< applications >
< param id="iw.formspub.expandall.enabled" value="false" >
< /param >
< /applications >

execute then the make_toolkit.ipl

Adam Stoller

Hello:

Short of adding the following JavaScript line manually to every datacapture.cfg file...

IWDatacapture.getItem("/myContainerPath/myContainerName").setCollapsed(false);

...In TeamSite 6.7, how do I un-collapse every DCR container or replicant by default?

The setting of whether [replicant] containers should be collapsed or expanded by default is set within the templating.cfg's viewoptions element's replicant-render attribute - the value being either "normal" or "collapsed" - but I believe the default is "normal" so unless someone explicitly set it to "collapsed" there, or added FormAPI code to explicitly collapse all the containers - they shouldn't be getting collapsed by default.
In the latter case, it should be relatively simple to find the offending code and comment it out - but if it's buried within some shared resource, it may not be a trivial fix, since fixing it in one place could be breaking it in a bunch of other places ....

Aryan

Greetings Adam,

I have a question... Even if I have default=0 as my container attribute, the container seems to get displayed if the container has mandatory elements.... Is this really the case? Or is this simply a case of making changes to the templating.cfg?

Adam Stoller

Greetings Adam,

I have a question... Even if I have default=0 as my container attribute, the container seems to get displayed if the container has mandatory elements.... Is this really the case? Or is this simply a case of making changes to the templating.cfg?

You need to make it clear whether you are talking about a brand new DCR based on this DCT or a pre-existing DCR based on this DCT in which one or more instances of this container have already been created.

In the former case, if you have min="0" and default="0" - then you should see essentially an empty/collapsed container.

In the latter case, unless you have replicant containers set to collapsed by default, you should see however many instances of the container are already populated when you bring the DCR up for editing.

If you simply specify a default="0" within setting the min="0" - I'm not sure that there's a defined behavior (basically your DCT code would be "wrong" in such a case).

Having required fields in an optional replicant instance which hasn't been created shouldn't be a problem ... though I suppose it's possible. The recommended solution in that case is to define the fields as non-required in the DCT and have onReplicantAdded event handler functions that marks the desired fields as required when an instance of the replicant is added.

Migrateduser

My $.02...

What Fish mentioned in his first reply above regarding viewoptions worked for us.

We're upgrading to 6.7.1 from 6.1, and many of our templates have nested replicants/containers. We were frustrated because the DCTs were opening existing DCRs with the containers collapsed (regardless of the min/max/default settings in the DCT)...no bueno!

It turns out that with TeamSite 6.7.1, for whatever reason the replicant-render attribute for viewoptions defaults to collapse-direct-children. We had to explicitly set replicant-render to normal for each template to expand all replicants for existing DCRs. Example is as follows:

[html]

[/html]

Also...FWIW...setting iw.formspub.expandall.enabled to true in application_custom.xml did NOT make any difference *shrug*. Not sure why. However, using the viewoptions setting is an acceptable alternative.

Tinac

<viewoptions replicant-render="normal"/> in the templating.cfg worked for me too - thanks Fish and dpike for providing the code!

Srinivasa Talla

Yes, we also used the same simple solution and no need to change any code.