Technology

This section describes known issues that pertain to the application framework.

AFL-3915

If you upgraded from a previous release to NexJ CRM 9.2, users may receive a file size limit error when adding notes or uploading documents beyond a certain size.

Workaround:
Increase the Maximum HTTP Request Size environment file property as needed, for example, by 30%, to allow for equivalent uploads in NexJ CRM 9.2.

AFL-4506

Cross-domain push connections are not supported in the Mozilla Firefox browser.

AFL-4731

When you create or edit an activity, and right-click on the For, Assign To, or Add Attachment fields, the browser native context menu does not display.

AFL-4818

Notifications manually triggered through the business model do not always clear and can be fired cumulatively.

AFL-5211

If you are using an Apple iPad with Apple iOS 13, and you open the New Contact dialog to add a contact, and in the Date of Birth field, tap the calendar icon

to open the calendar, and navigate between months, or select a year or date, the keyboard erroneously opens after each action.

AFL-5490

When the BatchViewObjectBatchJob runs and there are no records to process, its process status reports a false status of Failed.

CDM-4138

If you are using Studio to build and test reporting functionality, and you update the reporting host URL from a localhost address to a fully-qualified HTTP url, then reseeding the environment may not correctly update your databases.

Workaround: Continue to use a localhost address during your development cycle.

ECRM-29146

When you run the pushrd.sh script to start the push redirector in a Linux environment that is running Java 8 or higher, a warning message is generated that states that an illegal reflective access operation has occurred.

ECRM-29324

If you create an augment from a given class, and then apply a facet from that class to the augment, the facet may not always be recognized. If this happens you will receive an unrecognized facet error when you try to run the model.

ECRM-29650

On first server load of a Classic portlet, and if it uses POST data, the context parameters will be lost due to the time zone detection refresh.

Workaround:
Use GET on the first load of Classic portlets where context is required, or put the values into the URL of the POST.

ECRM-29964

The JVM property "com.ibm.jsse2.overrideDefaultTLS" must be set to TRUE in order for the inform:ArticleSearch HTTPConnection channel to work in a Websphere-based environment.

More information can be found here: https://www.ibm.com/support/knowledgecenter/SSYKE2_8.0.0/com.ibm.java.security.component.80.doc/security-component/jsse2Docs/matchsslcontext_tls.html#matchsslcontext_tls

ECRM-30167

The FileCleanupBatchJob runs daily, deleting File Persisted objects. However, in a clustered environment, it only deletes entries on the currently active node.

ECRM-31107

Documentation from message definitions may not be exported to corresponding Avro schemas generated using messages.

Workaround:
To trigger the documentation to be generated in your messages, set meta.documentation="true" in your environment file, which allows the documentation to be picked up by the schema generation.

ECRM-31502

When the Prioritize Folder Mixins option is selected in NexJ Studio, the JARs are repeatedly retrieved, and will override the folder mixin when the server is launched.

Workaround:
Preferably, and while the preference is set, skip retrieving the JAR or if that will introduce new bugs, then still prioritize the folder mixin even if both a JAR and a folder can match the requirements while the preference is set.

ECRM-31687

When you have unchecked the Prioritize Folder Mixins option in the NexJ Studio Launch Setting preferences, the open folders are still being used locally.