NexJ Logo

Resolved issues



Custom validation error messages for attachment questions in CPM forms now display in the user interface.


When you enter and then clear a value in a required drop-down or attachment question field in a CPM form, an error message now displays as expected.


When a user clicks Submit in a CPM form, the form is now submitted immediately and the Submit button is disabled, preventing the errors that would previously occur upon multiple clicks on the button.


An issue that sometimes prevented submission of CPM forms with file attachments has been resolved.


Global variables referenced in CPM forms no longer return null after the form is loaded.


Parent enumeration values now populate automatically based on the child enumeration value selected. For example, based on the enumeration mapping, the country field in a form automatically populates upon selecting a state.


An issue that caused file attachments in CPM forms to lose data during upload has been resolved.


Prior to this release, object pickers with the singleClickPicker property enabled would open when a user clicked on any field including disabled fields. This issue has been resolved and the pickers now open only on enabled fields as expected


A cross-site scripting issue with type-ahead controls has been fixed.



You no longer receive an error when trying to reseed on bp-list with flows registered on the Scheme console.


Repeaters pointing to the same object now allow for form submission.


Saving transient flows with NexJ CPM form validation no longer generates an error.


Dynamic validation now works for NexJ CPM object type fields and validation messages display in the user interface.


Users no longer experience an issue that resulted in an error when uploading large files.


When field values are changed the server validation messages are now displayed as expected.


An error message now displays as expected when an invalid date is selected.


Several performance issues with multiple picker dialogs in NexJ CRM when using Microsoft Internet Explorer have been resolved.


Prior to this release, when you created a new Custom Field for multiple contacts and selected Replace in the Update a Custom Field dialog, an issue caused the Unique checkbox in the Add Custom Field dialog to be cleared instead of selected by default. This issue has been resolved.


An issue that caused a contact import process to fail if an email address was not specified for any of the contacts has been resolved. The contact import process now completes successfully and contacts that do not have an email address specified are imported without an email address.


If multiple instances of the same BI attribute are referenced in existing ad hoc reports, and the SysUpgrade process has been run multiple times, these attributes were displaying as duplicate custom fields in the Fields and Filters dialog on the Ad Hoc Reports workspace. This has been resolved.


To promote consistency across the application, you can now search for users in the Manage Favorites dialog by last name instead of first name.


Enumeration values that have been deactivated in the Enumerations page in NexJ Admin Console are no longer available for selection in NexJ CRM.


Prior to this release, an issue caused Edit Security settings to override View Security settings for an activity or an entity when the View Security was set to Private and the Edit Security was set to Group. This issue has been resolved.


Prior to this release, when a delegate user scheduled a meeting on behalf of another user and then updated the meeting reminder time, the reminder time was not updated in the other user’s view. This issue has been resolved. Now the reminder time is updated for both users as expected.


Previously when selecting participants for a campaign, an issue caused the New Participants list in the Participants dialog to be sorted in reverse alphabetical order instead of alphabetically. This issue has now been resolved.


Users with the AdminScheduleItemDelete privilege (for example, system administrators) can now delete schedule items without having to be a user participant in the meeting.


The ScheduledTrigger table now stores the create time of a time-based notification.


The performance of the SysStatCleanupBatchJob was improved to also address the clean-up demands of a large cluster.


When invoking an event with primitive arguments through REST, arguments are no longer parsed as empty collections.


Previously, filtering contacts by using the Does not equal condition on the Category field omitted contacts for whom no category at all was set. This issue has been resolved.


An issue with the addressBlock token incorrectly formatting addresses as a single line rather than multiple lines when using Batch Email has been resolved.


A push redirector issue that resulted in blocked threads in the Java Virtual Machine has been resolved.


Prior to this release, when a user switched the home phone number to be the new business phone number and the business phone number to be the new home number, the (H) beside the home phone number was missing in the contact banner. This issue is now resolved.


Even with ad-block software enabled, the NexJ Systems logo now displays in the About NexJ Customer Relationship Management pop-up in NexJ CRM.


An issue caused the testExchangeOutboundTaskTransformation test case to fail when comparing messages that included different time zone IDs. This issue is resolved.

ECRM-26698, ECRM-26949

An issue that caused unit tests to fail has now been resolved. Previously, when you created multiple instances of rules:WorkflowRuleSet with the same target and trigger type, the notification engine produced an unexpected error.


When a parent dialog was closed before a child task/calendar dialog had been saved, the child task/calendar dialog was not closing. This has been resolved.


