Relation between JobRequest and Account
Overview
Some of Transactional Email features can be controlled at both JobRequest level or at Technical Account configuration level. If JobRequest flags have been meant to provide granular control over which message must enable a feature or not, on the other hand the Technical Account configuration has been designed to allow or not the usage of a feature, and define the default expected behaviour for every JobRequest.
At the Technical Account level you can ask for each feature to set the following values:
active
: define if the feature is authorized to be used with the Technical Account or not;defaultActive
: define the default expected behaviour if nothing is explictly set into the JobRequest sent to that Technical Account (see below).
If the feature flag is explicitly defined at the JobRequest level (true
or false
), it overrides the Technical Account defaultActive
configuration.
Sum up tab
JobRequest flag* (if available) | Feature configuration at Technical Account level | Result | |
---|---|---|---|
|
|
| |
true | true | true | feature enabled |
true | true | false | feature enabled |
true | false | true | JobRequest rejected (synchronous response) |
true | false | false | JobRequest rejected (synchronous response) |
false | true | true | feature not enabled |
false | true | false | feature not enabled |
false | false | true | feature not enabled |
false | false | false | feature not enabled |
<empty> | true | true | feature enabled |
<empty> | true | false | feature not enabled |
<empty> | false | true | feature not enabled |
<empty> | false | false | feature not enabled |
*flag could be X-Header or a REST parameter
Features list
List of features that can be controlled at the JobRequest level:
Open Tracking (REST only)
Link Tracking (REST only)
AntiVirus Multiscan
Secure Document Handling (REST only)
Message Signing
Trace & Recover (SMTP only)
Push Notification