Recent updates
-
Invoice Level Discounts/Adjustments
Updated on Aug 26, 2020ArticleThere are two options for apply discounts/adjustments to an invoice. Which type you use will depend on the type of discount/adjustment what your client wants to see on the invoice.
These instructions are for an invoice level discount/adjustment, which is applied as an individual line item.
Discounts/adjustments should be entered as negative numbers in order to reduce the invoice total.Knowledge Base / All Product End User Guides / Guides to Using BillingPoint
-
Contact BillingPoint Support
Updated on Aug 20, 2020ArticleKnowledge Base / All Product End User Guides / Guides to Using BillingPoint
-
Onit System Limits
Updated on Aug 14, 2020ArticleThis page lists various explicit limits that are enforced across the Onit platform.
Knowledge Base / Apptitude Developer Tutorials / Reference Materials
-
Release Notes - August 2020
Updated on Aug 11, 2020Article- Listcombo Fields have a new option: Use Facet Filtering. This makes the Listcombo available for the new filtering mode described below.
Knowledge Base / All Product Release Notes / Apptitude Release Notes
-
ELM Standard Reports Release Notes - v2.5 July 2020
Updated on Aug 10, 2020ArticleMTE Based - ELM Standard Reports are now based on the Multiple Table Extract (MTE) feature in Tableau. This feature ensures that the underlying design of the standard data sources is suitable for easy customizations when new fields are added in Matters, Vendors and Invoices Apps in Onit. This design also ensures that the data sources are no longer restricted to show only Matters that have Invoices.
DW Refresh Date - The ELM Standard Reports header now show the actual date the data was refreshed in the data warehouse. In previous versions, the date in the report header was based on the maximum of the “updated at” date in the Matters App.
Line Item Inactive Filter - An additional filter “Line Item Inactive” has been added to the new MTE based standard data sources. Line items marked as inactive (Line Item Inactive value of 1) in Billing Point do not get included in the data source.
Knowledge Base / All Product Release Notes / ELM Release Notes
-
Getting Started with BillingPoint
Updated on Aug 05, 2020ArticleOnboarding activites are required to be completed for each client you are invoicing via BillingPoint.
Once you have completed the onboarding steps required for your client, a registration email will be sent to the main contact used during the onboarding process. Your company specific login domain will be provided in the registration email.Knowledge Base / All Product End User Guides / Guides to Using BillingPoint
-
Liquid Variables, Filters, and Tags
Updated on Jul 31, 2020ArticleNew to Liquid? We recommend checking out our Crash Course on Liquid article first before you dive into these scripts.
The Liquid markup language can be leveraged in some very powerful ways to enhance business solution workflows in Onit; we recommend our Crash Course on Liquid as a good primer if you're just getting acquainted with the language, but that article just skims the surface of Liquid's potential.
Below we've documented a handful of the Liquid scripts we find ourselves commonly using, as well as some long-winded scripts we don't care to rewrite from scratch when building Apps.
Knowledge Base / Reference Materials / Resources
-
App Builder Objects Interactive Diagram
Updated on Jul 28, 2020ArticleWhen writing Liquid, it can be hard to remember all of the objects that you have available. The diagram below serves as a reference guide.
For example, let’s say you're building a workflow where an Action should fire when a comment contains the word solved. Using the diagram below, you’ll learn that you can easily access a comment’s contents using comments.message object.
Here’s a quick breakdown of the colors used within the diagram:
- The blue boxes represent the highest-level objects that you have available. Specifically, the Record that Liquid is running against and the current Onit User.
- The red and green boxes represent objects that live within a Record or a User. The red boxes represent objects that return arrays (e.g., an array of different discrete comments) while the green boxes represent objects that return a single value. When writing Liquid against arrays, you will almost always use a Liquid for Loop to iterate over each value in the array.
Knowledge Base / Apptitude Developer Tutorials / Reference Materials
-
Creating a Suite
Updated on Jul 21, 2020ArticleLet’s think big picture for a moment! Any given Onit client might use our platform to solve between one and many dozens of different business problems. From tracking legal spend, to budgeting, to accruals, to expense reports the range is far and wide. As a result, an Onit environment might contain lots of different Apps and Records.
This is great news for the client as a whole, as it means that Onit is orchestrating their business and providing tons of value. For individual end-users, however, lots of Apps and data can be overwhelming to navigate. Ideally, each end-user will be presented with a UI that only shows them the Apps and Records that they actually care about, as well as charts and tables that spot trends and highlight their action items and key metrics. And that’s where Suites come in!
Suites act as a user’s Onit homepage, the first page that a user sees when they log in. On this homepage each end-user sees a curated collection of “widgets” that list and link to Records that a specific user cares about - for example, invoices pending the user’s approval or legal matters upon which the user is a Participant. In addition, Suites provide a slide-out sidebar menu that gives the user access to a curated list of Apps, links, and reports that the user in question uses. As an Apptitude Developer, you can create multiple Suites, one for each type of user (e.g., one Suite for attorneys and another for paralegals) and/or you can create different Suites for different business problems (e.g., one Suite for budgeting and another for accruals).
In this tutorial we’ll explain how to build and configure Suites.
Knowledge Base / Apptitude Developer Tutorials / Building Workflow
-
Configuring a User Preferences Provider App
Updated on Jul 21, 2020ArticleWith a small amount of configuration, you can build out a simple App, called a User Preferences App, to contain a Record for each of the users in your system that includes details about them. User Preferences Apps are helpful when:
- Your business logic is dependent on attributes of your users. For instance, you may have an invoice approval workflow that determines which user should be added as an invoice approver based on that user’s approval authority.
- You are setting up a Suite in your environment. A User Preferences App is an essential component of a Suite configuration and is where landing pages and navigation within a Suite is determined for each user.
This tutorial will cover how to configure the User Preferences App and provide an example of how to build workflow off data in a user’s Record in this App.
Knowledge Base / Apptitude Developer Tutorials / Administration