E-COMMERCE APPLICATION BUILT USING WORKFLOWS ON A WORKFLOW ENGINE AND METHODS THEREOF

An e-commerce or business application built using workflows for execution as a series of steps by a workflow (or interpreter) engine. The steps might be arranged as a coded series of steps (i.e., a flowchart or the like). A page (or series of pages) is provided, each of which has content and actions. An interactive flow layer is also provided for facilitating the transition from one screen (or workflow) to another. An associated view layer is used to implement the series of steps within the screen. The view might implement at least one interactive step, which takes data incoming into the step and renders the data into a viewable language, such as HTML. This layer is known as the presentation layer. An address, name of the action, and sequence number are associated with each such interactive step. The elements displayed by the browser can be clicked upon and the address returned so that the steps can be navigated through without losing track of the sequence steps. At least one state variable, global or otherwise, is used to maintain persistence of certain data between the steps. As each of the steps is executed, the sequence number is incremented. If a user tries to move around in the sequence, the sequence number should match the one that is stored in server memory in order for a display to be valid. Actions can further be labeled as repeatable, non-repeatable, or conditional repeatable. Non-repeatable actions require the sequence numbers to match. Repeatable actions do not depend on the sequence numbers. Conditional repeatable actions are repeatable under certain conditions. L'invention concerne une application de commerce ou d'affaires électroniques construite au moyen d'un flux de travaux destinée à être exécutée en une série d'étapes par un moteur de flux de travaux (ou interpréteur). Les étapes peuvent être arrangées sous forme d'une série codée d'étapes (c'est-à-dire, un organigramme ou analogue). Ladite application comprend une page (ou une série de pages). Chacune des pages comprend un contenu et des actions. Ladite application comprend également une couche de flux interactive pour faciliter la transition entre un écran (ou flux de travaux) et un autre. Une couche de visualisation associée permet de mettre en oeuvre la série d'étape dans l'écran. La visualisation peut mettre en oeuvre au moins une étape interactive, qui prend les données entrantes dans l'étape et les transforme en un langage visualisable, tel que HTML. Cette couche est appelée couc