Workflow V2.8.1 Administrator and User Guide February 2015

Transcription

1 Workflow V2.8.1 Administrator and User Guide February

2 Table of Contents Contents Introduction...3 Server System Requirements...4 Client System Requirements...4 USER GUIDE SECTION...5 Overview...5 Dashboard Screen...6 Group Box Screen...7 My Inbox Screen...8 Workflow Task Screen...9 Next Screen Choice Log Out History Screen Admin Module Workflow Module Workflow Start Values Workflow Start Values Workflow Indexes Templates Custom Buttons Users Module Roles Module Permissions Module Rules Module Custom expressions Custom Processing Integration Importing Licensing General Settings Other Features Audit Page Custom Development Integration Sample

3 GL Coding Button Introduction ECM Toolbox's Workflow is a rapidly deployed, out-of-the-box, turnkey workflow automation solution that leverages Document Management software and the ECM Toolbox workflow engine. The magic of is THIS Workflow Solution is that users have a simple interface that provides full control of the workflow process within the Document Management System. ECM Toolbox's Workflow is a completely web-based processing solution that: AND Automates verifications and approvals by activity owners Offers advanced document management functionality Transforms paper-based approvals into electronic approvals Interfaces with your ERP and Business Line Solution softwares Allows you to Create and Manage Your Workflows - IT Department Free Features Benefits Simple interface Users can quickly create, manage and delete workflow tasks Process integrity Establish business rules and ad hoc task routing Users roles & permissions Ensure secure access based on user access rights New rules & departments Quickly add new workflows notifications Receive timely alerts Commenting Add comments for the next level(s) of approval to view Flexibility Accept, reject or reassign single or bulk workflow tasks Design customization Customize the look and feel Two-way integration with your business application systems Image-enable your ERP/accounting or other business application back-end systems 3

4 Auditing At every workflow step, see who reviewed the workflow, when an action was performed and any notes/comments (whether human or systemgenerated); audit information is attached to the invoice Server System Requirements This section indicates the recommended minimum hardware/software prerequisites for installing and running the Workflow application. The capacity and speed of the application is commensurate on load and can be enhanced with improved hardware. *Hardware may be physical or virtualized. Processor System memory Disk space Network Operating System Software Database Quad core, 3.1 GHz* 16 GB* 150gb or higher (dependent on current volume and needed growth)* Gigabit Ethernet* Windows Server 2012 R2 (x86/x64) Windows Server 2008 R2 (x86/x64) IIS7+ Internet Explorer 10+.NET Framework 4.0 SQL 2008 R2 SP3 SQL 2012 SP2 SQL 2014 Client System Requirements This section indicates the recommended minimum hardware/software for accessing the Workflow application. The capacity and speed of the application is commensurate on load and can be enhanced with improved hardware. Processor Dual core, 2 GHz System memory 4 GB Disk space 150gb or higher (dependent on current volume and needed growth) Network Gigabit Ethernet Operating System Windows 7 (x86/x64) Windows 8 (x86/x64) Software Internet Explorer

5 USER GUIDE SECTION Overview The ECM Toolbox's Workflow application consists of several modules/functions which are listed below in the order as shown on-screen. Dashboard Group Box My Inbox History Help Log Out Whenever seen, the Question Mark icon can be used to access tooltip information on a given function. Starting a Workflow A Workflow can begin by a new document arriving or kicking off a workflow based on an existing document. This is a screenshot noting the workflow name, starting index value and if a workflow can start based on changing the index of an existing document. 5

6 Dashboard Screen The Dashboard is the initial start screen for the Workflow Application. The welcome message (green box below) is editable via the Admin module. Metrics displaying the current status of tasks is also displayed. Out of the box the statistics are general and regard number of workflow tasks. This screen can be customized to the desired specifications and data requirements. 6

