Munis Revenues. Major Enhancements Munis April For more information, visit

Transcription

1 Munis Revenues Major Enhancements Munis April 2018 For more information, visit

2 TABLE OF CONTENTS Munis Revenues... 4 Tyler Hub... 4 New TylerForms Functionality New TylerForms Functionality Tyler University Accounts Receivable Aging Report Assess Late Fees, Payments Report, Reversals Report, Detail Receivables by Date Bill Inquiry Bill Inquiry, Contract Entry Charge Codes Customers, Apply Deposits Receipts Inquiry, Bill Refund Processing Detail Receivables by Date Over Short Adjustment Process Payment Entry, Bill Inquiry Accounts Receivable Settings, Payments Report Tyler Cashiering/Accounts Receivable Tyler Reporting Services Views General Billing Apply Deposits Charge Codes General Billing Settings, Recurring Invoices Invoice Inquiry, Invoice Entry and Proof Print Statements Permits and Code Enforcement Inspection Types, Inspection Entry Inspection Types, Field Inspector Mobile Application Revenues Page 2

3 Utility Billing Backflow Tracking Current Read/Consumption Utilities CSS Business Licenses System Administration Munis Hosting Roles General Revenues Property Revenues System Settings Tyler Reporting Services Views Workflow Business Rule Export and Import Revenues Page 3

4 Munis Revenues This document provides an overview of the major Revenues enhancements for Munis In addition to product-specific changes, this document also provides a summary of major enhancements for Tyler Hub and Tyler University. For each major enhancement, the document provides the Jira number, a brief purpose statement, and the estimated PACE training time. PACE is the Tyler Planned Annual Continuing Education (PACE) program that supports your organization with ongoing education designed to provide your staff with up-to-date training on new features and functions. For more information on PACE for Munis, contact your account representative. When reviewing PACE details, please keep in mind that sessions are scheduled in four-hour increments. Tyler Hub Tyler Hub is a central application that brings together permissions-based data from multiple places, offering pages that target the tasks you perform daily. It provides options to change the way you view data, and it features a variety of visualizations that help organize data to make it more meaningful. Tyler Hub also provides access to your Tyler Menu and Tyler University. Estimated PACE Training Time: 1 day to review functionality; 2-3 days to fully implement The Tyler Menu is accessible from the Apps button in the omnibar. Revenues Page 4

5 Tyler Hub is made up of pages, which provide data on cards. For example, the Invoice Trending page features the Paid Invoices cards, the Payment Trends card, the Invoices Recently Paid card, and the Payment Trends: What Vendors Have Been Paid? card. Different visualization options are available to display card data in a variety of ways. Revenues Page 5

6 The View/Output Data option provides the underlying data in a table format, which can be sorted, searched, filtered, or output as various reports. The Output Data option allows you to export the data as a PDF, Excel, or CSV file. Revenues Page 6

7 Links to individual records display the record details in applicable programs. The following table provides descriptions of major enhancements in Tyler Hub. Jira Number Program/Feature Description HUB-426 Card Designer Available data feeds display in the Card Designer dialog box based on the applications included in your hubconfiguration.config file. HUB-425 Tyler Menu Menu placeholders for EnerGov and New World ERP solutions are added to the Tyler Menu. HUB-421 Content Library The Content Library is updated to group cards, pages, and content packs by facets (used to categorize and filter content so only relevant choices display), according to the format Solution > Product > Functional Area > Module: On the Cards tab, cards are grouped by Functional Area. Each card displays the associated Functional Area > Module. On the Pages tab, pages are grouped by Functional Area. Each page displays the associated Functional Area > Module. On the Content Packs tab, content packs Revenues Page 7

