What is our primary use case?
In
Unqork, I worked in different industries including insurance, banking sectors, pharmacy trials, and real estate. Currently, I am working on a financial investment project. Throughout these six projects in
Unqork, we used it to integrate different systems, store databases, create workflows, case use cases workflows, and dynamic UIs, dashboards. We used almost all areas such as services and APIs, with most of them using data workflows where we manipulated data as per our requirements.
When I started working in Unqork, it was just entering the market. This is why we did not have proper predefined use cases in Unqork, and even now they are not fully available, only small snippets. We used these snippets, and from academic training and boot camp, we started developing small POCs before joining real-time projects. We developed cases based on experience and learned extensively. Based on our experiences, Unqork has also evolved significantly. Since 2021, there have been numerous changes in Unqork, including the designer portal, canvas, securities, and other features. We have implemented all new functionalities and features delivered by Unqork in quarterly patches.
Currently, I am working with a client where there is an agreement between the client and Unqork itself. Unqork provides software to the client under this agreement, and simultaneously, the Unqork product team uses this client environment as an early access environment. We are maintaining six projects - three completed and three in progress. They conduct experiments on live servers where applications are being used by different region users. The version I am using (71680) is not yet available in the market, as we have early access approximately six to seven months ahead.
What is most valuable?
Unqork provides everything by default as a tool. In the admin portal, we can configure everything related to module management, API management, roles, and groups immediately. We can maintain and manage services, databases, and almost everything in a single portal and tool. This is what I appreciate about Unqork. The platform has plugins, data workflows, and components, which we use extensively when approaching technical aspects.
The drag-and-drop functionalities in Unqork's developer portal are comprehensive. In the Unqork canvas, all components such as notepads, text areas, text fields, radio buttons, checkboxes, and drop-downs are provided without requiring code. Unqork provides default styling options, and if a project requires additional styling, it only needs minimal customization. Configurators do not need to write code for simple predefined elements in Unqork. This feature is similar to Pega, which I worked with in the past, but Unqork appears more advanced.
What needs improvement?
There are numerous areas for improvement in Unqork. For example, while they are replacing view grid with
Vega grid, the
Vega grid lacks certain features available in the view grid. In the view grid, we can have buttons against each row and events against each row event, which is not available in Vega grid.
Case management functionality is not currently available. Regarding versioning, while it is available to the market, it is not optimal. If versioning is deployed on any application, rolling back is not possible. When multiple people work on the same module in different versions or branches, merging can overwrite changes. The merging technology needs improvement in Unqork.
Connecting to the database is straightforward, but querying MongoDB and getting results requires additional effort. Case management is still unavailable to the general market. We attempted to implement it but had to step back as it did not meet all business functionalities. The Vega versioning also presents development challenges despite business interest.
For how long have I used the solution?
I received training in Unqork during the last quarter of 2020. I have over 4 years of experience in Unqork since 2021, and I am currently working on Unqork projects.
What was my experience with deployment of the solution?
I have not personally encountered deployment issues, though some colleagues have faced challenges specific to their design style. Upon reviewing their code within my company, I found that these issues could be resolved through enhanced codes and configurations.
What do I think about the scalability of the solution?
Regarding scalability, performance shows some lag when retrieving data, loading styling, and loading pages. The speed and performance when connecting with different systems can be improved. I reported these concerns to the product team during one-on-one calls with the Unqork product team.
On a scale, scalability rates at 8 or 8.5, with room for improvement of 1 to 1.5 points. The platform still needs to incorporate AI, voice technology, and service request technology. For customer care applications, call integration directly into the application rather than phone systems would be beneficial.
How are customer service and support?
Unqork support is very effective. All requests raised have been addressed or received timely responses. The Unqork community portal and academy provide extensive information, with 60 to 70% of required information readily available. For additional inquiries, service requests receive prompt responses.
How would you rate customer service and support?
What other advice do I have?
Anyone, including freshers, can learn and start practicing in Unqork. I would rate this solution 9 out of 10.
Unqork includes multiple tools within its UDLC toolkit portal. It provides a release management application where users can select modules, data collections, applications, and workflows for promotion. The promotion process is straightforward and easy to learn.
Infosys, my current company, provides support and development for Unqork. Some companies partner directly with Unqork for product-related support. When product issues arise, service requests can be handled either by direct Unqork team members or partner companies.
In Unqork terminology, the term 'configurator' is used instead of 'developer'. Configurators do not need to write code for predefined elements in Unqork. While this feature is similar to Pega, Unqork offers more advanced capabilities.
Which deployment model are you using for this solution?
[Answer to 'Which deployment model are you using for this solution?' from the text]
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
[Answer to 'If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?' from the text]