nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Using formapi to make Containers invisible

Mashuk

Hi,

Im quite new to formapi, Ive read some docs about formapi, e.g. setVisible(true) setVisible(false) etc The manual I have been reading does not mention anything about making an entire container invisible. i have tried just calling the container name, but to no avail e.g

IWDatacapture.getItem("/Container1/").setVisible(false);

My Container1 is a replicant consisting of two items. Either I restrict the visibility of the container with 1 command, or I will have restrict the visibility of each item with a separate command, depending upon how many replicants a user will add.

Surely there must be an easier way of controlling the visibility of containers????

Thanks
Mashuk

Find more posts tagged with

Comments

JonathonG

Try removing the trailing / in the item address. In other words change this:

IWDatacapture.getItem("/Container1/").setVisible(false);

to this:

IWDatacapture.getItem("/Container1").setVisible(false);

Jonathon
Independent Interwoven Contractor

Mashuk

We are using TS6.1, and with that, the replicants can be incorporated into the containers tag. However when I tried to make the container invisible, that didnt work.

So I took some of the 552 functionality and explicitly added an item for the replicants. By doing this, the entire container disappeared on a change item event, which is what i wanted to achieve.

Thanks
Mashuk

jkm

Hi All,
I am able to make my containers invisible and visible on change of selection but if a user entered some content in the container fields then I want to make them visible.

Is there any easy way around to make them visible as well rather than going to each and every child element and making them visible

TS6.5+sp2 + unix

jkm

Any ideas please?

Adam Stoller

Hi All,
I am able to make my containers invisible and visible on change of selection but if a user entered some content in the container fields then I want to make them visible.

Is there any easy way around to make them visible as well rather than going to each and every child element and making them visible

TS6.5+sp2 + unix

Are you saying that you want to modify the behavior you've managed to acheive such that if they select something that would normally make the fields hidden - but the fields happen to have values in them - you want the fields to remain visible?

If so - then yes - you will have to examine the contents of all the fields that you are planning to make invisible to determine whether or not you should make them invisible - I don't think there's any short-cut here other than that you might be able to short-circut the examination of the fields as soon as you find one field with a value (i.e. an all-or-nothing approach) - but you (hopefully) know your requirements better than I.

nodatamsg.JPG

jkm

Yes Adams, you understand it pretty well ... but if I need to identify too many fields inside multiple containers then it is kind a mess..seems to be too much formAPI involves in this and too many scenarios to cover..
Thinking of some easy way arnd to so that it is user frindly as well and quick to implement

Adam Stoller

Yes Adams, you understand it pretty well ... but if I need to identify too many fields inside multiple containers then it is kind a mess..seems to be too much formAPI involves in this and too many scenarios to cover..
Thinking of some easy way arnd to so that it is user frindly as well and quick to implement

So essentially you want everything to do what you want without you having to do much to make it work... Good luck ;-)

jkm

hehe ..no Adams, I am ready to do work but dont want to overkill in little amount of time
Is this sensible to implement this kinda extensive formAPI on a single DCT ... wat are the best practices in terms of formAPI ..
Is this a good design to hide 30-40 fields and multiple 2-3 level containers .. I havent implemented this before but just getting a feel it will be pretty complicated and will require some amount of time which we dont have at the moment.

Adam Stoller

hehe ..no Adams, I am ready to do work but dont want to overkill in little amount of time
Is this sensible to implement this kinda extensive formAPI on a single DCT ... wat are the best practices in terms of formAPI ..
Is this a good design to hide 30-40 fields and multiple 2-3 level containers .. I havent implemented this before but just getting a feel it will be pretty complicated and will require some amount of time which we dont have at the moment.

If you don't have the time, don't do the crime ;-)

Seriously though, if you don't have time, then you should keep things as simple as possible. You have code that basically says - "if you select this then hide that" - right?

In order to change it so that it becomes - "if you select this then hide that unless that contains values" - clearly is going to require that you traverse through every child element of that in order to determine if there are any values in order to determine if you can / cannot hide that.

It sounds overly complex and something which, especially if you don't have time to work out the design and implementation, should be handled as user training.

kisnak

Hi ,
I want to make some of the items in all the containers(replicants) invisble when user tries to click on "+". The formapi I wrote is making only first containers items invisible

I am pasting the code for DCT and formapi,could you please help me in this regard

<script language="javascript" location="template-type" src="quicklinksItem.js"/>

link

Link Title
Please insert the link title.

Document
Please select document's Normalized vPath

extns=".gif,.jpg,.jpeg,.bmp,.png,.tif,.tiff"/>

form api
function init() {

for(var i=1;i<=10;i++) {
var documentItem=IWDatacapture.getItem("/link[" + i + "]/document");
var urlItem=IWDatacapture.getItem("/link[" + i + "]/url");
if(documentItem) {
documentItem.setVisible(false);
}
if(urlItem) {
urlItem.setVisible(false);
}
IWDatacapture.redraw();
}

kisnak

Sorry ,I think browser has interpreted the dct code which I pasted
Now I attached it as doc,please check it and help me.

Adam Stoller

Sorry ,I think browser has interpreted the dct code which I pasted
Now I attached it as doc,please check it and help me.

You need to wrap code in either [html]...[/html] blocks to avoid it being interpreted (you can also use [code]...[/code] - but it's trickier - I've posted about this numerous times in the forums - search and hopefully you'll find)

That being said - your init routine is only called ... on init.
If you're using TS 6.5 or higher - dig out your copy of he FormAPI manual and look for information about onReplicantAdded.

ISCBorisB

Sorry ,I think browser has interpreted the dct code which I pasted
Now I attached it as doc,please check it and help me.

As already mentioned by Ghoti, you should call your code onInit and onReplicantAdded. In addition, your target Container is a replicant.
On both events you'll have to use IWItem.getChildren() method and loop through all Container replicas. I would recommend to code a
separate function and call it from(or as) event handlers