Changes between Version 21 and Version 22 of BluePrint/MultiStepForms


Ignore:
Timestamp:
05/04/13 23:26:58 (9 years ago)
Author:
hardik juneja
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/MultiStepForms

    v21 v22  
    7979* Generator should also adapt structural changes if the structure of the defined data changes.
    8080* Generator should provide full access control to the user, they can go back, skip steps and quit at any point.
     81* Wizards or Multi-Step forms should support decision(branches) Ex. they will ask user to choose from option A or option B to proceed further.
    8182* Multi-step forms or wizard should track the audit trails i.e keeping the record of the running processes as they unfold, so that users can come back to the same point where they left off.
    8283* Multi-step forms should have a simple and user-friendly user interface.
    8384* These Multi-step forms or wizards should be easily available and accessible to the user after successful login.
    84 * User should be given an option to allow All the steps to be displayed simultaneously on one page.
     85* User should be given an option to allow All the steps to be displayed simultaneously on one page.
     86* Wizards should support user role awareness.
    8587
    8688=== Non-functional ===
     
    99101* Data possibly will be a resource name along with fields list which makes up an activity.
    100102* These will be followed by control edges (Ex. whether node will be optional,required or not allowed).
     103* For each node developers will also define a pointer to the next node using a setter function as shown below.
    101104* Wizard generator will convert the given data into desired wizard template.
    102105
     
    107110{{{
    108111
    109 #General way to define a node is
    110 #node = S3SQLWizardForm("Table Name", "Description", **Fields Names)
    111 
    112 #defining first step
    113 node1 = S3SQLWizardForm("pr_person", "required", "first_name", "last_name", "gender", "date_of_birth")
    114 
    115 #defining second step
    116 node2 = S3SQLWizardForm("pr_person", "optional", "phone", "email")
    117 
    118 #These nodes will be then passed to another function which will then decide the flow of the wizard.
    119 #Example (Note - name of the function could be different ) -
     112# General way to define a node is
     113# node = S3SQLWizardForm("Table Name", Description, **Fields Names)
     114
     115# Defining first step
     116node1 = S3SQLWizardForm("pr_person", Required, "first_name", "last_name", "gender", "date_of_birth")
     117
     118# Defining second step
     119node2 = S3SQLWizardForm("pr_person", Optional, "phone", "email")
     120
     121
     122# Define flow of the Wizard by pointing each node to the next node
    120123 
    121 S3CreateWizard(node1, node2, node3,....)
     124node1.add_next(node2)   # node1 -> node2
     125
     126node2.add_next(node3, node4) # node2 -> (node3 or node4)
    122127
    123128}}}
    124129
    125 The other alternative of the data structure is discussed here - [[BR]]
    126 http://logs.sahanafoundation.org/sahana-eden/2013-04-30.txt
    127130
    128131==== As User ====