Objective

To create a centralised control of all commonly used dimensions in modules such as products, departments, staff etc so that any changes in them automatically updates the underlying modules data.

Delivered Feature Set

1. Created ability to generate multiple lists and blocks in one go (using javascript and jquery front end framework).
2. For drag and drop used jquery drag drop ui API.
3. For persistence data used JSON and AJAX.
4. List added, were both in platform platform as well as google drive with multiple validations.
5. Ability to assign list from selected row to all the rows below selected one (also update the corresponding google sheets).
6. Ability to move items between list and blocks
7. Validations
   1. to restrict,user to create duplicate list
   2. Also to restrict a module to which have already assigned list

Delivery Success

This provided the required centralised control of all commonly used dimensions and automatically updates all the underlying modules data. This provided the desired speed and accuracy to the module development process.

Objective

For our financial modeling domain project we need to visualize the customer data on dashboard by virtue of multiple charts

Exploration of possible solutions

For charting related taska we have decided to use Highcharts as it provide rich API which is simple and easy to use. It also provides important functionality which fulfills the requirements, key features that helped decisions

1. Open Source with Commercial Options
2. Responsive across devices
3. Annotations
4. Flexible styling

Delivery

In order to provide more insightful data, we provided this tool to create and add charts to dashboards. We pass following parameters through the API, to create chart

1. Chart name
2. Axis
3. Chart type (line, column etc)
4. Chart stacking (normal, stack)
5. Chart data, format

Charts are provided to be created in two ways

1. Interface for the users to create their own different types of charts
2. Developer can pass the parameter in the uploaded file and charts would be automatically

Chart are also provided to be created against

1. Single axis
2. Multiple axis

Delivery Success

As desired by dashboard tool , we were able to deliver customers an intuitive interface and solid stable code that allowed them create their dashboards, made up of multiple types of the charts and on multiple axis; and Stacked/Normal.
This tool is widely used and loved by the customers.

Objective

Delivery Success

Objective

Financial Modules are in core of Financial Modelling plan. This functionality is developed to enable end user to create an OnPlan Financial Module within the Platform which inherits all the attributes of the Parent Financial Model.

Delivery

• For creating an OnPlan Financial Module in the platform, we set
• Technology Stack
• Back-end
• Java, Google Sheet API
• Front-end
• HTML5,css3,Bootstrap framework,javascript,jquery
• Middle-Tier
• Google Client Library
• Framework
• Spring, Hibernate
• Methodology
• Agile- Scrum, Cultural DevOPS
• following set of features & functionality

1. Created the required metadata at the time of creation.
2. Set the parent Model time series
3. Set other related model meta metadata such as display name of module
4. Implement forecast logic as per Google Sheet/drive provisions
5. Create Module with first few blank rows for user to do immediate actions
6. Create module also in the calculation engine i.e. on google sheet on clients dedicated drive to be in sync with platform.
7. Extend the QB mapping functionality to the created module
8. Extend the List & Blocks to the created module
9. Also extend the Create Chart functionality
10. Extend all Editable features such as
    1. Add new Row
    2. Copy Row
    3. Move Row

Delivery Success

Creating a financial module use to big exercise and needs lot of experities in the Financial Modelling world, With this functionality, end users can create a new financial module with in few minutes and with basic knowledge of Financial modeling and platform provisions.

Objective

Delivery Success

Objective

Delivery Success

Objective

Delivery Success

Objective

Delivery Success

Objective

Delivery Success

Objective

To implement a mechanism for logging every user transactions that any user has wroteed in the platform so that later an audit can be performed when any data problem comes to notice.

Delivery

1. Centralized provision was placed inside all the places in product from where transaction can be initiated by the users.
2. Utility written to perform complex calculations that can be triggered due to the change and measuring its impact and shift from original values.
3. As future development of classes initiated from template file, this change log code becomes automatic part of finally block
4. This method inculcates method name; from which functionality the change log is invoked like user name, data and time of transactions, the controller name, and the process initiated by the transactions.
5. Change log UI designed and developed intuitively where user can filter of multiple columns simultaneously.

Delivery Success

This functionality proved to be path breaking for the problem identification and solving; problems that arises in the platform. This centralized and well executed functionality become pivotal to solve any data related issues for critical financial modelling perspective.

Objective

Delivery Success

Objective

Delivery Success

Objective

To upload an excel file that is having data as per defined structures into the platform in a seamless manner

Delivery

1. Structured excel file is parsed using Apache POI libraries; it validates the files against the defined structures for the model to be uploaded.
2. Upon successful validations, files gets uploaded to the corresponding google sheet account.
3. Subsequently, creates a google spreadsheet in google drive with the same name as the uploaded excel name by using BatchUpdateValuesRequest class provided by Google API.
4. Next, copying all the sheets present in the excel to the google spreadsheet with the help of SheetProperties and CopySheetToAnotherSpreadsheetRequest classes. (to keep part of the same financial model, one spreadsheet= one model)
5. Implementing data massaging (as google imposes limits on number of cells in spreadsheets)
   • Deleting extra rows and column
   • Rectifying ‘REF errors’ by connecting sheets as per the formula if exist or just removing the formula and making it a normal value.
   • Restricting duplicate copying of sheets.