7 Group Box Screen The Group Box module lists active Workflow Tasks and allows a user to View a document, as well as Approve, Reassign, and Terminate. This list is generated based on the user s permission. Un-owned documents are highlighted in yellow. Actions, such as Approve or Terminate are applied to tasks that are checked. Double clicking a task row will open the Workflow Task View for the individual Workflow item where additional features are available. Standard Action Buttons Approve o Moves the selected Task to the next role identified in the Rules Engine. If there are no other roles then the workflow ends/completes. Own o Takes ownership of the selected Task if it is currently un-owned. If a Task is already owned by another user, then a message will indicate that the request cannot be completed. Reassign o Opens the Reassign Options dialog which allows for the selected Task to be reassigned to a different Role of the user s choice. Refresh o Refreshes the data displayed in the Workflow Application. Terminate o Available based on individual permissions. Allows the ending/removing of a Task from the workflow. The workflow can be restarted from the History module if desired. Search o Opens the Document Management System Web Access Query in a separate browser window. 7

8 Column The columns display values from Document Management System and Workflow. The selection of which columns are visible and their order is managed in the Workflow Admin section. The first column is the icon. If you hover over this icon it will display a temporary preview of the first page of the document for that task. The State column provides information regarding that task. The icon identifies a task that has been reviewed and marked Pending. The icon notes that this task was sent to another user with Ad Hoc button. Ad Hoc allows the user to send a request to another user and ensure that the response is sent back to the originator. The icon identifies a Task whose document is a duplicate to another document inside Document Management System. The Admin controls which indexes determine a duplicate. Once the duplicate index field is changed then the icon disappears. The icon denotes all 'Package of Documents' Tasks are either not in workflow yet, or NOT complete based on the Workflow Indexes selected in the 'Package of Documents - Package Index' column. The icon denotes all 'Package of Documents' Tasks are either in workflow, or in workflow and complete based on the Workflow Indexes selected in the 'Package of Documents - Package Index' column. My Inbox Screen Documents which are owned by the currently logged in user can be accessed directly through their My Inbox module. Functionality of the My Inbox module is otherwise identical to the Group Box module. 8

9 Workflow Task Screen The Workflow task screen is accessed from within the Group Box or My Inbox screen. It provides the ability to view a document, the Workflow Task s history and the Document Management System and Workflow indexes. A user can create Notes for personal reference and for other individuals to view. Notes can (separate small Professional Service Work) also be captured as a separate page with the Audit information and be appended to the back of the document once the Workflow is complete. 9

10 Workflow / Document Information Tabs The Workflow Task screen provides tabs to track, add and modify indexes Index Tab This list the Document Management System and Workflow index values. Which indexes are Visible, can be Edited and the Order of the indexes are determined via Admin module. When a Document Management System index is modified in this screen it also modifies the value in Document Management System. This also works when a user is inside Document Management System and modifies a value. That value will be modified in the Workflow screen. The fields that are Workflow specific cannot be modified via the Document Management System. This data only flows one way from the Workflow system to Document Management System. Indexes that are important are colored in red. The system will allow a task to be approved if that field is empty. The red is a highlight to let the user know that they should be entering data into that field. Notes Tab Users can add notes regarding a specific workflow task. These notes are viewable by future workflow users and can be referenced in the Workflow History section. Within a document, a counter and bell icon are displayed and chimes when unread notes are available. Choosing the Reset to Unread button will mark notes as Unread until the tab is re-accessed. History Tab Users can view the history of this task. You can view who has worked on a task, the date/time of the action and the specific action. This history is viewable by future workflow users and can be referenced in the Workflow History section. 10

11 Standard Action Buttons Approve o Moves the selected Task to the next role identified in the Rules Engine. If there are no other roles then the workflow ends/completes. Terminate o Available based on individual permissions. Allows the ending/removing of a Task from the workflow. The workflow can be restarted from the History module. Pend Ad Hoc o o Close the task and mark as Pend in the GroupBox and MyInbox. The user can determine which Tasks are new and which ones they have viewed. This button is only visible when enabled by the Administrator. It allows a user to assign a Workflow Task to a specific individual (regardless of their assigned role permission) from a drop down list. Only individuals that have access to that particular Workflow will be displayed in the list. This will be represented by in the Group Box and My Inbox. Search o Doc Tracking When the person that has received the Task in an Ad Hoc format accepts the Workflow Task then it will escalate to the next level. If an individual does not belong to that role from which she received the Ad Hoc request then she will only see the Task in her InBox. This function is good for Workflows when the business rules are not clearly defined and tasks need to be manually routed. Opens the Document Management System Web Access Query in a separate browser window. This Functional Button presents a pop-up dialogue that allows the user to identify documents to track and to be notified when the documents are inside the Document Management System and if desired when those documents have gone through their own Workflow and have been completed. This needs to be added in the Admin Function Custom Buttons. 11

