[
https://issues.apache.org/jira/browse/OFBIZ-7970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15432325#comment-15432325 ]
Pierre Smits commented on OFBIZ-7970:
-------------------------------------
There is a logical sequence in setting up an ERP solution for a company (although there have been heated debates about this as this is dependent on industry sector, company size, etc. - the business requirements).
Ideally this sequence would be, with component names in brackets:
# setup the data structure (datamodel)
# setup the key internal parties + permissions (system, default company, default admin) as everything depends on this (party, securityext)
# setup supporting content (content)
# setup financial and accounting structure (accounting)
# setup payment management structure (accounting)
# setup facility and asset structure (facility, assetmaint)
# setup product structure (product)
# setup inventory management structure (facility)
# setup the order management structure for purchasing and sales (order)
# setup maintenance and manufacturing structure (workeffort, manufacturing) - optional
# setup additional organisation structure and additional permissions (humanres) - optional
# setup sales support structure (marketing, sfa) - optional
Unfortunately, there are many entanglements across components. And there are a few components having multiple applications encompassed.
That leads to a complex situation especially when it comes to loading demo data. And we have mingled setup demo data with transaction demo data.
As a result, we have created a major dependency on the ecommerce component to ensure that all data is loaded before test can be run.
In order to lessen the burden of ecommerce dependency, I have started to enhance the demo data sets of various components. As it is demo data, the aspect of duplicates are of minor importance.
Bringing the sequence of component loading more in line with the aforementioned list will bring structure to the implementation process, but it will also reveal the dependencies of the base components (in the reverse order of the list).
> Reorder the component loading in the application stack
> ------------------------------------------------------
>
> Key: OFBIZ-7970
> URL:
https://issues.apache.org/jira/browse/OFBIZ-7970> Project: OFBiz
> Issue Type: Improvement
> Components: ALL APPLICATIONS
> Affects Versions: Trunk
> Reporter: Pierre Smits
> Assignee: Pierre Smits
> Attachments: OFBIZ-7970-component-load.xml-v2.patch, OFBIZ-7970-component-load.xml.patch
>
>
> While working on the demo data in the ecommerce component, I noticed that the order of components in the application stack are not ordered correctly.
> This is related to OFBIZ-7016
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Locked
