Clarification of Behavior: Ennov InSight 7.3
This section provides an explanation of functionality that may be interpreted as an issue, but is in fact working as designed.
Ennov InSight : Common
| Issue | Affected Area | Description |
| DE32324 | N/A |
Veeva SSO does not work some times if the Ennov InSight user credentials does not match the Federated User for Veeva SSO. Workaround: Make multiple Microsoft accounts on the browser. You will be prompted to select the appropriate account to log on. |
| N/A | N/A |
After migrating to Ennov InSight 7.3, the following user settings are reset to default for the migrated users. — Assembly tree width — Product Details Set tree width — Home page side panels width and show/hide condition — Home page widgets show/hide condition — Columns width — Columns order — Columns sort order — Columns show/hide condition — DMS Browse window size |
| N/A | N/A | After migrating to Ennov InSight 7.3, Public or Private queries saved in the Ennov InSight 6.2 query list will not be available in the Ennov InSight 7.3 query list for the migrated and newly added users. |
| N/A | Assembly | Performing any action from Ennov InSight 6.2 CHF 1 against a Veeva repository on limited release version 18R2.2 will result in an exception caused by an unexpected error response from Veeva Vault. If you experience this issue, please contact Veeva Support. |
| Issue | Affected Area | Description |
| N/A | N/A | If you are using network security products to scan your local intranet hosts for vulnerabilities, be aware that these products have a specific scan used against a JBoss server at TCP/IP port AJP/8009. Scanning the Ennov InSight server with a network security product will cause an outage, requiring a restart. To avoid issues caused by network security scanning products, see Firewall Rule for TCP_IP Port AJP_8009 in the Ennov InSight Installation Guide. |
| DE30854 |
Entity History Query |
If selected ATC is removed, the Entity History Query > Registered ATC Audit Details query shows new row with D (Delete) action instead of both D and I (Insert). If multiple ATCs are removed, rows with D action as many as the number of ATCs removed are shown in the query. |
| 26740 | N/A | With the value for user.device.limit set to 1 in the insight.var file, when a user is logged on to InSight on device one, logging on to a second device terminates the InSight session on device one. However, refreshing the page on device one displays the InSight Home page. This is because of the Azure SSO functionality. |
| 26727 | N/A | When a user is not included in the mapping list during the migration process, attempting to reassociate the user with a group can cause an “Invalid Reference” error. The error indicates the user profile is corrupted and Azure AD does not recognize it for synchronization. |
|
26518; [INC0028282, CS0199557] |
N/A | Selecting documents in the Browse Documents > Assign Document window sends the Browse Documents window to the background (behind the Assembly window), making a user activate the window for subsequent document assignment. |
| 26418 | N/A | Duplicating Browser Tabs: Prior to Ennov InSight 6.2 CHF 3, duplicating a browser tab of an active Ennov InSight session DID NOT require login for the duplicated session created on the new tab. From Ennov InSight 6.2 CHF 3 onward, duplicating a browser tab of an active Ennov InSight session WILL require login for the duplicated session created on the new tab. |
Ennov InSight Publisher
| Issue | Affected Area | Description |
| N/A |
Assembly, Technical Administration |
When an assembly is created from an assembly file, the locations included in the assembly file that do not match the repositories in Ennov InSight Technical Administration will not be saved. |
| DE32135 | Assembly | After creating an EU 3.0.3 working assembly using Create eCTD wizard, when the eu-3-0-1 XML Definition is replaced with eu-3-1, the Submission Unit Type field cleared on the envelope\s attributes. |
| DE31682 | Assembly | When publishing, a file name or a server name or, a file path should not exceed the Windows file system limit, which is 260 characters. |
| Note: It is highly recommended to consider the file name length from DMS as long file names can cause issues. See Special Characters. | ||
| DE26775 |
Assembly,DMS Browse, Technical Administration |
The attempt to log in to Veeva from DMS Browse using SSO profile results in an error message. |
| DE30272 | Assembly | It is not possible to download output file for published reference leaf using the View File option. |
| DE28529 |
Data Administration (SPOR Master List) |
For Ennov InSight 7.2, after the migrated build is installed, the values for the new SPOR Master Lists tables may not appear. This was determined to be a data setup error. This issue can be resolved by starting the synchronization process from the beginning. The architecture requires that the database and blob data are in sync and replacing a database or blob from another environment will cause issues. |
| Issue | Affected Area | Description |
| DE28147 | Global Project Plan wizard | Using the Global Project Plan wizard, if multiple applications are created with the Create New Event for Existing CTA and/or IND Application(s) option and then a sequence is created, the same Sequence Standard Type value will be applied to all the created sequences. If there is at least one eCTD 4.0 sequence, under affected applications, the eCTD 4.0 will be the only available option. |
| DE27968 | Assembly | When the length of the output path exceeds the limit allowed by the operating system, publishing fails. This issue can be resolved by shortening the folder or leaf output names in assembly. |