[rules-users] Question about backing up a flow

[Nair, Mahesh]

Thanks Kris for your suggestion.

What we are trying to model is similar to an interview process (for diganosing some kind of trouble with a system). The user wants to be able to go back to any of the previously answered question and change the answer and the restart the interview process from that point (after which the flow would take a different route from the earlier route). if we have a loop back it would mean that all nodes are connected to all other nodes !. Events would definetley work but we are looking at some other approach which coul dbe mor elegant

Mahesh 

-----Original Message-----
From: Kris Verlaenen [mailto:kris.verlaenen at cs.kuleuven.be] 
Sent: Monday, October 19, 2009 7:49 PM
To: Rules Users List; Nair, Mahesh
Cc: rules-users at lists.jboss.org
Subject: Re: [rules-users] Question about backing up a flow

Quoting "Nair, Mahesh" <Mahesh.Nair at qwest.com>:

> [...]
> I expected the session to restart the process from node A once it was 
> recreated. Am I going in the right direction?
The process will be in the same state as it ended in the last time.

In general, I would not advice to use database transactions like this to roll back changes in your process (because you don't necessarily even know the boundaries of that transaction, so you could have strange side-effects).

Couldn't you model the same logic using for example a loop (draw a connection back to a previous location in the process), exception handlers, event signaling, or a combination of all of these?  It would make it much more visible for the user what's going on.

Kris

Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm