[jira] Updated: (OFBIZ-3339) Enhance Find Billing Account Screen to follow standard Find/List screen pattern
[ https://issues.apache.org/jira/browse/OFBIZ-3339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-3339: --- Attachment: Ofbiz_3339.patch I have attached patch for enhancing Billing Account screen.I have added Find and List forms for Billing Accounts. Testing steps are as follows : 1)Go to Accounting main screen https://localhost:8443/accounting/control/main. 2)Click on Billing Accounts tab https://localhost:8443/accounting/control/FindBillingAccount. Result : It will display Find/List form for Billing Account. -- Thanks Surya Kusumakar > Enhance Find Billing Account Screen to follow standard Find/List screen > pattern > --- > > Key: OFBIZ-3339 > URL: https://issues.apache.org/jira/browse/OFBIZ-3339 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: SVN trunk >Reporter: Ratnesh Upadhyay >Priority: Minor > Fix For: SVN trunk > > Attachments: Ofbiz_3339.patch > > > Enhance https://demo.ofbiz.org/accounting/control/FindBillingAccount. Add > Search form where user can enter search criteria. The screen should follow > standard Find/List screen decorator. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3337) Restrict Canceled Financial Account operations in AR Payment screens.
[ https://issues.apache.org/jira/browse/OFBIZ-3337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-3337: --- Attachment: Ofbiz_3337.patch I have put checks at service and Ui level for validating the deactivated Financial Account at AR Payment screens . Testing steps are as follows : Scenario 1 : 1)Cancel/Frozen any of the Fin Account (https://localhost:8443/accounting/control/EditFinAccount?finAccountId=ABN_CHECKING) by setting its status to Cancel/Set Manually Frozen. 2)Now go to Find Payments screen in AR https://localhost:8443/ar/control/findPayments. 3)Click on New Payment. 4)Select Fin Account Field. --> Expected Result : - It will not show inactive Fin Account. --> Actual Result : - Working as expected. Scenario 2 : 1)Now go to Find payments screen and then click on Batch Payments tab https://localhost:8443/ar/control/batchPayments. 2)Click on Find button. 3)Select few payments and select Create a batch option from select box. --> Expected Result : - It will not show inactive Fin Account. --> Actual Result : - Working as expected. Scenario 3 : 1)Remove check from batchPayments.ftl to validate this work. 2)Now go to Find payments screen and then click on Batch Payments tab https://localhost:8443/ar/control/batchPayments. 3)Click on Find button. 4)Select few payments and then select 'Create a batch' option from select box. 5)Select Fin Account which is in Inactive status. 6)Click on Run button. --> Expected Result : - Service will through Invalid status error. --> Actual Result : - Working as expected. -- Thanks Surya Kusumakar > Restrict Canceled Financial Account operations in AR Payment screens. > - > > Key: OFBIZ-3337 > URL: https://issues.apache.org/jira/browse/OFBIZ-3337 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: SVN trunk >Reporter: Surya Kusumakar >Priority: Minor > Fix For: SVN trunk > > Attachments: Ofbiz_3337.patch > > > When we create Payment (Batch Payment) at find AR payment screen then > deactivated bank account should not get displayed in Bank Account list. > Also add validation at service level so that deactivated(canceled/frozen) > financial account cannot be assigned to batch. > On New payment screen deactivated fin account should not get displayed in the > list. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-3337) Restrict Canceled Financial Account operations in AR Payment screens.
Restrict Canceled Financial Account operations in AR Payment screens. - Key: OFBIZ-3337 URL: https://issues.apache.org/jira/browse/OFBIZ-3337 Project: OFBiz Issue Type: Bug Components: accounting Affects Versions: SVN trunk Reporter: Surya Kusumakar Priority: Minor Fix For: SVN trunk When we create Payment (Batch Payment) at find AR payment screen then deactivated bank account should not get displayed in Bank Account list. Also add validation at service level so that deactivated(canceled/frozen) financial account cannot be assigned to batch. On New payment screen deactivated fin account should not get displayed in the list. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3334) Deactivated Financial Account should not get displayed in list for Issue Check Run process.
[ https://issues.apache.org/jira/browse/OFBIZ-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-3334: --- Attachment: Ofbiz_3334.patch I have put checks at service level as well as UI. Testing steps to check it : Scenario one : Checks at Ui level. 1)Edit any of the Fin Account (https://localhost:8443/accounting/control/EditFinAccount?finAccountId=ABN_CHECKING) and set its status to Cancel/Set Manually Frozen. 2)Go to AP Invoices screen https://localhost:8443/ap/control/FindApInvoices . 3)Click on Purchase Invoices tab https://localhost:8443/ap/control/FindPurchaseInvoices and then depress on Find button. 4)Select few invoices and select Vendor Payment Method from select box. --> Expected Result : It will not show deactivated Fin Account. --> Actual Result : Working as expected. Scenario 2 - Checks at service level : Remove checks from Ui level then run these steps. 1)Go to AP Invoices screen https://localhost:8443/ap/control/FindApInvoices 2)Click on Purchase Invoices tab https://localhost:8443/ap/control/FindPurchaseInvoices and then depress on Find button. 3)Select few invoices and select Vendor Payment Method from select box which is deactivated. 4)Click on Run button. --> Expected Result : Service will throw invalid status error. --> Actual Result : Working as expected. --- Thanks > Deactivated Financial Account should not get displayed in list for Issue > Check Run process. > --- > > Key: OFBIZ-3334 > URL: https://issues.apache.org/jira/browse/OFBIZ-3334 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: SVN trunk >Reporter: Surya Kusumakar >Priority: Minor > Fix For: SVN trunk > > Attachments: Ofbiz_3334.patch > > > Do not display deactivated(Cancel/Frozen) financial account in list for Issue > check (Vendor Payment Method) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-3334) Deactivated Financial Account should not get displayed in list for Issue Check Run process.
Deactivated Financial Account should not get displayed in list for Issue Check Run process. --- Key: OFBIZ-3334 URL: https://issues.apache.org/jira/browse/OFBIZ-3334 Project: OFBiz Issue Type: Bug Components: accounting Affects Versions: SVN trunk Reporter: Surya Kusumakar Priority: Minor Fix For: SVN trunk Do not display deactivated(Cancel/Frozen) financial account in list for Issue check (Vendor Payment Method) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3291) On PaymentGroup screens records are getting repeated and are not filtered on basis of PaymentGroupTypeId .
[ https://issues.apache.org/jira/browse/OFBIZ-3291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-3291: --- Attachment: OFBIZ_3291.patch Attached patch will cover following points : 1)Now records are not getting repeated. 2)Also records are getting filtered on basis of PaymentGroupTypeId for AR/AP screens. -- Thanks Surya Kusumakar > On PaymentGroup screens records are getting repeated and are not filtered on > basis of PaymentGroupTypeId . > -- > > Key: OFBIZ-3291 > URL: https://issues.apache.org/jira/browse/OFBIZ-3291 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: SVN trunk >Reporter: Surya Kusumakar >Priority: Minor > Fix For: SVN trunk > > Attachments: OFBIZ_3291.patch > > > Here are the testing steps to test the issue : > a) Testing steps for DepositSlips tab in Financial Accounts : > 1. Create some payment batches and check runs for different Fin Accounts. > 2. Go to Accounting ->Financial Account. > 3. Click on Find tab > https://localhost:8443/accounting/control/FindFinAccount > 4. Select any of the Fiancial Account. > 5. Click on Deposit Slips tab > https://localhost:8443/accounting/control/FindDepositSlips?finAccountId=SC_CHECKING&organizationPartyId=Company > 6. Click on search button. > 7. This will display all deposit slips created. Those which are > associated to FinAccount. > 8. It is also displaying the repeated records and records which have > Payment Group type as Check Run. > b)Testing steps for AP Invoices > 1. Go To AP tab and click on Purchase Invoices > https://localhost:8443/ap/control/FindPurchaseInvoices. > 2. Click on Search button and select the invoices to perform check run > and then select Issue to Check and click on run button. > 3. Now click on APPaymentGroups .Click on search button . > 4. It is also displaying the repeated records and records which have > Payment Group type as Batch Payments. > c)Testing steps for AR Payments > 1. Go To AR tab and click on AR Payments Groups > https://localhost:8443/ar/control/FindArPaymentGroups > 2. It is also displaying the repeated records and records which have > Payment Group type as Check Run. > -- > Thanks > Surya Kusumakar -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-3291) On PaymentGroup screens records are getting repeated and are not filtered on basis of PaymentGroupTypeId .
On PaymentGroup screens records are getting repeated and are not filtered on basis of PaymentGroupTypeId . -- Key: OFBIZ-3291 URL: https://issues.apache.org/jira/browse/OFBIZ-3291 Project: OFBiz Issue Type: Bug Components: accounting Affects Versions: SVN trunk Reporter: Surya Kusumakar Priority: Minor Fix For: SVN trunk Here are the testing steps to test the issue : a) Testing steps for DepositSlips tab in Financial Accounts : 1. Create some payment batches and check runs for different Fin Accounts. 2. Go to Accounting ->Financial Account. 3. Click on Find tab https://localhost:8443/accounting/control/FindFinAccount 4. Select any of the Fiancial Account. 5. Click on Deposit Slips tab https://localhost:8443/accounting/control/FindDepositSlips?finAccountId=SC_CHECKING&organizationPartyId=Company 6. Click on search button. 7. This will display all deposit slips created. Those which are associated to FinAccount. 8. It is also displaying the repeated records and records which have Payment Group type as Check Run. b)Testing steps for AP Invoices 1. Go To AP tab and click on Purchase Invoices https://localhost:8443/ap/control/FindPurchaseInvoices. 2. Click on Search button and select the invoices to perform check run and then select Issue to Check and click on run button. 3. Now click on APPaymentGroups .Click on search button . 4. It is also displaying the repeated records and records which have Payment Group type as Batch Payments. c)Testing steps for AR Payments 1. Go To AR tab and click on AR Payments Groups https://localhost:8443/ar/control/FindArPaymentGroups 2. It is also displaying the repeated records and records which have Payment Group type as Check Run. -- Thanks Surya Kusumakar -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3244) New feature to upload multiple Additional View Images at Product Content.
[ https://issues.apache.org/jira/browse/OFBIZ-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-3244: --- Attachment: OFBIZ_3244.patch Hello Jacques, Thanks for your comments. I have uploaded patch with the changes suggested by you. -- Thanks Surya Kusumakar > New feature to upload multiple Additional View Images at Product Content. > --- > > Key: OFBIZ-3244 > URL: https://issues.apache.org/jira/browse/OFBIZ-3244 > Project: OFBiz > Issue Type: New Feature > Components: content >Affects Versions: SVN trunk >Reporter: Surya Kusumakar >Priority: Minor > Fix For: SVN trunk > > Attachments: OFBIZ-3244.png, OFBIZ_3244.patch, OFBIZ_3244.patch > > > Added a new feature in Product Content to add all four images at a time and > one can preview those images in larger view on mouse over of particular image. > Here are the testing steps to test the feature : > 1)Go to catalog https://localhost:8443/catalog/control/main > 2)Search for product for e.g GZ-2644 > 3)Click on Product Name > https://localhost:8443/catalog/control/EditProduct?productId=GZ-2644 . > 4)Click on Content tab .It will open edit product content screen > https://localhost:28443/catalog/control/EditProductContent?productId=GZ-2644. > 5)Go to Add Additional images section at the bottom of the screen. > 6)Upload images from there and click on Upload button. > 7)You can preview uploaded images at the left side of file input tags. > 8)If you also preview larger images by doing mouse over at the images present > on left side . > I am also attaching screenshot for reference. > -- > Thanks > Surya Kusumakar > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3244) New feature to upload multiple Additional View Images at Product Content.
[ https://issues.apache.org/jira/browse/OFBIZ-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-3244: --- Attachment: OFBIZ_3244.patch OFBIZ-3244.png Attached patch and screenshot for the feature. Thanks Surya Kusumakar > New feature to upload multiple Additional View Images at Product Content. > --- > > Key: OFBIZ-3244 > URL: https://issues.apache.org/jira/browse/OFBIZ-3244 > Project: OFBiz > Issue Type: New Feature > Components: content >Affects Versions: SVN trunk >Reporter: Surya Kusumakar >Priority: Minor > Fix For: SVN trunk > > Attachments: OFBIZ-3244.png, OFBIZ_3244.patch > > > Added a new feature in Product Content to add all four images at a time and > one can preview those images in larger view on mouse over of particular image. > Here are the testing steps to test the feature : > 1)Go to catalog https://localhost:8443/catalog/control/main > 2)Search for product for e.g GZ-2644 > 3)Click on Product Name > https://localhost:8443/catalog/control/EditProduct?productId=GZ-2644 . > 4)Click on Content tab .It will open edit product content screen > https://localhost:28443/catalog/control/EditProductContent?productId=GZ-2644. > 5)Go to Add Additional images section at the bottom of the screen. > 6)Upload images from there and click on Upload button. > 7)You can preview uploaded images at the left side of file input tags. > 8)If you also preview larger images by doing mouse over at the images present > on left side . > I am also attaching screenshot for reference. > -- > Thanks > Surya Kusumakar > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-3244) New feature to upload multiple Additional View Images at Product Content.
New feature to upload multiple Additional View Images at Product Content. --- Key: OFBIZ-3244 URL: https://issues.apache.org/jira/browse/OFBIZ-3244 Project: OFBiz Issue Type: New Feature Components: content Affects Versions: SVN trunk Reporter: Surya Kusumakar Priority: Minor Fix For: SVN trunk Added a new feature in Product Content to add all four images at a time and one can preview those images in larger view on mouse over of particular image. Here are the testing steps to test the feature : 1)Go to catalog https://localhost:8443/catalog/control/main 2)Search for product for e.g GZ-2644 3)Click on Product Name https://localhost:8443/catalog/control/EditProduct?productId=GZ-2644 . 4)Click on Content tab .It will open edit product content screen https://localhost:28443/catalog/control/EditProductContent?productId=GZ-2644. 5)Go to Add Additional images section at the bottom of the screen. 6)Upload images from there and click on Upload button. 7)You can preview uploaded images at the left side of file input tags. 8)If you also preview larger images by doing mouse over at the images present on left side . I am also attaching screenshot for reference. -- Thanks Surya Kusumakar -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3095) Getting error "Number Format Exception" on OnePageCheckout.
[ https://issues.apache.org/jira/browse/OFBIZ-3095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-3095: --- Attachment: OFBIZ_3095.patch Attaching patch again with few changes. Thanks to Rishi for useful suggestion. -- Thanks > Getting error "Number Format Exception" on OnePageCheckout. > --- > > Key: OFBIZ-3095 > URL: https://issues.apache.org/jira/browse/OFBIZ-3095 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/ecommerce >Affects Versions: SVN trunk >Reporter: Surya Kusumakar >Assignee: Ashish Vijaywargiya >Priority: Minor > Fix For: SVN trunk > > Attachments: OFBIZ_3095.patch, OFBIZ_3095.patch > > > On OnePageCheckout page after clicking on button "Continue to Step 2 " > getting "NumberFormatException". -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3095) Getting error "Number Format Exception" on OnePageCheckout.
[ https://issues.apache.org/jira/browse/OFBIZ-3095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-3095: --- Attachment: OFBIZ_3095.patch Here is the patch for above mentioned error. > Getting error "Number Format Exception" on OnePageCheckout. > --- > > Key: OFBIZ-3095 > URL: https://issues.apache.org/jira/browse/OFBIZ-3095 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/ecommerce >Affects Versions: SVN trunk >Reporter: Surya Kusumakar >Priority: Minor > Fix For: SVN trunk > > Attachments: OFBIZ_3095.patch > > > On OnePageCheckout page after clicking on button "Continue to Step 2 " > getting "NumberFormatException". -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-3095) Getting error "Number Format Exception" on OnePageCheckout.
Getting error "Number Format Exception" on OnePageCheckout. --- Key: OFBIZ-3095 URL: https://issues.apache.org/jira/browse/OFBIZ-3095 Project: OFBiz Issue Type: Bug Components: specialpurpose/ecommerce Affects Versions: SVN trunk Reporter: Surya Kusumakar Priority: Minor Fix For: SVN trunk On OnePageCheckout page after clicking on button "Continue to Step 2 " getting "NumberFormatException". -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2922) Update Sign up for Contact List (signUpForContactList) service.
[ https://issues.apache.org/jira/browse/OFBIZ-2922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-2922: --- Attachment: OFBIZ_2922.patch Here is the patch for changes mentioned . -- Regards Surya KUsumakar > Update Sign up for Contact List (signUpForContactList) service. > --- > > Key: OFBIZ-2922 > URL: https://issues.apache.org/jira/browse/OFBIZ-2922 > Project: OFBiz > Issue Type: Improvement > Components: marketing >Affects Versions: SVN trunk >Reporter: Sumit Pandit > Fix For: SVN trunk > > Attachments: OFBIZ_2922.patch > > > Update service - signUpForContactList and add a new IN parameter - > partyId(o), if it passed then create Party Email Address and Contact List for > passed in partyId. If it is not then it will work in same manner as it is > working currently. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2854) Accounting - Cancel Invoice and Cancel Chck Run.
[ https://issues.apache.org/jira/browse/OFBIZ-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-2854: --- Attachment: CancelInvoicenCancelCheckRun.patch Both the above defined test cases are implemented in this patch. Thanks to Sumit. -- Surya Kusumakar > Accounting - Cancel Invoice and Cancel Chck Run. > > > Key: OFBIZ-2854 > URL: https://issues.apache.org/jira/browse/OFBIZ-2854 > Project: OFBiz > Issue Type: Sub-task >Reporter: Sumit Pandit > Attachments: CancelInvoicenCancelCheckRun.patch > > > Prepare a JUnit test case to test the GL Posting affected during following > process - > 1) Cancel Invoice > 2) cancel check run. > Idea to prepare this test case is to verify the GL accounting balances, when > above process will execute. > Prepare data if needed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2852) Accounting - Reconciliation - Issue in running total and ending balance calculation.
[ https://issues.apache.org/jira/browse/OFBIZ-2852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-2852: --- Attachment: OFBIZ_2852.patch This patch solves the issue in running total and ending balance calculation. Thanks to Sumit . -- Surya Kusumakar > Accounting - Reconciliation - Issue in running total and ending balance > calculation. > > > Key: OFBIZ-2852 > URL: https://issues.apache.org/jira/browse/OFBIZ-2852 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: SVN trunk >Reporter: Sumit Pandit > Fix For: SVN trunk > > Attachments: OFBIZ_2852.patch > > > In Accounting - Reconciliation, At Bank Reconciliation Tab - Running total is > not calculated properly. > Calculation should perform based on following formula - > if FinAccountTrans.FinAccountTransType is Withdraw > FinAccountTrans amount will minus from runningTotal > else > FinAccountTrans amount will add to running total (In case of adjustment > make sure that amount will add with sign) > Ending Balance = Opening Balance + Running total. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2851) Accounting - Void Payment and Check Run.
[ https://issues.apache.org/jira/browse/OFBIZ-2851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-2851: --- Attachment: OFBIZ_2851.patch This patch covers the above define two junit test cases. -- Surya Kusumakar > Accounting - Void Payment and Check Run. > - > > Key: OFBIZ-2851 > URL: https://issues.apache.org/jira/browse/OFBIZ-2851 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: SVN trunk >Reporter: Sumit Pandit > Fix For: SVN trunk > > Attachments: OFBIZ_2851.patch > > > Prepare a JUnit test case to test the GL Posting affected during following > process - > 1) Void a Payment > 2) Issue Check Run. > Idea to prepare this test case is to verify the GL accounting balances, when > about process will execute. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2824) Implement Inventory Valuation report
[ https://issues.apache.org/jira/browse/OFBIZ-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-2824: --- Attachment: Ofbiz_2824.patch Here is the patch for Inventory Valuation Report . Currently this patch works only for average cost. Thanks to Sumit,Rishi and Awdesh. Surya Kusumakar > Implement Inventory Valuation report > > > Key: OFBIZ-2824 > URL: https://issues.apache.org/jira/browse/OFBIZ-2824 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: SVN trunk >Reporter: Sumit Pandit >Priority: Minor > Fix For: SVN trunk > > Attachments: Ofbiz_2824.patch > > > The reports should be placed under Reports tab in accounting. > Filters: Facility id (owned by the company for which we are running the GL), > Product id , Product Category id, Date range; Cost Type > Columns: Product; Quantity on Hand; Unit Cost; Total Value. > According to the "Cost Type" selected the Unit Cost value will change; > however for now we will only implement "average costing". > The drop down for "Cost Type" should contain the same values in this (Cost Of > Goods Sold (COGS) Method): > https://localhost:8443/accounting/control/AdminMain?organizationPartyId=DemoLeadOwnersGroup > and the default value should be the same selected in that screen > (PartyAcctgPreferences) > Reuse artifacts from the following report that is already computing average > costs for products: > https://localhost:8443/facility/control/InventoryAverageCosts?facilityId=WebStoreWarehouse > Thanks Eva, Vince and Jacopo for guidance. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2803) In Components AP/AR show relevant screens.
[ https://issues.apache.org/jira/browse/OFBIZ-2803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740864#action_12740864 ] Surya Kusumakar commented on OFBIZ-2803: Above patch completes the implementation of relevant screens in AP/AR. Thanks to Sumit Pandit and Awdesh Parihar. > In Components AP/AR show relevant screens. > -- > > Key: OFBIZ-2803 > URL: https://issues.apache.org/jira/browse/OFBIZ-2803 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: SVN trunk >Reporter: Sumit Pandit >Assignee: Anil K Patel >Priority: Minor > Fix For: SVN trunk > > Attachments: Ofbiz_2803.patch, Ofbiz_2803.patch > > > From component AR remove - screens which are not associated to it like - > screen to Create an Outgoing Payment, to Create Purchase Invoice. And follow > same for AP. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2803) In Components AP/AR show relevant screens.
[ https://issues.apache.org/jira/browse/OFBIZ-2803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-2803: --- Attachment: Ofbiz_2803.patch This patch contains : 1.Incoming payment search and creation form in Accounts Receivable. 2.Sales Invoice search and creation form in Accounts Receivable. -- Regards Surya Kusumakar > In Components AP/AR show relevant screens. > -- > > Key: OFBIZ-2803 > URL: https://issues.apache.org/jira/browse/OFBIZ-2803 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: SVN trunk >Reporter: Sumit Pandit >Assignee: Anil K Patel >Priority: Minor > Fix For: SVN trunk > > Attachments: Ofbiz_2803.patch, Ofbiz_2803.patch > > > From component AR remove - screens which are not associated to it like - > screen to Create an Outgoing Payment, to Create Purchase Invoice. And follow > same for AP. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2803) In Components AP/AR show relevant screens.
[ https://issues.apache.org/jira/browse/OFBIZ-2803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-2803: --- Attachment: Ofbiz_2803.patch Hello Sumit , Here i am attaching patch which contains : 1. New Outgoing Payment Search form. 2. New Outgoing Payment create form. Regards Surya Kusumakar > In Components AP/AR show relevant screens. > -- > > Key: OFBIZ-2803 > URL: https://issues.apache.org/jira/browse/OFBIZ-2803 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: SVN trunk >Reporter: Sumit Pandit >Assignee: Anil K Patel >Priority: Minor > Fix For: SVN trunk > > Attachments: Ofbiz_2803.patch > > > From component AR remove - screens which are not associated to it like - > screen to Create an Outgoing Payment, to Create Purchase Invoice. And follow > same for AP. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2801) Add one more search cretria as - "Invoice type" at AP ->FindPurchaseInvoices form.
[ https://issues.apache.org/jira/browse/OFBIZ-2801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-2801: --- Attachment: Ofbiz_2801.patch Hello Sumit, i have added drop down as Invoice Type in Ap-->FindPurachseInvoices form. Attaching the patch. Regards Surya Ksumakar > Add one more search cretria as - "Invoice type" at AP ->FindPurchaseInvoices > form. > --- > > Key: OFBIZ-2801 > URL: https://issues.apache.org/jira/browse/OFBIZ-2801 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: SVN trunk >Reporter: Sumit Pandit >Priority: Minor > Fix For: SVN trunk > > Attachments: Ofbiz_2801.patch > > > At AP->FindPurchaseInvoice add a dropdown for Outgoing InvoiceTypeId. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2738) (Accounting) Junit test case for servic - setFinAccountTransStatus.
[ https://issues.apache.org/jira/browse/OFBIZ-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-2738: --- Attachment: Ofbiz_2738.patch Here is the test case patch for service setFinAccountTransStatus. -- Regards Surya Kusumakar > (Accounting) Junit test case for servic - setFinAccountTransStatus. > --- > > Key: OFBIZ-2738 > URL: https://issues.apache.org/jira/browse/OFBIZ-2738 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: SVN trunk >Reporter: Sumit Pandit > Fix For: SVN trunk > > Attachments: Ofbiz_2738.patch > > > Write a jUnit Test case for new service - setFinAccountTrans status. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2727) Enhance the existing FinAccount "transactions" screen to show more information about associated payments
[ https://issues.apache.org/jira/browse/OFBIZ-2727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-2727: --- Comment: was deleted (was: The following enhancements are done : 1.Shown more information about associated payments (payment method and payment type) 2.Added cancel button for canceling FinAccountTrans . 3.Shown the statusId field for each transaction. 4.Added search form to filter transactions by date range, type (deposit, withdrawal, adjustments, statusId) 5.At the bottom of the screen shown the following totals: a) Grand Total b) Created Grand Total c) Approved Grand Total d) Created/Approved Grand Total ) > Enhance the existing FinAccount "transactions" screen to show more > information about associated payments > > > Key: OFBIZ-2727 > URL: https://issues.apache.org/jira/browse/OFBIZ-2727 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: SVN trunk >Reporter: Sumit Pandit > Fix For: SVN trunk > > Attachments: EnhancementsInFinAccountTrans.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2727) Enhance the existing FinAccount "transactions" screen to show more information about associated payments
[ https://issues.apache.org/jira/browse/OFBIZ-2727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732856#action_12732856 ] Surya Kusumakar commented on OFBIZ-2727: The following enhancements are done : 1.Shown more information about associated payments (payment method and payment type) 2.Added cancel button for canceling FinAccountTrans . 3.Shown the statusId field for each transaction. 4.Added search form to filter transactions by date range, type (deposit, withdrawal, adjustments, statusId) 5.At the bottom of the screen shown the following totals: a) Grand Total b) Created Grand Total c) Approved Grand Total d) Created/Approved Grand Total > Enhance the existing FinAccount "transactions" screen to show more > information about associated payments > > > Key: OFBIZ-2727 > URL: https://issues.apache.org/jira/browse/OFBIZ-2727 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: SVN trunk >Reporter: Sumit Pandit > Fix For: SVN trunk > > Attachments: EnhancementsInFinAccountTrans.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2727) Enhance the existing FinAccount "transactions" screen to show more information about associated payments
[ https://issues.apache.org/jira/browse/OFBIZ-2727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732855#action_12732855 ] Surya Kusumakar commented on OFBIZ-2727: The following enhancements are done : 1.Shown more information about associated payments (payment method and payment type) 2.Added cancel button for canceling FinAccountTrans . 3.Shown the statusId field for each transaction. 4.Added search form to filter transactions by date range, type (deposit, withdrawal, adjustments, statusId) 5.At the bottom of the screen shown the following totals: a) Grand Total b) Created Grand Total c) Approved Grand Total d) Created/Approved Grand Total > Enhance the existing FinAccount "transactions" screen to show more > information about associated payments > > > Key: OFBIZ-2727 > URL: https://issues.apache.org/jira/browse/OFBIZ-2727 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: SVN trunk >Reporter: Sumit Pandit > Fix For: SVN trunk > > Attachments: EnhancementsInFinAccountTrans.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2727) Enhance the existing FinAccount "transactions" screen to show more information about associated payments
[ https://issues.apache.org/jira/browse/OFBIZ-2727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-2727: --- Attachment: EnhancementsInFinAccountTrans.patch Here is the patch for enhancements in FinAccountTrans screen. Thanks to Jacopo , Rishi and Sumit. > Enhance the existing FinAccount "transactions" screen to show more > information about associated payments > > > Key: OFBIZ-2727 > URL: https://issues.apache.org/jira/browse/OFBIZ-2727 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: SVN trunk >Reporter: Sumit Pandit > Fix For: SVN trunk > > Attachments: EnhancementsInFinAccountTrans.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2720) Add statusId field to the FinAccountTrans entity and verify that existing functionality is not broken.
[ https://issues.apache.org/jira/browse/OFBIZ-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-2720: --- Attachment: AddedStatusIdToFinAccountTrans.patch Did minor modification in migration service. Thanks you Vikas for your suggestion. -- Regards Surya Kusumakar > Add statusId field to the FinAccountTrans entity and verify that existing > functionality is not broken. > -- > > Key: OFBIZ-2720 > URL: https://issues.apache.org/jira/browse/OFBIZ-2720 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: SVN trunk >Reporter: Sumit Pandit >Assignee: Anil K Patel > Fix For: SVN trunk > > Attachments: AddedStatusIdToFinAccountTrans.patch, > AddedStatusIdToFinAccountTrans.patch, AddedStatusIdToFinAccountTrans.patch > > > A) Add statusId field to the FinAccountTrans entity. > B) Seed data: "Created", "Approved". > C) Create a database upgrade script that sets the statusId to "Approved" to > all the records with statusId set to null, no ECA should be triggered when > this update is done. > D) Verify that all the existing code that is using the FinAccountTrans entity > works fine; the idea is that if there is code that: > 1) creates new FinAccountTrans records, then it should create them in the > "Approved" status > 2) if there are accounting transactions posted when FinAccountTrans records > are created/updated, this should now happen only when the status is "Approved" > Thanks Jacopo for the Guidance. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2720) Add statusId field to the FinAccountTrans entity and verify that existing functionality is not broken.
[ https://issues.apache.org/jira/browse/OFBIZ-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-2720: --- Attachment: AddedStatusIdToFinAccountTrans.patch Hello Rishi , Thanks for your comments , i have uploaded patch again with changes. -- Regards Surya Kusumakar > Add statusId field to the FinAccountTrans entity and verify that existing > functionality is not broken. > -- > > Key: OFBIZ-2720 > URL: https://issues.apache.org/jira/browse/OFBIZ-2720 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: SVN trunk >Reporter: Sumit Pandit > Fix For: SVN trunk > > Attachments: AddedStatusIdToFinAccountTrans.patch, > AddedStatusIdToFinAccountTrans.patch > > > A) Add statusId field to the FinAccountTrans entity. > B) Seed data: "Created", "Approved". > C) Create a database upgrade script that sets the statusId to "Approved" to > all the records with statusId set to null, no ECA should be triggered when > this update is done. > D) Verify that all the existing code that is using the FinAccountTrans entity > works fine; the idea is that if there is code that: > 1) creates new FinAccountTrans records, then it should create them in the > "Approved" status > 2) if there are accounting transactions posted when FinAccountTrans records > are created/updated, this should now happen only when the status is "Approved" > Thanks Jacopo for the Guidance. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2720) Add statusId field to the FinAccountTrans entity and verify that existing functionality is not broken.
[ https://issues.apache.org/jira/browse/OFBIZ-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-2720: --- Attachment: AddedStatusIdToFinAccountTrans.patch Hello Sumit, Here is the patch for the above desired functionality. Thanks to Sumit and Rishi. -- Regards Surya Kusumakar > Add statusId field to the FinAccountTrans entity and verify that existing > functionality is not broken. > -- > > Key: OFBIZ-2720 > URL: https://issues.apache.org/jira/browse/OFBIZ-2720 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: SVN trunk >Reporter: Sumit Pandit > Fix For: SVN trunk > > Attachments: AddedStatusIdToFinAccountTrans.patch > > > A) Add statusId field to the FinAccountTrans entity. > B) Seed data: "Created", "Approved". > C) Create a database upgrade script that sets the statusId to "Approved" to > all the records with statusId set to null, no ECA should be triggered when > this update is done. > D) Verify that all the existing code that is using the FinAccountTrans entity > works fine; the idea is that if there is code that: > 1) creates new FinAccountTrans records, then it should create them in the > "Approved" status > 2) if there are accounting transactions posted when FinAccountTrans records > are created/updated, this should now happen only when the status is "Approved" > Thanks Jacopo for the Guidance. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2711) Junit test case for Accounting - Void Payment and Cancel Invoice services.
[ https://issues.apache.org/jira/browse/OFBIZ-2711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-2711: --- Attachment: TestCaseForInvoicePaymentReversing.patch Here is the patch for test cases of services voidPayment and cancelInvoice. -- Regards Surya Kusumakar > Junit test case for Accounting - Void Payment and Cancel Invoice services. > -- > > Key: OFBIZ-2711 > URL: https://issues.apache.org/jira/browse/OFBIZ-2711 > Project: OFBiz > Issue Type: Sub-task >Reporter: Sumit Pandit > Attachments: TestCaseForInvoicePaymentReversing.patch > > > Write a Junit test case which will test following service - > 1) voidPayment > 2) cancelInvoice - To test it prepare junit test case for setInvoiceStatus > with status Id - INVOICE_CANCELED > Prepare data if require. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2695) Imporve service on when set invoice status to cancel.
[ https://issues.apache.org/jira/browse/OFBIZ-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-2695: --- Attachment: CancelInvoice.patch Here is the patch for canceling invoice. -- Regards Surya Kusumakar > Imporve service on when set invoice status to cancel. > - > > Key: OFBIZ-2695 > URL: https://issues.apache.org/jira/browse/OFBIZ-2695 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: SVN trunk >Reporter: Sumit Pandit >Priority: Minor > Attachments: CancelInvoice.patch > > > Improve service when set invoice status to Cancel, reverse accounting > transaction entries along with removal of payment application. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2694) In Accouting Payment Section The PaymentSubTabBar options are not working properly, so converting it to ftl so that desired functionality can be achieved.
[ https://issues.apache.org/jira/browse/OFBIZ-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-2694: --- Attachment: PaymentSubTabBar.patch Here is the patch for above described functionality. > In Accouting Payment Section The PaymentSubTabBar options are not working > properly, so converting it to ftl so that desired functionality can be > achieved. > --- > > Key: OFBIZ-2694 > URL: https://issues.apache.org/jira/browse/OFBIZ-2694 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Release Branch 9.04, SVN trunk >Reporter: Surya Kusumakar >Priority: Minor > Fix For: Release Branch 9.04, SVN trunk > > Attachments: PaymentSubTabBar.patch > > > On Payment overview page if we select a payment to see its view for example > navigate through following link ; > https://localhost:8443/accounting/control/paymentOverview?paymentId=demo1 > On this link all the functionality is working fine when we go for changing > the status to statusId, but in case of changing the previous status to > "PMNT_VOID" and "PMNT_CANCELLED" a JS function confirmActionLink() call on > click. > The JS can not work due the MenuWidget renders not accordingly and not > handling the such scenario. So to achieve the functionality work properly > convert the Menu to ftl, without changing its any of the functionality . -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-2694) In Accouting Payment Section The PaymentSubTabBar options are not working properly, so converting it to ftl so that desired functionality can be achieved.
In Accouting Payment Section The PaymentSubTabBar options are not working properly, so converting it to ftl so that desired functionality can be achieved. --- Key: OFBIZ-2694 URL: https://issues.apache.org/jira/browse/OFBIZ-2694 Project: OFBiz Issue Type: Bug Components: accounting Affects Versions: Release Branch 9.04, SVN trunk Reporter: Surya Kusumakar Priority: Minor Fix For: Release Branch 9.04, SVN trunk On Payment overview page if we select a payment to see its view for example navigate through following link ; https://localhost:8443/accounting/control/paymentOverview?paymentId=demo1 On this link all the functionality is working fine when we go for changing the status to statusId, but in case of changing the previous status to "PMNT_VOID" and "PMNT_CANCELLED" a JS function confirmActionLink() call on click. The JS can not work due the MenuWidget renders not accordingly and not handling the such scenario. So to achieve the functionality work properly convert the Menu to ftl, without changing its any of the functionality . -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2685) Allow user, ability to void a Payment.
[ https://issues.apache.org/jira/browse/OFBIZ-2685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-2685: --- Attachment: VoidPayment.patch Hello Sumit , Here is the patch for the functionality described above. -- Regards Surya Kusumakar > Allow user, ability to void a Payment. > -- > > Key: OFBIZ-2685 > URL: https://issues.apache.org/jira/browse/OFBIZ-2685 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: SVN trunk >Reporter: Sumit Pandit >Priority: Minor > Attachments: VoidPayment.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2051) Changing controller request to refer to simple method files by component:// url instead of classpath resource location
[ https://issues.apache.org/jira/browse/OFBIZ-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648961#action_12648961 ] Surya Kusumakar commented on OFBIZ-2051: Hello Rishi, I tried doing it the same way as you said but it could not find the simple map processor when i tried to pass the simple map-processor location as component specific path i.e component://url. -- Regards Surya Kusumakar > Changing controller request to refer to simple method files by component:// > url instead of classpath resource location > -- > > Key: OFBIZ-2051 > URL: https://issues.apache.org/jira/browse/OFBIZ-2051 > Project: OFBiz > Issue Type: Improvement > Components: ecommerce, order, party >Reporter: Surya Kusumakar >Assignee: Vikas Mayur >Priority: Minor > Attachments: EcommerceScriptDirectoryPathChanged.patch > > > Remove script directory from classpath and changing controller request to > refer to simple method files by component:// url instead of classpath > resource location.This way project would be less class path dependent. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2051) Changing controller request to refer to simple method files by component:// url instead of classpath resource location
[ https://issues.apache.org/jira/browse/OFBIZ-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-2051: --- Attachment: EcommerceScriptDirectoryPathChanged.patch Made changes in controller.xml of ecommerce ,changed the path of simple method files , groovy files from class path resource location to component://url. Also changed the path of ftl files in Data files. -- Regards Surya Kusumakar > Changing controller request to refer to simple method files by component:// > url instead of classpath resource location > -- > > Key: OFBIZ-2051 > URL: https://issues.apache.org/jira/browse/OFBIZ-2051 > Project: OFBiz > Issue Type: Improvement > Components: ecommerce, order, party >Reporter: Surya Kusumakar >Priority: Minor > Attachments: EcommerceScriptDirectoryPathChanged.patch > > > Remove script directory from classpath and changing controller request to > refer to simple method files by component:// url instead of classpath > resource location.This way project would be less class path dependent. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-2051) Changing controller request to refer to simple method files by component:// url instead of classpath resource location
Changing controller request to refer to simple method files by component:// url instead of classpath resource location -- Key: OFBIZ-2051 URL: https://issues.apache.org/jira/browse/OFBIZ-2051 Project: OFBiz Issue Type: Improvement Components: ecommerce, order, party Reporter: Surya Kusumakar Priority: Minor Remove script directory from classpath and changing controller request to refer to simple method files by component:// url instead of classpath resource location.This way project would be less class path dependent. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2043) New profile pages and One page checkout should have state field should be optional if no associated states wrt country exists.
[ https://issues.apache.org/jira/browse/OFBIZ-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-2043: --- Attachment: UpdatedShipToCountryInNewProfile.patch Made changes in New Profile page .Added function copyShipToCountryToBillToCountry() in profile.js and also made minor changes in EditShipToAddress.ftl , OnePageCheckOut.ftl , NewCustomer.ftl and geoAutoCompletor.js. -- Regards Surya Kusumakar > New profile pages and One page checkout should have state field should be > optional if no associated states wrt country exists. > -- > > Key: OFBIZ-2043 > URL: https://issues.apache.org/jira/browse/OFBIZ-2043 > Project: OFBiz > Issue Type: Improvement > Components: ecommerce >Reporter: Rishi Solanki >Assignee: Vikas Mayur >Priority: Minor > Attachments: AssociatedStateListForSelectedCountry.patch, > AssociatedStateListForSelectedCountry.patch, > AssociatedStateListForSelectedCountry.patch, > UpdatedShipToCountryInNewProfile.patch > > > To Do : > -- Go to OnePageCheckout.ftl and change accordingly so that if No state list > returns then hide the states select box through checkoutProcess.js. > -- Do same for the NewCustomer.ftl and profile.js > -- ManageAddress.ftl and profile.js > -- In the same file "ManageAddress.ftl" on other forms as well. > Regards > -- > Rishi Solanki -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2043) New profile pages and One page checkout should have state field should be optional if no associated states wrt country exists.
[ https://issues.apache.org/jira/browse/OFBIZ-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-2043: --- Attachment: AssociatedStateListForSelectedCountry.patch > New profile pages and One page checkout should have state field should be > optional if no associated states wrt country exists. > -- > > Key: OFBIZ-2043 > URL: https://issues.apache.org/jira/browse/OFBIZ-2043 > Project: OFBiz > Issue Type: Improvement > Components: ecommerce >Reporter: Rishi Solanki >Priority: Minor > Attachments: AssociatedStateListForSelectedCountry.patch, > AssociatedStateListForSelectedCountry.patch, > AssociatedStateListForSelectedCountry.patch > > > To Do : > -- Go to OnePageCheckout.ftl and change accordingly so that if No state list > returns then hide the states select box through checkoutProcess.js. > -- Do same for the NewCustomer.ftl and profile.js > -- ManageAddress.ftl and profile.js > -- In the same file "ManageAddress.ftl" on other forms as well. > Regards > -- > Rishi Solanki -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2043) New profile pages and One page checkout should have state field should be optional if no associated states wrt country exists.
[ https://issues.apache.org/jira/browse/OFBIZ-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-2043: --- Attachment: AssociatedStateListForSelectedCountry.patch Replaced the deprecated "if_exists" ,"exists" and "default" built-ins in all the ftls . -- Surya Kusumakar Onima Kasliwal Kirti Dhakad > New profile pages and One page checkout should have state field should be > optional if no associated states wrt country exists. > -- > > Key: OFBIZ-2043 > URL: https://issues.apache.org/jira/browse/OFBIZ-2043 > Project: OFBiz > Issue Type: Improvement > Components: ecommerce >Reporter: Rishi Solanki >Priority: Minor > Attachments: AssociatedStateListForSelectedCountry.patch, > AssociatedStateListForSelectedCountry.patch > > > To Do : > -- Go to OnePageCheckout.ftl and change accordingly so that if No state list > returns then hide the states select box through checkoutProcess.js. > -- Do same for the NewCustomer.ftl and profile.js > -- ManageAddress.ftl and profile.js > -- In the same file "ManageAddress.ftl" on other forms as well. > Regards > -- > Rishi Solanki -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2043) New profile pages and One page checkout should have state field should be optional if no associated states wrt country exists.
[ https://issues.apache.org/jira/browse/OFBIZ-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647203#action_12647203 ] Surya Kusumakar commented on OFBIZ-2043: Sumit, Thank you for your suggestion we are working on it .After going through this link we have seen that exists and default is also deprecated so, we will replace all three of them. Regards Surya Kusumakar Onima Kasliwal Kirti Dhakad > New profile pages and One page checkout should have state field should be > optional if no associated states wrt country exists. > -- > > Key: OFBIZ-2043 > URL: https://issues.apache.org/jira/browse/OFBIZ-2043 > Project: OFBiz > Issue Type: Improvement > Components: ecommerce >Reporter: Rishi Solanki >Priority: Minor > Attachments: AssociatedStateListForSelectedCountry.patch > > > To Do : > -- Go to OnePageCheckout.ftl and change accordingly so that if No state list > returns then hide the states select box through checkoutProcess.js. > -- Do same for the NewCustomer.ftl and profile.js > -- ManageAddress.ftl and profile.js > -- In the same file "ManageAddress.ftl" on other forms as well. > Regards > -- > Rishi Solanki -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2043) New profile pages and One page checkout should have state field should be optional if no associated states wrt country exists.
[ https://issues.apache.org/jira/browse/OFBIZ-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-2043: --- Attachment: AssociatedStateListForSelectedCountry.patch Worked on 1)Create Profile 2)Edit Profile 3)View Profile 4)Manage Addresses. 5)Checkout Process Handled the special case of getting associated state list "No Sate Province exists :_NA_" in case of country with no states by hiding the state select box .Also created generic function getAssociatedStateList() for getting state list according to the selected country which is being used by all the above cases. Thanks to Rishi Solanki . -- Surya Kusumakar Onima Kasliwal Kirti Dhakad > New profile pages and One page checkout should have state field should be > optional if no associated states wrt country exists. > -- > > Key: OFBIZ-2043 > URL: https://issues.apache.org/jira/browse/OFBIZ-2043 > Project: OFBiz > Issue Type: Improvement > Components: ecommerce >Reporter: Rishi Solanki >Priority: Minor > Attachments: AssociatedStateListForSelectedCountry.patch > > > To Do : > -- Go to OnePageCheckout.ftl and change accordingly so that if No state list > returns then hide the states select box through checkoutProcess.js. > -- Do same for the NewCustomer.ftl and profile.js > -- ManageAddress.ftl and profile.js > -- In the same file "ManageAddress.ftl" on other forms as well. > Regards > -- > Rishi Solanki -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2012) On change quantity to zero randomly no itemes have been deleted from cart in One Page Check out process.
[ https://issues.apache.org/jira/browse/OFBIZ-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-2012: --- Attachment: RemoveItems.patch Made changes in removeItem() as well in cartItemQtyChanged() functions of checkoutProcess.js 1)Remove Items according to to removeId(remove_) and qtyId(qty_). 2)When quantity is equal to zero then it removes element from cart. Thanks to Rishi for his support. Surya Kusumakar > On change quantity to zero randomly no itemes have been deleted from cart in > One Page Check out process. > > > Key: OFBIZ-2012 > URL: https://issues.apache.org/jira/browse/OFBIZ-2012 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Reporter: Rishi Solanki >Priority: Minor > Attachments: RemoveItems.patch > > > To regenerate the error : > Add more than 3 product to cart then change individual qty to 0. Not in > serial First delete the 2nd product and then 3rd. > Here you will get the problem of not deleting the product from cart from the > 2nd time. You may check it by refreshing the page. > Solution : > When you click on remove item link it will call the function removeItem of > chekoutProcess.js. It will work fine for it. Now you need to one thing call > the same function when you get the zero as quantity. > Finally you need some customization in the removeItem as well in > cartItemQtyChanged. > Regards > -- > Rishi Solanki -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2000) Added check availability functionality on new create profile page of e commerce.
[ https://issues.apache.org/jira/browse/OFBIZ-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-2000: --- Attachment: CheckAvailUserName.patch Did the required changes in service checkAvailableUsername. --- Harsha Chadhar Surya Kusumakar Onima Kasliwal Kirti Dhakad > Added check availability functionality on new create profile page of e > commerce. > > > Key: OFBIZ-2000 > URL: https://issues.apache.org/jira/browse/OFBIZ-2000 > Project: OFBiz > Issue Type: New Feature > Components: ecommerce >Reporter: Rishi Solanki >Priority: Minor > Attachments: CheckAvailUserName.patch, CheckAvailUserName.patch, > CheckAvailUserName.patch, CheckAvailUserName.patch > > > After adding this functionality while creating a profile from e commerce new > profile pages, user will be able to check his/her selected userLoginId is > availabel or not. Instead after submitting the whole form can check it just > by clicking on a check availability link. For this implementation can use > Ajax.request for submitting the user name and finally getting back the error > list from the server. If got the error appear it else hide. > Affected files for this feature are ; > CustomerEvents.xml > ecommerce > profile.js ---> ecommerce > NewCustomer.ftl ---> ecommerce (for new one) > Regards > - Rishi Solanki -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2000) Added check availability functionality on new create profile page of e commerce.
[ https://issues.apache.org/jira/browse/OFBIZ-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-2000: --- Attachment: CheckAvailUserName.patch Did the required changes. Surya Kusumakar Kirti Dhakad Harsha Chadhar Onima Kasliwal > Added check availability functionality on new create profile page of e > commerce. > > > Key: OFBIZ-2000 > URL: https://issues.apache.org/jira/browse/OFBIZ-2000 > Project: OFBiz > Issue Type: New Feature > Components: ecommerce >Reporter: Rishi Solanki >Priority: Minor > Attachments: CheckAvailUserName.patch, CheckAvailUserName.patch, > CheckAvailUserName.patch > > > After adding this functionality while creating a profile from e commerce new > profile pages, user will be able to check his/her selected userLoginId is > availabel or not. Instead after submitting the whole form can check it just > by clicking on a check availability link. For this implementation can use > Ajax.request for submitting the user name and finally getting back the error > list from the server. If got the error appear it else hide. > Affected files for this feature are ; > CustomerEvents.xml > ecommerce > profile.js ---> ecommerce > NewCustomer.ftl ---> ecommerce (for new one) > Regards > - Rishi Solanki -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2000) Added check availability functionality on new create profile page of e commerce.
[ https://issues.apache.org/jira/browse/OFBIZ-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-2000: --- Attachment: CheckAvailUserName.patch Implemented the User Availability Check using Jsonservice instead of Jsonsimple.Also removed the check availability button and implemented the check functionality on "change" Event instead of "click" Event. Thanks Rishi for his support. __ Onima Kasliwal Kirti Dhakad Surya Kusumakar Harsha Chadhar. > Added check availability functionality on new create profile page of e > commerce. > > > Key: OFBIZ-2000 > URL: https://issues.apache.org/jira/browse/OFBIZ-2000 > Project: OFBiz > Issue Type: New Feature > Components: ecommerce >Reporter: Rishi Solanki >Priority: Minor > Attachments: CheckAvailUserName.patch, CheckAvailUserName.patch > > > After adding this functionality while creating a profile from e commerce new > profile pages, user will be able to check his/her selected userLoginId is > availabel or not. Instead after submitting the whole form can check it just > by clicking on a check availability link. For this implementation can use > Ajax.request for submitting the user name and finally getting back the error > list from the server. If got the error appear it else hide. > Affected files for this feature are ; > CustomerEvents.xml > ecommerce > profile.js ---> ecommerce > NewCustomer.ftl ---> ecommerce (for new one) > Regards > - Rishi Solanki -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2000) Added check availability functionality on new create profile page of e commerce.
[ https://issues.apache.org/jira/browse/OFBIZ-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-2000: --- Comment: was deleted > Added check availability functionality on new create profile page of e > commerce. > > > Key: OFBIZ-2000 > URL: https://issues.apache.org/jira/browse/OFBIZ-2000 > Project: OFBiz > Issue Type: New Feature > Components: ecommerce >Reporter: Rishi Solanki >Priority: Minor > Attachments: CheckAvailUserName.patch > > > After adding this functionality while creating a profile from e commerce new > profile pages, user will be able to check his/her selected userLoginId is > availabel or not. Instead after submitting the whole form can check it just > by clicking on a check availability link. For this implementation can use > Ajax.request for submitting the user name and finally getting back the error > list from the server. If got the error appear it else hide. > Affected files for this feature are ; > CustomerEvents.xml > ecommerce > profile.js ---> ecommerce > NewCustomer.ftl ---> ecommerce (for new one) > Regards > - Rishi Solanki -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2000) Added check availability functionality on new create profile page of e commerce.
[ https://issues.apache.org/jira/browse/OFBIZ-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-2000: --- Attachment: (was: CheckAvailableUserName.patch) > Added check availability functionality on new create profile page of e > commerce. > > > Key: OFBIZ-2000 > URL: https://issues.apache.org/jira/browse/OFBIZ-2000 > Project: OFBiz > Issue Type: New Feature > Components: ecommerce >Reporter: Rishi Solanki >Priority: Minor > Attachments: CheckAvailUserName.patch > > > After adding this functionality while creating a profile from e commerce new > profile pages, user will be able to check his/her selected userLoginId is > availabel or not. Instead after submitting the whole form can check it just > by clicking on a check availability link. For this implementation can use > Ajax.request for submitting the user name and finally getting back the error > list from the server. If got the error appear it else hide. > Affected files for this feature are ; > CustomerEvents.xml > ecommerce > profile.js ---> ecommerce > NewCustomer.ftl ---> ecommerce (for new one) > Regards > - Rishi Solanki -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2000) Added check availability functionality on new create profile page of e commerce.
[ https://issues.apache.org/jira/browse/OFBIZ-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surya Kusumakar updated OFBIZ-2000: --- Attachment: CheckAvailableUserName.patch Implemented the User Availability Check using Jsonservice instead of Jsonsimple.Also removed the check availability button and implemented the check functionality on "change" Event instead of "click" Event. Thanks to Rishi for his support. __ Onima, Kirti, Surya and Harsha. > Added check availability functionality on new create profile page of e > commerce. > > > Key: OFBIZ-2000 > URL: https://issues.apache.org/jira/browse/OFBIZ-2000 > Project: OFBiz > Issue Type: New Feature > Components: ecommerce >Reporter: Rishi Solanki >Priority: Minor > Attachments: CheckAvailableUserName.patch, CheckAvailUserName.patch > > > After adding this functionality while creating a profile from e commerce new > profile pages, user will be able to check his/her selected userLoginId is > availabel or not. Instead after submitting the whole form can check it just > by clicking on a check availability link. For this implementation can use > Ajax.request for submitting the user name and finally getting back the error > list from the server. If got the error appear it else hide. > Affected files for this feature are ; > CustomerEvents.xml > ecommerce > profile.js ---> ecommerce > NewCustomer.ftl ---> ecommerce (for new one) > Regards > - Rishi Solanki -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2000) Added check availability functionality on new create profile page of e commerce.
[ https://issues.apache.org/jira/browse/OFBIZ-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] surya kusumakar updated OFBIZ-2000: --- Attachment: CheckAvailUserName.patch To implement the functionality on Ecommerce profile pages so that user can check the availability of username he/she has entered on CreateProfilePage using Ajax request. Special thanks to Rishi Solanki . --- Kirti Dhakad Surya Kusumakar Onima Kasliwal > Added check availability functionality on new create profile page of e > commerce. > > > Key: OFBIZ-2000 > URL: https://issues.apache.org/jira/browse/OFBIZ-2000 > Project: OFBiz > Issue Type: New Feature > Components: ecommerce >Reporter: Rishi Solanki >Priority: Minor > Attachments: CheckAvailUserName.patch > > > After adding this functionality while creating a profile from e commerce new > profile pages, user will be able to check his/her selected userLoginId is > availabel or not. Instead after submitting the whole form can check it just > by clicking on a check availability link. For this implementation can use > Ajax.request for submitting the user name and finally getting back the error > list from the server. If got the error appear it else hide. > Affected files for this feature are ; > CustomerEvents.xml > ecommerce > profile.js ---> ecommerce > NewCustomer.ftl ---> ecommerce (for new one) > Regards > - Rishi Solanki -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1963) Added support for migrating FacilityRole to FacilityParty
[ https://issues.apache.org/jira/browse/OFBIZ-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] surya kusumakar updated OFBIZ-1963: --- Attachment: (was: LatestUpdatedFacilityParty.patch) > Added support for migrating FacilityRole to FacilityParty > - > > Key: OFBIZ-1963 > URL: https://issues.apache.org/jira/browse/OFBIZ-1963 > Project: OFBiz > Issue Type: Improvement > Components: product >Reporter: surya kusumakar >Assignee: Ashish Vijaywargiya >Priority: Minor > Attachments: LatestUpdatedFacilityParty.patch, > LatestUpdatedFacilityParty.patch > > > 1) Write a migrate service to upgrade existing data from the FacilityRole > entity to the new FacilityParty entity. For these, changes has been made in > UI as well. > 2) The FacilityRole entity has been deprecated and new entity FacilityParty > is created for these changes has been made in UI and entitymodel.xml files. > 3) Also add fromDate and thruDate fields to maintain records of FacilityRole > entity. > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1963) Added support for migrating FacilityRole to FacilityParty
[ https://issues.apache.org/jira/browse/OFBIZ-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] surya kusumakar updated OFBIZ-1963: --- Attachment: LatestUpdatedFacilityParty.patch > Added support for migrating FacilityRole to FacilityParty > - > > Key: OFBIZ-1963 > URL: https://issues.apache.org/jira/browse/OFBIZ-1963 > Project: OFBiz > Issue Type: Improvement > Components: product >Reporter: surya kusumakar >Assignee: Ashish Vijaywargiya >Priority: Minor > Attachments: LatestUpdatedFacilityParty.patch, > LatestUpdatedFacilityParty.patch, LatestUpdatedFacilityParty.patch > > > 1) Write a migrate service to upgrade existing data from the FacilityRole > entity to the new FacilityParty entity. For these, changes has been made in > UI as well. > 2) The FacilityRole entity has been deprecated and new entity FacilityParty > is created for these changes has been made in UI and entitymodel.xml files. > 3) Also add fromDate and thruDate fields to maintain records of FacilityRole > entity. > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1963) Added support for migrating FacilityRole to FacilityParty
[ https://issues.apache.org/jira/browse/OFBIZ-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] surya kusumakar updated OFBIZ-1963: --- Attachment: (was: LatestUpdatedFacilityParty.patch) > Added support for migrating FacilityRole to FacilityParty > - > > Key: OFBIZ-1963 > URL: https://issues.apache.org/jira/browse/OFBIZ-1963 > Project: OFBiz > Issue Type: Improvement > Components: product >Reporter: surya kusumakar >Assignee: Ashish Vijaywargiya >Priority: Minor > Attachments: LatestUpdatedFacilityParty.patch, > LatestUpdatedFacilityParty.patch, LatestUpdatedFacilityParty.patch > > > 1) Write a migrate service to upgrade existing data from the FacilityRole > entity to the new FacilityParty entity. For these, changes has been made in > UI as well. > 2) The FacilityRole entity has been deprecated and new entity FacilityParty > is created for these changes has been made in UI and entitymodel.xml files. > 3) Also add fromDate and thruDate fields to maintain records of FacilityRole > entity. > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1963) Added support for migrating FacilityRole to FacilityParty
[ https://issues.apache.org/jira/browse/OFBIZ-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] surya kusumakar updated OFBIZ-1963: --- Attachment: LatestUpdatedFacilityParty.patch This patch contains following changes : 1)In FacilityForms fromDate is added in deletelink as it was showing error when we delete FacilityParty. 2)Changes made in migrateFacilityRole service , now it is creating a record in PartyRole entity . Thanks. Surya Kusumakar > Added support for migrating FacilityRole to FacilityParty > - > > Key: OFBIZ-1963 > URL: https://issues.apache.org/jira/browse/OFBIZ-1963 > Project: OFBiz > Issue Type: Improvement > Components: product >Reporter: surya kusumakar >Assignee: Ashish Vijaywargiya >Priority: Minor > Attachments: LatestUpdatedFacilityParty.patch, > LatestUpdatedFacilityParty.patch, LatestUpdatedFacilityParty.patch > > > 1) Write a migrate service to upgrade existing data from the FacilityRole > entity to the new FacilityParty entity. For these, changes has been made in > UI as well. > 2) The FacilityRole entity has been deprecated and new entity FacilityParty > is created for these changes has been made in UI and entitymodel.xml files. > 3) Also add fromDate and thruDate fields to maintain records of FacilityRole > entity. > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (OFBIZ-1963) Added support for migrating FacilityRole to FacilityParty
[ https://issues.apache.org/jira/browse/OFBIZ-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633204#action_12633204 ] kusumakarsurya edited comment on OFBIZ-1963 at 9/22/08 3:43 AM: - Hello Ashish, This is updated patch with the required modifications. Thanks Surya . was (Author: kusumakarsurya): Hello Ashish, This is updated with the required modifications. Thanks Surya . > Added support for migrating FacilityRole to FacilityParty > - > > Key: OFBIZ-1963 > URL: https://issues.apache.org/jira/browse/OFBIZ-1963 > Project: OFBiz > Issue Type: Improvement > Components: product >Reporter: surya kusumakar >Assignee: Ashish Vijaywargiya >Priority: Minor > Attachments: LatestUpdatedFacilityParty.patch, > LatestUpdatedFacilityParty.patch > > > 1) Write a migrate service to upgrade existing data from the FacilityRole > entity to the new FacilityParty entity. For these, changes has been made in > UI as well. > 2) The FacilityRole entity has been deprecated and new entity FacilityParty > is created for these changes has been made in UI and entitymodel.xml files. > 3) Also add fromDate and thruDate fields to maintain records of FacilityRole > entity. > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1963) Added support for migrating FacilityRole to FacilityParty
[ https://issues.apache.org/jira/browse/OFBIZ-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] surya kusumakar updated OFBIZ-1963: --- Attachment: LatestUpdatedFacilityParty.patch Hello Ashish, This is updated with the required modifications. Thanks Surya . > Added support for migrating FacilityRole to FacilityParty > - > > Key: OFBIZ-1963 > URL: https://issues.apache.org/jira/browse/OFBIZ-1963 > Project: OFBiz > Issue Type: Improvement > Components: product >Reporter: surya kusumakar >Assignee: Ashish Vijaywargiya >Priority: Minor > Attachments: LatestUpdatedFacilityParty.patch, > LatestUpdatedFacilityParty.patch > > > 1) Write a migrate service to upgrade existing data from the FacilityRole > entity to the new FacilityParty entity. For these, changes has been made in > UI as well. > 2) The FacilityRole entity has been deprecated and new entity FacilityParty > is created for these changes has been made in UI and entitymodel.xml files. > 3) Also add fromDate and thruDate fields to maintain records of FacilityRole > entity. > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1963) Added support for migrating FacilityRole to FacilityParty
[ https://issues.apache.org/jira/browse/OFBIZ-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] surya kusumakar updated OFBIZ-1963: --- Attachment: LatestUpdatedFacilityParty.patch This patch contains implementation of the description given above. > Added support for migrating FacilityRole to FacilityParty > - > > Key: OFBIZ-1963 > URL: https://issues.apache.org/jira/browse/OFBIZ-1963 > Project: OFBiz > Issue Type: Improvement > Components: product >Reporter: surya kusumakar >Priority: Minor > Attachments: LatestUpdatedFacilityParty.patch > > > 1) Write a migrate service to upgrade existing data from the FacilityRole > entity to the new FacilityParty entity. For these, changes has been made in > UI as well. > 2) The FacilityRole entity has been deprecated and new entity FacilityParty > is created for these changes has been made in UI and entitymodel.xml files. > 3) Also add fromDate and thruDate fields to maintain records of FacilityRole > entity. > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1963) Added support for migrating FacilityRole to FacilityParty
[ https://issues.apache.org/jira/browse/OFBIZ-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] surya kusumakar updated OFBIZ-1963: --- Priority: Minor (was: Major) > Added support for migrating FacilityRole to FacilityParty > - > > Key: OFBIZ-1963 > URL: https://issues.apache.org/jira/browse/OFBIZ-1963 > Project: OFBiz > Issue Type: Improvement > Components: product >Reporter: surya kusumakar >Priority: Minor > Attachments: LatestUpdatedFacilityParty.patch > > > 1) Write a migrate service to upgrade existing data from the FacilityRole > entity to the new FacilityParty entity. For these, changes has been made in > UI as well. > 2) The FacilityRole entity has been deprecated and new entity FacilityParty > is created for these changes has been made in UI and entitymodel.xml files. > 3) Also add fromDate and thruDate fields to maintain records of FacilityRole > entity. > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-1963) Added support for migrating FacilityRole to FacilityParty
Added support for migrating FacilityRole to FacilityParty - Key: OFBIZ-1963 URL: https://issues.apache.org/jira/browse/OFBIZ-1963 Project: OFBiz Issue Type: Improvement Components: product Reporter: surya kusumakar 1) Write a migrate service to upgrade existing data from the FacilityRole entity to the new FacilityParty entity. For these, changes has been made in UI as well. 2) The FacilityRole entity has been deprecated and new entity FacilityParty is created for these changes has been made in UI and entitymodel.xml files. 3) Also add fromDate and thruDate fields to maintain records of FacilityRole entity. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
