Known Issues and Notes
This chapter describes issues that InterSystems is aware of in InterSystems IRIS for Health 2021.1 and notes related to this version of the product. These issues will be addressed in future releases.
Issue Using MultiValue Feature
InterSystems has identified some issues with InterSystems IRIS for Health MultiValue. We are investigating those and will fix them in a future release. If you are upgrading a MultiValue based application from Caché or Ensemble to InterSystems IRIS for Health, you should thoroughly test your application on InterSystems IRIS for Health before upgrading a production system. If you encounter any issues or want more information about the issues we have encountered, contact your sales engineer or the InterSystems Worldwide Response Center.
Management Portal Web Applications May Time Out Despite User Activity
In InterSystems IRIS for Health 2018.1 and later, an automatic logout feature was implemented and enabled by default. When the feature is enabled and a user is inactive on a Management Portal web application for longer than the Session Timeout value for the web application, then the user is logged out. However, InterSystems IRIS for Health only registers actions that result in a call to the server as activity. Consequently, a user may be modifying a Management Portal page immediately before an automatic logout and lose any unsaved changes. For example, if a user is editing a business process, but has not clicked Save for longer than Session Timeout threshold, then the user's session expires and any unsaved changes are discarded. After an automatic logout, the login page appears or the current page is refreshed.
You can take several steps to prevent users from losing work:
Remind users to save their work on a regular basis.
Extend the Session Timeout value for web applications where users are performing time-intensive configuration tasks such as modifying data transformations. The default Session Timeout value is 15 minutes.
Disable automatic logouts for the Interoperability pages in the Management Portal by modifying the ^EnsPortal global as follows:
set ^EnsPortal("DisableInactivityTimeout","Portal") = 1
InterSystems recommends that you consider the possible security implications before you make any changes.
For more information, see Automatic Logout Behavior in the Management Portal.
Multiple Files Created from a Single X12 Document
When an interoperability production uses the default X12 business operation to write to a file, a single X12 document can result in multiple files. In this scenario, an extra file is created for each Functional Group in the original X12 batch document. This error occurs with certain File Name options when the Auto Batch Parent Segs setting is enabled.
DTL Creates Empty Target Segment
A DTL includes an option called Ignore missing source segments and properties. When enabled, errors caused by a missing source segment are suppressed. However, in this release, an empty segment is still created in the target when the DTL encounters a missing source segment.