[jira] Issue Comment Edited: (OFBIZ-100) Addressing Verification

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] Issue Comment Edited: (OFBIZ-100) Addressing Verification

Nicolas Malin (Jira)

    [ https://issues.apache.org/jira/browse/OFBIZ-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12544906 ]

bjfreeman edited comment on OFBIZ-100 at 11/22/07 5:57 PM:
------------------------------------------------------------

I am reviewing code and services that create the postal code.
I feel the first step to accomplish the Address verification is to get all code to call the createPostalAddress  and two new ones for updatePostalAddress and deletePostalAddress service.

the easiest refactor is :
createPartyPostalAddress
updatePartyPostalAddress

there maybe more but I will add them as I find them.

I would like to refactor these so they call
createPostalAddress
updatePostalAddress
deletePostalAddress


Unless someone has a suggestion will submit patch.



      was (Author: bjfreeman):
    I am reviewing code and services that create the postal code.
I feel the first step to accomplish the Address verification is to get all code to call the createPostalAddress service.

the easiest refactor is :
createPartyPostalAddress
updatePartyPostalAddress

there maybe more but I will add them as I find them.

I would like to refactor these so they call
createPostalAddress

Unless someone has a suggestion will submit patch.


 

> Addressing Verification
> -----------------------
>
>                 Key: OFBIZ-100
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-100
>             Project: OFBiz
>          Issue Type: New Feature
>          Components: party
>            Reporter: BJ Freeman
>            Priority: Minor
>         Attachments: PostalAddressServiceChange.xml, xAL.xsd
>
>
> When the POSTALADDRESS entity is created or updated it will go thru verification, if availible.
> I suggest  POSTALADDRESSVERIFICATION entity to handle the additional data, instead of modifying the POSTALADDRESS .
> POSTALADDRESS  would be modified to add the vericationprocessed and verified flag and ID to the POSTALADDRESSVERIFICATION entiy.
> The reason for the two flag is speed and if the verified flag is false, then further processing of the POSTALADDRESSVERIFICATION  can be done.
> POSTALADDRESSVERIFICATION  may have a range of address that are valid but do not match the address.
> if may have address1 matches but not the City or zip.
> the Address Element Correction (AEC) service would thn do its best to validate and/or correct the address.
> when the AEC is run it will create Task for the user  to fix manually, since AEC does not alway work.
> The Upper level Verification will see the Verified Flag false and create an event.
> For Ecommerce this would alert the buyer that there address is not deliverable and allow them to see the choices and correct thier address.
> For Orderentry it would allow the sales person to verify the address with the customer.
> For addresses that imported, via webtools, a service will run nightly to validate all address.
> I have included proposed service changes and new service as an example.
> this changes the Create and Update POSTALADDRESS in the
> applications/party/script/org/ofbiz/party/contact/ContactMechServices.xml

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.