MarkView for SAP 6.3
EMC Captiva OCR for Kofax
This release includes a new product integration, EMC Captiva OCR for MarkView which is based on the integration between MarkView and EMC Captiva InputAccel for Invoices.
EMC Captiva InputAccel for Invoices is used to capture and extract both header and line level data from supplier invoices. It uses SAP data, provided by MarkView to validate the data it extracts from the invoice and provides a user interface for verification. Once verified, documents are exported from EMC Captiva InputAccel for Invoices and imported into MarkView In addition to validation, this data is also used by EMC to assist in the accuracy of recognition, and to perform advanced functions such as PO line matching.
Documentum for Kofax
This release also includes support for another new product integration, Documentum for MarkView which is based on the integration between EMC Documentum Content server and MarkView
With this integration, captured documents are automatically stored in Documentum repositories by the MarkView Document Server. In addition to storing the physical document images, MarkView also sends invoice metadata, such as Supplier, Invoice Number, Invoice Total, etc., to the object within
Documentum. MarkView maintains the accuracy of this Documentum data by synchronizing it as the invoice moves through the invoice lifecycle.
Accounting Details Distribution Default
This release also includes a new preference that allows the distribution amount to be defaulted when a user enters a new line using the Accounting Details (ACD) tool. With this release, you can use either no default or set the distribution default to the total remaining undistributed amount on the invoice.
Support for RedHat 5.0 and Firefox 3.0
This release also includes support for RedHat 5.0 as an application server and Firefox 3.0 as a MarkView desktop browser. The Supported Platform Matrix has been updated to reflect this change. Published versions of the Supported Platform Matrix are posted on Support Web answer 1168:
Version 6.3 includes bug fixes and improvements related to the installer and upgrades.
This release also introduces out-of-the-box and configurable methods to prevent users from viewing documents to which they should not have access. These updates prevent users from ?phishing? for documents based upon IDs or other criteria. Rules in the product constrain a user?s access to documents. Additionally, configurable hooks are built into the customization framework to provide more advanced and customer-specific logic that can be implemented. For example, AP invoices can only be viewed by members of the AP groups, as well as the user who is the current owner of the invoice.
In Advisor, having the Finance Manager role does not necessarily allow Increase Priority, Escalate and Reassign actions. The user performing these actions must have the associated roles in MarkView.
InvoiceSweep does not check for cancelled items in the Pending Payments queue.
When adding a non-MarkView document to a MarkView Folder, the description that is entered does not get saved, and as a result, the document is shown without a description in the MarkView folder.
Under certain, complex circumstances, a work-item was unable to be re-assigned and/or escalated due to auto-retrieval rules applied to various MarkView queues. Now, work-items can be re-assigned and/or escalated in accordance with the documentation.
In Advisor, users in lists are not sorted when attempting to reassign a workitem.
- Select the menu item: Advisor --> Managing Cash
- Select a "Business Unit" from the Busines Unit dropdown list.
- Select the "Unprocessed Financial Liability" report from the dashboard
- Click on the bar chart to display a list of invoices
- Locate an invoice that allows you to perform an action (the far left will have a checkbox in the row if the invoice can have an action executed against it)
- Select the invoice by ensuring that the checkbox on the far left has been checked
- Click on the "Reassign..." button.
- A new screen should appear with a LOV.
- Verify that the LOV is sorted in alphabetically ascending order
Keywords: user guide, documentation