Low-code Platform "WebPerformer"

For login authentication, you may develop applications which are compatible with basic authentication and form authentication commonly used in web applications. Also, you can control access to the menu items and fields and buttons on the screen based on the role information assigned to the logged-in user.

The screen generated by WebPerformer consists of a main area generated from repository information and a header / footer area. In the header / footer area, you can write HTML and JSP, so you can customize the company's logo and link to the portal site.

Information defined in the repository can be output in HTML format as a specification document. Documents that are synchronized with the repository definition can be output at any time, you may save time for creating and maintaining design documents.

We provide functions to export repository data as an XML file. By registering the exported XML file in SVN(*) etc, you many control the versions od the repository. Also, the exported XML file can be imported into the repository by the import function. (*) SVN stands for Apache Subversion. It is an open source application which manages the source code etc. of the program. It is widely used for source file version control when developing programs.

Yes, it is possible. For example, it is possible to develop applications using Oracle as master database and SQL Server as actual database.

Yes, it is possible. The scope of the transaction is the business process called from the screen. If a DB error occurred during execution of a business process, all data model operations called from the business process are automatically rolled back. Also, if you want to define a process that you do not want to roll back as a whole business process when an error occurs, you can execute commit processing on a table-by-table basis by specifying "independent commit" for the target data model operation.

You can create logic by defining data model operations and business processes. As a data model operation, you define the operation to the target table and how to modify the data. For the business process, you describe the order of invocation of data model operation using branch instructions. Data model operations are processing logic for tables in the database. Business processes control the order of execution of data model operations.