Resolved Issues: Ennov InSight 7.1
The following issues reported to Technical Support have been resolved. Issues are listed in descending order by their tracking numbers. Customer incident numbers that were recorded when the issues were reported are included in brackets [#####] following the tracking number.
If an issue was resolved in a previously released certified hotfix (CHF), that CHF build number is included.
Common
| Issue | CHF/Hotfix Build | Description |
|---|---|---|
| 26808;
[INC0069223] |
N/A | When a user is trying to assign a D2 document, an invalid reference error is displayed. This issue is resolved.
You can assign a D2 document successfully without any error. |
| 26790;
[CS0401640, INC0058360] |
6.2.0.6.0032 | When a Veeva document with overlay was assigned to an assembly and the Prepare to Publish query was run with the Generate Missing Renditions and Extractions option selected, the extract document data request failed to process correctly. This issue is resolved. Now, the extraction request is sent only if document with overlay is updated since last data retrieval. |
| 26789;
[INC0061160] |
6.2.0.6.0032 | In some cases, in FPP for Package Set Registrations with
Yes value for
XEVMPD Submission Required?
, after processing the XEVMPD Acknowledgement, the
XEVMPD Submission Required?
field did not change its value to
No. This issue is resolved.
After processing the XEVMPD Acknowledgement, the XEVMPD Submission Required? field shows as No in some cases. After the update of XEVMPD related fields in FPP, XEVMPD Submission Required? field value previously set up to No shows as Yes. |
| 26778;
[INC0057113] |
6.2.0.6.0032 | When creating a new Veeva document and assigning it to Assembly, Veeva Vault Connector failed to receive the latest document version. Veeva Vault received the latest version only when the DMS cache was refreshed every time. This issue is resolved.
If Properties of the Veeva document were changed, DMS synchronization of this document, happened within cache timeout, resulted out of date properties. The issue is resolved The DMS cache refreshes automatically and Veeva Vault receives the latest version of the document. |
| 26774 | N/A | Some users experienced
ORA-06512 error and users were unable to use the system. This issue is resolved.
Database configuration is updated to prevent this issue in future. |
Publishing
| Issue | CHF/Hotfix Build | Description |
|---|---|---|
| 26784;
[INC0061598] |
6.2.0.6.0032 | When nodes were updated in a
Working view through
Mass Update Properties, the changes were not applied to the
Sequence and
Publishing views. This issue is resolved.
After updating nodes in a Working view through Mass Update Properties, changes appear in the Sequence and Publishing views. |
| 26705;
[INC0046004] |
6.2.0.7.0006 | Performance issue related to the Synchronize with the Submitted View job resulted in a timeout. Changes have been made to the synchronization mechanism and now the job request passes with efficiency. |
| 26692 | 6.2.0.7.0006 | A mismatch between a Publishing Settings database sequence used by the code and the database sequence used in the corresponding database function caused the following error: ORA-00001 : unique constraint (ODS.PKSLIP_SETTING) violated. This issue is resolved. The database function is updated to use the same database sequence the code uses and ensuring that the sequence values are unique going forward. |
| 26687;
[INC0033088, INC0030024] |
6.2.0.6.0009 | The variables specified in the Default Values section of the Publishing Settings Library failed to resolve in the submission output if an assembly root was not selected during publishing. However, the variables set in places such as leaf properties resolved successfully. This issue is resolved. Now, the variables specified in the Default Values section of the Publishing Settings Library are resolved. |
Rendering
| Issue | CHF/Hotfix Build | Description |
|---|---|---|
| VCS-5014 | 5.0.1.1 | The format of the Ennov InSight Rendering log files was changed to comply with Azure Log Analytics requirements. This change has no impact on end user experience or system functionality. |
| VCS-5013 | 5.0.1.1 | SmartLinks in documents rendered by Documentum Content Transformation Services (CTS) were not present in the published output. This issue is resolved for Microsoft Office documents rendered by the CTS Doc6 plugin. |