This test no longer complain about the number of simulation movements inside the root applied rule when an init script defined on Sale Invoice Transaction Portal Type create some Sale Invoice Transaction Line, they will not be expanded unless site administrator creates a really strange invoice_transaction_rule predicate matrix.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@4008 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@3872 20353a03-c40f-0410-a6d1-a30d3c3de9de

 * invoice with cells
 * updateAppliedRule when adding/editing/removing/adding cells to an invoice line


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@3841 20353a03-c40f-0410-a6d1-a30d3c3de9de

rewrote for using Sequence class and increasing readability


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@3781 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@2482 20353a03-c40f-0410-a6d1-a30d3c3de9de

Predicate Groups inside the Invoice Transaction Rule must be indexed for the updateMatrix() function to work.
For this thest, we use immediate_reindex=1 when we create them, to be sure that they are here.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@2190 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@2095 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@2063 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@2053 20353a03-c40f-0410-a6d1-a30d3c3de9de

The logic is in, but maybe it should be spread in many little methods...


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@2046 20353a03-c40f-0410-a6d1-a30d3c3de9de