Configure Test Method¶

Rule is a Predicate and if rule.test(simulation_movement) is True, the rule will be expanded inside the simulation movement.

Table of Contents

• Configure Test Method
• How it works
• Configure Trade Phase
• Related Articles

How it works¶

For root level applied rules (eg. Order Simulation Rule etc.), it can be blank because root level applied rule is decided by 'XXX_getRuleReference' type based method. (XXX it is inconsistent and may be unified in the future.)

After r32519 (2010-02-15), the hierarchy of simulation tree is modified.

• old simulation tree

AR (Order Rule)
+-SM (order:Sale Order Line, delivery:Sale Packing List Line)
  +-AR (Invoicing Rule)
    +-...

• new simulation tree

AR (Order Simulation Rule)
+-SM (delivery:Sale Order Line)    <-- NEW
  +-AR (Deliverying Simulation Rule)          <-- NEW
    +-SM (delivery:Sale Packing List Line)
      +-AR (Invoicing Rule)
        +-...

Please configure test method appropriately to support intended simulation hierarchy, i.e. test methods for old rules should support old simulation tree only, and test methods for new rules should support new simulation tree only.

Please also note that the implementation of new rules will be modified quite soon, and reconfiguration will be required according to coming modification.

Configure Trade Phase¶

To use BPM, you need to specify the trade phase. (to be written more)

Related Articles¶