When using the Import Data tool and Oracle as the database, the Leads' and Contacts' Maximum Import Limits and Maximum Matching Limits in the Import page of the NexJ Admin Console were displaying as empty fields. This has been resolved.


Prior to this release, if the authentication protocol was set to custom, users would not be able to log in using SPNEGO. This issue is now resolved.


An issue that caused a same proxy multiple thread error to be logged when using IBM WebSphere MQ has now been resolved. Prior to this release, it was possible for an exception to create a state where the multiple thread error would occur continuously.


Previously, when you applied strikethrough formatting to a note, the formatting was not preserved after you saved the note. This issue is now resolved.


An issue caused intermittent optimistic lock exception errors to appear for the testDeleteInactiveToken test case in the sso:InactivityTimeout unit test. This issue is resolved.


An issue that caused an unexpected error to display when navigating to the Capital Markets tab on the Home workspace has been resolved.


Currency creation in unit tests now only allows for the creation of currencies that do not already exist.


A race condition in the session manager that resulted in blocked threads has been resolved.


An issue that caused a gradual increase of garbage collection overhead and CPU consumption by all Java Virtual Machines has been resolved.


An issue has been resolved that affected birthday notifications. Prior to this release, if you edited a contact's profile after you received a notification about the contact's birthday, you would receive an additional birthday notification.


The filter drop-down in the Activities tab on the Opportunities workspace was missing Email as an option. This issue is resolved.


BI bulk sync of Act is now parallelized. Acts are now read one page at a time, and bulk sync initiated for each page individually, rather than reading all Acts at once and initiating bulk sync for all of them in one batch. This is specific to Acts, but the same pattern can be applied to other sync classes as a customization.


An issue that affected time-based rules has been resolved. Prior to this release, if you ran a time-based rule from the Customize workspace, the process did not complete in the Process tab of NexJ Admin Console.


Files listed in the Print Attachments for Contacts dialog in the Attachment drop-down menu are now displayed in alphabetical order when printing a task with multiple attachments for multiple contacts in the Journal tab.


The message age in the object queue statistic is now calculated in milliseconds instead of minutes.


Prior to this release, pinning a note with multiple entities in the For field pinned the note for all listed entities instead of pinning it for the selected entity only. This issue has been resolved.


The behavior of ScheduleTriggerCleanupBatchJob has been updated. The batch job only performs clean-ups on executed scheduled triggers with an object due in the past.


Users no longer experience an issue where an upcoming reminder is not displayed at the top of the alarm list if there is a high number of reminders scheduled for a future date beyond the most immediate reminder.


Prior to this release, when you filtered by Description in the My Tasks user defined filter and selected the ends with operator the search results included all tasks that contained the inputted Value text string, instead of only those that ended with the inputted value. This issue has been resolved.


An custom field caching issue that prevented the execution of rules has now been resolved. Previously, if you created a custom field with any rule, a user who was not authorized to view the custom field experienced an error when triggering the rule.


An issue that affected the subscription type in Exchange Server has been resolved. Previously, the subscription type did not change if you changed an Exchange target's subscription from push to streaming.


Prior to this release, the generation of a malformed report could trigger an out of memory issue. This issue has been resolved.


Prior to this release, the Remove All button in the Select Accounts dialog in the Journal tab for contacts was disabled. This button is now enabled.


Previously, when you created a note with group edit security set to private, the quick note icon was missing. This has been fixed. Currently, when another user looks at the note, there is a quick note icon. Clicking the icon opens a dialog indicating that the note is read-only.


You can now create a custom filter from a contact's Journal tab, select the delegated tasks and conditions, and the picker window allows for the selection of Select User rather than Select Contact.


An issue that prevented users from seeing all the external meeting participants in the Attendees tab of a schedule item is fixed.


Prior to this release, when you were adding a new deal or opportunity, and you selected a company in the For field and opened the Contacts tab, the client in the For field defaulted to the Contacts tab and disappeared when you saved the deal or opportunity. This issue is resolved.


A rules:ConditionExpression threw an error when it was evaluated but the stack trace in the logs did not provide the required information needed to investigate the error. This issue is resolved.


After refreshing the user interface and clicking on a contact from the Opportunities workspace, the incorrect contact context would load in the Contacts workspace. This has been resolved.


An issue that causes the isPrintWhenDetailOverflows flag to be set to true for some predefined reports, and which can cause memory issues, is resolved.


When you send an email to a lead and then edit the email in the lead's journal, HTML tags no longer appear in the email body text in the Notes field in the Edit Email dialog.


The first few letters of some field names in the Edit User Group screen are no longer being cut off. The entire field name is displayed as expected.


