Kofax MarkView 10.1.0 Fix Pack 7

Build Date: January 10, 2023

Introduction

You can install Kofax MarkView 10.1.0.7 to resolve the issues listed below.

Note: Install Kofax MarkView 10.1.0.7 only after a full installation of Kofax MarkView 10.1.0 or on top of any previously installed 10.1.0 fix packs.

For a full product installation, see the Kofax MarkView Installation Guide.

List of Issues Resolved in This Fix Pack

1912424: Verification of incoming HTTP request and cookies attribute added to improve security

1882182: Parameter checking added to improve security

1858278: In mv_document table and other related MarkView tables, document_id values were too large for the column

1842465: Web application security improved

1842455: SQL security improved

1840918: When using the latest version of Google Chrome and Microsoft Edge, the Viewer did not always show Quick Info

List of Issues Resolved in Previous Fix Packs

Issues Resolved in Fix Pack 6

1775785: Viewer did not display all layers of certain PDF files ingested via Import Server

1734088: After applying Oracle patch for Log4j vulnerability, MarkView is negatively impacting core Oracle functionality

1728850: AUSS experiencing major performance issues with synchronization

1674203: Connector Tax Code / Tax Amount not being parsed as expected - increase the connector limit for Tax Code from 15 to 30 bytes

1633904: 500 Internal Server error trying to update or create user record (Also typo 'comor' is being added to url in referrer)

1564108: Encountering an issue when coding an invoice with NON billable project coding

Issues Resolved in Fix Pack 5

1604417: Security Assessment - Cross Site Request Forgery (527036)

1604415: Security Assessment - Privilege Escalation (527133, 527134)

1604409: Security Assessment - Privilege Escalation - Prev Entered Working Folder (527132)

1604403: Security Assessment - Cross-Site Scripting (XSS): Persistent (527049)

1589959: Markup Viewer Tool/Action Icons not displayed in the Viewer

1587064: JBoss failing to start deployments after 10.1.0.3 is applied in SAML environment

1572964: Double copying occurs when multiple lines are selected using only the left mouse button held down

1546002: "MarkView Server Error" message appears during 'Reassign Document' action if Contact does not exist

Issues Resolved in Fix Pack 4

1587035: MarkView Workflow Exception: The page needed to be refreshed because user updated the page; error caused by mv_document.creation_timestamp updated to batch creation local time

1585653: End users who click in Exp Type field without first entering a value in Project field caused a blind query

1584333: Import Server failed to import PDFs with embedded images or signed with Docusign

1582105: Enhancement Request to add TLS 1.2 support for Mail Gateway

1580968: Auto escalations did not work due to error ORA-01722: invalid number

1566613: MarkView 10.x Fix Pack Installer includes an option to select "Install Wildfly"

1566027: When adding project details for an invoice line in MarkView, the ap_invoice_distributions_all.PA_ADDITION_FLAG flag in Oracle was not set correctly

1562069: User who was not an owner experienced long delays opening a document in viewer for a workitem with many actions/transitions

Issues Resolved in Fix Pack 3

1559631: C&O: Support for RDBMS 19c (19.3) and Windows 2019 was to be added

1559295: The dependency on Oracle Java Advanced Imaging (JAI) was to be eliminated

1554631: The httpclient library included vulnerabilities

1550538: Opening MV Home in the Chrome browser caused an error due to unacceptable characters in the input

1548660: There was an unnecessary lock icon during line creation in MarkView Viewer

1546284: GL Accounts could not be ordered by frequently or recently used

1545506: The usermgmt.log file was absent in case MarkView was installed on JBoss EAP/ WildFly application servers

1545058: When a user had an alternate user and then their work items were reassigned to a third user, that user could not save accounting line data after editing

1540318: MarkView users could not copy information from tables in Viewer

1538781: KTM Validation screen 'Match Receipt Lines' was showing the Fully Invoiced Releases

1538777: KTM Validation screen 'Match Receipt Lines' was showing 'CLOSED' releases

1538755: Deliver To Person ID and Agent ID longer than 30 characters resulted in error when processing a PO invoice

1538745: R12 Tax Field - MV Tax Regime LOV values were not similar to Oracle LOV values.

1538734: Invoices with 'Misc Costs' in their amount after the queue 'Waiting for Interface Processing' got stuck in 'Interface Processing Error'

1538723: Account Coding - the ACD list of values did not show certain Legal Entities

1538715: MarkView showed end-dated Legal Entities in the ACD list of values

1531226: MarkView Documents did not open from an iExpense notification email when Java Web Start was enabled

1530083: Users with the LOCALE_de group assigned could not assign an alternate user

1530076: Oracle user names (USER_ID) longer than 30 characters resulted in error when opening the SFXRTINV form in Oracle Apps as that user

1530073: Oracle user names (USER_ID) longer than 30 characters resulted in error when opening the SFXPNDQS form in Oracle Apps as that user

1530070: Oracle user names (USER_ID) longer than 30 characters resulted in error when opening the Workflow Role Select form in Oracle Apps as that user

1530067: Oracle user names (USER_ID) longer than 30 characters resulted in error when opening the SFXWKFDR form in Oracle Apps as that user

1524474: Changes to the default displaying of invoices were not saved

1523723: AUSS was running slowly

1516034: Support for SAML using SHA256 was to be added

1512615: When attempting to apply the 10.0.0.5 hotfix, an error occured during publishing the batch class, if the KAMV workflow agent did not exist

1509983: An error handling vulnerability was detected

1509981: The jQuery library included vulnerabilities

1501730: Cross-site request forgery (CSRF) vulnerabilities were detected

1491235: When entering an OU into the invoice workbench in R12, after clicking Get Next an error was thrown

1467546: MarkView Viewer did not load when opening an invoice

1451694: Account Coding - Business Entity Segment LOV values did not match Oracle segment values; MarkView showed only the segments attached to a legal entity

1320738: MarkView KTM - Splitting or creating a document in KTM Validation caused an error

Issues Resolved in Fix Pack 2

1446994: The "To" LOV in the viewer email did not function properly

1442224: MarkView Document Library: received invalid browser error when attempting to view MarkView Documents in any supported browser except unsupported IE 11 in compatibility mode

1413519: Generating properties for silent installation was incorrect

1407754: Java Web Start (JWS): failed to open MarkView documents in a single instance of the viewer

1403720: PO Line Numbers greater than 5 characters lead to an error

1398534: Coding DFF: error encountered with apostrophe in DFF segment values

1397811: Filtering users in Contact combo box returned incorrect results when taking Request Comment, Reassign or Entry Complete

1380785: Request to support Oracle Database 19c (19.3)

1380757: Viewer: missing Scroll vertical bars

1377649: MarkView viewer had coding performance issues

1369161: Kofax Export Connector version was not getting updated in Kofax Capture to 10.1.0.1

1368634: BatchGUID and DocumentGUID were absent from Class Properties for MarkView 10.1

1361731: Re-Create Document action failed if mv_document_type.document_type_id contained a 3-digit value

1357812: Recreating document action failed if you define new fields/LOVs with the required flag set to Y

Issues Resolved in Fix Pack 1

1351354: Alternate User was unable to code or distribute invoices: "You do not have the necessary authorization to edit this document" error received while saving

1344238: There were no titles of controls in the AUSS "Select Source System Groups" window in Google Chrome browser

1343793: There were no Add and Remove buttons on the AUSS Source System groups page in Google Chrome browser

1343023: Change to MV_IMP_GENERIC to support Kofax Analytics for MarkView caused modifications to workitem properties in customer's MVT_DOCUMENT_CAPTURE_CUSTOM.PostCreateDocument procedure to be overwritten

1338166: Not possible to add or edit lines in the Accounting section after setting DFF Segments

1327705: XSS filter failed when there were double quotes in the header from Single Sign On

1327543: Verify Upload functionality did not work in MarkView Import API Configuration

1324791: Defaulted line amount was not the same as the undistributed amount when mverp_dfm_custom.GetAmountUndistributed was customized

1320984: The action buttons were enabled if you selected another line in edit mode

1320954: The Folder icon appeared when editing lines in Accounting

1317040: Get Next opened a new invoice in a new tab

1316777: Expenses did not work after a proper installation of MarkView 10.1

Applies To

