App Designer

THE STARTING POINT FOR THE WEB APPLICATION IS THE HOME PAGE, REPORTING ALWAYS THE LINK TO THE APP DESIGNER AND, BELOW IT, THE LIST OF THE ALREADY DEFINED APPLICATIONS.

Through this menu it is possible to access to the App Designer or to any of the interpreted applications. In any case, when clicking on one of these links, the Login Page is showed: once authenticated into the system, the user can access to the functionalities provided by the selected application.

Since the default authentication & authorization system is based on the module provided with 4WS.Platform, the Login Page requires:  “Company Id”, “Site Id”, “Username” and “Password”. Typically the “Company Id” and “Site Id” values are defined initially, when creating and filling out the database schema.

Before using an application, the application must be defined inside the app designed.

 

THE STEPS TO FOLLOW DURING THE DEFINITION OF A NEW APPLICATION

  • Login into the app designer, without selecting any application. This will allow to define a new application.
  • Main application settings must be defined in the app detail windows, including its name, subcontext path, theme, logo, background image, menu layout and many other settings, specific for each application.

 

 

  • Once defined the look and feel of the new application, it is time to define the data model, in terms of objects and relations among them. Objects are usually defined through a few mouse clicks, starting from the list of the already existing database tables, for whom the object will be automatically created, through a reverse engineering task.

 

 

  • Views can be configured, again through a few clicks. Windows can be created starting from the list of objects previously defined: it is possible to create any number of windows and panels, for each object and its outgoing relations. A wizard leads the user through the definition task, by choosing the right panel (grid, detail form, filter panel, tree, image panel, map or their combination), which is defined using the metadata extracted from the selected object.

 

 

  • Ad hoc business components can be created, based on objects and their relations, by adding additional filter conditions, by adding or removing inner/outer join relations. Furthermore, business components to feed grids or forms or trees can be defined starting from web services or lists of documents coming from a CMS.

 

  • Panels can be refined in terms of grid columns, input controls, filters, events. Users can in any time change the default settings for these components and customize in many ways their behavior.

 

  •  The application menu can be organized in folders and menu items. Reports (based on Jasper Report templates), shell commands and web services can be started as menu items, too.

 

 

CUSTOM CODE

There is always the chance to add additional files to the application, through the specific import functionality that reads a .zip file. This file can include:

  • Custom javascripts, automatically loaded by the web interpreter
  • Custom restful web services and custom EJB or Java Beans, automatically recognized and  loaded by the web interpreter
  • Css, images and any other static content, used to define an ad hoc theme for the application.

 

EXPORT/IMPORT

4WS.Platform makes it easy to move application metadata from one installation to another one: in this way the application defined in a development environment can be imported in test or production environments as a simple .zip file.

Custom content can be exported and imported to another environment in a similar way.