Another month, another release!
Moving ahead to September, we have some new features incorporated into SpreadsheetWEB. This release brings you new features to make your data validation tasks more effective, make third-party applications integration easier, and manage application access as per your need. Before focusing on the documentation, let's take a quick look at this month's updates.
Interface with Excel-Based Data Validation for Input Grids
We have added new features to validate the input grid with the help of data validation which is based on Excel. Users can add Excel like validation rules for each cell in the grid and ensure the input data suits the rules. Indeed, this is ideal for individuals working with big data or any data that requires precision in the analysis. The system ensures the implementation of these rules of data entry without errors.
Simplified Single Calculation Endpoint
We have introduced a new API method featuring a simpler JSON structure, designed to facilitate no-code integration with third-party tools that support REST APIs. This new method offers fewer features than our standard single calculate endpoint, but its simpler structure is easier for third-party platforms to consume. We have successfully tested this method with popular no-code platforms such as Bubble.io, PowerApps, Outgrow, and Salesforce. Over the next few weeks, we will publish tutorial articles explaining how to integrate complex Excel calculations into these platforms using our new API method, without any coding required.
New Access Types for Designer Applications
To enable you to control the level of access to your applications even more effectively, we have decided to expand the Access Typesin designer applications. In addition to renaming existing options for clarity, we’ve introduced a new access type that caters to a variety of use cases. In addition to renaming existing options for clarity, we’ve introduced a new access type that caters to a variety of use cases:
1. Require Authorization: Formerly called “Restricted Access,” this option still retains the procedure that enters into force only with due authorization from the user through the rights module.
2. Require Authentication: The access type was “Unrestricted Access” before, meaning unauthenticated users can access the web UI, but API access is restricted to authenticated clients only. In other words, this access type is relevant only for API-based access. If you are deploying an application solely for UI-based access, it functions the same as “Allow Anonymous”. We have this access type because an application designed for UI-based access can also be accessed through an API.
3. Allow Anonymous: This new access mode grants all access to the applications via the web and API without any authentication. It is best for public consumption or where an application needs to interface with another without any user identity verification. Although record-saving operations will still be there, operations that save a new record will still need proper authentication to ease security.