This fix pack is based on Kofax MarkView for Accounts Payable 10.1.0.

Only apply this fix pack to the MarkView 10.1.0 application server; do not run the fix pack installer on a MarkView Oracle Objects installation or on a Kofax Capture Output installation.

Verify that the version of all installed MarkView components (such as Self-Service Invoices, Document Library, Expenses) is 10.1.0.

For information about system requirements, see the Kofax MarkView 10.1.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 Kofax expects you to apply the latest fix pack on top of any previously installed 10.1.0 fix packs.

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.1.0.7.zip	10.1.0.7
ReadMe-KofaxMarkView-10.1.0.7.htm	10.1.0.7
ReadMe-KofaxMarkView_KTMProject-10.1.0.7.htm	10.1.0.7

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.1.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.1.0 and you plan to use the same method to install the fix pack, do the following:

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.1.0 Upgrade Guide.

Apply the Fix

Log in to the application server as the user who installed MarkView 10.1.0.
Ensure that the environment variables required for installing MarkView 10.1.0 are defined.
See the Kofax MarkView 10.1.0 Upgrade Guide for information about setting environment variables and about settings required to run the installer.
Locate the base MarkView directory where MarkView is installed. Use this pathname 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.1.0.7.zip file into a new directory on the application server where MarkView 10.1.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 SYSDBA user.
Assign all needed grants and privileges to the MarkView schema user by executing markview_grant_privileges.sql script, which is included in the following fix pack distribution directory:
<MARKVIEW-FIX-PACK-INSTALLER>/modules/installer-dist-10.1.0/scripts
where <MARKVIEW-FIX-PACK-INSTALLER> is the directory where KofaxMarkView-10.1.0.7.zip was extracted.
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 fix pack distribution directory:
<MARKVIEW-FIX-PACK-INSTALLER>/modules/installer-dist-10.1.0/installer-db
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.1.0 Upgrade Guide for information about running the installer.
The installer shows the list of all 10.1.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.1.0 installation.
(If available, use the installation worksheet that was completed for MarkView 10.1.0.)
Note: Install the fix pack in the same target directory specified for the MarkView 10.1.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 the on-screen instructions that appear in the installation summary window.
Restart the application server.
As a result of the implemented changes, the following procedure is modified in the MVERP_DFM_Custom package.
GetAmountUndistributed: Sets the undistributed amount for invoice lines or invoice header.
Follow these steps to update the customization:
1. In <MARKVIEW-INSTALL-DIR>/misc/10.1.0/FIX10312, find the mverp_dfm_custom_pb.sql package.
  
  Where <MARKVIEW-INSTALL-DIR> is the base directory where MarkView is installed.
2. If you have not customized your MVERP_DFM_Custom package, compile this package to upgrade it to the current version.
3. If you have customized your MVERP_DFM_Custom package, modify it manually and compile the package to correspond to the current specification.
4. Note that procedures and functions from the MVERP_DFM_Custom package are called only if the ENABLE_MVERP_DFM_CUSTOM preference is set to TRUE.
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.1 Upgrade Guide.
As a result of the implemented changes, recreate a database job for Connector Workflow Manager.
To create new database job for Connector Workflow Manager, follow the instructions in "Create a database job for Connector Workflow Manager" in the Kofax MarkView 10.1 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 located in the following fix pack distribution directory:
<MARKVIEW-FIX-PACK-INSTALLER>/modules/installer-dist-10.1.0/installer-db
Where <MARKVIEW-FIX-PACK-INSTALLER> is the directory where KofaxMarkView-10.1.0.7.zip was extracted.
In a clustered environment, point to one server, then propagate to other nodes in the cluster using the appropriate process for your application server.
If you plan to install Import Server or you have Import Server 10.1, verify that you clear the Verify Upload option on the Import tab of the MarkView Import Server Preferences window.

KTM Project Files

The KTM project was updated as part of the 10.1.0.3 Fix Pack. Skip this procedure if you have MarkView 10.1.0 Fix Pack 3 installed.
This Fix Pack is cumulative and includes all improvements to the MarkView 10.1.0 KTM project file.
Note: You can follow the steps in the ReadMe-KofaxMarkView_KTMProject-10.1.0.7.htm file to manually update your customized KTM project file with the new fixes.

Upgrade KTM Project Files

Follow the instructions in this section to install the new KTM project file and overwrite your existing KTM project. If you have customized your KTM project file, consider the following before you install the new KTM project:

You can follow the steps in the ReadMe-KofaxMarkView_KTMProject-10.1.0.7.htm file to manually update your customized KTM project file with the new fixes.

Alternatively, follow the steps in this section to install the new KTM project and overwrite your existing KTM project file.

You can either keep your existing KTM project, or alternatively, follow the steps in this section to install the new KTM project and overwrite your existing KTM project file. Installing this new KTM project will likely require Professional Services involvement to reintegrate any pre-existing project customizations.

Follow the instructions in this section only to overwrite your existing KTM project file with the new KTM project.

Prerequisites

Install Kofax Transformation Modules 6.2.1 and later, then return to this section.

To Upgrade KTM Project Files:

If you modified your KTM project files, copy them to a safe location before upgrading to a new version of the KTM project.
KTM projects files are located in C:\KTM\MARKVIEW.
Extract KTMProject.zip and copy all files from:
<MARKVIEW-INSTALL-DIR>/misc/10.1.0/KTMProject on the application server
To the folder which contains the MarkView KTM Project files, such as:
C:\KTM\MARKVIEW\MarkView KTM Invoices 50
Note: Upgrading MarkView KTM Project in such a way requires Professional Services involvement to reintegrate any pre-existing project customizations.
Start Kofax Transformation Modules Project Builder.
From the File menu, select Open Project and open the applicable Kofax Transformation Modules project.
Locate the MarkView KTM Invoices 50.fpr file (in C:\KTM\MarkView\MarkView KTM Invoices 50.fpr).
Update the project settings to reflect your configuration:
Follow the instructions in "Preparing the KTM Project Template for Use" in the Kofax MarkView 10.1.0 Installation Guide.
Save the Kofax Transformation Modules project.
If you see an upgrade warning, disregard the warning and close the warning window.
Close the Kofax Transformation Modules Project Builder.
In Kofax Capture Administration, synchronize the new project file with the Kofax Transformation Modules project.
In Kofax Capture Administration, publish the new batch classes.

Kofax MarkView Export Connector 10.1.0

Skip this section if you have MarkView 10.0.0 Fix Pack 7 or later installed.
Install Kofax MarkView Export Connector version 10.1.0.1.
Note: If you have any customizations of the MarkView KTM Project, back up your customized version.

If you have any customizations of the XSLT files used by MVImportAPIConfig, back up the XSLT files before running the installer.
If you do not plan to use Kofax Analytics for MarkView, you can restore the XSLT backup files after the installation of Kofax MarkView Export Connector.

To install Kofax MarkView Export Connector:

Run the msi file from:
<MARKVIEW-INSTALL-DIR>/misc/10.1.0/KCEC-MarkView/kcec-markview.msi
Where <MARKVIEW-INSTALL-DIR> is the base directory where MarkView is installed.
Clear the KTM Project Feature check box in the installer window.
To perform a silent installation or removal, run one of the following commands from the directory where kcec-markview.msi is located:
- To install Kofax MarkView Export Connector silently and overwrite your existing KTM project:
  
  msiexec.exe /i kcec-markview.msi /qn
- To install Kofax MarkView Export Connector silently without the new KTM project:
  
  msiexec.exe /i kcec-markview.msi ADDLOCAL=ProductFeature /qn
- To remove Kofax MarkView Export Connector:
  
  msiexec.exe /uninstall kcec-markview.msi /qn
The msiexec.exe file is located in the following directory:
C:\Windows\system32\

Capture and Output components for MarkView 10.1.0

The following Capture and Output components for MarkView were updated as part of MarkView 10.1.0 Fix Pack 4.
Skip configuring these components if you have them set up during MarkView 10.1.0 Fix Pack 4 installation:

