Recent updates
-
Creating a Conditional Compound Action
Updated on Aug 06, 2019ArticleAs you’ve likely learned in other tutorials, a big part of Onit App building revolves around Actions. Most Actions are designed to accomplish one (and only one) task. For example, a Send Notification Action sends an email; an Add Participant Action adds a participant to a Record.
Many times, running a single Action won’t solve your larger business problem. Instead, you’ll need to string a series of individual Actions together to accomplish your goal. For instance, let’s say that when a user clicks a Button, your App should do the following:
- Generate a document
- Edit a field value
- Add a participant to the Record
Since each of these things are handled via different Actions, you’ll need to configure Onit to run these Actions as a sequence in a specific order, one immediately after the other. How can you do this?
That’s where Conditional Compound Actions come into play. This special Action contains other sub-Actions, and runs them in a specific order. As a result, if you have a list of Actions that all need to run when a user clicks a Button (or a Business Rule fires), you can add those Actions into a Conditional Compound Action. When the Conditional Compound Action runs, it will run its contained sub-Actions.
Packaging Actions together like this reduces the redundancy of elements and keeps your Actions organized around business problems. Additionally, this is the only way to configure a Button or Business Rule to fire more than one Action.
In this tutorial, we’ll explain how to create and configure Conditional Compound Actions.
Developer Tutorials and Materials / Apptitude Developer Tutorials / Basics of Business Logic
-
Creating an Action
Updated on Aug 06, 2019ArticleActions are an essential type of building block within Onit Apps. They define what should happen when some event takes place during a transaction’s lifecycle. For example, you could build an Action that sends an email, and then configure that Action to run whenever a transaction is approved. In this example, the Action is the sending of the email.
Actions are not self-sufficient; they must be linked to a Business Rule or Button in order to be triggered. Similarly, all Business Rules and Buttons make use of Actions.
There are many different types of Actions, and you can choose which ones to leverage in your app. One of the most commonly used Actions is Send Notification. The notification is constructed in the Advanced Designer’s Action pane, where an app creator specifies who will receive the notification and what the content of the notification is. Another commonly used Action is Add Participant, which can be used to add a participant as a specific Role to a transaction.
Developer Tutorials and Materials / Apptitude Developer Tutorials / Basics of Business Logic
-
Using the Liquid Editor
Updated on Aug 06, 2019ArticleNew to Liquid? You may want to check out our Crash Course on Liquid article before learning about the Liquid Editor.
If you’re using Liquid or HTML in your Apps, your tool belt should include our Liquid Editor. The editor functions as a testing ground where you can use your App’s transaction and user data as test cases to:
- Validate Liquid Scripts: If you’re writing Liquid for a UI Action or Condition for example, you can preview the output of your script in the Liquid Editor to ensure that it is returning the data that you expect.
- Validate HTML Formatting: When writing HTML for some element of your App, such as an email notification or transaction widget, you can format and preview what it will look like in the editor.
While the Liquid Editor has a few gotchas that you’ll need to be aware of, it’s ultimately a great tool for taking the guesswork out of your App configuration.
In this tutorial, we’ll first cover how to use the Liquid Editor with a few examples. Next, we’ll finish up by explaining how to actually open the editor and get started.
Developer Tutorials and Materials / Apptitude Developer Tutorials / Getting Started
-
Building Your First App
Updated on Aug 06, 2019ArticleNo matter what type of business problems you are ultimately aiming to solve with Onit, you’ll always start by creating a basic App.
To do so, you’ll run through a simple Wizard, which will prompt you to create your App’s most fundamental components: its name, Fields, Roles, and Phases (among other things). Once you complete the Wizard, your new App will be created.
In this tutorial, we’ll walk through the process of creating a brand new App from scratch using the Wizard. We’ll take you step-by-step through the process of launching the Wizard and moving through its screens. Along the way, we’ll highlight the Wizard’s most important settings and configuration options.
Developer Tutorials and Materials / Apptitude Developer Tutorials / Getting Started
-
Release Notes - June 2019
Updated on Aug 03, 2019Article- You can now run bulk actions on all Records of an App. When you check the "Select All" checkbox on the first page, and then pick a bulk action, you get a confirmation dialog that allows you to run the Action on all pages, not just the first. If you select this option, the Actions will run in the background, and a user of your choice will receive an email notification when the process is done.
Release Notes / Apptitude Release Notes / Apptitude Release Notes
-
Using Complex Combo Fields
Updated on Jul 31, 2019ArticleWhen building an app, you’ll often want to offer users a dropdown Field from which they can select from a list of predefined options. In addition, sometimes you’ll want the options available in the dropdown list to automatically change based on the current value of an entirely different Field. In these situations, you’ll want to use a Complex Combo Field. These Field types can significantly increase the user-friendliness of your app, as they ensure that users will only see options that are currently relevant.
For instance, let’s say you have multiple managers for each department of your company. Using a Complex Combo Field, you can filter your manager Field’s dropdown options based on the value that a requester previously selected for the department Field. This ensures that the user will only see managers for the selected department.
Developer Tutorials and Materials / Apptitude Developer Tutorials / Working with Fields
-
Defining Custom Holidays
Updated on Jul 19, 2019ArticleOnit’s Holiday Provider App allows you to specify which days on a calendar should be considered “holidays” when executing Liquid-based date math. When a Holiday Provider App is created and configured, Onit’s add_business_days filter can exclude holidays that you define. Each holiday is represented by an individual Record in the Holiday Provider App.
Developer Tutorials and Materials / Apptitude Developer Tutorials / Building Workflow
-
Conditionally Hiding a Field
Updated on Jul 17, 2019ArticleHidden Conditions can be used to dynamically show and hide an app’s Fields. This allows you to only display a Field to a user when it is relevant to do so.
For example, let’s say that you ask a user to choose a product_type from a dropdown list, and you provide the user with four possible options: Product A, Product B, Product C, and Other. If the user selects Other, you may then want to immediately display a Textarea Field to the user, so that he/she can type in a product name. In this example, you would create a Hidden Condition that essentially says, “Only show my Textarea Field if the user selects Other from product_type.”
Developer Tutorials and Materials / Apptitude Developer Tutorials / Working with Fields
-
Crash Course on Liquid
Updated on Jun 25, 2019ArticleLiquid is an open-source markup language that can be used to expand your App’s functionality.
Liquid can help you:
- Format data: If you have a number in a Field (e.g., 1000), you could format it as a currency value (e.g., $1,000.00) using Liquid. This might be necessary when using the number in an email or report.
- Perform Math: You could add two Fields together to calculate and populate the value of a third Field.
- Make Decisions: Liquid can help you build decision making into your App. For example, you can create “if/then” statements, which allow you to define how your App should behave in various situations.
- A whole lot more! The examples above barely scratch the surface. Once you learn Liquid’s basics, you’ll find many opportunities to expand your App’s functionality.
If you’ve never heard of Liquid before, not to worry! Learning the basics isn’t difficult, and does not require any programming knowledge. In many cases, you can achieve a great deal in an App with only a limited understanding of Liquid.
In this tutorial, we’ll cover Liquid’s basic concepts and syntax.
Developer Tutorials and Materials / Apptitude Developer Tutorials / Getting Started
-
Release Notes - May 2019
Updated on Jun 10, 2019Article- Charts in suites now feature dashed scale lines for better visibility.
Release Notes / Apptitude Release Notes / Apptitude Release Notes