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

Change item labels using FormAPI

yanSi

Is it possible to using FormAPI to change the labels of containers and items in the datacapture form?

Currently, I have one container with labels in English and another container with labels in French and I use a radio button to show/hide the containers. I don't want to define two sets of containers in datacapture.cfg if all that's different between them are the captions.

Find more posts tagged with

Comments

Migrateduser

Sorry, that's what OR containers are for.

kaalraa

I don't believe there is anyway to do what you are asking. Better would be to use what you have solution along with your query.

Is it possible to using FormAPI to change the labels of containers and items in the datacapture form?

Currently, I have one container with labels in English and another container with labels in French and I use a radio button to show/hide the containers. I don't want to define two sets of containers in datacapture.cfg if all that's different between them are the captions.

chuckles

I printed a hack for TS 6.5 that does the job. This only does item labels, but you could probably extend it to containers. You just need to view source on a DCR edit screen and play with the DOM.

http://devnet.interwoven.com/forums_vb/showthread.php?t=10141&forumid=11

Migrateduser

I think hacks are great and all, but do you think it's likely to be forward-compatible? If it sticks to the DOM and IW doesn't change anything fundamental about the way their DCT's are structured, it would seem to be okay. But, this might become just another thing to have to put in change control when upgrades are performed.

Still, it might be preferred to do this hack versus maintaining multiple versions of the same thing.

chuckles

I wrote a JavaScript hack to get around the bug in 5.0 where datacapture.refreshform took forever on a DCR with lots of replicants and then in 5.5 it was built in to the API. I am hoping that once my hack outlives its usefulness, you can just drop in a supported method that does the same thing. Maybe that is wishful thinking Smiley Happy

Besides, we only do major upgrades about once in 18-24 months, so we will definitely get a lot of mileage out of this before it breaks.