1. Financials Version 11.2 March 2016

2. Accounts Payable

3. © Tyler Technologies 2015 3 Jira Issues: MUN-229699, MUN-228408 Purpose: To create custom layouts for invoice imports and check exports. Description: Export Checks, Invoice Import The Custom Templates option provides a template program for creating a custom template for your import or export files. When you save a template, it is available from the template list whenever you use the Custom Template option.

4. © Tyler Technologies 2015 4 Export Checks, Invoice Import

5. © Tyler Technologies 2015 5 Jira Issue: MUN-211857, MUN-231437 Purpose: To allow purchase order liquidation updates for unposted invoices. Description: For unposted invoices, the Re-Liquidate option allows you to access the PO Liquidation screen and update the liquidation details. Invoice Entry The Re- Liquidate is only available when valid liquidation records exist for an invoice.

6. © Tyler Technologies 2015 6 Jira Issue: MUN-210703 Purpose: To expand the number of detail items available on an invoice. Description: Invoice Detail accepts up to 999 detail lines for a single invoice; this applies to imported and manually entered invoices. Invoice Entry, Modify Invoices

7. © Tyler Technologies 2015 7 Jira Issue: MUN-224081 Purpose: To allow updates to existing purchase card statements according to status. Description: In Roles-Accounts Payable, the Allow Update of Purchase Card Transaction At or Below Status setting manages update permissions according to status. Purchase Card Statements, Workflow Business Rules

8. © Tyler Technologies 2015 8 Permissions: Controls the statement status levels when a user updates a purchase card transaction (PCT) on a statement. Does not override the existing P-card permissions that control whether a user can maintain his or her own and others’ P-cards and statements. Works in conjunction with the existing permissions. For example, to update another’s P-card statement that is Released, the user must have permissions to update others’ purchase cards and statements (either full permissions, or appropriate department-based permissions) and have permission to update PCTs on statements at or below the Released or Approved status levels. Purchase Card Statement: Uses the new permissions when determining whether a user can update a purchase card transaction. The update of a PCT can be a regular update of the PCT or its allocations, the allocation of a PCT with a code, or the liquidation of a PCT with a purchase order. With the appropriate permissions, users can update a PCT that is approved. Purchase Card Statements, Workflow Business Rules

9. © Tyler Technologies 2015 9 In Workflow Business Rules, the APC Process Code includes the Allow Munis Changes Without Restart setting. If enabled, transactions on released purchase card statements whose current workflow step is at the rule can be updated without causing a restart of the workflow process. For example, if a statement is released, and at a step that uses an APC rule for which this check box is selected, the user can update the GL allocations on a PCT on the statement without causing a workflow restart. If not enabled, allocation changes trigger a restart of workflow. Purchase Card Statements, Workflow Business Rules

10. Vendor Self Service (VSS)

11. © Tyler Technologies 2015 11 Jira Number: MUN-118725 Purpose: To allow vendors to submit invoices directly from VSS. Description: If the Allow Invoice Submissions check box is selected on the Vendor page for User Administration, vendors can submit invoices for payment using Vendor Self Service. When this permission is enabled, the Invoices group on the vendor’s home page in VSS includes the Submit Invoices option. Invoices

12. © Tyler Technologies 2015 12 The Submit Invoices option guides the vendor through the submission process. Invoices

13. Budgeting

14. © Tyler Technologies 2015 14 Jira Issue: MUN-227363 Purpose: To provide more efficient search and review options. Description: For each program, provides segment find capabilities when you click Search, and provides the option to produce an Excel spreadsheet for review prior to updating. Budget Multiyear Recalc Utility, Load Historical Tables The Post Updates option applies the actual changes to the general ledger data.

15. © Tyler Technologies 2015 15 Jira Issue: MUN-227363 Description: Multi Year accounts - The Expense Accounts Always Roll Available Budget Forward and Revenue Accounts Always Roll Available Budget Forward settings specify whether to roll available budget forward if no budget has been established. Budget Settings, General Ledger Open New Fiscal Year

