Long lasting activities best practises?

  • 17 August 2009
  • 2 replies
  • 0 views
B
Badge +11

Hi


are there any best practises to handle long lasting activities? Some activities may range from 1 to 90 days. They will pile up in the worklist for no reason and will affect the performance . 10000 process are expected daily.


Making a process instance go to sleep mode was one of the suggestions; but the question was how to "Unsleep" these instances.


Other's suggested that k2 will dehydrate and hydrate processes; but this cannot be controlled by us, it is a feature in k2.


Do you have any suggestions?


 

2 replies

G
Badge +6

Hi there,

How does these long running steps work, are they active during that whole time? I.e. someone opens a task on day 2 and then keeps it open for 88 days until he finally finishes it and moves to the next step?

If so perhaps you could have an action that moves it to a "working" activity where the client event is assigned to a different "platform". By default all client events are assigned to the "ASP" platform, but in the "working" step you could assign it to a "work" platform? This would prevent these items being displayed in the default work list, and you could have a special work list that only retrieves these "work" platform items, since I'm sure that would be a manageble amount of items per user. 

B
Badge +11
regarding your question the activity may finish in 1 day or 90 days.

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings