Archiving an Inactive Timekeeper

Article

1. Select Master Settings from the Client dropdown menu.

Editing a Timekeeper Profile

Article

1. Select Master Settings from the Client dropdown menu.

Emails and Links Liquid Examples

Article

Emails and Links

Approval Button: {{ 'Approve' | button_link : approve_url }}

Reject Button: {{ 'Reject' | button_link : reject_url }}

View Request Button: {{ 'View Request' | button_link : view_request_url }}

Add Buttons to Emails

{{ 'Onit' | button_link : 'http://onit.com' }}

Wizard / Widget link filters (Second Mover Form)

In emails You can also embed {{ 'button text' | wizard_link : atom }} in a notification, which will create an anchor link that will take the user directly to the launch form in edit mode without rendering the atom view. See also edit_form, which can be appended to the end of an atom URL and will render the atom in launch form view.

in addition to wizard_link there is wizard_url, e.g., {{ atom | wizard_url }} which will generate a URL instead of a link. The URL can then be used with button_link, e.g., 

{% assign my_url = atom | wizard_url %}{{ 'Press Me' | button_link : my_url }}

From a Suite. Use “widget_atom_link” (to render second mover) form or widget_atom_link_popup(render full atom view in popup form.) E.g., 

{{ 'Edit' | widget_atom_link: atom}}

 {{ task.name | widget_atom_link: task }}

Get Email Attachment IDs

This Liquid will get the attachment IDs of documents sent to a Record via email.

{% assign mail_id = atom.emails.last.id %}
{% for doc in documents %}
{% if doc.attachment_owner_id == mail_id %}
{{ doc.id }}
{% endif %}
{% endfor }

Project Emails

Approve email: {{email_address.account}}.approve@{{email_address.subdomain}}.app.onit.com

Reject email: {{email_address.account}}.reject@{{email_address.subdomain}}.app.onit.com

Non-Anonymous attachment download URL

The user must be logged into Onit to use this link, it is not anonymous. 

{% attachment_link generated_document %}

Generate Anonymous Attachment Download URL

This Liquid will generate an anonymous URL that will let anyone download the contents of an attachment Field. Parameters: the field name, the expiration period. The expiration period is expressed in days. The default is 45 days. The parameter accepts a decimal: .5 for 12 hours, .001 for 86 seconds, etc. You can also say "never".

{% capture url %}
{% anonymous_attachment_url atom, attachment_field_name, 30 %}
{% endcapture %}
<a href="{{url}}" download>Anonymous Download Link</a>

Launch App Form from Suite Widget

This Liquid creates a clickable link that will launch an App without navigating the user away from their dashboard. This only works in the context of a suite portal widget, not an atom portal widget.

{{ "click here" | widget_atom_launch: "App Name" }}

Parametrized Links (Anonymous Launch Page)

To create anonymous launch with included parameters, use the {% create_launch_url %} tag, along with subtags {% app %} and {% param %}. An example:

{% create_launch_url my_link %}
    {% app 'My App' %}
    {% param name = 'Test Atom' %}
    {% param requester_name = 'Alice' %}
    {% param checkbox = true %}
{% endcreate_launch_url %}

This example constructs a link which is stored in my_link. You can then use my_link in a hyperlink:

<a href = "{{my_link}}">Click Here</a>

Or a button link, as shown just above:

{{ 'Click Here' | button_link: my_link }}

Working with Fields Liquid Examples

Article

Determine If a Field is Either Blank or Null

For a Text Field: {% if matter_name == blank %}true{% endif %}

For a Date Field: {% if date_field == blank %}true{% endif %}

Access the Display or Save Value of a Combo Field:

Display Value: {{ atom | combo_display: 'combo_field_name' }}

Save Value: {{ atom | combo_value: 'combo_field_name' }}

*This does not work with ListCombo Fields

Access the Display or Save Value of a MultiSelect Field:

Display Value: {{ atom | combo_display: 'multiselect_field_name' }}

Save Value: {{ atom | combo_value: 'multiselect_field_name' }}

*This Liquid will return an Array of values

MultiCurrency Values

Get international currency code: {{ currency_field.currency }}

Get MultiCurrency Value: {{ currency_field.amount }}

Get MultiCurrency Value in subunits (e.g., cents):  {{ currency_field.cents }}

List Lookup

{{ [field_from_atom] | list_lookup: '[List Name]', '[column name to match]', '[column name to output]' }}

Below we are finding the value of name field in the activity column in the T3 list and returning the corresponding html_instructions from the matching row.

{{ name | list_lookup: 'T3', 'activity', 'html_instructions' }}

List Lookup – Whole Atom

If an atom is part of a Transaction List Provider, you can populate a variable with all of its attributes. For example, let's say you have a TLP that lists your legal entities. In your Matters app, once the legal entity is set, you want to look up its address, phone number, main contact, and so on. Instead of doing 21 different list lookups, you can do one list_lookup_atom:

{% assign entity = legal_entity | list_lookup_atom: 'Legal Entities', 'name' %}

and then output:

{{ entity.address }}

{{ entity.country }}

