Uploaded image for project: 'OFBiz'
  1. OFBiz
  2. OFBIZ-12142

Creating a new Customer create a wrong record in CommunicationEvent

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: Trunk
    • Fix Version/s: 18.12.01
    • Component/s: framework/common, party
    • Labels:
      None

      Description

      Excerpts from this user ML thread: https://markmail.org/message/pf3d3qyjfucicbj7

      Reportedby Emad Radwan <eradwan1967@gmail.com>:

      While creating a new Customer a new related record is created in CommunicationEvent table

      Answered by Pritam Kute <pritam.kute@hotwaxsystems.com>:

      In OOTB flow, after creating a customer, the system calls sendCreatePartyEmailNotification service asynchronously. This service is called to send an email notification to the customer about account creation. This causes the creation of a record in CommunicationEvent table.
      I feel that sending email should be configurable but an initial cursory look at the codebase doesn't guarantee about it.
      Also, one thing to notice is that the CommunicationEvent created has a record with partyIdFrom as FrenchCustomer which is completely wrong as it should be a company party. The logic in createCommEventFromEmail (line no. 776) to find out "fromCm" is what causing this problem.

      Answered by myself:

      I think found the reason. In demo data 13 parties use <<infoString="ofbiztest@example.com">> as in
      <ContactMech contactMechId="FRA01" contactMechTypeId="EMAIL_ADDRESS" infoString="ofbiztest@example.com"/>
      I guess this one is loaded last. Rather
      <ContactMech contactMechId="Company" contactMechTypeId="EMAIL_ADDRESS" infoString="ofbiztest@example.com"/>
      which is the 1st one, should be loaded last.

       

        Attachments

          Activity

            People

            • Assignee:
              jleroux Jacques Le Roux
              Reporter:
              jleroux Jacques Le Roux
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: