Skip to main content

Power User Spotlight: Ranghanathan Lakshmi

Ranghanathan Lakshmi

Accenture Associate Manager Ranghanathan Lakshmi explores what it takes to build complex enterprise software today

Ranghanathan Lakshmi has 10 years of experience as an enterprise developer. In recent years, he has been an avid user of Unqork’s no-code platform for a variety of companies, most recently with Accenture where he is an Associate Manager. We explored the challenges of modern development and how no-code helps him address them.

What is a recent project that you developed using Unqork that you are proud of?

Ranghanathan: We’re currently building an exception reporting tool for an Australian bank. The previous version required a lot of manual tasks that forced users to search through a huge set of data. Not only were there lots of errors, but building the exception reports took up a lot of time. 

We built the POC using Unqork in just two months, complete with various data analytics functionality and robust RBAC settings. 

The primary concern for the client was the ability to extract the data from various files and corroborate the data from those files. These records were huge, and the processes involved were tedious. We built the POC using Unqork in just two months, complete with various data analytics functionality and robust RBAC settings. 

We used the File component and Data Workflow for data structures, while we leveraged data analytics to build out user-facing charts and dashboards. The client was impressed and happy with how fast we were able to move, and we closed the deal. Now, we are building the actual production-ready application. 

What parts of the Unqork platform do you enjoy using the most?

Two things come to mind: Data Workflow features and how Unqork handles deploying to higher environments. 

The Data Workflow makes my job of structuring JSON easier thanks to the various operators involved that make the conversion quick. That’s quite difficult to achieve in programming language applications.

The deployment to higher environments is also quite easy in Unqork. With just a few clicks, we can deploy to any environment. The revision history makes it easy to roll back to previous versions if necessary.

The Data Workflow makes my job of structuring JSON easier thanks to the various operators involved that make the conversion quick. That’s quite difficult to achieve in programming language applications.

Is it easier to accomplish key tasks with Unqork than using a traditional code-based approach?

Yes, absolutely. You can accomplish a lot by configuring different Unqork components such as Data Workflow, Calculator, and Decision components. The Unit Testing feature is a differentiator because it allows you to test while you build. You can check values to see whether they’re working properly and whether the logic is returning the designed output. 

If there is any issue you don’t need to log in to the rendered application view. You can just debug the issue in the no-code interface by entering and testing various input combinations. This is very rare in any other low-code/no-code applications.

What are some best practices you’ve discovered using Unqork to produce the most value?

From a development perspective, we use camelCase for all propertyIds as best practice. We started to do this so that it is easier for us to maintain unique propertyIds for each component, which makes debugging easy. Another thing that streamlines debugging is adding Unit Testing for our Data Workflows and Decision components.

Also, we arranged components in linear order based on how they are displayed on the screens. When someone reviews or analyzes our build, it’s easy for them to start from top-to-bottom to follow the application logic. They can see how the application executes based on our configuration, and having the components in a linear order speeds up the reviewing process.