Creating a new EDI is used to ease your work, by automating specific tasks.

In the below example, we create a new EDI task that triggers an email to a specific email address and attaching pictures. We define what we would like the Email Subject to be and also defines the file naming of the attached pictures. Also we define that it is mandatory for the user triggering this EDI, that input of an Estimate No. is required, that the email cannot contain more than 15 pictures, and that the sending the actual email should be delayed 5 minutes, to allow the Estimate to be submitted via seperate system, eg. a Depot Management System.

Below is the description of how to do this:

In 1) "Terminal" we define which Users/Devices should have permission to see and user the EDI task. Then we give the task a name 2) "Destination name", and specifies what the task should do.

We want 3) "Document type" to be "Attached pictures" and 4) "Protocol" is E-mail.

Then we define the 5) "Address" (email address) where to send the email and in 6) "Email subject" we want the Container Code inserted. If required it is possible to 7) "Additional email" define one or more CC email adresses, seperated by "," (comma).

When attaching the pictures to the email, the filename(s) 8) "Filename mask" needs to be formatted specially. Here we use variables to automate this for us. Check later in this document for supported Variables.

To make the EDI task active, check 9) "Is active", and all users that have access to pictures in Terminal "MAIN", can use the new task.

The last thing to do is define some special10) "Params", to prompt for input of Estimate No, splitting email into multiple emails if there are more than 15 pictures to be emailed, and define the delayed send of emails. Check later in this document for supported Params. 

Variables that you can use in the Subject and Filename mask fields:

{est_num}, {est#} or {estimate} = Replaced with the Estimate Number entered when submitting in the EDI form

{est_date} or {estimate_date} = Replaced with the specified Estimate Date when submitting the EDI form.

{container} = Replaced with the actual Container Code.

{counter} = Counter with 1 digit (1, 2, 3, 4, etc.)

{counter2} = Counter with 2 digits (01, 02, 03, 04, etc.)

{counter3} = Counter with 5 digits (001, 002, 003, 004, etc.)

{counter4} = Counter with 6 digits (0001, 0002, 0003, 0004, etc.)

{counter5} = Counter with 7 digits (00001, 00002, 00003, 00004, etc.)

{Y-m-d}  = Currently only valid in “Filename mask”


INPUT_ESTIMATE_ID=1 (0 or 1: 1 will show a field where you can type in the Estimate Number. 0 will hide the field.

INPUT_ESTIMATE_DATE=1 (0 or 1: 1 will show a field where you can type in the date of the Estimate. 0 will hide the field)

INPUT_MESSAGE_BODY=1 (0 or 1: 1 will show a text input field where you can type in text that will be used as email body. 0 will hide the field)

SEND_PICTURES_CHUNK_SIZE=8 (Some digit value: Some recipients don’t allow emails larger than X MB. Normally ConPDS pictures are resized to around 80-120 Kb. If you set this parameter to e.g. 8,  and you are trying to send 14 pictures. Then it will trigger a split of photos into two separate emails. The first email with have 8 pictures attached, and the second email will have the remaining 6 pictures)

SEND_DELAY=5 (0 to some digit value (minutes): Some recipients require the estimate to be received before they allow they will accept pictures. Setting this value to e.g., 20, will trigger a delayed email send of 20 minutes. That way, the estimate has time to be received and imported at the receiving party)