Back4

Sometimes, the underscores were replaced with spaces into the Subject string of the received emails.
The problem occurred using POP3 protocol, because the email's Subject was decoded from 'quoted-printable' format.
In fact, the email watcher replaced the underscores with spaces, but only if the string didn't contain any space already.
Now fixed: if the Subject is not 'quoted-printable' encoded, it is returned untouched (that is, with underscores).
Note that the string is considered 'quoted-printable' encoded only when it contains the '=' character followed by two numeric characters or new-line.

Modified date: 21/07/2016 11:54:09 - P4 Changelist: 83058 - From build: main.2973.x

A wrong index on gn_AuditSnapshotTable caused multiple records to be added to it. Now fixed.
To solve the problem without upgrading the build it is possible to execute this query (must be done out of production and must be executed again after a db upgrade):
 
delete gn_AuditSnapshotTable from gn_AuditSnapshotTable sel where gn_objectid=sel.gn_ObjectId and gn_ModifiedDate != (select max (gn_modifieddate) from gn_AuditSnapshotTable where gn_ObjectId=sel.gn_ObjectId) go 
 
drop index dbo.gn_AuditSnapshotTable.iTPCVAKVV1FR0TEBOFKHMEUV9M5 
go 
 
CREATE UNIQUE NONCLUSTERED INDEX iJKDTAQ9FDRD9OE18M3GLUAMF75 ON dbo.gn_AuditSnapshotTable ( gn_ObjectId ASC ) 
go 

Modified date: 20/07/2016 11:20:57 - P4 Changelist: 82991 - From build: main.2972.x (T)

When the Back4 email queue was configured to use the IMAP protocol, all the emails were read as plain/text, even if the html version was available.
Note that the HTML was correctly read when the mail client used the POP3 protocol.
Now fixed: Back4 is able to read the html version of the emails received using both the IMAP and POP3 protocol.
Modified the wf_ImportActivityData.xml workflow to create the gn4:story containing the input HTML, so to keep the HTML styles.

Modified date: 19/07/2016 17:50:35 - P4 Changelist: 82982 - From build: main.2971.x

When receiving an email using the IMAP protocol, the Back4 email watcher raised the 'System.OutOfMemory' exception.
Now fixed.

Modified date: 15/06/2016 17:26:21 - P4 Changelist: 82558 - From build: main.2937.x (T)

In Back4, when the workflow associated to the email watcher ended with errors, the task was logged as success. 
Now fixed: according to the dataSourceTemplate 'onError' attribute, if the task workflow ends with errors, then the task result is logged as error (showing the red icon into the task log panel).

Modified date: 13/06/2016 14:54:07 - P4 Changelist: 82511 - From build: main.2935.x (T)

The time for a scheduling rule was wrongly adjusted according the dailight saving time.
So if the start date was set when the daylight saving time was off, it moved one hour ahead when the daylight saving time started.
Now fixed: despite the daylight saving time, the time set to run a schedule doesn't change (assuming that the client and server are into the same time zone).

Modified date: 07/06/2016 11:53:43 - P4 Changelist: 82418 - From build: main.2929.x (T)

Processing an email in Back4, the followed error occurred: "Value was either too large or too small for an unsigned byte.".
This was because one byte contained into a multi-byte Unicode character was internally translated into a Unicode character (greater than 255): converting again the Unicode character into a byte caused the error.
Now fixed: the received email generates a story containing the correct Unicode characters.
Moreover, now the wrong emails are copied into the error folder (configured into the Back4 queue) even when the error occurs while parsing the email content.
Note that, before this change, an email file was copied into the error folder only if the associated workflow failed.

Modified date: 01/06/2016 17:29:09 - P4 Changelist: 82397 - From build: main.2923.x (T)

In cleanup process, limited the error, warning or success logs to 4096 characters.

Modified date: 31/05/2016 11:41:16 - P4 Changelist: 82370 - From build: main.2922.x

[18] Pop3watcher: UTF-8 characters are not read correcty when using POP3 protocol

GN4-4137

Emails that contained UTF-8 characters (mainly accented chars) were not read correctly when using the POP3 protocol, while it worked fine using IMAP.
Now fixed: the Back4 email poller tries to retrieve the correct charset parsing the textual content of the email.

Modified date: 19/04/2016 15:59:04 - P4 Changelist: 81782 - From build: main.2880.x (T)

[359] Back4: connection error from mail watcher displays the password

GN4-3828

If for any reason there was a connection error from a mail watcher in Back4, the password for the email account was displayed in clear in the error log.
Now fixed: for security reason the password is not displayed anymore in error log.

Modified date: 17/12/2015 11:35:36 - P4 Changelist: 80094 - From build: main.2756.x (T)