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

hiding callout buttons

Adam Stoller

I've seen at least three threads (1, 2, 3) on this topic - and nobody seems to have found a solution.

However, in the interest of never ceasing to wonder - has anyone found a solution to this? or even a way to make the button inactive (perhaps using an onCallout even trigger?)

Like the others, we are in a situation where we want a callout button to appear for certain roles and/or based on certain conditions - but otherwise do not want the button to show up at all - or if it does, to probably send an alert indicating it can't be used in the present conditions and to then do "nothing" rather than trying to run the actual callout script.

Suggestions welcome. Known bug or feature requests welcome too.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Find more posts tagged with

Comments

Johnny

I don't know if it's ideal, but I've put this in recently to disable the callout when setting a field readlony.



        IWDatacapture.getItem("/story-page/dateline").setReadOnly(true);
        // The following line is a hack to prevent the callout button from
        // being executed. Unfortunately setReadOnly does not disable it!!
        IWEventRegistry.addItemHandler("/story-page/dateline", "onCallout", function(item) { return false });

You could use an alert in the anonymous function there.

Or perhaps you could use FormAPI to manage two different fields with the same label, and present one based on their profile.
John Cuiuli

Adam Stoller

The onCallout solution is what I figured I'd end up with - thanks for the reference code - I'll probably have it call a function which pops up an alert before returning false - so that the user doesn't sit there wondering why clicking on the button 100 times doesn't do any more than clicking on it once ;-)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Tim__D

If I understand your question correctly you can use this syntax to hide the callout button. I'm on 5.5.2

In this case I see the callout and the value when logged in under one of the given roles. Anything else and I just see the value.

Hope this helps.

<readonly required="t" size="65" maxlength="100" >
<cgi-callout url="/iw-bin/callout.ipl" label="Callout" window-features="width=400,height=100,resizable=yes,toolbar=no,scrollbars=yes"/>
<allowed>
<cred role="master"></cred>
<cred role="administrator"></cred>
</allowed>
</readonly>

Migrateduser

Remember, if you are on 5.5.x you should upgrade as soon as possible, since your version is at end-of-life.

Regards,

lissa

ISCBorisB

You may want to try something like the following:

// Hide Callout
var item = IWDatacapture.getItem("/story-page/dateline");
item.itemImpl.type = _iwdatacapture.types.kHiddenType;
item.itemImpl.callout = null;

That should work in 6.x

sunsun

here is your answer

make a container like this
<root-container combination="and" location="location" name="location">
<container name="hide" location="hide">
<item name="h" pathid="h">
<hidden>
<callout label="button"/>
</hidden>
</item>
</container>
</root-container>

and then hide the whole container by saying

var x = IWDatacapture.getItem("/location/hide/h");
x.setVisible(false);

do this on whatever condition you want it to happen.
This will instead of hiding the callout button will hide the container containing the callout. and thus solve your purpose.

Do tell me if this helped.

Adam Stoller

<readonly required="t" size="65" maxlength="100" >
<cgi-callout url="/iw-bin/callout.ipl" label="Callout" window-features="width=400,height=100,resizable=yes,toolbar=no,scrollbars=yes"/>
<allowed>
<cred role="master">
<cred role="administrator">
</allowed>
</readonly>This won't work because I need the hiding / exposing to be dynamic - and as far as I can tell there is no ability to add/remove 'allowed' / 'cred's via FormAPI.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Adam Stoller

// Hide Callout
var item = IWDatacapture.getItem("/story-page/dateline");
item.itemImpl.type = _iwdatacapture.types.kHiddenType;
item.itemImpl.callout = null;

What is this? It looks very much like some reverse-engineered non-supported code.

Unless you're with Interwoven Engineering and are stating that this is a supported interface - I don't think I want to try it.

Thanks, but no thanks.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Adam Stoller

make a container like this<root-container combination="and" location="location" name="location">
<container name="hide" location="hide">
<item name="h" pathid="h">
<hidden>
<callout label="button"/>
</hidden>
</item>
</container>
</root-container>and then hide the whole container by sayingvar x = IWDatacapture.getItem("/location/hide/h");
x.setVisible(false);Hmm, well this would certainly fall under a generally supported approach, however i'd have to consider the imapact on the structure of the DCR. A significant change to the structure could be bad.

I'll try to play around with this when I get back to that particular DCT (switched over to other stuff that's taken higher priority for the moment).

Thanks.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