12 Next Screen Choice The Next Screen Choice dialog configures the behavior of the application after a document action is chosen such as Approved, Rejected, Pending, or Ad-Hoc. The Next Screen Choice can be set from any application screen, by accessing the drop-down menu in the upper-right Welcome Button. A selection is saved by closing the window. The tasks are selected by the oldest scan/import date first. Help Screen The Help Screen provides general help. Log Out The Log Out function gracefully exits the application and ensures the proper release of a consumed license. It is best practice to Log Out before exiting the browser or navigating away from the Workflow application. 12

13 History Screen The History module displays completed Tasks. History records provide information such as which users have accessed a given Task, the date/time of actions, and a description of the actions. If you have Manager or Admin Role permission you can restart a workflow. The Task will go to the first role queue for its Workflow. The previous audit history and notes will be viewable. You call also click on a row to open the actual document in Document Management System. The History Module also shows Notes and a detailed History through the same right-click menu. 13

14 ADMINISTRATIVE GUIDE Admin Module The Admin module provides access to the configuration settings required to operate the Workflow application. Best practice is to start from Workflows at the bottom and work up to Rules when creating new workflows. 14

15 Workflow Module The Workflow Module is the section that manages what values start a workflow and the general user interface feature for the workflow. When first creating a Workflow the user names the Workflow and selects which Document Management System Application and which Document Management System Index starts a workflow. 15

16 Once a Workflow is Created, or if a Workflow needs to be Edited, then you proceed to this page that provides the Admin Five more functions 1) if a workflow can start by changing the DM indexes Also Start Workflow on Index Modification, 2) determine Workflow Start Values, 3) modify Workflow Indexes, 4) create Templates, and 5) implement Custom Buttons. Also Start Workflow on Index Modification allows for workflows to start for existing records in the Document Management System when an index value is changed to match a Workflow Trigger value. If a Workflow is already active for that Document then the user will receive a Pop Message informing her of that fact. Enable Ad Hoc Makes the Ad Hoc button appear in the Workflow Task Screen for that Workflow. This button allows a user to assign a Workflow Task to a specific individual (regardless of their assigned role permission) from a drop down list. Only individuals that have access to that particular Workflow will be displayed in the list. When the person that has received the Task in an Ad Hoc format accepts the Workflow Task then it will escalate to the next level. This function is good for Workflows when the business rules are not clearly defined and tasks need to be manually routed. 16

17 Workflow Start Values This is the screen that displays the Workflow and its related Rule Names, Start Value and Start Level Workflow - The grouping of certain rules - which usually covers a Department or a group of users that have similar workflow processing needs. Rule Name The specific workflow task rule(s) that will be created. The escalation levels for each rule is managed in the other Admin Module, Rules Start Value The Document Management System Index that starts a Workflow Start Level Each workflow task will escalate in a linear fashion out of the box. The order of the workflow will follow the numeric level for each task. The levels will be based on increments of ten. There maybe points where the desired start level is 20 or higher. This occurs when you desire to have a role which normally does not participate in the workflow but may need to see a workflow task under special circumstances. The Investigation Department is a good example. 17

18 Workflow Start Values Select Add New Rules or the Edit button to opens this screen. You can add a New Rule or select an existing rule from the drop down. Assign a value to be monitored in the Document Management System application, as well as a start value. Adding a rule within this area initiates the creation of a Rule Definition, which must be further configured in the Rule Definitions module. 18