8 Jira Number Program/Feature Description are grouped by Functional Area. Each content pack displays the associated Solution > Product > Functional Area > Module. HUB-419 Onboarding The onboarding process is updated to use the Solution > Product > Functional Area > Module organizational structure. Step 1 groups the content alphabetically by Functional Area, as does the Pages card once the Home page is built. HUB-418 Edit Pages When you click the Menu button, pages are grouped by facets in this menu and in the Edit Pages dialog box. Facets are used to categorize and filter content so only relevant choices display. HUB-417 Tyler Hub Tyler Hub uses data definitions to present datasets from data sources. HUB-414 Tyler Hub External system interactions are updated in Tyler Hub. HUB-413 Onboarding The Dashboard Migration Report utility is available. During the onboarding process, this utility recommends Tyler Hub content to current Dashboard users when they migrate to Tyler Hub. HUB-373 Card Designer In the Card Designer, the Select Your Dataset, Fields, and Options dialog box groups datasets by Functional Area. HUB-228 Publish Page When you publish a page, the Lock Page option is available to prevent other users from modifying the page. HUB-210 Narrative Card The Narrative card is updated to provide richtext editing tools. Keyboard shortcuts are enabled, such that you can press Ctrl+B to add boldface text and Ctrl+I to add italics. HUB-6 Card Designer The Threshold option is available for Count cards in the Card Designer. This option allows you to set a threshold value that changes the card display when reached, such as changing a card color to red when an amount falls below a defined threshold value. HUB-244 Onboarding, Home Page During the onboarding process, the Home Page step provides options to select the layout of the cards on the page and choose the cards that appear. Revenues Page 8

9 Jira Number Program/Feature Description HUB-203 Reports The Reports List Viewer card is available to view reports. HUB-201 Cards, Media Card The Media card is available. This card displays an embedded video. HUB-200 Cards, Embedded The Embedded Source card is available. This HUB-26 Source Card Card Designer, Delete Card card displays embedded content using iframe. When you click the More button on a card, the Options group features the Delete Card option. When clicked, the program displays the Delete Card confirmation message prior to deleting the card. The Card Designer replaces the Query Designer and Card Properties dialog boxes, and provides a series of steps to guide you through creating a custom card. HUB-1 Pages Pages are updated to allow read-only permissions. HUB-207 Data Table Card, Cards Data table cards provide clickable actions for records. HUB-214 Workflow, Cards, Pages, Content Packs The Tyler Workflow content pack is available. When you add this content pack, Workflowspecific pages and cards are accessible. HUB-367 Esri Map Card The Esri Map card is available. This card displays locations on an Esri basemap. HUB-422 Tyler Hub Tyler Hub supports Tyler Identity version HUB-428 Tyler Hub Tyler Hub is updated to support data consumption from OData web services. HUB-429 Tyler Hub Tyler Hub is updated to support data consumption from REST web services. HUB-431 Tyler Hub Tyler Hub is updated to support data consumption from a SQL database using a SELECT command. HUB-702 HUB-257 HUB-392 Configurations, Tyler University, Tyler Hub Administration, Tyler Hub EAM Analytics Center Tyler University courses correspond with the version of Munis your organization has installed. If Munis is not enabled, the Tyler Hub Configurations page allows you to set the Tyler University version. Tyler Hub exception log files are available on the Administration page. The EAM Analytics Center page is available. This page features the Department Levels of Service card, which provides links to pages that have been created from the EAM Level of Revenues Page 9

10 Jira Number Program/Feature Description Service Template. HUB-464 View Data A search box is added to the View Data dialog box. HUB-660 Tyler Hub When you migrate from Tyler Hub version to version , user favorites and custom menu items are retained. HUB-716 Tyler Hub, Admin Access to Tyler Hub administrative settings can HUB-718 Settings Tyler Hub, Admin Settings be restricted based on users and roles. Administrative settings can be restricted based on active directory groups in an active directory environment through Tyler Identity role claims. HUB-745 Output Data The Output Data dialog box allows you to create PDF exports of card data. HUB-762 Onboarding The onboarding process is redesigned for improved usability. HUB-788 HUB-527 Tyler Hub, Admin Settings Out of Office Card, Hiring Page, Employee Review Page, Workforce Trending Page The Environment Banner Settings group is added to the Administration page on the Settings tab. This group provides options to configure a banner with custom text, such as live, test, or train environment information, that displays at the top of Hub pages. The Out of Office card is added to the Content Library. This card displays a daily, weekly, or monthly calendar of out-of-office data. The Hiring page is updated as follows: The Open Positions card is relabeled Open Job Postings. The applicant number links on the Applicants: Who Should I Hire? card display the selected record in the Applicant Central program, when clicked. The View Data dialog box for the Applicants: Who Should I Hire? card features the Is Internal Candidate and Job Identifier columns. The Employee Review page is updated as follows: Cards that use the Employees dataset display the Expiring Driver Licenses and Scheduled Substance Testing columns in the View Data dialog box. Columns for trainings, certifications, and Revenues Page 10

