Annotations tend to break information sharing and, worse, workflow modeling.

Table of Contents

• Introduction
• Why not?
• Related Articles

Introduction¶

Many applications use annotation or are based on annotation:

• CMF proposes discussions on every document
• IMAP proposes a system to attach a persistent flag to every email
• KDE includes a notes feature (like postit)

Why not?¶

So, why not add annotation features to ERP5 ? Because it tends to break information sharing and, worse, workflow modeling:

• users will start to use personal annotations to track the status of a document
• this is like creating yet another workflow system in parallel with the existing one
• if annotations are private (per user), it is like adding some organisation system which becomes user dependent rather corporate wide and user independent

All this shows that the greatest care must be taken before adding annotations to ERP5 because annotations may lead to complete irrelevance of business workflows.

Related Articles¶

• Guidelines | A Validation Workflow Must Have A Delete State And Action
• Guidelines | Configuration And Project Business Templates Must Include Roles For Group, Site And Function
• Guidelines | Define And Translate Workflow Titles
• Guidelines | Define The Roles Allowed To Excecute A Transition
• Guidelines | Define Transition Title From A Business Point Of View
• Guidelines | Define Workflow Permission To Allow Redefinition On Workflow States
• Guidelines | Define Workflow Titles From A Business Point Of View
• Guidelines | Favor simulation_state Or validation_state For Workflow State
• Guidelines | First Level Portal Types Should Have A Validation Workflow
• Guidelines | Generic Business Templates Must Have Security Roles Set On States And Transitions
• Guidelines | Never Access State_change Object In ERP5 Workflow Scripts
• Guidelines | Never Forget Edit Workflow On Documents
• Guidelines | Never Hardcode Interactions
• Guidelines | Never Use DoActionFor In ERP5
• Guidelines | The Default Dialog Should Be Used For All Transitions
• Guidelines | Workflow State Is Single Adjective Or Verb
• Guidelines | Workflow Validation Scripts Must Be Well Defined
• Guidelines | Workflow Validation Scripts Must Return Translated Messages
• Guidelines | Workflows Should Define Worklists
• HowTo | Create Interactors
• HowTo | Use and Define Interaction Workflows
• HowTo | Use and Define Workflows
• HowTo | Use Transactional Variable
• Technical Note | Annotation And Workflow