Priority ERP

Engini’s Priority ERP activities allow you to create and modify records, activate form activations, and make API calls from your Priority ERP using Priority’s Webhooks module.

Getting Started with Priority ERP #

Prerequisites #

• Priority API License.
• Open access to Priority via port 443. If you can’t open this access, you can also just whitelist our IP. send us an email to support@engini.io.
• Enabled API access to FORMLIMITED form.
• Optional – Dictionary Module: To enable language-specific operations for both CRUD operations (Create, Read, Update, Delete) and procedures, ensure that the dictionary module is activated in your Priority ERP system. By default, the API will operate according to the system language unless specified otherwise.

Connecting Engini to Priority ERP #

1. Enter your Engini account at https://app.engini.io.
2. Navigate to Connections page by clicking on the Connections on the left sidebar or by clicking here.
3. Click on the Add connection option located at the topbar.

4. Choose Priority’s option from the available applications.

1. Enter the following details in the “Edit Connection” form:
   1. Connection name
   2. API Url including the tabula.ini. for example https://erp.engini.io/odata/Priority/tabula.ini.
      • To specify the language for API operations, append a comma and the language code to the end of the URL.
        For example, for American English, use “https://erp.engini.io/odata/Priority/tabula.ini,3“.
   3. Database name (company id in companies form)
   4. API Username (Companies that use Priority identity management module should place their personal access token)
   5. API Password (Companies that use Priority identity management module should place “PAT” in all caps)
   6. X-App-Id & X-App-Key (Optional. used when using a dedicated priority connector)
   7. WebSDK Username & WebSDK Password (Optional. used when using a Priority’s form activations, for example, for printing a Price quotation document)
   8. Communication Channel
      Choose the appropriate connection type based on your setup:
      • Cloud- If you are connecting to a database hosted in a cloud environment, select “Cloud”.
      • OPA- If your database is on-premises and you are using an On-Premises Agent (OPA) for the connection, select “OPA”.
        In this case, an additional field will appear:
        On-Prem Agent- Choose the specific On-Premises Agent that you want to use for this connection if you have multiple agents configured.
        
2. Click on the Save button located at the bottom of the form.
3. Engini will now try to reach your Priority and read the forms marked for access by API in the FORMLIMITED form. Each opened form will get it’s unique action type Activities for Creating, Updating, Reading records and trigger type Activity to use in Priority webhooks for triggering Workflows in Engini.

Main Form Records #

Engini’s main form activities let you interact with main form entity records such as Customers, Sales Orders, Purchase Orders etc and do the following:

• Create a record
• Update a record
• Get a record
• Get records
• Get notified when a record is created / modified (depending on the business rule defined in Priority)

To describe how to use Engini’s Priority main form activities we’ll use the Priority’s Sales Orders form.

Sales Order updated #

Triggers when a “Send webhook” business rule defined in the Sales Orders form / Sales Orders BPM is activated.

1. Choose Priority’s “Sales Order Updated” trigger.
2. Copy the provided url and create a new webhook in Priority “Webhook Definitions” form in the following path – System Management > System Maintenance > Periodic Maintenance > BPM Maintenance > Webhook Definitions and paste the url in the “URL” field.
   Priority Developer Portal (prioritysoftware.github.io)
3. Add a new rule to send a webhook using the Sales Order BPM (defined only on statuses) / Business Rules (can be defined on any field in the Sales Orders form).
4. Name the business rule (only English characters are supported).
5. Add the form fields that will be sent in the webhook body when triggered in the business rule body.
6. Define the conditions in which the business rule will send the webhook.
7. Define the user / users group and company/ies in which the business rule will send the webhook.
8. Save the business rule.
9. Back in Engini, add you can setup conditions that only when the conditions are met the Workflow will continue passed the trigger activity.
10. Save the workflow.

You have successfully setup a Priority trigger in Engini.

Create Sales Order #

Creates a new Sales Order.

1. Choose Priority’s “Create Sales Order” activity.
2. Click on the “Add field” button.
   
3. Choose the form field you want to populate from the fields list.
4. You can populate the field in one of the following options:
   • Static value – number / string. when using strings you need to surround them with single quotes (‘).
   • Property value from a previous activity (Using the tooltip that opens when clicking on the field).
   • Expression – using functions and/or Previous activity properties and/or static values (Using the tooltip that opens when clicking on the field).
5. Repeat steps 1-3 for all the fields you want to populate.

Update Sales Order #

Updates an existing Sales Order.

1. Choose Priority’s “Update Sales Order” activity.
2. Enter the Sales Order number of the record you want to update.
3. Click on the “Add field” button.
4. Choose the form field you want to populate from the fields list.
5. You can populate the field in one of the following options:
   • Static value – number / string. when using strings you need to surround them with single quotes (‘).
   • Property value from a previous activity (Using the tooltip that opens when clicking on the field).
   • Expression – using functions and/or Previous activity properties and/or static values (Using the tooltip that opens when clicking on the field).