11 Jira Number Program/Feature Description evaluations display check marks if applicable for the record. The Frequent Actions card on the Workforce Trending page is updated to use an OData datafeed rather than XML. HUB-528 Financials, Cards The following Financials cards are available: Vendor Self Service Registration Expiring Vendor Certificates Expiring Purchase Orders Open Contracts Expiring Contracts The Open Positions card is available for HR pages. HUB-679 Open Positions Card HUB-727 Top Vendors Card The Top Vendors card is available. This card displays the top ten vendors in your organization's Munis system. HUB-720 HR Calendar Card The HR Calendar card is available to display scheduling data. HUB-101 View/Output Data The Output Data option is added to the View Data dialog box, and the View Data card menu option is renamed View/Output Data. The Output Data dialog box provides options to define the card output, including as a PDF, Excel, or CSV file. Additional options to specify the number of records and the columns to include are also available. For chart cards, images can be included in the output. HUB-728 Data Table Card Service requests can be converted to work orders directly from data table cards that are properly configured. Revenues Page 11

12 New TylerForms Functionality A new TylerForms application is available for you to create configurable forms from a rich library of templates. This application is comprised of a document generation framework, powered by the DocOrigin engine, and tools for the import and export of custom forms. Notably, the application provides: Standard templates for various modules The ability to preview template changes within the user interface The ability to update organization logos, addresses, and signatures Estimated PACE Training Time: ½ day The application provides options to add, update, and import custom templates. You can also select a standard template from the categories listed in the pane. Revenues Page 12

13 If you select a standard template, the screen refreshes and provides an option to add a new form. Any existing templates of this type are listed on the screen. After creating a basic form, additional options display for you to customize it, organized by tabs. The Configuration Options tab allows you to specify the output type, document partition, and sort criteria. Revenues Page 13

14 The Data Display Options tab provides various options to specify the details to include on the form, such as comments and other relevant information. The Form Design tab allows you to change the overall design of the form, including background and font colors, logos, and signatures. Once the form is saved, the template is available for use with programs that utilize TylerForms. Revenues Page 14

15 New TylerForms Functionality Jira Numbers: MUN , MUN , MUN Purpose: To move document processing into Munis applications rather than TylerForms servers by implementing a new TylerForms application. Estimated PACE Training Time: 1-2 days Description: Munis is updated to integrate with a new TylerForms application. This model ensures that document generation occurs within TylerForms, but document processing (such as ing and printing) occurs within Munis applications. To use the new TylerForms application with Munis, the Tyler Forms Base URL field must be completed on the Application Integration tab in the Site Settings program. This field enables Munis programs to display the Tyler Forms output option. Revenues Page 15

16 Programs that are integrated with TylerForms provide access to the Tyler Forms Preset Configuration utility, where you can configure forms templates. The ability to create new presets is determined by Tyler Forms permissions in the Roles - Munis System program and menu permissions. Users without menu access to specific programs will not be able to create or update presets in those programs, even if the Tyler Forms permission is enabled. Revenues Page 16

17 Once you have established presets, you can use them to specify Tyler Forms output in the Output dialog box for programs that support integration with TylerForms. If you select the Tyler Forms output type, you can select which preset to use and view a PDF preview of the form. If you select Sample Data, the program provides options to download or save an XML file of sample data. Lastly, the Preset Import and Preset Export programs are available to facilitate moving TylerForms presets between environments. You can export presets from one environment and then import them into another. Revenues Page 17

18 Tyler University A new user experience for Tyler University is available. This generation of Tyler University overlays Munis programs, which allows you to complete courses in your own environments, using your own data. Estimated PACE Training Time: 1 day Depending on which database you are using, Tyler U will play a different style of course: if you are using a TRN database, a scenario-based class using organizational data launches; if you are using a Live or Test database, step-by-step guidance plays. The following is an example of the step-by-step guidance provided in a Live or Test database. Revenues Page 18

19 To access Tyler U, click the Apps button in Tyler Hub or click the Help button in a Munis program. Tyler U provides two methods for taking a class: The Learn about and Prerequisites tabs. Revenues Page 19

20 The Learn about tab allows you to search for classes by subject and to expand the modules to see all of the available classes. The Prerequisites tab helps new users get started using Munis programs. This tab is commonly used during implementation and by newly hired employees. Revenues Page 20

