Zervicepoint Components

Core components add value to the overall functionality

Central server role

The central server role contains webs for the end-user portal, service designer and administrative configuration. It also contains a workflow engine, service bus queues and a database.

The provisioning server has windows services for finding and executing registered PowerShell activities and a web site with web services that are connected to PowerShell data sources.

Zervicepoint User web
Admin Web

Workflow Manager

Microsoft Workflow Foundation, all workflows that are designed in ZervicePoint Admin Web are compiled to Microsoft Workflow Foundation.
Microsoft Service Bus, Message Queue used by the Workflow Engine.


Microsoft SQL Server, stores information used by ZervicePoint. Data is logically separated between stores.

Provisioning server

Provisioning service

ZervicePoint Provisioning System, a Windows Service that executes PowerShell modules when they are a part of a Workflow. The response is delivered back to the Workflow and can be used as input to the next steps in the Workflow.

Client Web Service

ZervicePoint Client Web Service (CWS), a Web Service that responds to Ajax queries from the devices. CWS Executes different PowerShell Modules and delivers the response from the target systems to the request or approval forms (on the device).


Integrate and the automation magic kicks off!

When it is not enough to build static forms and manual workflows, you can integrate with other systems to get dynamic data and automate processes.

There are two field types you can use to display data from a PowerShell data source: drop-downs and multi-checkboxes. You can also use JavaScript that triggers a specific event, such as when a form is loaded or a field is changed, to add more control.

Another way to integrate external systems, is to use a text block field and use custom HTML code to frame an external web site on the service details page. You can for instance embed video clips, online reports or a complete web app.


Structured and built to always mind security

We don’t store any passwords in Zervicepoint. Instead we use Microsoft ADFS as federation service, for authentication and for getting claims you can use for authorization.

We don’t replicate data from external systems to the central server. The web browser gets the data via a local data source instead, and only stores selected values for the service order centrally.
We encrypt all communication with the central server role and the local provisioning servers. Data retrieved from the data sources is digitally signed to prevent modifications.