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

save extended attributes

Eruditionist

Other than running iwextattr to set extended attributes is there a way to set additional attributes after an author clicks on save/generate for example.
Here are the default attributes that are set on a generated file.

TeamSite/Templating/PrimaryDCR: address
TeamSite/Templating/PrimaryDocumentType: Components/Address
TeamSite/Templating/PrimaryPT: address.xsl

I want to store this name value pair in addition to the default where the zip code will be retrieved from the DCR and than stored as ext attribute.

Zipcode: 09090

CGI Code to call iwextattr is not the route we want to take.

Find more posts tagged with

Comments

nipper

Not many choices, use the Tag command in the GUI, set up some FormAPI/call server on the save to add the EA or as part of the WF, parse the DCR and set the EA. #3 is easiest if you have Perl based WF or WF tasks.

Eruditionist

tag command in the GUI? Can you elaborate on that.

nipper

basic functionality select a file, use the File Menu and choose Tag

Adam Stoller

Not many choices, use the Tag command in the GUI, set up some FormAPI/call server on the save to add the EA or as part of the WF, parse the DCR and set the EA. #3 is easiest if you have Perl based WF or WF tasks.

If you're using a perl-based PT (.tpl) you could probably do this directly within the PT code - where you already have access to the DCR information and you can run CLTs like iwextattr...