21 The updated Tyler U also features an improved Tyler U Manager experience that does not require user management, usernames, or passwords since the classes are taken directly from the programs. It also submits a weekly report on classes taken directly to your as the Tyler U manager. The report features the user name of the Munis user, the client identifier, the date the class was taken, the name of the class, and the name of the associated prerequisite checklist. Revenues Page 21

22 Accounts Receivable Aging Report Jira Number: MUN Purpose: To provide an option to exclude unposted transactions. Description: The Exclude Unposted Transactions check box causes the report to exclude these transactions. When this check box is selected, the report does not include transactions that have not been posted. Revenues Page 22

23 Assess Late Fees, Payments Report, Reversals Report, Detail Receivables by Date Jira Number: MUN Purpose: To include the customer number in the Excel export file. Description: The Export Filter screen for the Assess Late Fees, Payments Report, Reversals Report, and Detail Receivables by Date programs include the Customer Number check box. Select this check box to include the Customer Number field in the export file. Revenues Page 23

24 Bill Inquiry Jira Number: MUN Purpose: To provide bill adjustment detail. Description: On the History tab of the Bill Inquiry screen, click an adjustment to display the Adjustment Inquiry screen. This is a display-only screen that provides adjustment details, including charge and installment amounts. Bill Inquiry, Contract Entry Jira Number: MUN Purpose: To provide miscellaneous receipt revenue contracts in Payment Entry. Description: Miscellaneous receipts can apply to revenues contracts. In this case, the Revenue Limitless and Revenue Not-to-Exceed (NTE) are the applicable contract types: Revenue Limitless: Assigns very little verification. This type uses any charge code, amount, general ledger account, or general ledger amount for the receipt. Revenue NTE: Assigns significant verification. For this type, the charge code must be outlined on the contract, the amounts need to add up to and not exceed the contract amount, the general ledger account needs to match the general ledger accounts outlined in the contract, and the general ledger accounts cannot exceed the maximum amount allowed for that specific account on that charge code. Revenues Page 24

25 When you add a revenue NTE contract, the Contract Entry program provides a Charge Codes screen that stores the charge code details. On the Miscellaneous Receipts screen, the Contract field identifies the contract number to which the receipt applies. Charge Codes Jira Number: MUN Purpose: To expand the number of accounts applicable to Utility Billing charge codes. Description: For charge codes created and maintained for Munis Utility Billing, you can assign up to five revenue accounts and assign percentages to each. Percentages must total 100. The Add Revenue button refreshes the Accounts tab to provide lines for adding the accounts. Revenues Page 25

26 Customers, Apply Deposits Jira Number: MUN Purpose: To allow you to view deposits from a customer record. Description: The Credit Information group on the General Billing tab of the Customers program shows each specific deposit that customers currently have available. The hold status on each of the deposits can be updated from this tab when updating the customer record. The View All button in the Apply Deposits program displays all available deposits for each customer. From the All Available Deposits screen, the Hold? check box is accessible when you click Update. Revenues Page 26

27 Receipts Inquiry, Bill Refund Processing Jira Number: MUN Purpose: To provide a simplified option for refunding miscellaneous receipts, animal licenses, prepayments, and deposits. Description: Miscellaneous receipts can be refunded without having to manually create invoices in Accounts Receivable. Refund records for miscellaneous receipts can be generated from several Accounts Receivable programs and then processed through the standard refund process: Receipt Inquiry when selected from the menu Customers using the GB Deposits option on the General Billing tab General Billing Apply Deposits using the View All screen Accounts Receivable Prepayments from the View All and Browse screens of Apply Prepayments Revenues Page 27

28 Detail Receivables by Date Jira Number: MUN Purpose: To include the general ledger effective date for receivables. Description: The Detail Receivables by Date Report includes date range options, the ability to isolate activity by GL Effective Date, and a GL Account Summary by Charge Code option. Over-Short Adjustment Process Jira Number: MUN Purpose: To expand special condition assignments. Description: The Advanced button for the Attach Special Condition field displays the Assign Special Conditions screen. On this screen, you can select types of bills and then specific bill attributes to which to attach the selected special condition. Revenues Page 28

