Request state value is not changing when using with task creation in workflow

karola1
Kilo Contributor

‎10-09-2017 07:15 AM

Hi all,

I am having problems with request state not changing value in workflow.

  1. I am having a workflow that is triggered when our business request is created (it is extending Request table).
  2. In next step I am using Set Values activity to set request_state=Approved and state=in_process
  3. Then I am creating a business task (it is extending Task table).
  4. Then I am using Set values activity again, but now setting the request_state=Closed complete and state=Closed complete

The problem is that when workflow is not waiting for creation of task (Wait for completion checkbox   is unchecked) the value of request_state is still Approved and not Closed complete.(The same happens when I delete the creation of task completely).

When workflow is waiting for the creation of task the request_state is set to Closed complete.

For me creation of task should not have any connection to request state.

Thanks for responding,

Karolina

Labels:
0 Helpfuls
  • 1,169 Views
7 REPLIES 7

Chuck Tomasi
Tera Patron
In response to karola1

‎10-09-2017 08:13 AM

What would you like the workflow to wait on? If you simply have some Set Value activities, it will execute one right after the other. It sounds like you want it to wait for something, but not create   task. Is that correct?


0 Helpfuls

karola1
Kilo Contributor
In response to Chuck Tomasi

‎10-10-2017 01:15 AM

This is how my workflow looks like:


find_real_file.png


And I want to get rid of Create Task activity. Bu when I do that the Request State is set to Work in Progress as a result of the workflow and I want it to be Closed Complete. So it looks like the second Set Values activity did not set the value of the Request State properly.


Preview file
19 KB
0 Helpfuls

Chuck Tomasi
Tera Patron
In response to karola1

‎10-10-2017 03:06 PM

Hi Karolina,



It might be a race condition. Since the workflow is proceeding "in the background", it might not be done with the first record update when the second comes along. If you take out the Create Task, the workflow basically says "Set these values, then sent those values". Is it supposed to wait for something before doing the second set? It doesn't seem like much of a workflow if all it is doing is setting the state, and then changing it again immediately.


0 Helpfuls