Sage 200 Evolution
Sage 200 Evolution is an ERP platform used to manage inventory, purchasing, sales, and related finance processes through the Evolution SDK and its SQL-backed company databases.
The Flowgear Sage 200 Evolution Node lets you create, update, complete, and process the supported Sage document types in a Workflow by using a direct database Connection and template-selected request payloads.
Revision History
0.0.0.1 - Initial release.
0.0.0.13 - Repair project file SDK version reference.
0.0.0.17 - Fixed template returns and runtime error handling.
0.0.0.20 - Split invoke methods.
0.0.0.23 - Overhaul to new standard.
0.1.0.0 - Completed the V2 overhaul with eager first-document startup and lazy input continuation.
0.1.0.25 - Added Run Anywhere Cluster support.
0.1.0.31 - Added multi-version Sage Evolution SDK support.
0.1.1.1 - Published the current V2 overhaul release.
0.1.1.5 - Added version-matched SDK support through Sage Evolution 12 and standardized mutation responses.
0.1.1.6 - Fixed Sage DLLs.
0.1.1.9 - Improved request parsing, SDK type matching, error handling, and response messages.
Connection
Use the Connection to configure the Sage company and common SQL Server databases.
| Property | Type | Description |
|---|---|---|
Server |
String | The SQL Server instance that hosts the Evolution company database. |
Database |
String | The Evolution company database name. |
Username |
String | The SQL username for the company database when UseWinAuth is false. |
Password |
Masked | The SQL password for Username. |
UseWinAuth |
Boolean | Set to true to use Windows authentication for the company database. |
CommonDbServer |
String | The SQL Server instance that hosts the common database. This is typically the same server as the company database. |
CommonDbDatabase |
String | The Evolution common database name. This is typically EvolutionCommon. |
CommonDbUsername |
String | The SQL username for the common database when CommonDbUseWinAuth is false. |
CommonDbPassword |
Masked | The SQL password for CommonDbUsername. |
CommonDbUseWinAuth |
Boolean | Set to true to use Windows authentication for the common database. |
Branch Id |
Integer | Optional. Use this to target a specific Sage branch. |
Setup Notes
- Ensure the selected Flowgear Cluster can reach the Sage 200 Evolution SQL Server.
- If the SQL Server is behind a firewall, allow the Flowgear tenant or selected Cluster IP address.
- Configure both the company database and common database settings. When Windows authentication is disabled, the matching username and password Properties are required.
- The Node reads the Sage application version from the company database and selects the matching embedded SDK. Sage Evolution 7, 8, and 9 use the 9.20 SDK; version 10 uses the 10.1 SDK; version 11 uses the 11 SDK; and version 12 uses the 12 SDK.
Methods
The current public surface is mutation-oriented. Use the Node templates to populate DocumentType and the Request schema for the selected Sage document type.
Create
Creates a Sage document. This method supports InventoryItem, ApPurchaseOrders, ArSalesOrders, ApReturns, and ArCreditNotes.
| Parameter | Type | Description |
|---|---|---|
Connection |
Connection | The Sage 200 Evolution Connection profile. |
DocumentType |
Dropdown | The type of document to create. Select a document type supported by this method. |
Request |
Array | The document payload. Select a template to populate the schema. |
| Return | Type | Description |
|---|---|---|
Response |
Array | The processed document rows returned by the Sage SDK. Each row includes Flowgear.IsSuccess, Flowgear.Message, and the original input under Flowgear.Request. |
Update
Updates a Sage document. This method supports InventoryItem, ApPurchaseOrders, ArSalesOrders, ApReturns, and ArCreditNotes.
| Parameter | Type | Description |
|---|---|---|
Connection |
Connection | The Sage 200 Evolution Connection profile. |
DocumentType |
Dropdown | The type of document to update. Select a document type supported by this method. |
Request |
Array | The document payload. Select a template to populate the schema. |
| Return | Type | Description |
|---|---|---|
Response |
Array | The processed document rows returned by the Sage SDK. Each row includes Flowgear.IsSuccess, Flowgear.Message, and the original input under Flowgear.Request. |
Complete
Completes a purchase order. This method supports ApPurchaseOrders.
| Parameter | Type | Description |
|---|---|---|
Connection |
Connection | The Sage 200 Evolution Connection profile. |
DocumentType |
Dropdown | The document type to complete. Use ApPurchaseOrders. |
Request |
Array | The purchase order payload. Include DocumentID or OrderNo to identify the existing purchase order. |
| Return | Type | Description |
|---|---|---|
Response |
Array | The processed document rows returned by the Sage SDK. Each row includes Flowgear.IsSuccess, Flowgear.Message, and the original input under Flowgear.Request. |
Process
Processes a sales order. This method supports ArSalesOrders.
| Parameter | Type | Description |
|---|---|---|
Connection |
Connection | The Sage 200 Evolution Connection profile. |
DocumentType |
Dropdown | The document type to process. Use ArSalesOrders. |
Request |
Array | The sales order payload. Include DocumentID or OrderNo to identify the existing sales order. |
| Return | Type | Description |
|---|---|---|
Response |
Array | The processed document rows returned by the Sage SDK. Each row includes Flowgear.IsSuccess, Flowgear.Message, and the original input under Flowgear.Request. |
Usage Notes
Each Request item must contain one Sage document. The Node returns one response row per request item and includes Flowgear success or failure metadata for downstream processing.
The first Sage document is processed while the Node invoke is awaited. Later documents are consumed lazily as the Workflow reads the response stream, and an empty connected input performs no SDK work.
| DocumentType | Sage document | Supported methods |
|---|---|---|
InventoryItem |
Inventory item | Create, Update |
ApPurchaseOrders |
Purchase order | Create, Update, Complete |
ArSalesOrders |
Sales order | Create, Update, Process |
ApReturns |
Supplier return | Create, Update |
ArCreditNotes |
Credit note | Create, Update |
Known Issues
ProcessAllOrNoneis not applied. The Node processes documents one at a time.