Access to add and change pages is restricted. See: https://cwiki.apache.org/confluence/display/OFBIZ/Wiki+access

  • Created by Unknown User (bjfree@free-man.net), last modified on Aug 09, 2008

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

  1. overview
    change the Postaladdress entity to support more address and direction lines
    refer to Extending+PostalAddress+Information
  2. scope
    work with the PostalAddress entity and associated entities.
    1. remove the fields toName and attnName and add them as ContactMech types that can relate to the Postaladdress entity
    2. add a one to many from PostalAddress to Address+line+entity
    3. add a one to many from postalAddress to Direction+Lines+Entity
  3. Justification
  • the current format only supports the US addressing mode
  • the ability to validate a address that never changes should be a one time thing to there should only be one address entry in the database.
  1. Considerations
    1. overview
      This is a major schema Change. so upgrade support is necessary for those with Live systems.
    2. Scope
      Using eca's provide two way updates.
      1. If the data is in the legacy format put in the new format
      2. if the data is in the new format put in the legacy format till the conversion process it complete.
  2. Upgrade process
    1. What will be effected
      • change PostalAddress from package-name="org.ofbiz.party.contact" to package-name="org.ofbiz.party.postal.
    1. how to change
  2. list
  • No labels