[OFBIZ-6976] Updating data sets

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Won't Do
• Affects Version/s: Trunk
• Component/s: ALL COMPONENTS, ALL PLUGINS
• Labels: Demo configuration data test
• Assignee: Pierre Smits
• Reporter: Pierre Smits
• Created: 02/Apr/16 12:00
• Updated: 28/Mar/24 16:53
• Resolved: 10/Feb/21 12:03

Description

This is a placeholder issue.

Having correct data shipped with OFBiz is key to not only

1. have a good operational state (meaning adopters can work with OFBiz out of the box)
2. have a good data set for demonstration purposes
3. have a good data set to enable unit, system integration and acceptance testing

Re aspect 1:
This encompasses all security, system property and other seed data sets

Re aspect 2:
This encompasses all data records in the various DemoData.xml files. This kind of data needs to be coherent from the perspective of the main internal organisation (or the legal demo party) that operates the OFBiz implementation.

Re aspect 3:
The data set for this aspect encompasses all data under aspect 1 and 2.

With a good data set for demonstration purposes it is easier for potential adopters (and their influencers) to see the added value of implementing OFBiz in their company/organisation, while at the same time it helps developers to understand the coherence between widgets, templates, services, functions and other data counter parts. Also, good demo data helps contributors to identity issues regarding the usability of OFBiz, work to resolve them and ultimate improve OFBiz.

Demo data sets should be grouped in accordance to the component load order (as defined in e.g. component-load.xml, see links below). The first appearance of a data record of the demo kind should also (as much as possible) be in accordance with where the related entity is defined and where the first appearance of related seed data records are defined. For guidance see the entity reference (per link below)

Example 1:
The ProductStore entity is defined in the entity model for the Product component (the product-entitymodel.xml).

Thus any new demo record regarding this ProductStore entity should first appear in the ProductDemoData.xml file.

Example 2:
Following record is defined in WorkEffortTypeData.xml

<WorkEffortType description="Project" hasTable="N" workEffortTypeId="PROJECT"/>

Thus any first appearance of a demo record for the WorkEffort entity with the defined workEffortTypeId="PROJECT" should appear in the WorkEffortDemoData.xml file

With the above we minimise the risk of duplication and dependency mismatches

Issue Links

• is part of: OFBIZ-3500 Umbrella issue for components dependency
• is related to: OFBIZ-6110 Move as much as possible demo data from ecommerce to product or order components
• is related to: OFBIZ-4674 Human Resource Manager Tree
• is related to: OFBIZ-9237 order entry initial screen does not show productStore
• is related to: OFBIZ-9238 order entry initial screen. customer auto suggestion does not work
• is related to: OFBIZ-11699 Have improvements to data-sets go into demo-stable
• is related to: OFBIZ-5965 PartyRole Lifespan fields - Have PartyRole screens/forms work with the change
• is related to: OFBIZ-5959 Add lifespan fields to PartyRole
• is related to: OFBIZ-11713 Allow party selection only for appropriate request roles
• supercedes: OFBIZ-11017 In demo data many parties are incorrectly set with role 'INTERNAL_ORGANIZATIO'
• links to: Application components load order
• links to: Framework components load order
• links to: GitHub Pull Request #18
• links to: GitHub Pull Request #117
• links to: Github Pull Request #117
• links to: OFBiz Entity Reference