ofbiz-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Taher Alkhateeb (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OFBIZ-6703) Cannot create more than one lead in the SFA component by same user
Date Fri, 30 Oct 2015 08:14:27 GMT

    [ https://issues.apache.org/jira/browse/OFBIZ-6703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14982101#comment-14982101

Taher Alkhateeb commented on OFBIZ-6703:

Hi Hans,

You are right, the revert is not necessary for releases 12.04 and 13.07, after investigating
this I found that below commit. This is now irritating me more. We are switching from minilang
to entity-auto without any thought to business rules embedded in the services! Why do we do

I think a cleaner solution is revert the logic on all the releases including trunk and instead
reintroduce the service implementation instead of entity auto. What do you think?

r1622161 | jleroux | 2014-09-03 06:55:32 +0300 (Wed, 03 Sep 2014) | 30 lines

A patch from  Nicolas Malin for "Convert Party entites CRUD service from simple to entity-auto"

I converted CRUD service to entity-auto for :

> Cannot create more than one lead in the SFA component by same user
> ------------------------------------------------------------------
>                 Key: OFBIZ-6703
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-6703
>             Project: OFBiz
>          Issue Type: Bug
>          Components: marketing
>    Affects Versions: Trunk
>            Reporter: Taher Alkhateeb
>            Assignee: Taher Alkhateeb
>             Fix For: Upcoming Branch
> Repeat steps:
> # go to SFA component and click on leads
> # click on create new
> # fill mandatory information and save
> # repeat the above steps again and observe failure
> The reason for the failure is that the implementation of the createLead service tries
to create a PartyRole of type OWNER every time a lead is created. So it works only the first

This message was sent by Atlassian JIRA

View raw message