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

Browser field changes in DCR

sanhitaroyc

Hello,

I have a tpl file having a field -

< item name="SomeLink" pathid="SomeLink">
< browser extns="html" initial-dir="/common/bios/" required="f" maxlength="100" />
< /item>
----------------------------------------------------------
where the user needs to select the html file.

When the user selects the file, the entire path comes into the DCR.
eg: /common/bios/test.html

But I need the value in the field as only - test.html and not /common/bios/test.html

Is there any way through which this can be done?

Find more posts tagged with

Comments

Adam Stoller

Hello,

I have a tpl file having a field -

< item name="SomeLink" pathid="SomeLink">
< browser extns="html" initial-dir="/common/bios/" required="f" maxlength="100" />
< /item>
----------------------------------------------------------
where the user needs to select the html file.

When the user selects the file, the entire path comes into the DCR.
eg: /common/bios/test.html

But I need the value in the field as only - test.html and not /common/bios/test.html

Is there any way through which this can be done?

You can use a FormAPI onItemChange handler to do this, or take care of it within an onSaveValid handler - but both of those are questionable since the browser field functions based on the path being able to be resolved relative to the current workarea.

It might be better to use a hidden field with an onItemChange event handler on the browse field that sets the hidden field with just the file name - that way the browse functionality works as expected / desired, and you just point whatever needs the bare filename to look at the hidden field.

sanhitaroyc

Thanks ghoti for your reply.

I have written a js for onItemChange of that field which is shown below -

function init() {
alert("Helloo");
IWEventRegistry.addItemHandler("/Index/BiosHtml/ManagementBios/ManagementBiosLink", "onItemChange", testFunction);
testFunction(IWDatacapture.getItem("/Index/BiosHtml/ManagementBios/ManagementBiosLink"));
}
function testFunction(item) {
alert("testing");
var str= item.getValue();
var strt = str.substring(5);
alert(strt);
IWDatacapture.getItem("/Index/BiosHtml/ManagementBios/ManagementBiosLink").setValue(strt);
}
IWEventRegistry.addFormHandler("onFormInit", init);
---------------------------------------------------------------------

This code is working but the problem is that substring function seems to be called in an iteration because of which the value in the ManagementBiosLink field decreases and finally it becomes blank ... since i have kept an alertbox it appears that the substring function is called again and again.

Were you able to understand the problem that I am facing.

ISCBorisB

Posted code fragments should not get into a loop, not on it's own anyway. onItemChange trigger
does not fire if you modify Item's Value within code. You must be calling 'testFunction' somewhere
else as well, possibly on some other Events.

Adam Stoller

Posted code fragments should not get into a loop, not on it's own anyway. onItemChange trigger
does not fire if you modify Item's Value within code. You must be calling 'testFunction' somewhere
else as well, possibly on some other Events.

Actually, I have seen situations where the onItemChange event does seem to trigger itself when the event handler modifies the value of the item that did the initial triggering - perhaps this is a "feature" of the newer versions of TeamSite (7.2.x ?)

If this is, in fact, what's happening, then add a hidden field that you can use to track state information - something like:

function onItemChangeHandler(item) {
    var state = IWDatacapture.getItem("/some/hidden/field");
    if (state.getValue() == "") {
        state.setValue("1");
        // do the changes you want to item
    }
    else {
        state.setValue("");
    }
}

sanhitaroyc

Thanks ISCBorisB and ghoti for your reply.

onItemChange event is getting triggered but seems like it is going under iteration. this is TS 6.7.2 SP2, Linux OS

I have cut short my code just to check why there is an iteration.

I have my cfg file containing only one field -

< root-container name="Index" location="Index" >
< item name="ManagementBiosLink" pathid="ManagementBiosLink" >
< label >Management Bios Link
< browser extns="html" initial-dir="/common/bios/" required="f" maxlength="100" />
< / item >
< / root-container >

And my js code is -

function init() {
alert("Helloo");
IWEventRegistry.addItemHandler("/Index/ManagementBiosLink","onItemChange", testFunction);
}

function testFunction(item) {
alert("testing");
var str = item.getValue();
alert("test");
item.setValue("Sanhitaa");
alert("done");
}
IWEventRegistry.addFormHandler("onFormInit", init);

When the form loads, it goes like this -
msgbox -Helloo
I fill in the field
msgbox - testing
msgbox - test
msgbox - testing
msgbox - test
msgbox - done
msgbox - done

The msgbox clearly shows that testFunction is going into loop. Is there any way by which I can stop this iteration or atelast find out why this iteration is happening

Thanks,
Sanhitaa

Adam Stoller

onItemChange event is getting triggered but seems like it is going under iteration. this is TS 6.7.2 SP2, Linux OS
[...]
The msgbox clearly shows that testFunction is going into loop. Is there any way by which I can stop this iteration or atelast find out why this iteration is happening

Okay - I wasn't sure if it happened with 6.7.2, but apparently it does.
Why it happens - because you are changing the value of the field as part of your onItemChange handler.
How to prevent it from having an adverse effect - see my previous response.

The other alternative is for your onItemChange handler to disable the onItemChange event handler at the beginning and re-instate it at the end.

ISCBorisB

Okay - I wasn't sure if it happened with 6.7.2, but apparently it does

It's a TS bug then. Documentation clearly states that an event is triggered by manual modifications plus
(in some cases) focus change. That's how it used to work in previous TS Versions and in any event-driven
GUI that I worked with like VB, Forté, JS and whatnot

Adam Stoller

It's a TS bug then. Documentation clearly states that an event is triggered by manual modifications plus
(in some cases) focus change. That's how it used to work in previous TS Versions and in any event-driven
GUI that I worked with like VB, Forté, JS and whatnot

Based on the documentation, I would agree - it's a bug (feel free to file it)
Based on past experience, the fact that there is a work-around (what I posted) means that the bug is unlikely to get fixed any time soon.

If you (any of "you") do file this and manage to get a bug ID from support (sometimes they tell you they can't give it out, sometimes they give it out) - post the information here so others of us who are interested can register our organizations / our customer's organizations as being interested in seeing the bug fixed.