6. Segregating formulae and normal value to give a clear vision to the user about the data and their relationships
7. Providing similar user interface like excel to alleviate the risk of confusion in understanding the application separately.

Delivery Success

Implementing this raised us to a new milestone as we could use the benefit of using google sheet as our cloud computing engine and saved significant efforts to develop own calculation engine for financial modelling. Further this helped with google precisions of calculations.

Objective

Delivery Success

Objective

Delivery Success

Objective

Delivery Success

Objective

Delivery Success

Objective

Web application we developed was also expected to connect to Salesforce so that SalesForce data can be used for the Financial forecasting by the platform.

Delivery

Exploration of available alternatives for the best platform usage

1. Web Server OAuth Authentication Flow – For the Apps that are hosted on a secure server to make use the web server authentication flow.
2. User-Agent OAuth Authentication Flow – The user-agent authentication flow is used by client apps (consumers) that reside on the user’s device or computer. But, because the apps are widely distributed, the client secret are difficult to be kept confidential.
3. Username-Password OAuth Authentication Flow – totally out of context for using this for the platform implementation

Upon all candidates evaluations, it was arrived that the best way to get your platform gets authenticated with Salesforce is the Salesforce OAuth 2.0 system. It is because it supports the required web-to-server, one time interaction ( those between platform in google clouds and a Salesforce Connected app)..

Delivered Functionality

1. Keeping in mind the Salesforce architecture, we implemented one common callback controller. This served the following services
2. Handles the call back request from connected app (our app in Salesforce App Store).
3. Retrieve & save the access token in one centralized credential table, that maintains client wise information
4. Sending back Responses to the connected client’s instance.

Delivery Success

Post this authentication, we were able to seamlessly connect to Salesforce data and retrieve whatever we wanted and store in the platform. This stored data was sufficiently consumed the client for their analytics and projections.

Objective

Delivery

Delivery Success

Objective

Our platform used existing excel financial modules to be uploaded and to create them as cloud platform financial modules.

Delivery

1. We uploaded the excel file using spring multipart file upload, to our platform.
2. Subsequently, we parse and extract the excel data using Apache POI from all the sheets and load it into our DB.

Various Classes and methods used of Apache POI, for the purpose
For workbook related operations
XSSFWorkbook workbook = new XSSFWorkbook();
For sheet creation and getting the sheet from workbook
XSSFSheet sheet = workbook.createSheet(“sheetname”);
XSSFSheet sheet = workbook.getSheetAt(i);
For row related operations
XSSFRow row =sheet.getRow(index)
XSSFRow row =sheet.createRow((short) i)
For cell related operations
Iterator <Cell> cellIterator = row.cellIterator()
Cell cell=Row.getCell(i),
For getting cell Values
getStringCellValue(), getBooleanCellValue(), getDateCellValue(), getCellFormula() etc.
For cell styling
CellStyle and its method like setDataFormat(), getDataFormat()
For data formatting we have used
XSSFDataFormat dataFormat =workbook.createDataFormat()

Delivery Success

As this was the very core foundation of the platform, Apache POI java library greatly helped us to accomplish our objectives

Objective

This is about the uploading the existing financial models written by the prospective customers.in excel in their own format, a format that platform does not recognizes.
This tool was intended to intuitively extract & transform the customer format and load into the platform into the platform format.

Delivered Feature set

1. We first identify whether the uploaded file is as per platform structures or not by using Apache POI java library (Using classes: XSSFWorkbook, XSSFSheet, XSSFRow, Cell, CellStyle).
2. If the file is NOT per structure, we prompted the user to upload it via this tool.
3. Then, we first extract the excel file data using Apache POI and show it on this ETL tool interface for the ‘transformations’.
4. On this interface, the customer is prompted to transform his data into platform style through a guided tool. The tool asks the customer to select and map the data and data range according to our platform model structures.
5. Post mapping, the modified data is requested via JSON to be pasted to the google sheets and upload the file into corresponding google drive and convert into a spreadsheet.
6. We further massaged the data and delete still unwanted data from the google spreadsheet Using Google Sheet API methods and classes ( BatchUpdateSpreadsheetRequest, AppendDimensionRequest, CutPasteRequest, GridRange, GridCoordinate, BatchUpdateValuesRequest )
7. Now that the data in google spreadsheet is according to platform model structure, we call platform upload services to load into the database.

Delivery Success

Prospective customers were successfully able to upload any of their excel models and able to use them as a platform model in very quick time.

Objective

Delivery

Delivery Success

Objective

Delivery

Delivery Success

Objective

Delivery

Delivery Success

Objective

Delivery Success

Objective

Delivery Success

Objective

Delivery Success

Objective

Delivery Success

Objective

The project was based on the heavy JSP pages that needed a lightweight and totally responsive UI.

Delivered Feature Set

