The RequestFlow service allows users to emulate the behavior of a request page in Exact Synergy Enterprise. The RequestFlow service encapsulates the whole Workflow engine of Exact Synergy Enterprise. It allows users to perform multiple request actions, such as create, approve, realize, process, and reject. It is also tied to the standard request business component in Exact Synergy Enterprise. Thus, the standard request validation is also implemented into the RequestFlow service.
The information in this document is based on product update 253.
From the data contract, these are the few main “Complex type” definitions that will be used:
o Actions — List of request actions that user can execute for a certain request.
o Request header
§ Information on the request’s definition.
§ ID of the request.
§ Request type and request type description.
§ Current status of the request.
§ Number of attachments in this request.
o Flow — The request flow information, such as:
§ the number of stages of the request,
§ current actor,
§ current request stage,
§ next actor, and
§ date of approval.
§ The fields of a request.
§ Contains information whether the field is mandatory, editable, or a browser.
§ Value of each request field.
o BaseName — The field name that will be used in the query for filtering.
o DataType — The data type of the column.
o IsQuickSearch — To determine if the column is a quick search column (that uses Enterprise Search logic in Exact Synergy Enterprise, for example Document and Request browsers).
o IsSearchable — To determine if the column allows filtering with filter criteria (when IsQuickSearch is true, there will only be 1 column having IsSearchable is true).
o IsVisible — To determine if the column is allowed to be visible in the browser.
o Name — The name of the column.
o SelectionValues — The selection values if the column supports selection values (drop-down box).
o “LeadingFields” property — This property indicates if the field has dependency on another request field.
o “DisplayValue” and “DisplayDescription” properties — These two properties are used to construct the “description” of a browser field.
o Here, the “DisplayValue” will describe the value displayed in the Account browser field. In the example above, the account code “2000000071” will be the value of the DisplayValue property.
o The “DisplayDescription” is used to describe the browser field.
The RequestFlow service has the following functions:
A) Open New
B) Retrieve All
o Clear remark
o Done remark
o Mark as read
o Mark as unread
o Print SMS report
o Create word merge letter
o Create word merge email
o Request type number.
o Property name (name of the browse field).
o Batch size (to determine the paging size of the returned results).
o Session ID (used for paging purpose).
o Leading fields values (to inform the server whether the browser field has dependency on another field).
o SearchColumns (to provide the filter criteria to the browser to filter on the browse result).
The main purpose of the RequestFlow service is to replicate or emulate the Workflow module and features in Exact Synergy Enterprise. In order to do that, it is important to reuse existing codes and functions that have been implemented such as Exact Connectivity Layer, Exact Workflow engine, and Request business component validations.
The diagram below describes how the RequestFlow service is implemented:
As of product update 252, most of the major features and core functions of the Workflow have been covered. However, certain features of the module and enhancements on the Workflow are still incomplete. The request features for the following modules or solutions are not covered yet for the RequestFlow service as more refactoring work are needed.
At this moment, the following features are not covered: