Automate

Hi,

We are developing forms with workflows which will go in production soon. Until now in development when the users ask for an improvement, we implement it, we cancel all ongoing workflows and we deploy the new form.

The lead time of these forms/workflows can be very long, around 30 days.

In run mode, when we will be in production, I'm asking my self if there is a possibility to continue already launched workflows in the version of the launched form and new ones are launched on the new version? Or do you have any other idea on how to manage this?

Thanks for the answers and the help!

Regards,

Hi Skander,

You are correct, the already existing Processes/Documents work on the solution version they are originated on.

If you deploy a new version and launch a template it will automatically point to the latest version.

Already existing Documents should work fine unless the solution versions are abruptly corrupted or deleted from the database.

Hope this answers your question.

Regards

Hi,

We are developing forms with workflows which will go in production soon. Until now in development when the users ask for an improvement, we implement it, we cancel all ongoing workflows and we deploy the new form.

The lead time of these forms/workflows can be very long, around 30 days.

In run mode, when we will be in production, I'm asking my self if there is a possibility to continue already launched workflows in the version of the launched form and new ones are launched on the new version? Or do you have any other idea on how to manage this?

Thanks for the answers and the help!

Regards,

Hi Hammad,

Thanks for your anwer.

In fact this way of working doesn't allow even light changes, like for instance a mistake in a field label.

If I turn off the versioning option for the solutions, will the already launched workflows continue to work? Of course I'm talking about light changes, not a recast of it.

Thanks

Hi Skander,

You are correct, the already existing Processes/Documents work on the solution version they are originated on.

If you deploy a new version and launch a template it will automatically point to the latest version.

Already existing Documents should work fine unless the solution versions are abruptly corrupted or deleted from the database.

Hope this answers your question.

Regards

Hi,

We are developing forms with workflows which will go in production soon. Until now in development when the users ask for an improvement, we implement it, we cancel all ongoing workflows and we deploy the new form.

The lead time of these forms/workflows can be very long, around 30 days.

In run mode, when we will be in production, I'm asking my self if there is a possibility to continue already launched workflows in the version of the launched form and new ones are launched on the new version? Or do you have any other idea on how to manage this?

Thanks for the answers and the help!

Regards,

Hi Skander,

You can make the changes in the solution and the already existing Processes will work as they were on the earlier deployed versions.

Also, I don't think we can turn off the versioning for a Form solution, let me know if I am missing something here.

Regards

Hi Hammad,

Thanks for your anwer.

In fact this way of working doesn't allow even light changes, like for instance a mistake in a field label.

If I turn off the versioning option for the solutions, will the already launched workflows continue to work? Of course I'm talking about light changes, not a recast of it.

Thanks

Hi Skander,

You are correct, the already existing Processes/Documents work on the solution version they are originated on.

If you deploy a new version and launch a template it will automatically point to the latest version.

Already existing Documents should work fine unless the solution versions are abruptly corrupted or deleted from the database.

Hope this answers your question.

Regards

Hi,

We are developing forms with workflows which will go in production soon. Until now in development when the users ask for an improvement, we implement it, we cancel all ongoing workflows and we deploy the new form.

The lead time of these forms/workflows can be very long, around 30 days.

In run mode, when we will be in production, I'm asking my self if there is a possibility to continue already launched workflows in the version of the launched form and new ones are launched on the new version? Or do you have any other idea on how to manage this?

Thanks for the answers and the help!

Regards,

Hi,

I saw this option on version in the app configuration:

But I didn't find in the documentation if it switches on and off the versioning of the templates. Do you have more info on it.

Thanks,

Hi Skander,

You can make the changes in the solution and the already existing Processes will work as they were on the earlier deployed versions.

Also, I don't think we can turn off the versioning for a Form solution, let me know if I am missing something here.

Regards

Hi Hammad,

Thanks for your anwer.

In fact this way of working doesn't allow even light changes, like for instance a mistake in a field label.

If I turn off the versioning option for the solutions, will the already launched workflows continue to work? Of course I'm talking about light changes, not a recast of it.

Thanks

Hi Skander,

You are correct, the already existing Processes/Documents work on the solution version they are originated on.

If you deploy a new version and launch a template it will automatically point to the latest version.

Already existing Documents should work fine unless the solution versions are abruptly corrupted or deleted from the database.

Hope this answers your question.