16. © Tyler Technologies 2015 16 Jira Issue: MUN-218772 Purpose: To provide a default value for budget amendments. Description: In Budget Settings, the Default Budget Projection Inclusion list identifies a default value for all new amendments. Budget Settings, Budget Transfers and Amendments One-time (temporary) budget amendments can be excluded from budget projections. Continuing amendments are included in budget projections.

17. © Tyler Technologies 2015 17 The Budget Transfers and Amendments program completes the Budget Projection Inclusion field for each new journal with the default value from Budget Settings, but you can change this, as required. The Update Recurring Journal check box indicates if the journal is related to a recurring journal in Munis; this was formerly identified using the Special Conditions field. Budget Settings, Budget Transfers and Amendments

18. Cash Management

19. © Tyler Technologies 2015 19 Jira Issues: MUN-229454, MUN-229423, MUN-229479 Purpose: To facilitate improved reconciliation between bank and Munis accounts. Description: Bank Reconciliation allows your organization to reconcile bank account balance activity to general ledger balance transactions within Munis using Bank Administration Institute (BAI) transaction data. Bank Reconciliation Within Munis, to complete bank reconciliation using BAI imports, you must have access to the Bank Codes, BAI Import, and Bank Reconciliation Manager programs.

20. © Tyler Technologies 2015 20 Bank Codes For the Bank Reconciliation process using the BAI Import, only Munis accounts that are associated with bank accounts within the bank account setup are used. Before accounts can be linked, you must create a bank code record with the Use BAI option selected. Bank Reconciliation Once you have created the bank code record, use the Accounts option to link the account to Munis accounts.

21. © Tyler Technologies 2015 21 BAI Import The BAI Import program facilitates the import of BAI files as a one-time process or as a delayed/repeat process using Munis Scheduler. The import parses BAI files and stores the transaction information for use within the Bank Reconciliation Manager program. The import process auto-matches transactions (checks and deposits) based on specified criteria, and in the case of checks, clears them within Munis during the import. Bank Reconciliation

22. © Tyler Technologies 2015 22 Bank Reconciliation Manager The Bank Reconciliation Manager program provides an overview of all matched and unmatched bank transactions that have been imported, and allows you to complete the matching process, and then submit the reconciliation changes for approval. Bank Reconciliation Overview  Provides details for Cash on Hand and Unmatched Items. Match  Provides options for reconciling the Munis and Bank Records. Reconcile  Defines the reconciliation time period, allows you to correct any final items, and to release the actions to workflow for approval.

23. Contract Management

24. © Tyler Technologies 2015 24 Jira Issue: MUN-157955 Purpose: To ensure that encumbered contract amounts that are rolled to the next year are identified as CFWD for reporting and accounting purposes. Requirements: The Holding Current Year Open check box must be selected in General Ledger Settings. Once the Close Current Year and Open New Fiscal Year processes are complete, the amount is available for the new year. Contract Entry, Requisition Entry, Purchase Order Entry, Invoice Entry, Other Miscellaneous Financials Programs

25. © Tyler Technologies 2015 25 Description: Contract amounts rolled into the next fiscal year track as carry forward amounts, and the amounts are tracked and deprecated when the contract is referenced or liquidated on purchasing transactions. The Holding Current Year Open check box must be selected in General Ledger Settings. Once the Close Current Year and Open New Fiscal Year processes are complete, the amount is available for the new year. Contract Entry, Requisition Entry, Purchase Order Entry, Invoice Entry, Other Miscellaneous Financials Programs

26. © Tyler Technologies 2015 26 Jira Issue: MUN-223694 Purpose: To maintain and track contract carry forward monies allocated to purchase orders associated with contracts. Description: The programs accurately maintain and track contract carry forward monies when these monies are allocated to purchase orders associated with contracts: For contracts that are fully rolled to the next year, open purchase order amounts from prior years are identified as carry forward purchase order amounts on the Contract Amount lines and the PO Allocation lines. When purchase orders associated with contracts are maintained, any PO allocation lines with amounts identified as contract carry forward purchase order dollars update those carry forward amounts on both the Contract and the PO allocation, as applicable, according to the update made to the PO allocation line. Contract Change Orders, Purchase Order Change Orders

