Best Of

3-127 →152→146→9

at step 3 you have the attributes

at step 127 you have a WR(It can update any part of attributes,whether it is WF attributes or category attributes)

at 152 it can also change attributes(IH is a special step that can do a lot of manpiulation). Given so many OOB avenues to update OTCS objects, I fail to understand why the WF Execute step is used to call a REST api against the same OTCS or is the rest api going to a different syste,m then it would make sense.If you intended to update OTCS stuff, then no need to invoke restapi or is it updating some other workflow instance?

Your design is way too confusing, or your explanation is sorry I have no idea what do you mean it is dead ? if 152 executes its only path is 146 ? if you see your WF never reaches 146 that is probably because of a bad design…

I think you need to study briefly about how a workflow is constructed and remembered in OTCS

• You go to Map Painter and you add a Step internally, it is marked 1, if you delete it, I dont think the number is used again, this roughly becomes your taskid. An instance of a workflow, the one that you get when you start one, is represented in the database as a workid,subworkid pair . A task is identified as workid,subworkid, and taskid . So in a workflow instance, someone is actually on a task, so if you look at my screen graphic, my first step, identified as Initiator, is probably task 1 or 2. You can identify the active step as one with GREEN. These are candidates for the REST API or any valid user who is supposed to do the assignment.
• Assume my map now has two more steps after an evaluation, so step eval is 3. And one goes to a true and one goes to a false evaluated by an attribute, but it will only reach there if step 1 and 2 is completed. I hope you can visualize it or create a map and paint the logic. If OT allowed you to change the values of attributes at any forward step that is not ACTIVE=GREEN, then the business logic would not hold, which is why you get that error saying the STEP is NOT active, please wait your turn.

PS in that screencap of yours, the left Panel,Attributes is the master library of attributes as a WF manager, you are able to change it regardless of steps. I hope you can understand the difference. AFAIK OT may not have made a REST API implementation for WF managers because it can cause the workflow to stall or die miserably by people who cannot understand the business logic.

If you are still not convinced post a screencap of your map, and I expect to see TASK44 in green and it is assigned to either opntxt or Admin.As a quick test, go to TASK44 and assume it is Green,if you look carefully, you will see something like re-assign task, assign it to opntxt or Admin, and then run your REST query :) Some example screen caps to help

In that DC sends to the Engineer step, there is no assignee, so I have not tested if the REST api can move that step forward. I would most likely use the Re-assign and try to send the step with REST api.

None of those other step in the map can be done anything at this time because the map is constructed as one thing leads to another way.