This avoid random permission errors (like if another user run the
same test)

This is a followup to commit 8995b645
("always start transactions with begin() and make tic() commit automatically"):
there is now no need to use self.stepTic() instead of self.tic()

It is required use Security Category Mapping Configurator Item at the
consulting workflow, like it is done at Standard workflow.

The related tests were updated for check this change.

This Constraint do not work for packing lists because according to
the constraint the "lines" should be order movements and not delivery
movements. Update related Test.

Test were updated to check the change.

This Configurator Item configures the script ERP5Site_getSecurityCategoryMapping, This can be
combined with roles generations and categories spreadsheet in future to generate full security
definition.

Update configuration to use Security Category Mapping Configurator Item instead include the
script directly, otherwise it breaks the instance due the dependency with scripts on erp5_dms

Initial code is almost the same as the one provided by erp5_simulation_test
in order to preserver initial compatibility

Now Consulting Tests have similar behavior them Standard.
Also test simulation and secutity for others configurations
(France, Brazil and Russia)

The Rules are now used as template and not as it is anymore, the rules are
cloned and updated with appropriate categories defined by the configurator.

Business Process Configurator Item was reimplemented to use
spreadsheet to generate an Business Process.

 - Solvers were moved to erp5_configurator_standard_solver
 - trade related code and rules to  erp5_configurator_standard_trade_template
 - accounting related code and rules to  erp5_configurator_standard_accounting_template
 - invoicing related code and rules to  erp5_configurator_standard_invoicing_template

Code were moved and splited to several diferent business templates. The rules
and related code should be used only as template.

This script is required to generate the basic security of standard
configuration.

The Configurator Items should handle the state changes for each object. Previous approach make sense with the previous design.

Use Categories Spreadsheet to present the values for the user. Unify User creations form.

Move configurator after script from Business Template to Workflow. This will make management easier

Instead get Informations from the Business Configuration, get information directly from the Workflow Document. This easly creates a identity if the workflow and also simplify the process of Pré-configuration.

This file is a generic element.

Now title and Descrptions is used to present messages to the user.

Conflicts:

	bt5/erp5_configurator_standard/bt/revision

Conflicts:

	bt5/erp5_configurator_standard/bt/revision

Dropped last_id on XML

This Configurator Item was a Legacy which has no importance anymore, as
Business Template is not exported and installed on third party Instances
during the configuration.

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

* Added default image on default_standard_configuration and a better description.
* Added new business configuration for consulting workflow.

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