|
[ https://issues.apache.org/jira/browse/OFBIZ-11183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Malin updated OFBIZ-11183: ---------------------------------- Description: Currently entity-auto manage a service who attendee a statusId on IN parameter and a oldStatusId on OUT parameter. {code:java} <service name="updateRequirement" default-entity-name="Requirement" engine="entity-auto" invoke="update" auth="true"> <description>Update an existing requirement</description> <auto-attributes include="pk" mode="IN" optional="false"/> <auto-attributes include="nonpk" mode="IN" optional="true"/> <attribute name="oldStatusId" type="String" mode="OUT" optional="true"/> </service> {code} I propose to extend this logic to itemSatusId {code:java} <service name="updatePicklistItem" default-entity-name="PicklistItem" engine="entity-auto" invoke="update" auth="true"> <description>Update PicklistItem</description> <permission-service service-name="facilityPermissionCheck" main-action="UPDATE"/> <auto-attributes include="pk" mode="IN" optional="false"/> <auto-attributes include="nonpk" mode="IN" optional="true"/> <attribute name="oldItemStatusId" type="String" mode="OUT" optional="true"/> </service>{code} was: Currently entity-auto manage a service who attendee a statusId on IN parameter and a oldStatusId on OUT parameter. {code:java} <service name="updateRequirement" default-entity-name="Requirement" engine="entity-auto" invoke="update" auth="true"> <description>Update an existing requirement</description> <auto-attributes include="pk" mode="IN" optional="false"/> <auto-attributes include="nonpk" mode="IN" optional="true"/> <attribute name="oldStatusId" type="String" mode="OUT" optional="true"/> </service> {code} I propose to extend this logic to itemSatusId {code:java} <service name="updatePicklistItem" default-entity-name="PicklistItem" engine="entity-auto" invoke="update" auth="true"> <description>Update PicklistItem</description> <permission-service service-name="facilityPermissionCheck" main-action="UPDATE"/> <auto-attributes include="pk" mode="IN" optional="false"/> <auto-attributes include="nonpk" mode="IN" optional="true"/> <attribute name="oldItemStatusId" type="String" mode="OUT" optional="true"/> </service>{code} > Manage itemStatusId and oldItemStatusId on entity-auto > ------------------------------------------------------ > > Key: OFBIZ-11183 > URL: https://issues.apache.org/jira/browse/OFBIZ-11183 > Project: OFBiz > Issue Type: Improvement > Components: framework > Affects Versions: Trunk > Reporter: Nicolas Malin > Priority: Minor > Attachments: OFBIZ-11183.patch > > > Currently entity-auto manage a service who attendee a statusId on IN parameter and a oldStatusId on OUT parameter. > {code:java} > <service name="updateRequirement" default-entity-name="Requirement" engine="entity-auto" invoke="update" auth="true"> > <description>Update an existing requirement</description> > <auto-attributes include="pk" mode="IN" optional="false"/> > <auto-attributes include="nonpk" mode="IN" optional="true"/> > <attribute name="oldStatusId" type="String" mode="OUT" optional="true"/> > </service> > {code} > I propose to extend this logic to itemSatusId > {code:java} > <service name="updatePicklistItem" default-entity-name="PicklistItem" engine="entity-auto" invoke="update" auth="true"> > <description>Update PicklistItem</description> > <permission-service service-name="facilityPermissionCheck" main-action="UPDATE"/> > <auto-attributes include="pk" mode="IN" optional="false"/> > <auto-attributes include="nonpk" mode="IN" optional="true"/> > <attribute name="oldItemStatusId" type="String" mode="OUT" optional="true"/> > </service>{code} -- This message was sent by Atlassian Jira (v8.3.2#803003) |
| Free forum by Nabble | Edit this page |
