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

TagUI default values

Ram_IWOV

Hi All,

I have a little annoyance that I'm wondering if anyone has come across before.

with a TS 6.7.1 install, I have defined the metadata capture fields in datacapture.cfg and metadata-rules.cfg, some of these metadata fields are drop down boxes which have default selections applied.

Now, when tagging through CC-Pro (file -> tag menu option and workflow external task) the form displays correctly but none of the default selections are applied... anyone seen this behaviour before ?

[html]

Choose a weight.
Weight

[/html]

Regards,
Ram

Find more posts tagged with

Comments

Adam Stoller

Are you talking about tagging a file that's never been tagged before - or one which was previously tagged?

The former definitely sounds like an issue. The latter would be expected behavior (you won't want to override a previously selected value with a default value)

vaibhav2288

Hi All,

I have a little annoyance that I'm wondering if anyone has come across before.

with a TS 6.7.1 install, I have defined the metadata capture fields in datacapture.cfg and metadata-rules.cfg, some of these metadata fields are drop down boxes which have default selections applied.

Now, when tagging through CC-Pro (file -> tag menu option and workflow external task) the form displays correctly but none of the default selections are applied... anyone seen this behaviour before ?

[html]

Choose a weight.
Weight

[/html]

Regards,
Ram

Are this options coming from inline script or hardcoded in the datacapture.cfg ?

Ram_IWOV

Are this options coming from inline script or hardcoded in the datacapture.cfg ?

Hi,

Thanks for your reply.

Dropdown options are hardcoded in datacapture.cfg.

Regards,
Ram