Recent updates
-
How to Create a Sibling App Panel
Updated on Mar 27, 2019ArticleHave you built any parent-child relationships yet in Onit? If so, great! This tutorial will expand your skill set in this area. If not, however, this tutorial might not make a lot of sense - in that case, check out Creating a Parent-Child Relationship before moving on. In addition, you’ll also need to understand what an App Panel is in Onit if you’re not familiar with this concept, see our Displaying Related Atoms Dashboards as Tabs tutorial.
Knowledge Base / Apptitude Developer Tutorials / Building Workflow
-
Building Email-based Reports using the Multi Report Action
Updated on Mar 27, 2019ArticleThe Multi Report Action is designed to send email-based reports that list one or more user’s pending work in Onit (e.g., invoices that need to be approved, tasks that need to be completed).
This Action can be configured to solve two (very different) types of use cases:
- Example Use Case #1: The Employee Email: The ACME Corporation wants to send each Onit user a daily email that lists their pending work in Onit. That said, many of their users are responsible for approving Records in both the Contracts App and the Risks App. As a result, they don’t want to send each user two separate email reports each day (that would be pretty noisy). They instead want to send each user a single email each day that lists all of their pending work across both apps. A Multi Report Action can be configured to do exactly this! Below is an example screenshot of this report.
Knowledge Base / Apptitude Developer Tutorials / Configuring Actions
-
Release Notes - Dec. 2018
Updated on Jan 15, 2019Article- When you click an "Approve and Next" button, we immediately remove the transaction from your pending work queue. So even if the approval takes some time to process, you won't see that transaction in the "My Pending Work" view on a dashboard grid, and it won't be counted as pending by suite counter widgets.
- The Reject Action in the Designer now has an "Endorsement" field. It's used to find a specific participant or participants to reject for: you enter a Liquid expression that evaluates to an endorsement ID.
Knowledge Base / All Product Release Notes / Apptitude Release Notes
- When you click an "Approve and Next" button, we immediately remove the transaction from your pending work queue. So even if the approval takes some time to process, you won't see that transaction in the "My Pending Work" view on a dashboard grid, and it won't be counted as pending by suite counter widgets.
-
Release Notes - Oct. 2018
Updated on Jan 09, 2019ArticleThe React Designer can now be made the default in your environment. In environments that are set to use "New Home Page" and "React UI", the system administrator can turn on a setting that will take users directly to the React Designer when they edit an App. (You can still get to the Legacy UI Designer, by editing the URL in the browser bar.)
Knowledge Base / All Product Release Notes / Apptitude Release Notes
-
Approved HTML Tags
Updated on Nov 09, 2018ArticleIf you are in a widget, Field, or Action that accepts HTML these tags are the only HTML tags Onit will accept.
Knowledge Base / Apptitude Developer Tutorials / Reference Materials
-
Using Badges to Enhance App Orchestration Visibility and Workflow
Updated on Aug 16, 2018ArticleYour business case may require an App whose primary responsibility is to orchestrate the firing of Actions on a large number of Records. The Earn Badge Action can be used to support workflows that require orchestrator Apps by providing visibility into the progress of work across these Records and information on the success or failure of that work. Workflow following the conditional success or failure of a batch of work is also supported by this Action.
A good use case for the Earn Badge Action is a budgeting process, where forecast values must be recalculated on a monthly basis. With an Earn Badge Action, an App Creator can configure a Portal Widget to display on the orchestrator Record which shows how many forecast Records are pending an update, how many were successfully updated and how many failed an update. When all forecast records have been recalculated, a Conditional Action can send a success or failure email to the user that is responsible for managing this monthly process.
The Earn Badge Action is a very versatile Action. Advanced workflows can be supported with this type of Action where multiple Earn Badge Actions are configured to take Records through multiple sets of Actions on reoccurring and conditional bases.
Knowledge Base / Apptitude Developer Tutorials / Beta Features
-
Configuring iManage
Updated on Aug 15, 2018ArticleThis document contains an outline of what is needed to set up the iManage Actions that create and maintain a workspace from Onit to iManage. This procedure will require you to work directly with the client's iManage consultant, as there are Field names and values that are brought over from iManage that you will not have access to inside of Onit.
Knowledge Base / Apptitude Developer Tutorials / Integrations
-
Data Integration Configuration
Updated on Aug 15, 2018ArticleHave you checked out our Syncing Flat-File Data to Transactions tutorial yet? If not, it may be helpful to read through before beginning this one.
Knowledge Base / Apptitude Developer Tutorials / Integrations
-
Overview of Mechanisms for Uploading Data to Onit
Updated on Aug 13, 2018ArticleOnit provides three different mechanisms for creating and updating Records from files of data. While each serve as efficient ways to translate rows of data in external files into Onit Records, their use cases vary slightly.
-
Synchronize Transactions from List can be used when you have an Excel file of data you need to create or update Records from. It is executed from a corporation's Administration page, not from an Action; it is therefore a good option when you need to make a one-time upload of data to Onit.
See the Creating and Updating Transactions from a List tutorial for more information.
- The Update Related Atoms from Spreadsheet Action is typically used in conjunction with a Generate Spreadsheet Action. After users have generated an Excel spreadsheet of Record data and made updates to that spreadsheet, this Action provides a mechanism for pushing those changes back to Onit.
See the Keeping Transactions Updated with a Generated Spreadsheet tutorial for more information.
- Finally, the Sync Data to Transactions Action is for creating, updating, and optionally deleting Records from a delimited flat file (e.g., CSV file), rather than an Excel file. This Action is typically used for data migrations and, in conjunction with an SFTP Server, data integrations between an external system and Onit. This Action provides the fastest way to upload data to Onit.
See the Sync CSV Data to Transactions tutorial for more information.
The table below outlines the main differences between these mechanisms:
Knowledge Base / Apptitude Developer Tutorials / Working with Spreadsheets and Documents
-
Synchronize Transactions from List can be used when you have an Excel file of data you need to create or update Records from. It is executed from a corporation's Administration page, not from an Action; it is therefore a good option when you need to make a one-time upload of data to Onit.
-
Configuring a Calculated Value for a Field
Updated on Aug 10, 2018ArticleYou can configure a Field to automatically calculate its own value. For certain Fields, this approach is preferable to a user manually typing a value, as it eliminates the chance for human error and is also less work for the user.
For example, let’s say that an app contains the following two Fields: contract_expiration_date and days_until_contract_expiration. When a user manually enters a value into the first Field, a Field Calculation could automatically determine and populate the second Field. In this example, the Field Calculation is performing basic math to determine the difference in days between the current date (i.e., today) and the date entered into contract_expiration_date.
Knowledge Base / Apptitude Developer Tutorials / Working with Fields