DEX configuration Your school has options for four different levels of success/failure notification emails.
Admin Emails at the Import / Export / FTP, etc. level
Admin Emails at the Group (Process) level
IO Process Notification Emails at the Import / Export / FTP, etc. level
IO Process Notification Emails at the Group (Process) level
Samples Details/samples of each email type are shown below.
Your school may choose to receive all four, each of which could be sent to different email lists if desired (multiple addresses separated by a comma). It is recommended that schools use email distribution lists, that they control, versus email addresses for specific people. Each distribution list can be configured with a different “From” address if desired, i.e., the emails could appear to have been sent from your own IT department.)
By design, Regent IT Ops and the Regent DEX team also get gets the high-level emails when a failure occurs in a DEX process.
Please note that the IO Process Notification Emails could have a custom Stored Procedure stored procedure can be implemented to pull additional information regarding the errorsIO Process Notification Emails. A JIRA ticket Customer Zone request must be submitted for this.
SBL
...
Success/Failure Email Types
1. Admin emails at the Import / Export / FTP, etc. level
...
(General Summary, by design)
Example trigger: An SBL file is not formatted correctly and the entire file failed to load
...
Notes: When submitting a request to Ops to set up this upemail type, the following details need to be suppliedare needed:
Success Email: the email address(es) to send 'success' emails to - multiple addresses separated by a comma
Send Success Email: flag to indicate if 'success' emails should be sent
Failure Email: the email address(es) to send 'failure' emails to - multiple addresses separated by a comma
Send Failure Email: flag to indicate if 'failure' emails should be sent
Email From: can be any address; typically this will always be the default non-reply address: DEX_Automated_Notification@regent.com
Note the "Email Server" value will be set by Ops
...
2. IO Process Notification emails at the Import / Export / FTP, etc. level
...
Example email scenario: IO Process
...
information such as
...
Total Records, Processed Records, Unprocessed Records
...
Notes: When submitting a request to Ops to set up this upemail type, the following details need to be suppliedare needed:
Process Notification SP: this will always be "dex_IOProcess_NotificationDetailsGet" unless specific DEX development was done to create a new SP for this (per a JIRA ticket)
Success Email: the email address(es) to send 'success' emails to - multiple addresses separated by a comma
Send Success Email: flag to indicate if 'success' emails should be sent
Failure Email: the email address(es) to send 'failure' emails to - multiple addresses separated by a comma
Send Failure Email: flag to indicate if 'failure' emails should be sent
Email From: can be any address; typically this will always be the default non-reply address: DEX_Automated_Notification@regent.com
Note the "Email Server" value will be set by Ops
Note the "Send email as HTML" is for future use
...
3. Admin emails at the Group (Process) level
...
(General Summary, by design)
Example trigger: An SBL file is not formatted correctly and the entire file failed to load
...
Notes: When submitting a request to Ops to set up this upemail type, the following details need to be suppliedare needed:
Success Email: the email address(es) to send 'success' emails to - multiple addresses separated by a comma
Send Success Email: flag to indicate if 'success' emails should be sent
Failure Email: the email address(es) to send 'failure' emails to - multiple addresses separated by a comma
Send Failure Email: flag to indicate if 'failure' emails should be sent
Email From: can be any address; typically this will always be the default non-reply address: DEX_Automated_Notification@regent.com
Note the "Email Server" value will be set by Ops
...
4. IO Process Notification emails at the Group (Process) level
...
Example email scenario: IO Process
...
information such as
...
Total Records, Processed Records, Unprocessed Records
...
Notes: When submitting a request to Ops to set up this upemail type, the following details need to be suppliedare needed:
Process Notification SP: this will always be "dex_IOProcess_NotificationDetailsGet" unless specific DEX development was done to create a new SP for this (per a JIRA ticket)
Success Email: the email address(es) to send 'success' emails to - multiple addresses separated by a comma
Send Success Email: flag to indicate if 'success' emails should be sent
Failure Email: the email address(es) to send 'failure' emails to - multiple addresses separated by a comma
Send Failure Email: flag to indicate if 'failure' emails should be sent
Email From: can be any address; typically this will always be the default non-reply address: DEX_Automated_Notification@regent.com
Note the "Email Server" value will be set by Ops
Note the "Send email as HTML" is for future use
Example Success/Failure Email Notifications:
| View file | ||
|---|---|---|
|
| View file | ||
|---|---|---|
|
| View file | ||
|---|---|---|
|
| View file | ||
|---|---|---|
|
| View file | ||
|---|---|---|
|
| View file | ||
|---|---|---|
|
| View file | ||
|---|---|---|
|
| View file | ||
|---|---|---|
|