/** * The main template file * * This is the most generic template file in a WordPress theme * and one of the two required files for a theme (the other being style.css). * It is used to display a page when nothing more specific matches a query. * E.g., it puts together the home page when no home.php file exists. * * @link https://developer.wordpress.org/themes/basics/template-hierarchy/ * * @package WordPress * @subpackage Tally * @since 1.0.0 */ ?>
Tally has been a thick client that runs on the Windows platform in isolation, with no requirement to connect to external systems for a long time. But with the changing business landscape and market demands, Tally is transforming and delivering features that require it to be connected to 3rd party entities. Some of these features are---e-invoice bill generation, sending payment links via WhatsApp, GST upload/download and filing returns, and so on.
The following article is intended for both technical and non-technical audiences, hence you may find some of the information abstract or at bird's eye view. Please reach out to us directly for more details with respect to the technical implementation.
Note: Sandbox is a kind of server that is developed by the 3rd party entity to simulate the actual production server.
During the initial development phase (where the connection with 3rd party is not yet ready), where we have the required specifications from the 3rd party; we have some of the following challenges/requirements to sign off the initial releases:
There are two ways for QA:
To address the challenges with 3rd party integration, at Tally we decided to develop our own Mock server (a kind of sandbox that is developed for Tally Solutions by the Tally QA team). This helped us to overcome all the challenges that were mentioned earlier and helped us with better automation.
Integration with a 3rd party has its challenges, but here in this article, we will focus on what are the challenges that the QA team faces to test and certify the features that the Tally client needs to talk to 3rd party entities. Following are some of the challenges:
Developing our sandbox has its own set of challenges and/or requirements:
The Mock server developed has the following mechanism in principle:
Following are some of the aspects which Mock Server needs to support:
Following are some of the finer details of how the mock server is built:
So, when a request is received at the mock server, the mock server extracts the type of request, endpoint, keys, and values from the request and compares what is already set. It will pick the matching response and responds with that response status code and payload.
Having an in-house mock server has the following advantages:
How to Easily Shift/Migrate Your Data to TallyPrime
Nuts & Bolts of Tally Filesystem: RangeTree
A Comprehensive Guide to UDYAM Payment Rules
UDYAM MSME Registration: Financial Boon for Small Businesses
Understanding UDYAM Registration: A Comprehensive Guide
MSME Payment Rule Changes from 1st April 2024: A Quick Guide