You are incorrect. The steps do modify the document. I should note that the version control activity happens more than once. The first time makes sure that version control is enabled. That works correctly (although I should note I would expect to be able to modify the comments at that time for the already existing version.) After I download an electronic document and attach it to document I am looking to update to a new version (which works correctly) the version control step, labelled in the diagram above as "Set Version Comments?" is where I am attempting to change the comments on the new version.

Right, that's what I'm saying. I don't see an activity that modifies the document after "Set Version Comments?" that sets the comment to "This doesn't appear to work..."

Any comments set in "Version Control" will apply to the original version if the document is not already under version control. They'd also apply to the version created by attaching the electronic document.

"This does not appear to work..." comment will apply to versions created after that activity.

In this particular case, none of it is working. If I have both of those set the comments on the file to something, in this case I have already tried setting the before change comments to "test" and the after change comments to "test2".

The file has no versioning comments period. This activity does not set any comments regardless of how I use it.

If I go to the document in question, I can manually set comments on a version, which I can then retrieve via the get version history activity.

But I can never set the comments through a workflow.

Are you attaching the e-doc to the first result of your search?

Which entry is the "Version Control" activity set to act on?

The edoc is attached to the first result of the search. Version control is set on the same entry.

Summary flow of the process:

Step 1: check to see if a document with the same name exists in the resultant folder. using a search and a branch. If it does, goto step 2, otherwise go to branch 2

Step 2: make sure version control is on for the already existing document.

Step 3: download the starting document as an edoc

Step 4: attach the edoc to the already existing document

Step 5: update version comments on the new version (of the document found in the search, not the starting document) that was just created (this step does not work.)

End Branch 1

Branch 2

Step 1: Turn on version control and set the comments to be "Initial Comments" (this also doesn't apply the comments)

Step 2: route document to the new folder.

End Branch 2

As a test process, to eliminate any other possibilities I setup this:

I find a particular document by it's entry ID. The comments on this version are set to "bad comments"

I then attempt to update the version comments using the version control activity to "good comments".

Yet, the version control activity appears to do absolutely nothing at all. when this process is run.

This works as designed. Version Control will put the document under version control, if it's not already under version control. Setting the comment is contingent on putting the document under version control.

In your case, it sounds like the document is already under version control, so there's nothing for the activity to do.

Set Version Comments sets the comment, but does not trigger a new version. There has to be a subsequent change made to the document so the Laserfiche Server generates a new version. That version will have the comment you specified in Set Version Comments.