The unsuccessful completion of batch processes to add/delete team members has been resolved by adding a new queue (CoverageTeamUpdateQueue). This new queue should only have a concurrency of one. Please note, changing the concurrency of this queue could cause the issue to recur.


Inactive products are no longer appearing in the list of available products under Opportunities.


An issue that caused deleted stages for opportunity templates to display in the Stages subtab, in the Opportunity Management tab, on the Customize workspace is resolved. You no longer need to refresh the list of templates to remove deleted stages.


An issue with closing file journals has been resolved. Previously, this would result in many warnings appearing in the logs and occasionally triggered an error.


An issue that caused the My Contacts' Recent Activities Report to display incorrect data when provided in an Excel CSV format is resolved.


Previously, in the Campaign Participants tab of the Campaigns workspace, parent company names in the Company column were not showing. This has been resolved.


Prior to this release, an issue with the My Client's Recent Activities report caused the Last Edited field to display values of Last Edited By and (Blanks) when the report was generated in Microsoft Excel format. This issue has been resolved.


Previously, if you created a rule for service requests and made it time-based, set the time-based value to 0 hours or 0 days after the service request creation date, and triggered the notification by creating a service request, the notification was not sent. This issue is resolved.


When editing an email journal entry created by a batch email action you can now View/Edit Full Notes as expected.


The Service Request Summary Report has been removed from the application due to lack of adoption.


Users no longer experience an issue that caused the Edit Note dialog for certain journal entries to display with cut off text. Previously, when you opened a Birthday Mailer or a Client KYC journal entry for editing and clicked View/Edit Full Notes the Edit Note dialog was truncated.


An issue that caused blocked threads in the push redirector to create other blocked threads in the corresponding push servers has been resolved.


Exchange sync links were automatically disabled after 48 hours of subscription errors. This is no longer the case.


Prior to this release, when you created a time-triggered rule action in the Customize workspace to send a notification to a user when a new contact was created, the user did not receive the notification, and the pending action disappeared from the Pending Time Based Actions page in NexJ Admin Console instead of changing to an executed status. This issue is resolved.


An issue in NexJ Studio caused the sort combo in the picker editor to reject changes to the value of the combo. This issue is resolved.


Previously, when you changed the contact's service level in the contact's Edit dialog, you were unable to save your changes and close the dialog. This issue is now resolved.


An audit trail message for Exchange Synchronization did not include the expected folder name. This issue is resolved.


Because most users have their categories show in rule conditions, the hard-coded value of 4 in Category'MAX_IN_RULE_CONDITIONS in the Category unit test case was causing the test case to fail. This has been resolved.


An issue where the user was not being informed upon attempting to perform an operation that exceeded the max HTTP request size has been fixed. Users are now presented with a prompt to reduce their request size.


An unexpected error that occurs during schema upgrade has been resolved. This error was triggered by any user that selected My Sync List as a list favorite before schema upgrade.


The date-part function has been enhanced to support null arguments in the persistence layer.


An issue that caused RollupEngine messages in the object system queue to slow down the processing of reports and other batch jobs has been resolved.


Prior to this release, adding parts with a transfer encoding type other than 7bit to an email or invitation sent from NexJ CRM caused the email or invitation not to render properly in Hotmail. You can now prevent this by setting the value of the TRANSFER ENCODING attribute of the EXCHANGE-CRUD class to the encoding type you are using, for example, base64. This converts the entire email or invitation to the encoding type you specified, ensuring the email or invitation renders properly.


The font size used for imported contacts error message is now consistent with the standard font size used for text.


An issue that caused an access error when a non-admin user creates a new user list has been resolved. Previously, when you assigned the PublicUserListManage and UserListManage privileges to a non-admin user, an access error occurred when the non-admin user created a new user list on the Customize workspace.


An issue that would cause an unresponsive state in the application when the X button on a dialog was clicked has been resolved.


The ${birthdaySummaryString}, ${startTimeFormatWithTimeZone}, and ${endTimeFormatWithTimeZone} notification tokens now format in french when using the French locale. The browser must be refreshed after changing the application locale in order to see the updated notification summary strings.


Previously, if you created an Opportunity with a non-USD currency and exported to CSV format, the currency values appeared as USD values in the CSV. This has been fixed so that currency values in the CSV are now in the same unit that the Opportunity was configured to use.


An issue that affected drop-downs in NexJ CRM has now been resolved. Previously, if you navigated to a different workspace while you had a drop-down open and then returned to the same workspace, the drop-down would sometimes remain open.


