Changes between Version 2 and Version 3 of GoFlow_Doc


Ignore:
Timestamp:
May 23, 2008, 7:48:21 AM (17 years ago)
Author:
GoFlow administrator
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GoFlow_Doc

    v2 v3  
    88
    99== Prerequisite ==
    10 Create a directory, and copy the directory''goflow''in this directory (you can also place it in any directory PYTHONPATH).
     10Create a directory, and copy the directory ''goflow''in this directory (you can also place it in any directory PYTHONPATH).
    1111
    1212''Note'':
     
    2323}}}
    2424
    25   * Add the following applications in the file''settings.py''
     25  * Add the following applications in the file ''settings.py''
    2626{{{
    2727   INSTALLED_APPS = (
     
    3232   )
    3333}}}
    34    The application''workflow''contains the "static" model data (modeling
    35    process), and application''forums''contains the dynamic part, or runtime.
     34   The application ''workflow'' contains the "static" model data (modeling
     35   process), and application ''forums'' contains the dynamic part, or runtime.
    3636
    3737  * Setting up the party's database file settings, for example like this:
     
    4141}}}
    4242
    43   * Add the following lines 2 das''urls.py file'':
     43  * Add the following lines 2 in ''urls.py''  file:
    4444{{{
    4545   urlpatterns = patterns ('',
     
    5858}}}
    5959
    60 We can now open the console admin [http://localhost:8000/admin], and discover the data models introduced by! GoFlow:
    61    [[Image (GoFlow_DocFr:admin1.png)]]
     60We can now open the console admin [http://localhost:8000/admin], and discover the data models introduced by !GoFlow:
     61   [[Image(GoFlow_DocFr:admin1.png)]]
    6262
    63 we can also discover the Dashboard''!''GoFlow, which has the status of workflows using a "back-office", [http://localhost:8000/workflow]
    64    [[Image (GoFlow_DocFr:admin2.png)]]
     63we can also discover the ''!GoFlow'' Dashboard, which has the status of workflows using a "back-office", [http://localhost:8000/workflow]
     64   [[Image(GoFlow_DocFr:admin2.png)]]
    6565
    6666We will now create a process workflow.
    6767  * Return to the admin console, add an entity Process; screen below is shown:
    6868
    69    [[Image (GoFlow_DocFr:admin3.png)]]
     69   [[Image(GoFlow_DocFr:admin3.png)]]
    7070
    7171  * Take the title "Hello world", and a description
    72   * Register using the''Save button and continue editing'': there is an activity''End''was added automatically.
    73   * Create an initial activity, by clicking on the icon "+" in the field''Initial activity'': take a title, set the process on the current process "Hello world", leave the default values for other fields.
     72  * Register using the ''Save button and continue editing'': there is an activity ''End'' was added automatically.
     73  * Create an initial activity, by clicking on the icon "+" in the field ''Initial activity'': take a title, set the process on the current process "Hello world", leave the default values for other fields.
    7474  * Save
    7575We have to create our first process workflow:
    76    [[Image (GoFlow_DocFr:admin4.png)]]
     76   [[Image(GoFlow_DocFr:admin4.png)]]
    7777
    7878We have specified no application in our business, we will see that it is not necessary to begin to "play" with our application.
    7979
    80 Indeed, when an activity is not associated with an application, a special application is still invoked, to simulate this activity: a panel is simply presented to the user, displaying the name and description of activity . A history of workflow is also displayed. A''OK''button allows you to complete the activity.
     80Indeed, when an activity is not associated with an application, a special application is still invoked, to simulate this activity: a panel is simply presented to the user, displaying the name and description of activity . A history of workflow is also displayed. A ''OK'' button allows you to complete the activity.
    8181
    82 Before you start implementing our process workflow, it lacks one thing: allow the current user (''admin''for example) to instantiate the process.
     82Before you start implementing our process workflow, it lacks one thing: allow the current user (''admin'' for example) to instantiate the process.
    8383
    84   * Add a group named''''Hello world, give him permission''can_instantiate''on the content type''workflow.process'', and save
    85   * Add this group to the current user: this allows the user to instantiate the process''''Hello world.
     84  * Add a group named ''Hello world'', give him permission ''can_instantiate'' on the content type ''workflow.process'', and save
     85  * Add this group to the current user: this allows the user to instantiate the process ''Hello world''.
    8686
    8787Everything is now ready to execute our workflow: go on the dashboard [http://localhost:8000/workflow]. You will find our process and its definition, and other information on the roles and permissions
    8888
    89   * Click on the link''start a simulation instance''under the''process''Hello world
     89  * Click on the link ''start a simulation instance'' under the process ''Hello world''
    9090
    91 Bug''rev 21: name of process with a white''
     91''Bugrev 21: name of process with a white''
    9292
    9393----
    9494
    95 '' 'TO BE CONTINUED'''
     95'''TO BE CONTINUED'''
Back to Top