• HowTo | Use DREAM
• Guidelines | A PROJECT MUST DO SOMETHING
• Guidelines | A Business Template Has Only One Field Library
• Guidelines | Code Snippet Uses Code Tag Wrapped In Pre Tag
• Guidelines | A Document Form Uses The form_view Page Template
• Guidelines | A Documentation Document Must Have Group And Classification Defined
• Guidelines | A Fast Input Must Use object_fast_input Action
• Guidelines | A Form Field Proxies From A Buiness Template Field
• Guidelines | A Link Between Internal Documents Uses A Relative Url
• Guidelines | A Non Anonymous JavaScript Method Must Be Declared Before Use
• Guidelines | A Proxy Field Never Links To An External Field Library
• Guidelines | A Python Class Is Defined Inside ERP5 Product Only
• Guidelines | A Screeshot Displays Full Screen Without Bars
• Guidelines | A Validation Workflow Must Have A Delete State And Action
• Guidelines | Abbreviation Link Title Must Contain Abbreviated Text And Description Split By Semicolon
• Guidelines | Abbreviations Are Not Allowed
• Guidelines | Abbreviations Are Not Allowed In ERP5 Code
• Guidelines | Add Column Portal Type If Listbox Contains Multiple Types
• Guidelines | Add Date In Listbox As Editable Date-Time Field
• Guidelines | Add Viewable Listbox Fields To More Columns
• Guidelines | Always Provide Portal Type Description
• Guidelines | Assign Properties To Zope Objects Only
• Guidelines | Attribute Must Be Assigned Only To Object Or Class
• Guidelines | Business Library Fields Proxy From Core Fields
• Guidelines | Business Reference Is An Uppercase Id And Number Sequence Separated By Hyphen
• Guidelines | JavaScript Class Name And Id Attribute Are Lowercase With Underscore Separator
• Guidelines | Code Must Be Validated With JsLint
• Guidelines | Commits Are Atomic
• Guidelines | Commits Are Purpose Based
• Guidelines | Configuration And Project Business Templates Must Include Roles For Group, Site And Function
• Guidelines | Define Declare Fast Input As Hidden Content Type
• Guidelines | Define Action Name Explicitly For Users
• Guidelines | Define And Translate Workflow Titles
• Guidelines | Define Count Method As countFolder On Module Listbox
• Guidelines | Define Document Actions As Global Actions
• Guidelines | Define Module Author And Auditor In Roles Tab Based On Use Cases
• Guidelines | Define Module Default Actions On Portal Action Tool
• Guidelines | Define Report Actions As object_report Linked With View Permission
• 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 | Dialog Form Name Is Postfixed With Dialog
• Guidelines | Do Not Add Any New Messages To User Interface
• Guidelines | Do Not Test Required In Field View Form
• Guidelines | Document Content Is Written In British English
• Guidelines | Document Content Is Written In HTML5
• Guidelines | Document Has Mandatory View And Optional Detais And History Tab
• Guidelines | Document Keywords Are Lowercase Singular And Line Separated
• Guidelines | Document Name Is Camel Case And Dot Separated
• Guidelines | Document Name Must Use Anchor, Reference, Name, Version, Language And File Type
• Guidelines | Document Theme Is Set Using Follow Up Software Product
• Guidelines | Document Title Uses Capitalized Keywords Prefixed By Publication Section
• Guidelines | Documentation Document Anchor Uses Software And Publication Section Split By Hyphen
• Guidelines | Documentation Document Is Classified Using Publication Section
• Guidelines | Documentation Document Must Have Introduction Paragraph
• Guidelines | Documentation Document Must Have Description Abstract
• Guidelines | Embedded SVG Image Must Have A Format Specified
• Guidelines | End A File With Empty Line
• Guidelines | Field Title Must Be Singular, Capitalized And Uses Space Separator
• Guidelines | Fix Whitespace In A Separate Commit
• Guidelines | Form Name Uses Lowercase View After Portal Type
• Guidelines | Form Report Dialog Is Postfixed With Report
• Guidelines | Forms Must Use Left, Right, Center, Bottom And Hidden Groups
• Guidelines | Generic Business Templates Must Have Security Roles Set On States And Transitions
• Guidelines | Group Reference Is Uppercase And Uses Category Value
• Guidelines | Headers Start At Level 1 And Are Not Numbered
• Guidelines | Hide Listbox Editable Fields On The Form
• Guidelines | Image Format Must Be SVG Or PNG
• Guidelines | Image Must Have Alt Attribute
• Guidelines | Image Must Have Alt Attribute For Automatic Captioning
• Guidelines | Image Must Have Format And Display Parameter In Url
• Guidelines | Image Should Not Be Wrapped By Hand For Fullsize Viewing
• Guidelines | Image Uses Publication Section As Anchor Reference
• Guidelines | In Document Name Publication Section Is Written In Camelcase
• Guidelines | Include Module Base Categories In Business Template
• Guidelines | Include Module Local Roles In Business Template
• Guidelines | Inline CSS And JavaScript Are Not Allowed
• Guidelines | Inside The Roles Tab, Assignor, Assignee, Associate And Auditor Must Be Defined
• Guidelines | Interface Name Uses Camelcase
• Guidelines | JavaScript Closing Bracket Is At Indent Of Function Call
• Guidelines | JavaScript Constructor Starts With Captial Letter
• Guidelines | JavaScript Opening Brace Is On Line Of Current Statement
• Guidelines | Language Is Abbreviated As Two Lowercase Characters
• Guidelines | Language Priority
• Guidelines | Link Explaining Abbreviation Is Wrapped in Square Bracket And Uses Abbreviation As Link Text
• Guidelines | Link Text On Applicable And Referenced Documents Is AD/RD
• Guidelines | Link To Applicable Or Referenced Document Uses Title And Is Wrapped In Square Brackets
• Guidelines | ListField Or MultListField For Categories Must Use Item List Method
• Guidelines | Listbox Method Is Named Using Module Type And Portal Type List
• Guidelines | Listbox Must Only Be Put In Form Bottom Group
• Guidelines | Listbox Selection Name Must Follow module_name_selection Pattern
• Guidelines | Listbox Selection Uses Name Selection Postfix
• Guidelines | Listbox Uses List, Stat Or Count Method
• Guidelines | Live Tests Should Not Be Run On Production
• Guidelines | Log Clear Enough To Disable Easily
• Guidelines | Logs Must Contain Their Cause
• Guidelines | Metadata Is Last Tab For Managers
• Guidelines | Method In Listbox Is Prefixed With Listbox Section
• Guidelines | Method Name Is Camelcase Starting With Lowercase Letter
• Guidelines | Method Name Is Prefixed With Portal Or Meta Type, Class Or Interface
• Guidelines | Method Name Uses Mixed Case And Begins With Verb
• Guidelines | Modify Correct Changelog On Business Template Commits
• Guidelines | Module Title Is Plural, Capitalized And Space Separated
• Guidelines | Never Hardcode If Not Necessary
• Guidelines | Only Site Wide Script Uses ERP5Site Prefix
• Guidelines | Only Use Proxy Fields In Non Field Library Forms
• Guidelines | Page Template Containing Multiple Macros Is Postfixed With Renderer
• Guidelines | Page Template Macro Id Is Lowercase
• Guidelines | Page Template Macro Variables Must Be Defined In Header
• Guidelines | Page Template Uses Method Naming Conventions
• Guidelines | Place Simulation And Validation Fields At Bottom Of Right Group
• Guidelines | Plural In ERP5 Is Written Using List And Count
• Guidelines | Plural Is Not Allowed
• Guidelines | Png Is Saved In Image And Svg In Web Page Module
• Guidelines | Private Method Starts With Underscore
• Guidelines | Project Reference Uses A Suffix And Character Sequence Separated By Hyphen
• Guidelines | Pseudo Constant Uses Uppercase In ERP5
• Guidelines | Publication Section In Document Name Is Separated By Hypen And Lowercase
• Guidelines | Python Script Method Name Be Prefixed With Portal Type
• Guidelines | Reference Anchor Uses Uppercase Group, Project, Publication Section Or Business
• Guidelines | Report Method Name Uses ReportSectionList Postfix
• Guidelines | Report Name Uses Portal Type Followed By View Report Name And Report
• Guidelines | Rule Uses Optional Root And Mandatory Simulation Rule Postfix
• Guidelines | Semantic Field Is Named Using My Prefix, Technical Context And Semantic Name
• Guidelines | Sentence Starts With Capital Letter And Finishes With Semi-Colon Or Full-Stop
• Guidelines | Sessions Are Not Allowed
• Guidelines | Set At Least View Action On Module Action Tab
• Guidelines | Set Content Permission To Fast Input
• Guidelines | Set Description On Form Fields
• Guidelines | Set Document Form Ids To PortalType_view
• Guidelines | Set Document Form Titles To What Is Displayed
• Guidelines | Set Form Action Base_doSelect On Forms
• Guidelines | Set Form Action To Base_edit
• Guidelines | Set Form Encytype to multipart/form-data When Using File Upload
• Guidelines | Set Form Id To ModulePortalType_viewPortalTypeList
• Guidelines | Set Form Title To What Is Displayed
• Guidelines | Set List Method To contentValues On Document Form Listbox
• Guidelines | Set Listbox Action To List Action On Document Form Listboxes
• Guidelines | Set Listbox Selection Name To form_name_selection_name
• Guidelines | Set Listbox Title To Plural Of Portal Type Title If Applicable
• Guidelines | Set Post Method And Utf-8 Encoding On Document Forms
• Guidelines | Set Priorities On Important Activities
• Guidelines | Short Title On Documentation Documents Uses Title Without Publication Section
• Guidelines | Split Large Forms On Multiple Tabs
• Guidelines | SQL Column Id Is Lowercase
• Guidelines | SQL Column Id Use Singular For Related Key
• Guidelines | SVG Image Must Have Format Specified In Url
• Guidelines | Tab Title Is Singular Capitalized And Space Separated
• Guidelines | Table Has Caption Defined After Tbody Tag
• Guidelines | Table Uses Thead Tbody And Caption Tags
• Guidelines | Technical Template Fields Are Defined In Base_viewFieldLibrary
• Guidelines | Test Changes Before Committing
• Guidelines | Text From The User Interface Is Written In Italic
• Guidelines | Tool Title Is Plural
• Guidelines | Use Base_view Prefix Followed By Business Filed and FieldLibrary For Field Library Title
• Guidelines | Use Correct Names For Simulation And Validation Titles
• Guidelines | Use form_list Page Template On Forms
• Guidelines | Use gender neutral writing in documentation
• Guidelines | Use getTranslatedId To Display Document Ids In Listbox Or Form
• Guidelines | Use Glossary Defined Prefix For Specific Semantics
• Guidelines | Use Localizer For Module Title Translation
• Guidelines | Use Log Levels
• Guidelines | Use Method Post And UTF-8 Encoding On Forms
• Guidelines | Use Methods To Access Properties In ERP5
• Guidelines | Use My Prefix and Class Name For Template Field Name
• Guidelines | Use Of JavaScript Id Attribute Is Not Allowed
• Guidelines | Use Only Allowed Html Tags
• Guidelines | Use Path Links For Linking To Images Or Assets
• Guidelines | Use Path Links For Links To Large Files
• Guidelines | Use Proxy Fields Of Proxy Fields In Form
• Guidelines | Use Translated Portal Type To Display Portal Type
• Guidelines | Use Two Space Indentation
• Guidelines | User Interface Module Title Is Singular, Separated By Space And Capitalized
• Guidelines | User Interface Must Use Uppercase Abbreviations
• Guidelines | Validator Method Is Prefixed With Validator
• Guidelines | Variable Name Is Lowercase Separated By Underscore
• Guidelines | Version Number Is Ascending And Use Three Digits
• 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 | Write Testable Code And Test Smart
• Guidelines | ZSQL Method Is Lowercase And Uses Z Prefix And Underscore Separator
• Guidelines | ZSQL Method Is Prefixed With Z In Portal Skin
• HowTo | Configure Movement Group
• HowTo | Configure Rule
• HowTo | Create Automatic Target Solvers
• HowTo | Create ERP5 Trade From Scratch
• HowTo | Create Target Solvers
• HowTo | Customize Price Lookup
• HowTo | Use and Define Order Builders
• HowTo | Use Delivery Causality Workflow
• HowTo | Use Product Variation
• Technical Note | Configure Simulation
• Technical Note | Merging Deliveries
• Technical Note | Movement Group
• Technical Note | Input Output API
• Technical Note | Open Order
• Technical Note | Payment Simulation
• Technical Note | Simulation Motos
• Technical Note | Solver Process
• Technical Note | Stable Expand
• Technical Note | Subscription Service
• Technical Note | Tax Lines
• Guidelines |
• Guidelines |
• Guidelines |
• Guidelines |
• Guidelines |
• Guidelines |