27. © Tyler Technologies 2015 27 Jira Issue: MUN-229555, MUN-231609 Purpose: To allow payments against contracts as work progresses. Description: The program allows you to enter and submit payments against contracts as work progresses, upon the basis of costs incurred, on a percentage of completion to- date, or on a particular state of completion. Contract Progress Payments

28. © Tyler Technologies 2015 28 The program allows you to indicate the lines and accounts that should be directly liquidated and paid for by accounts payable. The CPP-Contract Progress Payments process code supports contract progress business rules. Once a progress payment has been approved, it automatically generates an AP invoice that flows through the Accounts Payable process for payment. Contract Progress Payments

29. © Tyler Technologies 2015 29 Jira Issue: MUN-231609 Purpose: To support approvals for contract progress payments. Description: The CPP-Contract Progress Payments process code is available for contract management business rules. Contract Management Workflow

30. © Tyler Technologies 2015 30 For business rules using this process code, the approval process is enabled for the approval of contract progress payments. You can generate workflow for progress payments for the following rule types: AMT-Total Amount CHK-Checklist NOT-Notification Only OVR-Over Budget (GL), PE1-PA Segment and Amount (Expense) PE2-PA Segment and Over Budget (Expense) PEO-PA Over Budget (Expense) PES-PA Segment (Expense) PET-PA Amount (Expense) Contract Management Workflow PF1-PA Segment and Amount (Funding) PFS-PA Segment (Funding) PFT-PA Amount (Funding) SEG-GL Segment SEO-GL Segment and Over Budget SOA-GL Segment Amount VEN-Vendor VER-Verify Contract Type Contract Subtype

31. Fixed Assets

32. © Tyler Technologies 2015 32 Jira Issue: MUN-230077 Purpose: To provide visual images for asset records. Description: Fixed Assets and Work Order Asset records can contain images be uploaded from your personal computer directory or a networked directory. Fixed Assets, Work Order Assets

33. © Tyler Technologies 2015 33 For fixed assets, in the New Assets or the Adjustments and Retirements program, the Images tab stores the uploaded image. Fixed Assets, Work Order Assets

34. © Tyler Technologies 2015 34 For work order assets (that is, Equipment Assets, Facility Assets, and so on), the Images tab controls access to the asset image and also displays the full image. The Asset Detail group displays a thumbnail image. Fixed Assets, Work Order Assets

35. General Ledger

36. © Tyler Technologies 2015 36 Jira Issue: MUN-226020 Purpose: To support monthly budgeting for the next year. Description: The Monthly Budget Amounts program allows you to initiate and view monthly budget transfers. Monthly Budget Amounts

37. © Tyler Technologies 2015 37 The Original Budget, Transfers/Amendments, Revised Budget, Actuals, and Percent Used detail fields provide a breakdown of monthly budgeting and spending versus budget for a specific account. Use the available options to manage the budget data: Reallocation—Initiate the transfer of the budget across months, which refreshes the screen to display the updated amounts. Create Journals—When you are certain the adjustments entered are correct, post budget transfer journals in the periods affected. Mass Update—Adjust an active set of accounts’ monthly budget using percentages, and then generate the transfer journals to update amounts. If the Allow for Budget Reserves parameter is selected in Budget Settings, the program allows for reserving a budget in period 13. Reserving budget creates BUA journals, with budget amounts being removed from one or more periods and reallocated to period 13. Monthly Budget Amounts

38. © Tyler Technologies 2015 38 Additionally: Monthly Budget Amounts In Next Year Budget Entry and Central Budget Entry, you can establish monthly budget amounts by fiscal period. For accounts for which the Allow Monthly Budgeting check box is selected in Account Master, budget detail may be entered with a designated period to which to post the original budget. Post to Master for Reports creates a soft post of the Next Year budget and places the respective amount in the appropriate period. When the projection is posted, a BUC journal is posted in each period for the amount designated in the budget projection detail records. The total Original Budget remains the total amount budgeted for the account, but the monthly budgeted amounts is reflected in the respective periods.

