...
- An Webhook Issue Event occurs, rendering a TemplateSet (selected in Email Notification Mapping). As part of that, unique links are generated (see later) for each required DirectiveSet to run. The email is then sent to the Recipient.
- The Recipient clicks on a link, that contains no data other than a token. The link points to a public REST API on the JEMHCloud server.
- The JEMH REST service validates the token is still valid (not yet used), and executes the process.
- JEMH Cloud renders a processing result, that the user can customize (in a DirectiveSet Render Result TemplateSet) and which is selected in each directiveSet it is needed. The HTML is returned to the user.
| Gliffy | ||||||
|---|---|---|---|---|---|---|
|
How it works
Directive Sets work in a very similar way to the manual approach (a Test Case), in a nutshell, the DirectiveSet is the 'body' of a text email, JEMH Cloud will 'supply' a minimal set of headers with specific values in order to drive the JEMH Cloud processing logic (issue selection by subject, sender lookup by address). They key pieces of information are shown below:
...