Yes it is totally possible.
"jump to new": propagation="none"
"list of unfinished": conversationList
There is plenty of info about these features in the documentation.
Reading Chapter 6 of the documentation now. Thanks, Gavin.
How could I access the conversationList object in code? This would be useful for me so that if the user logs off, then I could persist the data related to the conversations and then retrieve later at next logon so the user could see what needs his attention. Of course, in that case I am not sure how to put these items in conversation scope again. Hmm.
Is there a better approach to this scenario then the one I just suggested?
Personally, I would consider this a data issue, not so much a framework issue.
Just put a "completed" field in your Order entity that is only set when the order is completed.
Then you can call "select * from orders o where completed = null" or whatever to see the incompleted orders.
Your approach is certainly viable and pretty simple, and it has occurred to me as a possible solution. Of course, I would argue a lot of the solutions provided by Seam could be accomplished through clever persistence mechanisms as well.
My question therefore was meant to address the possibility that Seam had something to address this requirement "out-of-the-box" so that I didn't have to. After all, from what I have read, the business process context manages the state of a business process across roles and logins, and something similar could be in play for the scenario I described.
If that isn't the case, then the solution you suggested is probably where I would go. However, I would still need to know how to access and manipulate the conversationList in code.