The following unsupported block styles have been removed from the Document Manager rich text editor: Marker, Big, Small, Typewriter, Computer Code, Keyboard Phrase, Sample Text, Variable, Deleted Text, Inserted Text, Cited Work, Inline Quotation, Language: LTR, and Language: RTL.


The Schedule Month Report now shows appointments in the correct order according to time.


An issue that caused opportunities to disappear from the Opportunities journal when NexJ CRM was opened in Internet Explorer has now been resolved. Prior to this release, when you opened an opportunity for editing from the Opportunities journal and then closed the Edit dialog, some of the opportunities that were previously listed would disappear. The issue was specific to Internet Explorer.


A Null Pointer Exception (NPE) sometimes occurred while saving client state for the Opportunity workspace. This has been resolved.


The "in the next (days)" filter condition for the birthdate User Defined Filter (UDF) has been removed, and the caption for "upcoming in (days)" filter condition has been renamed to "in the next (days)".


An issue that prevented portlets from refreshing has been resolved. Previously, if you generated a report in the Contacts workspace, some options in NexJ CRM did not function properly.


An issue that caused turned off notifications to display in the wrong language has now been resolved. Prior to this release, the descriptions of turned off notifications would display in the language the notifications were triggered in, regardless of your current language preference in NexJ CRM. You can view turned off notifications in the Notifications tab under User Preferences.


Customized ETL activities should use the where clause of any read cursors to avoid reading deleted instances when isBulkSync is true. This should improve the performance of bulk BI sync, and avoid bugs.


Prior to this fix, some UserPersonACL records were not synchronized to the BI database and because of this, some UserPerson data could have been missing from Ad Hoc Reports or any dashboards/graphs driven by BI data.


An issue that caused object queues with unlimited concurrency to be starved by those that have concurrency has been resolved.


The session persistence mechanism has been improved to ensure that stale transactions in JBoss do not prevent session passivation.


Date type fields such as Birthdate and Last Update are now available when creating user-defined filters with mixed subject areas such as Contacts and Companies.


An issue where a Date Custom Field that was only specific to Contacts was incorrectly accessible as filter criteria for other entities such as Companies and Households has been resolved.


An issue where the integration log cleanup batch job was unable to process large volumes has been fixed.


Users no longer experience an issue that caused the Add Custom Field dialog to display with cut off text.


When attempting to edit a Stage in Opportunity Management, the Edit Opportunity Stage Template dialog was not opening. This has been resolved.


An issue that caused text not to display in Rich Text Editors in NexJ CRM workspaces has now been resolved. Prior to this release, when you entered text into a Rich Text Editor, for example, when composing a batch email or adding notes for a new document, the text would not be visible as you typed it in. This issue occurred only in Google Chrome.


 Index out of bounds errors during inbound Exchange synchronization have been resolved.


Prior to this release, resources from embedded repositories in NexJ Studio could not be edited.  This issue is resolved.


Due to an incorrect DST-related calculation, some scheduled triggers were set for one hour later than would have been appropriate.


An error experienced when sending a batch email with an encrypted PDF attachment has been resolved.


Previously, a BI sync error had been encountered. This has been resolved.


An issue with cookie parsing that caused unexpected errors in JasperReports when the Dynatrace User Experience Monitoring (UEM) feature was enabled has now been resolved.


Prior to this release, during inbound Exchange synchronization, a query created to filter out blocked items would be executed even when there was no data to be synchronized, causing slow performance. This issue is now resolved.


Upgrade steps for the ObjectQueueDatabase augment were missing. This has been corrected and the generated script now contains create table for messageXdai.


A database column with a null converter was triggering an exception if a query with that column linked in the WHERE clause was attempted. This issue has been resolved.


Prior to this release, if a cluster had multiple nodes on the same machine listening on the same port with different IP addresses and the clusterDiscoveryProtocol was set to TCP, the nexj.bind.address property would be ignored, resulting in a bind exception. This issue is now resolved.


The rendering of a URL-specified remote portlet in the NexJ Studio workspace editor has been changed to no longer display as an "unknown reference" with a red label.


An issue that slowed down the loading of the Edit Filter dialog when a large number of date type custom fields existed in the application has been resolved.


An issue that prevented NexJ Server from starting up when configured for HTTPS communication has been resolved.


Only users with approver privileges and read access to a work queue can approve business process steps assigned to that work queue.


Previously, when you cleared the Unique checkbox, you could not modify the selected Show in rule conditions checkbox. Now, the Show in rule conditions checkbox is automatically cleared as expected.


