Munis Major Enhancements 2018.1 Financials Major...System Administration/Roles ... For each major enhancement, the document provides the Jira number, a brief purpose statement, and

Munis Financials ______________________________________________________

Major Enhancements Munis 2018.1

April 2018

For more information, visit www.tylertech.com.

Munis Major Enhancements 2018.1 Financials Page 2

TABLEOFCONTENTS

MunisFinancials.................................................................................................................................................3

TylerHub...............................................................................................................................................................3

NewTylerFormsFunctionality...................................................................................................................12 NewTylerFormsFunctionality..................................................................................................................................15

TylerUniversity...............................................................................................................................................18

Budget..................................................................................................................................................................22

GeneralLedger.................................................................................................................................................25

ProjectAccounting..........................................................................................................................................26

Purchasing.........................................................................................................................................................27 ContractChangeOrders................................................................................................................................................27

ContractEntry/ContractChangeOrders...............................................................................................................28

PurchaseCardStatements,PurchaseCardImport...........................................................................................32

WorkflowBusinessRules(ContractManagement)..........................................................................................33

VendorSelfService(VSS).............................................................................................................................................33

AccountsPayable.............................................................................................................................................35 APPaymentManager.....................................................................................................................................................35

PendingInvoices..............................................................................................................................................................37

Vendors................................................................................................................................................................................38

Vendors,EFTSetup.........................................................................................................................................................38

SystemAdministration/Roles.....................................................................................................................39 MunisHosting....................................................................................................................................................................39

Roles......................................................................................................................................................................................41

Financials........................................................................................................................................................................41

SystemSettings.................................................................................................................................................................43

TylerReportingServicesViews.................................................................................................................................43

WorkflowBusinessRuleExportandImport.......................................................................................................44


Munis Financials This document provides an overview of the major Financials enhancements for Munis® 2018.1. 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 quickly 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.


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.


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.


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 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 rich-text 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.

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 Source Card

The Embedded Source card is available. This card displays embedded content using iFrame.

HUB-26 Card Designer, Delete Card

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, Workflow-specific 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 2017.4.

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 Configurations, Tyler University, Tyler Hub

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.

HUB-257 Administration, Tyler Hub

Tyler Hub exception log files are available on the Administration page.

HUB-392 EAM Analytics Center 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 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 2017.4 to version 2018.1, user favorites and custom menu items are retained.

HUB-716 Tyler Hub, Admin Settings

Access to Tyler Hub administrative settings can 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.


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.

HUB-527 Out of Office Card, Hiring Page, Employee Review Page, Workforce Trending Page

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 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

HUB-679 Open Positions Card The Open Positions card is available for HR pages.

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.


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.


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.


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.


New TylerForms Functionality Jira Numbers: MUN-288684, MUN-291913, MUN-295046 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 emailing 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.


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.


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.


Tyler University A new user experience for Tyler University is available. This new generation of Tyler U overlays your own Train, Test, and Live databases so that when you take classes, you are using data that is specific to your work. Estimated PACE Training Time: 1 day


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.


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.


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 email 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.


Budget Monthly Budget Amounts, Next Year Budget Entry, Central Budget Entry Jira Number: MUN-279486 Purpose: To provide a means to enter next-year monthly budget amounts by percentage. Estimated PACE Training Time: Less than ½ day Description: The Monthly Budget Amounts, Next Year Budget Entry, and Central Budget Entry programs accept budget-level requests by percentage.


In Next Year Budget Entry, the Monthly Amounts button is available on the Account Info screen.

If there are no detail lines, but there are percentages defined for the account, the Monthly Amounts screen displays the amounts by percentage per period. This screen is available for accounts that have the Allow Monthly Budgeting setting selected in Account Master.

Multiple Budget Programs Jira Number: MUN-288473 Purpose: To provide additional budget projection levels. Estimated PACE Training Time: Less than ½ day Description: Twenty customizable budget projection levels are available rather than five, allowing users to create budget projections with additional levels of approval. The General


Ledger Settings, Next Year Budget Entry, Central Budget Entry, Roll/Factor/Merge Projection, and Next Year Budget Reports programs are updated to accommodate this change. The General Ledger Settings program is reorganized to accommodate the additional budget levels; the fields in the Budget Settings group on the General tab are moved to a new tab, Budget Settings.