39. © Tyler Technologies 2015 39 Jira Issue: MUN-232626 Purpose: To provide budget-to-actuals variance and comparison to last year and year-to-date amounts. Description: The Monthly Budget Report is available on the Munis > Financials > General Ledger > Inquiries and Reports menu. Monthly Budget Report

40. © Tyler Technologies 2015 40 This SSRS report provides budget-to-actuals variance data for a specified period. The report also shows a comparison to last year and year-to-date amounts. Monthly Budget Report

41. © Tyler Technologies 2015 41 The Search for Accounts option makes the Account Search fields accessible, and the Define Report Parameters establish the report settings. Monthly Budget Report

42. © Tyler Technologies 2015 42 The Forecasting Method list utilizes projected actuals formulas to display budget versus projected actual amounts. Monthly Budget Report

43. © Tyler Technologies 2015 43 Jira Issues: MUN-225640, MUN-229433 Purpose: To eliminate the concept of open journals, having posted transactions update the Monthly Amount tables when journal records are created. Description: All posted transactions update the Monthly Amount tables when the journal records are created, eliminating the need to complete the Month End Process program, which is replaced by the Month End Manager program. Reports do not require you to complete a process in order to view posted transactions, and the updated processes allow you to better budget monthly amounts and report on those figures. Multiple Financial Programs

44. © Tyler Technologies 2015 44 Specifically: The Monthly Amounts table is updated at the time a journal is posted to the general ledger. Previously, the monthly amounts were updated by the month end process, which also moved the journals from an Open status to the History status. With this enhancement, all journals are posted to the History status and monthly amounts are updated immediately. This eliminates the need to run the Month End Process; Account Actuals and Monthly Balances are updated when the journal is posted. Monthly Budgeting is simplified and improved. If your organization budgets on a monthly basis, Next Year Budget Entry and Central Budget Entry allow the budget detail to specify the period to which the budget applies. Monthly budget transfers are initiated through the Monthly Budget Amounts program and create transactions to represent the transfer between periods. This further improves the reliability of this data. Multiple Financial Programs

45. © Tyler Technologies 2015 45 Jira Issue: MUN-225640, MUN-227804 (open 1/7/18) Purpose: To provide month end process Description: The Month End Manager program allows you to establish a Closed date for each period. It supports the ability to roll the Current Period forward upon closing of that period. Month End Manager

46. © Tyler Technologies 2015 46 For each period, the program displays up to four possible inquiry results: Unposted Journal—Provides lists of all unposted transactions by the transaction type. For example unposted journals, purchase orders, contracts, invoices, requisitions, and so on. All the unposted transactions that are queried in Table Validation are also represented here. Open Journals—Provides a list of all journals that have been posted after the period’s closed date. If a period has not been closed, then all posted journals show in this inquiry. Once the period has been closed, only journals posted after this date will be displayed. This replaces the previous Table Validation functionality that listed open journals. Month End Manager

47. © Tyler Technologies 2015 47 Unbalanced Journals—Provides the inquiries that display journals that are out of balance based on both net debits and credits, as well as expenses to expenditure control or revenues to revenue control. This functionality previously existed in Table Validation, but now displays for the entire period regardless of the journal’s posted date with respect to closed date for the period. Unbalanced Funds—Provides the inquiries that display funds that are out of balance based on both net expense versus revenue, as well expense actuals to expenditure control and revenue actuals to revenue control. This functionality remains in Table Validation, but is replicated here. Month End Manager

48. Inventory

49. © Tyler Technologies 2015 49 Jira Issue: MUN-210047 Purpose: To provide workflow approval processing for inventory adjustments. Description: In Workflow Business Rules, the INA-Inventory Adjustment Approvals process code available. Inventory Transactions, Workflow Business Rules

50. © Tyler Technologies 2015 50 Workflow business rules can be defined for inventory adjustments based on any combination of location (warehouse location), inventory reason codes, the adjustment's item number (or item number range), and/or general ledger account segments (or segment range). Adjustment approvals can be managed directly from the Inventory Transactions > Adjustments screen or from the Approvals web part on the Tyler Dashboard. Inventory Transactions, Workflow Business Rules