Category labels for entities in the Select Categories dialog on the Contacts workspace are correctly sorted by the group displayed in the Group column.


On the Work Schedules page in NexJ Admin Console, users no longer experience an extra Select option for Holidays in the menu that appears when they right-click.


Previously, an issue with the My Clients Recent Activities report threw an error when generating PDF output. This issue has now been resolved.


A fix has been made to prevent errors when deploying to a WebSphere environment that was previously upgraded from JDK 6 to JDK 7 or JDK 8.


The default max pool size for the FileStorage datasource connection has been increased to 1024 to mitigate system errors during operations involving a large number of files.


The integration logging feature has been enhanced to log an invalid response in addition to an exception. Previously, only an exception was being logged for this scenario.


Prior to this release, when a user incorporated a custom field type in an ad hoc report, and the custom field type was deleted or the entity type for that custom field type was deleted, the report broke and an error was generated. This issue is now resolved and the user is notified that by deleting the custom field type, the user may be removing the custom field type from any ad hoc reports that include it.

Note: Due to a known issue, the notification does not display when making changes to the contact types available in the Custom Fields tab on the Customize workspace.


Query limit errors are no longer experienced when navigating to a Contact or Household with large volumes of interactions.


Text now wraps correctly for schedule items in the Schedule workspace.


The NexJ logo is no longer missing in emailed conversations in Microsoft Outlook.


An issue that caused the object queue dispatcher to experience a performance degradation during unit test runs is resolved.


The default max pool size for FileConnection has been increased to mitigate system errors that occur when working with a large number of files simultaneously in the same transaction (e.g., performing Merge Contact).


An issue with the object queue engine that sometimes caused application shutdown requests to hang has been resolved.


Prior to this release, an issue occurred where threads in the object queue engine would indefinitely get blocked, causing local messages not to be processed and triggering a large number of Initializing Object Queue dispatcher messages in the application logs. This issue is now resolved.


An issue with the cross-site scripting (XSS) involved in label controls has been fixed.


An issue has been fixed where threads in the ObjectQueue engine would get into a state where they would wait indefinitely on a condition, causing the entire server to hang during shutdown while waiting for the hung threads to terminate.


A BI data source 8.9 upgrade error, where a single instance lookup was returning multiple items, has been resolved.


A file connection leak under certain error scenarios has been identified and fixed.



An issue has been resolved affecting schedule items. Previously, when you created a schedule item, the contact in the For field was removed if Completed was not selected in the Status drop-down. This issue no longer occurs.


Prior to this release, the token values in email and inbox notification messages were not translated in the French locale. This issue is now resolved.


The french locale is now supported in the rich text editor.


Prior to this release, when you clicked Add to open a drop-down using Google Chrome, the drop-down values occasionally remained visible when you navigated to another workspace or tab. This issue is now resolved.


Prior to this release, if you added new deals with legs on the Events workspace, the deals did not appear in the Event List report. This issue has now been resolved.


Prior to this release, when you attempted to delete a link to an Exchange server folder for a user, an error occurred if the folder had more than 4096 objects. This issue is now resolved.


Prior to this release, if you maximized the rich text editor in a dialog and collapsed the menu items, you may have observed background text at the dialog boundaries. This issue is now resolved.


Prior to this release, when you selected Streaming as the subscription type for an Exchange Server target, the NexJ URL and Notification fields, which are not applicable to this subscription type, displayed in the Exchange Server EWS details zone. This issue is now resolved.


An issue has been resolved affecting reminders. Previously, if you created reminders, the earliest reminders did not display before any remaining high volume reminders. In addition, the high-volume reminders did not maintain the sort order. This issue no longer occurs.


Prior to this release, when you docked a contact's profile, the Insights tab did not display. This issue is now resolved.


An issue has been fixed which prevented users with access to a large number of schedule items from accessing the Schedule tab in NexJ CRM.


Prior to this release, on the Opportunities workspace when you exported opportunities and selected Probability under Set List Columns, an error message displayed. This issue has now been resolved.


Prior to this release, when you added a product opportunity, the product name was not required and resulted in a product with an unspecified name. This issue is now resolved.


Prior to this release, the rich text editor was vulnerable to cross-site scripting. This issue is now resolved.


Prior to this release, uploading an attachment on the Document Manager workspace using Safari resulted in an error condition when rich text was enabled on the notes field. This issue is now resolved.


Prior to this release, when you clicked the email hyperlink in a contact's banner, the To field in the email template did not populate the email address. This issue is now resolved.


