E-mail transport via Exchange Web Services
Active Roles can use Exchange Web Services (rather than SMTP server) to communicate with Exchange Server when sending notification messages and getting response to notification messages. This enables notification recipients to perform approval tasks by replying to notification messages from their regular e-mail clients, instead of using the Web Interface pages to approve or reject the requests. With the use of Exchange Web Services, Active Roles makes it possible for an approval workflow to behave as follows:
- A change request that requires approval causes Active Roles to send a notification message to the designated approver, with the message body containing the option to approve or reject the request.
- The approver replies to the notification message by choosing the desired option (either approve or reject) and typing in a text to explain the reason for that choice.
- Active Roles receives the reply message from the approver, checks to see if the approver elected to approve or reject the request, and then allows or denies the requested changes accordingly.
The use of Exchange Web Services calls for the following prerequisites:
- Exchange Server 2013 or later. Exchange Web Services is deployed with the Client Access server role.
- Dedicated mailbox hosted on Exchange Server 2013 or later. The mailbox should be reserved for the exclusive use of Active Roles.
The following configuration settings are available with the Exchange Web Services option for e-mail transport.
Exchange Web Services address
This setting identifies the URL of the Exchange Web Services endpoint, which locates the exchange.asmx file on the Exchange server running the Client Access server role. For example, https://CAServer.domain.com/EWS/exchange.asmx
Active Roles mailbox credentials
Active Roles’ mailbox credentials
This setting specifies the user name and password of the mailbox through which Active Roles will send and receive e-mail. The mailbox must be located on Exchange Server 2013 or later, and must be reserved for the exclusive use of Active Roles.
It is important that no applications other than Active Roles access this mailbox. Processing e-mail messages in Active Roles’ mailbox by other applications, such as Office Outlook, can cause an adverse effect on the functionality of Active Roles.