ISCBorisB

You are correct, it is not supported and all that.

At some point I had to adhere to corporate Data Capture standards
that had little in common with IW DCT Layouts / GUI, that's where it's coming from...
I'm not advocating bad practices, it is just that sometimes we have little choice
other than use non-documented API.

Goes without saying, this tricks must be limited, documented and ramifications with vendor's patches, SP's
etc explained to the Client. End of day if Client still demands it I do not argue.

Just tried to be helpfull, do not think I deserved such a harsh rebuke.
Peace

Adam Stoller

I didn't think the rebuke was that harsh - especially considering that you didn't bother to post the disclaimer with the original posting.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

ISCBorisB

My bad, absolutely.
Will be more accurate next time.

Meanwhile, I have yet to see a single request on DevNet that states
"Only fully documented and supported suggestions, please".

4 different threads with participants that obviusly did their due diligence
granted a little deviation from TS documentation in my opinion.

-----------------------------------------------------------------------------------------------------
Your use of this posting is at your own risk. Neither ISCBorisB, any of its agencies,
nor any other party involved in creating, producing, or delivering this posting will be liable
for any direct, incidental, consequential, indirect, or punitive damages arising out of
your access to, or use of, the posting. Without limiting the foregoing, everything on the
posting is provided to you "AS IS" without warranty of any kind, either expressed or implied,
including, but not limited to, the implied warranties of merchantability, fitness for a
particular purpose, or noninfringement.

LooseCannon

In reply to:

My bad, absolutely.
Will be more accurate next time.

Meanwhile, I have yet to see a single request on DevNet that states
"Only fully documented and supported suggestions, please".

4 different threads with participants that obviusly did their due diligence
granted a little deviation from TS documentation in my opinion.

-----------------------------------------------------------------------------------------------------
Your use of this posting is at your own risk. Neither ISCBorisB, any of its agencies,
nor any other party involved in creating, producing, or delivering this posting will be liable
for any direct, incidental, consequential, indirect, or punitive damages arising out of
your access to, or use of, the posting. Without limiting the foregoing, everything on the
posting is provided to you "AS IS" without warranty of any kind, either expressed or implied,
including, but not limited to, the implied warranties of merchantability, fitness for a
particular purpose, or noninfringement.

That's great.... thks for the laugh!

cliffhanger

-----------------------------------------------------------------------------------------------------
Your use of this posting is at your own risk. Neither ISCBorisB, any of its agencies,
nor any other party involved in creating, producing, or delivering this posting will be liable
for any direct, incidental, consequential, indirect, or punitive damages arising out of
your access to, or use of, the posting. Without limiting the foregoing, everything on the
posting is provided to you "AS IS" without warranty of any kind, either expressed or implied,
including, but not limited to, the implied warranties of merchantability, fitness for a
particular purpose, or noninfringement.

Too FUNNY!!

Adam Stoller

I finally had a time to look into this a bit more.
It didn't seem to work.
Perhaps it's because I didn't use a doubly-nested container (I wasn't doing this at the root-level to begin with), and your setVisible directive still seems to be on the callout item, not the container surrounding it (I tried both, neither seemed to work).

While this isn't the greatest in terms of UI, it does provide the minimal functionality I needed (I used a function call with an alert)

function callout_handler(item){
    if (conditions-are-X){
        alert("This button is only active under Y conditions");
        return false;
    }
    return true;
}

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

sunsun

sorry.. when i was looking at he problem i was making changes so seems that i sent you the old one

var x = IWDatacapture.getItem("/location/hide/h");x.setVisible(false);
has to be
var x = IWDatacapture.getItem("/location/hide");x.setVisible(false);

and it works. I have tried to do it and it works
all you have to do is create a container with a callout button and hide the container instead of trying to hide the callout button.

did you try to hide the container?

Adam Stoller

I'm pretty sure I tried to hide the container.
This has once again fallen from the top of my priority list, but when I get a chance I may try it again.
When you verified it - did you do so in 6.5 or 5.x ?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

rodigz

Hi Ghoti,

How did you implemented it? Basically once field has value already the callout button should be disable.

Just want to know how did you implemented it.

thanks.

Migrateduser

Here's a less than elegent solution.

I just tried this and it worked.

Create two fields for the one you want. (model1, model2)
model1 has the button
model2 has now button and can be read-only if desired
On load of the page, hide model2.
When data is entered into model1 or another field then hide model1 and show model2.