29 Jira Number: MUN Purpose: To populate write-off amounts on assigned special condition codes. Description: When you assign special condition codes using the Advanced button in the Over-Short Adjustment Process program, the Special Conditions/Notes record includes the write-off amount and any note details added. Payment Entry, Bill Inquiry Jira Number: MUN Purpose: To improve the overall user interface for payment entry processing. Description: The usability of the Bill Search screen is improved in Payment Entry and Bill Inquiry. The User Preferences screen for Accounts Receivable Payment Processing programs includes the Bill Search Options tab. Use this tab to determine the search options that display Revenues Page 29

30 in Payment Entry and Bill Inquiry. In Payment Entry, the View Batch option allows you to view and reverse receipts through the Receipt Inquiry program. The Batch Information group on the Payment Entry screen provides the batch details in virtual tape format. Accounts Receivable Settings, Payments Report Jira Number: MUN Purpose: To provide bill status messaging. Description: In Accounts Receivable Settings, the Payments tab includes the Bill Payment Statuses button. This button allows you to define a bill payment status message for each of the payment statuses: Credit Balance, Paid in Full, Balance Past Due, Balance Due Now, and Revenues Page 30

31 Balance Current, Future Installment Pending. When you create a Posted Payments report, the XML report option directs the program to create XML output for each receipt in the active set of records. Revenues Page 31

32 Tyler Cashiering/Accounts Receivable Jira Number: MUN Purpose: To expand AR/Cashiering handling of miscellaneous sales tax to support multiple sales tax charge codes. Description: In Tyler Cashiering, when a customer is paying for Munis items that are subject to sales tax, Cashiering stores the Munis sales tax charge code as an external item reference for the sales tax payment, reducing the need to use only the STAX charge code for processing Munis payments. In this case, transactions identify two payments, one for the item and another for the sales tax. The Munis charge code displays as the External Item References on the Transactions screen in Tyler Cashiering. Tyler Reporting Services Views Jira Number: MUN Purpose: To create data access views for special conditions. Description: The following views are added to improve the efficiency of reports that filter bills by special condition: AccountsReceivableDataAccess.BillSpecialConditions AccountsReceivableDataAccess.CustomerSpecialConditions AccountsReceivableDataAccess.ParcelSpecialConditions AccountsReceivableDataAccess.AccountIdentifierSpecialConditions AccountsReceivableDataAccess.UBAccountSpecialConditions Revenues Page 32

33 General Billing Apply Deposits Jira Number: MUN Purpose: To improve the process for taking general billing deposits and receipts. Description: General Billing deposits are tracked individually, allowing you to reserve deposits for specific purposes and apply them to individual general billing invoices. In the Payment Entry program, you can initiate deposits by clicking Enter Receipts, selecting GB Deposit, and then entering the prepayment details. Revenues Page 33

34 Jira Number: MUN Purpose: To provide the ability to apply deposits to specific invoice lines. Description: In the Apply Deposits program, you can update the default deposit allocation by clicking the View Selected button. The Apply Deposits to Interest? check box allows you to pay interest using a deposit. On the Review Deposits screen, the amount allocated to each invoice can be changed by clearing the Apply check box to clear the allocation for that invoice. When you select the Apply check box, the program allocates the maximum amount of currently unallocated deposits to the invoice. Clicking Allocate makes the allocation values on an invoice available to edit. On the Allocation screen, the invoice lines display, followed by all the deposits applicable to the current selected invoice line. Charge Codes Jira Number: MUN Purpose: To restrict the application of deposits by AR code and charge code. Description: In Charge Codes, you can set up General Billing deposit charge codes so that the application of deposits with those charge codes is restricted to invoices with certain AR codes or to invoice lines with certain charge codes. When you create a GB charge code for which the Use for Miscellaneous Cash and Use for Prepayments/Deposits settings are enabled, the Deposit Settings option is available. This option provides the ability to define the Revenues Page 34

35 AR code and invoice lines to which the charge code applies. General Billing Settings, Recurring Invoices Jira Number: MUN Purpose: To provide a unique ID for recurring invoices. Description: The Use Next Invoice Number for Recurring Invoices setting is added to General Billing Settings. If selected, this check box directs that the next available invoice number be used when creating a new recurring invoice. Revenues Page 35

