Change Request - Invalid Update

hamed4
Kilo Contributor

‎06-19-2018 08:41 AM

Hello,

I am facing a difficulty concerning the Change Request Workflow in which I am unable to find the root cause of such error.

I have updated the Normal RFC workflow by adding another workflow inside this latter after the "Change moves to Assess" activity. This workflow automatically creates a task upon certain met conditions.

Creating a new Normal RFC meeting the included workflow seems to work flawlessly, but when the "else" conditions is executed, we get an "Invalid Update" error on RFC form which happens when "Requesting an Approval" (in other words moving from New state to Assess). This is probably due to the "State model - Can change state?" Business Rule that checks if the RFC is able to "MoveFrom" a previous state to another.

The question:

Has anyone had a similar use case / issue?

Or is anyone able help me to troubleshoot the issue and eventually to come up a with an appropriate solution?

Update:

I have just removed the included workflow and added its contents directly to the parent workflow (Normal RFC WF) and it seems to be working properly without the error that I have mentioned.

Is anyone able to explain what is going on and what is the difference between the first and the second method? Or what am I possibility doing wrong?

Thank you for your time and effort. It is very much appreciated.

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

Michael Fry1
Kilo Patron

‎06-19-2018 05:57 PM

Can you provide screen shots of your workflow and the IF statements that's causing the issue. Not sure I can help, but maybe someone will spot an issue.

0 Helpfuls

hamed4
Kilo Contributor

‎06-20-2018 12:46 AM

Sure.

 

As you may see, I have marked 2 spots.

  1. Is the part where I get the Invalid update error when using the exact same activities in an included workflow
  2. This one follows the same principle as (1) but with one more additional task.

 

As it appears there is nothing wrong the workflow (or the sub workflow) but rather at the Assess state (when submitting a Request Approval).

 

find_real_file.png

Preview file
104 KB
0 Helpfuls

Michael Fry1
Kilo Patron
In response to hamed4

‎06-20-2018 05:24 AM

1 - So we do something similar but my IF is after the Approval Action. Can you move yours to be after the Approval Action?

2 - so what's the thinking here? The changes move to Scheduled and tasks are created? Do they have to complete the tasks before moving to Implement?

 

0 Helpfuls

hamed4
Kilo Contributor
In response to Michael Fry1

‎06-20-2018 05:33 AM

  1. No problem on changing the order. The importance is to create a mandatory task at the Assess state.
  2. Yes, just like (1), when the change moves to Scheduled state, 2 mandatory task are created and must be completed before moving to Implement.
0 Helpfuls