Priyanka was introduced to the Unqork platform in early 2021 after five years as a backend engineer working in Java databases and services. In less than two years, she has become a Certified Professional Configurator and taken a leadership role with her team at Accenture. To top it all off, her entry in the 2022 Unqork Creator Hackathon—an expense tracking app—won first place.
Tell us about your award-winning Hackathon project?
Priyanka: I created an expense tracker application using different features of Unqork, including the workflow module, dynamic grids and free-form grid, and Unqork Marketplace snippets. The application helps employees claim their expenses. Once entered, the submissions are routed to management for approval or rejection. The application also includes dashboards for employees and managers, email notifications to employees upon approval, and cash transfers based on the employee’s bank details.
How did the Unqork platform enable you to build this solution so quickly?
The Marketplace snippets helped me a lot, especially functionalities like date pickers and single upload files. I was able to easily modify them according to my needs. The app also included complex logics such as loops, and Marketplace provides a variety of loop snippets, including batch loop.
I also used API configurations and SSN masking. I just had to implement the logic, and those features were easily available in the modules.
In addition, Unqork’s enhanced grid system helped a lot. It has lots of inbuilt functionalities similar to Excel spreadsheets. And the nested data structures and inline functions made things go faster.
With Unqork, the entire application can be built surprisingly fast, thanks to its cloud-based architecture. That means we can really focus on client requirements, rather than building complex coding structures.
Tell us about some of the most exciting projects you have built using Unqork on the job?
Currently, I’m working on an insurance project with a centralized workflow that enables vehicle insurance quoting. The application has multiple external interfaces, timers, and also includes a variety of different roles. It has a dashboard too, with a graphical overview of KPIs.
How does working with Unqork compare to your previous experience as a developer?
Before Unqork, I was working in Java. We would work for months or years on huge, code-based applications. Just fixing runtime errors and debugging was really time-consuming.
I was lucky enough to be introduced to the Unqork platform after this coding journey, and I can see a huge difference. With Unqork, the entire application can be built surprisingly fast, thanks to its cloud-based architecture. That means we can really focus on client requirements, rather than building complex coding structures.
How does Unqork change your day-to-day experience?
I really like working with Unqork. It has allowed me to work on a larger variety of projects, and also across different domains. When I was coding, I was much more limited. I worked only within a single domain. Also, we were confined to one aspect of development, For example, testing and promotion were handled by different teams, so I didn’t get much exposure to the larger software lifecycle. With Unqork, you can visualize the entire flow. You can easily build, test, deploy, and promote an end-to-end application in no time.
What is your favorite thing about creating with the Unqork platform?
With Unqork, you can be more creative, because you are able to build an application just by dragging and dropping. Complex logic—sending emails, automating Google addresses, maps, charts, and graphs—are very easy to implement, and so are third-party integrations. I also really enjoy data workflows, which have a lot of functionality and can be configured in multiple ways. You can even visualize the data flow. All this gives you a sense of confidence that you can build any application end to end.
However, my favorite aspect is security and encryption, which is required in a perfect application. I particularly love the role-based features in Unqork. I recently built an application with lots of different roles for different users, including a portal with different views depending on roles. Unqork made it much easier to handle all of that.
Do you have any best practices to share with your fellow Unqork Creators?
First, when you are creating a module for a large application, there can be a huge amount of components. It really helps to break those modules into smaller modules, and then import them to the main module.
Also, the naming convention is very important, especially in a large project. It helps other Creators understand a module’s logic properly and ensure things like proper error handling for better performance.
You Might Also Be Interested in
