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

TaggerGUI

msrinivas

TS 6.7.1 SP1 and MT 4.1.2

My understanding is that when MT is configured with TS every time a user invokes TaggerGUI a call to MT is made. Is there anyway to change/prevent the call to MT. The use case for the client is that they have MT and non-MT metadata fields. The MT ones don't change once tagged. So the calls to MT are just expense and they would like to avoid it.

TIA.

Find more posts tagged with

Comments

msrinivas

Bump!! Bump!! :rolleyes:

Migrateduser

Once the item has EAs set in TeamSite the TagUI does not automatically invoke TeamSite. It merely displays the current EAs. To invoke MT you neet to use the Suggest All button in the TagUI.

So the scenario cycles could be:
New document - blank EAs -> File:Tag -> TagUI invokes MT, MT reponsde to TagUI, TagUI loads values -> SAVE writes values as EAs.

File - existing EAs ->File:Tag -> TagUI displays EAs.

File -existing EAs -> File Tag-> TagUI displays EAs -> Suggest All button invokes MT -> MT responds to TagUI with values ->TagUI displays values -> SAVE writes new values over existing EAs.

msrinivas

Ah! That makes sense. Thank you, Morgen!