19 Workflow Indexes This section controls the Indexes in the Group Box Columns and the in the Workflow Task. Index This is the Document Management System and the Workflow indexes. You can drag and drop the rows to determine in which order the users will see the indexes. Source Identifies if the index value is being created by Document Management System or Workflow. Visible Will the field be visible to the end users. NOTE It is recommended to uncheck Document Management System fields that are Sync To Workflow fields. Please see Sync To for more information. Editable Can the end user edit the index in the Workflow Task. If they edit the index then the index value in Document Management System will be updated. Likewise if an index is modified in Document Management System then this change will be displayed in the Workflow system. NOTE/EXCPTION Indexes that are Workflow Type are not Editable and changes in value only flows from Workflow to Document Management System. Required Selecting this field turns the Index Name red in the Workflow Task screen. This lets the user know that they should complete the field. The system does not check this field though and a task can be accepted with this filed being blank. Identify Duplicate If fields are checked then the workflow system will check Document Management System to determine if there are potential duplicate records and display a note in the Group Inbox. Identify Matches - Selection of two or more indexes then searches the Document Management database and "marks" that workflow task with an icon in both the Group Box and specific Workflow Task. When one of the Index values are changed then the icon is automatically removed. Package of Documents o Key Indexes - The selection of the Index that identifies the base Index(es) to which a Package is created and tracked. For example if an Index value called "Name" was selected then documents o with the same "Name" index value can be identified to be tracked. Package Indexes - The selection of the field that holds the different document types that can exist within a package. Multi-Doc View The Document Management query result will be displayed in the Workflow Task based on the search criteria of the workflow start document plus that search index. NOTE Select Doc ID if you desire to only show the Workflow related document. AP Inv Amount This identifies the Document Management index field that represent the dollar threshold to determine if an invoice should be escalated to the next level. Sync To - Workflow Indexes Specifically Created by Workflow - Each Workflow is automatically assigned certain workflow indexes. These are values that are created by the Workflow engine based on each Workflow Task. These values can be mapped to the fields in Document Management system using the column Sync To. 19

20 IMPORTANT - A few items to note Workflow Type fields can push data to Document Management System but will not allow data from the Document Management System values to be pushed into the workflow values It is recommended that the Visible selection be unchecked for DM Type indexes that are mapped to the Workflow Type fields In the Document Management System Admin Screen the fields below should be mapped o Status should have drop down list of NEW IN PROGRESS APPROVED TERMINATED 20

21 Templates Preconfigured messages containing variable fields can be generated for document Arrival, Reminder, and Escalation. Multiple addresses may be entered by using a comma or semicolon to separate the addresses. Copying and pasting from Fields drop down allows for the addition of the variable fields into any of the dialogs. The Templates feature requires SQL Agent service running on the server to operate. 21

22 Custom Buttons JavaScript customizable buttons are available for selection within the Workflow Task Screen. For example, Yahoo could be configured as a button to allow users quick access to that website. Here is a sample Feature that you can copy and paste height=600,width=1124,modal=no,alwaysraised=yes,status=1,resizable=1,scrollbars=1 Here is the URL for Doc Tracking id% 22

23 Users Module Allows the Administrator to create, delete, and configure user based access. Access is granted when the Workflow application successfully matches the current logged in Active Directory user. User Name Last Name First Name Active Admin Terminate The end users name inside Active Directory The end user s last name The end user s first name The address to be used if the end user is to receive s from the Workflow Determines if the End User is able to participate in the Workflow process. If a User is Inactive she will not receive a workflow notifications or tasks via Round Robin distribution. Their current tasks will remain inside the My Inbox module unless the task is Reassigned to the general queue. The ability to access the Workflow Admin functions. The end user can end / remove a Workflow before it completes the routing based on the Workflow Rules. The Document Management System WF Doc Status will display as Terminate. 23

24 Roles Module Allows the Administrator to configure generic Roles that are applied during Workflow. These are not attached to a specific Workflow Category. Thus a single Role, such as Supervisor, could be used in multiple Workflow Categories. Permissions Module Allows the Administrator to create, delete, and configure permissions for a given user based access. This sections ties together Users with their Role(s) and hence determine which Workflow they can view in the Group Box. Permissions: Create, delete, and configure permissions for a given user. Clone User: Duplicate a user s setting to another user without configured permissions. Workflows Role User Exclude from Distribution Note Workflow Category for assigned permission Role for assigned permission User for which permission will be applied. Whether user should be excluded from Round Robin distribution for designated workflow. Space for administrative note, not available within the workflow process 24