Prior to this release, when you added more than 4096 categories in the system and edited a rule criteria on the Customize workspace by selecting a field using the Field Picker dialog, an unexpected error occurred. This issue is now resolved.


An issue has been resolved affecting Microsoft Outlook synchronization when Microsoft Outlook was used to assign a task to another user. Previously, the second user had to add another task in Microsoft Outlook to view the assigned task in NexJ CRM.


JAAS Authentication is now supported to configure an application-specific Kerberos keytab file.


The loading behavior of the Field Picker dialog for editing contact-related rule criteria has been improved. In addition, a maximum of 3000 has been set for the number of custom fields that can have the Show Rule in Conditions flag set to true.


Prior to this release, if a rule existed with a category in the condition, and you cleared the Show in Rules Condition option for the category, the rule condition no longer applied. This applied when there are more than 4096 categories added to the system. This issue is now resolved.


The Save and Close and Save and Add Another buttons are now enabled after you complete required fields in dialogs.


The following integration logging issues have been resolved:

    • An issue where the top-level request was not persisted when an exception occurred at the inner level of nested service calls.
    • An issue that prevented persistence of a log entry due to an inconsistent transaction state.


Prior to this release when using JBoss, some object queue messages remained in processing state which reduced the efficiency of the object queue engine. This issue is now resolved.


An issue has been resolved that caused an unexpected error in NexJ CRM when the user performed an operation that attempted to access more than 4096 custom fields.


Prior to this release, a NexJ reporting framework mechanism to limit the number of pages generated by a JasperReport, was not functioning correctly and resulted in aggressive consumption of application server resources. This issue has now been resolved.


The rendering of the remote portlet in the Workspace editor has been changed. It no longer shows as “unknown reference” in a red label.



Prior to this release, when you used certain browsers, and if you copied and pasted formatted text from Microsoft Excel into a NexJ CRM field where the rich text editor was enabled, then the bold, italic, and underlined formatting was sometimes not retained. This issue is now resolved.


An issue that caused tablets running the iOS 10 operating system to render a blank screen after accessing an add or edit dialog has now been fixed.


Prior to this release, when you created a new meeting series of over 50 participants that recurs daily, the following behavior occurred:

    1. If you opened a schedule item of the series with a future date and changed the recurrence to weekdays, only a few schedule items were deleted.
    2. If you attempted to delete the meeting series, an error message displayed.

This issue has now been resolved.


Prior to this release, and when NexJ CRM was deployed on NexJ Server, attachments and images were silently removed from batch emails that were larger than 2 MB. This issue has now been resolved.


Prior to this release, running a report with an Event Meeting subject area and Detail Report report type could cause an unexpected error. This issue has now been resolved.


Prior to this release, and if you used Internet Explorer version 11, the Outlook window did not open on the first click of the contact's email link in the contact banner. This issue has now been resolved.


Prior to this release, if you added an invalid token to the Title field in a business process form on the Customize workspace, an error occurred when the business process was started on the Contacts workspace. Tokens which were valid when working with notifications might not have been valid when working with business processes. This issue has now been resolved.


Prior to this release, uploading images from a user's computer to include in the body of a batch email was not supported in Internet Explorer. This issue has now been resolved.


An error has been resolved which caused an unexpected error when the touch interval of a contact was set to None using the batch update option.


Prior to this release, when you used Google Chrome, and you provided notes using the Document Manager, the grey area for notes did not occupy the entire notes zone. This issue has now been resolved.


An issue has been corrected which could arise if you disabled the hierarchical access model, enabled Exchange Synchronization, and then set a task template's security to Group for two users. Under these circumstances, if one of the users modified a delegated task created by the other user using that template, the security of the task would erroneously switch to Private. This no longer occurs.


Prior to this release, and if you were using Microsoft Internet Explorer, you could not save copied text into a note for a contact by right-clicking and selecting Paste. This issue has now been resolved.


A Document Manager issue has been fixed, which affected the display of the Body field contents in the Batch Email dialog when using the Chrome browser. Previously, when creating a batch email for a single contact, the Body field could appear blank even though contents did, in fact, exist.


An issue has been corrected, which sometimes prevented edits to tasks with notes from being saved on the first attempt. Edits to tasks now save as expected.



A bug has been fixed which, in some cases, prevented a parent company's journal from displaying the activities of its child companies.


An issue that affected search performance by causing redundant SQL calls has been corrected.


A number of issues associated with popup dialog appearance and behavior have been resolved in this release.

ECRM-23189, ECRM-24127