Regards

Hi,

We are developing forms with workflows which will go in production soon. Until now in development when the users ask for an improvement, we implement it, we cancel all ongoing workflows and we deploy the new form.

The lead time of these forms/workflows can be very long, around 30 days.

In run mode, when we will be in production, I'm asking my self if there is a possibility to continue already launched workflows in the version of the launched form and new ones are launched on the new version? Or do you have any other idea on how to manage this?

Thanks for the answers and the help!

Regards,

Hi,

We are developing forms with workflows which will go in production soon. Until now in development when the users ask for an improvement, we implement it, we cancel all ongoing workflows and we deploy the new form.

The lead time of these forms/workflows can be very long, around 30 days.

In run mode, when we will be in production, I'm asking my self if there is a possibility to continue already launched workflows in the version of the launched form and new ones are launched on the new version? Or do you have any other idea on how to manage this?

Thanks for the answers and the help!

Regards,

Hi Skander

You want this behavior - the workflow instance completing with the version it was launched.  Every workflow engine I've ever worked with adheres to this.

Why? 

• Because it could corrupt
  • the way the assignments are made
  • the data
  • tasks that are required
  • overall - how it executes and finishes, if it can finish as all, depending on the changes you made. 
• And auditors would frown on this, too, as they won't know which version(s) of your process each instance used.  And when you think process (or workflow), think of company policy, business rules, roles and assignments.  And there could be many changes over time - especially with a long running process - which could completely change a process.  You may now require something at the start which isn't part of the already running processes, which again could cause problems. Etc.

For all of these reasons, and more, it is not a good idea to allow this.  Processes should complete with the same version they started with.  If needed, have an admin cancel an already running process.  

I hope this helps.

Best Regards,

Sigrid

Hi,

We are developing forms with workflows which will go in production soon. Until now in development when the users ask for an improvement, we implement it, we cancel all ongoing workflows and we deploy the new form.

The lead time of these forms/workflows can be very long, around 30 days.

In run mode, when we will be in production, I'm asking my self if there is a possibility to continue already launched workflows in the version of the launched form and new ones are launched on the new version? Or do you have any other idea on how to manage this?

Thanks for the answers and the help!

Regards,

Hi Sigrid,

Thanks for your answer.

I think you missunderstood me.

Of course a launched process in a version X of a workflow has to finish with this version X, this is obvious. And cancelling should be a bad idea too if we already started to create data in SAP.

My question was to know if:

• Launched processes in version X continue in version X
• New launched process can rely on a version X+1

But from what I understand, this is not possible. So after thinking about this issue, when we have to modify a form, named for instance "Product create":

• we will deploy a new solution (embedding the modifications) with the name for instance "Product create V2"
• we remove all rights to create a process with "Product create"

In this case all exisitng processes launched with "Product create" will finish with this version of the solution and all new processes will be launched in "Product create V2".

This looks to be the only way to manage it properly.

Thanks again for your answer.

Regards,

Hi Skander

You want this behavior - the workflow instance completing with the version it was launched.  Every workflow engine I've ever worked with adheres to this.

Why? 

• Because it could corrupt
  • the way the assignments are made
  • the data
  • tasks that are required
  • overall - how it executes and finishes, if it can finish as all, depending on the changes you made. 
• And auditors would frown on this, too, as they won't know which version(s) of your process each instance used.  And when you think process (or workflow), think of company policy, business rules, roles and assignments.  And there could be many changes over time - especially with a long running process - which could completely change a process.  You may now require something at the start which isn't part of the already running processes, which again could cause problems. Etc.

For all of these reasons, and more, it is not a good idea to allow this.  Processes should complete with the same version they started with.  If needed, have an admin cancel an already running process.  

I hope this helps.

Best Regards,

Sigrid

Hi,

We are developing forms with workflows which will go in production soon. Until now in development when the users ask for an improvement, we implement it, we cancel all ongoing workflows and we deploy the new form.

The lead time of these forms/workflows can be very long, around 30 days.

In run mode, when we will be in production, I'm asking my self if there is a possibility to continue already launched workflows in the version of the launched form and new ones are launched on the new version? Or do you have any other idea on how to manage this?

Thanks for the answers and the help!

Regards,

Hi Skander

If I understand you correctly, it does that automatically.  For example:

Product create version 1 January 15 - all instances of the process that started will finish