General Ledger Account Inquiry Jira Number: MUN-262073 Purpose: To provide graphs of account data. Estimated PACE Training Time: Less than ½ day Description: The Account Inquiry program features the 4 Year Graph and History Graph tabs, which display graphs of account data.

• The 4 Year Graph tab displays a bar graph of amounts for the current year, two previous years, and the next year. Available, Actual (Memo), Encumbrances, and Requisitions amounts are charted on the graph in distinct colors.

• The History Graph tab provides a graph of historical Available, Actual (Memo), and Encumbrances amounts for previous years, beyond those shown in the 4 Year Graph tab.


Project Accounting Project Import Jira Number: MUN-262444 Purpose: To provide a means to import project data. Estimated PACE Training Time: Less than ½ day Description: The Project Import program is available to import new project codes into Munis from an Excel file.

The Generate Excel Template button creates an Excel file that includes the required columns for the import file. Enter the project data in this template and then upload the file to import the new project codes into Munis.

If your organization uses Munis Workflow, new projects are imported with a status of Pending until they are approved.


Purchasing Contract Change Orders Jira Number: MUN-290501 Purpose: To provide additional options for withholding payment from a contractor or vendor. Estimated PACE Training Time: Less than ½ day Description: Contract processing is updated to provide additional options for withholding payment from a contractor. The Withholding Types program is updated as follows:

A Munis system withholding type of Contract Lien is added and is available for use in the Contract Change Orders program. You cannot modify the details of the Contract Lien withholding type.

For withholding types that your organization creates, fields are available for configuring withholding types to use a flat amount. Once you select the Flat Withholding check box, you can define the Default Flat Amount, Minimum Invoice Amount, and Maximum Withheld Amount.


In the Contract Change Orders program, the Contract Liens option is available for adding, maintaining, and viewing lien details on a contract.

Invoice Entry is updated to enforce withholding on invoices entered for a contractor against whom there is a contract lien. The Roles program includes additional permissions for contract liens:

Roles - Accounts Payable includes the Override Contractor Lien Withholdings on Invoices permission.

Roles - Contract Management includes the Maintain Contractor Lien Records permission.

Contract Entry/Contract Change Orders Jira Number: MUN-285325 Purpose: To require users to enter a valid purchase order before they can enter an invoice against a contract. Estimated PACE Training Time: Less than ½ day


Description: The Require PO for Payment option is available in the header section of contract records in Contract Entry.

This check box, when selected, indicates that the Invoice Entry program requires the user to enter a valid purchase order number before an invoice can be entered against the contract. A contract change order is required to make changes to the Require PO for Payment check box. In addition, the program maintains audit information about changes made to this field. Jira Number: MUN-292882 Purpose: To track contract contingency dollars. Estimated PACE Training Time: Less than ½ day Description: The Contract Entry and Contract Change Orders programs include options for maintaining and using contract contingency amounts on encumbered contracts:

The Totals section of the contract header includes fields for Contingency Balance (showing the total of available contingency amounts) and Avail w/Contingency (showing the total available contract amount plus any available contingency amounts).


The Accounts/Amounts tab includes the Contingency Amounts button, which opens the Contract Contingencies program. This program displays a list of all contingency lines entered against the contract. In Contract Entry, use this screen enter contract contingencies.

The Contingencies Are Encumbered check box defines whether contingencies encumber GL accounts. When you open Contract Contingencies from the Contract Change Orders program, the Invoke option is available for transferring a contingency amount to a new or existing contract amount line. Selecting a contingency line and clicking Invoke opens a dialog box from which you can transfer the highlighted amount to a new or existing contract amount line.

In Workflow Business rules, the CCA - Contingency and Amount workflow approval type is available for COM (contract change orders) business rules. In Roles - Contract Management, the following permissions control access to contract contingencies:

Maintain Contract Contingencies View Contingency Amounts


Jira Number: MUN-284151 Purpose: To define contract payment terms. Estimated PACE Training Time: Less than ½ day Description: Contract Entry allows you to define payment terms on a specific contract. Within a contract record, clicking Terms in the Additional Information group opens the Contract Terms program, where you can add or update payment terms for the selected contract and vendor, including Payment Discount Percentage, Days to Discount, and Days to Net.