An issue has been resolved which which caused unexpected results when exporting the list of merge fields on the Merge Codes tab of the Document Codes page in the NexJ Admin Console.


Prior to this release, if you created a custom field type with the same name as a seeded BI attribute, the SysUpgrade process failed and the server failed to start. This issue has been resolved.


After this change is applied, you must generate a BI bulk sync (snapshot) of custom fields.


An issue affecting NexJ CRM running with JDK 7 has been addressed so that the -Dhttps.protocols flag now properly allows you to configure any version of TLS.


After you have added a new contact and the contact's date of birth in the Contacts workspace, the expected date of birth now displays in the list of contacts.


Prior to this release, if two different BI Class Relationships were defined for the same attribute, then reseeding caused reports to display child attributes inconsistently. This issue has now been resolved.


As this change can potentially remove BI attributes that have been used in existing reports, you should do the following:

  1. Analyse existing reports (for example, test them in a lower environment) to determine which existing reports and corresponding attributes are affected
  2. Allow users to update or change the affected reports before running them


An issue has been resolved where an incorrect default Oracle driver was used during deployment and configuration.


The SLM workspace now refreshes as expected after adding notes to and completing a newly scheduled touch.


An issue has been fixed which caused the EditInteraction, AddTelcom, and EditTelcom portlets to open with their contents truncated in some test environments.


When editing or viewing the Body field of a batch email with Rich Text enabled, long text didn't wrap as expected and a horizontal scrollbar was unexpectedly displayed instead. This issue used to occur intermittently and only when using Internet Explorer. This release resolves known instances of this issue.


An issue in affecting outbound channels configured for SPNEGO Authentication, which were not configured to fall back to Basic Authentication, has been resolved.


An issue has been fixed where a held Exchange Synchronization lock could previously block other threads indefinitely.


In predefined reports which include activity details, line breaks within the text in the Notes field now display as expected.


The text in the Notes field for an activity now displays as expected when it contains a less then (<) character.


The description for a batch email activity no longer displays HTML markup code when it is included in the My Contacts' Recent Activities tab on the Home workspace or in the My Contacts' Recent Activities Report generated from that tab.


An issue which caused connection pool leaks under specific circumstances associated with user notifications has been resolved.


An issue has been fixed that, under specific circumstances, caused the object queue dispatcher to enter an infinite loop while accessing HashHolder objects in the Java API.


An issue has been resolved where, if an incorrect URL was used to access NexJ CRM on a tablet, then the application was not displayed and a performance issue occurred.



Sending an email from NexJ CRM using the Batch Email feature no longer causes an error if the email subject line is longer than 255 characters.


You can now deactivate a call script while the call script is being used.


When you generate an SLM Touches Report and set Group by to Tier and Sort by to Touch Status, the touches are sorted within the groups as expected.


In the Contacts workspace, if you click on a contact's email address in the banner, you may have received an unexpected error message under certain circumstances. This issue has been resolved.


An issue has been fixed that, in rare cases, prevented details from being saved when new schedule items were created.


All the options on the My Delegated Tasks tab on the Schedule workspace are are displayed as expected after you refresh the browser window.


An issue that caused nodes to drop out of their cluster has been fixed. This issue was specific to deployments using WebSphere Application Server.


A condition has been corrected, which previously had the potential to prevent some connections from being released at the end of a transaction.


An issue has been fixed which, in some cases, prevented users from successfully adding notes to existing documents.


A user interface issue has been fixed in which the advanced search fields overran the available window space. This issue occurred only on the Internet Explorer 11 browser.



When changing the template for an activity, attachments from the new template are now preserved.


The conversation and the notification beacons on the top tool bar now display the correct number of unread conversations and existing notifications, as expected.


Prior to this release, if you created a rule with an update field action that adds a category to a contact or household, the action did not always run successfully under certain circumstances. This issue has now been resolved.


When using Internet Explorer, you can now use the Contacts workspace to view a contact's opportunities and related products as expected.


On the Service Level Management page in NexJ Admin Console, you can now sort the contents of the Activity Templates tab by template type.


In the Call List workspace, if you click Add another script, you are now informed if no active scripts exist.


When you are configuring a business process or another flow, you can now connect page nodes in form flows, regardless of which browser you are using.


Users can now delete leads that have associated email records.


After you click the Select Coverage Group option on the Contacts workspace, you are informed if no coverage group has been configured.


Removing the Actual Close Date value from an opportunity no longer results in an unexpected error.


In the Lists tab of the Customize workspace, you can now see the View and Edit security values in the detail area on the right.


Newly created custom fields now appear as expected in the fields and filters selection window.