6. Repeat steps 2-4 for all the fields you want to populate.

Get Sales Order #

Retrieves a specified Sales Order.

1. Choose Priority’s “Get Item Sales Order” activity.
2. Enter the Sales Order number of the record you want to get.

Get Sales Orders #

Retrieves a list of Sales Orders.

1. Choose Priority’s “Get Items Sales Order” activity.
2. Output fields
   You can select specific fields from a column dropdown menu to retrieve only relevant information instead of getting all fields by default.
3. Add Sorting
   You can sort the retrieved list by multiple Sales Order fields either Ascending or Descending.
4. Add Filter
   You can add filters to query the Sales Orders and retrieve only the records that met the conditions.
5. Top N
   You can set the maximum number of Sales Order records Engini will return during one workflow cycle (default = all records).
   • If you set Top N = 1, a single record will be returned instead of an array. If no record is found, the action will fail, allowing you to implement an IF condition within the workflow. This can be useful for processes where the existence of a record determines the next steps in the workflow.
6. Offset
   The offset parameter allows you to skip a certain number of records from the beginning of the result set (default = 0 records).

Uploading Files to Priority (Version 21 and Above) #

To upload files in Priority, follow these steps starting from version 21:

Download File from URL Activity

#

1. Add the “Download File from URL” activity.
2. In the URL field, specify the URL from which the desired file is to be downloaded.
3. You can populate the field in one of the following options:
   • String Static value – when using strings you need to surround them with single quotes (‘).
   • Property value from a previous activity (Using the tooltip that opens when clicking on the field).
   • Expression – using functions and/or Previous activity properties and/or static values (Using the tooltip that opens when clicking on the field).

Create Attachments Activity

#

1. For example, for the specific screen where you wish to upload files, add the “Create Attachments” activity.
   • You can attach files to any screen in Priority that allows you to upload files.
2. Click the “Add field” button. Priority requires the following details to populate:
   • File Path: The structure by Priority should follow this pattern-
     “data:();base64,()”. To execute this process, use the following functions:
     • Concat- This function enables the merging of various elements into a single string, crucial for constructing the file path structure required by Priority.
       • For your convenience, you can copy the contents of the Concat function. Don’t forget to include the BASE 64 as a property and the “GetMimeType” function:
         Concat(‘data:’,GetMimeType(Populate here the file extension),‘;base64,’,Base64 String)
     • GetMimeType- This function is utilized to fetch the MIME type associated with a specific file extension, a vital component within the file path construction process.
       For example:
       
   • File Name: The file name should include the extension of the specific file. You can populate the field in one of the following options:
     • Static value – number / string. When using strings you need to surround them with single quotes (‘).
     • Property value from a previous activity (Using the tooltip that opens when clicking on the field).
     • Expression – using functions and/or Previous activity properties and/or static values (Using the tooltip that opens when clicking on the field).

Form Activations #

To use Priority’s form activations, follow these steps:

WebSDK details #

1. Navigate to Connections page by clicking on the Connections on the left sidebar or by clicking here.
2. Press on the 3 dots on the right side of the Priority connection and click on the “Edit” option.
   
3. Enter the WebSDK username and password and press Save.
   • If your Priority On the public cloud (AWS), you have to enter the WebSDK URL as well.
     1. For production environments, the url is:
        https://p.priority-connect.online/wcf/service.svc
     2. For test environments, the prefix is an s, instead:
        https://s.priority-connect.online/wcf/service.svc

Form Activation Activity #

1. Add the “Form Activation” activity of Priority.
2. Choose the Form name from the drop down menu. The available forms are the open parent screens and child screens from your Priority account.
   
3. Choose the Activation from the drop down menu.
4. According to the Form name, an identifier field will appear. Enter a static value as you can see at the image below:
   
5. Press Run. Each Run can add new fields to fill in.
6. Repeat steps 4-5 until all required fields are filled up and “Ran successfully” message will appear.
   
7. Now you can replace the static value (step 4) with dynamic value from previous activities.

Run Procedure Activity #

Prerequisites:

1. EPROG form is accessible to API in FORMLIMITED form.
2. The user used for the integration should have at least read privileges to EPROG form.
3. The user used for the integration should have privileges to execute the relevant procedure.

To use Priority’s run procedure, follow the following steps:

1. Add the “Run Procedure” activity of Priority.
2. Choose the procedure name from the field options tab in the tooltip menu. All the available procedures.



3. Fill in the required fields with static values first to setup the activity.

   

4. Press Run. Each Run can add new fields to fill in. When you need to reset the values you can press the “Reset” button.
5. Repeat steps 3-4 until all required fields are filled up and “Ran successfully” message will appear.
   
6. After the procedure ran successfully, you can now change the relevant static values to parameters to allow the workflow to run using dynamic values.