[
https://issues.apache.org/jira/browse/OFBIZ-7098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295950#comment-15295950 ]
Deepak Dixit commented on OFBIZ-7098:
-------------------------------------
I think yes, this scenario make sense to me if you want to use different status to manage party. As per current flow we are only using party.statusId for enable and disable purpose. We can add different status like created, hold etc. to manage parties.
> Remove restriction of setting PARTY_ENABLED as first default status of party
> ----------------------------------------------------------------------------
>
> Key: OFBIZ-7098
> URL:
https://issues.apache.org/jira/browse/OFBIZ-7098> Project: OFBiz
> Issue Type: Bug
> Components: party
> Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, Release Branch 15.12
> Reporter: Suraj Khurana
> Assignee: Mridul Pathak
> Fix For: 14.12.01, Upcoming Branch, 15.12.01, 13.07.04
>
> Attachments: OFBIZ-7098.patch
>
>
> I was creating a new Party through custom service and tried to set its initial status as "PARTY_DISABLED" using setPartyStatus service but it defaults set as PARTY_ENABLED. In setPartyStatus service of PartyServices.java, if oldStatusId is not found then party status is set to "PARTY_ENABLED" (which is not necessary for all scenarios), a user can also set "PARTY_DISABLED" as first default party status.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Locked
