Recent updates
-
Crash Course on Security
Updated on Jul 06, 2020ArticleA 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:
Developer Tutorials and Materials / Apptitude Developer Tutorials / Administration
-
BillingPoint Release Notes - June 2020
Updated on Jun 29, 2020Article- 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 / BillingPoint Release Notes / BillingPoint Release Notes
-
Release Notes - June 2020
Updated on Jun 25, 2020Article- 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.
Release Notes / Apptitude Release Notes / Apptitude Release Notes
-
Scheduling Email-Based Reports
Updated on Jun 23, 2020ArticleYou 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.
Developer Tutorials and Materials / Apptitude Developer Tutorials / Building Workflow
-
Configuring Daily Schedules
Updated on Jun 23, 2020ArticleA 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:
Developer Tutorials and Materials / Apptitude Developer Tutorials / Building Workflow
-
Creating a Business Rule
Updated on Jun 15, 2020ArticleBusiness Rules are one of the critical components to building Apps in Onit. While Actions enable you to specify what should happen inside of your App (e.g., an email should be sent, a spreadsheet should be generated), Business Rules enable you to specify when your Action should fire.
For example, an App creator may have created an Action that adds a participant to a Record. A Business Rule could be used to specify exactly when this should happen. The App creator could have the Add Participant Action run when the Record is first created, by tying it to a Transaction Created Business Rule. Alternatively, the App creator could have the Action run when a phase change occurs by instead tying it to a Transaction Phase Change Business Rule. There are over a dozen different types of pre-defined Business Rules, each of which enable you to run an Action at a different time.
In many cases, you can also add a Condition to a Business Rule, which allows you to get even more specific when configuring when an Action should run. For example, you could run an Add Participant Action only if the Record in question had a price field value that was greater than $1,000.
Developer Tutorials and Materials / Apptitude Developer Tutorials / Basics of Business Logic
-
Locked Matter Timekeeper Rates
Updated on Jun 15, 2020ArticleSome clients require billing rates remain in effect for the duration of an engagement without increase.
End User Guides / BillingPoint End User Guides / Guides to Using BillingPoint
-
A Contextual Guide to Accessing Variables from Different Business Rules
Updated on Jun 09, 2020ArticleWhen 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.
Developer Tutorials and Materials / Apptitude Developer Tutorials / Reference Materials
-
Creating a Button to Execute an Action
Updated on Jun 09, 2020ArticleWhile Onit Apps are pre-configured with a few standard Buttons out-of-the-box, an App creator can also create their own custom Buttons. While there are different types of Buttons that you can create, in this tutorial we’ll explain how to create Action Buttons, which are helpful if your App’s users need to run an Action ad-hoc.
For example, you might want users to run a Generate Spreadsheet Action on a Record whenever they want. If so, you can create a Button that fires this Action.
Action Buttons can be configured to display in one of two places: on View Pages or on the App's Dashboard.
- View Page Action Buttons: When clicked, these Buttons usually run an Action on a single Record -- the one that is currently being viewed by the user.
- Dashboard Bulk Action Buttons: These Buttons work in bulk -- they run the same Action on many different Records at the same time. A user browses to an App’s Dashboard, selects all of the Records that they want to run the Action on, and then clicks the Button.
An Action Button can optionally accept a Condition that will affect if and when the Button displays. For example, you could create a Condition that only displays a Button to a certain type of user (e.g., only Managers).
Developer Tutorials and Materials / Apptitude Developer Tutorials / Basics of Business Logic
-
Miscellaneous Liquid Examples
Updated on Jun 09, 2020ArticlePut 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 %}
Reference Materials / Liquid Variables, Filters, Calculations, Tags, and Examples / Resources