Screen Form Builder

The screen form designer has two implementations - for Windows Desktop applications and for WEB applications - SrWebExpress. The main difference between these tools is that the main focus in developing application has been shifted from development to customization. Which means most part is performed not by a programmer, but by a business analyst.

The designer allows you to create new screen forms using simple visual settings.The created creen forms can be used in all functional modules of the system. These forms can be used to build business process models, to expand the functionality as separate dynamic frames on existing forms, as independent dialogs. This approach allows you to create an individual version of the software product, meeting the requirements of a particular client, thereby significantly expanding the capabilities of the system.

There are two kinds of dynamic forms available for setting up. The first one is a regular, multi-tab dialog with a standard set of customizable parameter types and a Grid-type form.

The main functionality of the SrDynamicForms constructor:

• Creating dynamic information "footers" for any screen forms of the system
• Setting up extensions for parameter sets of most system objects
• Setting up autonomous subsystems with their own object types, operation models, business processes, filtering and sorting tools
• Setting up "multilayered", cascading forms for editing system objects of any complexity
• Setting up complex ways of visualization, control of input values, calculation of interdependencies between object parameters during its editing by the user.

In accordance with the requirements of a specific business process, the screen form allows to configure:

• A set of typed data entry fields (date, text and numeric fields, check-box, etc.)
• A set of dmalog form visualization options (Tab Sheet, watermarks, separators, etc.)
• Layout of fields – both vertically and horizontally
• Configuring related fields
• Rules for simple validation of input values (check for fullness, range of values, etc.)
• Rules for complex validation of input values (using Pl/Sql, Groove)
• Using linked lookup Selectors ( for example, selecting accounts for the selected counterparty)
• The ability to impose a "where" condition for the lookup Selector, regarding changes in the selected values of any input fields
• Rules for the visibility, availability and mandatority of fields (including dependence on the values of other fields, on the process or process stages)
• Setting up autocomplete rules for the fields. Procedures and functions (Pl/Sql, Groove) may be used to calculate values.
• Setting up an event-based form model (eg Init_Form, Edit_Form, Save_Form, etc.). These events can be used to set up a stack of procedures and functions to execute both arbitrary business logic and to render the form itself in Run Time mode
• Default field values