This is an automated email from the ASF dual-hosted git repository.

mridulpathak pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/ofbiz-framework.git


The following commit(s) were added to refs/heads/trunk by this push:
     new eaad9d260d Fixed: The phone extension entered when creating an SFA 
account or lead is silently dropped (OFBIZ-13657)
eaad9d260d is described below

commit eaad9d260d838383cb48e342b67514636c5f2d0d
Author: Mridul Pathak <[email protected]>
AuthorDate: Thu Oct 8 00:37:52 2026 +0530

    Fixed: The phone extension entered when creating an SFA account or lead is 
silently dropped (OFBIZ-13657)
    
    When createPartyGroupRoleAndContactMechs became a real service call, run 
service: started filtering its input to the declared attributes. The servicedef 
declared no extension, although the telecom map processor copies it and 
PartyContactMech stores it, so the number was saved without its extension and 
no error was raised. Declare extension as an optional IN attribute; 
createAccount and createLead both pass it through.
---
 applications/party/servicedef/services.xml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/applications/party/servicedef/services.xml 
b/applications/party/servicedef/services.xml
index 70a0362229..0417f15f8d 100644
--- a/applications/party/servicedef/services.xml
+++ b/applications/party/servicedef/services.xml
@@ -107,6 +107,7 @@ under the License.
         <attribute name="groupName" type="String" mode="IN" optional="false"/>
         <attribute name="address1" type="String" mode="IN" optional="true"/>
         <attribute name="contactNumber" type="String" mode="IN" 
optional="true"/>
+        <attribute name="extension" type="String" mode="IN" optional="true"/>
         <attribute name="emailAddress" type="String" mode="IN" 
optional="true"/>
         <attribute name="postalAddContactMechPurpTypeId" type="String" 
mode="IN" optional="true"/>
         <attribute name="phoneContactMechPurpTypeId" type="String" mode="IN" 
optional="true"/>

Reply via email to