Design Apps

ASG-Studio helps businesses to rapidly design, develop and test the process apps for both web and mobile with single code base. Businesses can build the applications with zero / low code which do not require developers to have any knowledge of complex code. The business analysts / process owners can configure the data model, define the process model, design visual model with the use of drag and drop elements which creates single code base for the target operating system. Using the single code base simply deploy both browser and mobile applications for the business users to initiate, execute and complete their specific day-to-day tasks.

In ASG-Studio, each app is a Project which includes the required resources for an app such as Datasources, UI Model, Process Model, Decision Model, RPA Model, Queues, and App Roles.


Project

Project is a place holder for all the required resources to design your apps. Create a separate project for each app that you design in ASG-Studio and add datasource, UI model, process model, RPA model and app roles as required. See Create Project.


Datasources

ASG-Studio provides open data access by using datasource integration. Datasource integration enables the applications to access multiple data repositories, such as ERPs, Mainframes, RDBMS, and Flat files for accessing and processing the data for business purposes. A datasource object has properties that can be modified when necessary. For example, if the datasource is moved to a different server, the property for the server can be changed. Since datasource properties can be changed, any code accessing that datasource does not need to be changed. See, Create Datasource.


UI Model

The UI Model visual designer provides you everything to design your app. It has been designed to make your application development more efficient and faster with a no-code or low-code builder.

The UI Model visual designer that you use comes with a collection of widely used ready made controls which you can drag and drop onto the canvas to quickly design the application and its user interface. Controls are a type of user interface elements that the user would use when interacting with the application and perform a specific task. Based on your requirement, configure the actions performed by them using control settings. You can also bind the UI controls with custom scripts to invoke web service task, function calls, process tasks, and route tasks. You can use CSS to customize how each control is displayed on the user interface. The UI Model visual designer also provides you the options to define the application page life cycle, for example, you call a specific data table when a page is loaded or trigger particular action at a specific point of the page lifecycle. See, Create and Design UI Model.


Process Model

Process model is a graphical representation for specifying the sequential series of events, tasks, and decisions that form an application process. Process Model when integrated with UI Model enables the applications with the flow of tasks required to achieve specific business process goal. See, Create Process Model.


Decision Model

Decision Model is a modeling notation for decisions that will support business rules. The decision model when called into a business rule task in Process Model, provides a mechanism for the process to provide input to a business rule engine and to get the output of calculations that the business rule engine might provide. See, Create and Design Decision Model.


RPA Model

RPA model is a graphical representation of related and structured activities or tasks that can be performed by a bot. The activities that you can use in your RPA model are grouped based on type and target application. Each activity consists of a custom set of actions, such as mouse click, renaming a file, creating excel worksheet, or opening an application. You can define the properties of each activity based on your requirements. See, Create RPA Model.


Queues

The Queue holds work items that can be processed by number of users who are assigned to a specific app role. You can associate the queue to a user task in your process model. When the process is executed and the corresponding user task is triggered, the task will show up in the users queued tasks. The task is not assigned to any user, but the user can claim the task which will make that one user the assignee. Then the other users will not see that task in the queued tasks any more. If the assignee releases the task before it is completed, the other users can see that task in the queued tasks again so that one of them can claim the task. The queue can be associated with user task only. See, Create Queues.


App Roles

App roles are permissions to a specific role pack within a deployable application. App roles allow you to desing and test the application on one server and deploy it to several other servers without having to redefine permissions on each server.

As you map the application roles to enterprise roles, the enterprise roles you define as per your organization requirements and the users that belong to each enterprise role are the foundation of access control. See, Create App Roles.