51. © Tyler Technologies 2015 51 Jira Issue: MUN-210046 Purpose: To provide conversion criteria for requisitions and purchase orders. Description: When the Replenish Items Warehouse Stock Via Requisitions, Purchase Orders, or Both permission is enabled in the Roles-Inventory program, and you have permission to either Add New Reqs (Requisitions) or Add Open POs (Purchasing), the Convert Criteria group is available when you use the Convert option in the Item Reorder Report program. Item Reorder Report

52. Purchasing

53. © Tyler Technologies 2015 53 Jira Issue: MUN-224607 Purpose: To create a single requisition for items commonly purchased together. Description: Within Munis Purchasing, the Order Form Classifications and Item Order Forms programs are available on the Setup menu. Using these programs, you can define order form classifications and create order forms for commonly requested items. On the Processing menu, the Item Order Forms Requests program allows you to create a requisition directly from an order form. Order Form Classifications, Item Order Forms, Item Order Form Requests

54. © Tyler Technologies 2015 54 The Order Form Classifications program provides hierarchal classifications and definitions for Item Order Forms. Assigning a classification to each form allows you to identify forms efficiently. Order Form Classifications, Item Order Forms, Item Order Form Requests

55. © Tyler Technologies 2015 55 The Item Order Forms program establishes order forms for groups of items commonly purchased. Using this program, you can define item order forms consisting of items available in the Items program. Order Form Classifications, Item Order Forms, Item Order Form Requests

56. © Tyler Technologies 2015 56 The Order Form Requests program, which is similar to the Item Order Forms program, provides the option of creating requisitions using a standard order form and then creating the actual requisition without exiting the program. Order Form Classifications, Item Order Forms, Item Order Form Requests

57. © Tyler Technologies 2015 57 Jira Issue: MUN-202338 Purpose: To facilitate the review process for web services imported from third parties. Description: The Third Party Interface Settings tab includes the Save Proof Report for Imported Web Service Purchase Orders at Status Posted setting. This setting is enabled by default and only impacts third-party web services. If you accept the default setting of enabled, a proof report is created. If you disable this setting, the proof report is prevented from being generated. Purchasing Settings

58. © Tyler Technologies 2015 58 Jira Number: MUN-227842, MUN-234403 Purpose: To allow multiple requisitions to be merged into a single bid. Description: Multiple requisitions can be merged into a single Munis bid. When you elect to place requisition items on a bid, the program provides a prompt allowing you to create a new bid or add the items to an existing bid. Requisition Entry, Requisitions

59. © Tyler Technologies 2015 59 Existing bids must be at the Bid Preparation phase in order to be available for selection. If you select Create New Bid, the Bid Central program opens. Requisition Entry, Requisitions

60. Work Orders, Fleet and Facilities

61. © Tyler Technologies 2015 61 Jira Issue: MUN-215084 Purpose: To support class codes as asset search criteria. Description: The Class Code field specifies the asset class for asset records. When you assign the user-defined field to an asset, you can use the Class Code on the User Defined tab as search criteria. When you are searching for a specific asset record and you specify a class code, the search results exclude assets that do not include the defined class code. Asset User Defined Fields

62. © Tyler Technologies 2015 62 The list of user-defined fields that display for an asset record are those fields that are specific to the asset type and department, in addition to those fields specific to the asset class. This allows for both department-specific fields, as well as asset class-specific fields, to display in the same list. Asset User Defined Fields

63. © Tyler Technologies 2015 63 Jira Issue: MUN-224297 Purpose: To support the import process with customized layout files. Description: The Customer Format option defines import layout file. Fuel Usage Import Selecting this option allows you to create a custom fueling system import format using the Template Editor, a visual editing tool. Once created, you can use the import file to complete the Work Order Fuel Import process.