{{ entity.main_billing_contact }}

... and so on.

Copy MultiCurrency Values

Suppose you have two apps, APP 1 and APP 2, and both apps are related (parent-child for example). You want to copy over a multi-currency field from APP 1 to APP 2 using an 'Update Related Transaction' action. Here is how we configure the params liquid property of the action:

p_mcf_app_2:{{mcf_app_1.amount}} {{mcf_app_1.currency}}

Note: mcf stand for Multi-Currency Field, and of course you need one multi-currency field in each app.

Update Attachment Field with a Document from a DocumentFolder Field

Suppose we have an App, that App has an attachment field and a DocumentFolder field. We want to trigger and action that will set/update the content of the attachment field to the first document in the DocumentFolder field. Here is how we do it:

• Create an Update Transaction action, and in the Params Liquid filed use this:

p_name_of_the_attachment_field: {{atom.documents[0]._id}}

• Now we can create a button or business rule so we can attach the above Update Transaction action

Import a Textarea Field into a Word Document Without Losing Line Breaks

When pulling data from a Textarea Field using a Generate Document Action Word will take the formatting out of the Textarea Field. This Liquid will look for line breaks and insert a split.

{% assign splits = '{ "key": "\r\n"}' | parse_json %}
{% assign lines = textarea_field | split: splits.key%}
{% for line in lines %}
{{line }}
{% endfor %}

Working with Participants Liquid Examples

Article

Display One Participant with a Specific Role

{% assign displayemail = "" %}
{% for endorsement in endorsements %}
{% if endorsement.role == "Attorney"%}
{% if displayemail == "" %}
{{ endorsement.user.email }}
{% assign displayemail = endorsement.user.email %}
{% endif %}
{% endif %}
{% endfor %}

Accessing the user object using 'email_to_user'

{% assign my_user = 'john.gilman@onit.com' | email_to_user %} {{my_user.name}} - {{my_user.has_used_password}} 

Returns - "John Gilman - true"

Accessing a user's preferences using 'user_preferences_for_user'

Assuming a "User Preferences" app is configured as a User Preferences provider in Advance Builder you can use the filter "user_preferences_for_user" to get any of a user's attributes. You need to pass a user object to the filter, not just an email address, so "current_user" will work. But you can always use "email_to_user" to first get a user object then pass it to the filter.

Use with "current_user" 

{% assign my_user = current_user | user_preferences_for_user %} {{my_user.approval_authority}} 

Returns "10000"

Use with an email address 

{% assign my_user = 'john.gilman@onit.com' | email_to_user | user_preferences_for_user %} 

Returns "50000"

Display How Many People are in a Specific Role

{% for endorsement in endorsements %}
{% if endorsement.role == "Attorney" %}
{% assign count = count | plus: 1 %}
{% endif %}
{% endfor %}

Display All Current Approvers with Status

{% for endorsement in endorsements %}
{% if endorsement.requires_action and endorsement.active %}
{{ endorsement.user.email }} - {{ endorsement.status }}
{% endif %}
{% endfor %}

Display Approvers Still Pending

{% for endorsement in endorsements %}
{% if endorsement.requires_action and endorsement.active and endorsement.status == 'Pending' %}
{{ endorsement.user.email }}
{% endif %}
{% endfor %}

Return the Role and Name of Every Participant on a Transaction

{% assign all_participants = ''%}
{% for role in roles%}
{% assign participants_in_role = ''%}
{% for participant in role[1]%}
{% assign participants_in_role = participants_in_role | append: participant | append: "; "%}
{% endfor %}
{% assign size = participants_in_role | size | minus: 2 %}
{% assign participants_in_role = participants_in_role | slice: 0, size %}
{% assign all_participants = all_participants | append: '"' | append: role[0] | append: '" Participant(s): ' | append: participants_in_role | append: ". "%}
{% endfor %}
{% assign size = all_participants | size | minus: 1 %}
{{ all_participants | slice: 0, size }}

Hide a Button From All Users Except Those in a Certain Role

{% assign hideButton = true %}
{% for e in endorsements %}
{% if e.role == "Requester Approval" and e.email == current_user.email %}
{% assign hideButton = false%}
{% break %}
{% endif %}
{% endfor %}
{{hideButton}}

Initialize requester to current user

1. Place the following in the requester name's initial value field:
   • {{ current_user.name }}
2. Place the following in the submitter email's initial value field:
   • {{ current_user.email }}

Date Calculations Liquid Examples

Article

Date Calculations

If you are using any date math in a UI Action (as opposed to a regular Action), you must first use the to_date filter. E.g., {{ date_field | add_days: 3 }} will produce an error; {{ date_field | to_date | add_days: 3}} will work.

Formatting Dates

27 Nov 2017: {{ created_at | short }}

November 27, 2017: {{ created at | long }}

27 Nov 2017 9:29AM: {{ created_at | short_time }}

November 27, 2017 9:29AM: {{ created_at | long_time }}

3 months ago: {{ created_at | when }}

11/27/2017: {{ created_at | date: '%m/%d/%Y' }}

Common Date Math:

