I have an orchestrator process project, to test out long running workflows. I’ve published to orchestrator and I’ve successfully sent the form task to the task queue, open the task form, assign it to myself, and see the form as i’ve designed it. When it’s sent to the task queue, it’s state is displayed as suspended, which is fine. However, when i go into the task and complete the task object, it moves to a user of “Pending Allocation” and a state of “…Resumed”.
I can’t figure out how to allocate a user to it. I’ve launched the process as an attended bot, i haven’t tried using the unattended yet. I would think if i wasn’t to be launching via attended bot, it wouldn’t let me serve it up on my desktop. In short, how do i trigger the bot to start up after the wait for form task has completed?
When i ran this code in debug in studio, i ran it up to the Wait for Form Task & Review activity, I completed the task, then had to hit the Resume button on my studio instance for it to synch up with the task status to move forward.
For the record, this task/form combo is awesome. When i saw the code snippets for tasks (using asynch for each activities), it furthered my excitement. This is really good stuff. Thanks!