1   Data structures

• portal_stack_registry which is referencing the existing stacks to be used.

• Data Structure registry to register new stacks within the portal_stack_registry.

• The data structures used for the stack by default

  • BaseStack class
  • SimpleStack class
  • HierarchicalStack class

  It's extensible with the portal_stack_registry tool for integration.

  Possible to specify rulez about ds management in here :

  • canManage()
  • listLocalRolesMapping()

2   Stack Definitions

• Holds a given stack configuration.
  • properties (common + specific)
• Holds a data structure instance.

Default Stack Definition Type

• BaseWorkflowStackDefinition
• SimpleWorkflowStackDefinition
• HierarchicalWorkflowStackDefinition
• potal_stack_registry (cf. above)
• Stack Definition registry to register new stack definition

Extensible, with the portal_stack_registry tool for integration.

Possible to add more information on these objects.

3   State information

• State information related to stacks
  • flags on the states
    • push behavior
    • pop behavion
• State definition holds stack definition declaration.

4   Transition information

• Transition information related to stacks

  • transition flags
    • push on variables
    • pop on variables
    • returned up hierarchy on variables
    • workflow up on variables
    • workflow down on variables

  N.B.: variable above is a global workflow variable holding a stack definition instance.

5   CPSWorkflow

• CPSWorkflow related

  • _executeTransitions()

    cope transition flags for stacks

  • _checkTransitionGuard()

    Hook for delegatees and local roles check.

  • updateRoleMapping()

6   CPSWorkflowTool

• getStackDefinitionsFor(self, ob)
• getDataStructureStacks(self, ob)
• getDataStructureStackFor(self, ob, wf_var_id)

7   CPSWorkflowExpression

• CPSWorkflowExpression extended DC WF expr

  [? Check if I really need it ?]

8   Status

• The stack data structure is stored within the workflow status, not on the Stack definition.