e:Mission side

Möglicher Ablauf

Beschreibung der Schritte

Smtp-In

Checks recipient of incomming message.

If  it  addressed to support@company.com , then moves to  the ‘Cabus-Trouble-Ticket-In’,  otherwise adds the message to the queue with ‘unrecognized messages’.

Trouble-Ticket-In

Checks, weather an incomming messsage is a new Trouble Ticket or contains an additional information to already opend one and passes e:Client as a job parameter to a corresponding workflow step:

• New Trouble Ticket goes to ‘Insert into Table “A”’;
• Old Trouble Ticket goes to ‘Insert into Table “B”’;

Insert into Table “A”

(Table “A” contains initial Trouble Ticket info )

• Reads fields values from e:Client and inserts them into the table;
• Passes a complete e:Client as a job's parameter to the next Workflow's step.

Insert into Table “B”

(Table “B” contains Trouble Ticket Reports )

• Inserts Trouble Ticket’s additional information into the table”B”;
• Passes e:Client as parameter to the next Workflow’s step ‘Save-e:Client-As-Blob’

Save-e:Client-As-Blob

Saves e:Client as a Blob-field into Table “A”

Timer

Every 5 minutes starts ‘e:Client-Send-Check’ eScript

e:ClientSenden-Check

• Checks in table "A" which report (which Trouble Ticket and what kind of report: "Annahmebericht", "Zwischenbericht" or

     "Schlussbericht") can be sent to Customer;

• Writes to e:Client-XML-structure of selected records all info from the record’s fields;
• Passes e:Client as parameter to the ‘Save-e:Client-As-Blob’;
• Passes e:Client as parameter to the ‘Reports-Out’

Reports-Out

Creates a message to Customer with Trouble Ticket Report  and e:Client attached;

Smtp-Out

Sends Message with Report and e:Client attached to Customer