Qntrl 3.0: new updates and migration

Latest additions and enhancements

We recently released a new version of Qntrl: 3.0. This version has a fresh interface with simplified navigation and seamless performance. We’ve tried to incorporate as many feedback and suggestions as possible in our new version to build a solution-driven product for our customers.

 

As a major terminology update, we've renamed Orchestration as Boards for simplicity. The following is a list of the new features, enhancements, and interface updates you can experience in the new version of Qntrl.

 

Pick-and-use onboarding templates

To make onboarding for new users easier, we’ve built a bunch of tailor-made, ready-to-install-and-use templates that are equipped with full-fledged automation to kick-start your processes. You can access them during onboarding or from the left panel under Board Templates, after onboarding. Learn More

 

All-encompassing navigation

All navigation options have now been moved to the left-panel. We've deprecated the Cards tab from the top-panel and moved board short-cut tabs to the left panel. You can now access boards, templates, requests, reports, and settings from the left navigation options. Each board is also equipped with quick access options where you can edit, manage, and add automation options. Learn More

 

Simplified user permissions

User permissions to access boards or cards can now be configured within each board independently. The configurations also reflect instantly in the board, eliminating the need to republish them. Each board has a separate option to manage users, requesters, and permissions. The user who creates a Board is the admin, and the other users added to the board can be customized with appropriate profiles and permissions. Learn More

 

External user requests

Users who are not a part of your Qntrl organization can still create requests (cards) in Qntrl using Public Forms and Email In options in Manage Requesters. Organization users who are not a part of the board can also be allowed to create requests by enabling the Organization Users option. Learn More

 

New Dashboard view

Track each orchestration’s updates in a visually appealing dashboard view. You can also customize the charts and tables displayed here. Learn More

 

Introducing CodeX

Server scripts are now called CodeX. You can code company-specific business logic to manage your database, perform time-consuming processes quickly, and automate activities in your business workflows using CodeX.

 

Lite Users

Our new Lite User model allows user additions where they can just create, view, and track their requests. Lite users do not require purchase of user license. However, if you’d like to convert them to conventional users, you’d have to purchase one. Learn More

 

Enhanced Kanban Boards

Kanban boards are now visually enhanced with expand and collapse options that assist you with a comprehensive view. Sorting cards based on ascending and descending orders is also now possible. Learn More

 

Unified Filters 

We’ve upgraded the user interface for filters and unified them to the right panel.  

 

Increased field limits

Qntrl 2.0 allowed fields to be reused between boards but you could only create 580 fields in the whole portal. The new version of Qntrl 3.0 allows you to create 580 fields per board independently, without the provision of reusing.

 

New profile permissions

With Card-level and Field-level permissions now moved to Board-level ones, we've added two new permissions under Profiles in Settings. Add New Board allows users to create boards and Manage Org Users allows users to invite new users to boards. Learn More

 

New Pages tab

Extensions with location mentioned as top-panel will now be moved to the left-panel under Pages. If you have any previous extensions with this location, you will be able to view this tab.

 

Key changes to note during migration

When migrating from Qntrl 2.0 to Qntrl 3.0, a few modules have significant impact which are listed below.

 

Migrating Boards

After migrating a board, the user who created the board will be added as the admin and all other associated Users/Teams/Roles, mentioned in 'Access Cards' of Set Permissions in Bluepints, will be added as members. If the board creator is not a part of the organization anymore, the organization admin will be added as the board’s admin.

 

Migrating Business Rules

In Qntrl 2.0, each business rule can either be associated with a specific board, multiple boards, or all boards. Since Qntrl 3.0 is board-specific, rules that were associated with more than one board will be duplicated individually for each associated board. We recommend that you go-through the duplicates and retain only those required.

 

Migrating Webhooks and Custom Functions

In Qntrl 2.0, Webhooks and Custom Functions were not associated with boards. Since Qntrl 3.0 is board-specific, Webhooks and Custom Functions with module type 'Cards' will be duplicated individually for each board with which it is indirectly associated. If they are not indirectly associated with any board, they are mapped to the first board by default. We recommend that you go-through the duplicates and retain only those required.

 

Migrating Email Templates

In Qntrl 2.0, Email Templates can be created without associating them with any board. Since Qntrl 3.0 is board-specific, Email Templates will be duplicated individually for each board with which it is indirectly associated. If they are not indirectly associated with any board, they are mapped to the first board by default (except default emails and circuit-based emails). We recommend that you go-through the duplicates and retain only those required.

 

Migrating Users

After migration, the user who created the orchestration will be the board admin. If this user is not a part of the organization anymore, the organization admin will be the board admin. Users/Teams/Roles mentioned in Access Cards of Set Permissions will be added as Members to the board. Users/Teams/Roles mentioned in Create Cards of Set Permissions will be mapped under Manage Requesters-‘All board users can add cards’. Users/Teams/Roles mentioned in ‘Who can perform this transition’ in before section of the blueprint will be added as External Requesters if they are not a part of the board.

 

If you’d like to update the permission of board users, visit this help document.

 

How to migrate to the new version

To access the new version of Qntrl, your organization’s data is required to be migrated to the new version, which is completely assisted by Qntrl’s support team. We ensure that your entire data is migrated and the new version’s onboarding is hassle-free.

 

To migrate to Qntrl 3.0, reach out to our support team at support@qntrl.com. Only the Organization Administrator can initiate data migration to the new version. Please note that once an organization is migrated to the new version, the old version will no longer be supported.

 

Before you migrate to the new version, if you’d like to work hands-on the new features and enhancements of Qntrl 3.0, we’ve got a sneak-peak pilot organization. You can request our support team to enable this feature to you.

 

Once enabled, navigate to Settings and select Preferences under Organization. Under Assisted Migration to new Qntrl version click the button Initiate Pilot.

 

Do note that the pilot organization is just a temporary channel to check out Qntrl 3.0. Any updates performed here will not be saved to your original Qntrl organization as the Pilot organization only has a copy of your configurations but not the actual data. Additionally, your configured widgets, extensions, and integrations will not be available in the Pilot org. Connections will be available, but requires re-authentication to work.

 

To switch permanently to the new version, please email our support team at support@qntrl.com. Our team will get in touch with you and initiate the assisted migration. 

• Related Articles

• Lite Users

  Lite users in Qntrl will only have permissions to raise requests while they are a part of the organization. Those who are just a resource to bring in information to the organization and don't need to perform any further actions in the cards ...

• Quick onboarding guide

  Introduction to Qntrl Qntrl is workflow automation software that helps organizations take the lead in automating their everyday workflows. The mainstay of organized businesses are their time-tested workflows, seasoned with practice and expertise. To ...

• My Requests

  Users who raise requests in a board can stay informed about the progress of their requests from the My Requests module. Organization users who are not a part of the board can create cards as requests in the board . Only users within an Organization ...

• Non-orchestration users' transition

  Board owners (admins) can allow a non- board users to perform a particular transition in the board by configuring Organization users in the Before section of the Blueprint transition. An email template will be triggered to the non- board user along ...

• Replace User

  When an employee gets promoted or quits the organization, their tasks and responsibilities must be handed-over to another employee to takeover. Qntrl helps you handle such replacement processes efficiently by transferring ownerships from the former ...