36 When this check box is selected, the Invoice Prefix field in Recurring Invoices is replaced with the Recurring ID field to provide a unique identifier for the record. In this case, the program assigns the next available invoice number when generating recurring invoices. Invoice Inquiry, Invoice Entry and Proof Jira Number: MUN Purpose: To provide field-level auditing for General Billing invoices. Description: Changes to General Billing invoice header records are audited. Invoice Inquiry and reporting views provide the option to view audit records. Print Statements Jira Number: MUN Purpose: To include General Billing customer deposit amounts in the XML output. Description: The XML output contains the general billing customer deposit amount, as well as the total unpaid balance. Revenues Page 36

37 Permits and Code Enforcement Inspection Types, Inspection Entry Jira Number: MUN Purpose: To allow inspections to be scheduled on weekend days. Description: In Inspection Types, the Allow Weekend Days check box determines if the type of inspection is permitted on weekend (Saturday/Sunday) days. If this check box is selected, Inspection Entry accepts inspections of this type scheduled on weekend days. Revenues Page 37

38 Inspection Types, Field Inspector Mobile Application Jira Number: MUN Purpose: To enable inspectors to print a results report in the field. Description: Using the Field Inspector mobile application, an inspector can print an inspection results report from an off-site location. In the Inspection Types program, the Generate Inspection Results Report check box determines if mobile printing is allowed for a specific inspection type. Mobile printing can also be enabled for a department through the Department/Board Codes program. If you select the Generate Inspection Results Report check box in this program, it overrides the Inspection Type setting, enabling mobile print for all inspections associated with the department. When the Generate Inspection Results Report setting is enabled and inspection results are processed, a report is automatically generated and attached to the record in the Inspections Entry program. Using the Field Inspector mobile application, the inspector can open the attachment and print the PDF file to a mobile printer. Revenues Page 38

39 Utility Billing Backflow Tracking Jira Number: MUN Purpose: To improve backflow tracking and reporting. Description: Backflow Tracking is updated to provide enhanced service order and test result processing. In the Utility Billing Settings program, the Use Alternate Work Order Processing and Test Results Tracking for Backflow and Create Additional Work Order for Customer Actions settings are added to support enhanced backflow processing. Use Alternate Work Order Processing and Test Results Tracking for Backflow Enables the enhanced backflow processing. Create Additional Work Order for Customer Actions Causes the Customer Actions (Create Pending) program to provide options for defining a second work order to be created by the Create Pending process. When you create a user-defined field for a meter record with the label Type of Service, the Type of Service list is available in the Backflow Service Accounts program. Your organization can define the options for this list. Revenues Page 39

40 In the Work Order/Print program, for the BFIN-Backflow Inspection and account number combination, the Additional Services section of the Work Order/Print screen refreshes to display all backflow devices related to the service order. Selecting the Backflow button in the Work Order/Print program opens the Backflow Service Account program for the associated account. The Backflow Test Results program stores detail results for each device test, and the Backflow Letters program creates letters or service orders for backflow inspections. Current Read/Consumption Jira Number: MUN Purpose: To provide an efficient option for completing final billing directly from the Current Read/Consumption program. Estimated Pace Training Time: ½ day Description: The Guided Express Final Bill button is available on the toolbar. To complete final billing using the express process, the Express Bill Run setting in the UB Settings program Revenues Page 40

41 must be set to Final. The Guided Express Final Bill button launches a guided conversation that identifies the account, customer, location, and charges for a final bill. When you have completed all the steps provided, the final billing process is complete. Utilities Jira Number: MUN Purpose: To provide an efficient option for adding utility billing accounts. Description: The Guided Add Account option provides step-by-step prompts for adding a utility billing account. When you click Add Guided Account, the program displays the Add a New Account option box, which provides the Start from Scratch, Copy an Existing Account, and Start from a Model Account selections. Depending on your choice, the program provides a series of dialog boxes that guide you through the procedure. For example, if you choose Start from Scratch, the program provides the Location Information dialog box. Once you have entered the location details and click Continue, the Account Information dialog box displays. This guided process Revenues Page 41

42 continues until you have entered all the required information for creating an account. Jira Number: MUN Purpose: To provide an efficient option for transferring customers to and from accounts. Description: The Add Guided Move process provides a step-by-step procedure for moving customers to or from an account. When you navigate to an account record and then click Add Guided Move, the program displays a dialog box of options to complete: Move Out, Move In, Revert to Owner, or Transfer. Once you select an option, the program guides you through the process, providing prompts for the required data. For example, if you select Move Out, the program displays the Select Customer dialog box, which provides a list of customers associated with the selected account. When you select a customer and click Continue, the Update Forwarding Address dialog box displays. At you enter information and click Continue at each step, the program guides you Revenues Page 42

