> ## Documentation Index
> Fetch the complete documentation index at: https://docs.engini.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Priority (legacy)
**Note:** This is a Legacy connector and does not receive ongoing maintenance or new updates. To switch to the latest Priority connector, [click here](/help/apps/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 (see below).
* 34.159.217.185
* 34.141.24.31
* 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](https://app.engini.io/).
2. Navigate to Connections page by clicking on the Connections on the left sidebar or by clicking [here](https://app.engini.io/connections).
3. Click on the "*New Integration"* option located at the topbar.
4. Choose Priority’s option from the available applications.
5. Enter the following details in the “Edit Connection” form:
1. *Connection name -* Choose a significant name.
2. *API Url* - Including the tabula.ini.
For example: [https://erp.engini.io/odata/Priority/tabula.ini](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](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. *WebSDK URL* - **Optional.** used when using a dedicated priority connector. X-App-Id & X-App-Key
7. *WebSDK Username -* **Optional.** used when using a Priority’s form activations, for example, for printing a Price quotation document.
8. *WebSDK Password* - **Optional.** used when using a Priority’s form activations, for example, for printing a Price quotation document.
9. *Time Zone - Choose the correct time zone of your location, or you enterprise location.*
10. *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.
11. *Advanced settings*
1. *Key -* Enter the username provided by your Priority service provider.
2. *Value -* Enter the corresponding password for the username above.
12. *Save Settings -* Click on the Save button located at the bottom of the form.
**Note:** 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.
## Triggers
### Sales Order updated
Triggers when a “Send webhook” business rule defined in the Sales Orders form / Sales Orders BPM is activated.
1. *URL -* The webhook endpoint where the updated record data will be sent. This is the destination that receives the event.
2. *Add Conditions -* Click Add Conditions to define conditions that narrow down the data list and return only the relevant items. To learn more about using filters, [click here](/help/workflows/workflow-editor#add-conditions).
## Actions
### Create Sales Order
Creates a new Sales Order.
* *Add Field* - Click Add Field to add and populate additional fields for the selected activity. To learn more about managing activity data, [click here](/help/workflows/workflow-editor#add-fields).
### Update Sales Order
Updates an existing Sales Order.
1. *Order -* Enter the Sales Order number of the record you want to update.
2. *Add Field* - Click Add Field to add and populate additional fields for the selected activity. To learn more about managing activity data, [click here](/help/workflows/workflow-editor#add-fields).
### Get Sales Order
Retrieves a specified Sales Order.
*Order -* Enter the Sales Order number of the record you want to get.
### Get Sales Orders
Retrieves a list of Sales Orders.
1. *Output fields -* You can select specific fields from a column dropdown menu to retrieve only relevant information instead of getting all fields by default.
2. *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.
3. *Offset -* The offset parameter allows you to skip a certain number of records from the beginning of the result set (default = 0 records).
4. *Add Filter -* Click Add Filter to define conditions that narrow down the data list and return only the relevant items. To learn more about using filters, [click here](/help/workflows/workflow-editor#add-filters).
5. *Add Sort -* Click Add Sort to organize the data list by a selected field in ascending or descending order. To learn more about sorting data, [click here](/help/workflows/workflow-editor#add-sorts).
## 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
* *Url -* In the URL field, specify the URL from which the desired file is to be downloaded. For more information about the action click [here](/help/tools/http-requests#download-file-from-url).
### Create Attachments Activity
1. *Order(Sales Orders) -* Select the specific Sales Order record to which the attachment will be added. This defines the parent order that the new attachment will be associated with.
Click the “Add field” button. Priority requires the following details to populate:
2. *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:
3. *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](/help/tools/enginis-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.
2. Press on the 3 dots on the right side of the Priority connection
3. Click on the “Edit” option.
4. 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](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](https://s.priority-connect.online/wcf/service.svc)
### Form Activation Activity
1. *Form name -* Choose the Form name from the drop down menu. The available forms are the open parent screens and child screens from your Priority account.
2. *Activation -* Choose the Activation from the drop down menu. According to the Form name, an identifier field will appear. Enter a **static value** as you can see at the image below:
1. *Quote Number –* Enter the specific quote identifier to retrieve or filter the related subform records. This value determines which quote the action will be executed against.
2. *Add Subform Filter –* Allows you to add additional filtering conditions to the subform data. This helps narrow down the returned records based on specific field values or criteria.
3. Repeat steps 1-2 until all required fields are filled up and “Ran successfully” message will appear.
3. *Run -* Press Run. Each Run can add new fields to fill in.
### 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. *Procedure name -* Choose the procedure name from the field options tab in the tooltip menu. All the available procedures.
2. Fill in the required fields with static values first to setup the activity.
3. *Run -* Press Run. Each Run can add new fields to fill in. When you need to reset the values you can press the “Reset” button.
4. Repeat steps 2-3 until all required fields are filled up and “Ran successfully” message will appear.
5. After the procedure ran successfully, you can now change the relevant static values to parameters to allow the workflow to run using dynamic values.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.