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

Q about publishing editions

JackIntheBox

We maintain a XML page (version.xml) which contains the name of the published edition. This value, of course, is different for each edition. Is there some way for the user to hit File--> Publish and have the version.xml modified with the version name, date and publisher. The problem is that the version.xml page should be part of the edition.

My first thought was to create a custom menu item which kicks of a workflow. The workflow would modify the version.xml file in a specified workarea, submit it to staging and then publish the edition.
However, this idea is quite cumbersome and I would be thankful for some suggestions on this topic.

Thanks in advance.

Find more posts tagged with

Comments

Migrateduser

Instead of a custom menu item that kicks off a workflow, have the custom menu item just kick off a script that updates version.xml then submits it and publishes an edition. This would be a very simple script. You could then disable the File->Publish so the users would have to use your version.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Johnny

Another option is to create a publish trigger script.
It would be fired off every time a publish event occurs.

Triggers arent always the first answer to a problem though

John
Sydney, Australia

Adam Stoller

If I understand the issue correctly - Smitty's solution is cleaner and better - because the trigger script is post-operative and I believe they want to update the file *and* submit it along with everything else so it has to be pre-operative.

Presumably you would use either the iwnexted CLT or you are explicitly naming your editions when you publish them.

The name of the user, branch, etc., should be accessible via form variables within the custom CGI script.

--fish
(Interwoven Senior Technical Consultant)

Johnny

Looks like you are right there ghoti.
Over looked the part requiring the xml file to be part of the edition.

John
Sydney, Australia