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

links in data capture template / record

I have a need to have an active, clickable, anchor for each replicating DCR element. When editing the DCR through the interface, the link could be clickable to pre-defined value from the DCR.

I hope this made sense.

-Jon

Find more posts tagged with

Comments

You might try using the label (not supported). There was a post recently about putting HTML in labels. You can use FormAPI to set the label dynamically (not supported, but possible), if the URL is variable. But why not just use a callout?

Thanks for the reply. It's unclear to me how I would use a callout to perform this.

Your callout can activate a FormAPI function, which can do a window.open to any URL.

Was that last post even in english? Smiley Wink

I think I follow, however I have don't know to activate a FormAPI function. I checked out: http://devnet.interwoven.com/site.fcgi/techlib/049148, and I think I get it.

Thank you.

Edited by jsmarsalek on 07/28/04 09:13 AM (server time).

I've done both label and callout and can post code if you have trouble with the docs.

http://teamsite/iw/help/tst/formapi/formapi_25.html#SEC25

Isn't this what the left-nav portion of the Edit DCR window provides for you already? Or am I missing something here?

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

That is different.

The situation is as follows:

We received XML snippets from a vendor. Each one is a news item, and is imported into a DCR via some a workflow. A business user then uses the mere process of editing the DCR to either keep or delete, and order the news replicates. The TeamSite Templating becomes the news admin. tool.

I have received feedback that it would be nice to preview the full article since the news title, and snippet aren't very informative sometimes. Thus I have a need to add an arbitrary button within the DCR element that will bring the user to a external URL.

I hope this explanation helps.

-Jon

That helps! Thanks.

One thing that isn't clear to me, (I'm a n00b), is where the Userscript code goes. Can that be in the datacapture.cfg, or does it have to be in an external JS file?

I tried to get the demo. (shoe) from the above URL working, and it didn't seem to do the verification as listed in shoescript.js. I take it I don't have the type or location correct..??

I put this line in the DCR, and had the JS in the same directory as the .cfg file.
<script language="javascript" location="template-type" src="shoescript.js"/>

The formapi code can either be directly embedded within the DCT (generally not recommended except for quick/simple/one-off cases) or in a separate file - the location parameter tells templating where to look for the referenced JS file - in the case of "template-type" I believe the location should be in the same directory as the datacapture.cfg file.

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

If I follow you, then this code would work?

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE datacapture SYSTEM "datacapture5.0.dtd">
<data-capture-requirements type="content" name="News">

<ruleset name="">
<description></description>

<item name="myButton">
<hidden>
<cgi-callout label="My Button"/>
</hidden>
</item>

<script language="javascript">
function sayHello(item) {
alert ("Hello! You pressed the button!");
}
IWEventRegistry.addItemHandler("/myButton", "onCallout", sayHello);
</script>
</ruleset>
</data-capture-requirements>

Other than the fact that your cgi-callout should have a url attribute ... I believe that should work - though I haven't tested it myself and thus I might be missing something.

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

If you did, that would be swell.

-Jon

Are you sure FormAPI is enabled on your TeamSite server? In your iw.cfg, there should be something that looks like this:

[teamsite_templating]
enable_formapi=true

Jonathon
Independent Interwoven Contractor

I don't think it needs a URL, and if it did it would be just a dummy one.

Here's the label one; you might have to experiment to get HTML into the label. One thing to be aware of, if the labels are dynamic, you have to set them when the DCR loads and when a replicant item is added (there is some info on this at http://devnet.interwoven.com/forums/cgi-bin/showthreaded.pl?Cat=&Board=PRODUCTS_TEMPLATING&Number=29817&Search=true&Forum=All_Forums&Words=handle%20replicant%20addition&Match=And&Searchpage=0&Limit=25&Old=allposts&Main=29686).

function setItemLabel( item, label )
{
if ( item.itemImpl != undefined && item.itemImpl.label != undefined )
{
item.itemImpl.label = label;
}
}

Here's an example using the callout - you would want to check teamsite documentation to use CCI links, or JavaScript documentation for window parameters, etc. As far as your FormAPI not working, check the setting someone else on this thread mentioned in iw.cfg, then you may need to reboot/reset/whatever.

IWEventRegistry.addItemHandler( '/container/field', 'onCallout', handleFieldCallout );

function handleFieldCallout( item )
{
var vpath = getDCRvpath();
// window.open( '/iw/webdesk/edit?vpath=' + vpath + '&done_page=CLOSE&closeDCRParentWin=true' );
item.setValue( 'whatever' );
return( true );
}

Where the .js should go is arguable. I would put it in IWHOME/httpd/iw/formapi/category/type.js, where category and type are the DCT category and type. I would put shared libraries in IWHOME/httpd/iw/formapi/lib. There are threads about how to get FormAPI working (Interwoven - it should probably be enabled by default by now), or someone else can help you with that (setting in iw.cfg and possible restart of somethings). I don't know anything about shoe.

There are threads about how to get FormAPI working (Interwoven - it should probably be enabled by default by now),

It is enabled by default in 6.x - in fact there's no option to enable/disable it anymore in 6.x. It's only in 5.5.2 that you have to specifically enable it (I believe this was when they first provided the functionality and they wanted to hedge their bets by not enabling it by default [backwards compatible] and being able to disable it if needed [new functionality - might cause problems somewhere] - so it was a reasonable precaution to take when the feature was first introduced).

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

Ahh.. You were correct. It was disabled. I had the kind technology staff activate it, and it's rolling now. Thanks!

Example.rptdesign


        <script language="javascript">
 function doURLPreview(item) {

 var test2;
 test2 = item[/../Access Code].getValue();
 alert (test2);

 }
 IWEventRegistry.addItemHandler("/Article/Preview", "onCallout", doURLPreview);
        </script>

Thank you all for your help thus far.

Having a bit of a problem with the FormAPI, and trying to get the value of a sibling item, Access Code. The access code's value is essential in compiling the full URL for the new browser window instance.

I know that above code in the brackets [], won't work, it's there to show you where i'm stuck.

I can get the value of the item easily, but the sibling, just won't go.

Thanks in advance...

Something like this might work:


function doURLPreview(item) {
// Get the name of this item, and do a replace to get the sibling
var siblingLabel = item.getName().replace(/Preview/, "Access Code");

// Get a new IWItem which represents the sibling object
var sibling = IWDatacapture.getItem(siblingLabel);

    var test2;
    test2 = sibling.getValue();
   alert (test2);
}

Completely untested. Probably syntax errors all over the place. But you get the idea

--

Current project: TS 5.5.2/6.1 W2K

So, I thought I found a bug with the FormAPI. If the item's instance is a readonly it will return a null. There's a value in the dcr, so just switching it to text makes the code work.

I kept looking and I found:

"This method is not related to the <readonly> item type, which the FormAPI does not support."

Well, there I go. I just have to use the FormAPI to manually make the text instance read-only to cover me.

Fun!