RE: Triggering Process With Email

arunramanathtm — Fri, 10 Apr 2020 19:21:11 GMT

Have a logic to check for common (unique) thing among both emails .... example Customer Id.
When this common field is received from two emails, then kick the subprocess

RE: Triggering Process With Email

Stewart Burchell — Tue, 07 Apr 2020 16:02:41 GMT

I'm sure there are a variety of patterns to address this, but here's one possible pattern:

1st Email received triggers Process Model A that writes the content of the body to a database table, along with a correlation token (something unique that both emails share in common)
2nd Email triggers Process Model B that stores the attachment as an Appian document, and writes an entry to a database table that holds the new Document Id and also the same correlation token value as described in Step 1.
A Process Model that runs on a regular basis (e.g. every hour) looks to see if there are any entries in the Database that indicate that both emails for a given Case have been received. If so, it starts the sub-process you describe, passing it the necessary data.
The sub-process completes, and either deletes or marks the data in the database as having had a case completed so that the next time the regular process runs it doesn't submit a duplicate process

A alternative process-centric pattern would have process models that get triggered by the incoming emails and send messages to a process instance that is waiting (this gets more complicated because I assume the emails could come in either order - Body then Attachment, or Attachment then Body), but the principle would be the same - you'd need to have a process to receive each email, some correlation token value that would help you find if a waiting process existed and route to it if it did, or start it if it didn't.