25 Rules Module This section allows the creation and modification of the workflow Rules. There are two templates 1. AP Workflow Escalates based linear rules and dollar limits 2. Generic - Escalates based on linear rules only Workflow Rules Role Escalate to Role Distribution Level Notes Upon Arrival Remind / Remind # of Days Escalate / Escalate # of Days / Escalate To Drop Down from Workflow module Rule Definition that the in progress rule will apply to Current Role to escalate from The next Role required to review after the current Role None or Round Robin The order in which rules will be processed. Once it reaches the last line, it then ends the workflow and codes the Document Complete in Document Management System Notes regarding rules. This information does not display in any other screen Checkmark to enable if that Role Group will receive an when a Workflow Task arrives in a Group Inbox Determines if a reminder should be sent to the Individual that has taken ownership of that Workflow Task, but has not finished processing the task within the designated number of days Number of days after an individual has taken ownership of a record and has not completed a task. An will then be sent to the Escalate To person 25

26 The Rules Engine reads top down (in priority order) each time a workflow task is Approved. The Workflow will move to the level of review until the final row and will then become a completed Workflow Task. Priority Role Escalate To 10 Clerk Manager 20 Manager Controller 30 Manager Vice President 40 Vice President Controller Custom expressions The Rules Engine can be further customized using the Custom Expression dialog which provides the option to use VB.net scripting. It is available when editing within the Rules module by clicking the right-side drop-down arrow. The drop-down list can be used with the Copy button to paste the variable name into the edit area. 26

27 Custom Processing Integration The Rules Module Processing Integration is available from the Rules Module configuration panel screen. The panel provides hooks for custom level processing via the dropdown list items. Custom program classes can be written in Visual Studio.Net as regular.net VB.Net or C# language classes, and used within a workflow task instance. NOTE: No items will be available in the dropdown if the classes have not been created beforehand. An example custom class is provided in Appendix A. This section discusses some of the possible options available to a developer to handle custom logic for a workflow task. The custom actions can run before, during, or after given workflow tasks. These can be background related tasks, a custom user popup, or some special route level handle that cannot be accomplished through either the provided Rules templates, or Custom Expressions. A Developer can write a program class that can be hooked into the workflow either before or after a Workflow Task. The program class is compile into a DLL and the method name is provide to initialize the program logic to run. The method provide the custom actions to the workflow process. Some examples: Send an SMS text message Notify a workflow has been completed Add records to a different database, Submit records to an ERP system Ensure routing integrity (auditing). The custom program class and method can be invoked at different stages during each workflow task. A developer can choose when the integration will occur as explained below. The fourth option provides a Custom UI interface when a user is viewing a workflow item. On Arrival When a workflow first arrives in a processing queue and before the user has taken action. An example would be if an invoice arrives and the invoice amount equals the PO amount then the workflow might immediately move out of the queue and end the workflow before the user even opens the workflow task. Pre-Submit When the user selects Approve and before the workflow moves to the next queue. An example would be that the method will check that certain fields are completed before the Workflow moves to the next step. If the correct state is false then the user will receive a notification about why the workflow cannot be processed. 27

28 Post Submit After the Workflow has been Approved then action may occur. An example is that a new employee system request has been completed so the system will then send a text message to the Department Manager letting her know the process has been completed. Custom UI When the End User opens a Workflow Task they will see the Customer User Interface and not the Document Management System. They will still the Workflow Functions just not the Document Management System. This allows for users to see other Data Entry Screens when or system applications embedded inside the workflow. This same type of function can also be achieved through Custom Buttons in the Admin Role. Importing Import Workflow: Allows the Administrator to import a workflow from another Workflow environment. This feature is ideal for replicating a workflow between separate development and production environments. Begin by providing connection strings to the two SQL environments storing the Workflow applications. Upon connection, the Workflow to replicate can be chosen and the new Workflow can be named. Sample connection String: Data Source=SQLSERVER;Initial Catalog=SampleDB;User ID=SA;Password=

