Transaction scenarios : prefab online apps.

Access modelling : design how end-users access available applications from marketing pages, navigate between use cases and possibly switch from one transaction to another.

Workflow modelling : each transaction is given a specific workflow, composed of prototyped screens. The generic workflow includes the following stages : preconditions, configuration, confirmation by the user, confirmation by the system.

Conditional paths can be modelled and possible additional screens can be added for error messages, warnings and opt-in screens.

Screen modelling : you can customize each screen with WebMS WYSIWYG ++ screen modeller.

Easily add recordsets, group and ungroup them, edit their multilingual description, add support data (help links, FAQ's).

And of course, error handling features (multilingual error messages, client-side data validation) are available.

Transaction scenarios have been conceived to help you build robust and flexible transactional applications. Default behavior is proposed in order to display back-end data, iterate through tables, for conditional displays and front-end error reporting.

Also, the XML and HTML/CSS output to be deployed on your applicative server is completely standard and can easily be integrated with your .Net, ASP, JSP or EJB code.

And there are several options available to integrate WebMS with your content management system.

Getting your applicative GUI out-of-the-box, and customizing it using WebMS is not only development-savvy. It also will make the difference at maintenance stage, where organisation and documentation are always critical.

Transaction scenarios are easily reconfigurable, be it to add a new use case, change a record's validation rules, show an extra warning or confirmation screen.

And finally, WebMS collaboration layers will guarantee that the marketing may edit the content and presentation layers without messing up your application code.

This allows a complete parallelisation of tasks between departments, which in turns entails better transversal collaboration and sensible savings on the bottom line.