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; } } }

An item hidden by FormAPI is visible in DCR in preview mode

shekhar_iw

Hi,

I am using TeamSite 6.1 SP1 on Solaris.

I have a field called length which I need to hide from the users. The value of this field is being used for some validation.

I am using the following function for the same:
-------------------------------------------------------------------------
function init()
{
var itemToHide = IWDatacapture.getItem("/pageTitleIntro/length");
if (itemToHide)
itemToHide.setVisible(false);
}

IWEventRegistry.addFormHandler("onFormInit", init);
------------------------------------------------------------------------

During new form entry, or when DCR is opened in edit mode (by clicking on the edit link next to the DCR), this field remain hidden. If we click on the DCT directly, the is displayed.

Is there a way to execute a method similar to init() and hide the length item in preview mode.

regards,
Shekhar

Find more posts tagged with

Comments

Adam Stoller

Hi,

I am using TeamSite 6.1 SP1 on Solaris.

I have a field called length which I need to hide from the users. The value of this field is being used for some validation.

I am using the following function for the same:
-------------------------------------------------------------------------
function init()
{
var itemToHide = IWDatacapture.getItem("/pageTitleIntro/length");
if (itemToHide)
itemToHide.setVisible(false);
}

IWEventRegistry.addFormHandler("onFormInit", init);
------------------------------------------------------------------------

During new form entry, or when DCR is opened in edit mode (by clicking on the edit link next to the DCR), this field remain hidden. If we click on the DCT directly, the is displayed.

Is there a way to execute a method similar to init() and hide the length item in preview mode.

regards,
Shekhar

Nope - FormAPI is only executed in Edit mode - not in [pre]View mode.

There might be a FR for this?
You could mark the field as hidden explicitly in the DCT.

rodigz

Is there other way??

nipper

Is there other way??

Nope, that is a documented feature of formapi, as opposed to an undocumented feature (which we have seen many). :-)

Andy

sandy123

There can be a way but i dont know if it solves your problem.

You can make this item invisible in the datacapture.cfg only instead of making it invisible using FormAPI....

I hope it helps ...

Regds,
Sandy

ISCBorisB

There can be a way but i dont know if it solves your problem.

You can make this item invisible in the datacapture.cfg only instead of making it invisible using FormAPI....

I hope it helps ...

Regds,
Sandy

Your desire to help is admirable... Two years too late it's just a waste of electrons though

Srinivasa Talla

Is this issue resolved?

Anyone have the idea about 'any alternate method or the new versions supporting it(6.5 or later)'?

Thanks for your help.

nipper

I have never heard of any changes to this and would be very surprised if the FR ever gets much traction. It is not a trivial development effort for IWOV and IMHO, only a few people are truly interested in this.

Srinivasa Talla

We are using 6.5 SP2. Our problem is we have to change the label of a check box based on the branch name(part of it). I heared that changing label is available in 6.7.1. So we are trying to use 2 checkboxes and hiding them by using Javascript. But both are visible in view mode. If javascript is doing this functionality, why are they not allowing it in view mode..

If we use hidden attribute for any field and trying to get its value(either giving directly with value attribute or inline code), it is not working properly in Javascript. Without hidden attribute, they are working fine.

nipper

. If javascript is doing this functionality, why are they not allowing it in view mode...

Javascript is not doing it in view mode, that is basic DCT functionality

Try disabling FormAPI and view again, you will see the same thing.

I knew someone who was using the proxy that, when a DCR is viewed, it went through a special viewer (custom code) and then he could parse and show what he wanted. You could do soemthing like that, but it is a significant effort I expect.

Srinivasa Talla

I was talking about FormAPI sorry for that.

Ok.. my previous question should be :
If FormAPI is working in Edit mode, why is it not working or not available in view mode?...

