Sync new version changes with old version screens

100 views
Skip to first unread message

bestfri...@gmail.com

unread,
Nov 4, 2014, 4:20:05 PM11/4/14
to suppor...@runmyprocess.com
Hi Team,

Could you please whether there is any way to make all the screens in the same Project with different versions run with the latest version changes without throwing any error.

Currently we have screens running with different versions and still more changes to be deployed in the new version.


Thanks
Sai

Mariem Mouakhar

unread,
Nov 5, 2014, 5:00:07 AM11/5/14
to suppor...@runmyprocess.com
Hi,

can you please give us more details about your request ?

Best regards,

--
Mariem Mouakhar,
Customer Solution Engineer

bestfri...@gmail.com

unread,
Nov 6, 2014, 1:26:14 PM11/6/14
to suppor...@runmyprocess.com
Hi Mariem,

IN our RMP project, we have many versions and the screens created in each version run with the same till it gets completed .

Suppose , in my project we have two versions -A and B

Screens created with version A(eg -5 processes were started) and screens created with B (eg 4 processes were started)

Now if a create a new C and I want all the processes available run with new version changes i.e C in this case.



Thanks
Sai

Mariem Mouakhar

unread,
Nov 7, 2014, 4:47:04 AM11/7/14
to suppor...@runmyprocess.com
Hi Sai, 

Yes you can make all the screens in the same Project with different versions run with the latest version change and you have two choices:
      
     - You just launch the new version in prod mode 
     -  You choose the process with you want and you select the latest version like the screenshot bellow.
 
           Inline image 1   

And despite that process were started they will continue with the new version. 

Best regards 

bestfri...@gmail.com

unread,
Nov 7, 2014, 10:12:57 AM11/7/14
to suppor...@runmyprocess.com
On Friday, November 7, 2014 4:47:04 AM UTC-5, Mariem wrote:
> Hi Sai, 
>
>
> Yes you can make all the screens in the same Project with different versions run with the latest version change and you have two choices:
>       
>      - You just launch the new version in prod mode 
>      -  You choose the process with you want and you select the latest version like the screenshot bellow.
>  
>               
>
>
>
> And despite that process were started they will continue with the new version. 
>
>
>
> Best regards --
>
>
>
>
> Mariem Mouakhar,
> Customer Solution Engineer
>
>
> Website: Fujitsu RunMyProcess

Hi Mariem,

If each version is having more changes , and even if update with latest version ,will that work without error.

Because we found errors in running process with more changes running with latest version.

Changes - adding new measure , adding new output and input parameter, adding new field

thoshino

unread,
Nov 14, 2014, 1:32:14 PM11/14/14
to suppor...@runmyprocess.com, bestfri...@gmail.com
Hi Nagasai,

How are you doing?

When you have application running in several versions already, it is likely that your version chain has been broken.
Chain I am referring to is, every time you push a new version to LIVE and choose "force pending tasks to new version", it will add a new entry to the chain.
Like, 
pending tasks in V0 should run in V1 when updated
pending tasks in V1 should run in V2 when updated
pending tasks in V2 should run in V3 when updated

and when you update a process waiting in V0, it will jump to V3.

Chain broken means, somewhere in the version deployment you didn't choose "force new version" so V0 will not move to V3, maybe stuck in V2.

If case some process instances are running in old version, you can still manually go into its process report and edit the execution path, and save+replay in "selected" version.


So, the answer to your question is:
1. Create a new version.
2. Push it to LIVE with "force new version" option.
3. For instances that were not forced to new version (broken chain), you need to manually restart them in new version.

Of course all the best practices around version deployment apply here.

If you do not follow this correctly, there will be tons of process instances that abort with error and supervisor/admin has to fix all of them manually.
Please be very careful.

Once you have all instances running in single version, next time you release a upgrade version of application, you do not have to do #3 because chain will be effective.

Best regards,

Taka
Reply all
Reply to author
Forward
0 new messages