MarkView Import Server:
To install or upgrade the MarkView Import Server, run the msi file from:
<MARKVIEW-INSTALL-DIR>/misc/10.1.0/FIX14823/MVImport.Installer.msi
Configure MarkView Import Server on a machine with KTM installed.
MarkView Mail Gateway:
To install or upgrade MarkView Mail Gateway, run the msi file from:
<MARKVIEW-INSTALL-DIR>/misc/10.1.0/MailService/sfMailService.Installer.msi
Configure MarkView Mail Gateway on a machine with KTM installed.

Skip this procedure if you have MarkView 10.1.0 Fix Pack 3 installed and you are not currently using RDBMS 19c in this environment.
To support RDBMS 19c and Windows 2019, do the following steps:

Install the ODAC1931_x64;
Install the Oracle Database 19c Client (19.3) for Microsoft Windows (32-bit):
1. Run the installer.
2. Select the Custom installation type.
3. On the Available Product Components page, select the following components:
  Oracle ODBC Driver
  Oracle Provider for OLE DB
  Oracle Data Provider for .NET
4. Install the product.
Register the Oracle.DataAccess.dll in the GAC by running the following commands in the CMD (use 32-bit CMD):

cd <Oracle Database 19c Client for Microsoft Windows (32-bit) installation directory>\odp.net\bin\4
OraProvCfg.exe /action:ungac /providerpath:<Oracle Database 19c Client (32-bit) installation directory>\ODP.NET\bin\4\Oracle.DataAccess.dll
OraProvCfg.exe /action:ungac /providerpath:<Oracle Database 19c Client (32-bit) installation directory>\odp.net\PublisherPolicy\4\Policy.4.112.Oracle.DataAccess.dll
OraProvCfg.exe /action:ungac /providerpath:<Oracle Database 19c Client (32-bit) installation directory>\odp.net\PublisherPolicy\4\Policy.4.121.Oracle.DataAccess.dll

cd <Oracle Database 19c Client (32-bit) installation directory>\odp.net\bin\4
OraProvCfg.exe /action:gac /providerpath:<Oracle Database 19c Client (32-bit) installation directory>\ODP.NET\bin\4\Oracle.DataAccess.dll
OraProvCfg.exe /action:gac /providerpath:<Oracle Database 19c Client (32-bit) installation directory>\odp.net\PublisherPolicy\4\Policy.4.112.Oracle.DataAccess.dll
OraProvCfg.exe /action:gac /providerpath:<Oracle Database 19c Client (32-bit) installation directory>\odp.net\PublisherPolicy\4\Policy.4.121.Oracle.DataAccess.dll

cd <Oracle Database 19c Client (32-bit) installation directory>\odp.net\bin\2.x
OraProvCfg.exe /action:ungac /providerpath:<Oracle Database 19c Client (32-bit) installation directory>\ODP.NET\bin\2.x\Oracle.DataAccess.dll
OraProvCfg.exe /action:ungac /providerpath:<Oracle Database 19c Client (32-bit) installation directory>\odp.net\PublisherPolicy\2.x\Policy.2.102.Oracle.DataAccess.dll
OraProvCfg.exe /action:ungac /providerpath:<Oracle Database 19c Client (32-bit) installation directory>\odp.net\PublisherPolicy\2.x\Policy.2.111.Oracle.DataAccess.dll
OraProvCfg.exe /action:ungac /providerpath:<Oracle Database 19c Client (32-bit) installation directory>\odp.net\PublisherPolicy\2.x\Policy.2.112.Oracle.DataAccess.dll
OraProvCfg.exe /action:ungac /providerpath:<Oracle Database 19c Client (32-bit) installation directory>\odp.net\PublisherPolicy\2.x\Policy.2.121.Oracle.DataAccess.dll

cd <Oracle Database 19c Client (32-bit) installation directory>\odp.net\bin\2.x
OraProvCfg.exe /action:gac /providerpath:<Oracle Database 19c Client (32-bit) installation directory>\ODP.NET\bin\2.x\Oracle.DataAccess.dll
OraProvCfg.exe /action:gac /providerpath:<Oracle Database 19c Client (32-bit) installation directory>\odp.net\PublisherPolicy\2.x\Policy.2.102.Oracle.DataAccess.dll
OraProvCfg.exe /action:gac /providerpath:<Oracle Database 19c Client (32-bit) installation directory>\odp.net\PublisherPolicy\2.x\Policy.2.111.Oracle.DataAccess.dll
OraProvCfg.exe /action:gac /providerpath:<Oracle Database 19c Client (32-bit) installation directory>\odp.net\PublisherPolicy\2.x\Policy.2.112.Oracle.DataAccess.dll
OraProvCfg.exe /action:gac /providerpath:<Oracle Database 19c Client (32-bit) installation directory>\odp.net\PublisherPolicy\2.x\Policy.2.121.Oracle.DataAccess.dll
To install or upgrade MarkView Bar Code Server, run the msi file from:
<MARKVIEW-INSTALL-DIR</misc/10.1.0/FIX14539/MVBarcodeServer.Installer.msi
Configure MarkView Bar Code Server on a machine with KTM installed.

Kofax Capture batch class templates

Skip this section if you have MarkView 10.1.0 Fix Pack 2 installed.
Kofax Capture batch class templates for MarkView were updated as a part of 10.1.0.2 Fix Pack.

To apply the changes, follow the steps:

Copy the MarkView.cab file
From:
<MARKVIEW-INSTALL-DIR>/misc/10.0.0/KTMProject
To:
C:\KTM\MarkView
In Kofax Capture Administration, import the MarkView.cab file.
Resynchronize your project and republish the corresponding batch classes.

MarkView Post-Installation Steps (WildFly and FileNet only)

If you are installing this fix pack on WebLogic Application Server, or if you do not use the FileNet server, skip this section.
If you are installing this fix pack on WildFly Application Server and you use the FileNet server, perform the following post-installation steps:

Back up $JBOSS_HOME/standalone/configuration/standalone.xml.
Open $JBOSS_HOME/standalone/configuration/standalone.xml and locate the following tag:
<subsystem xmlns="urn:jboss:domain:security:1.2">
Within <subsystem xmlns="urn:jboss:domain:security:1.2">, locate the <security-domains> tag and add the following strings:

<security-domain name="FileNetP8WSI" cache-type="default">
<authentication>
<login-module code="com.filenet.api.util.WSILoginModule" flag="required"/>
</authentication>
</security-domain>
Save the file and restart the WildFly Application Server.

MarkView Post-Installation Steps (Oracle E-Business Suite using Java Web Start only)

Skip this section if you have MarkView 10.1.0 Fix Pack 2 installed.
MarkView 10.1.0 Fix Pack 2 includes an interim solution to Oracle E-Business Suite issue (Doc ID 2386335.1) WEB.SHOW_DOCUMENT Target WindowName Does Not Work with Java Web Start (JWS) that affects MarkView Get Next functionality by opening a new browser tab for every invoice.
If you are integrating with Oracle E-Business Suite using Java Plug-In technology to run Oracle Forms, skip this section.
If you are integrating with Oracle E-Business Suite using Java Web Start technology to run Oracle Forms, perform the following steps for the appropriate client browsers.

To apply MarkView patch in the Internet Explorer and Edge browsers:

Log in to MarkView as the Admin user.
Open Administration > MarkView Admin menu and set the MVOAIN_FORM_JWS preference value to TRUE.
Allow pop-up windows in the Internet Explorer and Edge client browsers.

MarkView 10.1.0 Fix Pack 2 also includes plugins for the Google Chrome and Firefox browsers that can be applied in the debug mode or published in Web Store.

To apply the fix in the Google Chrome browser in the debug mode:

Extract <MARKVIEW-INSTALL-DIR>/misc/10.1.0/FIX12311/Chrome.zip

where <MARKVIEW-INSTALL-DIR> is the base directory where MarkView is installed.
Open the browser and navigate to the Chrome extensions management page located here:
chrome://extensions
Ensure that the developer mode is on.
Click the Load Unpacked button and select the extension directory.
To publish the fix in the Chrome Web Store, follow the Chrome extension developer guide.

To apply the fix in the Firefox browser in the debug mode:

Extract <MARKVIEW-INSTALL-DIR>/misc/10.1.0/FIX12311/Firefox.zip
where <MARKVIEW-INSTALL-DIR> is the base directory where MarkView is installed.
Open the browser and enter "about:debugging#addons" in the address bar.
Click the Load Temporary Add-on button and select manifest.json file from the extension directory.
To publish the fix in the Firefox Web Store, follow the Firefox extension developer guide.