Prior to this release, unnecessary notification messages were being created for various locales. This used to slow down the loading of notifications in the notifications sidebar. This issue has been resolved. In the current release, only the required localized copies of notification messages are being created.


When using the Add option in the top tool bar, the profile of a newly created contact is now always displayed by default.


Users no longer encounter an unexpected error when adding and removing users from the Assign To field of a task.


Prior to this release, on NexJ Server installations, custom configuration and properties files were overwritten on deployment. This issue is resolved in the current release.


Prior to this release, when deploying using both a template environment file and a properties file, any changes made to the properties file without modifying the environment file were not applied. This issue has been resolved.


Process logs are now created for monthly Service Level Management batch jobs as expected.


A problem with a third-party library that affected NexJ CRM when running on IBM WebSphere Application Server and using virtual hosts has been resolved.


On NexJ Server installations, redundant previous models are now removed when deploying updated model versions, as expected.


Batch processing has been improved to decrease contention and increase throughput.


Users can now successfully update the Default Country preference in the User Preferences.


When a user has a very large number of notifications, the loading time for the notifications has been improved.


Some compatibility issues with Google Chrome version 58 have been resolved.


An issue with SPNEGO silent sign-on that was experienced when signing on from another domain has been resolved.


On the Schedule workspace, if you select how a calendar should be displayed (day, week, workweek, or month), your selection will be remembered the next time you log in.


An issue that could cause object queues to hang when processing large data loads has been fixed.


When the system is using the 24 hour clock, the time field values in the Schedule Item dialog are displayed in the HH:MM format, as expected.


An issue with batch email which used to cause the java.lang.NullPointerException error has been resolved.


If you modify a touch type, you will no longer encounter an unexpected error if there are touches of that type with due dates in the past.


If you attempt to send a notification message that is over 255 characters long (or becomes over 255 long when tokens are resolved), the message will be truncated at 255 characters and successfully sent.


When a schedule item reminder dialog is open, you can now continue to interact with the NexJ CRM workspace below without closing the dialog.


Some potential performance issues with transaction recovery have been resolved.


A slow memory leak due to transaction timeout tasks not being cleaned up properly when committing or rolling back transactions has been resolved.


Duplicate notifications are no longer sent to users when they create a task for one or more contacts using the Actions button on top of the contacts list in the Contacts workspace. This used to occur under certain configurations of notification rules for tasks.


An issue which caused an increased risk of a potential deadlock between cluster manager and stats manager has been resolved.


Resolved an issue in which, under some circumstances, user sessions could grow to larger than normal sizes, resulting in poor performance.


An issue leading to long running exclusive locks on the database and abnormally high CPU usage during inbound synchronization of recurring events has been corrected.



On the Contacts workspace, when you expand the Contact Details area to the left, the Contact List area is narrowed and displays as expected. However, if you expand the Contact Details area sufficiently far to the left, the display of the Contact List area may still be affected.

ECRM-20707, ECRM-20880, ECRM-21514

This release contains performance optimizations related to object queues and two-phase transaction commits.


The list of available currencies in workspaces such as the Opportunities workspace has been expanded to properly align with ISO standards.


Resolved an issue that caused some Italian phone numbers to format incorrectly.ECRM-20887With HAM security enabled, you can enable synchronizing private meetings with multiple participants from Microsoft Outlook to NexJ CRM. This functionality is enabled by setting the Enable Inbound Sync for private meetings with multiple participants user option in NexJ Admin Console.


User can now successfully start business processes that do not have explicit start dates.


With HAM security enabled, you can now select the Restrict access to users in the Assign To option in schedule items and tasks to synchronize those items as private from NexJ CRM to Microsoft Outlook. You can also synchronize schedule items and tasks from Outlook to NexJ CRM with restricted access. Previously, this option made schedule items or tasks private only in NexJ CRM.


An issue in NexJ Studio, which caused a null-pointer exception when opening some editors or the NexJ Studio perspective, has been resolved.



Hover text information on the Product Opportunity Pipeline chart of the Pipeline dashboard no longer truncates when using Internet Explorer.


The Tier & Rank tab no longer appears when you edit a fund or department


When updating an opportunity coverage team, removing a user from the team and then immediately removing an opportunity coverage group now works as expected.


It is no longer possible to specify an end time that occurs before the start time when editing an activity and using the Related tab to add a follow-up action.


Using the multi-select action in the Contact workspace to set or update the service levels of multiple contacts at the same time no longer risks resetting the service level settings for contacts that are already at the selected service level.