Product create version 2 is now deployed March 20 - all new instances of the process will use version 2 and complete with version 2

Product create version 3 is now deployed June 5 - all new instances of the process will use version 3 and complete with version 3

etc.

So I do not think you need to deploy a solution with a new name - Evolve versioning takes care of it for you.

I hope this helps.

Best Regards,

Sigrid

Hi Sigrid,

Thanks for your answer.

I think you missunderstood me.

Of course a launched process in a version X of a workflow has to finish with this version X, this is obvious. And cancelling should be a bad idea too if we already started to create data in SAP.

My question was to know if:

• Launched processes in version X continue in version X
• New launched process can rely on a version X+1

But from what I understand, this is not possible. So after thinking about this issue, when we have to modify a form, named for instance "Product create":

• we will deploy a new solution (embedding the modifications) with the name for instance "Product create V2"
• we remove all rights to create a process with "Product create"

In this case all exisitng processes launched with "Product create" will finish with this version of the solution and all new processes will be launched in "Product create V2".

This looks to be the only way to manage it properly.

Thanks again for your answer.

Regards,

Hi Skander

You want this behavior - the workflow instance completing with the version it was launched.  Every workflow engine I've ever worked with adheres to this.

Why? 

• Because it could corrupt
  • the way the assignments are made
  • the data
  • tasks that are required
  • overall - how it executes and finishes, if it can finish as all, depending on the changes you made. 
• And auditors would frown on this, too, as they won't know which version(s) of your process each instance used.  And when you think process (or workflow), think of company policy, business rules, roles and assignments.  And there could be many changes over time - especially with a long running process - which could completely change a process.  You may now require something at the start which isn't part of the already running processes, which again could cause problems. Etc.

For all of these reasons, and more, it is not a good idea to allow this.  Processes should complete with the same version they started with.  If needed, have an admin cancel an already running process.  

I hope this helps.

Best Regards,

Sigrid

Hi,

We are developing forms with workflows which will go in production soon. Until now in development when the users ask for an improvement, we implement it, we cancel all ongoing workflows and we deploy the new form.

The lead time of these forms/workflows can be very long, around 30 days.

In run mode, when we will be in production, I'm asking my self if there is a possibility to continue already launched workflows in the version of the launched form and new ones are launched on the new version? Or do you have any other idea on how to manage this?

Thanks for the answers and the help!

Regards,

Hi,

Yes that's exactly what I'm expecting as behaviour as in fact Evolve manages the versions. But it doesn't seem to work. When I try this I got an error message when I open a task from an ongoing process saying that a new version of the form is deployed and it cannot continue.

So I don't know why I have this message. Is it linked to a setting in evolve?

Regards,

Hi Skander

If I understand you correctly, it does that automatically.  For example:

Product create version 1 January 15 - all instances of the process that started will finish

Product create version 2 is now deployed March 20 - all new instances of the process will use version 2 and complete with version 2

Product create version 3 is now deployed June 5 - all new instances of the process will use version 3 and complete with version 3

etc.

So I do not think you need to deploy a solution with a new name - Evolve versioning takes care of it for you.

I hope this helps.

Best Regards,

Sigrid

Hi Sigrid,

Thanks for your answer.

I think you missunderstood me.

Of course a launched process in a version X of a workflow has to finish with this version X, this is obvious. And cancelling should be a bad idea too if we already started to create data in SAP.

My question was to know if:

• Launched processes in version X continue in version X
• New launched process can rely on a version X+1

But from what I understand, this is not possible. So after thinking about this issue, when we have to modify a form, named for instance "Product create":

• we will deploy a new solution (embedding the modifications) with the name for instance "Product create V2"
• we remove all rights to create a process with "Product create"

In this case all exisitng processes launched with "Product create" will finish with this version of the solution and all new processes will be launched in "Product create V2".

This looks to be the only way to manage it properly.

Thanks again for your answer.

Regards,

Hi Skander

You want this behavior - the workflow instance completing with the version it was launched.  Every workflow engine I've ever worked with adheres to this.

Why? 

• Because it could corrupt
  • the way the assignments are made
  • the data
  • tasks that are required
  • overall - how it executes and finishes, if it can finish as all, depending on the changes you made. 
