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

OVERWRITE_****: Can I Get A Thorough Definition Please???

System

Can someone provide a detailed and thorough definition, including what each one does that the others do not, of these Submit options:

OVERWRITE_ALL
OVERWRITE_CONFLICTS
OVERWRITE_VERSIONED
OVERWRITE_NONE

I would love to know the difference between OVERWRITE_ALL and OVERWRITE_CONFLICTS and why you would use one of these as opposed to another in various situations. Same with OVERWRITE_VERSIONED - when would I use that?

OVERWRITE_NONE - wtf does that even mean? Why would you ever do this?

Pretty please. And please don't guess...I want a valid and thorough definition.

Find more posts tagged with

Comments

Adam Stoller

Can someone provide a detailed and thorough definition, including what each one does that the others do not, of these Submit options:

OVERWRITE_ALL
OVERWRITE_CONFLICTS
OVERWRITE_VERSIONED
OVERWRITE_NONE

I would love to know the difference between OVERWRITE_ALL and OVERWRITE_CONFLICTS and why you would use one of these as opposed to another in various situations. Same with OVERWRITE_VERSIONED - when would I use that?

OVERWRITE_NONE - wtf does that even mean? Why would you ever do this?

Pretty please. And please don't guess...I want a valid and thorough definition.

I cannot give an authoritative response - but judging from the workflow manuals (both WF Developer's Guide and WFM Developer's Guide) it looks like these have been simplified to a single boolean expression. As such, I would guess that those flags are historical in nature.

However, as you are most likely looking at this from a CSSDK perspective - there it appears that each one of these flags has a different value and thus there should be some distinction.

Although you don't always get what you're looking for - I'd suggest filing a case with Support and see if they can get an authoritative response from engineering (explicitly ask for such in your case). I'd be curious to see what the response is.

Migrateduser

Thanks - I stared at those definitions in the CSSDK for a long time and still came away with more questions than answers. I filed a support case today and I'll let you know what they say.

nipper

Thanks - I stared at those definitions in the CSSDK for a long time and still came away with more questions than answers. I filed a support case today and I'll let you know what they say.

Sure, they'll say I have no clue and refer you to this thread on DevNet.

Migrateduser

If that wasn't so true it would be funny...

vpatel

My answer will be similar to Adam's, it is not authoritative but here it is anyway:

Keep in mind that these four flags apply to Submit as well as Update. Also note that for our discussion here our source area will be the current workarea and target area will be the staging for submit and vice versa for update.

1. OVERWRITE_NONE:
- On submit: not to overwrite files in staging from the current workarea.
- On update: not to overwrite files in current workarea with the updated version.

2. OVERWRITE_CONFLICTS:
- On submit: overwrite files in staging from current workarea if there are conflicts.
- On update: overwrite files in current workarea from staging if there are conflicts.

3. OVERWRITE_ALL:
- On submit: overwrite ALL files in staging from current workarea.
- On update: overwrite ALL files in current workarea from staging.

4. OVERWRITE_VERSIONED:
- On submit: overwrite files, in staging, that have been submitted to staging before.
- On update: overwrite files, in current workarea, that have been submitted to staging.

Ok so all of these are pretty confusing and some of this confusion may stem when these flags are thought about from either a submit or an update perspective and not both. Some of these are similar in many use cases with subtle differences in few uses cases.

For example, let's say: you have an existing file a.txt (version 2+) and when you do an "update" with "OVERWRITE_ALL" it will overwrite your changes for a.txt and "reset" it back to the contents from previous version. This is as expected and fine and dandy. But what happens when you have a brand new file in the workarea (never submitted before)? Let's say: you have a brand new file new.txt (version 0+ I think it is) and when you do an "update" with "OVERWRITE_ALL" it will DELETE your file -- probably not the outcome you wanted. So in this case you probably want to do an "update" with "OVERWRITE_VERSIONED" or "OVERWRITE_CONFLICTS".

This is just one example but there many different permutations that you could possibly run into. Overall here is the gist of it:

OVERWRITE_NONE will not submit / update anything. This will come in handy for submitting new content and updating content that doesn't exist in the workarea and leaving rest of the stuff untouched.

OVERWRITE_VERSIONED will come in handy when you want to do an update but want to preserve unsubmitted files. OVERWRITE_CONFLICTS will come in handy when you want to submit/update files that are in conflict and conflicts typically arise when you have something versioned. So these two get a bit confusing on submit but hopefully my example above made it clear how it is different in update.

OVERWRITE_ALL: this is more or less a combination of OVERWRITE_VERSIONED and OVERWRITE_CONFLICTS.

I think as far as submit goes: OVERWRITE_ALL and OVERWRITE_CONFLICTS will give you "almost" similar results for submit.

Again this is not authoritative by no means. It is just the way I believe it is. In absence of any "additional clarification" on this, the best way to absolutely figure this out would be to do some testing out with various overwrite flags with submit as well as update ops.

My loooooooooong $0.02!

Adam Stoller

(Sorry Smitty - this is an interesting question, too difficult to keep from speculating ;-)

Hmm, interesting. Perhaps some of the flags only make sense depending on the context in which they are used.
There are three high-level modes:

I still agree, this needs better documentation, but I think that part of the reason it isn't well documented is because of the number of permutations - and the people responsible for the documentation probably never sat down with the engineers to understand them (just a guess)

Migrateduser

A speculative answer is better than no answer at all, I suppose, which is what I've received from Interwoven so far.

Vpatel's answer only made my head hurt. Not clear at all.

I can simplify my question by only looking at it in terms of a Sbmit operation. I think the main confusion may lie in the fact that it can be looked at differently across different operations, as ghotu mentioned. So let's just say I'm only talking about Submit. I still don't see when I'd want to use some ofthese flags as opposed to the other. In what cases would I not want to perform an OVERWRITE_ALL? What's the difference between OVERWRITE_ALL and OVERWRITE_CONFLICTS?

It wouldn't surprise me much if there was maybe one person in all of IW who might know the answer. Wouldn't surprise me if no one knew the answer either - if it's true that all the engineering and development has been outsourced.

Adam Stoller

A speculative answer is better than no answer at all, I suppose, which is what I've received from Interwoven so far.

Push back on Support and request a response from Engineering.