Kofax MarkView 10.4.0 Fix Pack 4
Build date: July 29, 2024
© 2024 Tungsten Automation. All rights reserved.
Use is subject to license terms.
Introduction
Install Kofax MarkView 10.4.0.4 to resolve the issues listed below.
Note: Install Kofax MarkView 10.4.0.4 only after a full installation of Kofax MarkView 10.4.0 or on top of any previously installed 10.4.0 fix packs.
For a full product installation, see the Kofax MarkView Installation Guide for instructions.
Issues resolved in this fix pack
| ID | Issue | Solution |
|---|---|---|
| 2122329 | Reworked issue # 2097844: After canceling the SSI invoice and submitting the new invoice with the same number, an error appeared. | Added a new request to the ap_invoices_interface table. |
| 2115522 | The size of the Supplier Sites field was too small for some columns and caused errors. | Increased field size on MarkView side to conform to column length in Oracle. |
| 2098605 | Request to make the Blue Sticky Note window resizable. | Added ability to increase the size of the Blue Sticky Note window. |
Issues resolved in previous fix packs
Fix Pack 3
| ID | Issue | Solution |
|---|---|---|
| 2100630 | Data Export failed in Production because the string length was exceeded in MVOA_USER_INFO.GETUSERINFO (ORA-06502). |
The string length is no longer exceeded, and Data Export now works properly. |
| 2097844 | After canceling the SSI invoice and submitting the new invoice with the same number, an error appeared. |
A new request was added. |
| 2097168 | Value "NU" (Nunavut) was missing in Province LOV in SSI Supplier Site screen. | Added new value in Province LOV in SSI Supplier Site screen (Nunavut). |
| 2096488 | An email contained a link with HTML tags. |
HTML tags were replaced with line breaks. |
| 2086895 | When the Automatically Add distribution check box was selected, auto-adding distribution did not copy the DFF attribute column value from line level to distribution level. | Added a possibility to select whether distributions should copy values from lines. To automatically fill in Descriptive Flexfield values from line level to distribution level when the Automatically Add distribution setting is selected in Viewer, follow these steps.
|
| 2072378 | The Return to Supplier action removed leading and trailing lines in the comment text. | Added the required parameters. |
| 2071863 | AUSS sync failed with an error (ORA-02291). | A filter to an SQL query which fetches responsibilities was added. |
| 2070220 | When running Email from Viewer or Return to Supplier, the text contained <br> tags. | New lines are no longer replaced with <br> tags. |
| 2068688 | In MarkView -> Web Inquiry -> AP Invoices, the search option was case-sensitive. | Made the search option case-insensitive. |
| 2054659 | It was not possible to use the Calendar to set an alternate user assignment when thelocale was not set to US and the day was greater than 12. |
The Date Parser was updated. |
| 1994889 | Users other than Admin could not access the authentication configuration page. | All users are able now to access the authentication configuration page. |
| 1990200 | In Web Inquiry, when selecting dates from the calendar, the default date format was used instead of customized. | The Date Parser was updated. If there are umlauts in the month names, or if the month name differs from the English locale (US), the calendar is now displayed correctly. |
| 1972481 | AP Invoice Follow-Up barcode generation resulted in an error. | The SQL query was updated. |
Fix Pack 2
| ID | Issue | Solution |
|---|---|---|
| 2039462 | It was impossible to create an alternate user assignment if the user's locale was not set to US. |
Updated the MVT_Alternate_User_Assignment database package body to make it possible to create alternate user assignments if the locale of the user is something other than US. |
| 2000764 | Could not print or email documents not associated with the MarkView work item. | Fixed several NPEs to make printing or emailing documents not associated with the MarkView work item possible. |
| 1979917 | After attaching a document to a PO and closing the MarkView window, the 500 error appeared. | Added the additional values to the "Action" request input parameter to make attaching documents to POs and closing the MarkView window work without errors. |
| 1968688 | When clicking "Get Next" on the Oracle EBS Create Supplier page, the "Request Denied" message appeared. | Clicking "Get Next" now works properly using different browsers. |
| 1965208 | In Administration, after clicking "Submit" on the Alternate User Assignment page or selecting "Authentication Configuration", the 500 error appeared. | Improved date validation for custom date format settings. Clicking "Submit" or selecting "Authentication Configuration" now works without producing any errors. |
| 1964000 | It was impossible to email from MarkView Viewer. | Added the possibility to connect to mail server without entering login and password. The email option now works correctly. |
| 1959643 | F5 load balancer server request response returned the wrong data type in the Content-Type header causing missing menus. |
Added the "X-Content-Type-Options" security header to server response and set the appropriate "Content-type" header value. Data types and all the menus are now displayed correctly. |
| 1938267 | Export requests (Print or Email) from Viewer failed using https with the following exception: Received fatal alert: handshake_failure javax.net.ssl.SSLHandshakeException. |
Now sending emails is done directly through the java code. |
Fix Pack 1
| ID | Issue | Solution |
|---|---|---|
| 1933918 | On Alternate User Assignment page and Support tools, when entering the lowercase User ID or User ID that does not exist in the system, a 500 error appeared. | Changed the display of an error when a user enters a User ID that does not exist in the system. |
| 1929415 | Request to apply additional security enhancements. | The commons-net library was upgraded to enhance security. |
| 1912422 | Request to apply additional security enhancements. | Verification of incoming HTTP request and cookies attribute were added to enhance security. |
| 1908994 | When using the latest version of Google Chrome and Microsoft Edge, the Viewer did not always show Quick Info. | Opening, reloading, refreshing, and redirecting to the Quick Info section in different browsers now works correctly. |
| 1908993 | In mv_document table and other related MarkView tables, document_id values were too large for the column. | Changed the type for some fields from NUMBER(8) to NUMBER(11). |
| 1893157 | In DEFAULT_EXPORT_QUEUE - Queue Assignments - SMTP User, it was impossible to set SMTP user name if it was more than 30 characters. | SMTP User name in DEFAULT_EXPORT_QUEUE - Queue assignments was extended to 160 characters. |
| 1883668 | Request to add the HTTP response header. | The HTTP response header was added. |
| 1883665 | Request to add an attribute to the cookie. | The required attribute to the cookie was added. |
| 1883272 | Request to apply additional security enhancements. | The xercesImpl library was upgraded to enhance security. |
| 1883271 | Request to apply additional security enhancements. | The xalan library was upgraded to enhance security. |
| 1825890 | After saving the layout by the administrator, changes were not saved. | After applying the fix, changes are saved properly. |
| 1800812 | Request to add OrgContext/Apps Initialization to MVOA_FND_Util.GetKeyFlexConcSegments. |
OrgContext/Apps Initialization was added to MVOA_FND_Util.GetKeyFlexConcSegments. |
| 1550439 | In the Accounting tool, fields could not be rearranged for all users. | The method to rearrange the fields in the Accounting tool for all users was added to Administrator within the Manage layout settings feature. |
Applies to
This fix pack is based on Kofax MarkView for Accounts Payable 10.4.0.
Only apply this fix pack to the MarkView 10.4.0 application server; do not run the
fix pack installer on a MarkView Oracle Objects installation.
Verify that the version of all installed MarkView components (such as Self-Service Invoices, Document Library, Expenses) is 10.4.0.
For information about system requirements, see the Kofax MarkView 10.4.0 Planning Guide and the Technical Specifications document on the Kofax MarkView Product Documentation website.
Applying this fix pack multiple times on the same system causes no harm. Also, fix packs are cumulative for a release, so you do not need to install previous 10.4.0 fix packs before applying this latest fix pack.
This fix pack includes files that are staged on the application server and that require manual steps, which are included in the sections that follow.
Files included
This fix pack includes the following files:
| File name | Version |
|---|---|
| KofaxMarkView-10.4.0.4.zip | 10.4.0.4 |
| ReadMe-KofaxMarkView-10.4.0.4.htm | N/A |
Install this fix pack
Use the following procedures to install the fix pack.
MarkView Application Server installation (includes Database Components)
Only apply this fix pack to the MarkView 10.4.0 application server.
Before starting the following procedure, read this entire ReadMe file.
Silent installation preparation
If you used the silent installation method to install MarkView 10.4.0 and you plan to use the same method to install the fix pack, perform the following actions.
Go to the distribution > conf folder.
Open the preliminary_interview.properties file.
Complete the properties file information, but leave the SelectedProducts.selected_products parameter blank.
Run the generateInterviewTemplate script to create or update the installer_interview.properties file.
Open the installer_interview.properties file.
Complete the properties file information according to the Kofax MarkView 10.4.0 Upgrade Guide.
Apply the fix
Log in to the application server as the user who installed MarkView 10.4.0.
Ensure that the environment variables required for installing MarkView 10.4.0 are defined.
See the Kofax MarkView 10.4.0 Upgrade Guide for information about setting environment variables and other settings required to run the installer.Locate the base MarkView directory where MarkView is installed. Use this path name when prompted for the "Install Directory" during installation.
The base MarkView install directory includes the following files:- target_registry.properties
- thirdparty.txt
Extract the KofaxMarkView-10.4.0.4.zip file into a new directory on the application server where MarkView 10.4.0 is installed.
Verify that the system is quiet to ensure that the data remains synchronized.
Log in to an SQL*Plus command window as the MarkView schema user.
Stop the currently running database user jobs by executing the breakDBJobs.sql script, which is included in the following MarkView 10.4.0 installation distribution directory:
<MARKVIEW-10.4.0-INSTALLER>/modules/installer-dist-10.4.0/installer-db
where <MARKVIEW-10.4.0-INSTALLER> is the base directory of the MarkView 10.4.0 installation distribution.To run the installer, invoke the installation script in the bin directory of the fix pack distribution (install.bat|sh or install_silent.bat|sh).
See the Kofax MarkView 10.4.0 Upgrade Guide for information on running the installer.
The installer shows a list of all 10.4.0 fixes in the fix pack.Provide answers to any unspecified values in the installer windows.
Use values that match those provided during version 10.4.0 installation.
(If available, use the installation worksheet that was completed for MarkView 10.4.0.)
Note: Install the fix pack in the same target directory specified for the MarkView 10.4.0 installation.
If you run the installer and see pre-populated information for the wrong environment, such as production URLs when running against a non-production environment, update the fields manually in the installation window.
If you install this fix pack on WildFly, do one of the following:
For standalone mode:
In the Enter App Server information for MarkView applications, leave the Domain field blank.For domain mode:
In the Enter App Server information for MarkView applications, enter your domain name in the Domain field.
When the installation is completed, follow any on-screen instructions that appear in the installation summary window.
Restart the application server.
To ensure that all database objects are compiled successfully, follow the instructions in the "Check for Invalid Packages" section of Chapter 5 of the Kofax MarkView 10.4 Upgrade Guide.
Log in to an SQL*Plus command window as the MarkView schema user.
Start database user jobs by executing the startDBJobs.sql script found in the following MarkView 10.4.0 installation distribution directory:
<MARKVIEW-10.4.0-INSTALLER>/modules/installer-dist-10.4.0/installer-db
where <MARKVIEW-10.4.0-INSTALLER> is the base directory of the MarkView 10.4.0 installation distribution.
In a clustered environment, point to one server, then propagate to other nodes in the cluster using the appropriate process for your application server.