Use the Maintain Text Terms and Select Text Terms options to enter custom notes or text to include on contracts. In addition, the standard Notes program includes a Program field for defining whether to include the note or text on transactions in the Munis Purchasing programs (Requisitions and Purchase Orders), Contract programs, or Both. When this option is set to either Purchasing or Both, Munis automatically includes the payment terms on any Purchasing and Accounts Payable transactions that reference the contract.


Purchase Card Statements, Purchase Card Import Jira Number: MUN-249622 Purpose: To reverse an unintended import of purchase card transactions. Estimated PACE Training Time: Less than ½ day Description: The Void Statements function is added to the Purchase Card Statements program to provide a way to reverse an unintended import of purchase card statements. The void operation voids all statements imported under a specified statement code, and reverses the general ledger and project ledger updates that occurred during the statement file import. Once a statement is voided, no further action can be taken on the statement or any of the transactions contained within the statement.

The feature includes an Un-Void option for reversing the void operation on an import that was mistakenly voided. Reversing a void operation restores the statements associated with the specified statement code to the status of New, and restores the GL updates for the transactions within these statements. To make the Void Statements functionality available, your user role must be assigned the Void Purchase Card Statements permission in Roles - Accounts Payable.


Workflow Business Rules (Contract Management) Jira Number: MUN-277152 Purpose: To provide a means of configuring ranges of user-defined fields that start contract workflow processes. Estimated PACE Training Time: ½ day Description: Business rules for the COE, COM, REQ and RQC process codes can be configured so that workflow is initiated by ranges of user-defined fields. When one of these process codes is selected and user-defined fields exist for the related contract or requisition programs, the program makes the User-Defined Field Ranges list available at the bottom of the Workflow Business Rules screen. In addition, the option for Allow Munis Changes Without Restart is available for the COE and COM process codes.

Vendor Self Service (VSS) Jira Number: MUN-238356 Purpose: To make the labeling of the Bids tab and Bid fields in VSS customizable. Estimated PACE Training Time: ½ day Description: The MSS administrative setting for Bid Proposal Semantics allows you to customize the label of the Bids tab and Bid fields that are displayed to vendors in the VSS application. The setting is found in the Application section of MSS Vendor Administration, and includes fields for defining the singular and the plural form of the custom terminology. If you


make no entries in these fields, VSS uses the default label of Bid for the singular and Bids for the plural.

If your organization has configured bid types in the Munis Bid Types program, VSS search and search results screens include the Type field, showing the available bid types. The detail view of a bid record when opened from search results also includes the Type field.


Accounts Payable AP Payment Manager Jira Number: MUN-250063 Purpose: To provide a single, streamlined program for processing accounts payable cash disbursements. Estimated PACE Training Time: ½ day Description: If your organization uses TylerForms, and you want to consolidate all of your Munis accounts payable cash disbursement functions into a single program, you can work with your Tyler representative to enable the optional AP Payment Manager program.

When enabled, the AP Payment Manager replaces the following previous cash disbursement programs:

Select Items to Be Paid Print Checks Generate EFTs Cash Disbursements Void Checks Generate Positive Pay


When you open the AP Payment Manager, the Search field is available for searching by check run code.

Search results display in a list format.

Clicking a check run code in the search results opens the Check Run Details page, from which you can perform many of the AP Payment Manager’s major functions, including voiding individual checks, voiding an entire check run, printing checks and electronic funds transfer (EFT) advices, posting cash disbursements journals, and generating positive payment files.

From the search results, you can also click a vendor name to open the Vendor Central program for that vendor record.


Pending Invoices Jira Number: MUN-289929 Purpose: To decentralize the invoice entry process, and identify current pending invoices from all sources. Estimated PACE Training Time: Less than ½ day Description: The Pending Invoices option is added to the Invoice Entry program. This screen shows accounts payable records from several sources, including Request for Check, Contract Progress Payments, and Vendor Self Service, all of which can be converted into active invoices by batch from this screen.

Records shown in Pending Invoices are at the Pending status until approvers take further action on them. From Pending Invoices you can route an invoice to an accounts payable clerk or department responsible for completing entry of invoices. You can view invoice batches created in Pending Invoices in the main Invoice Entry program, and can release them into workflow, approve, and then post them in the same way as other invoice batches.


