Issue: Comsense's automated email feature puts an email function parameter (&subject=) and the automated subject line in the recipient field.

Environment: Comsense Enterprise
Cause: Microsft's update to the Monthly Channel of Office 365. On this update, Outlook is version 2001 (build 12430.20184). Outlook version 2001 manages command line parameters in a way that does not consistently work with Comsense's current command line parameters. The Microsoft update more strictly supports industry standards outlined in IETF RFC 6068.
Resolution: Create a new email client configuration that accommodates the update to the Monthly Channel of Office 365.
In this article:
Accessing Email Client
Enterprise > System Options > Email Client

Creating a New Email Client Configuration
In the fillable line item of the Email Client window:
- Enter a name for the new email client configuration in the Email Client column
- We recommend "Outlook 2"
- Copy & Paste the parameters from the original Outlook email client configuration into the new email client configuration
In the new email client configuration line item:
- Replace all & symbols with ? symbols
- None column
- Email Address and Attachment column
- Email Address Only column
- Attachment Only column

- Click Save
You now have a new email client configuration.
Using the New Email Client Configuration
These procedure will refer to the new email client configuration as Outlook 2. Outlook 2 does not automatically become the default email configuration. You must assign Outlook 2 on a user-by-user basis.
Accessing User
Enterprise > System Options > User

Assigning the New Email Client Configuration
In the User window:
- Click Open
- The Find window will open
- Click Find Now
- The user list will populate
- Select your user
- Click Open
In the Email Client field:
- Select Outlook 2

- Click Save
Outlook 2 is now the default email client configuration for this user.
This fix does not work, at least not universally. Outlook 2016 now throws an error "Object Not Found" upon generation of the email.
Hi Ralph,
We have successfully tested this with Outlook 2016 build 16.0.4966.1000. I will create a ticket for you and have a colleague follow up to get a resolution for you.
Thanks!
This worked for us. Thanks Patrick!