29 Data Importer: Allows the Administrator to quickly import Permissions, Roles, and User settings to the Workflow application. Excel templates are provided for download, and once filled can be uploaded using the Upload Templates dialog. After upload, the data is immediately validated and import status is shown. Licensing License: Allows the Administrator to configure and save the License Key. The total number of concurrent users is indicated at the top of the page as the current number of licenses. Sessions: Allows the Administrator to view the active sessions. Each username shown consumes one license and can be forcibly logged off with the Delete button. 29

30 General Settings Changes made will not take effect unless saved. Welcome message: Message to be displayed on Dashboard when users login to the application. AX Prefix: For connection to AX. Provide AX database name and associated schema. For example AX.dbo. AX Data Source: For connection to AX. Provide AX Data Source name. Your AX Web Base URL: For connection to AX. Provide Website URL for AX Web Services. Server: For Workflow notifications. Provide SMTP server name. User Name: For Workflow notifications. Provide username for authentication. Password: For Workflow notifications. Provide password for authentication. From Address: For Workflow notifications. Provide address if different from User Name. Enable Ctrl-Y For All: For account impersonation. Default is for Administrator access only, enable to allow all users to access account impersonation through Ctrl-Y shortcut key. 30

31 Other Features Audit Page The workflow can also be configured to create an audit page an attach it to the back of the document that triggered the workflow. This is a Professional Service Engagement of one or two days. 31

32 Custom Development Integration Sample The Rule Module provides options to allow for custom actions to run before, or after given workflow tasks. These can be background related tasks, a custom user popup, or some special route level handle that cannot be accomplished through either the provided Rules templates, or Custom Expressions. Creating the Custom Actions. 1. Start a new project or solution in Visual Studio (2008 or newer). 2. Create a new Class Library 3. Enter a desired class name 4. Set the namespace the same as the class name. 5. Enter the desired method name - Its signature should be as in the following format (VB.Net example method SetLevel) Public Function SetLevel(ByVal staskid As String) As clscustomactionresponse NOTE: The Task Id is passed in as a parameter. This allows for retrieval of any associated data from the database. Define the clscustomeractionresponse class Public Class clscustomactionresponse Public slog As String Public ilevel As Integer Public buselevel As Boolean Public berror As Boolean Public serrormessage As String End Class NOTE: This class is returned to the workflow process to determine execution of the task. Set buselevel to false. - Returns from the method does not alter the Tasks workflow level - The workflow s normal approval engine will be invoked to determine the next level. Set buselevel to true, and set ilevel to the desired level. - Returns from the method and alters the Tasks workflow level - The workflow s normal approval with not be invoked. - The Task level must exist configured in the Rule Definition Set berror to true, and message in serrormessage. - Returns from the method and display a message to the user - The workflow s normal approval engine will not be invoked 32

33 Example Custom Action Start Level Based on Document Management System Field and Value The following is an example of a Custom Action that has been designed to alter the Start Level for incoming Tasks based on the Document Management System index field and its value. The Custom Action would be configured to a level 10 Rule, On Arrival. Imports System.Data.SqlClient Imports System Imports Microsoft.VisualBasic Imports System.IO Public Class clsonarrival Private m_slog As String = "" Public Function SetLevel(ByVal staskid As String) As clscustomactionresponse StatusMsg("SetLevel Starting...") Dim ocustomactionresponse As clscustomactionresponse = New clscustomactionresponse Try StatusMsg("sTaskId : " & staskid) Dim odt As DataTable = GetTask(sTaskId) If odt.rows.count = 1 Then '--- get the ax rec based on doc id Dim odtaxrec As DataTable = GetAxRec(oDT.Rows(0).Item("DocId").ToString) If odtaxrec.rows.count = 1 Then '--- is this the vendor we are looking for If IsDBNull(oDTAxRec.Rows(0).Item("field7")) Then '--- must not be StatusMsg("Field7 is Null") ocustomactionresponse.slog = m_slog ocustomactionresponse.berror = False ocustomactionresponse.serrormessage = "" ocustomactionresponse.ilevel = 0 ocustomactionresponse.buselevel = False Else If odtaxrec.rows(0).item("field7").tostring = "787" Then StatusMsg("Field7 is 787") ocustomactionresponse.slog = m_slog ocustomactionresponse.berror = False ocustomactionresponse.serrormessage = "" ocustomactionresponse.ilevel = 20 ocustomactionresponse.buselevel = True Else '--- not 787 StatusMsg("Field7 : " & odtaxrec.rows(0).item("field7").tostring) ocustomactionresponse.slog = m_slog ocustomactionresponse.berror = False ocustomactionresponse.serrormessage = "" ocustomactionresponse.ilevel = 0 ocustomactionresponse.buselevel = False End If End If Else StatusMsg("Didn't find AX rec for DocId : " & odt.rows(0).item("docid").tostring & " : row count : " & odtaxrec.rows.count) ocustomactionresponse.slog = m_slog ocustomactionresponse.berror = True ocustomactionresponse.serrormessage = "Didn't find AX rec for DocId : " & odt.rows(0).item("docid").tostring & " : row count : " & odtaxrec.rows.count ocustomactionresponse.ilevel = 0 ocustomactionresponse.buselevel = False 33