64. © Tyler Technologies 2015 64 Jira Issue: MUN-215085 Purpose: To provide employee time-tracking by work order. Description: The program provides an interface for maintaining employee time for selected work orders. The user interface program captures the employee number, work order and task numbers, and provides the Start/End time options. Work Order Employee Time Tracking When an employee begins a work order, he or she completes the fields and clicks Start Time. When the task is completed, he or she clicks End Time.

65. © Tyler Technologies 2015 65 Jira Number: MUN-162666 Purpose: To support the equipment rental process. Description: The Work Order Asset Rental program manages your rental fleet. The program allows you to make reservations, check equipment in and out, and include the rental equipment use in the interdepartmental billing process. Work Order Asset Rental

66. System Administration

67. © Tyler Technologies 2015 67 Roles – Financials ModuleField NameDescription Financials Accounts Payable MUN-224084 Allow Update of Purchase Card Transaction at or Below Status Controls the statement status levels when a user updates a purchase card transaction (PCT) on a statement. The status options are New, Released, and Approved. Users assigned this permission can only update purchase card transactions up to the defined status level. The default status is New. MUN-218147 Allow Entry of Replacement Invoices Grants permission for users to create replacement invoices. The default value for this permission is not enabled. MUN-229457Access to Invoice NotesDetermines if the user can add or maintain notes for invoices: Full, Add/Update Only, None. The default value for the field is none.

68. © Tyler Technologies 2015 68 Roles – Financials Contract Management MUN- 227576 Maintain Own Posted Contracts Prior to Release Maintain Own Posted Contracts After Release Provides individual permission for maintaining posted contracts before and after release. These permissions replace the previous single Maintain Own Posted Contracts permission. MUN- 227576 Maintain Others' Contracts After Release Maintain Others' Posted Contracts Prior to Release Maintain Others' Posted Contracts After Release Create Contract Progress Payments Update Contract Progress Payments Delete Contract Progress Payments View Contract Progress Payments For each data access category, you can assign the Full, Limited, or None permissions. The default value for the new Data Access permissions is None. When you select Limited, you can restrict permissions to specific departments.

69. © Tyler Technologies 2015 69 Roles – Financials Fixed Assets Capitalized Assets Non-Capitalized Assets Separates permissions for managing assets into the Capitalized and Non-Capitalized categories. As a result, you can assign role permissions in each category, independent of the other category. This change provides additional control over assets posting to the general ledger. Programs affected include Depreciation Recalculation, Depreciate Assets, Fixed Asset Transaction Entry Post, New Assets, Adjustments and Transfers, Fixed Asset Work File, and Depreciation Reversal. MUN- 228729MUN- 230123 Post Asset TransactionsGrants users permission to post capitalized fixed asset transactions. The default value is not selected. In addition, permissions are sorted according to capitalized and on-capitalized assets. The available permissions for each group are identical, allowing you to assign varying permissions for each asset type.

70. © Tyler Technologies 2015 70 Roles – Financials Inventory MUN-222891 Replenish Item Warehouse Stock Via Determines how a user can replenish items in a warehouse: Purchase Order, Requisition, Both, or None.

71. © Tyler Technologies 2015 71 Roles – Financials Purchasing MUN-215682 MUN-211857 Close/Cancel Posted POs Defines a user's ability to close or cancel purchase orders. Specifically, this permission determines access to the Close PO, Cancel PO, Mass Close PO, Mass Cancel PO, and Cancel by GL menu options in Purchase Order Change Orders. Options are Full (can cancel or close any), None, (cannot cancel or close any), or Limited. When you select Limited, the user is restricted to closing or cancelling purchase orders only for the departments defined on the Data Access screen. The default value is set according to the value of the Maintain Others' POs. If that permission is assigned to a user, the Close/Cancel Posted POs value is Full; if that permission is not granted, the Close/Cancel Posted POs value is None. The Close/Cancel Posted POs permission checks permissions against the department of the purchase order being viewed. With full permissions, or limited permissions for the department associated with purchase order, users can access all of the Close and Cancel actions on the menu. Without the permissions, the Close and Cancel options are not accessible.

