Asynchronous workflow

One of our client has called for a requirements stating that, they would need a Asynchronous workflow as currently their Teamsite workflow interfaces to an external vendor for translation and till all the tasks in the workflow are completed, the workflows are in the memory and eventually kills the performance. Over a period of time the workflows are un-attended and remains in the memory. When ever the performance of the Teamsite goes low, the CMS admin has a job of identifying the workflows that are long pending and kill them.

Is there a way that I can implement Asynchronous workflow in Teamsite, where the once the task has been taken over by some person, it need not wait in memory till its completed?

Kindly, Pour in your thoughts

Find more posts tagged with

Comments

kaalraa

One of our client has called for a requirements stating that, they would need a Asynchronous workflow as currently their Teamsite workflow interfaces to an external vendor for translation and till all the tasks in the workflow are completed, the workflows are in the memory and eventually kills the performance. Over a period of time the workflows are un-attended and remains in the memory. When ever the performance of the Teamsite goes low, the CMS admin has a job of identifying the workflows that are long pending and kill them.

Is there a way that I can implement Asynchronous workflow in Teamsite, where the once the task has been taken over by some person, it need not wait in memory till its completed?

Kindly, Pour in your thoughts

As a concept of acheiving the requirement, you can have a separate child workflow for your external vendor in the form of wft file.

Form the parent workflow, initiate the wft using an external task instead of wftask element. If you need more on that and if possible by you, please provide your workflow diagram.

HTH

Adam Stoller

One of our client has called for a requirements stating that, they would need a Asynchronous workflow as currently their Teamsite workflow interfaces to an external vendor for translation and till all the tasks in the workflow are completed, the workflows are in the memory and eventually kills the performance. Over a period of time the workflows are un-attended and remains in the memory. When ever the performance of the Teamsite goes low, the CMS admin has a job of identifying the workflows that are long pending and kill them.

Is there a way that I can implement Asynchronous workflow in Teamsite, where the once the task has been taken over by some person, it need not wait in memory till its completed?

Kindly, Pour in your thoughts

Are you saying that you want the workflow to continue - perhaps complete and end - instead of waiting for translated content to come back from your translation vendor?

If so - then whatever process you use to send the content to your translation vendor - presumably an externaltask - could transition on its own instead of waiting for a response.

Is this a good idea? Not in my opinion.

I think a better solution would be the one that Nipper has been advocating for quite some time now (and which I agree with) which is to make sure all your tasks have timeout values on them - which (at the very least) sends email notification to the job and/or task owner letting them know that they are tardy, and then transitions - either back to the tardy task, or forward to the next task.

If your system is getting bogged down because of hundreds / thousands of jobs hanging around never being completed - then the timeout concept is a good one - and if you really do want to kill the tardy jobs - it will make it much easier to know which ones are tardy. You can have the timeout handler transition to an Admin usertask where the Admin has the option to either End or Retry / Continue.

Migrateduser

Thanks every one, the time out handler with escalation to admin is a good idea, i will talk to my clients about this and repost if required