25 JUNE 2020
This update includes an enhancement and a resolved issue.
- Naming Email Listener message file attachment.
When the option to save the email as an attachment is selected, an Email Listener saves the message files as attachments with .msg (for AWS, POP3, and IMAP) or .eml (for Graph API) extension.
The name of the attachment is extracted from the email subject line, and can have a maximum of 225 characters including a 14 characters time stamp of date and hour at the end. If the email has no subject line or an invalid subject line the attachment is saved with the name "Untitled-DDMMYYYY HHMM.msg" or "Untitled-DDMMYYYY HHMM.eml".
An IMAP protocol email with the subject, "Email !@#?$#@/$:-956 5463.rtrkl" received on June 22 at 15:30 will be saved with the name, Email !@#$#@$-956 5463.rtrkl-22062020 1530.msg.
The attachment name can have a space, but not any of these special characters (\, <, >, *, ?, /, ", :, |).
|Email Listener||For an email listener created with IMAP email server, the emails were not getting deleted from the gmail account after being fetched by the listener.||88629|
There are six pre-build application deployment packages available, depending on the type of application that you are deploying. You install each Cora SeQuence application separately.
|Site applications||Service applications|
When you deploy pre-built applications, you can choose between the Standard and Premium packages. The Premium package includes HotOperations. You can also build and deploy your own Cora SeQuence applications.
Click here to see how to deploy Cora SeQuence in an environment with pre-built applications.
For more details on installing and deploying Cora SeQuence, see this article.
You need credentials to access the Cora SeQuence repositories. Contact Support to obtain credentials.
Before upgrade, make sure to update the PowerShell modules to the latest version.
Click here to view a sample PowerShell script. Consider this sample for reference only, and do not copy paste from here.
During upgrade, all product application folders are deleted and redeployed:
- Web and App config files are overwritten in each release. You need to reapply your custom configuration settings after the upgrade.
- All custom files located in the application folders are also deleted. Custom files should be packaged as a custom application NuGet.
Files in the central configuration location are not changed.
For more details, see this article.