[ https://issues.apache.org/jira/browse/OFBIZ-7098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Suraj Khurana updated OFBIZ-7098: --------------------------------- Description: 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. (was: 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.) > 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 > 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)