Nintex Connect

Problem: I've got to project which link with deliverables and dependencies. At first project i created  deliverable, at second project - dependency to deliverable. How to create disabling workflow for publishing, if changing of finish deliverable at first project bring changing of finishing dependency at second project.

 Workflow must be the next:

1. Project Manager update schedule in Project Pro

2. Deliverable Finish has changed.

3. Project Manager try to published Project to Project Server, but he can't because system open information window about changing in Deliverable Finish

4.  Project Managers start wokflow to Project Management Office or another about permission to publishing Project

5. If responsible agree with changing in  schedule, he say "Yes" to workflow.

6. Project Managers received "Yes", system unblocked published options.

Your opinion about this scenario?

Strange. So any idea from developers?

How to develop workflow for deliverables?

Hi,

Apologies for the delay in responding.

The short answer, to meet your original requirements is no, whilst Nintex provides actions to read the PSI (Query Project Server) and indirectly to update (Call Web Service), I don't think you can accomplish your scenario using workflow. I am not even sure you can accomplish that scenario at all.

You basically wish to dynamically change access to the publish command via workflow. Turning off publish for that user across all projects is not going to be an option. So you will need to change the security of an individual against an individual project. In order to achieve this you would need to dynamically set up categories covering that project and then deny the publish permission which is going to be very hard to accomplish and maintain in any technology you choose.

I would also be concerned with whether the Project client would respond to changes in security on the fly. I am pretty sure if you change permissions you would need the eGlobal to come down again to pick up the button changes. You would have to write something at the client level in either VSTO or VBA to restrict the client.

Of course, just to clarify the final point, you can still bind a workflow to the deliverables list using our out of the box capabilities and use the various actions on the list, its just your specific scenario around restricting publishing that is problematic.

Alex.