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

Is it possible to deploy a specific version of dcr/output xml

swatis

I would like to know is it possible to deploy the 8th version of a dcr/generated output xml out of the 10 versions available in staging area to the target server? If yes then how?

Also is there a way to determine which is the hightest version number available for a file in the staging area?

Any pointers?

Find more posts tagged with

Comments

Samir_Friend

I would like to know is it possible to deploy the 8th version of a dcr/generated output xml out of the 10 versions available in staging area to the target server? If yes then how?

Also is there a way to determine which is the hightest version number available for a file in the staging area?

Any pointers?

Conceptually, all files that are deployed to a target server should be deployed from STAGING which contains the latest version. If you're deploying from WORKAREA, I don't think it's possible to get hold of an earlier version to deploy.

Coming to the second part, you can use iwcat CLT or refer to the cssdk docs if you're doing it in Java.

Rick Poulin

I think what Samir is getting at, is that the ideal way to do this is to create editions at proper points in time (even if it's on every submit/publish) because deploying files from a named edition is much much easier. Nevertheless...

I would like to know is it possible to deploy the 8th version of a dcr/generated output xml out of the 10 versions available in staging area to the target server? If yes then how?

You can if you write a custom Java workflow task. Pseudocode goes something like this:
* resolve CSSimpleFile in the workarea/staging/edition
* ask the file for a specific revision, or cycle through all revisions until you get the one you want
* get that version's path and put that in a filelist
* the key is that your "area" in your ODconf will have to be parameterized to take in fileVersionEight.getArea().getVpath(), and you'll only be able to deploy files from that same hidden edition -- meaning that the logic gets rapidly complex if you're looking to deploy multiple files at once and finding a hidden edition that's common to all.

Also is there a way to determine which is the hightest version number available for a file in the staging area?

csfile.getFileRevision()

ISCBorisB

I think what Samir is getting at, is that the ideal way to do this is to create editions at proper points in time (even if it's on every submit/publish) because deploying files from a named edition is much much easier. Nevertheless...

You can if you write a custom Java workflow task. Pseudocode goes something like this:
* resolve CSSimpleFile in the workarea/staging/edition
* ask the file for a specific revision, or cycle through all revisions until you get the one you want
* get that version's path and put that in a filelist
* the key is that your "area" in your ODconf will have to be parameterized to take in fileVersionEight.getArea().getVpath(), and you'll only be able to deploy files from that same hidden edition -- meaning that the logic gets rapidly complex if you're looking to deploy multiple files at once and finding a hidden edition that's common to all.

csfile.getFileRevision()

iwrlog CLT may simplify the search for Edition (named or anonymous) that contains required Version.
Ghoti once illustrated the usage in [post=130016]this post[/post].