cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Workflow is taking a new version when completing a task.

Former Member
0 Likes
519

Hello Experts,

I am working with workflows and I have a problem, in my development system I am completing some work items manually using SWIA, those work items are "in process" status and they are from the last year, early this year I made a change in this workflow adding a couple of activities in the flow. The problem is; now when I am trying to complete those work items manually for some reason the workflow is taking the new version of the workflow, even when these instances of the workflow were created with an old version, should be using the version with it was created. this only happens in my development system, I have tested in Quality and it works perfect even when the new version is in Quality and production but in those system the behaviour is as expected when I complete the work item manually the workflow uses the version with they were created, which is an old one. so the problem is just in Developemnt and I wanna know if there is any way for fixing this.

I hope I explained myself clearly.

Thanks in advance for your help.

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Likes

So let me get this straight,

If you go check the workflow log for this workflow and technical details says version 0004 for step 1. After manually completing this task the next step has in technical details 00012?

That doesn't sound like that should be happening.

If I were you I would check OSS for similar behaviour if during a process the version changes.

If you don't find anything usefull I would take some screenshots and raise a message in OSS.

Also be aware that if you change a task on method level that is workbench and doesnt conform to version management.

Kind regards, Rob Dielemans

Former Member
0 Likes

Hi Rob.

This is what is happening,

I have a lot of workflows hanging in my system since last year, let's say that those workflows instances were created with WF version 003, early this year I changed somme things in the workflow, I added a couple of activities and those changes were moved into QA and Prod, at this point everything is OK.

Now in my dev system I am trying to complete some of these work items from the last year, the correct behaviour should be that thos instances of the workflow use the version 003 in what they were created, but instead when I am completing the work item, wich is the last activity of the old version instead of finishing the workflow is falling on a next activity which is one of the activities added in the new version let's say 004. this is my problem, I don't know why the workflow is using a new version instead of using the version in what it was created. I QA I tried the same and is working as expected, but in development those old workflows are acting like they were created with the newest version and that's not correct.

Former Member
0 Likes

Hello,

In DEV you can change workflows without generating a new version and it sounds like that is exactly what you did. Lesson learned! You can't do anything about it now. Always generate a new version when making changes.

It's only DEV so don't worry too much about it.

regards

Rick

Former Member
0 Likes

Hi Freddy,

If the issue is only there in Dev system, some changes has been made already and not yet moved to Quality.

Is it happning for all workflows in Dev system?

Thanks,

Viji.

Former Member
0 Likes

Hello Viji,

The workflows are exactly equal in Development, Quality and Production, no changes are pending, the problem seems to be related to the versions on each system. I found note 1027175, and I can see some differences between the versions in the systems, so I think is a known issue in workflows and there is no way we can get the old workflows in their original version back

anjan_paul
Active Contributor
0 Likes

Hi,

  Can you check and share screenshot in log which version is showing.