Workflow Implementation Report



Workflow Implementation ReportHyland encourages its partner companies and customers to create an instance of this report every time an OnBase workflow solution is placed into a customer production environment. It documents critical information about the workflow solution: its business purpose, key stakeholders, design decisions and implementation details. The report will inevitably support maintenance of the solution and subsequent refinements or additions to the solution. Hyland accepts submissions of the WIR from partners and customers, and employs them in its support function. Partners and customers can submit this report, along with related OnBase workflow configuration reports, to installation_report@. WIR Submitter InformationYour Name: FORMTEXT Type here...Your E-mail: FORMTEXT Type here...Your Company Name: FORMTEXT Type here...Customer InformationCustomer Name: FORMTEXT Type here...Principle Business Activity: FORMTEXT Type here...Workflow Completion Date (mm/dd/yy): FORMTEXT Type here...OnBase Workflow Administrator(s): FORMTEXT Type here...What is the Workflow Administrator’s account name on Hyland Community? FORMTEXT Type here...Database Administrator(s): FORMTEXT Type here...Company implementing the Workflow Solution: FORMTEXT Type here...OnBase Workflow Developer for the Solution: FORMTEXT Type here...OnBase VersionVersion/Build Installed (e.g., 12.0.1.566): FORMTEXT Type here...Core Version Installed (e.g., 12.0.1.84): FORMTEXT Type here...Key StakeholdersNameRole/PositionObjectives for Solution FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here...End UsersBusiness UnitUser Group# of UsersWork Schedule FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here...Database ServerDatabase Server Name: FORMTEXT Type here...Database Product Name (e.g., MS SQL, Oracle): FORMTEXT Type here...Database Product Version (e.g., SQL 2008 R2): FORMTEXT Type here...# CPUs/Speed: FORMTEXT Type here...Memory (RAM) of Machine: FORMTEXT Type here...OS and Service Pack Level: FORMTEXT Type here...Physical Drive Configuration: FORMTEXT Type here...OS Location/Size: FORMTEXT Type here...Database File(s) Location/Name: FORMTEXT Type here...Database Log Location/Size: FORMTEXT Type here...Database Backup Procedure: FORMTEXT Type here...Database Backup Location: FORMTEXT Type here...Any provisions for high availability and/or redundancy in the solution? FORMTEXT Type here...Provide the time and date of the last verified database backup. FORMTEXT Type here...What is the current failover strategy for the workflow solution? FORMTEXT Type here...Other applications active on or accessing database server (include virus scanning): FORMTEXT Type here...Workflow ServerNumber of Workflow Servers (Timer and Application) Employed with this Solution: FORMTEXT Type here...Workflow Server Machine Name(s): FORMTEXT Type here...# of CPU/Speed: FORMTEXT Type here...Memory (RAM): FORMTEXT Type here...Operating System/Service Pack Level: FORMTEXT Type here...Other Applications Loaded on the Workflow Server: FORMTEXT Type here...Process DefinitionDefine the business problem addressed by the workflow solution: FORMTEXT Type here...Attach a flowchart of the business process:? Flowchart attached? Flowchart not attachedIdentify the contributions the manner in which workflow supports the business process:? Enforce business policy? Enable auditing? Regulatory compliance? Improve customer service? Improved efficiencyWorkflow Technical DescriptionDescribe the solution design for this implementation in the format below or submit a copy of the technical specification for the solution used for this product.Life Cycle LevelFor each life cycle, identify the following:What is the function of this life cycle? FORMTEXT Type here...What document types enter the initial queue upon archival? FORMTEXT Type here...Identify users performing work in the life cycle. FORMTEXT Type here...List related life cycles and how they are related. FORMTEXT Type here...Identify system links or integrations related to this life cycle. FORMTEXT Type here...Identify the principle business owners of the supported work process. FORMTEXT Type here...TasksList tasks assigned to this queue and their purpose. FORMTEXT Type here...Timer WorkIdentify purpose of all timers FORMTEXT Type here...Identify the frequency for all timersEvery: FORMTEXT Type here...After: FORMTEXT Type here...At a specific timer? FORMTEXT Type here...Upgrades and TestingIdentify the test or development environment that will support enhancements or future development of this solution. (Environment names can be modified. Other examples include Training, Disaster Recovery, etc.)Identify versions where appropriate.Test EnvironmentOnBase Version FORMTEXT Type here...Database Server FORMTEXT Type here...Application Server FORMTEXT Type here...Development EnvironmentOnBase Version FORMTEXT Type here...Database Server FORMTEXT Type here...Application Server FORMTEXT Type here...UpgradingIdentify change control procedures and/or process requirements (I.E. ISO9001, HIPAA, etc. required with any upgrades. FORMTEXT Type here...Are there any outstanding issues with the currently installed version of OnBase that dictate an upgrade in the near future? Identify them and their associated issue or SCR #s: FORMTEXT Type here...TestingProvide the test plan, if used: FORMTEXT Type here...Provide network location and file names of test files/data: FORMTEXT Type here...Additional OnBase ModulesWhat additional OnBase modules were added to the solution to enable implementation of the workflow component (e.g., eForms, Outlook Integration, Application Enabler)? FORMTEXT Type here...Where in the solution are they used? FORMTEXT Type here...Application Enabler(Skip if not used.)How is Application Enabler used (e.g., index, retrieval)? FORMTEXT Type here...Identify the application being enabled. Include the name, version, screen/tab, and type (such as Smartscreen or HTML). FORMTEXT Type here...Who configured Application Enabler for this application? FORMTEXT Type here...Line of Business Application IntegrationList all other applications with which OnBase interacts. Identify the method of interaction (e.g., Application Enabler, specific OnBase API) and the business function of the other application.ApplicationVersionModule/Interface/screen/tab (e.g., Lawson AP)Method of Integration FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here... FORMTEXT Type here...Custom CodePlease describe all custom code used in this solution. Provide the following for each piece of code:Identify the file name for the code. FORMTEXT Type here...Identify what the code accomplishes. FORMTEXT Type here...Identify which OnBase API is used and its version. FORMTEXT Type here...Identify any custom tables used in this implementation. FORMTEXT Type here... ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download