FormAPI in TagUI

Server: Solaris
Version: Interwoven TeamSite 6.7.2.0
Build Number: 69626

Hi all,

I have a question about Form API in the new and "improved" TagUI interface. I have configured my rules so I see the Tag interface, and have attached FormAPI - when tagging one file the validation works fine, but when tagging more than one file the validation fails to work. Is there any way I can configure tagger to get FormAPI to work when tagging multiple files?

Thanks for your help in advance

Find more posts tagged with

Comments

Ugan

This is a bug in the teamsite, you will get a patch for this. Open a ticket with support they will provide you the patch for fixing it.

Thanks,
UD

jagadesh

This is not a bug. Its functionality. TS 6.7.2 is having two kind of Tag UI. Form API used in Next Generation TAG UI, it will support for single file tagging only.

The next release will support Form API for Multiple Files Tagging.

Please refer the Release notes documentation at Page no 100.

 The next generation Tagger GUI is invoked whenever an end-user selects a single file to tag through ContentCenter Standard or Professional. To ensure backward compatibility, the next generation Tagger GUI is capable of implementing rulesets based on the schemas used by both the original and next generation Tagger GUIs.

 The original Tagger GUI is invoked whenever an end-user selects more than one file to tag through ContentCenter Standard or Professional.

Tim__D

This is not a bug. Its functionality. TS 6.7.2 is having two kind of Tag UI. Form API used in Next Generation TAG UI, it will support for single file tagging only.

The next release will support Form API for Multiple Files Tagging.

Please refer the Release notes documentation at Page no 100.

 The next generation Tagger GUI is invoked whenever an end-user selects a single file to tag through ContentCenter Standard or Professional. To ensure backward compatibility, the next generation Tagger GUI is capable of implementing rulesets based on the schemas used by both the original and next generation Tagger GUIs.

 The original Tagger GUI is invoked whenever an end-user selects more than one file to tag through ContentCenter Standard or Professional.

It looks to me like FormAPI is implemented in 6.7.2 but only to a point.

FormAPI that is executed onSave or onSaveValid for example is run on all tagged files. I just implemented one today that truncates metaTagger fields which can get set to values higher than the DCT max length apparently. Other examples that also work are hiding fields onFormInit or setting hidden values etc..

What does NOT work unfortunately for me, is an onFormInit --> callServer() during the TagUI process to populate drop downs etc.. I think this is due to the callServer() being executed so many times in a row that only the last request actually has time to complete. Ideally each of these should be separate requests and send back variables or data in scope for each file only not every file in the list. An onFileChange event handler may have helped but not necessarily.

Tim__D

This is not a bug. Its functionality. TS 6.7.2 is having two kind of Tag UI. Form API used in Next Generation TAG UI, it will support for single file tagging only.

The next release will support Form API for Multiple Files Tagging.

Please refer the Release notes documentation at Page no 100.

* The next generation Tagger GUI is invoked whenever an end-user selects a single file to tag through ContentCenter Standard or Professional. To ensure backward compatibility, the next generation Tagger GUI is capable of implementing rulesets based on the schemas used by both the original and next generation Tagger GUIs.

* The original Tagger GUI is invoked whenever an end-user selects more than one file to tag through ContentCenter Standard or Professional.

If you look at the 6.7.2 supplement they make this statement.

In TeamSite 6.7.1 and earlier releases, Metadata Capture Tagging (sometimes
referred to as Tagger GUI) was used. This method is supported for backward
compatibility and is described in the “Configuring Metadata Capture” chapter of the
TeamSite Administration Guide.
* In TeamSite 6.7.1 SP1, the next-generation tagging system was introduced.
However, it could only be used to tag one file at a time.
* TeamSite 6.7.2 provides TagUI, which is the single-file and multi-file
next-generation tagging system. This method is the default for all tagging activities.

In the release notes it looks like they were talking about the functionality in 6.7.1. This makes sense as my other post indicates FormAPI is enabled but callServer() and probably other aspects fall down in multi-tagui