Hi @cferrer,

I had a look at the functionality and it doesn’t seem to exhibit the behaviour you described. I have two actions created, and despite their target action completion date being set to various dates, I can complete either of the actions if they are assigned to me. See the below screenshot:

By default (when loading the page) the second item does appear collapsed, but this can be expanded and actioned using the + sign:

Hope this helps Please let me know if you have the same experience, or whether it shows up differently for you.

Kind Regards,

Mark.

Hi Mark,

Thanks for the prompt reply.

Probably I did not explain myself clearly, apologies.

What I meant is that if we have, say 10 actions in a plan, AND those are supposed to be completed by 10 different stakeholders AND the completion should occur sequentially (very common in an IT change request) e.g. 1) Define Scope; 2) Collect data; 3) Implement software changes; 4) test software changes; 5) confirm changes are working properly, etc, etc, we would expect the list of actions to be shown in the action plan in a sequential manner (from top to bottom).

This is, the first action at the top of the action plan would be (1) (as per above example), then (2), (3), etc.

Now, say that when creating the actions, we did not create them in that order but (1), (3), (2), (4), (5), this is the way it will be shown in the action plan, even if they have different target dates for completion. Furthermore, if we want to drag action (2) and place it under (1) -to fix the order of execution-, this is not possible.

The example above was a simple one, but we could have more complex changes where the order to follow for completion is not that obvious.

Therefore, unless the action plan is created in the exact order in which we want it to be executed, it is not currently possible (or is it?) to add new actions AND insert them in the order of occurrence where they should be i.e. for instance, when they have been missed from the initial plan or when we decide that say an action (8) -of an already approved action plan- should be completed before action (7).

This is causing some noise within my team because more often than not, they don’t know who should be next in completing an allocated action, i.e. when the action plan has not been created in the order of execution.

Hope this makes more sense now?

Please advise,

Thanks,

Carlos

Hello @cferrer 

That shouldn’t happen. Actions should be able to be completed regardless of the order they were created. Also I don’t believe there is any setting that affects that behaviour e.g. to force sequential order resolution for actions.

I would suggest you raising this with support@nintex.com as it might be something wrong in your tenant that needs to be fixed/requires more investigation.

Ok. Let’s try something different :)

I have attached a pic of what I want to do.

Yes, we can complete the actions regardless of the order. That is not the issue.

However, if I want to show the actions list in a particular order (after the plan has been created - as in the example in the pic), it doesn’t seem to be possible to rearrange them i.e. like drag them up/down.

Why do we need this? Because in a more complex change, we need all participants in the change request to know who should be completing an action first, second, etc. Otherwise, it can be confusing unless the action plan is created -from the onset- in the exact order we want it to be executed. However, this is not always the case.

Please, let me know if it is clearer now. Otherwise, I am happy to provide another way to explain the issue .

Thanks,

Carlos

...to reinforce the example in the pic, please note that the first 2 actions: “Purchase the new cake processor” and “Test the new cake processor” should be listed as 5 & 6 respectively, this is, if we want to show them in a logical order of execution. My query is, do we have a way to rearrange this order, so it is shown sequentially?

Thanks,

Carlos

I see now. Unfortunately, there is no way to perform a reorder right now. 

Only workaround I can see is add a number at the beginning of the action. It’s not ideal and relies on the discipline of the action owners for it to be executed in order.

Next best thing, I can suggest is raising this in Nintex Ideas. Maybe something along the lines of:

• Ability to re-order action order
• Ability to enforce sequential resolution of actions

Hi @EvgeniosE,

Thanks for your reply. will do.

Kind regards,

Carlos