Synergize Process Server Basics

Synergize Process Server (SPS) is a fully configurable business process environment that works in conjunction with other parts of the complete Synergize solution including repositories, workflows, and documents.

 

 

Process Designer

Processes are designed and configured in a graphical environment called the Synergize Process Designer.

Once created, the processes run on the Process Server itself.

The processes are actually XML files with a file type of .sjd.

This stands for Synergize Job Description.

When the Process Designer saves a file, it will report "Job was saved successfully", which means that the XML file was written to disk.

The default save location is:

C:\Program Files\Microdea\Synergize Process Server\Processes

 

 

Changing the Default Save Location

We recommend that you edit the Microdea.ProcessServer.Service.exe.config file (in the Synergize Process Server\bin directory) to change the default save location for processes.

That way, you can reinstall Process Server and your processes remain intact.

Edit the line as follows:

Original:
<add key="ProcessPath" value="C:\Program Files\Microdea\Synergize Process Server\Processes" />

Recommended:
<add key="ProcessPath" value="C:\Users\<username>\SPS Processes" />

 

 

Actions

Actions are the building blocks of any process.

In the Process Designer, a toolbox (or palette) contains a wide range of actions.

Additional actions can be created for even more customization.

Actions are connected together to form a flow.

Actions can derive useful information from each other through a technique known as "binding".

By binding a property of one action to the property of another action, dynamic data processing can be done.

Actions can not only represent discrete steps in a process but can act as logical containers, representing loops and branches in the flow.

In this way, actions can be nested within other actions.

In fact, nesting is often necessary to design a valid process.

 

 

Data Types

Although many properties of actions are bindable, specific types of data are required by some downstream actions.

For example: an action may extract a specific string from a document.

Although that string may be a valid date, a subsequent action would still need to convert the string to an actual date for use by actions expecting the date data type.

In another example: The TextFormatter action is useful as an intermediary between actions that output, for instance, only integers and ones that need a valid string.

 

 

Data Scope

Because a property's value is sometimes no longer "in scope" when an action has completed, nesting is necessary for some actions.

This is true for actions that connect to another source, like a database.

For example, a connection to the Synergize Repository must be active for queries to be made on that repository.

Therefore, the Synergize Connection action contains all the actions that rely on the search for — and the return of — documents from the connected repository.