Oracle Forms Integration

Apply FIX8627

Starting from version 10.1.0.3, the fix pack contains FIX8627 for the folowing bug:
Bug 1491235: Connector invoices and MOAC responsibility: When entering an OU into the invoice workbench in R12 and then clicking Get Next, an error message pops up saying 'FRM-402020: Field must be entered'
If you do not experience the same issue or if you already applied this fix, skip the steps.

To apply FIX8627:

Log in to the operating system where the Oracle ERP server is installed as the owner of the Oracle ERP system.
Copy the MVOAUTIL.pll file from:
<MARKVIEW-INSTALL-DIR>/misc/10.1.0/FIX8627
To:
$c_MARKVIEW_TOP/MVOA/6.1.0.0/libraries
where <MARKVIEW-INSTALL-DIR> is the base directory where MarkView is installed.
Back up the previous version of $c_MARKVIEW_TOP/MVOA/6.1.0.0/libraries/MVOAUTIL.plx.
Compile MVOAUTIL.pll into MVOAUTIL.plx using your valid connection string value:

frmcmp userid=apps/apps-pw@connectstring module=$c_MARKVIEW_TOP/MVOA/6.1.0.0/libraries/MVOAUTIL.pll module_type=LIBRARY compile_all=YES
Note: If you copy and paste from this file, remove any line breaks.
Back up the previous version of $AU_TOP/resource/MVOAUTIL.plx.
Copy the MVOAUTIL.plx file from:
$c_MARKVIEW_TOP/MVOA/6.1.0.0/libraries
To:
$AU_TOP/resource

Apply FIX12715

Starting from version 10.1.0.3, the fix pack contains FIX12715 for the following bugs:
Bug 1530067: Update SFXWKFDR form to allow for longer user names
Bug 1530070: 170 Workflow Role Select form no data found error is raised when opening if user name greater than 30 characters
Bug 1530073: Update SFXPNDQS form to allow for longer user names
Bug 1530076: Update SFXRTINV form to allow for longer user names

If you do not experience any of these issues or if you already applied this fix, skip the steps. You may skip the steps for any form that you do not use.

To apply FIX12715:

