Settings

(1) Use V2 file names: Some software systems create or expect files whose names match V2 but have V3 content. You can set this checkbox for that.

(2) Support EngPART: Only applies to V3 messages. In this case, changes to your master data (My information) will be transmitted to the partner on the next transmission. See section My/Partner information.

(3) Create EngPART: If the button is clicked, all contacts for this partner (Partner information) are marked as changed and will be sent as ENGPART message on the next transmission. Useful if you want to set up a new partner and send all contact details.

(4) OFTP service: You can select an OFTP service here (as defined in configuration file ./etc/factory.xml).

(5) Trace OFTP: An OFTP trace file is created, similar to the one for profiles in phase 1.

(6) Route: The route (also address code) consists of 5 arbitrary characters and serves the internal distribution of the data on the receiver side.

(7) Keep for (in days): The time after the message has been sent completely and without error. Messages and their files that are older will be deleted automatically.

(8) Mail notification to: If you want to send a report or a notification for new messages or errors to specific people via email, fill out this input field. Multiple recipients can be specified, separated with semicolons (;).

(9) Permitted users: Only the selected users (that also have the user right ENGDAT) are allowed to view/edit the inbound and outbound ENGDAT messages. Important note: If you set checkbox Is exclude list in the subdialogue, then all users except the selected ones are allowed to see/edit.

(10) Cron schedule: In addition, times (in crontab syntax) can be defined for an automatic transfer.

File pattern

For V2 messages, the mandatory syntax is ENG resp. EN2 + <yyMMddHHmmss> + <route> + <number of technical documents> + <counter of current file>. yy stands for the year, MM for the month, dd for the day, HH for the 24-hour format, mm for the minutes and ss for the seconds. A valid file name for a message, for example on the 21.1.2013 14:30:00, consisting of three documents (+ meta information = 4) is ENG130121143000PART1004001.

For V2 messages, the filename is ENG resp. EN3 + <yDDDHHmmss> + <route> + <number of technical documents> + <counter of current file>, where DDD stands for the day in a year. A valid V3 filename would be ENG3021143000PART100040001.

Note: The ENGDAT module automatically generates these file names, you do not have to do this yourself.