Good project ideas often emerge spontaneously. Therefore, it is important to be able to capture them easily at any time. This is the reason why many organizations need to control projects not only during the execution phase, but throughout its entire project lifecycles: from starting as an idea, through planning and execution, all the way to project closeout. Microsoft Project Server / Project Online and the SharePoint environment it is part of (“Microsoft PPM”) provides configurable basic workflows and forms out of the box. These allow users to map a consistent project management process from idea to closure.
But companies often require more functions than the SharePoint Designer in the PPM environment can provide. K2 is the appropriate platform for them.
Why Use the TPG WorkflowConnector instead of SharePoint Designer?
Through low-code applications, K2 supports companies in transforming processes into efficient business applications using workflows and forms. 1.5 million users in over 84 countries are already working with this application. K2 is a great choice for organizations that need more than the built-in capability of SharePoint Designer to build Microsoft PPM Demand Management Workflows. However, K2 on its own does not offer integration with Microsoft Project Server or Project Online. This is where the TPG WorkflowConnector comes in.
TPG developed this connector primarily to implement workflows in idea management and to replace the SharePoint Designer workflows. This “bridge” makes it possible to create projects in Microsoft Project Server / Project Online directly from the K2 workflows. In addition, it allows users to create new tasks and update projects and resource data.
SharePoint Designer Demand Management | Demand Management Workflows and Forms |
|---|---|
Very basic form design capability | Form design by drag-and-drop |
Text-based workflow designer, suitable only for fairly simple workflows | Graphical, wizard-driven workflow designer, suitable for complex workflows |
DM workflow can only be sequential, one stage after the other | With the TPG WorkflowConnector, workflows can go directly to any desired stage |
No workflow debugging capability | Extensive workflow debugging |
Every field in the PDP form requires an Enterprise Project field | Designer can choose which workflow fields need mapping Enterprise Project fields |
Audit trail is limited and implemented as a SharePoint list | Extensive and secure audit trail |
Very limited workflow management | Extensive workflow management (redirect, repair, ViewFlow, workflow versions and more) |
Extensive custom coding needed for extensions | No or little custom coding needed for extensions |
Some complex end-to-end business cases with workflows already implemented by TPG using the TPG WorkflowConnector and Microsoft Project Server / Project Online are:
