Using Stragiliti

Stragiliti makes enterprise application development simple because most of it is autodeveloped, not manually coded. Review its capability here, and if you want a more personalized demonstration, do let us know

A. 3 Steps to rapidly assemble your application, your product or a semi working prototype

  • Assemble your application, minimum viable product (MVP) or semi working prototype rapidly using Stragiliti in three short steps
  • 1. Define your project and processes
  • 2. Model the details of your processes
  • 3. Generate and use the application
Subscribe to Stragiliti. Then define your projects, the modules it contains, and the processes you wish to auto develop. Processes include typical masters, transactions and user interface used in the application. Processes are those transactions that typically have multiple use cases (like create, modify, update, view, authorize, cancel.)
The details of your processes are declared in english like definitions which can be modeled by process owners, product managers or business analysts familiar with software usage. It can either be defined in the Stragiliti Do it yourself tool, or in a spreadsheet and uploaded. The definition needs to be accurate with good knowledge in the use of application, but one does not need to know coding to model the application
When your model is defined accurately, it can be auto developed and defined on the cloud. During the auto generation process, one has to ensure that the definitions of the application are declared accurately. Autogeneration and deployment is an automated service done by the Stragiliti back office and usually takes about 4 to 8 working hours to complete. At the end of it you have a deployed application on the cloud. The timeframes here are between 3x to 100 x times faster than conventional development, depending on the application

B. Add Powerful features without coding

Applications auto developed on stragiliti are now ready for a number of powerful features that can easily be configured without coding, during application usage, by the application administrator.
Alerts are conditions within application that require your attention. Alerts usually depend on the role of the user logging in. On click of the alert one can see a summary and then one can drill down into the details of the same to the source transaction. The Alert can beco configured in Stragiliti without having to know coding.
Depending on the responsibility of the user in the business, different roles (like finance user, approver, employee or administrator) can be configured. To a specific role one can attach a specific set of processes or actions allowed, and then attach users to that role. User actions will then be limited to the permissions given for the role the user belongs to.
Based on the role in which one logs in, one can configure landing page panels which have useful information relevant to the role. Typical useful panels are Alerts, favourite (commonly used) processes, graphs, tables and links. Different types of panels are configurable which can be sequenced and sized depending on the role, and these will appear while logging in and using the application
While retrieving an existing transaction, one may have to go through a large number of transactions. One can make this easier by filtering the record of choice and then choosing the right one. In Stragiliti on can define the filters the user will use to rapidly retrieve the record.
Some processes require approval, which may require multiple personnel to approve. The process, the condition on which it occurs as well as the routing to be followed can be configured for use. Suitable alerts are available as and when the approval reaches a particular status or stage, enabling users to expedite the approval process.
The access levels of users who belong to roles can be configured. The permissions set is applicable to all the roles. Permissions can be set at a process level, as well as a specific action level - which means that a user in one role could be allowed all permissions while another can be restricted only to view or create a record
Stragiliti has many more powerful features needed for enterprise class applications including audit logs, token based encryption of transaction details etc. The list of these features are continuously getting added and being a subscribed user, you get access to them as soon as they are enhanced or new features added.

C. Manage complexity and change easily

Subscribe to Stragiliti. Then define your projects, the modules it contains, and the processes you wish to auto develop. Processes include typical masters, transactions and user interface used in the application. Processes are those transactions that typically have multiple use cases (like create, modify, update, view, authorize, cancel.)
As a part of the generation, webservices for server side interactions are automatically available for use in integrations with other applications, as well for customer user interfaces. These web services can be termed as micro (web) services since they are available at process and action combinations. This allows easier development and maintenance.
Under some special conditions it becomes necessary to write custom code. This could be for a specialized logic, or a specialized report or a specialized user interface. In order to ensure easy maintenance or change, the custom code written is clearly kept in a seperate area compared to the auto generated code. This makes it easy to keep modifying the application at both ends - auto generated and custom, allowing far more agiliti in usage and adaption of the application over the years of usage. The level of flexibility and agility is far higher than conventional applications. because of this.