You are viewing limited content. For full access, please sign in.

Question

Question

Workflow updating version comments incorrectly

asked on April 25, 2016 Show version history

We have a workflow with a conditional decision that moves a document to a particular folder if the folder is empty and merges with a file if the document exists.  

When the version control activity is used to add version comments, and the destination folder is empty, version comments are applied correctly.  If the document already exists and pages are merged, two different version comments will be applied.  The first will display the comments correctly and the second will not show any comments.  Every attempt to merge files after that will produce two versions both with empty comments.  I have attempted moving the Version Control activity to just about every portion of the workflow possible thinking another activity is causing the duplication, but placing this activity at the end of the workflow produces the same result.  

That said, I also have an Assign Field Values activity that takes the same token data and adds this to a read-only "version history" field.  This field displays exactly the same information as I wish to have in the version comments.  

What could be the underlying issue with this version comments issue in Workflow?  Any help would be greatly appreciated.

 

Thanks!

0 0

Replies

replied on April 26, 2016

Versions are created every time the document is modified. The Move Pages activity does not have the ability to add a version comment at this time. So assuming your workflow includes a Version Control activity followed by Move Pages, what you're seeing is expected behavior: the document is put under version control, which creates the first version and adds the comment specified, then pages are merged, which changes the document again, so the LFServer automatically creates the second version.

In the case where the folder is empty, I expect you move the document in and then run the Version Control activity, which puts the document under version control and adds the comment.

0 0
replied on June 26, 2018

Miruna, I have a similar case, where I'm not seeing the version comment that I assigned to the document

My use is that I'm assigning fields, then evaluating the document to see if it is version controlled.  If it is, then I want to update the version comment to identify the field that was updated.  I do not see any comment at all.  I know I went through the conditional statement because I got the email that is part of that in-line statement.

Thoughts?

6-26-18 vers control2.PNG
6-26-18 vers control3.PNG
6-26-18 vers control.PNG
0 0
replied on June 26, 2018

There is no way to add version comments to the the version created with Assign Fields. The activity does not have any options for that.

You'd have to do your own field update through the SDK in order to add version comments to it.

0 0
replied on June 27, 2018

Miruna, thanks for weighing in on this.  I was hopeful that it was something in my workflow setup, but that wasn't it. We do not have the SDK, so I will not be able to add the version comment to the change in field assignment.  Thanks.

0 0
replied on June 27, 2018

You don't need to purchase the SDK to use the SDK Script activity in Workflow.

1 0
replied on June 28, 2018

Miruna,  The SDK Script activity will require some assistance from our developer.  I saw that there is another post where you provided some C++ code to effect the field update and add the comment which will help. 

What are best references for learning more about the SDK scripting activity?  I was in the help files and as a beginner, I'm looking more for a tutorial at my level.  Is there anything like that or is there something at Empower that I should sign up for?

0 0
replied on July 6, 2018 Show version history

Miruna, can you weigh in on what I'm seeing in the version comments field after I update the contents of the Document Owner (or Approver) field? 

 

Sometimes I see the last version's comment in the comment field, other times I see a version comment from two or three versions prior to the one I just created.  How is it assigning this version comment, and why doesn't it just stay blank?

7-6-18 ver cmt3.PNG
7-6-18 ver cmt4.PNG
0 0
replied on July 6, 2018

How are you creating these versions?

0 0
replied on July 9, 2018

Miruna, these versions are being created when I assign the new title to the owner or approver field(s) see image above from June 26.  The documents reside in a version controlled folder.  Is this what you were asking?

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.