Log in to the operating system where the Oracle ERP server is installed as the owner of the Oracle ERP system.
Copy SFXWKFDR.fmb, SFXURSEL.fmb, SFXPNDQS.fmb, SFXRTINV.fmb files from:
<MARKVIEW-INSTALL-DIR>/misc/10.1.0/FIX12715
To:
$c_MARKVIEW_TOP/MVOA/6.1.0.0/forms
where <MARKVIEW-INSTALL-DIR> is the base directory where MarkView is installed.
Back up the previous versions of $c_MARKVIEW_TOP/MVOA/6.1.0.0/forms/*.fmx files.
Important: Add the AU_TOP/forms/US path to the FORMS_PATH variable:

FORMS_PATH=$FORMS_PATH:$AU_TOP/forms/US
Note: If you skip this step, the forms may be still successfully compiled but they may not work correctly.
Compile SFXWKFDR.fmb into SFXWKFDR.fmx using your valid connection string value:

frmcmp userid=apps/apps-pw@connectstring module=$c_MARKVIEW_TOP/MVOA/6.1.0.0/forms/SFXWKFDR.fmb module_type=FORM compile_all=YES
Note: If you copy and paste from this file, remove any line breaks.
Compile SFXURSEL.fmb into SFXURSEL.fmx using your valid connection string value:

frmcmp userid=apps/apps-pw@connectstring module=$c_MARKVIEW_TOP/MVOA/6.1.0.0/forms/SFXURSEL.fmb module_type=FORM compile_all=YES
Note: If you copy and paste from this file, remove any line breaks.
Compile SFXPNDQS.fmb into SFXPNDQS.fmx using your valid connection string value:

frmcmp userid=apps/apps-pw@connectstring module=$c_MARKVIEW_TOP/MVOA/6.1.0.0/forms/SFXPNDQS.fmb module_type=FORM compile_all=YES
Note: If you copy and paste from this file, remove any line breaks.
Compile SFXRTINV.fmb into SFXRTINV.fmx using your valid connection string value:

frmcmp userid=apps/apps-pw@connectstring module=$c_MARKVIEW_TOP/MVOA/6.1.0.0/forms/SFXRTINV.fmb module_type=FORM compile_all=YES
Note: If you copy and paste from this file, remove any line breaks.
Back up the previous versions of $c_MARKVIEW_TOP/forms/US/*.fmx files.
Copy the compiled SFXWKFDR.fmx, SFXURSEL.fmx, SFXPNDQS.fmx, SFXRTINV.fmx forms from:
$c_MARKVIEW_TOP/MVOA/6.1.0.0/forms
To:
$c_MARKVIEW_TOP/forms/US

Apply FIX16695

Starting from version 10.1.0.6 the fix pack contains FIX16695 for the following bug:
Bug 1734088: After applying Oracle patch for Log4j vulnerability, MarkView is negatively impacting core Oracle functionality". If you already applied this fix, skip the steps.

To apply FIX16695:

Log in to the operating system where the Oracle ERP server is installed as the owner of the Oracle ERP system.
Change the directory to <MARKVIEW-INSTALL-DIR>/misc/10.1.0/FIX16695:
cd <MARKVIEW-INSTALL-DIR>/misc/10.1.0/FIX16695
where <MARKVIEW-INSTALL-DIR> is the base directory where MarkView is installed.
Extract the files from mvoa_patch.zip archive into $JAVA_TOP directory:

unzip -o -d $JAVA_TOP mvoa_patch.zip
Change the directory to $JAVA_TOP:

cd $JAVA_TOP
Optionally, remove log4j classes from $JAVA_TOP if they exist:

rm -f log4j.jar log4j.properties
rm -rf org/apache/log4j
rmdir --ignore-fail-on-non-empty org/apache org
For Oracle EBS 12.2.x only:
1. Back up the previous version of $JAVA_TOP/customall.jar file.
2. Run adcgnjar utility to recreate and sign $JAVA_TOP/customall.jar file:
  
  adcgnjar
  (Enter APPS schema name and password when prompted.)
Restart the Oracle ERP system.

Apply FIX18102

Starting from version 10.1.0.7, the fix pack contains FIX18102 for the folowing bug:
Bug 1858278: document_id values are becoming too large for the column on mv_document table (and other related MV tables) If you already applied this fix, skip the steps.

To apply FIX18102:

Log in to the operating system where the Oracle ERP server is installed as the owner of the Oracle ERP system.
Copy the MVOAUTIL.pll file from:
<MARKVIEW-INSTALL-DIR>/misc/10.1.0/FIX18102
To:
$c_MARKVIEW_TOP/MVOA/6.1.0.0/libraries
where <MARKVIEW-INSTALL-DIR> is the base directory where MarkView is installed.
Back up the previous version of $c_MARKVIEW_TOP/MVOA/<version_number>/libraries/MVOAUTIL.plx.
Compile MVOAUTIL.pll into MVOAUTIL.plx using your valid connection string value:

frmcmp userid=apps/apps-pw@connectstring module=$c_MARKVIEW_TOP/MVOA/<version_number>/libraries/MVOAUTIL.pll module_type=LIBRARY compile_all=YES
Note: If you copy and paste from this file, remove any line breaks.
Back up the previous version of $AU_TOP/resource/MVOAUTIL.plx.
Copy the MVOAUTIL.plx file from:
$c_MARKVIEW_TOP/MVOA/<version_number>/libraries
To:
$AU_TOP/resource

Issues Resolved in This Fix Pack

FIX17824 addresses COD17824

Bug 1882182: Parameter checking added to improve security

Summary of changes: Added checking of incoming request parameters.

Impact of changes: No additional impact.

Patch testing: It has been verified that when sending valid and invalid request input values, all invalid input values are filtered out.

FIX17822 addresses COD17822

Bug 1912424: Verification of incoming HTTP request and cookies attribute added to improve security

Summary of changes: Added verification of incoming HTTP request for validity Origin and Referer headers. Added SameSite cookies attribute for MarkViewCookie.

Impact of changes: No additional impact.

Patch testing: It has been verified by using links in mails from external mailboxess and buttons from Oracle EBS to MarkView.

FIX17821 addresses COD17821

Bug 1842465: Web application security improved

Summary of changes: The second parameter is forced to be validated by checking against the whitelist of the supported rule names. If the ruleName parameter shows up with an invalid value, an error page opens.

Impact of changes: No additional impact.

Patch testing: It has been verified that it is impossible to enter a JavaScript snippet to build it into the response page and pass it over to the user.

FIX17820 addresses COD17820

Bug 1842455: SQL security improved

Summary of changes: The input is validated and all invalid request input values are filtered out and not used in the underlying SQL queries.

Impact of changes: No additional impact.

Patch testing: It has been verified that all invalid request input values are filtered out and not used in the underlying SQL queries.

FIX17893 addresses COD17893

Bug 1840918: When using the latest version of Google Chrome and Microsoft Edge, the Viewer did not always show Quick Info

Summary of changes: When using the latest version of Google Chrome and Microsoft Edge, the Viewer now always shows Quick Info.

Impact of changes: No additional impact.

Patch testing: It has been verified by opening, reloading, refreshing, and redirecting to the Quick Info section in different browsers.

FIX18102 addresses COD18102

Bug 1858278: In mv_document table and other related MarkView tables, document_id values were too large for the column

Summary of changes: Changed type for some fields from NUMBER(8) to NUMBER(11).

Impact of changes: No additional impact.

Patch testing: It has been verified by modifying document ID with valid and invalid values.

Issues Resolved in Previous Fix Packs

Issues Resolved in Fix Pack 6

FIX16695 addresses COD16695: MarkView classes in EBS JAVA_TOP do not directly depend on log4j library

Bug 1734088: After applying Oracle patch for Log4j vulnerability, MarkView is negatively impacting core Oracle functionality

Summary of changes: Changed MVFrameworkUtils.class and added Logger.class not to directly depend on log4j library.

Impact of changes: No additional impact.

Patch testing: The impacted Oracle pages (Suppliers, Expenses) are opened without errors even if log4j classes are not on the EBS class path.

FIX16614 addresses COD16614: AUSS synchronization performance was improved

Bug 1728850: AUSS experiencing major performance issues with synchronization

Summary of changes: Updated several sql requests that impacted AUSS synchronization performance.

Impact of changes: No additional impact.

Patch testing: The AUSS synchronization (including first-time sync, all SS groups sync, force full sync, and one user sync) now takes much less time than earlier.

FIX16326 addresses COD16326: Viewer Does Not Display All Layers of Certain PDF Files Ingested via Import Server

Bug 1775785: Viewer Does Not Display All Layers of Certain PDF Files Ingested via Import Server

Summary of changes: Add library for processing images with JBIG compression.

Impact of changes: No additional impact.

Patch testing: Attached PDF files ingested via Import Server render correctly in MarkView.
Also, the regression testing was performed: TIFF and PDF files ingested via Import Server render correctly in MarkView.

FIX15981 addresses COD15981: Tax Code field limit was increased from 15 to 30 bytes

Bug 1674203: Connector Tax Code / Tax Amount not being parsed as expected - increase the connector limit for Tax Code from 15 to 30 bytes

Summary of changes: Tax Code field limit was increased from 15 to 30 bytes.

Impact of changes: No additional impact.

Patch testing: The TEXT_LENGTH field limit was increased to 30 bytes.

FIX15464 addresses COD15464: Unexpected server error on User Profile update was resolved

Bug 1633904: 500 Internal Server error trying to update or create user record (Also typo 'comor' is being added to url in referrer)

Summary of changes: Added new filter to verify Origin/Referer http headers for the configured request. The previous fix for Bug 1501730 was removed as it was incorrect and caused a lot of issues.

Impact of changes: No additional impact.

Patch testing: MVAP_REFRESH_IPA_PO_TABLES_JOB is present in Scheduler > Jobs and absent in Scheduler > DBMS jobs.
If the MVAP_APA_ENABLE_INTEGRATION preference is set to false, the MVAP_IPA_PO_HEADER and MVAP_IPA_PO_LINES tables are empty.
If the MVAP_APA_ENABLE_INTEGRATION preference is set to true, the MVAP_IPA_PO_HEADER and MVAP_IPA_PO_LINES tables are filled in with data.

FIX14578 addresses FIX14578: Passing Distribution Flexfield data to the procedure that derives Invoice Account for Project data

Bug 1564108: Encountering an issue when coding an invoice with NON billable project coding

Summary of changes: Passed Distribution Flexfield data into the Oracle's pa_acc_gen_wf_pkg.ap_inv_generate_account.

Impact of changes: No additional impact.

Patch testing: Checked the proposed scenario and related areas.

Issues Resolved in Fix Pack 5

FIX15113 addresses COD15113: Security Vulnerability issues need to be resolved

Bug 1604403: Security Assessment - Cross-Site Scripting (XSS): Persistent (527049)

Bug 1604409: Security Assessment - Privilege Escalation - Prev Entered Working Folder (527132)

Bug 1604415: Security Assessment - Privilege Escalation (527133, 527134)

Bug 1604417: Security Assessment - Cross Site Request Forgery (527036)

Summary of changes: Added the prevention mechanism to avoid malicious form submission at the Unassign Alternate User form.

Added the user privileges verification on the Previously Entered Invoices page.

Reset the 'IsAuthorized' flag to false in GET_SECURITY joint points for APINVOICE and MVAP_RPT_SUPPLIER_WO_ATTACH inquires to disable access to these inquires for users who are not allowed to have the respective menu items.

Encoding of AUSS field values is not interpreted by Sencha framework as a part of html code.

Impact of changes: No additional impact.

Patch testing: It was verified that a session-unique identifier was added to the unassign alternate user request to prevent cross site request forgery.

It was verified that users not assigned to MODULE ADMINISTRATOR, WEB INQUIRY, INTERACTIVE QUERIES, or MARKVIEW WEB ADMINISTRATOR groups have no access to Suppliers with no MarkView Attachment During the Specified Period and AP Invoices inquires.

It was verified that users not included in MODULE ADMINISTRATOR or PREVIOUSLY ENTERED INVOICES groups cannot open Previously Entered Working Folder.

It was verified that HTML encoding is enabled on AUSS pages to prevent from potential user input executing.

FIX14860 addresses COD14860: Markup Viewer Tool/Action Icons display in the Viewer

Bug 1589959: Markup Viewer Tool/Action Icons not displayed in the Viewer

Summary of changes: Now the viewer model includes base64 encoded EOT Kofax-Action-Icons font.

Impact of changes: No additional impact.

Patch testing: It was verified that all icons are successfully displayed in MarkView Viewer when using a new added font file with the IE11 browser. The regression testing was performed for Google Chrome and Microsoft Edge browsers.

FIX14859 addresses COD14859: Specifying the dependency for core-apps.ear (JBoss)

Bug 1587064: JBoss failing to start deployments after 10.1.0.3 is applied in SAML environment

Summary of changes: Added jboss-all.xml with the dependency to core-apps.ear/META_INF.

Impact of changes: No additional impact.

Patch testing: No error appears after restarting Jboss EAP7.

Issues Resolved in Fix Pack 4

FIX14857 addresses COD14857: PLSQL code does not update creation_timestamp value in mv_document table after it was initially set

Bug 1587035: MarkView Workflow Exception: The page needed to be refreshed because user updated the page; error caused by mv_document.creation_timestamp updated to batch creation local time

Summary of changes: PLSQL code does not update creation_timestamp value in mv_document table after it was initially set.

Impact of changes: No additional impact.

Patch testing: Batch creation local time does no longer update the document creation timestamp.

FIX14841 addresses COD14841: Eliminating unnecessary Project blind queries upon requesting ACD Project fields

Bug 1585653: End users who click in Exp Type field without first entering a value in Project field caused a blind query

Summary of changes: Unnecessary Project blind queries upon requesting ACD Project fields were eliminated.

Impact of changes: No additional impact.

Patch testing: No blind query is sent when a user clicks other project fields without filling in Project field first.

FIX14823 addresses COD14823: Import Server fails to import PDFs with embedded images or signed with Docusign

Bug 1584333: Import Server fails to import PDFs with embedded images or signed with Docusign

Summary of changes: Implement repair for pdf's with errors.

Impact of changes: No additional impact.

Patch testing: Import Server successfully imports PDF files from the customer. Regression testing of Import Server was also provided.

FIX13443 addresses COD13443: Enable TLS 1.2 support for MailGateway

Bug 1582105: Enable TLS 1.2 support for MailGateway

Summary of changes: third-party email library replaced with Aspose Email for .NET, which supports TLS 1.2

Impact of changes: No additional impact.

Patch testing: TLS1.2 is supported for Mail Gateway. Smoke testing was performed: Approve/Reject action works correctly on IMAP, POP3 and SMTP servers with or without SSL on proper address with proper credentials and with TLS and TLS1.2. Approve/Reject action also works correctly with IMAP servers using different mailboxes, with and without authentication, and with different preferred formats. Connection tested for different servers.

New logging was verified for Outbound and Inbound service. Regression testing was performed: Approve/Reject action works correctly with TLS1.2 and IMAP with authentication.

FIX14736 addresses COD14736: Auto escalations work under all conditions

Bug 1580968: Auto escalations did not work due to error ORA-01722: invalid number

Summary of changes: Query predicate updated to use to_char instead of problematic to_number.

Impact of changes: No additional impact.

Patch testing: No errors occur after running automatic escalations.

FIX14849 addresses COD14849: When adding project details for an invoice line in MarkView, the ap_invoice_distributions_all.PA_ADDITION_FLAG flag in Oracle is set correctly

Bug 1566027: When adding project details for an invoice line in MarkView, the ap_invoice_distributions_all.PA_ADDITION_FLAG flag in Oracle was not set correctly

Summary of changes: "pa_addition_flag" is set to the correct value in the MarkView code.

Impact of changes: No additional impact.

Patch testing: The ap_invoice_distributions_all.PA_ADDITION_FLAG flag in Oracle is now set correctly when a user adds project details for an invoice line in MarkView.

FIX14563 addresses COD14563: Some document loading delay was eliminated

Bug 1562069: User who is not an owner experienced long delays opening a document in viewer for a workitem with many actions/transitions

Summary of changes: improved the performance of sql request for calculating document tools rights.

Impact of changes: No additional impact.

Patch testing: No performance problems occur when a user who is not an owner opens a document with numerous actions.

Issues Resolved in Fix Pack 3

FIX14688 addresses FR14688: The possibility to copy information in Viewer was returned

Bug 1540318: MarkView users could not copy information from tables in Viewer

Summary of changes: The possibility to copy from main tables on the left side was added in MarkView Viewer.

Patch testing: It has been verified that a line or lines in all tables in the Viewer, including the Additional Details window, can be copied to clipboard. The functionality has been verified in all supported browsers (IE11, Chrome, FireFox, Edge).

FIX14613 addresses FR14613: The dependency on Oracle Java Advanced Imaging (JAI) was eliminated

Bug 1559295: The dependency on Oracle Java Advanced Imaging (JAI) was to be eliminated

Summary of changes: Oracle Java Advanced Imaging (JAI) was changed to the Twelvemonkeys library.

Patch testing: It has been verified that MarkView can function without using JAI. Regression testing in scope of image importing, loading and displaying for images with different resolution has been provided, including performance testing.

FIX14539 addresses COD14539: C&O: Support for RDBMS 19c (19.3) and Windows 2019 was added

Bug 1559631: C&O: Support for RDBMS 19c (19.3) and Windows 2019 was to be added

Summary of changes: The support for RDBMS 19c and Windows 2019 was added to MarkView Mail Gateway and Kofax MarkView Bar Code Server.

Impact of changes: No additional impact.

Patch testing: It has been verified that Capture and Output components installed on Windows 2019 connect to RDBMS 19c and work correctly.

FIX13433 addresses COD13433: Now MV Home can be reached in the Chrome browser

Bug 1550538: Opening MV Home in the Chrome browser caused an error due to unacceptable characters in the input

Summary of changes: Now request header parameters can be wrapped with double quotes.

Impact of changes: No additional impact.

Patch testing: Using Chrome, tried to reach the MarkView Home URL.

FIX13428 addresses COD13428: DFM User accounts are now ordered by most frequently or most recently used

Bug 1546284: GL Accounts could not be ordered by frequently or recently used

Summary of changes: The default sorting by the "Account" field for the GL Account list has been removed.

Impact of changes: No additional impact.

Patch testing: It has been verified that DFM User Frequent Accounts are now ordered by most frequently or most recently used GL Account codes by default.

FIX13352 addresses COD13352: The Alternate User functionality was improved

Bug 1545058: When a user had an alternate user and then their work items were reassigned to a third user, that user could not save accounting line data after editing

Summary of changes: The Alternate User functionality was improved; the "Reassign Document" action was updated to handle cases with Alternate Users.

Impact of changes: No additional impact.

Patch testing: It has been verified that invoices assigned to an alternate user and then reassigned are still successfully coded and distributed by the user they were reassigned to.

FIX13295 addresses COD13295: MarkView installed on JBoss EAP/ WildFly application servers writes the usermgmt.log file

Bug 1545506: The usermgmt.log file was absent in case MarkView was installed on JBoss EAP/ WildFly application servers

Summary of changes: The ability to write log files was added in the MarkView framework.

Patch testing: It has been verified that the usermgmt.log file is now available.

FIX13146 addresses COD13146: The AUSS performance issue was resolved

Bug 1523723: AUSS was running slowly

Summary of changes: The incorrect changes were reverted back.

Impact of changes: No additional impact.

Patch testing: Regression testing was performed.

FIX13082 addresses COD13082: A new preference allows selecting the statuses of receipt that should be shown in the MVAP_RECEIPTS_MV table

Bug 1538781: KTM Validation screen 'Match Receipt Lines' was showing the Fully Invoiced Releases

Summary of changes: A new preference MVERP_RECEIPTS_FILTER_CONDITION was added.

It contains a boolean expression to filter the list of receipt lines in the MVAP_RECEIPTS_MV table returned by the MVERP_RECEIPTS.RefreshReceiptsTable procedure. The preference is limited by 2000 characters.

The following set of predefined fields can be used in the expression:

po_number, po_header_id, line_num, po_release_num, material_doc_num, material_doc_line_num, material_doc_year, movement_type, posting_date, document_date, material_number, description, quantity, unit_of_measure, receipt_total, delivery_note, bill_of_lading, ses_num, ses_line_num, invoicing_status.

By default, the preference value is empty.

For example, if you want to additionally exclude any OVER INVOICED and FULLY INVOICED receipts lines from the result set, you can use the following value: "INVOICING_STATUS not in ('FULLY INVOICED','OVER INVOICED')".

Impact of changes: No additional impact.

Patch testing: It has been verified that:

A new preference MVERP_RECEIPTS_FILTER_CONDITION was added and works correctly;
The performance of the MVAP_RECEIPTS_MV table has not significantly decreased.

FIX13080 addresses COD13080: KTM Validation screen 'Match Receipt Lines' is not showing 'CLOSED' releases

Bug 1538777: KTM Validation screen 'Match Receipt Lines' was showing 'CLOSED' releases

Summary of changes: The SQL query was changed to get the list of receipts without receipts for 'CLOSED' releases.

Impact of changes: No additional impact.

Patch testing: It has been verified that closed releases of a blanket PO have become unavailable for matching in KTM.

FIX13076 addresses COD13076: Links to MarkView Documents are now opened from the iExpense notification email, when MVOAIN_FORM_JWS is enabled

Bug 1531226: MarkView Documents did not open from an iExpense notification email when Java Web Start was enabled

Summary of changes: Expense documents in MarkView should not be processed by the JWS feature. Processing Expense documents by JWS was disabled.

Patch testing: It has been verified that links to MarkView documents work correctly when the MVOAIN_FORM_JWS is enabled.

FIX12963 addresses COD12963: An error handling vulnerability was resolved

Bug 1509983: An error handling vulnerability was detected

Summary of changes: The HTTP response was changed to hide private data.

Impact of changes: No additional impact.

Patch testing: It has been verified that the HTTP responses do not disclose private data.

FIX12962 addresses COD12962: jQuery libraries were updated to the 3.5.0 version

Bug 1509981: The jQuery library included vulnerabilities

Summary of changes: All jQuery libraries were updated to the 3.5.0 version.

Impact of changes: No additional impact.

Patch testing: Regression testing of the following modules was passed: SSI, Invoice Audit, Mobile, Migration Utility, Authentication Configuration, Print from Viewer.

FIX12944 addresses COD12944: Cross-site request forgery (CSRF) vulnerabilities were eliminated

Bug 1501730: Cross-site request forgery (CSRF) vulnerabilities were detected

Summary of changes: The CSRF filter was added.

Impact of changes: No additional impact.

Patch testing: It has been verified that after applying a special index.html, the request causes the 500 HTTP error. Tested on all supported browsers.

FIX12925 addresses COD12925: Success publishing the batch class, even if the KAMV workflow agent does not exist

Bug 1512615: When attempting to apply the 10.0.0.5 hotfix, an error occurred during publishing the batch class, if the KAMV workflow agent did not exist

Summary of changes: The Workflow Agent for KAMV was removed from the batch class. The MarkView.cab file was updated.

Patch testing: It has been verified that after importing the MarkView.cab and upgrading KCEC, the workflow agent for KAMV is absent in the MarkView Invoice batch class.

Also, it has been verified for both cases that documents and invoices are imported successfully from KTM to MV.

FIX12884 addresses COD12884: Users with LOCALE_de group assigned can assign an alternate user

Bug 1530083: Users with the LOCALE_de group assigned could not assign an alternate user

Summary of changes: UserID parameter was added to the standard header script for legacy UI generated in pl/sql - MVT_Web_Display_JS.DataValidation. Dates are validated considering the current user locale.

Impact of changes: No additional impact.

Patch testing: It has been verified that now a user with any locale can complete an alternate user assignment.

Also, regression testing in scope of date validation in forms for Interactive Queries, Web Inquiry, SSI, Doc Library was provided with the German locale.

FIX12836 addresses COD12836: SAML was configured to use the Sha-256 algorithm instead of Sha-1

Bug 1516044: Support for SAML using SHA256 was added

Summary of changes: SAML was configured to use the Sha-256 algorithm.

Impact of changes: No additional impact.

Patch testing: It has been verified that the SAML still works in a local environment.

FIX12727 addresses COD12727: MarkView workflow is fine when the userID > 30 characters

Bug 1538755: Deliver To Person ID and Agent ID longer than 30 characters resulted in error when processing a PO invoice

Summary of changes: Maximum size was changed to 100 for variables.

Impact of changes: No additional impact.

Patch testing: It has been verified that the error is not reproduced. Smoke testing for Non-PO, PO, Pre-Approved invoices, SSI and Expenses workflows was provided. Non-PO invoice import through KTM to MV has also been verified.

FIX12715 addresses COD12715:170 Workflow forms now allow user names greater than 30 characters

Bug 1530067: Oracle user names (USER_ID) longer than 30 characters resulted in error when opening the SFXWKFDR form in Oracle Apps as that user

Bug 1530070: Oracle user names (USER_ID) longer than 30 characters resulted in error when opening the Workflow Role Select form in Oracle Apps as that user

Bug 1530073: Oracle user names (USER_ID) longer than 30 characters resulted in error when opening the SFXPNDQS form in Oracle Apps as that user

Bug 1530076: Oracle user names (USER_ID) longer than 30 characters resulted in error when opening the SFXRTINV form in Oracle Apps as that user

Summary of changes: Enlarged user name limit for 170 Workflow forms to 150 characters.

Impact of changes: No additional impact.

Patch testing: It has been verified that Working Folder, Pending, Role Select, and Returned Invoices work fine with big user names.

FIX12666 addresses COD12666: MarkView Viewer loads successfully

Bug 1467546: MarkView Viewer did not load when opening an invoice

Summary of changes: In the index.jsp file for AUSS and MarkView Viewer, the Microloader script was moved into the page body.

Impact of changes: No additional impact.

Patch testing: It has been verified that MarkView Viewer loads without freezing.

FIX12428 addresses COD12428: Splitting or creating a document in KTM Validation does not cause error

Bug 1320738: MarkView KTM - Splitting or creating a document in KTM Validation caused an error

Applies to: MarkView KTM project.

Summary of changes: All callouts of pXDoc.Locators.ItemByName in KTM Validation are used on condition Locators.Exists returns True.

Impact of changes: No additional impact.

Patch testing: It has been verified that there is no error when splitting or creating a new document in KTM Validation now.

FIX10910 addresses COD10910: R12 Tax Field - MV Tax Regime LOV values are similar to Oracle LOV values

Bug 1538745: R12 Tax Field - MV Tax Regime LOV values were not similar to Oracle LOV values

Summary of changes: A new preference MVOA_ENABLE_TAXATION_COUNTRY_FILTER is created to control Taxation Country filtering with the default value set to TRUE.

If it is FALSE, Tax Regimes are not filtered by country code.

Impact of changes: No additional impact.

Patch testing: It has been verified, that the MVOA_ENABLE_TAXATION_COUNTRY_FILTER preference was added and works correctly:

if the MVOA_ENABLE_TAXATION_COUNTRY_FILTER = true (by default), Tax Regime LOV in MarkView is the same as it is on the Lines Tab and is filtered by Country Code;
if the MVOA_ENABLE_TAXATION_COUNTRY_FILTER = false, Tax Regime LOV in MarkView is the same as in Tax Details (a button below the list of lines) and is not filtered by Country Code;
Tax Jurisdictions LOV corresponds to Tax Regime and also depends on the MVOA_ENABLE_TAXATION_COUNTRY_FILTER.

FIX10704 addresses COD10704: Business Entity Segment LOV values match Oracle segment values

Bug 1451694: Account Coding - Business Entity Segment LOV values did not match Oracle segment values; MarkView showed only the segments attached to a legal entity

Summary of changes: The SQL request was changed to get correct Business Entity Segment LOV values.

Impact of changes: No additional impact.

Patch testing: It has been verified that in a LOV MarkView shows the balancing segments attached to a legal entity.

FIX9760 addresses COD9760: Invoices with 'Misc Costs' in their amount are now processed properly

Bug 1538734: Invoices with 'Misc Costs' in their amount after the queue 'Waiting for Interface Processing' got stuck in 'Interface Processing Error'

Summary of changes: Dummy lines are deleted before validation to avoid double validation of dummy lines.

Impact of changes: No additional impact.

Patch testing: It has been verified that invoices with dummy lines after "Waiting for receipt" queue are validated correctly.

Smoke testing for KC/KTM was also provided: Several invoices of different types were imported from KTM to Markview.

FIX8858 addresses COD8858: MarkView does not show end-dated Legal Entities in the ACD list of values anymore

Bug 1538715: MarkView showed end-dated Legal Entities in the ACD list of values

Summary of changes: The SQL request was updated to filter out end-dated Legal Entities.

Impact of changes: No additional impact.

Patch testing: It has been verified that end-dated Legal Entities are not displayed in the ACD list of values.

FIX8857 addresses COD8857: ACD list of values shows a complete list of Legal Entities

Bug 1538723: Account Coding - the ACD list of values did not show certain Legal Entities

Summary of changes: Establishing an ERP session before accessing ERP data inside the IsFlexValueInLOV function.

Impact of changes: No additional impact.

Patch testing: Passed the regression testing for accounting 1st segment and other of ACD, including adding new Legal Entities in 1st segment.

FIX8627 addresses COD8627: OU's are now entered the invoice workbench in R12 properly

Bug 1491235: When entering an OU into the invoice workbench in R12, after clicking Get Next an error was thrown

Summary of changes: MVOAUTIL library was updated to eliminate the error.

Impact of changes: No additional impact.

Patch testing: It has been verified that the Invoice workbench Get Next action loads the next invoice image and data correctly in case Multi-Org Access Control is enabled.

Issues Resolved in Fix Pack 2

FIX12491 addresses COD12491: The "To" LOV in the viewer email functions properly

Bug 1446994: The "To" LOV in the viewer email did not function properly

Summary of changes: Viewer backend and frontend were fixed. The preference EMAIL_DOCUMENT_RECIPIENT_LIST_FAST was added in MarkView. The default value is TRUE.

If MVERP_CUSTOM.GetUserEmailAddress is used for customization Email addresses for users, it needs to set EMAIL_DOCUMENT_RECIPIENT_LIST_FAST to FALSE.

Impact of changes: No additional impact.

Patch testing: The search among 11000 emails takes 1 second. The regression testing of new preference was performed.

FIX12430 addresses COD12430: MVDL - receives no errors when attempting to view MarkView Documents in any supported browser except unsupported IE 11 in compatibility mode

Bug 1442224: MarkView Document Library: received invalid browser error when attempting to view MarkView Documents in any supported browser except unsupported IE 11 in compatibility mode

Summary of changes: Support for new browsers was added.

Impact of changes: No additional impact.

Patch testing: MarkView Documents can now be opened in MarkView Document Library without any errors in all the supported browsers.

FIX12311 addresses COD12311: Java Web Start (JWS): opens MarkView documents in a single instance of the viewer

Bug 1407754: Java Web Start (JWS): failed to open MarkView documents in a single instance of the viewer

Applies to: Oracle EBS using Java Web Start only.

Summary of changes: A new preference MVOAIN_FORM_JWS was added. The setting forces the closure of the previous MarkView viewer browser windows in Get Next functionality. Plugins for Google Chrome and Firefox browsers are included into the Fix Pack.

Impact of changes: No additional impact.

Patch testing: GetNext functionality works correctly in JWS mode. The 'MVOAIN_FORM_JWS' preference works fine. Plugins for Google Chrome and Firefox browser work as designed.

FIX8376 addresses COD8376: PO Line Numbers greater than 5 characters do not cause an error

Bug 1403720: PO Line Numbers greater than 5 characters lead to an error

Summary of changes: String length increased.

Impact of changes: No additional impact.

Patch testing: Different scenarios of working with PO invoices passed correctly when PO line number was more then 5 characters.

FIX12195 addresses COD12195: Coding DFF - error is not encountered with apostrophe in DFF segment values

Bug 1398534: Coding DFF: error encountered with apostrophe in DFF segment values

Summary of changes: The method for processing strings containing an apostrophe was changed.

Impact of changes: No additional impact.

Patch testing: The error no longer occurs if you encode DFF segments with values that include an apostrophe or the following characters: _ - € $ ^ { + ~ * \ @

FIX12191 addresses COD12191: Filtering users in Contact combo box returns correct results when taking Request Comment, Reassign or Entry Complete

Bug 1397811: Filtering users in Contact combo box returned incorrect results when taking Request Comment, Reassign or Entry Complete

Summary of changes: LOV Combo box was fixed.

Impact of changes: No additional impact.

Patch testing: LOV Combo box works correctly.

FIX10567 addresses FR10567: Support for Oracle Database 19c (19.3) added

Bug 1380785: Request to support Oracle Database 19c (19.3)

Summary of changes: DBMS Job for Connector Workflow Manager was replaced with Oracle Scheduler Job.

Impact of changes: No additional impact.

Patch testing: MarkView 10.1.0.2 can now be installed on Oracle Database 19c. Regression testing of the database jobs and Connector workflows was performed.

FIX11034 addresses COD11034: Viewer has Scroll vertical bars

Bug 1380757: Viewer: missing Scroll vertical bars

Summary of changes: The scroll vertical bar was added in Action dialogs.

Impact of changes: No additional impact.

Patch testing: Scroll vertical bar appears for different forms in case the form is larger then the browser window.

FIX11091 addresses COD11091: MarkView viewer coding performance does not have issues

Bug 1377649: MarkView viewer had coding performance issues

Summary of changes: GL form was fixed.

Impact of changes: No additional impact.

Patch testing: During coding in MarkView while entering segment values, we can continue tabbing to enter the segment values while it keeps validating in the background. The loader does not appear when switching between input fields.

FIX10922 addresses COD10922: Re-Create Document action does not fail if mv_document_type.document_type_id contains a 3-digit value

Bug 1361731: Re-Create Document action failed if mv_document_type.document_type_id contained a 3-digit value

Summary of changes: Size of control name variable was increased to 45.

Impact of changes: No additional impact.

Patch testing: Copy/Re-Create/New/Follow-Up Document actions, KTM and Bar Code Generation for custom document type no longer fail.

FIX10891 addresses COD10891: Recreating document action does not fail if you define new fields/LOVs with the required flag set to Y

Bug 1357812: Recreating document action fails if you define a new fields/LOVs with the required flag set to Y

Summary of changes: The cover page class property generator processor was fixed. The issue of displaying cover page class property labels in actions forms was fixed as well

Impact of changes: No additional impact.

Patch testing: Re-create, copy, export new document from Kofax Capture and creating new document with New Document annotation/Complete Manual Review do not fail.

Issues Resolved in Fix Pack 1

FIX10312 addresses COD10312: Defaulted line amount was not the same as the undistributed amount when mverp_dfm_custom.GetAmountUndistributed was customized

Bug 1324791: Defaulted line amount was not the same as the undistributed amount when mverp_dfm_custom.GetAmountUndistributed was customized

Summary of changes: the method GetAmountUndistributed was modified in the MVERP_DFM_Custom package. The method allows to customize the calculation of the undistributed amount for the following entities:

the invoice header undistributed amount
the line undistributed amount
the default distribution amount

Impact of changes: No additional impact.

Patch testing: Updated mverp_dfm_custom.GetAmountUndistributed function structure covers all situations where undistributed amount is shown. In each place where the undistributed amount is shown, it can be calculated with a custom code or with the default implementation, independently from other places.

FIX10354 addresses COD10354: XSS filter failed when there were double quotes in the header from Single Sign On

Bug 1327705: XSS filter failed when there are double quotes in the header from Single Sign On

Summary of changes: Security filter was reconfigured. XSS filter does not fail when there are double quotes in the http request header for "cookie" and "surrogate-capability" parameters.

Impact of changes: No additional impact.

Patch testing: XSS filter for header parameters "cookie" and "surrogate-capability" allows double quotes. For other header parameters double quotes are still not allowed.

FIX10598 addresses COD10598: Expenses did not work after a proper installation of MarkView 10.1

Bug 1316777: Expenses did not work after a proper installation of MarkView 10.1

Summary of changes: Removed incorrect record from SF_WORKITEM_CLASS_PROPERTY table.

Impact of changes: No additional impact.

Patch testing: After correction of record in the SF_WORKITEM_CLASS_PROPERTY table, the Expenses pass through the workflow correctly.

FIX10456 addresses COD10456: Verify Upload functionality did not work in MarkView Import API Configuration

Bug 1327543: Verify Upload functionality did not work in MarkView Import API Configuration

Summary of changes: "Verify upload" functionality was enabled in the MarkView ImportAPI module.

Impact of changes: No additional impact.

Patch testing: Enabling Verify in the MarkView Import API causes no problems with importing documents and invoices.

FIX10643 addresses COD10643: Change to MV_IMP_GENERIC to support Kofax Analytics for MarkView caused modifications to workitem properties in customer's MVT_DOCUMENT_CAPTURE_CUSTOM.PostCreateDocument procedure to be overwritten

Bug 1343023: Change to MV_IMP_GENERIC to support Kofax Analytics for MarkView caused modifications to workitem properties in customer's MVT_DOCUMENT_CAPTURE_CUSTOM.PostCreateDocument procedure to be overwritten

Summary of changes: Prevented overwriting values set in the MVT_DOCUMENT_CAPTURE_CUSTOM.PostCreateDocument package.

Impact of changes: No additional impact.

Patch testing: MV_IMP_GENERIC is changed to support Kofax Analytic for MarkView. MVT_DOCUMENT_CAPTURE_CUSTOM.PostCreateDocument package values are not overwritten.

FIX10801 addresses COD10801: Alternate User unable to code or distribute invoices: "You do not have the necessary authorization to edit this document" error received while saving

Bug 1351354: Alternate User unable to code or distribute invoices: "You do not have the necessary authorization to edit this document" error received while saving

Summary of changes: Alternate User is able to code or distribute invoices.

Impact of changes: No additional impact.

Patch testing: An alternate user can encode lines and distributions, successfully save changes and send invoices further along the workflow.