[jira] [Assigned] (OFBIZ-12025) Unable to add address while selecting option split shipment
[ https://issues.apache.org/jira/browse/OFBIZ-12025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar reassigned OFBIZ-12025: --- Assignee: Chinmay Patidar > Unable to add address while selecting option split shipment > --- > > Key: OFBIZ-12025 > URL: https://issues.apache.org/jira/browse/OFBIZ-12025 > Project: OFBiz > Issue Type: Bug >Affects Versions: 17.12.04 >Reporter: Rashi Dhagat >Assignee: Chinmay Patidar >Priority: Major > Attachments: NewAddress-SplitShipmenterror.png, > SplitShipmentError.webm > > > Steps to regenerate: > 1. Add multiple items in the cart > 2. Click on View cart > 3. Click on checkout > 4. Click on Split shipment option > 5. Click on Add new address > Actual: Error renders while trying to add the address or selecting the > existing address. > Please refer to the attachment. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11898) Create new Find Security Group screen
[ https://issues.apache.org/jira/browse/OFBIZ-11898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-11898: Attachment: OFBIZ-11898.patch > Create new Find Security Group screen > -- > > Key: OFBIZ-11898 > URL: https://issues.apache.org/jira/browse/OFBIZ-11898 > Project: OFBiz > Issue Type: Improvement > Components: framework/webtools >Affects Versions: Trunk >Reporter: Pawan Verma >Priority: Minor > Attachments: OFBIZ-11898.patch > > > Implement new Find Security Group screen under > webtools/control/FindSecurityGroup to facilitate webtools users to find > appropriate security group with search parameters. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11898) Create new Find Security Group screen
[ https://issues.apache.org/jira/browse/OFBIZ-11898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-11898: Attachment: (was: OFBIZ-11898) > Create new Find Security Group screen > -- > > Key: OFBIZ-11898 > URL: https://issues.apache.org/jira/browse/OFBIZ-11898 > Project: OFBiz > Issue Type: Improvement > Components: framework/webtools >Affects Versions: Trunk >Reporter: Pawan Verma >Priority: Minor > > Implement new Find Security Group screen under > webtools/control/FindSecurityGroup to facilitate webtools users to find > appropriate security group with search parameters. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11898) Create new Find Security Group screen
[ https://issues.apache.org/jira/browse/OFBIZ-11898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17202599#comment-17202599 ] Chinmay Patidar commented on OFBIZ-11898: - Provided patch containing the support with which the user would be able to search/filter the Security Groups list. Thanks [~pawan] for reporting the issue. > Create new Find Security Group screen > -- > > Key: OFBIZ-11898 > URL: https://issues.apache.org/jira/browse/OFBIZ-11898 > Project: OFBiz > Issue Type: Improvement > Components: framework/webtools >Affects Versions: Trunk >Reporter: Pawan Verma >Assignee: Chinmay Patidar >Priority: Minor > Attachments: OFBIZ-11898 > > > Implement new Find Security Group screen under > webtools/control/FindSecurityGroup to facilitate webtools users to find > appropriate security group with search parameters. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (OFBIZ-11898) Create new Find Security Group screen
[ https://issues.apache.org/jira/browse/OFBIZ-11898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar reassigned OFBIZ-11898: --- Assignee: (was: Chinmay Patidar) > Create new Find Security Group screen > -- > > Key: OFBIZ-11898 > URL: https://issues.apache.org/jira/browse/OFBIZ-11898 > Project: OFBiz > Issue Type: Improvement > Components: framework/webtools >Affects Versions: Trunk >Reporter: Pawan Verma >Priority: Minor > Attachments: OFBIZ-11898 > > > Implement new Find Security Group screen under > webtools/control/FindSecurityGroup to facilitate webtools users to find > appropriate security group with search parameters. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11898) Create new Find Security Group screen
[ https://issues.apache.org/jira/browse/OFBIZ-11898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-11898: Attachment: OFBIZ-11898 > Create new Find Security Group screen > -- > > Key: OFBIZ-11898 > URL: https://issues.apache.org/jira/browse/OFBIZ-11898 > Project: OFBiz > Issue Type: Improvement > Components: framework/webtools >Affects Versions: Trunk >Reporter: Pawan Verma >Assignee: Chinmay Patidar >Priority: Minor > Attachments: OFBIZ-11898 > > > Implement new Find Security Group screen under > webtools/control/FindSecurityGroup to facilitate webtools users to find > appropriate security group with search parameters. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (OFBIZ-11898) Create new Find Security Group screen
[ https://issues.apache.org/jira/browse/OFBIZ-11898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar reassigned OFBIZ-11898: --- Assignee: Chinmay Patidar > Create new Find Security Group screen > -- > > Key: OFBIZ-11898 > URL: https://issues.apache.org/jira/browse/OFBIZ-11898 > Project: OFBiz > Issue Type: Improvement > Components: framework/webtools >Affects Versions: Trunk >Reporter: Pawan Verma >Assignee: Chinmay Patidar >Priority: Minor > > Implement new Find Security Group screen under > webtools/control/FindSecurityGroup to facilitate webtools users to find > appropriate security group with search parameters. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-8014) Introduce the "Product" Screen under Party app to manage the products supplied by any supplier
[ https://issues.apache.org/jira/browse/OFBIZ-8014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17103239#comment-17103239 ] Chinmay Patidar commented on OFBIZ-8014: Hi [~pawan]. Thanks for the improvements. I have verified the new changes and improvements at my end and they look good to me. > Introduce the "Product" Screen under Party app to manage the products > supplied by any supplier > -- > > Key: OFBIZ-8014 > URL: https://issues.apache.org/jira/browse/OFBIZ-8014 > Project: OFBiz > Issue Type: New Feature > Components: party >Affects Versions: Release Branch 14.12, 16.11.01, Release Branch 15.12 >Reporter: Swapnil Shah >Assignee: Pawan Verma >Priority: Major > Attachments: OFBIZ-8014.patch, OFBIZ-8014.patch, SupplierProduct.png > > > Currently, upon logging into the Party application (or login as supplier > itself) and go to any specific supplier view then there is no way to manage > the list of supplied products. > # We can try introducing the "Product" tab/screen along with other tabs. (to > begin with we can simply mimic the Supplier screen from Catalog app e.g., > https://ofbiz-vm.apache.org:8443/catalog/control/EditProductSuppliers?productId=MAT_A_COST) > > # We can also choose to show the "Products" tab for only Parties in supplier > role and later can try to extend for other roles with further needed > refinements. > Please refer to attached screenshot for the same. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-10951) Add code level support to honor the compatibility between the opted products during configurable order workflow
[ https://issues.apache.org/jira/browse/OFBIZ-10951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-10951: Description: Have the ability to set and honor the compatibility between opted product during configurable goods ordering There is already an entity "ProductConfigOptionIactn" in place for defining the compatibility between the config options. Need to add code level support to honor the compatibility rule defined in that entity. The below is a detailed description of the items which will be covered in this task. dObjective: To implement the service level support to establish compatibility between configurable product options. Purpose: To provide support for compatibility between the config options by making use of the existing entity 'ProductConfigOptionIactn'. Implementation Design: The various methods would be implemented in the Product Config Wrapper class to enable creation/deletion of the compatibility, to add/remove the config items from the compatibility. This implementation can also handle incompatibility between config options depending on how we setup the data in the 'ProductConfigOptionIactn' entity. was: Have the ability to set and honor the compatibility between opted product during configurable goods ordering There is already an entity "ProductConfigOptionIactn" in place for defining the compatibility between the config options. Need to add code level support to honor the compatibility rule defined in that entity. The below is a detailed description of the items which will be covered in this task. Objective: To implement the service level support to establish compatibility between configurable product options. Purpose: To provide support for compatibility between the config options by making use of the existing entity 'ProductConfigOptionIactn'. Implementation Design: The various methods would be implemented in the Product Config Wrapper class to enable creation/deletion of the compatibility, to add/remove the config items from the compatibility. This implementation can also handle incompatibility between config options depending on how we setup the data in the 'ProductConfigOptionIactn' entity. > Add code level support to honor the compatibility between the opted products > during configurable order workflow > --- > > Key: OFBIZ-10951 > URL: https://issues.apache.org/jira/browse/OFBIZ-10951 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: Trunk >Reporter: Pritam Kute >Assignee: Chinmay Patidar >Priority: Major > > Have the ability to set and honor the compatibility between opted product > during configurable goods ordering > There is already an entity "ProductConfigOptionIactn" in place for defining > the compatibility between the config options. Need to add code level support > to honor the compatibility rule defined in that entity. > The below is a detailed description of the items which will be covered in > this task. > dObjective: > To implement the service level support to establish compatibility between > configurable product options. > Purpose: > To provide support for compatibility between the config options by making > use of the existing entity 'ProductConfigOptionIactn'. > Implementation Design: > The various methods would be implemented in the Product Config Wrapper class > to enable creation/deletion of the compatibility, to add/remove the config > items from the compatibility. This implementation can also handle > incompatibility between config options depending on how we setup the data in > the 'ProductConfigOptionIactn' entity. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (OFBIZ-10796) Check run payment(A/P) transactions not getting available for reconciliation
[ https://issues.apache.org/jira/browse/OFBIZ-10796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16870174#comment-16870174 ] Chinmay Patidar commented on OFBIZ-10796: - Yes, it can be true that check run transaction is not a financial transaction. But I think we agree that each transaction must go through a reconciliation process. The problem being here is that such transactions are not getting available for reconciliation just because of the status in which they are being created. And the resolution provided is addressing the same. > Check run payment(A/P) transactions not getting available for reconciliation > > > Key: OFBIZ-10796 > URL: https://issues.apache.org/jira/browse/OFBIZ-10796 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk, 17.12.01, 16.11.05, 18.12.01 >Reporter: Chinmay Patidar >Assignee: Chinmay Patidar >Priority: Major > Attachments: OFBIZ-10796.patch > > > Check run payment group transactions don't get available for Financial > Account reconciliation. Though the financial account balance gets updated > during the A/P check run process, the system must allow the user with an > additional step of reconciling the transactions. > Steps to regenerate: > # Create a Check Run type payment group by issuing checks for an invoice/ > the invoices from the following screen: > [https://demo-trunk.ofbiz.apache.org/ap/control/FindPurchaseInvoices] > # (Additional Note)The balance of the financial account gets updated as soon > as the payment group is created. > # Visit to the "Find Transaction" screen of the company from which the check > run was created. > # Set 'Gl Reconciliation ID' field to value 'Not Assigned' and find the > transaction. The newly created Financial account transaction won't be > available to assign to a reconciliation. > The cause of this is that the financial account transaction doesn't get > created in the 'Created' status and has an 'Approved' status. An approved > status financial transaction directly updates the financial account balance > and thus don't appear in the list of the transactions to be reconciled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-8014) Introduce the "Product" Screen under Party app to manage the products supplied by any supplier
[ https://issues.apache.org/jira/browse/OFBIZ-8014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16870094#comment-16870094 ] Chinmay Patidar commented on OFBIZ-8014: Thanks [~pierresmits] for pointing out the unncesary check. I have removed the patch previously provided and have added the updated patch. > Introduce the "Product" Screen under Party app to manage the products > supplied by any supplier > -- > > Key: OFBIZ-8014 > URL: https://issues.apache.org/jira/browse/OFBIZ-8014 > Project: OFBiz > Issue Type: New Feature > Components: party >Affects Versions: Release Branch 14.12, 16.11.01, Release Branch 15.12 >Reporter: Swapnil Shah >Assignee: Chinmay Patidar >Priority: Major > Attachments: OFBIZ-8014.patch, SupplierProduct.png > > > Currently, upon logging into the Party application (or login as supplier > itself) and go to any specific supplier view then there is no way to manage > the list of supplied products. > # We can try introducing the "Product" tab/screen along with other tabs. (to > begin with we can simply mimic the Supplier screen from Catalog app e.g., > https://ofbiz-vm.apache.org:8443/catalog/control/EditProductSuppliers?productId=MAT_A_COST) > > # We can also choose to show the "Products" tab for only Parties in supplier > role and later can try to extend for other roles with further needed > refinements. > Please refer to attached screenshot for the same. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-8014) Introduce the "Product" Screen under Party app to manage the products supplied by any supplier
[ https://issues.apache.org/jira/browse/OFBIZ-8014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8014: --- Attachment: (was: SupplierProducts.patch) > Introduce the "Product" Screen under Party app to manage the products > supplied by any supplier > -- > > Key: OFBIZ-8014 > URL: https://issues.apache.org/jira/browse/OFBIZ-8014 > Project: OFBiz > Issue Type: New Feature > Components: party >Affects Versions: Release Branch 14.12, 16.11.01, Release Branch 15.12 >Reporter: Swapnil Shah >Assignee: Chinmay Patidar >Priority: Major > Attachments: OFBIZ-8014.patch, SupplierProduct.png > > > Currently, upon logging into the Party application (or login as supplier > itself) and go to any specific supplier view then there is no way to manage > the list of supplied products. > # We can try introducing the "Product" tab/screen along with other tabs. (to > begin with we can simply mimic the Supplier screen from Catalog app e.g., > https://ofbiz-vm.apache.org:8443/catalog/control/EditProductSuppliers?productId=MAT_A_COST) > > # We can also choose to show the "Products" tab for only Parties in supplier > role and later can try to extend for other roles with further needed > refinements. > Please refer to attached screenshot for the same. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-8014) Introduce the "Product" Screen under Party app to manage the products supplied by any supplier
[ https://issues.apache.org/jira/browse/OFBIZ-8014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8014: --- Attachment: OFBIZ-8014.patch > Introduce the "Product" Screen under Party app to manage the products > supplied by any supplier > -- > > Key: OFBIZ-8014 > URL: https://issues.apache.org/jira/browse/OFBIZ-8014 > Project: OFBiz > Issue Type: New Feature > Components: party >Affects Versions: Release Branch 14.12, 16.11.01, Release Branch 15.12 >Reporter: Swapnil Shah >Assignee: Chinmay Patidar >Priority: Major > Attachments: OFBIZ-8014.patch, SupplierProduct.png > > > Currently, upon logging into the Party application (or login as supplier > itself) and go to any specific supplier view then there is no way to manage > the list of supplied products. > # We can try introducing the "Product" tab/screen along with other tabs. (to > begin with we can simply mimic the Supplier screen from Catalog app e.g., > https://ofbiz-vm.apache.org:8443/catalog/control/EditProductSuppliers?productId=MAT_A_COST) > > # We can also choose to show the "Products" tab for only Parties in supplier > role and later can try to extend for other roles with further needed > refinements. > Please refer to attached screenshot for the same. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10951) Add code level support to honor the compatibility between the opted products during configurable order workflow
[ https://issues.apache.org/jira/browse/OFBIZ-10951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar reassigned OFBIZ-10951: --- Assignee: Chinmay Patidar > Add code level support to honor the compatibility between the opted products > during configurable order workflow > --- > > Key: OFBIZ-10951 > URL: https://issues.apache.org/jira/browse/OFBIZ-10951 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: Trunk >Reporter: Pritam Kute >Assignee: Chinmay Patidar >Priority: Major > > Have the ability to set and honor the compatibility between opted product > during configurable goods ordering > There is already an entity "ProductConfigOptionIactn" in place for defining > the compatibility between the config options. Need to add code level support > to honor the compatibility rule defined in that entity. > The below is a detailed description of the items which will be covered in > this task. > Objective: > To implement the service level support to establish compatibility between > configurable product options. > Purpose: > To provide support for compatibility between the config options by making use > of the existing entity 'ProductConfigOptionIactn'. > Implementation Design: > The various methods would be implemented in the Product Config Wrapper class > to enable creation/deletion of the compatibility, to add/remove the config > items from the compatibility. This implementation can also handle > incompatibility between config options depending on how we setup the data in > the 'ProductConfigOptionIactn' entity. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10951) Add code level support to honor the compatibility between the opted products during configurable order workflow
[ https://issues.apache.org/jira/browse/OFBIZ-10951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-10951: Description: Have the ability to set and honor the compatibility between opted product during configurable goods ordering There is already an entity "ProductConfigOptionIactn" in place for defining the compatibility between the config options. Need to add code level support to honor the compatibility rule defined in that entity. The below is a detailed description of the items which will be covered in this task. Objective: To implement the service level support to establish compatibility between configurable product options. Purpose: To provide support for compatibility between the config options by making use of the existing entity 'ProductConfigOptionIactn'. Implementation Design: The various methods would be implemented in the Product Config Wrapper class to enable creation/deletion of the compatibility, to add/remove the config items from the compatibility. This implementation can also handle incompatibility between config options depending on how we setup the data in the 'ProductConfigOptionIactn' entity. was: Have the ability to set and honor the compatibility between opted product during configurable goods ordering There is already an entity "ProductConfigOptionIactn" in place for defining the compatibility between the config options. Need to add code level support to honor the compatibility rule defined in that entity. > Add code level support to honor the compatibility between the opted products > during configurable order workflow > --- > > Key: OFBIZ-10951 > URL: https://issues.apache.org/jira/browse/OFBIZ-10951 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: Trunk >Reporter: Pritam Kute >Priority: Major > > Have the ability to set and honor the compatibility between opted product > during configurable goods ordering > There is already an entity "ProductConfigOptionIactn" in place for defining > the compatibility between the config options. Need to add code level support > to honor the compatibility rule defined in that entity. > The below is a detailed description of the items which will be covered in > this task. > Objective: > To implement the service level support to establish compatibility between > configurable product options. > Purpose: > To provide support for compatibility between the config options by making use > of the existing entity 'ProductConfigOptionIactn'. > Implementation Design: > The various methods would be implemented in the Product Config Wrapper class > to enable creation/deletion of the compatibility, to add/remove the config > items from the compatibility. This implementation can also handle > incompatibility between config options depending on how we setup the data in > the 'ProductConfigOptionIactn' entity. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10856) Customer Party getting set as 'organizationPartyId' in one the Account transaction for Customer Invoice
[ https://issues.apache.org/jira/browse/OFBIZ-10856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16805648#comment-16805648 ] Chinmay Patidar commented on OFBIZ-10856: - Provided the patch with the resolution. The problem was due to the wrong use of the variables from which the value was getting assigned. Additionally, I would like to bring the attention towards the record which gets created in this affected area of code. Even if the tax amount is zero we do create the record. Is it a required behavior? > Customer Party getting set as 'organizationPartyId' in one the Account > transaction for Customer Invoice > --- > > Key: OFBIZ-10856 > URL: https://issues.apache.org/jira/browse/OFBIZ-10856 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Release Branch 14.12, Trunk, 17.12.01, Release Branch > 16.11, Release Branch 18.12 >Reporter: Chinmay Patidar >Assignee: Chinmay Patidar >Priority: Critical > Attachments: OFBIZ-10856.patch > > > During the research over some of the unposted transactions, it was found that > the customer party Id is getting set as organization party Id for one of the > transactions belonging to a customer return invoice. > Steps to regenerate: > Simply create a return and receive it so as to eventually generate the return > invoice. Inspect the return invoice's transaction. One of the transaction > would be containing the customer party Id as the organization party Id. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10856) Customer Party getting set as 'organizationPartyId' in one the Account transaction for Customer Invoice
[ https://issues.apache.org/jira/browse/OFBIZ-10856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-10856: Attachment: OFBIZ-10856.patch > Customer Party getting set as 'organizationPartyId' in one the Account > transaction for Customer Invoice > --- > > Key: OFBIZ-10856 > URL: https://issues.apache.org/jira/browse/OFBIZ-10856 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Release Branch 14.12, Trunk, 17.12.01, Release Branch > 16.11, Release Branch 18.12 >Reporter: Chinmay Patidar >Assignee: Chinmay Patidar >Priority: Critical > Attachments: OFBIZ-10856.patch > > > During the research over some of the unposted transactions, it was found that > the customer party Id is getting set as organization party Id for one of the > transactions belonging to a customer return invoice. > Steps to regenerate: > Simply create a return and receive it so as to eventually generate the return > invoice. Inspect the return invoice's transaction. One of the transaction > would be containing the customer party Id as the organization party Id. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10856) Customer Party getting set as 'organizationPartyId' in one the Account transaction for Customer Invoice
Chinmay Patidar created OFBIZ-10856: --- Summary: Customer Party getting set as 'organizationPartyId' in one the Account transaction for Customer Invoice Key: OFBIZ-10856 URL: https://issues.apache.org/jira/browse/OFBIZ-10856 Project: OFBiz Issue Type: Bug Components: accounting Affects Versions: Release Branch 16.11, Trunk, Release Branch 14.12, 17.12.01, Release Branch 18.12 Reporter: Chinmay Patidar Assignee: Chinmay Patidar During the research over some of the unposted transactions, it was found that the customer party Id is getting set as organization party Id for one of the transactions belonging to a customer return invoice. Steps to regenerate: Simply create a return and receive it so as to eventually generate the return invoice. Inspect the return invoice's transaction. One of the transaction would be containing the customer party Id as the organization party Id. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10796) Check run payment(A/P) transactions not getting available for reconciliation
[ https://issues.apache.org/jira/browse/OFBIZ-10796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741170#comment-16741170 ] Chinmay Patidar commented on OFBIZ-10796: - Provided the patch with the resolution. As the existing comment suggested, we need to pass the status to the service so that the financial account transaction gets created in a 'Created' status. If it's not passed, then service creates it in Approved status and hence the financial account balance gets updated. > Check run payment(A/P) transactions not getting available for reconciliation > > > Key: OFBIZ-10796 > URL: https://issues.apache.org/jira/browse/OFBIZ-10796 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk, 17.12.01, 16.11.05, 18.12.01 >Reporter: Chinmay Patidar >Assignee: Chinmay Patidar >Priority: Major > Attachments: OFBIZ-10796.patch > > > Check run payment group transactions don't get available for Financial > Account reconciliation. Though the financial account balance gets updated > during the A/P check run process, the system must allow the user with an > additional step of reconciling the transactions. > Steps to regenerate: > # Create a Check Run type payment group by issuing checks for an invoice/ > the invoices from the following screen: > [https://demo-trunk.ofbiz.apache.org/ap/control/FindPurchaseInvoices] > # (Additional Note)The balance of the financial account gets updated as soon > as the payment group is created. > # Visit to the "Find Transaction" screen of the company from which the check > run was created. > # Set 'Gl Reconciliation ID' field to value 'Not Assigned' and find the > transaction. The newly created Financial account transaction won't be > available to assign to a reconciliation. > The cause of this is that the financial account transaction doesn't get > created in the 'Created' status and has an 'Approved' status. An approved > status financial transaction directly updates the financial account balance > and thus don't appear in the list of the transactions to be reconciled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10796) Check run payment(A/P) transactions not getting available for reconciliation
[ https://issues.apache.org/jira/browse/OFBIZ-10796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-10796: Attachment: OFBIZ-10796.patch > Check run payment(A/P) transactions not getting available for reconciliation > > > Key: OFBIZ-10796 > URL: https://issues.apache.org/jira/browse/OFBIZ-10796 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk, 17.12.01, 16.11.05, 18.12.01 >Reporter: Chinmay Patidar >Assignee: Chinmay Patidar >Priority: Major > Attachments: OFBIZ-10796.patch > > > Check run payment group transactions don't get available for Financial > Account reconciliation. Though the financial account balance gets updated > during the A/P check run process, the system must allow the user with an > additional step of reconciling the transactions. > Steps to regenerate: > # Create a Check Run type payment group by issuing checks for an invoice/ > the invoices from the following screen: > [https://demo-trunk.ofbiz.apache.org/ap/control/FindPurchaseInvoices] > # (Additional Note)The balance of the financial account gets updated as soon > as the payment group is created. > # Visit to the "Find Transaction" screen of the company from which the check > run was created. > # Set 'Gl Reconciliation ID' field to value 'Not Assigned' and find the > transaction. The newly created Financial account transaction won't be > available to assign to a reconciliation. > The cause of this is that the financial account transaction doesn't get > created in the 'Created' status and has an 'Approved' status. An approved > status financial transaction directly updates the financial account balance > and thus don't appear in the list of the transactions to be reconciled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10796) Check run payment(A/P) transactions not getting available for reconciliation
[ https://issues.apache.org/jira/browse/OFBIZ-10796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-10796: Description: Check run payment group transactions don't get available for Financial Account reconciliation. Though the financial account balance gets updated during the A/P check run process, the system must allow the user with an additional step of reconciling the transactions. Steps to regenerate: # Create a Check Run type payment group by issuing checks for an invoice/ the invoices from the following screen: [https://demo-trunk.ofbiz.apache.org/ap/control/FindPurchaseInvoices] # (Additional Note)The balance of the financial account gets updated as soon as the payment group is created. # Visit to the "Find Transaction" screen of the company from which the check run was created. # Set 'Gl Reconciliation ID' field to value 'Not Assigned' and find the transaction. The newly created Financial account transaction won't be available to assign to a reconciliation. The cause of this is that the financial account transaction doesn't get created in the 'Created' status and has an 'Approved' status. An approved status financial transaction directly updates the financial account balance and thus don't appear in the list of the transactions to be reconciled. was: Check run payment group transactions don't get available for Financial Account reconciliation. Though the financial account balance gets updated during the A/P check run process, the system must allow the user with an additional step of reconciling the transactions. Steps to regenerate: # Create a Check Run type payment group by issuing checks for an invoice/ the invoices from the following screen: [https://demo-trunk.ofbiz.apache.org/ap/control/FindPurchaseInvoices|[http://example.com].|http://example.com]./] # (Additional Note)The balance of the financial account gets updated as soon as the payment group is created. # Visit to the "Find Transaction" screen of the company from which the check run was created. # Set 'Gl Reconciliation ID' field to value 'Not Assigned' and find the transaction. The newly created Financial account transaction won't be available to assign to a reconciliation. The cause of this is that the financial account transaction doesn't get created in the 'Created' status and has an 'Approved' status. An approved status financial transaction directly updates the financial account balance and thus don't appear in the list of the transactions to be reconciled. > Check run payment(A/P) transactions not getting available for reconciliation > > > Key: OFBIZ-10796 > URL: https://issues.apache.org/jira/browse/OFBIZ-10796 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk, 17.12.01, 16.11.05, 18.12.01 >Reporter: Chinmay Patidar >Assignee: Chinmay Patidar >Priority: Major > > Check run payment group transactions don't get available for Financial > Account reconciliation. Though the financial account balance gets updated > during the A/P check run process, the system must allow the user with an > additional step of reconciling the transactions. > Steps to regenerate: > # Create a Check Run type payment group by issuing checks for an invoice/ > the invoices from the following screen: > [https://demo-trunk.ofbiz.apache.org/ap/control/FindPurchaseInvoices] > # (Additional Note)The balance of the financial account gets updated as soon > as the payment group is created. > # Visit to the "Find Transaction" screen of the company from which the check > run was created. > # Set 'Gl Reconciliation ID' field to value 'Not Assigned' and find the > transaction. The newly created Financial account transaction won't be > available to assign to a reconciliation. > The cause of this is that the financial account transaction doesn't get > created in the 'Created' status and has an 'Approved' status. An approved > status financial transaction directly updates the financial account balance > and thus don't appear in the list of the transactions to be reconciled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10796) Check run payment(A/P) transactions not getting available for reconciliation
[ https://issues.apache.org/jira/browse/OFBIZ-10796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-10796: Affects Version/s: (was: 16.11.04) (was: Release Branch 16.11) (was: Release Branch 15.12) (was: Release Branch 14.12) (was: Release Branch 13.07) 18.12.01 17.12.01 > Check run payment(A/P) transactions not getting available for reconciliation > > > Key: OFBIZ-10796 > URL: https://issues.apache.org/jira/browse/OFBIZ-10796 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk, 17.12.01, 16.11.05, 18.12.01 >Reporter: Chinmay Patidar >Assignee: Chinmay Patidar >Priority: Major > > Check run payment group transactions don't get available for Financial > Account reconciliation. Though the financial account balance gets updated > during the A/P check run process, the system must allow the user with an > additional step of reconciling the transactions. > Steps to regenerate: > # Create a Check Run type payment group by issuing checks for an invoice/ > the invoices from the following screen: > [https://demo-trunk.ofbiz.apache.org/ap/control/FindPurchaseInvoices|[http://example.com].|http://example.com]./] > # (Additional Note)The balance of the financial account gets updated as soon > as the payment group is created. > # Visit to the "Find Transaction" screen of the company from which the check > run was created. > # Set 'Gl Reconciliation ID' field to value 'Not Assigned' and find the > transaction. The newly created Financial account transaction won't be > available to assign to a reconciliation. > The cause of this is that the financial account transaction doesn't get > created in the 'Created' status and has an 'Approved' status. An approved > status financial transaction directly updates the financial account balance > and thus don't appear in the list of the transactions to be reconciled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10796) Check run payment(A/P) transactions not getting available for reconciliation
Chinmay Patidar created OFBIZ-10796: --- Summary: Check run payment(A/P) transactions not getting available for reconciliation Key: OFBIZ-10796 URL: https://issues.apache.org/jira/browse/OFBIZ-10796 Project: OFBiz Issue Type: Improvement Components: accounting Affects Versions: 16.11.05, 16.11.04, Release Branch 16.11, Release Branch 15.12, Trunk, Release Branch 14.12, Release Branch 13.07 Reporter: Chinmay Patidar Assignee: Chinmay Patidar Check run payment group transactions don't get available for Financial Account reconciliation. Though the financial account balance gets updated during the A/P check run process, the system must allow the user with an additional step of reconciling the transactions. Steps to regenerate: # Create a Check Run type payment group by issuing checks for an invoice/ the invoices from the following screen: [https://demo-trunk.ofbiz.apache.org/ap/control/FindPurchaseInvoices|[http://example.com].|http://example.com]./] # (Additional Note)The balance of the financial account gets updated as soon as the payment group is created. # Visit to the "Find Transaction" screen of the company from which the check run was created. # Set 'Gl Reconciliation ID' field to value 'Not Assigned' and find the transaction. The newly created Financial account transaction won't be available to assign to a reconciliation. The cause of this is that the financial account transaction doesn't get created in the 'Created' status and has an 'Approved' status. An approved status financial transaction directly updates the financial account balance and thus don't appear in the list of the transactions to be reconciled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-8014) Introduce the "Product" Screen under Party app to manage the products supplied by any supplier
[ https://issues.apache.org/jira/browse/OFBIZ-8014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697780#comment-16697780 ] Chinmay Patidar commented on OFBIZ-8014: Provided patch containing the implementation. This feature has been implemented in the party component and the menu item would be visible for the parties having 'SUPPLIER' role. Currently, it doesn't entertain any kind of permission checks. Thanks [~rohit.koushal] for the various discussions and [~swash78] for the detailed explanation. > Introduce the "Product" Screen under Party app to manage the products > supplied by any supplier > -- > > Key: OFBIZ-8014 > URL: https://issues.apache.org/jira/browse/OFBIZ-8014 > Project: OFBiz > Issue Type: New Feature >Affects Versions: Release Branch 14.12, 16.11.01, Release Branch 15.12 >Reporter: Swapnil Shah >Assignee: Chinmay Patidar >Priority: Major > Attachments: SupplierProduct.png, SupplierProducts.patch > > > Currently, upon logging into the Party application (or login as supplier > itself) and go to any specific supplier view then there is no way to manage > the list of supplied products. > # We can try introducing the "Product" tab/screen along with other tabs. (to > begin with we can simply mimic the Supplier screen from Catalog app e.g., > https://ofbiz-vm.apache.org:8443/catalog/control/EditProductSuppliers?productId=MAT_A_COST) > > # We can also choose to show the "Products" tab for only Parties in supplier > role and later can try to extend for other roles with further needed > refinements. > Please refer to attached screenshot for the same. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-8014) Introduce the "Product" Screen under Party app to manage the products supplied by any supplier
[ https://issues.apache.org/jira/browse/OFBIZ-8014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8014: --- Attachment: SupplierProducts.patch > Introduce the "Product" Screen under Party app to manage the products > supplied by any supplier > -- > > Key: OFBIZ-8014 > URL: https://issues.apache.org/jira/browse/OFBIZ-8014 > Project: OFBiz > Issue Type: New Feature >Affects Versions: Release Branch 14.12, 16.11.01, Release Branch 15.12 >Reporter: Swapnil Shah >Assignee: Chinmay Patidar >Priority: Major > Attachments: SupplierProduct.png, SupplierProducts.patch > > > Currently, upon logging into the Party application (or login as supplier > itself) and go to any specific supplier view then there is no way to manage > the list of supplied products. > # We can try introducing the "Product" tab/screen along with other tabs. (to > begin with we can simply mimic the Supplier screen from Catalog app e.g., > https://ofbiz-vm.apache.org:8443/catalog/control/EditProductSuppliers?productId=MAT_A_COST) > > # We can also choose to show the "Products" tab for only Parties in supplier > role and later can try to extend for other roles with further needed > refinements. > Please refer to attached screenshot for the same. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-8014) Introduce the "Product" Screen under Party app to manage the products supplied by any supplier
[ https://issues.apache.org/jira/browse/OFBIZ-8014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar reassigned OFBIZ-8014: -- Assignee: Chinmay Patidar (was: Rohit Koushal) > Introduce the "Product" Screen under Party app to manage the products > supplied by any supplier > -- > > Key: OFBIZ-8014 > URL: https://issues.apache.org/jira/browse/OFBIZ-8014 > Project: OFBiz > Issue Type: New Feature >Affects Versions: Release Branch 14.12, 16.11.01, Release Branch 15.12 >Reporter: Swapnil Shah >Assignee: Chinmay Patidar >Priority: Major > Attachments: SupplierProduct.png > > > Currently, upon logging into the Party application (or login as supplier > itself) and go to any specific supplier view then there is no way to manage > the list of supplied products. > # We can try introducing the "Product" tab/screen along with other tabs. (to > begin with we can simply mimic the Supplier screen from Catalog app e.g., > https://ofbiz-vm.apache.org:8443/catalog/control/EditProductSuppliers?productId=MAT_A_COST) > > # We can also choose to show the "Products" tab for only Parties in supplier > role and later can try to extend for other roles with further needed > refinements. > Please refer to attached screenshot for the same. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-9763) Create separate Permission Services for CRUD services of ShoppingList and ShoppingListItem
[ https://issues.apache.org/jira/browse/OFBIZ-9763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-9763: --- Attachment: OFBIZ-9763.patch Updated the patch with an occurrence which was left out. i.e. replace the method call to 'checkShoppingListItemSecurity' with service call as it's converted into a service. > Create separate Permission Services for CRUD services of ShoppingList and > ShoppingListItem > -- > > Key: OFBIZ-9763 > URL: https://issues.apache.org/jira/browse/OFBIZ-9763 > Project: OFBiz > Issue Type: Improvement > Components: ecommerce, party >Affects Versions: Trunk, Release Branch 16.11 >Reporter: Chinmay Patidar >Assignee: Arun Patidar > Fix For: Trunk > > Attachments: OFBIZ-9763.patch, OFBIZ-9763.patch > > > In CRUD services for ShoppingList and ShoppingListItem entities, the security > related checks are present inline in the services. This implementation > violates the best practice of keeping security implementation different from > the business logic. > We need to implement security services for such operations and to call them > as a permission-service from the CRUD operation services definition -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OFBIZ-9764) UI error on Shopping Lists screen
[ https://issues.apache.org/jira/browse/OFBIZ-9764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar closed OFBIZ-9764. -- Resolution: Duplicate The same issue has been reported in OFBIZ-9764. Thus closing this. > UI error on Shopping Lists screen > - > > Key: OFBIZ-9764 > URL: https://issues.apache.org/jira/browse/OFBIZ-9764 > Project: OFBiz > Issue Type: Improvement > Components: ecommerce >Affects Versions: Trunk >Reporter: Chinmay Patidar >Assignee: Chinmay Patidar > Fix For: Trunk > > > Shopping Lists screen on ecommerce is not rendering. Getting following error - > 'Found string literal: "DAILY". Expecting: number'. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-9764) UI error on Shopping Lists screen
Chinmay Patidar created OFBIZ-9764: -- Summary: UI error on Shopping Lists screen Key: OFBIZ-9764 URL: https://issues.apache.org/jira/browse/OFBIZ-9764 Project: OFBiz Issue Type: Improvement Components: ecommerce Affects Versions: Trunk Reporter: Chinmay Patidar Assignee: Chinmay Patidar Fix For: Trunk Shopping Lists screen on ecommerce is not rendering. Getting following error - 'Found string literal: "DAILY". Expecting: number'. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-9763) Create separate Permission Services for CRUD services of ShoppingList and ShoppingListItem
Chinmay Patidar created OFBIZ-9763: -- Summary: Create separate Permission Services for CRUD services of ShoppingList and ShoppingListItem Key: OFBIZ-9763 URL: https://issues.apache.org/jira/browse/OFBIZ-9763 Project: OFBiz Issue Type: Improvement Components: ecommerce, party Affects Versions: Release Branch 16.11, Trunk Reporter: Chinmay Patidar Assignee: Chinmay Patidar Fix For: Trunk In CRUD services for ShoppingList and ShoppingListItem entities, the security related checks are present inline in the services. This implementation violates the best practice of keeping security implementation different from the business logic. We need to implement security services for such operations and to call them as a permission-service from the CRUD operation services definition -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-8454) Improvements in ShipmentGatewayConfig entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8454: --- Attachment: OFBIZ-8454.patch Added the patch with update service implemented using entity-auto for ShipmentGatewayConfig and ShipmentGatewayConfigType. Thanks [~arunpati] for pointing the enhancement. Also verified the patch using the service engine. > Improvements in ShipmentGatewayConfig entity definition and services > > > Key: OFBIZ-8454 > URL: https://issues.apache.org/jira/browse/OFBIZ-8454 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Amit Gadaley >Assignee: Chinmay Patidar >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-8454.patch, OFBIZ-8454.patch > > > Required improvements; > - All is good with entity definition. > - Add CRUD services using entity-auto (only create and delete). Make sure PK > is optional while create service, so that can be generated from OFBiz > sequence generator. > - Do related changes if any occurrence found for direct create/delete of this > entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (OFBIZ-8454) Improvements in ShipmentGatewayConfig entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar reopened OFBIZ-8454: Assignee: Chinmay Patidar (was: Arun Patidar) Reopening the issue as update service has not been implemented using entity-auto. > Improvements in ShipmentGatewayConfig entity definition and services > > > Key: OFBIZ-8454 > URL: https://issues.apache.org/jira/browse/OFBIZ-8454 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Amit Gadaley >Assignee: Chinmay Patidar >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-8454.patch > > > Required improvements; > - All is good with entity definition. > - Add CRUD services using entity-auto (only create and delete). Make sure PK > is optional while create service, so that can be generated from OFBiz > sequence generator. > - Do related changes if any occurrence found for direct create/delete of this > entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8775) Improvements in StatusValidChange entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8775: --- Assignee: (was: Chinmay Patidar) > Improvements in StatusValidChange entity definition and services > > > Key: OFBIZ-8775 > URL: https://issues.apache.org/jira/browse/OFBIZ-8775 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Affects Versions: Trunk >Reporter: Rishi Solanki >Priority: Minor > > Required improvements; > - All is good with entity definition . > - Add crud services using entity-auto. Make sure PK is not optional while > create service. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8728) Improvements in ProdCatalogInvFacility entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8728: --- Attachment: OFBIZ-8728.patch Added the patch for the improvement. Thanks [~rishisolankii] for the detailed description. Also verified the resolution using the service engine. > Improvements in ProdCatalogInvFacility entity definition and services > - > > Key: OFBIZ-8728 > URL: https://issues.apache.org/jira/browse/OFBIZ-8728 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Rishi Solanki >Assignee: Chinmay Patidar >Priority: Minor > Attachments: OFBIZ-8728.patch > > > Required improvements; > - All is good with entity definition . > - Add crud services using entity-auto. Make sure PK is not optional while > create service. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As from date/thru date exists in entity, so use expire action in the delete > service and service name should be 'expireEntityName'. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8728) Improvements in ProdCatalogInvFacility entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8728: --- Description: Required improvements; - All is good with entity definition . - Add crud services using entity-auto. Make sure PK is not optional while create service. - Do related changes if any occurrence found for direct create/update/delete of this entity, and replace them with crud services implemented. - As from date/thru date exists in entity, so use expire action in the delete service and service name should be 'expireEntityName'. was: Required improvements; - All is good with entity definition . - Add crud services using entity-auto. Make sure PK is not optional while create service. - Do related changes if any occurrence found for direct create/update/delete of this entity, and replace them with crud services implemented. - As no status/from date/thru date exists in entity, so nothing needs to be taken care while deleting the records from service. > Improvements in ProdCatalogInvFacility entity definition and services > - > > Key: OFBIZ-8728 > URL: https://issues.apache.org/jira/browse/OFBIZ-8728 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Rishi Solanki >Assignee: Chinmay Patidar >Priority: Minor > > Required improvements; > - All is good with entity definition . > - Add crud services using entity-auto. Make sure PK is not optional while > create service. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As from date/thru date exists in entity, so use expire action in the delete > service and service name should be 'expireEntityName'. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (OFBIZ-8440) Improvements in SequenceValueItem entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8440: --- Comment: was deleted (was: Added the patch for the improvement. Thanks [~rishisolankii] for the detailed description. Also verified the resolution using the service engine.) > Improvements in SequenceValueItem entity definition and services > > > Key: OFBIZ-8440 > URL: https://issues.apache.org/jira/browse/OFBIZ-8440 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Reporter: Amit Gadaley >Assignee: Chinmay Patidar >Priority: Minor > Attachments: OFBIZ-8440.patch > > > Required improvements; > - All is good with entity definition. > - Add CRUD services using entity-auto. Make sure PK is optional while create > service, so that can be generated from OFBiz sequence generator. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8440) Improvements in SequenceValueItem entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8440: --- Attachment: OFBIZ-8440.patch Added the patch for the improvement. Thanks [~rishisolankii] for the detailed description. Also verified the resolution using the service engine. > Improvements in SequenceValueItem entity definition and services > > > Key: OFBIZ-8440 > URL: https://issues.apache.org/jira/browse/OFBIZ-8440 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Reporter: Amit Gadaley >Assignee: Chinmay Patidar >Priority: Minor > Attachments: OFBIZ-8440.patch > > > Required improvements; > - All is good with entity definition. > - Add CRUD services using entity-auto. Make sure PK is optional while create > service, so that can be generated from OFBiz sequence generator. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8774) Improvements in StatusType entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8774: --- Attachment: OFBIZ-8774.patch Added the patch for the improvement. Thanks [~rishisolankii] for the detailed description. Also verified the resolution using the service engine. > Improvements in StatusType entity definition and services > - > > Key: OFBIZ-8774 > URL: https://issues.apache.org/jira/browse/OFBIZ-8774 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Affects Versions: Trunk >Reporter: Rishi Solanki >Assignee: Chinmay Patidar >Priority: Minor > Attachments: OFBIZ-8774.patch > > > Required improvements; > - All is good with entity definition. > - Add CRUD services using entity-auto. Make sure PK is optional while create > service, so that can be generated from OFBiz sequence generator. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-8775) Improvements in StatusValidChange entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar reassigned OFBIZ-8775: -- Assignee: Chinmay Patidar > Improvements in StatusValidChange entity definition and services > > > Key: OFBIZ-8775 > URL: https://issues.apache.org/jira/browse/OFBIZ-8775 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Affects Versions: Trunk >Reporter: Rishi Solanki >Assignee: Chinmay Patidar >Priority: Minor > > Required improvements; > - All is good with entity definition . > - Add crud services using entity-auto. Make sure PK is not optional while > create service. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-8774) Improvements in StatusType entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar reassigned OFBIZ-8774: -- Assignee: Chinmay Patidar > Improvements in StatusType entity definition and services > - > > Key: OFBIZ-8774 > URL: https://issues.apache.org/jira/browse/OFBIZ-8774 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Affects Versions: Trunk >Reporter: Rishi Solanki >Assignee: Chinmay Patidar >Priority: Minor > > Required improvements; > - All is good with entity definition. > - Add CRUD services using entity-auto. Make sure PK is optional while create > service, so that can be generated from OFBiz sequence generator. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8772) Improvements in ProductType entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8772: --- Attachment: OFBIZ-8772.patch Added the patch for the improvement. Thanks [~rishisolankii] for the detailed description. Also verified the resolution using the service engine. > Improvements in ProductType entity definition and services > -- > > Key: OFBIZ-8772 > URL: https://issues.apache.org/jira/browse/OFBIZ-8772 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Rishi Solanki >Assignee: Chinmay Patidar >Priority: Minor > Attachments: OFBIZ-8772.patch > > > Required improvements; > - All is good with entity definition. > - Add CRUD services using entity-auto. Make sure PK is optional while create > service, so that can be generated from OFBiz sequence generator. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8771) Improvements in ProductStoreGroupType entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8771: --- Attachment: OFBIZ-8771.patch Added the patch to fix this issue. Thanks [~rishisolankii] for the detailed description. Also verified the resolution using the entity engine. > Improvements in ProductStoreGroupType entity definition and services > > > Key: OFBIZ-8771 > URL: https://issues.apache.org/jira/browse/OFBIZ-8771 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Rishi Solanki >Assignee: Chinmay Patidar >Priority: Minor > Attachments: OFBIZ-8771.patch > > > Required improvements; > - All is good with entity definition. > - Add CRUD services using entity-auto. Make sure PK is optional while create > service, so that can be generated from OFBiz sequence generator. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-8773) Improvements in ProductTypeAttr entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar reassigned OFBIZ-8773: -- Assignee: Chinmay Patidar > Improvements in ProductTypeAttr entity definition and services > -- > > Key: OFBIZ-8773 > URL: https://issues.apache.org/jira/browse/OFBIZ-8773 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Rishi Solanki >Assignee: Chinmay Patidar >Priority: Minor > > Required improvements; > - All is good with entity definition . > - Add crud services using entity-auto. Make sure PK is not optional while > create service. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8770) Improvements in ProductStoreGroupRollup entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8770: --- Attachment: OFBIZ-8770.patch Added the patch to fix this issue. Thanks [~rishisolankii] for the detailed description. Also verified the resolution using the entity engine. > Improvements in ProductStoreGroupRollup entity definition and services > -- > > Key: OFBIZ-8770 > URL: https://issues.apache.org/jira/browse/OFBIZ-8770 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Rishi Solanki >Assignee: Chinmay Patidar >Priority: Minor > Attachments: OFBIZ-8770.patch > > > Required improvements; > - All is good with entity definition . > - Add crud services using entity-auto. Only need to add delete service as > create and update services already exists. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As from date/thru date exists in entity, so use expire action while > deleting the records and service name should be expireEntityName. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-8771) Improvements in ProductStoreGroupType entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar reassigned OFBIZ-8771: -- Assignee: Chinmay Patidar > Improvements in ProductStoreGroupType entity definition and services > > > Key: OFBIZ-8771 > URL: https://issues.apache.org/jira/browse/OFBIZ-8771 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Rishi Solanki >Assignee: Chinmay Patidar >Priority: Minor > > Required improvements; > - All is good with entity definition. > - Add CRUD services using entity-auto. Make sure PK is optional while create > service, so that can be generated from OFBiz sequence generator. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8769) Improvements in ProductStoreGroupRole entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8769: --- Attachment: OFBIZ-8769.patch Added the patch to fix this issue. Thanks [~rishisolankii] for the detailed description. Also verified the resolution using the entity engine. > Improvements in ProductStoreGroupRole entity definition and services > > > Key: OFBIZ-8769 > URL: https://issues.apache.org/jira/browse/OFBIZ-8769 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Rishi Solanki >Assignee: Chinmay Patidar >Priority: Minor > Attachments: OFBIZ-8769.patch > > > Required improvements; > - All is good with entity definition . > - Add crud services using entity-auto. Make sure PK is not optional while > create service. Update service is not required for this entity. > - Do related changes if any occurrence found for direct create/delete of this > entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-8770) Improvements in ProductStoreGroupRollup entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar reassigned OFBIZ-8770: -- Assignee: Chinmay Patidar > Improvements in ProductStoreGroupRollup entity definition and services > -- > > Key: OFBIZ-8770 > URL: https://issues.apache.org/jira/browse/OFBIZ-8770 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Rishi Solanki >Assignee: Chinmay Patidar >Priority: Minor > > Required improvements; > - All is good with entity definition . > - Add crud services using entity-auto. Only need to add delete service as > create and update services already exists. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As from date/thru date exists in entity, so use expire action while > deleting the records and service name should be expireEntityName. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8768) Improvements in ProductPriceType entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8768: --- Attachment: OFBIZ-8768.patch Added the patch to fix this issue. Thanks [~rishisolankii] for the detailed description. Also verified the resolution using the entity engine. > Improvements in ProductPriceType entity definition and services > --- > > Key: OFBIZ-8768 > URL: https://issues.apache.org/jira/browse/OFBIZ-8768 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Rishi Solanki >Assignee: Chinmay Patidar >Priority: Minor > Attachments: OFBIZ-8768.patch > > > Required improvements; > - All is good with entity definition. > - Add CRUD services using entity-auto. Make sure PK is optional while create > service, so that can be generated from OFBiz sequence generator. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-8769) Improvements in ProductStoreGroupRole entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar reassigned OFBIZ-8769: -- Assignee: Chinmay Patidar > Improvements in ProductStoreGroupRole entity definition and services > > > Key: OFBIZ-8769 > URL: https://issues.apache.org/jira/browse/OFBIZ-8769 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Rishi Solanki >Assignee: Chinmay Patidar >Priority: Minor > > Required improvements; > - All is good with entity definition . > - Add crud services using entity-auto. Make sure PK is not optional while > create service. Update service is not required for this entity. > - Do related changes if any occurrence found for direct create/delete of this > entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-8768) Improvements in ProductPriceType entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar reassigned OFBIZ-8768: -- Assignee: Chinmay Patidar > Improvements in ProductPriceType entity definition and services > --- > > Key: OFBIZ-8768 > URL: https://issues.apache.org/jira/browse/OFBIZ-8768 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Rishi Solanki >Assignee: Chinmay Patidar >Priority: Minor > > Required improvements; > - All is good with entity definition. > - Add CRUD services using entity-auto. Make sure PK is optional while create > service, so that can be generated from OFBiz sequence generator. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-8767) Improvements in ProductPricePurpose entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar reassigned OFBIZ-8767: -- Assignee: Chinmay Patidar > Improvements in ProductPricePurpose entity definition and services > -- > > Key: OFBIZ-8767 > URL: https://issues.apache.org/jira/browse/OFBIZ-8767 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Rishi Solanki >Assignee: Chinmay Patidar >Priority: Minor > > Required improvements; > - All is good with entity definition. > - Add CRUD services using entity-auto. Make sure PK is optional while create > service, so that can be generated from OFBiz sequence generator. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8730) Improvements in ProductAssocType entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8730: --- Attachment: OFBIZ-8730.patch Added the patch to fix this issue. Thanks, [~rishisolankii] for the detailed description. Also, verify the same from entity engine. > Improvements in ProductAssocType entity definition and services > --- > > Key: OFBIZ-8730 > URL: https://issues.apache.org/jira/browse/OFBIZ-8730 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Rishi Solanki >Assignee: Chinmay Patidar >Priority: Minor > Attachments: OFBIZ-8730.patch > > > Required improvements; > - All is good with entity definition. > - Add CRUD services using entity-auto. Make sure PK is optional while create > service, so that can be generated from OFBiz sequence generator. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8729) Improvements in ProdConfItemContentType entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8729: --- Attachment: OFBIZ-8729.patch Added the patch to fix this issue. Thanks, [~rishisolankii] for the detailed description. Also, verify the same from entity engine. > Improvements in ProdConfItemContentType entity definition and services > -- > > Key: OFBIZ-8729 > URL: https://issues.apache.org/jira/browse/OFBIZ-8729 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Rishi Solanki >Assignee: Chinmay Patidar >Priority: Minor > Attachments: OFBIZ-8729.patch > > > Required improvements; > - All is good with entity definition. > - Add CRUD services using entity-auto. Make sure PK is optional while create > service, so that can be generated from OFBiz sequence generator. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-8729) Improvements in ProdConfItemContentType entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar reassigned OFBIZ-8729: -- Assignee: Chinmay Patidar > Improvements in ProdConfItemContentType entity definition and services > -- > > Key: OFBIZ-8729 > URL: https://issues.apache.org/jira/browse/OFBIZ-8729 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Rishi Solanki >Assignee: Chinmay Patidar >Priority: Minor > > Required improvements; > - All is good with entity definition. > - Add CRUD services using entity-auto. Make sure PK is optional while create > service, so that can be generated from OFBiz sequence generator. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-8728) Improvements in ProdCatalogInvFacility entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar reassigned OFBIZ-8728: -- Assignee: Chinmay Patidar > Improvements in ProdCatalogInvFacility entity definition and services > - > > Key: OFBIZ-8728 > URL: https://issues.apache.org/jira/browse/OFBIZ-8728 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Rishi Solanki >Assignee: Chinmay Patidar >Priority: Minor > > Required improvements; > - All is good with entity definition . > - Add crud services using entity-auto. Make sure PK is not optional while > create service. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-8730) Improvements in ProductAssocType entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar reassigned OFBIZ-8730: -- Assignee: Chinmay Patidar > Improvements in ProductAssocType entity definition and services > --- > > Key: OFBIZ-8730 > URL: https://issues.apache.org/jira/browse/OFBIZ-8730 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Rishi Solanki >Assignee: Chinmay Patidar >Priority: Minor > > Required improvements; > - All is good with entity definition. > - Add CRUD services using entity-auto. Make sure PK is optional while create > service, so that can be generated from OFBiz sequence generator. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8729) Improvements in ProdConfItemContentType entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8729: --- Description: Required improvements; - All is good with entity definition. - Add CRUD services using entity-auto. Make sure PK is optional while create service, so that can be generated from OFBiz sequence generator. - Do related changes if any occurrence found for direct create/update/delete of this entity, and replace them with crud services implemented. - As no status/from date/thru date exists in entity, so nothing needs to be taken care while deleting the records from service. was: Required improvements; - All is good with entity definition. - Add CRUD services using entity-auto. Make sure PK is not optional while create service. - Do related changes if any occurrence found for direct create/update/delete of this entity, and replace them with crud services implemented. - As no status/from date/thru date exists in entity, so nothing needs to be taken care while deleting the records from service. > Improvements in ProdConfItemContentType entity definition and services > -- > > Key: OFBIZ-8729 > URL: https://issues.apache.org/jira/browse/OFBIZ-8729 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Rishi Solanki >Priority: Minor > > Required improvements; > - All is good with entity definition. > - Add CRUD services using entity-auto. Make sure PK is optional while create > service, so that can be generated from OFBiz sequence generator. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8729) Improvements in ProdConfItemContentType entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8729: --- Description: Required improvements; - All is good with entity definition. - Add CRUD services using entity-auto. Make sure PK is not optional while create service. - Do related changes if any occurrence found for direct create/update/delete of this entity, and replace them with crud services implemented. - As no status/from date/thru date exists in entity, so nothing needs to be taken care while deleting the records from service. was: Required improvements; - All is good with entity definition. - Add CRUD services using entity-auto. Make sure PK is optional while create service, so that can be generated from OFBiz sequence generator. - Do related changes if any occurrence found for direct create/update/delete of this entity, and replace them with crud services implemented. - As no status/from date/thru date exists in entity, so nothing needs to be taken care while deleting the records from service. > Improvements in ProdConfItemContentType entity definition and services > -- > > Key: OFBIZ-8729 > URL: https://issues.apache.org/jira/browse/OFBIZ-8729 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Rishi Solanki >Priority: Minor > > Required improvements; > - All is good with entity definition. > - Add CRUD services using entity-auto. Make sure PK is not optional while > create service. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-8478) Improvements in ShoppingListType entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar reassigned OFBIZ-8478: -- Assignee: Chinmay Patidar > Improvements in ShoppingListType entity definition and services > --- > > Key: OFBIZ-8478 > URL: https://issues.apache.org/jira/browse/OFBIZ-8478 > Project: OFBiz > Issue Type: Sub-task > Components: order >Affects Versions: Trunk >Reporter: Amit Gadaley >Assignee: Chinmay Patidar >Priority: Minor > Attachments: OFBIZ-8478.patch > > > Required improvements; > - All is good with entity definition. > - Add crud services using entity-auto. Make sure PK is not optional while > create service. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As no status/from date/trhu date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8473) Improvements in ShippingDocument entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8473: --- Attachment: OFBIZ-8473.patch Added the patch to fix this issue. Thanks, [~amit.gadaley] for the detailed description. Also, verify the same from entity engine. > Improvements in ShippingDocument entity definition and services > --- > > Key: OFBIZ-8473 > URL: https://issues.apache.org/jira/browse/OFBIZ-8473 > Project: OFBiz > Issue Type: Sub-task > Components: datamodel >Affects Versions: Trunk >Reporter: Amit Gadaley >Priority: Minor > Attachments: OFBIZ-8473.patch > > > Required improvements; > - All is good with entity definition. > - Add CRUD services using entity-auto. Make sure PK is not optional while > create service. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8461) Improvements in ShipmentGatewayFedex entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8461: --- Assignee: Chinmay Patidar > Improvements in ShipmentGatewayFedex entity definition and services > --- > > Key: OFBIZ-8461 > URL: https://issues.apache.org/jira/browse/OFBIZ-8461 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Amit Gadaley >Assignee: Chinmay Patidar >Priority: Minor > Attachments: OFBIZ-8461.patch > > > Required improvements; > - All is good with entity definition. > - Add CRUD services using entity-auto (only create and delete). Make sure PK > is not optional while create and delete services. > - Do related changes if any occurrence found for direct create/delete of this > entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8461) Improvements in ShipmentGatewayFedex entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8461: --- Description: Required improvements; - All is good with entity definition. - Add CRUD services using entity-auto (only create and delete). Make sure PK is not optional while create and delete services. - Do related changes if any occurrence found for direct create/delete of this entity, and replace them with crud services implemented. - As no status/from date/thru date exists in entity, so nothing needs to be taken care while deleting the records from service. was: Required improvements; - All is good with entity definition. - Add CRUD services using entity-auto (only create and delete). Make sure PK is optional while create service. Make sure PK is not optional while create and delete services. - Do related changes if any occurrence found for direct create/delete of this entity, and replace them with crud services implemented. - As no status/from date/thru date exists in entity, so nothing needs to be taken care while deleting the records from service. > Improvements in ShipmentGatewayFedex entity definition and services > --- > > Key: OFBIZ-8461 > URL: https://issues.apache.org/jira/browse/OFBIZ-8461 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Amit Gadaley >Priority: Minor > Attachments: OFBIZ-8461.patch > > > Required improvements; > - All is good with entity definition. > - Add CRUD services using entity-auto (only create and delete). Make sure PK > is not optional while create and delete services. > - Do related changes if any occurrence found for direct create/delete of this > entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8461) Improvements in ShipmentGatewayFedex entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8461: --- Attachment: OFBIZ-8461.patch Added the patch to fix this issue. Thanks [~amit.gadaley] for the detailed description. For the update service, an existing service with name 'updateShipmentGatewayConfigFedex' exists. Removed it's declaration and definition and used the same service name with entity-auto. > Improvements in ShipmentGatewayFedex entity definition and services > --- > > Key: OFBIZ-8461 > URL: https://issues.apache.org/jira/browse/OFBIZ-8461 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Amit Gadaley >Priority: Minor > Attachments: OFBIZ-8461.patch > > > Required improvements; > - All is good with entity definition. > - Add CRUD services using entity-auto (only create and delete). Make sure PK > is optional while create service. Make sure PK is not optional while create > and delete services. > - Do related changes if any occurrence found for direct create/delete of this > entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8460) Improvements in ShipmentGatewayDhl entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8460: --- Attachment: (was: OFBIZ-8460.patch) > Improvements in ShipmentGatewayDhl entity definition and services > - > > Key: OFBIZ-8460 > URL: https://issues.apache.org/jira/browse/OFBIZ-8460 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Amit Gadaley >Assignee: Chinmay Patidar >Priority: Minor > > Required improvements; > - All is good with entity definition. > - Add CRUD services using entity-auto (only create and delete). Make sure PK > is not optional while create and delete service. > - Do related changes if any occurrence found for direct create/delete of this > entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (OFBIZ-8460) Improvements in ShipmentGatewayDhl entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8460: --- Comment: was deleted (was: Added the patch to fix this issue. Thanks, [~amit.gadaley] for the detailed description. Also, verify the same from entity engine.) > Improvements in ShipmentGatewayDhl entity definition and services > - > > Key: OFBIZ-8460 > URL: https://issues.apache.org/jira/browse/OFBIZ-8460 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Amit Gadaley >Assignee: Chinmay Patidar >Priority: Minor > > Required improvements; > - All is good with entity definition. > - Add CRUD services using entity-auto (only create and delete). Make sure PK > is not optional while create and delete service. > - Do related changes if any occurrence found for direct create/delete of this > entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8460) Improvements in ShipmentGatewayDhl entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8460: --- Attachment: OFBIZ-8460.patch Added the patch to fix this issue. Thanks, [~amit.gadaley] for the detailed description. Also, verify the same from entity engine. > Improvements in ShipmentGatewayDhl entity definition and services > - > > Key: OFBIZ-8460 > URL: https://issues.apache.org/jira/browse/OFBIZ-8460 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Amit Gadaley >Assignee: Chinmay Patidar >Priority: Minor > Attachments: OFBIZ-8460.patch > > > Required improvements; > - All is good with entity definition. > - Add CRUD services using entity-auto (only create and delete). Make sure PK > is not optional while create and delete service. > - Do related changes if any occurrence found for direct create/delete of this > entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8461) Improvements in ShipmentGatewayFedex entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8461: --- Description: Required improvements; - All is good with entity definition. - Add CRUD services using entity-auto (only create and delete). Make sure PK is optional while create service. Make sure PK is not optional while create and delete services. - Do related changes if any occurrence found for direct create/delete of this entity, and replace them with crud services implemented. - As no status/from date/thru date exists in entity, so nothing needs to be taken care while deleting the records from service. was: Required improvements; - All is good with entity definition. - Add CRUD services using entity-auto (only create and delete). Make sure PK is optional while create service, so that can be generated from OFBiz sequence generator. - Do related changes if any occurrence found for direct create/delete of this entity, and replace them with crud services implemented. - As no status/from date/thru date exists in entity, so nothing needs to be taken care while deleting the records from service. > Improvements in ShipmentGatewayFedex entity definition and services > --- > > Key: OFBIZ-8461 > URL: https://issues.apache.org/jira/browse/OFBIZ-8461 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Amit Gadaley >Priority: Minor > > Required improvements; > - All is good with entity definition. > - Add CRUD services using entity-auto (only create and delete). Make sure PK > is optional while create service. Make sure PK is not optional while create > and delete services. > - Do related changes if any occurrence found for direct create/delete of this > entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8464) Improvements in ShipmentGatewayUsps entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8464: --- Description: Required improvements; - All is good with entity definition. - Add CRUD services using entity-auto (only create and delete). Make sure PK is optional while create service, make sure PK is not optional while create and delete services. - Do related changes if any occurrence found for direct create/delete of this entity, and replace them with crud services implemented. - As no status/from date/thru date exists in entity, so nothing needs to be taken care while deleting the records from service. was: Required improvements; - All is good with entity definition. - Add CRUD services using entity-auto (only create and delete). Make sure PK is optional while create service, so that can be generated from OFBiz sequence generator. - Do related changes if any occurrence found for direct create/delete of this entity, and replace them with crud services implemented. - As no status/from date/thru date exists in entity, so nothing needs to be taken care while deleting the records from service. > Improvements in ShipmentGatewayUsps entity definition and services > -- > > Key: OFBIZ-8464 > URL: https://issues.apache.org/jira/browse/OFBIZ-8464 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Amit Gadaley >Priority: Minor > > Required improvements; > - All is good with entity definition. > - Add CRUD services using entity-auto (only create and delete). Make sure PK > is optional while create service, make sure PK is not optional while create > and delete services. > - Do related changes if any occurrence found for direct create/delete of this > entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8460) Improvements in ShipmentGatewayDhl entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8460: --- Description: Required improvements; - All is good with entity definition. - Add CRUD services using entity-auto (only create and delete). Make sure PK is not optional while create and delete service. - Do related changes if any occurrence found for direct create/delete of this entity, and replace them with crud services implemented. - As no status/from date/thru date exists in entity, so nothing needs to be taken care while deleting the records from service. was: Required improvements; - All is good with entity definition. - Add CRUD services using entity-auto (only create and delete). Make sure PK is not optional while create service. - Do related changes if any occurrence found for direct create/delete of this entity, and replace them with crud services implemented. - As no status/from date/thru date exists in entity, so nothing needs to be taken care while deleting the records from service. > Improvements in ShipmentGatewayDhl entity definition and services > - > > Key: OFBIZ-8460 > URL: https://issues.apache.org/jira/browse/OFBIZ-8460 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Amit Gadaley >Assignee: Chinmay Patidar >Priority: Minor > > Required improvements; > - All is good with entity definition. > - Add CRUD services using entity-auto (only create and delete). Make sure PK > is not optional while create and delete service. > - Do related changes if any occurrence found for direct create/delete of this > entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8460) Improvements in ShipmentGatewayDhl entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8460: --- Description: Required improvements; - All is good with entity definition. - Add CRUD services using entity-auto (only create and delete). Make sure PK is not optional while create service. - Do related changes if any occurrence found for direct create/delete of this entity, and replace them with crud services implemented. - As no status/from date/thru date exists in entity, so nothing needs to be taken care while deleting the records from service. was: Required improvements; - All is good with entity definition. - Add CRUD services using entity-auto (only create and delete). Make sure PK is optional while create service, so that can be generated from OFBiz sequence generator. - Do related changes if any occurrence found for direct create/delete of this entity, and replace them with crud services implemented. - As no status/from date/thru date exists in entity, so nothing needs to be taken care while deleting the records from service. > Improvements in ShipmentGatewayDhl entity definition and services > - > > Key: OFBIZ-8460 > URL: https://issues.apache.org/jira/browse/OFBIZ-8460 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Amit Gadaley >Assignee: Chinmay Patidar >Priority: Minor > > Required improvements; > - All is good with entity definition. > - Add CRUD services using entity-auto (only create and delete). Make sure PK > is not optional while create service. > - Do related changes if any occurrence found for direct create/delete of this > entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8431) Improvements in SalesOpportunityCompetitor entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8431: --- Assignee: (was: Amit Gadaley) > Improvements in SalesOpportunityCompetitor entity definition and services > - > > Key: OFBIZ-8431 > URL: https://issues.apache.org/jira/browse/OFBIZ-8431 > Project: OFBiz > Issue Type: Sub-task > Components: marketing >Affects Versions: Trunk >Reporter: Amit Gadaley > Attachments: OFBIZ-8431.patch > > > Required improvements; > - All is good with entity definition. > - Add CRUD services using entity-auto. Make sure PK is not optional while > create service as there is composite primary key. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8437) Improvements in SalesOrderItemFact entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8437: --- Assignee: (was: Chinmay Patidar) > Improvements in SalesOrderItemFact entity definition and services > - > > Key: OFBIZ-8437 > URL: https://issues.apache.org/jira/browse/OFBIZ-8437 > Project: OFBiz > Issue Type: Sub-task > Components: order >Affects Versions: Trunk >Reporter: Amit Gadaley >Priority: Minor > Attachments: OFBIZ-8437.patch > > > Required improvements; > - All is good with entity definition. > - Add CRUD services using entity-auto. Make sure PK is not optional while > create service as there is composite primary key. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8435) Improvements in SalesOpportunityTrckCode entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8435: --- Assignee: (was: Amit Gadaley) > Improvements in SalesOpportunityTrckCode entity definition and services > --- > > Key: OFBIZ-8435 > URL: https://issues.apache.org/jira/browse/OFBIZ-8435 > Project: OFBiz > Issue Type: Sub-task > Components: marketing >Affects Versions: Trunk >Reporter: Amit Gadaley >Priority: Minor > Attachments: OFBIZ-8435.patch > > > Required improvements; > - All is good with entity definition. > - Add CRUD services using entity-auto. Make sure PK is not optional while > create service as there is composite primary key. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8433) Improvements in SalesOpportunityRole entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8433: --- Assignee: (was: Amit Gadaley) > Improvements in SalesOpportunityRole entity definition and services > --- > > Key: OFBIZ-8433 > URL: https://issues.apache.org/jira/browse/OFBIZ-8433 > Project: OFBiz > Issue Type: Sub-task > Components: marketing >Affects Versions: Trunk >Reporter: Amit Gadaley >Priority: Minor > Attachments: OFBIZ-8433.patch > > > All is good with entity definition. > - Add only delete service. > - Do related changes if any occurrence found for direct create/delete of this > entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8437) Improvements in SalesOrderItemFact entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8437: --- Attachment: OFBIZ-8437.patch Added the patch to fix this issue. Thanks, [~amit.gadaley] for the detailed description. Also, verify the same from entity engine. > Improvements in SalesOrderItemFact entity definition and services > - > > Key: OFBIZ-8437 > URL: https://issues.apache.org/jira/browse/OFBIZ-8437 > Project: OFBiz > Issue Type: Sub-task > Components: order >Affects Versions: Trunk >Reporter: Amit Gadaley >Assignee: Amit Gadaley >Priority: Minor > Attachments: OFBIZ-8437.patch > > > Required improvements; > - All is good with entity definition. > - Add CRUD services using entity-auto. Make sure PK is not optional while > create service as there is composite primary key. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-8438) Improvements in SecurityGroup entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar reassigned OFBIZ-8438: -- Assignee: Chinmay Patidar (was: Amit Gadaley) > Improvements in SecurityGroup entity definition and services > > > Key: OFBIZ-8438 > URL: https://issues.apache.org/jira/browse/OFBIZ-8438 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Affects Versions: Trunk >Reporter: Amit Gadaley >Assignee: Chinmay Patidar >Priority: Minor > > Required improvements; > - All is good with entity definition. > - Add CRUD services using entity-auto(only delete). > - Do related changes if any occurrence found for direct delete of this > entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8284) Improvements in OrderAdjustmentTypeAttr entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8284: --- Attachment: OFBIZ-8284.patch Added the patch to fix this issue. Thanks, [~rishisolankii] for the detailed description. Also, verify the same from entity engine. > Improvements in OrderAdjustmentTypeAttr entity definition and services > -- > > Key: OFBIZ-8284 > URL: https://issues.apache.org/jira/browse/OFBIZ-8284 > Project: OFBiz > Issue Type: Sub-task > Components: order >Affects Versions: Trunk >Reporter: Rishi Solanki >Assignee: Chinmay Patidar >Priority: Minor > Attachments: OFBIZ-8284.patch > > > Required improvements; > - All is good with entity definition . > - Add crud services using entity-auto. Make sure PK is not optional while > create service. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-8284) Improvements in OrderAdjustmentTypeAttr entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar reassigned OFBIZ-8284: -- Assignee: Chinmay Patidar > Improvements in OrderAdjustmentTypeAttr entity definition and services > -- > > Key: OFBIZ-8284 > URL: https://issues.apache.org/jira/browse/OFBIZ-8284 > Project: OFBiz > Issue Type: Sub-task > Components: order >Affects Versions: Trunk >Reporter: Rishi Solanki >Assignee: Chinmay Patidar >Priority: Minor > > Required improvements; > - All is good with entity definition . > - Add crud services using entity-auto. Make sure PK is not optional while > create service. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8270) Improvements in InvoiceType entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8270: --- Attachment: OFBIZ-8270.patch Added the patch to fix the issue. Thanks, [~rishisolankii] for the detailed description. Also, verified the same from the entity engine. > Improvements in InvoiceType entity definition and services > -- > > Key: OFBIZ-8270 > URL: https://issues.apache.org/jira/browse/OFBIZ-8270 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk >Reporter: Rishi Solanki >Assignee: Chinmay Patidar >Priority: Minor > Attachments: OFBIZ-8270.patch > > > Required improvements; > - All is good with entity definition . > - Add CRUD services using entity-auto. Make sure PK is optional while create > service, so that can be generated from OFBiz sequence generator. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-8270) Improvements in InvoiceType entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar reassigned OFBIZ-8270: -- Assignee: Chinmay Patidar > Improvements in InvoiceType entity definition and services > -- > > Key: OFBIZ-8270 > URL: https://issues.apache.org/jira/browse/OFBIZ-8270 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk >Reporter: Rishi Solanki >Assignee: Chinmay Patidar >Priority: Minor > > Required improvements; > - All is good with entity definition . > - Add CRUD services using entity-auto. Make sure PK is optional while create > service, so that can be generated from OFBiz sequence generator. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8249) Improvements in InventoryItemTypeAttr entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8249: --- Attachment: OFBIZ-8249.patch Added the patch to fix this issue. Thanks, [~rishisolankii] for the detailed description. Also, verify the same from entity engine. > Improvements in InventoryItemTypeAttr entity definition and services > > > Key: OFBIZ-8249 > URL: https://issues.apache.org/jira/browse/OFBIZ-8249 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Rishi Solanki >Assignee: Chinmay Patidar >Priority: Minor > Attachments: OFBIZ-8249.patch > > > Required improvements; > - All is good with entity definition . > - Add crud services using entity-auto. Make sure PK is not optional while > create service. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8249) Improvements in InventoryItemTypeAttr entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8249: --- Assignee: Chinmay Patidar > Improvements in InventoryItemTypeAttr entity definition and services > > > Key: OFBIZ-8249 > URL: https://issues.apache.org/jira/browse/OFBIZ-8249 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Rishi Solanki >Assignee: Chinmay Patidar >Priority: Minor > > Required improvements; > - All is good with entity definition . > - Add crud services using entity-auto. Make sure PK is not optional while > create service. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, so nothing needs to be > taken care while deleting the records from service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8005) Improvements in BudgetScenarioApplication entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-8005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Patidar updated OFBIZ-8005: --- Assignee: Amit Gadaley > Improvements in BudgetScenarioApplication entity definition and services > > > Key: OFBIZ-8005 > URL: https://issues.apache.org/jira/browse/OFBIZ-8005 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk >Reporter: Rishi Solanki >Assignee: Amit Gadaley >Priority: Minor > Attachments: OFBIZ-8005.patch > > > Required improvements; > - All is good with entity definition . > - Add crud services using entity-auto. Make sure PK is not optional while > create service. > - Do related changes if any occurrence found for direct create/update/delete > of this entity, and replace them with crud services implemented. > - As no status/from date/thru date exists in entity, but it looks like it > will contain the revisions of same data so history needs to be maintain. We > should not provide service for delete its record. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
