Release notes - i2 Analyze 4.4.1

The following system requirements should be used to ensure that the setup you are running is fully supported. Ensure that existing deployments are upgraded to currently supported versions of all the software required.

Customers who have entitlement can request copies of i2 products.

For more information, see Where can I download the latest i2 products?

The following issues are currently reported:

Web clients

Table 1. Table 1. Web clients

Problem	Description
Importing entity types that do not have source reference schema fragments set up can cause the import to fail	If you have made use of source reference schema fragments to have different schemas for individual items types or groups of item types, it is not advisable to add source references to imported records.
Only 500,000 records can be added to a i2 Notebook chart in a single operation	Charting more than 500,000 records results in the first 500,000 records being added to the i2 Notebook chart, and no notification is provided that some of the items were not charted.
Keyboard navigation does not work within visualizations	Attempting to navigate around records that contain visualizations, the visualization cannot be accessed using the tab key. If the tab key is pressed when an item in the visualization is selected, focus is removed from the visualization.
Blocks of text are clipped when printing in Firefox	If large amounts of text (more than will fit on a printed page) are entered into a record property, note, or source reference, the text will be clipped if the record is printed.
Using reserved terms in the highlight-queries-configuration.xml file can cause issues when results are expanded in the Show More view	Reserved terms should not be used as the id value in the highlight-queries-configuration.xml for example: <highlightQuery title="Suspects"> <path> <segments> <segment> <Listed_In-I /> <Person-I> <exportFields> <propertyField propertyType="last_name-P" aggregatingFunction="MAX" id="term" /> </exportFields> </Person-I> </segment> </segments> </path> <sortBy> <field id="term" order="ASC" /> </sortBy> </highlightQuery> If reserved terms are added to the id value, the system will try and interpret them as system specific commands causing unexpected behavior. The following list of reserved terms should not be used as values for id in the highlight-queries-configuration.xml file: version, id, full_text, full_text_reversed, item_type_id, link_from_id, link_to_id, is_link, link_direction, merged_record_info, record_version, data_source_created, data_source_modified, data_source_seen, data_source_name, data_store_created, data_store_modified, data_store_seen, record_first_uploaded_by, record_last_uploaded_by, record_id, text_facet, source_references_id, source_references_ref_type, source_references_source_name, source_references_location,source_references_image, source_references_description, source_references_is_modifiable

Information Store

Table 2. Table 2. Information Store

Problem	Description
Some non-English characters are replaced in the Information Store table and column names	This replacement of characters can change the names that you expect to see, when you are completing operations such as ingesting data. For example, the German language esszett character (written 'ß') is replaced by an underscore in Information Store table and column names.
Information Store does not support Read Cloaked	The security classification Read Cloaked is not supported in the Information Store.

i2 Analyze services

Table 3. Table 3. i2 Analyze - services

Problem	Description
Visual Query timeout for Geospatial searches of large datasets	Depending on the scale and geographic distribution of geospatial data in the system, Visual Query searches can return results slowly, or even timeout. To improve the performance of Visual Queries that use geospatial information, you can create geospatial indexes manually.
The message Enter fewer characters is displayed in the Record Inspector when a user enters data into a single-line string	The number of characters is less than the limit set in the i2 Analyze schema but contains special characters (for example 'ä'). When data is used in the client, some special characters use more bytes than standard characters. This can cause a validation error because the size of the string is too long.
Messages when Solr starts or stops	If you are using third-party tools that contain a find executable, you might see messages that indicate files cannot be found: find: unable to access "TCP ": The system cannot find the file specified. find: unable to access ":0 ": The system cannot find the file specified. find: unable to access ":8983 ": The system cannot find the file specified. These messages might indicate that the system variable that defines the environment path has the path to the third-party tool before the system files. Verify that the Path= system variable contains paths that point to the third-party command line tools added after the paths that point to the system folders.
Searches can stop running after i2 Analyze is restarted	If the WebSphere® Liberty Application Server is restarted while searches are running, the search might time out. To prevent this issue, ensure that the HTTP server is restarted when you restart the Application Server.