. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 2. General rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BIZ/OFBiz+Documentation+Team] for further information and how we are organised. 1 2. General rules 2.1. Document configuration Documents that will be published as standalone guides (e.g. developer limitations under the License. //// 2.3. File name conventions We will be implementing a consistent naming convention for the documentation content files. Filenames should be in lower case with the extension

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. General rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . / [5] https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Documentation+Team 2 2. General rules 2.1. Document configuration Documents that will be published as standalone guides (e.g. developer root asciidoc/images directory 2.4. File name conventions We will be implementing a consistent naming convention for the documentation content files. Filenames should be in lower case with the extension

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. General rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . / [5] https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Documentation+Team 2 2. General rules 2.1. Document configuration Documents that will be published as standalone guides (e.g. developer root asciidoc/images directory 2.4. File name conventions We will be implementing a consistent naming convention for the documentation content files. Filenames should be in lower case with the extension

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. General rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . / [5] https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Documentation+Team 2 2. General rules 2.1. Document configuration Documents that will be published as standalone guides (e.g. developer root asciidoc/images directory 2.4. File name conventions We will be implementing a consistent naming convention for the documentation content files. Filenames should be in lower case with the extension

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. General rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . / [5] https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Documentation+Team 2 2. General rules 2.1. Document configuration Documents that will be published as standalone guides (e.g. developer root asciidoc/images directory 2.4. File name conventions We will be implementing a consistent naming convention for the documentation content files. Filenames should be in lower case with the extension

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 5.2. Golden Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . than Scenario Test but the Goal is different For each type there are specifics constrains and Goals/rules. 1.1. Unit Test Goals Each test must test only one, functionality, clearly defined Each test should same test A test is linked to the base data and its test data associated, so, without specifics rules / actions it 20 will failed if it’s run a second time in same environment. It’s not a good thing

menu : if value = N "edit button" not appears Security rules • nothing at the screenlet level, only at the update service level (and component rules) 2.1.2. Contact Mechanism This screenlet displays the a purpose which will be used when creating Security rules • nothing at the screenlet level, only at the update service level (and component rules) 2 Technical remarks This portlet displays the Contact add screen. In this case Party roles list is contain only role which are in the group Security rules • PORTAL_ADMIN is needed to edit portlet attributes 2.1.4. User login list for a Party. This screenlet

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 6.6.1. Similar to Price Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 6.6.4. Rules tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 6.7. Price Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 5.6.1. Similar to Price Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 5.6.4. Rules tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 5.7. Price Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 5.6.1. Similar to Price Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 5.6.4. Rules tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 5.7. Price Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .