Crash Course on Security

Article

A critical component of any system is its security model. It’s important to identify the different types of users that you have, and what each user type should be granted access to see and do inside the system.

In Onit, the default approach to security is always one of least access possible. That is, unless you configure otherwise, the only access that any given user will have is to the Records to which he/she is a Participant of. In most cases though, you’ll want to create a more robust and customized security model for your Onit implementation.

To do so, Onit offers multiple, overlapping layers of security. In this tutorial, we’ll cover each possible layer:

BillingPoint Release Notes - June 2020

Article

• Vendors can now add Timekeeper summary information to PDF export. Timekeeper data will automatically be added in Quick PDF. In Custom PDF choose "Timekeepers" from the "Include Section" to include Timekeeper data in the export.

Release Notes - June 2020

Article

• There's now a "Used In" section for filters. Also, trying to delete a filter that is in use will now throw an error.
• The Settings page has been revamped: controls have been organized into categories, and a link has been added to documentation.
• User Preferences Providers have been made more flexible. Previously all you could do there was set an app, and this app had to have certain hard-coded field names. Now ​​​​​the app fields can have any names you want, and you can set the field functions in the Preferences Provider.

Scheduling Email-Based Reports

Article

You can schedule the generation and distribution of email-based reports that contain Record data.

For instance, you could configure your Contract Administration app to send out a list of Records that are in Phase 1. Or, you could notify certain Roles about transactions that haven’t been worked on in over a week.

Reports can query for Records that match a Filter on a nightly basis and only send out a notification if one or more matches are found. Reports require very little maintenance but can play a critical role in your Apps’ success.

Configuring Daily Schedules

Article

A Daily Schedule Business Rule allows you to run Actions on a specified schedule. In this tutorial, we will go over how to build a Daily Schedule to send users an email on the first day of each new quarter. First a general pointer on configuring Daily Schedules:

Creating a Business Rule

Article

Locked Matter Timekeeper Rates

Article

Some clients require billing rates remain in effect for the duration of an engagement without increase.

A Contextual Guide to Accessing Variables from Different Business Rules

Article

When it comes to Onit app building, context is king! The Liquid syntax required to access any particular Onit object may change based on location in which it is used. For example, to access a Record’s Field value, the Liquid syntax within a Condition would be different if it lives in a Transaction Created versus a Participant Added Business Rule. Always keep context in mind when constructing your Liquid.

In this tutorial, we’ll provide a contextually-focused breakdown of all Business Rules, explaining which objects each Rule has access to and the specific syntax that you should use.

Creating a Button to Execute an Action

Article

Miscellaneous Liquid Examples

Article

Put more detail about changes into the history log 

By default, the history in each transaction just says "[user] edited the [app name] Request Form." For more detail, create an "Add History" action, with this as the Message:

{{current_user.name}} updated the following attributes: 
{% for change in atom.changed_values %} 
{% unless change.field_name == 'updated_at' or change.display_name == blank %} 
{%unless change.previous == blank and change.current == blank%} 
{{ change.display_name }} ({{change.field_name}}) : {{ change.previous }} > {{change.current}} <br> 
{% endunless %}
{% endunless %}
{% endfor %}