43 through the entire process. Revenues Page 43

44 CSS Business Licenses Jira Number: MUN Purpose: To determine when businesses can file taxes. Description: In CSS Business License Administration, the Limit Filing Availability by Cycle Code Bill Date setting causes Citizen Self Service (CSS) to control when business license filing periods are accessible to taxpayers. When the Limit Filing Availability by Cycle Code Bill Date check box is selected, CSS uses the bill date defined in the Cycle Codes program to determine the date on which filing options are available. Revenues Page 44

45 System Administration Munis Hosting Jira Number: MUN Purpose: To provide a single login for your Tyler products. Estimated PACE Training Time: N/A Description: Munis is updated to use the new Tyler Identity authentication mechanism, so that only a single login is required for all your Tyler products. For example, if you are logged in to Munis, you are not required to log in a second time in order to access EnerGov. Tyler Identity utilizes token-based authentication which means that Tyler products no longer require Windows Authentication in Internet Information Services (IIS). Roles The following table provides a description of permission changes in the Munis Roles programs. Jira Number Permission Description General Revenues Accounts Receivable MUN , Override Batch Locks MUN General Billing MUN , MUN Modify Adjustments Pending Approval Grants a user permission to override locks on batches when the Use Batch Locking setting is enabled in Accounts Receivable Settings. Users who do not have this permission cannot access batches that are locked by other users. Allows a user to update adjustment records that are pending approval. Revenues Page 45

46 Jira Number Permission Description MUN , MUN , MUN Post Invoices Billed to Inactive Customers Enables a user to post invoices billed to inactive customers in Invoice Entry and Proof. The user cannot create invoices with inactive customer numbers in General Billing programs that allow manual invoice creation. Property Revenues Business Licenses MUN Show History Button Determines if the History button displays in Business Accounts. Permits and Code Enforcement MUN , MUN MUN , MUN Complaint/Violation Owner Update Plan Review Maintenance Access by Department Tax Lien/Tax Sale MUN Tax Lien Tax Sale Utility Billing MUN , MUN Add/Update UB Work Order Records Delete UB Work Order Records Determines how the Invoice To value in the Invoice Generation program is updated when the property owner associated with the complaint/violation changes: Automatically Update with No User Entry, Display Option to Update Violation Owner, or No Automatic Update of Violation Owner. Grants plan review approval permission to users who do not have permit application update permissions. Use this list to set the access level to Full, None, or Limited. If you select Limited, you can define the department codes to which the user's approval permissions are restricted. Displays the Tax Lien and Tax Sale folders on the Roles screen for all states. Relabels the Add/Update Service Order Records permission to Add/Update UB Work Order Records. Relabels the Delete Service Order Records permission to Delete UB Work Order Records. Revenues Page 46

47 System Settings Jira Number: MUN Purpose: To provide an option to share analytics data with Tyler. Estimated PACE Training Time: 1 hour Description: The Analytics tab, which features the Share Analytics with Tyler check box, is added to the program. When this box is selected, you authorize Tyler to collect application analytics to help improve your Munis experience. The collected data contains no sensitive or personally identifying information. To opt out of this service, clear the check box. Tyler Reporting Services Views Jira Number: MUN Purpose: To migrate reporting views permissions to a system data access restriction. Description: Reporting views permissions are migrated to a system data access restriction. The Tyler Reporting Services Reviews (sprviews) program is removed. The global security for reporting views is moved to the System Settings (spsysrec) program. The Tyler Reporting Services Views program is removed from the menu and replaced with the Tyler Reporting Service View Restrictions program, which calls the Roles - Munis System program, where the Reporting Views Access settings are available. Revenues Page 47

48 Workflow Business Rule Export and Import Jira Number: MUN Purpose: To move business rules from one database to another. Estimated PACE Training Time: 2 hours Description: Using the Business Rule Export and Business Rule Import programs, your organization can move business rules from one database to another. The Business Rule Export program exports existing rules by process code. You can export rules for one or multiple process codes. The Business Rule Import program imports the rules stored in an import file. The Munis version must be the same in the source and target environments for a successful import/export process. Revenues Page 48