34 End If Else StatusMsg("Didn't find Task ID : " & staskid & " : row count : " & odt.rows.count.tostring()) ocustomactionresponse.slog = m_slog ocustomactionresponse.berror = True ocustomactionresponse.serrormessage = "Didn't find Task ID : " & staskid & " : row count : " & odt.rows.count.tostring() ocustomactionresponse.ilevel = 0 ocustomactionresponse.buselevel = False End If Return CType(oCustomActionResponse, Object) Catch ex As Exception ocustomactionresponse.berror = True ocustomactionresponse.serrormessage = "Error in clsonarrivalsetlevel :: SetLevel : " & ex.message Return ocustomactionresponse End Try End Function Public Function GetTask(ByVal staskid As String) As DataTable Try Dim odt As New DataTable Dim oconn As SqlConnection = New SqlConnection(My.Settings.Item("DbConn").ToString) oconn.open() Dim ocommand As New SqlCommand("Tasks_GetByTaskId", oconn) ocommand.commandtype = CommandType.StoredProcedure ocommand.parameters.addwithvalue("@task_id", staskid) Dim oreader As SqlDataReader = ocommand.executereader odt.load(oreader) oconn.close() Return odt Catch ex As Exception Throw New ApplicationException("Error in GetTask : " & ex.message) End Try End Function Public Function GetAxRec(ByVal sdocid As String) As DataTable Try Dim odt As New DataTable Dim oconn As SqlConnection = New SqlConnection(My.Settings.Item("DbConnAx").ToString) oconn.open() Dim ocommand As New SqlCommand("select * from ax.dbo.ae_dt9 where docid = " & sdocid, oconn) ocommand.commandtype = CommandType.Text Dim oreader As SqlDataReader = ocommand.executereader odt.load(oreader) oconn.close() Return odt Catch ex As Exception Throw New ApplicationException("Error in GetAxRec : " & ex.message) End Try End Function Private Sub StatusMsg(ByVal smsg As String) m_slog = m_slog & Now.ToShortTimeString & " " & smsg & vbcrlf If My.Settings("Debug").ToString = "On" Then Dim ofile As System.IO.StreamWriter Dim sfilename As String = My.Settings.Item("serverPath").ToString & "Debug\debug_customactions.txt" ofile = My.Computer.FileSystem.OpenTextFileWriter(sFileName, True) If smsg.tolower().contains("starting") Then ofile.writeline(vbcrlf & Now.ToString("yyyy-MM-dd hh:ss:mm") & " " & smsg) Else ofile.writeline(now.tostring("yyyy-mm-dd hh:ss:mm") & " " & smsg) End If ofile.close() End If End Sub 34

35 Public Class clscustomactionresponse Public slog As String Public ilevel As Integer Public buselevel As Boolean Public berror As Boolean Public serrormessage As String End Class End Class GL Coding Button A GL Coding Button can be added for AP Workflows. The data can be pulled from a view table, multi-indexes into Document Management System and then submitted into the ERP. 35