Vendors Jira Number: MUN-274725 Purpose: To improve the function of the Mass Inactivate option. Estimated PACE Training Time: Less than ½ day Description: The Mass Inactivate screen in the Vendors program includes a field for Exclude Vendors Created After Date. The program does not deactivate vendor records that were added to the system after the date you define.

Vendors, EFT Setup Jira Number: MUN-275549 Purpose: To provide a means of defining the EFT file format for a vendor. Estimated PACE Training Time: Less than ½ day Description: In the Vendors program, the General tab within a vendor record includes the EFT File Type field, which is available for use when a vendor’s Payment Method is set to EFT. The EFT file types available in this list include CCD (Cash Concentration or Disbursement format) and PPD (Prearranged Payment and Deposit Entry format).


In the EFT Setup program, the Output Options tab includes a check box for Generate Both CCD and PPD Files Containing Invoices Based on the Vendor's EFT File Type. This field is available when either the CCD or PPD file type is selected, and directs the program to generate both a CCD-formatted file for all invoices from CCD vendors and a PPD-formatted file for all invoices from PPD vendors from a single warrant.

System Administration/Roles Munis Hosting Jira Number: MUN-255731 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

Financials Accounts Payable MUN-264756 Maintain Check

Runs Print Checks Post AP Cash

Disbursements Create AP Positive

Pay File Generate EFT File Void AP Checks

When you migrate from an earlier version of Munis, these role permissions are set to a default value of Y (selected).

MUN-283966, MUN-282478

Void Purchase Card Statements

Allows a user to void purchase card statements.

MUN-277058, MUN-277017

Override Contractor Lien Withholdings on Invoices

Allows a role assignee to override contractor lien withholding amounts on invoices in the Invoice Entry program.

MUN-287184 Allow Vendor Debarment Verification

Allows a user to execute the SAM vendor debarment verification check and maintain vendor debarment statuses.

MUN-287201 Allow Override of the Default Document Number in Invoice Entry

Allows a user to override the default document number in the Invoice Entry program.

Contract Management MUN-277077, MUN-277017

Maintain Contractor Lien Records

Controls whether a user can manage contractor lien records to withhold contract payments.

Maintain Contract Contingencies

Controls whether a user can modify contract contingency records in Contract Entry and Contract Change orders.

View Contingency Amount

Controls whether a user can view contingency amounts in inquiry programs.

General Ledger MUN-277919, MUN-278655

Allow Excluding Bank Transactions

Allows a user to exclude transactions from the bank reconciliation process in Bank Reconciliation Manager.

Inventory MUN-277013, MUN-277014

Override Frozen Items on Transactions

Allows a role assignee to override warnings in the Purchasing program’s


Jira Number Permission Description

warning messages on items marked as Item Frozen.

MUN-287170 Maintain Obsolete Items

Controls access to the Obsolete Items program, which is used to set outdated item records to a status of Obsolete, and also restore obsolete item records to active status. Obsolete item records are hidden in the Items program.

Purchase Orders MUN-272606, MUN-272607, MUN-271584

Modify Own PO Change Orders Up to and Including Status

Controls access to the Purchase Order Change Orders program according to the status of the user’s change order records. The possible values are None, Created, Rejected, and Approved. The most restrictive setting is None, and the most permissive is Approved. The default setting is None.

Modify Others’ PO Change Orders Up to and Including Status

Controls access to the Purchase Order Change Orders program according to the status of other users' change order records. The possible values are None, Created, Rejected, and Approved. The most restrictive setting is None, and the most permissive is Approved. The default setting is None.

Student Activity MUN-284624, MUN-214392

Create/Maintain Purchase Orders Up to/Including Status

Controls a role's access to Student Activity purchase orders based on the workflow status of the change order.

Create/Maintain Disbursements Up to/Including Status

Controls a role's access to Student Activity disbursements based on the workflow status of the disbursement.

Add Receipts Allows a role assignee to add receipts to Student Activity transactions, when selected.


System Settings Jira Number: MUN-291157 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-253117 Purpose: To migrate reporting views permissions to a system data access restriction. Estimated PACE Training Time: Less than ½ day 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.


Workflow Business Rule Export and Import Jira Number: MUN-279762 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.

Documents

Munis Major Enhancements 2018.1 Financials Major...System Administration/Roles ... For each major enhancement, the document provides the Jira number, a brief purpose statement, and