Recent updates
-
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.
Developer Tutorials and Materials / 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.
Developer Tutorials and Materials / 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.
Developer Tutorials and Materials / 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:
Developer Tutorials and Materials / 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.
Developer Tutorials and Materials / Apptitude Developer Tutorials / Working with Fields
-
Release Notes - July 2018
Updated on Aug 06, 2018ArticleAs an App Creator, you now have the ability to trigger a calculation on a single transaction. A new action called "Recalculate Single Transaction"
Release Notes / Apptitude Release Notes / Apptitude Release Notes
-
Release Notes - May 2018
Updated on May 25, 2018ArticleAn App Creator can easily navigate through the navigation menu to configure an application.
Release Notes / Apptitude Release Notes / Apptitude Release Notes
-
Release Notes - March 2018 - Hotfix
Updated on Mar 29, 2018ArticleThe Liquid filter "execute_reaction_url" allows people to trigger actions by following links in their email. We've introduced a new parameter to it: "email_recipient".
When this parameter is used, then the person who received the email link can click it and fire the action without ever having to log in to the system. (Note that if the redirect is 'atom' or 'dashboard' rather than 'message', then the person will have to log in to complete the redirect.)
You can also use "authenticated_user" here, and that will produce the old behavior, where a login is required before the action can fire. And if you leave the parameter blank, that also will behave the same way it used to.
Release Notes / Apptitude Release Notes / Apptitude Release Notes
-
Release Notes - March 2018
Updated on Mar 13, 2018ArticleWe’ve added some handy features to ManyToMany App Panels to support users' ability to quickly create and remove relationships to the current transaction.
As part of the configuration for a ManyToMany Related Atom Panel, App Creators can now optionally include a Plus icon for creating new relationships and a bulk action to unrelate existing relationships. Both properties can be conditionally hidden.Release Notes / Apptitude Release Notes / Apptitude Release Notes
-
Release Notes - Feb. 2018
Updated on Mar 04, 2018ArticleWe've added a new property named Saved File Name to the Generate Document Action that allows App Creators to give documents custom file names. This property supports Liquid.
Release Notes / Apptitude Release Notes / Apptitude Release Notes