72. © Tyler Technologies 2015 72 Roles – Financials Item File MUN-225137  Add Item Order Forms  Update Item Order Forms  Delete Item Order Forms  Create Item Order Form Requests Grant users full permissions for these activities, no permissions for these activities, or limits these activities to specific purchasing departments. The default value for these data access permissions is None. MUN-225137  Restrict to Updating Own Order Forms  Restrict to Deleting Own Order Forms  Restrict to Creating Order Form Requests from Own Order Forms Restricts a user to managing only those order forms that they have created. The default value for these check boxes is not selected.

73. © Tyler Technologies 2015 73 Roles – Financials Requisitions MUN- 230084 Allow Conversion of Requisitions to Contracts Works with the Allow Creation of Contracts from Requisitions setting in Contract Settings. When that setting is enabled, the program verifies the status of the Allow Conversion of Requisitions to Contracts permission:  If this permission is enabled, the user has access to the Convert To field in Requisitions and is able to identify requisitions for conversion to a purchase order or a contract.  If this permission is disabled, the user does not have access to the Convert To field in Requisitions. When the user enters a new requisition, the Convert To value is automatically set to a purchase order. When updating an existing requisition, the Convert To field is not accessible.

74. Munis Menu

75. © Tyler Technologies 2015 75 The Centrals option is removed from the Other Applications menu and programs formerly known as Central programs are available on the menu for the applicable products. See the Munis Major Enhancements 11.2 Financials document for a list of programs and their new locations on the Munis Financials menus. Munis Menu

76. Workflow

77. © Tyler Technologies 2015 77 Jira Issue: MUN-232180 Purpose: To provide flexibility for managing the approval and forwarding processes. Description: In the Workflow User Attributes program, the Forwarding Changes option improves the flexibility for workflow approvals and forwarding. Using Selective Forwarding, you can establish forwarding for specific process codes: Forward approval items for certain process codes, while retaining the no- forwarding status for other codes. Forward all items for an approver. Forward items for all process codes. The Workflow Automated Start/Stop Forwarding fields allow you to begin and end workflow forwarding for specified times. Workflow User Attributes, Workflow Settings

78. © Tyler Technologies 2015 78 Workflow User Attributes

79. © Tyler Technologies 2015 79 In Workflow Settings, the Excluded Processes tab allows you to exclude workflow actions from being available in web parts or mobile applications. Workflow Settings

80. Tyler Dashboard

81. © Tyler Technologies 2015 81 Jira Issue: DSH-2301 Purpose: To provide quick access to Tyler University and the Tyler Community from the Dashboard. Description: The My Tyler menu on the main Dashboard page provides quick access to Tyler University and the Tyler Community. My Tyler

82. © Tyler Technologies 2015 82 TylerU – Provides access to your Tyler University courses and course transcripts, and includes a link that you can use to enroll in new courses. Tyler Community – Provides access to Tyler’s user-driven online software support community. My Tyler

83. © Tyler Technologies 2015 83 Jira Issue: DSH-2299 Purpose: To add education plans and transcripts to the Tyler University pages. Description: The Tyler University group on the Dashboard ribbon includes links for Enroll, My Courses and My Transcript: Enroll – Complete your TylerU course registration. My Courses – Preview course descriptions and take a course. My Transcript – Review courses taken, completion dates, and scores. Tyler University

84. © Tyler Technologies 2015 84 Jira Issue: DSH-2213 Purpose: To enhance the Tyler University login process and improve course sorting. Description: Login does not require that you provide credentials each time you view course content. Entering credentials can be completed directly from the Curricula or Enrolled Courses pages. Classes are labeled by version and provide information on classes specific to your Tyler product version. Enrolled Courses sorts by curricula and then course title, but you can reorder sorting by clicking column headers. Tyler University

85. © Tyler Technologies 2015 85 Added: o Accounts Payable - Expired Vendor Certificates o Work Orders - Preventative Maintenance, Internal Requests, Citizen Requests o Utility Billing - Top Consumption Accounts o Human Resources - Terminated, New Hires Removed: o Class Statistics o eLearning o Staffing Relabeled: Exceptions to Scheduled Evaluations In addition, many web parts were converted to the tile format. Tyler Dashboard Web Parts for Munis