Please hlep to fix "Resolve Conflict" problem

Hi
I am facing problem with "resolve conflict". My Branch is having two workareas. But the files in these two
workares are different. None of the files having same name.
when users started workflow, at the time of "submit task" it is giving an error message "resolve conflict". Please help me to fix this problem.
My users doesn't want to see this error message anymore.

Thanks in Advance
Raymand.

Find more posts tagged with

Comments

Adam Stoller

Hi
I am facing problem with "resolve conflict". My Branch is having two workareas. But the files in these two
workares are different. None of the files having same name.
when users started workflow, at the time of "submit task" it is giving an error message "resolve conflict". Please help me to fix this problem.
My users doesn't want to see this error message anymore.

Thanks in Advance
Raymand.

First - what version of TeamSite (including SP-level) on what platform?
Second - why are none of the files the same in the two workareas?
This sounds like a classic case of someone not understanding TeamSite basics - trying to make TeamSite do something it wasn't intended to do
Third - have any files been submitted from either of the workareas before?
Fourth - are there pre-selected files before trying to submit them, or is this an attempt to "submit the workarea" without any pre-selected files.

(there's probably more - but we'll start with the above)

Raymand

First of all I like to thank you for your response. Here are the reply msgs for your query.

First - what version of TeamSite (including SP-level) on what platform?
* Teamsite 6.5
Solaris 5.8
Second - why are none of the files the same in the two workareas?
* Two workareas are having different files.
Third - have any files been submitted from either of the workareas before?
* No. Whenever user clicks on submit button our workflow will trigger.
we are Not using default workflow submit.

Fourth - are there pre-selected files before trying to submit them, or is this an attempt to "submit the workarea" without any pre-selected files.
* User will select files and trigger the workflow using submit button.

Thanks in Advance

Bhargav Coca

I am not a big techie as Fish, But try comparing the files in Staging and in you Workareas, If there are no files in staging at all, as a test submit some files using the "Submit Workflow" Provided my Interwoven (Out of the Box Workflow), Try submitting few example files from both the branches and then, try to run the workflow which you are using to submit the files, see if the problem still persist. If it does, try changing the files you have submitted in the workarea and resubmit using the Submit workflow. See if it throws any conflicts. Please post your research, it would be lot more easier to resolve this at this point.
Thank you

nipper

Second - why are none of the files the same in the two workareas?
* Two workareas are having different files.
Third - have any files been submitted from either of the workareas before?
* No. Whenever user clicks on submit button our workflow will trigger.
we are Not using default workflow submit.

Many problems with resolve conflict are self induced. I suspect this is the case for you.

First, with very few exceptions Workareas on the same branch should NOT have different files. They will have different VERSIONS of files.

I have seen multiple implementations where they have had different files. Under VERY WELL DESIGNED circumtances this can work. Under less than idea circumstances this is a train wreck waiting to happen and you do not want to be near there when it does.

If there is a true need to make WAs with differnet files all the time, then they should be different branches.

Final point. People are very afraid of Get Latest. It is a good thing. Proper use of Get Latest and an Update task is critical to working with multiple WAs per branch. I had an implementation where 200 people used 1 Workarea. Works great, but the sight lends itself to that model well.

HTH

Andy

Adam Stoller

Second - why are none of the files the same in the two workareas?
* Two workareas are having different files.
Third - have any files been submitted from either of the workareas before?
* No. Whenever user clicks on submit button our workflow will trigger.
we are Not using default workflow submit.
Fourth - are there pre-selected files before trying to submit them, or is this an attempt to "submit the workarea" without any pre-selected files.
* User will select files and trigger the workflow using submit button.

As has been pointed out - trying to have different files in different workareas on the same branch is generally a losing proposition - and my guess is that you will need to resolve that issue sooner or later.
Additional Questions:

If you're not using the submit workflow that comes with TeamSite - what workflow are you using?
Does the workflow handle pre-selected files?
Does the workflow use a submittask or does it use an externaltask running the iwsubmit CLT?

Raymand

? If you're not using the submit workflow that comes with TeamSite - what workflow are you using?

* I developed workflow according to the user requirement.
? Does the workflow handle pre-selected files?
* Yes.
? Does the workflow use a submittask or does it use an externaltask running the iwsubmit CLT?
* Yes, workflow uses Submittask.

jbonifaci

When the submit a file that has conflicts, does it already exist in the othe workarea? If you're trying to have different files in the two workareas (which is an extremely poor design), there can be no files with the same path/name between the two workareas.

So if someone from workarea A creates a file '/directory/file.htm' and submits it to staging and then someone from workarea B creates a file '/directory/file.htm' and tries to submit it, they are going to get a conflict, as a different version of the file already exists in staging.

The same thing will happen if staging has say version 3 of file '/directory/file.htm' and workarea B only has version 1 or 2 of the file. If the user edits this file without performing a get latest first and tries to submit it, it will be in conflict because they edited an older version of the file and are trying to overwrite a new version.

Sounds to me like you have some serious branch/workarea design issues to resolve here.

~Jeff

margin_dynamic.rptdesign