readonly browser can't browse

If I set a browser item to readonly using FormAPI the browse button disappears. That's pretty lame. Does anyone have a workaround other than developing a custom callout for browsing and using a text instance instead?

Find more posts tagged with

Comments

Adam Stoller

I'm actually kind of interested in this too. I've looked at several threads in the forums, but none seemed to do what I wanted. Basically I want something like:

read-only text-field

BUTTON

I tried several ways of playing with this as a cgi-callout within a text-field specification - but I ran into the same problem you did, if you make the text-field read-only, the button disappears.
I'm thinking of trying to create two items, using row-continue where the first item is a read-only text-field and the second item is a cgi-callout button - the callout CGI code would have to make sure to set the value in the text-field rather than in the button's field.<item name="abc"rowcontinue="t">
<text>
<readonly/>
</text>
</item>
<item name="xyz">
<cgi-callout url=".../xyz.cgi?update-field=abc" label="..."/>
</item>It seems kind of hokey, but I haven't thought of a better solution yet (and haven't had a chance to test this idea yet either - if you do, please let me know if it works)

All of the above is with respect to TS5.5.2 - this maybe even more important in TS6 because the Forms UI "hides" the BUTTON until the field associated with it has the focus (this might be another reason to use the separate cgi-callout item from the text-field item...)

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

Migrateduser

That's an option but then I have to maintain a mapping between the field and it's corresponding hidden/etc, or use a naming convention. And I have to either develop a custom CGI browser or hack the default browser with URL params.

I wish the product would just work or someone would explain these kinds of things. I guess Interwoven hides the button when a field goes readonly because they don't want the value to change, but I could do that by disabling the callout myself if that was the behaviour I needed.

Adam Stoller

The mapping of the association can be done via the url query string - but yes, this does mean developing your own browser CGI (which we already have at our site, so it isn't that big a deal).

I agree - it would be nice if the stuff that came OOTB worked for everyone in every situation - but it isn't clear what the original design requirements were when they developed the DCT rendering code - and (IMO) even less clear in TS-6 why they feel they need to hide the buttons until the associated text-field has the focus -- but I figure it's not toooooo difficult to work-around (assuming my two-fields-is-better-than-one approach works)....

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