Warning!
This is a legacy document. The features described below are only usable within the classic-generation environment.
Currently, Betty Blocks offers faster and more advanced options that are available in next-gen. Before you start working on some new features in your application, consider doing it using the next-gen version. In particular, you might find it useful to check out Using the HTTPS action step and Setting your remote data source articles.
Good luck!
What is HighQ?
HighQ is a secure and customizable online platform to help manage legal operations. This includes legal intake, matter management, contract management, document management and self-service tools.
Being a rather user-friendly document management solution for lots of law firms, banks, and other corporations, HighQ still has several challenges that its users might face. The outdated user interface makes data management and collaboration more difficult and fixed iSheet field types limit what users can do with their data. Some might even have issues with notifications and reminders not working properly, which occasionally leads to misalignment.
Those minor issues could be easily eliminated for a smoother user experience as now citizen developers can build customer-facing applications to collect data and documents into HighQ and iSheets. Extending iSheet table capabilities could be a great asset to boost overall productivity, and creating custom actions will help build fully personalized workflows.
Betty Blocks HighQ integration enables you to keep working with HighQ and iSheets alongside Betty Blocks capabilities for better workflows and build customer-facing solutions that integrate seamlessly with your HighQ setup.
What integrations do we provide?
HighQ Sheets API
The HighQ Sheets API connects with the iSheets functionality from HighQ and allows you to connect to the functionalities iSheets has to offer: sharing, collaborating on and tracking dynamic data, and processes integration with convenient import and export to Excel. iSheet module provides tools to deal with such tasks, as advanced transaction management, real estate portfolio management, monitoring trading positions, insurance claims tracking solutions and others.
After installing and configuring the sheets API, you will have access to a bunch of pre-generated endpoints that allow you to manage your sheets, add new data and view it in your Betty Blocks application.
HighQ Site resource API
The HighQ Sites API connects with the “sites” functionality from HighQ and allows you to connect and manage site data. For example, getting user information, inviting new users and if installed together with sheets, connect your site data to sheets.
Different sites are aimed to serve various purposes or groups. The HighQ Sites API allows you to set up as many sites as needed with three primary roles provided: Site Administrators, System Administrators and End Users having both internal and external roles. Find out more about the types of users, how to group them and give the right access and permissions here.
HighQ Organizations API
The HighQ Organizations API connects with the organization functionality from HighQ and allows you to retrieve data from your HighQ organization. Use the organization data to group users in your application based on the organization they are in.
Whenever a new user is created by a System Administrator, they have to be assigned to either some existing organization or a new one should be created. Read more about adding users to organizations in this article.
What can you do with integrations?
By integrating Betty Blocks with HighQ you can keep HighQ running as your backbone, and use Betty Blocks to build user-friendly client portals to collect data that automatically integrates with iSheets. With this integration, your data always is in perfect sync between HighQ and Betty Blocks, no matter where you make changes. You can also build customized actions to create automated processes that cater to you and your client's needs.
Why is Betty Blocks a good fit for HighQ?
Considering the information mentioned above, let's go through the key points why Betty Blocks is a good fit for HighQ integration:
Integration: Easily integrate Betty Blocks with our out-of-the-box integrations for HighQ in our Block Store.
Customer-facing portals: Built customer-facing portals fully in line with your branding where customers can upload their documents and fill in their information.
Data management: HighQ and Betty Blocks integrate with each other allowing data to pass through both platforms. It’s easier to create an application that directly feeds information into your HighQ iSheets and vice versa.
Custom actions: Create pitch-perfect workflows by using Betty Blocks' custom actions within HighQ.
Extend: Use HighQ for the secure data room functionality as the backbone and use Betty Blocks to pull data and documents into HighQ and iSheets.
Views: Create different views for an iSheets table.
Notifications and reminders: Set notifications and reminders within Betty Blocks for your HighQ processes.
Enrich iSheets data fields: Proprietary Excel, table format, and different field types that the platform supports. It would be also useful to push such features from Betty Blocks to iSheets as single select drop-down, multi-select, dates, free form, numbers, file storage, etc.
Create different views: Create different views for clients and your legal team.
How to install HighQ integration?
In this guide, we will briefly explain how to set the HighQ integration within the Betty Blocks application.
Go to the application’s dashboard and open the Block store. |
Select the HighQ web service you need. For this example, we will install the iSheets API. |
Select the application in which you want to install the HighQ block.
Note: If you install the block in the wrong application, you can simply delete the configured functions without harming your application. |
 |
The installed API can be found in the webservices section of your application. Navigate to your web services section via the toolbox. |
When accessing the web services section, you can view the installed HighQ iSheets connection. The next thing you have to do is to configure some details before we can use the functionalities generated by the block. |
Authentication
As the web service will be installed without a set authentication, you will need to create this first based on the credentials from your HighQ account.
Navigate to the configurations tab in your toolbox to set up an Oauth2 Basic configuration. |
Fill in the information to set up your configuration. This information can be provided via your IT department, or you can find it via your HighQ connection. More information about HighQ can be found here. |
After having created your configuration, set it as the authentication you want to use in your web service settings. |
Using the integration
After the authentication data for the HighQ integration has been configured, you can use the web service in your application's actions to manage your data.
Open the actions in the old environment. |
Click on
Note: If you need data from your application, you’ll have to choose a data model while creating a new action. |
Use the HTTP request step to select the installed web service. |
After selecting the web service, you will be able to select any one of the endpoints provided with the web service.
For example, select the “To get a list of iSheet items” endpoint. After selecting the endpoint you will have to fill in the Host and Version settings of your HighQ connection. You can fill these in by hand or create a configuration that holds the information. |
Per endpoint, there can also be different kinds of path variables. In this case, the integration also asks for the iSheetid it wants to get data from. |
After configuring the HTTP request step, you can use the data from the step in the following steps to manage the data from the request. |
With the HighQ endpoints and Betty Blocks actions, you will be able to use your HighQ data to a greater extent whilst also being able to customize the technical capabilities you would normally not have. |