• And auditors would frown on this, too, as they won't know which version(s) of your process each instance used.  And when you think process (or workflow), think of company policy, business rules, roles and assignments.  And there could be many changes over time - especially with a long running process - which could completely change a process.  You may now require something at the start which isn't part of the already running processes, which again could cause problems. Etc.

For all of these reasons, and more, it is not a good idea to allow this.  Processes should complete with the same version they started with.  If needed, have an admin cancel an already running process.  

I hope this helps.

Best Regards,

Sigrid

Hi,

We are developing forms with workflows which will go in production soon. Until now in development when the users ask for an improvement, we implement it, we cancel all ongoing workflows and we deploy the new form.

The lead time of these forms/workflows can be very long, around 30 days.

In run mode, when we will be in production, I'm asking my self if there is a possibility to continue already launched workflows in the version of the launched form and new ones are launched on the new version? Or do you have any other idea on how to manage this?

Thanks for the answers and the help!

Regards,

Hi Skander

You should have versions - go to the solutions icon, select one and click version history

You should see multiple versions if you've made changes:

Based on the date, future versions will use newest/latest version.  And if you wanted to back out a change, you can click on a previous version, it will open it and you can deploy it, which will create another version.

For form solutions, it should be automatic - creating versions and completing with the version that it started

For excel solutions only, if you have version checking on, it will tell you there's a newer version on the server and you should use it.

I'm not sure why you're getting that error.  Deleting a solution isn't possible if you have open tasks for that very reason - complete or cancel with the version you started with.

You can search the support site for it with the exact message or open a support ticket to track it down.  

Best Regards,

Sigrid

Hi,

Yes that's exactly what I'm expecting as behaviour as in fact Evolve manages the versions. But it doesn't seem to work. When I try this I got an error message when I open a task from an ongoing process saying that a new version of the form is deployed and it cannot continue.

So I don't know why I have this message. Is it linked to a setting in evolve?

Regards,

Hi Skander

If I understand you correctly, it does that automatically.  For example:

Product create version 1 January 15 - all instances of the process that started will finish

Product create version 2 is now deployed March 20 - all new instances of the process will use version 2 and complete with version 2

Product create version 3 is now deployed June 5 - all new instances of the process will use version 3 and complete with version 3

etc.

So I do not think you need to deploy a solution with a new name - Evolve versioning takes care of it for you.

I hope this helps.

Best Regards,

Sigrid

Hi Sigrid,

Thanks for your answer.

I think you missunderstood me.

Of course a launched process in a version X of a workflow has to finish with this version X, this is obvious. And cancelling should be a bad idea too if we already started to create data in SAP.

My question was to know if:

• Launched processes in version X continue in version X
• New launched process can rely on a version X+1

But from what I understand, this is not possible. So after thinking about this issue, when we have to modify a form, named for instance "Product create":

• we will deploy a new solution (embedding the modifications) with the name for instance "Product create V2"
• we remove all rights to create a process with "Product create"

In this case all exisitng processes launched with "Product create" will finish with this version of the solution and all new processes will be launched in "Product create V2".

This looks to be the only way to manage it properly.

Thanks again for your answer.

Regards,

Hi Skander

You want this behavior - the workflow instance completing with the version it was launched.  Every workflow engine I've ever worked with adheres to this.

Why? 

• Because it could corrupt
  • the way the assignments are made
  • the data
  • tasks that are required
  • overall - how it executes and finishes, if it can finish as all, depending on the changes you made. 
• And auditors would frown on this, too, as they won't know which version(s) of your process each instance used.  And when you think process (or workflow), think of company policy, business rules, roles and assignments.  And there could be many changes over time - especially with a long running process - which could completely change a process.  You may now require something at the start which isn't part of the already running processes, which again could cause problems. Etc.

For all of these reasons, and more, it is not a good idea to allow this.  Processes should complete with the same version they started with.  If needed, have an admin cancel an already running process.  

I hope this helps.

Best Regards,

Sigrid

Hi,

We are developing forms with workflows which will go in production soon. Until now in development when the users ask for an improvement, we implement it, we cancel all ongoing workflows and we deploy the new form.

The lead time of these forms/workflows can be very long, around 30 days.

In run mode, when we will be in production, I'm asking my self if there is a possibility to continue already launched workflows in the version of the launched form and new ones are launched on the new version? Or do you have any other idea on how to manage this?

Thanks for the answers and the help!

Regards,