Add Days: {{ date_field | add_days: 3 }}

Subtract Days: {{ date_field | subtract_days: 3 }}

To Date: {% assign now_date = now | to_date %} {{ now | to_date }}

Subtract Dates (returns a number): {{ date1 | subtract_date: date2 }}

Assign Current Date: {{ now | date: "%y/%m/%d" }}

Assign Current DateTime: {{ now | date: '%Y-%m-%dT%T' }}

Useful Date Liquid Filters:

{{ add_years }}
{{ subtract_years }}
{{ add_months }}
{{ subtract_months }}
{{ add_business_days }}
{{ subtract_business_days }}

Output the number of days that have elapsed between two DateTime Fields:

{% assign started_sec = phase_started | date: "%s"%}
{% assign ended_sec = phase_ended | date: "%s"%}
{% assign total_elapsed_seconds = ended_sec | minus: started_sec%}
{% assign days_elapsed_int = total_elapsed_seconds | divided_by: 86400%}
{% assign days_elapsed_mod = total_elapsed_seconds | modulo: 86400%}
{% assign hours_elapsed_int = days_elapsed_mod | divided_by: 3600%}
{% assign hours_elapsed_mod = days_elapsed_mod | modulo: 3600%}
{% assign minutes_elapsed_int = hours_elapsed_mod | divided_by: 60%}
{% assign minutes_elapsed_mod = hours_elapsed_mod | modulo: 60%}
{{days_elapsed_int}} Days, {{hours_elapsed_int}} Hours, {{minutes_elapsed_int}} Minutes

*Where phase_started and phase_ended represent the custom DateTime Field names whose values should be used in the calculation.

Output the number of elapsed business days between two DateTime Fields:

{% assign start = phase_started | date: '%s' %}
{% assign end = phase_ended | date: '%s' %}
{% assign days = end | minus: start %}
{% assign leftover = days |  modulo: 86400 %}
{% assign days = days | minus: leftover %}
{% assign days = days |  divided_by: 86400 %}
{% assign first_day = phase_started | date: '%u' %}
{% assign last_day = phase_ended | date: '%u' %}
{% assign diff = first_day | minus: last_day %}
{% if first_day > last_day %}
{% assign days_to_subtract = 7 | minus: diff %}
{% else %}
{% assign days_to_subtract = diff | times: -1 %}
{% endif %}
{% assign days = days | minus: days_to_subtract | plus:1 | round %}
{% assign weeks = days | divided_by: 7 %}
{% assign business_days = weeks | times: 5 %}
{% if last_day > first_day %}
{% assign last_minus_days = last_day  | minus: days_to_subtract %}
{% if last_minus_days > 6 %}
{% assign business_days = business_days | plus: days_to_subtract | minus: 1 %}
{% else %}
{% assign business_days = business_days | plus: days_to_subtract %}
{% endif %}
{% else %}
{% if days_to_subtract != 0 %}
{% assign days_greater= days_to_subtract | minus: last_day %}
{% assign days_to_subtract = days_to_subtract | minus: days_greater %}
{% assign business_days = business_days | plus: days_to_subtract %}
{% endif %}
{% endif %}
{% if leftover > 0 %}
{% assign business_days = business_days | plus: 1 %}
{% endif %}
{{business_days}}

*Where phase_started and phase_ended represent the custom DateTime Field names whose values should be used in the calculation.

How to Create a Budget Template

Article

Records on the Budget App can serve as templates for future budgets. To create a new Budget template, launch the Budget App and click the Is Template radio button.

Creating Spot Rate Conversions

Article

Spot rate conversions need to be manually set up in BillingPoint. If they are not set up in BillingPoint, the Onit App Builder spot rate conversion Actions will not work.

To do this in BillingPoint:

1. Log into the client in question’s BillingPoint instance.

Overview of Budgets in Onit

Article

When it comes to storing budget and spend information, Onit is able to do so at either the overall-level (life of the matter), or monthly, quarterly, or yearly. Within any of these time ranges, Onit can optionally further break up the data by fees versus expenses or they can be grouped together.

For granular budgeting (life-of-matter, annual, quarter, etc.), there are a number of configuration tasks that you should usually complete. Some of the below are a few hard-fast rules, while others are general recommendations/FYIs that you should be aware of.

Customizing the Timekeeper Rate Approval Workflow

Article

The timekeeper approval workflow can easily be modified according to your business needs. The default Timekeeper Rates App approval workflow has four phases:

1. New
2. Pending
3. Approved
4. Rejected

All new Records will move immediately into the “Pending” phase. The Record will stay in the “Pending” phase until all approvals have been granted, then it will advance to the “Approved” phase. If the Record is rejected by an approver the Record will move to the “Rejected” phase until the vendor resubmits the Record in BillingPoint.

Custom phases may be added between the “Pending” and “Approved” phase. The “Approved”, and “Rejected” phases should not be modified as these tie into BillingPoint logic. Customizing a Timekeeper Rates workflow is the same as customizing any other workflow in Onit. Let’s breakdown how one custom solution was implemented.

This client chose to add two additional phases between “New” and “Approved”.