Stragiliti – Features is a low code development platform meant for process owners and citizen developers to take the lead in building products and applications rapidly, with much lower effort than conventional developed. It can also be used by seasoned developers to accelerate the pace at which software is being developed, and enhance collaboration and accuracy in the development process. Complex applications that can scale to thousands of users can be modeled and deployed using Stragiliti. The platform covers the following broad areas


1. Modeling

The following are some of the aspects of the application that can be modeled for subsequent auto- development

Projects Define one or more applications as projects
Processes Define processes that form a core of the system and model them
Modules Group processes into modules for easier packaging and visual depiction
Process Detailing Specify details of business processes with accuracy in depiction, providing details of individual elements
Application Codes Typical codes and data types used in the application
UX Interfaces Define various user interfaces, integrations for processes
UX Interface Detailing Detailing out the layout, the sections and the elements of the user interface
Views Define views by which one can filter, view and extract data
Record Pickers Define filters for retrieving records and views
Standard Rules Standard rules like validations, unique keys, defaulting, data size verifications are modeled semi-automatically
And more …

The models are then used for auto-deployment as per the next step

2. Auto develop

The model is used to auto-develop significant part of the application. The auto-development is done as a semi-automatic process typically done overnight by the Stragiliti team.

All the processes, UX interfaces and views modeled, most of the rules are auto developed. The auto development covers the following

  • The user interface layer which is seen by the user. The interface is usable via the browser. It is responsive in nature which indicates that when the aspect ratio of the screen changes the application adapts itself accordingly. It is also usable in the leading browsers. Front end validations are also applied
  • The service layer on the cloud, which is exposed yet secure for use by different devices, user interfaces as well as integrations
  • The business logic layer where key server-side business logic is executed
  • The database interaction and the actual data layer where data is stored

3. Attach Extension Code

The user interface auto-developed is the standard Stragiliti one. One can replace this with manually written user interfaces (e.g. in html5), in case a specialized one is needed. The standard interface can also be published to Android and iPhone native devices.

Additional business rules that could not be modeled can be plugged in at the right place as extendible rules – on the server side as well as the client side. These rules are typically SQL statements or front-end validation code.

The written code is well separated from the automatically coded areas and hence when changes occur in the automated areas, change management is not difficult.

4. Package and Deploy

The application, so far available as code, is then packaged for deployment on the cloud. It is then deployed and published as a working application on the cloud. This part of the Stragiliti service is also done by the Stragiliti team overnight. The deployed address is available for use – whether it is a prototype, MVP or a production version.

5. Run time Utilities

Once deployed the user can configure many features which can be deemed as ‘auto developed’ during run time. These features are detailed here

Roles One can define new roles
Users One can define users
Permissions Permissions can be set up for role and user combinations for processes and specific actions for a process
Menu One can configure the menu in which processes are grouped
Approval Workflow Setup approval routings and workflows for specific processes. The number of steps of approvals and the users / alternate users who perform the approval can be configured
Role based dashboards Set up dashboards for specific roles and attach panels for the same. The visual display of the panels can also be rearranged
Alerts Set up alerts that appear on the panels for specific conditions or situations – so that users can initiate the next step of a workflow – when pending
Email Notification Configure Email notifications based on occurrence of a event. The mail content and the variables used in the mail can be configured
And many more …

By completing the run time modeling, the auto development, deployment and run time utility configuration the application is ready for use.