The acronim prefw is the reverse of wferp.

This is a work flow system with extensive business module components.

1. Work flow architecture

   • CRUD work flow containers
   • CRUD instance of work flow components
   • Insert and re-order components inside containers
   • Defines its own JSON-Schema that sustains the whole progress

2. Work flow components

   • Options interface should be built upon JSON-Schema and schema-form.
     ^{i.e. Input from what properties, output to what properties.}
   • Has data schema optionally derived from the container
   • Has its own form schema for interface purpose
   • Serves form schema for interface purpose

3. Functional Modules

   • Modules will serve as work flow components in the system
   • Modules should provide component schemas for interface
   • Modules inject hooks into component modification process (pre/post save/delete)
     ^{Note: Only do processing works, validations should be done by JSON-Schemas.}
   • Modules define components

4. User/Role

   • Each component instance
   • Support read-only access
   • Users automatically has read access to container when one of its component is accessible
   • Container modification is a separated permission
   • Once the previous parts are finished, module codes can be written in the interface.
     ^{Note: Requires write permission to the corresponding module}