The following information I found :
Note: Because there is no FormAPI in view mode, all items, whether hidden or previously invisible, are visible in view mode.
(FormAPI Developer's Guide - tst.650a.formapi.pdf - Pg 25,33)

Is there any update in recent versions about this feature?

ISCBorisB

If FormAPI is working in Edit mode, why is it not working or not available in view mode?...

It's absolutely correct behavior. FormAPI is essentially Java Script, evaluated by local Browser. As soon as IWOV allows it in the View
mode there would be no way to ensure that DC Form is not modified by scripting. Since the Form can not be saved that would have been a bug.

Is there any update in recent versions about this feature?

It is the same in 6.7.X and IMO that's how it should be. Your branch-related Label tuning can (should?) be done using DCT inline(s), that'll work in both modes

DateParameterIssue.zip

nipper

It is the same in 6.7.X and IMO that's how it should be. Your branch-related Label tuning can (should?) be done using DCT inline(s), that'll work in both modes

I had forgotten to mention this as well. I use inlines for a number of things, TS preview works great with the inline. The main difference is that the inline will only change the look during instantiation of the form and not during real time editing.

Srinivasa Talla

FormAPI is essentially Java Script, evaluated by local Browser. .... Since the Form can not be saved that would have been a bug.

The javascript should work for both modes(veiw and edit) in a browser. Are you saying this is a bug? Whatever may the mode, we should have control to show or hide an item. In normal javascript, we could hide a div/span/item.

Can we able to do this functionality by inline? Here is the requirement :
From database I will get the Line value 1, 2 or 3. and field value 1(checked) or 0(unchecked).

For 1, Display a check box with text : Line 1 - If field value is 1, make it readonly(so user should not change)
For 2, Display a check box with text : Line 2 - If field value is 1, make it readonly(so user should not change)
For 3, don't display anything

Once user submits DD, the user selection or default value should go to the database table. We got everything in Edit mode, but we are not able to hide in view mode. Here is our solution :
We are using two checkboxes because of the different text to display and getting the database value by using inline and keeping in a hidden variable1(making hidden in init()). In init(), we are checking the value of hidden1 and making active/inactive the checkboxes 1 and 2. When user submits, we are updating the hidden2(default is empty) based on the Checkbox 1 or 2. The hidden2 is the DD variable for the database. So it is working fine. So this is combination of inline and javascript(FormAPI).

Any one have idea how to handle this whole thing by using inline? Any example please.. Thanks for your help.

nipper

The javascript should work for both modes(veiw and edit) in a browser. Are you saying this is a bug? Whatever may the mode, we should have control to show or hide an item. In normal javascript, we could hide a div/span/item.

No it is not a bug. That is how the product is implemented. If you want it to behave differently you are quite capable of calling Interwoven and asking for a feature request. However, many customers do not want this behavior (I certainly don't). Since it is far from a consensus and a significant effort, fat chance of seeing this behavior change.

Can we able to do this functionality by inline? Here is the requirement :
From database I will get the Line value 1, 2 or 3. and field value 1(checked) or 0(unchecked).

For 1, Display a check box with text : Line 1 - If field value is 1, make it readonly(so user should not change)
For 2, Display a check box with text : Line 2 - If field value is 1, make it readonly(so user should not change)
For 3, don't display anything

Once user submits DD, the user selection or default value should go to the database table. We got everything in Edit mode, but we are not able to hide in view mode. Here is our solution :
We are using two checkboxes because of the different text to display and getting the database value by using inline and keeping in a hidden variable1(making hidden in init()). In init(), we are checking the value of hidden1 and making active/inactive the checkboxes 1 and 2. When user submits, we are updating the hidden2(default is empty) based on the Checkbox 1 or 2. The hidden2 is the DD variable for the database. So it is working fine. So this is combination of inline and javascript(FormAPI).

Any one have idea how to handle this whole thing by using inline? Any example please.. Thanks for your help.

Yes you certainly can do this via an inline. Maybe someone will write it for you.

So again you can wait for someone to do your job or you can start playing with inlines. Learn how they work, write a simple inline to just show a couple check box options.

Then change it to depending on something (say a variable setting), vary the label. That should take no more than 15 minutes.

Use that code to implement your fix.