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

Need of hidden fields

nirjari

[html]

Image

Image English
English Image

Image French
French Image

English image ALT
English ALT tag to the Image

French image ALT
French ALT tag to the Image

English link URL

French link URL

English link Target

French link Target

[/html]

In this code, en_image_id and fr_image_id are hidden fields. Where do these fields get their values from ? Are these fields required for capturing image from mediabin ? If these fields are not there and if I remove field_ref field from DCT, will it be possible to capture images from mediabin ?

Pls explain, as I dont understand the need of hidden fields of en_image_id and fr_image_id

thanks

Find more posts tagged with

Comments

Jamik

Well if you want to know why certain fields are set up the way they are in that DCT you should probably ask the original writer of the DCT. If they're not available you should probably do a little more research into how the DCT is being used, what files are being generated based on this DCT and how are those generated files being used. No one's going to be able to tell you what those hidden fields are used for based on the single DCT file you've provided as it's unique to your environment. At best we can only make guesses. (My guess is to store the value of the id on the file for use some point later)

I would also recommend you read up on the ECM connector in your TeamSite manuals as it covers what each field is related too for the mediabin dialog section.

And generally hidden fields are fields that you want to hide from the users but you want to populate through some automation generally based on user input because you want to have that information available.

Do a little more research and play around with it you should be able to figure it out easily.

nirjari

I was trying to read thru manual. I did not understand following points

1 In the first , but there is no item by the name "asset-id". Does it mean that new parameter by the name asset-id is created ? But I dont see the use of that parameter anywhere ? I

2 There is no item by the name path. en_image is connected to this "path". Does it mean that "path" oparameter is created and passed to mediabin

3 There is no item by the name "label" and en_image_alt" is passed as dialog-output. There is no dialog-input for this

what does this dialog-input and dialog-output do ?

thanks

Jamik

I was trying to read thru manual. I did not understand following points

1 In the first , but there is no item by the name "asset-id". Does it mean that new parameter by the name asset-id is created ? But I dont see the use of that parameter anywhere ? I

from the manual:

"asset-id. The MediaBin ID value for the selected digital asset. The value can later be used by the presentation template import tags to import the selected asset. When you specify an input value, it indicates a previously-selected asset that allows the browser to open up in the context of that asset."

2 There is no item by the name path. en_image is connected to this "path". Does it mean that "path" oparameter is created and passed to mediabin

If you actually read the manual and put some thought into what it's telling you, you'd see that those are params that get passed to mediabin and the list of possible params are:

asset-id
label
immediate
label
path
arearelpath
format
task
width
height
ceilingDirectory
destinationDirectory

So when you build your dialog box you then map those params to fields in your dct, and you specify if that field is the input (what gets sent to MediaBin) or the output (what MediaBin sends to the form) for the given parameter.

3 There is no item by the name "label" and en_image_alt" is passed as dialog-output. There is no dialog-input for this

what does this dialog-input and dialog-output do ?

thanks

for each param you can set what fields are input fields and what fields are output fields. not having mediabin i'm making a guess here but setting a field for a param as input most likely means the dialog box grabs the info in the dct field and passes the value from that field into ECM connector. Setting a field as an output field most likely means whatever value Mediabin returns for that paramenter gets placed in that dct field.

We don't have MediaBin so my guesses could be wrong but from what I've read and seen (we've looked at getting MB here but no department wanted to pony up the money) i'm pretty sure that's how it works. You really need to learn how to do research on your own as this seems like pretty basic questions to be asking and/or as been mentioned to you before you should get some formal training. I would assume you have a Dev environment where you could play around with these DCTs and see how they work. It should only take you a couple minutes of doing that to figure out what's going on.

nirjari

thanks for the answer. That helped to remove some confusion.

slow_report.rptdesign