Problem

Some additional fields in COTI.xml should be used as task fields on task creation to better support integration and automation processes.

Solution

For the following COTI.xml

    <project
            name="COTI-Description" ==> Used as description of the project
            project-id="4711"
            proposal="yes"
            checkout-date="2013-08-21T11:59:00Z"
            due-date="2013-09-10T00:00:00Z" ==> deadline date
            comment="very urgent!"
            tms-id=""
    >
    <subject>Subject</subject>
    <meta name="fieldName" value="123" description=""/>
    <meta name="customerNumber" value="321" description=""/>

We expect the following fields in Translate5:

• add the content of "comment" to the project description with the prefix "\n\nComment:\n" before it. First 2 newlines omitted in case project name attribute from COTI is empty.

• add the value of "project-id" as value of "order number"

• use date in due-date for the deadline-date of the task

• add the content of "subject" as value to "subject", in case such a custom field exists in the instance
  <subject>Subject</subject> -> "Subject" in custom-field subject

• add the value and the description of meta as value to "fieldName", in case such a custom field exists in the instance. Where "fieldName" is meant as a placeholder of any kind of value.
  <meta name="fieldName" value="123" description=""/> -> 123 in custom-field

• assign created task to customer submitted in meta-field. The matching field in Translate5 is "client number".
  Hirachy of setting the client/customer in Translate5 will be:
  1. if COTI config runtimeOptions.plugins.CotiHotfolder.filesystemConfig is customer-specific, then use this cutomer no matter which information is submnitted in the COTI.xml.
  2. when customerNumber is submitted in the COTI.xml file and we find a matching client/customer in Translate5, this client should be used.
  3. usual fallback as configured in Translate5