Cons of leaving a workflow open

  • 29 January 2015
  • 4 replies
  • 0 views

Badge +2

What are the cons of leaving multiple workflows open?  Where can I find more information?


4 replies

Badge +10

Hi

 

Could you provide some more information about your question and your specific concerns?  Are you asking about having a lot of active workflows running on the K2 server waiting for people to complete their tasks?

Badge +2

Yes, that is exactly what I mean.

Badge +10

 Its very common to have hundreds if not thousands of active instances running on the K2 server awaiting user response.  The K2 server automatically takes processes out of memory when awaiting a user response so its very scalable that way.  When a user accesses their worklist or the form, on the backend the K2 server then loads the process back into memory and executes from that point.  Most of the time you'll find that the K2 workflow server is idle awaiting user respones.

 

With that said its not recommended to design processes that will be active for years at a time, not that it will not work but more that the actual business process will almost certainly change over time.  In cases like that you'll want to break your business process into multiple sub workflows that can be updated more frequently to keep up with the changing business requirements.

 

Here is a best practices document that will provide some guidance on this and other topics:

http://help.k2.com/kb000352

 

Hope this helps.

 

Regards,

Tim

 

Badge +2

Thanks @timkn!  This was a fantastic response!  Very clear, quick and informative!  Take care!

Reply