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

Multiple cgi-callouts per dcr-item?

RonaldV

Hi,

Is it possible to define multiple cgi-callouts for 1 dcr-item?

I need 1 callout to open a customise browse-window and another to open an edit-window for the file that is referenced in the field.

If it not possible, does anybody know any tricks to make this happen?

TS 552 & Win2k

Thanks, Ronald

Find more posts tagged with

Comments

gzevin

I have not tried, but you could invoke another CGI from the first callout window

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

Adam Stoller

My reading of the datacapture5.0.dtd and datacapture6.0.dtd indicates that each item can have only 1 [cgi-]callout associated with it.
However, if you can use the OOTB browser element - that too indicates that it can have a [cgi-]callout associated with it, so you *might* be able to do something like <browser ....><cgi-callout ....></browser>

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

Migrateduser

Interesting question -- and good answers provided, so far. What are you trying to do? Maybe multiple callouts overcomplicate what you want to do.

Dave

Current Environment(s):
(1) TS 6.1 SP1 on W2K3
(2) TS 6.1 SP1 on W2K
(3) TS 5.5.2 SP2 on Win2K

RonaldV

What I want to acchive is this:
- Button-1: opens a customize browser window with "standard" browse behaviour except over multiple branches
- Button-2: open a dcr-edit window to edit the asp-file referenced by the value in the dcr-field

Is this clear?

Migrateduser

Yep, that's clear... I'm going to ask questions and suggest things on the side of simplicity so bear with me.

1. Will these DCR's (eventually) be in workflows? If so, why not have the workflow attach the DCT-selected file and edit it in a later usertask?
2. I realize this involves painful TS navigation, but what other benefit(s) does this provide that simply browsing the file and editing it does not accomplish?

Dave

Current Environment(s):
(1) TS 6.1 SP1 on W2K3
(2) TS 6.1 SP1 on W2K
(3) TS 5.5.2 SP2 on Win2K

RonaldV

Hi Dave,

thanks for your time.

1. no we will not use any workflow for these dcr's
2. it will indeed do no extra benefits then make life easier for the teamsite users. But isn't that what Teamsite is all about? :-)

To give you soem background on our TST-env. We have page-tpl's that in effect are collection of page-components. From a page-dcr user can browse to select a component to show on the page. But often they work the other way around: they want to modify some text in page X. Some they open the dcr for page X to find out the name of the component that contains the text to be modified. With this they have to open&edit the dcr for this. To make this easy for them they requested a "Edit component" button on the page-dcr.

Hope to hear from you, Ronald

Migrateduser

That actually sounds pretty cool. What about this, then --

Your DCT is normal, but your PT displays a modular page, as you had indicated. Instead of editing these other pages via the browser function, you put an EDIT button or link on the generated page, itself. The EDIT link can take you to an ActiveX control or even another DCT where you can edit the component. Using Javascript, you have the page regenerate after the editing of the component is done.

How does that sound?

Dave

Current Environment(s):
(1) TS 6.1 SP1 on W2K3
(2) TS 6.1 SP1 on W2K
(3) TS 5.5.2 SP2 on Win2K

gzevin

on a funny note... wait till TS 7 comes out. the screen 'snapshots' suggest a similar functionality being built....

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

RonaldV

Thanks Dave,

that sound like a nice alternative. I'll give it a go.

Meanwhile all other suggestions are welcome.

Ronald

JonathonG

Something simple that we do here is to have another item (historically a <hidden> type) with a cgi-callout defined right after the first item. Then, you set the first item's rowcontinue property to "t" and voila, you get 2 buttons next to 1 field. A couple of gliches with this:

1) In TS6.1, <hidden> items don't respect the rowcontinue attribute, and thus always appear on the next line. Assuming that you don't want this, I discoverd a workaround. You can specify a <checkbox> item with no contained <option> tags and it will display just the button.
2) Depending on your form layout, you'll probably have to play around with colspan in some of your other items to get the second button close to the first button. We had what was in essence a 2 column form (2 columns of data entry), and had to introduce another "dummy" column for the second button to appear in.

Jonathon
Interwoven Developer
Allstate, Inc.

RonaldV

Thanks Jonathan,

That sounds like another good workaround. I'll give it a try.

Ronald