Issue/Symptom/Question
What areas of Penta use/integrate with OnBase?
Applies To
Penta for Windows
OnBase
Resolution/Fix/Answer
Security:
Penta Users automatically create OnBase users
Security Groups assigned to users should also map automatically
Notes:
Document Type Security is maintained in OnBase Only
Penta menu items/window access, report access, and OU (Organizational Unit) security is in Penta Only
Penta Created Documents
Documents are created in Penta and stored in the OnBase repository using two methods:
Manual Created Document (File > Reports) Examples:
Purchase Orders/PO Change Orders
Subcontracts/Sub Change Orders
Change Orders
Work Order Tickets
System and Process Generated Documents
Accounts Payable Checks/Direct Deposits (Based on system Option)
Payroll Checks/Direct Deposits (Employee Portal Customers only)
W2s (Employee Portal Customers Only)
Work Order Inspection Reports
Work Order Summary of Work Document
Work Order/Maintenance Contract Invoices/Support Schedules
Other Documents
Documents are created externally, imported within the source window (Employee Payroll Information, Job Information, etc), and stored in OnBase. Documents are available via the paperclip or within OnBase client.
Workflow Integration:
Customers using standard or custom-built workflows in OnBase may have integration enabled to pass documents and information between the two systems
Example:
Penta AP (Accounts Payable) Routing Solution
Information is queried from the Penta database and made available within OnBase for ease of routing invoices for approval
Once invoices are approved in the OnBase workflow, the AP Invoice record is interfaced to Penta, the AP Invoice Document is linked via the paperclip icon in various Penta windows
Invoice & Credit Memo Entry
Project Review & Forecast Entry
AP Query windows
RQ AP Routing Solution (same as above)