Easy Configuration
Standard Form layout templates allow multiple columns & grouping of fields.
Fields to be shown on the form can be selected individually either by the administrative tools of fmWEB or the database.
The list View provides the following functions:
- Inline or form-based data editing with intergrated data explorer
- Data Import/Export to a File.
- Sophisticated Search Form
The Master/Detail View additionally provides the following advantages.Crosslink to other data within the same or another database.fmWEB commonly uses such views to show Assets linked to Work Orders and Work Order History, Work Orders linked to Labor, Parts or another. This can be comfortably used to check and create new Work Orders from History Data, Tasks, Projects or external data.
All Forms and Views can be configured and used individually for each page of fmWEB.
fmWEB is based on an application framework that can handle serveral database connections. For example, Labor and Parts data may originate from another data source.
This concept has serveral advantages besides the fact that those data need not to be imported and synchronised with the main database source.
The Online Help is available for each fmWEB page and is connected to the integrated HTML editor. Besides this, the HTML editor is used for the document management of fmWEB, making it a versatile and easy-to-use tool to store any form of document in fmWEB. This allows users to easy retrieve any information.
Extending fmWEB
fmWEB can integrate additional databases into its versatile framework.
This make data access and integration to central data stores or applications easy and avoids redundancy. IT further reduces costs for interfaces and its maintenance. We have done a similar approach by integrating Microsoft Reporting Services.
A common place for such an solution may be the parts and labor management, which is mostly realized by a daily data sychronization.
Creating a Client Request Form
Creating a Request Form/Page involves the following 3 steps:
Creating a viewWORequest_Standard containing the fields to be displayed;
field properties need not be specified. as they are already known to the system.
Link to SitemapLinking the view into the Sitemap of the application
Template to useDeciding which template to use.
That's all; the rest is done by the application framework !