1. Designed fully responsive financial modeling theme and implement them in the products for (modules views, drag n- drop interface, dashboards, user views, file upload, ETL tool)
2. Made interface for every type of data visualization like Charts, Dashboards, widget boxes, grid views, tree grids etc
3. Developed fully customized and fully editable components for the views.
   1. Dynamic list and blocks
      • (Input and JQuery event )
      • (JSON and AJAX)
   2. Dynamic grid data change
      • (Input and JQuery event )
      • (JSON and AJAX)
   3. ETL tool for transformation
      • (Cell selection and focus change)
      • (JSON and AJAX)
      • (Javascript and JQuery events)
   4. User commenting
      • (Dynamic HTML for comment messages and UI)
      • (JSON and AJAX)
      • (Javascript and JQuery events)
4. We have developed an interface for dynamic contentations .For editing data of cell click on cell Input will appear dynamically and after change value click anywhere on the platform dynamic input content goes off.
5. Developed drag and drop interface and also designed thumbnails for financial modules using JQuery drag-n-drop API and JQuery event.
6. We have customized and implemented pre-designed theme- Metronic Theme
   1. Customized Side nav In multi-level
   2. Change Theme popup model themes
   3. Change theme table structures per requirement
7. We have customized themes for messaging and info sharing in the platform.
   1. BootBox
      • Use for confirmation box(BootBox.confirm(<Message Here>))
      • Use for messaging and alert(BootBox.alert(<Message Here>))
   1. Toaster
      • For every event notifications(Toaster.Success(<Message Here>))
      • For Error Handling Of AJAX(Toaster.Erro(<Message Here>))
8. Also developed themes with using frontend frameworks like (BootStrap, vue.js and many more…).
9. We have developed some specific themes using (JQuery UI)
   We have designed fully responsive and user-friendly UI for multiple projects . and also implemented pre-design interfaces in the products and customized as per customer requirements.

Objective

Excel modeling files that gets uploaded in platform, needed to have an interface that can move the uploaded files thumbnails using drag-n-drop to their respective destinations (Financial Module Areas).

Delivered Feature Set

1. Created interface that had a clean list view of draggable components ( thumbnail of excel models).
2. This provided user with ease of draggability to the destination (In left nav); user can select any thumbnail, make it draggable by single click event and further move using mouse to the destination.
3. In an enhanced feature request, the dropped assets (financial modules) can again be dragged, with in another draggable area within dropped region.(resolved many conflicts with existing functionality)
4. After drop, iterated all the assets (Financial modules) inside the dropped destinations.

Delivery Success

This interface provided an easy & flexible draggable contents ( single sheet or multi- sheet excel, both) so that dropped items (financial modules) are ready for further expected transactions in the platform. It has been working in seamless manner since last 18 months without any customer reported issues.

Objective

Once a new release is needed to be deployed to customer instances in an automated manner. In our delivery model where each customer instance is unique, and each customer instances also needed to be updated with the latest release.

Delivery

We maintains all changes in a centralised database. Then using MySQL Utilities, we
compare the each instance database with this uptodate centralised database. There were following type of changes observed, that goes with almost each release; such transformations were initiated and completed with single click of the button (automated updation of the releases)

1. Add New Tables
2. Drop Tables
3. Update Procedures
4. Alter table (Add/Drop columns, Add/Drop properties -add primary key, make foreign key,update cascading).

Delivery Success

Customer Instances are getting updated with latest data structures in seamless and clean manner.

Objective

Delivery

Delivery Success

Objective

Platform has multi-instance SaaS architecture due to uniqueness of structure of each instance.
However for the sake of simplicity and controllability, one centralised login was required; that should authenticate centrally and then redirect it to the respective instance (very much like SalesForce.com)

Delivery

1. 1. We have create one centralized application as login app and have all customer user data was moved to centralized table in the database; so that users of all distinct instances can login & authenticated through this centralized login server. (Incase any user want to access directly their instance without login then they will be redirect to this login app)
   2. Once any user login through centralized login server after successful login, we generate one unique access token using our tokenizer services (and also save this to database).
   3. After successful login, we subsequently call our instance redirection services and redirect the user to the corresponding instance along with the access token generated.
   4. On the instance, we check whether the request contains the access token or not and validate this access token from the DB.
   5. If the token matches, then we create the user session (using the ‘session generating services’) and process user to his instance .

If token cannot be validated, then redirect the user back to the centralized login app.

1. This also helped in our integrations like Quickbook and SalesForce, where we are able to use only one configuration account (client id, client secret and redirect url) overcoming limitations of multi-instance SaaS model.
2. For the associated use cases that of Quickbook and Salesforce call backs, we set the instance id as payload param to identify which instance response is this; so that we can to redirect to appropriate instance after their transactions.
3. After QB or SF transactions, we get the access token from api call back response (which contain realmId and auth code in json response) and save these auth token into DB ( to be used for future requests)

Delivery Success

Any user of every instance was seamlessly able to use their unique instances and along with their respective QuickBooks & SalesForce accounts. All operations are running seamlessly and successfully, according to their respective roles and permissions.