[jira] [Commented] (OFBIZ-10439) Entity Maintenance / FindGeneric result list misses first data set
[ https://issues.apache.org/jira/browse/OFBIZ-10439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538411#comment-16538411 ] Aman Agrawal commented on OFBIZ-10439: -- Hi [~mbrohl], I ran the steps mentioned above and found that in both cases 5 records are listed. So, can you please share more details on this? > Entity Maintenance / FindGeneric result list misses first data set > -- > > Key: OFBIZ-10439 > URL: https://issues.apache.org/jira/browse/OFBIZ-10439 > Project: OFBiz > Issue Type: Bug > Components: framework/webtools >Affects Versions: Trunk >Reporter: Michael Brohl >Priority: Major > > Steps to reproduce on the demo instance for trunk: > # [https://demo-trunk.ofbiz.apache.org/webtools/control/EntitySQLProcessor:] > select * from ORDER_HEADER -> shows 6 rows > # > [https://demo-trunk.ofbiz.apache.org/webtools/control/FindGeneric?entityName=OrderHeader&noConditionFind=Y] > -> shows 5 rows, the first one with orderId DEMO10090 is missing > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10442) Blank field appears in drop-down where the fields are not pre-populated
[ https://issues.apache.org/jira/browse/OFBIZ-10442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538404#comment-16538404 ] Aman Agrawal commented on OFBIZ-10442: -- Hi Archana, This is the default behavior of select box. If a value is selected then that value is highlighted otherwise blank or default option is highlighted. So, IMO this is not a valid issue. > Blank field appears in drop-down where the fields are not pre-populated > --- > > Key: OFBIZ-10442 > URL: https://issues.apache.org/jira/browse/OFBIZ-10442 > Project: OFBiz > Issue Type: Bug > Environment: > https://demo-trunk.ofbiz.apache.org/catalog/control/FindSubscription >Reporter: Archana Asthana >Priority: Major > Attachments: Highlighter.png, PopulatedHighlighter.png > > > Steps to regenerate: > 1. Open https://demo-trunk.ofbiz.apache.org/catalog/control/FindSubscription > 2. On Find Subscription screen, check all the dropdowns one by one. > Actual: > The highlighter in the drop-down is not consistent. > If the fields are prepopulated, they are highlighted in blue. > If the field is not prepopulated the blank field is highlighted in the > drop-down. > Check Subscription Resource ID, Subscription Type, and Automatic Extend > Images are attached for reference. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10441) Exception Error renders while removing the Shipment Method
[ https://issues.apache.org/jira/browse/OFBIZ-10441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538392#comment-16538392 ] Aman Agrawal commented on OFBIZ-10441: -- Hi Archana, This is a type data. After creating a new shipment method type data, it is possible to delete it. But, once you start using the shipment method data, the system doesn't allow us to delete the data. So, IMO this is not a valid issue. > Exception Error renders while removing the Shipment Method > -- > > Key: OFBIZ-10441 > URL: https://issues.apache.org/jira/browse/OFBIZ-10441 > Project: OFBiz > Issue Type: Bug > Environment: Open > https://demo-trunk.ofbiz.apache.org/catalog/control/deleteShipmentMethodType >Reporter: Archana Asthana >Priority: Major > Attachments: ShipmentMethodRemovalError.png > > > Steps to Regenerate: > 1. Open > https://demo-trunk.ofbiz.apache.org/catalog/control/deleteShipmentMethodType > 2. Select any Shipment Method Type ID > 3. Click Remove button > Actual: > Exception Error is rendered on the screen. > Image is attached for reference -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10391) Make accounting entry configurable
[ https://issues.apache.org/jira/browse/OFBIZ-10391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16491530#comment-16491530 ] Aman Agrawal commented on OFBIZ-10391: -- Thanks Arun for reviewing. I have updated the patch in which default accounting is enabled. Accounting gets disabled when flag is set to 'N'. > Make accounting entry configurable > -- > > Key: OFBIZ-10391 > URL: https://issues.apache.org/jira/browse/OFBIZ-10391 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Reporter: Aman Agrawal >Priority: Major > Fix For: Trunk > > Attachments: OFBIZ-10391.patch > > > In current flow, if we want to disable the accounting then we need to disable > the set of seca's. We don't have any configurable setting to disable > accounting. > We can manage this by adding a new field 'enableAccounting' in the > 'PartyAcctgPreference' entity. Accounting transaction entries will be > entertained accordingly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10391) Make accounting entry configurable
[ https://issues.apache.org/jira/browse/OFBIZ-10391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Agrawal updated OFBIZ-10391: - Attachment: (was: OFBIZ-10391.patch) > Make accounting entry configurable > -- > > Key: OFBIZ-10391 > URL: https://issues.apache.org/jira/browse/OFBIZ-10391 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Reporter: Aman Agrawal >Priority: Major > Fix For: Trunk > > Attachments: OFBIZ-10391.patch > > > In current flow, if we want to disable the accounting then we need to disable > the set of seca's. We don't have any configurable setting to disable > accounting. > We can manage this by adding a new field 'enableAccounting' in the > 'PartyAcctgPreference' entity. Accounting transaction entries will be > entertained accordingly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10391) Make accounting entry configurable
[ https://issues.apache.org/jira/browse/OFBIZ-10391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Agrawal updated OFBIZ-10391: - Attachment: OFBIZ-10391.patch > Make accounting entry configurable > -- > > Key: OFBIZ-10391 > URL: https://issues.apache.org/jira/browse/OFBIZ-10391 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Reporter: Aman Agrawal >Priority: Major > Fix For: Trunk > > Attachments: OFBIZ-10391.patch > > > In current flow, if we want to disable the accounting then we need to disable > the set of seca's. We don't have any configurable setting to disable > accounting. > We can manage this by adding a new field 'enableAccounting' in the > 'PartyAcctgPreference' entity. Accounting transaction entries will be > entertained accordingly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10391) Make accounting entry configurable
[ https://issues.apache.org/jira/browse/OFBIZ-10391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Agrawal reassigned OFBIZ-10391: Assignee: (was: Aman Agrawal) > Make accounting entry configurable > -- > > Key: OFBIZ-10391 > URL: https://issues.apache.org/jira/browse/OFBIZ-10391 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Reporter: Aman Agrawal >Priority: Major > Fix For: Trunk > > Attachments: OFBIZ-10391.patch > > > In current flow, if we want to disable the accounting then we need to disable > the set of seca's. We don't have any configurable setting to disable > accounting. > We can manage this by adding a new field 'enableAccounting' in the > 'PartyAcctgPreference' entity. Accounting transaction entries will be > entertained accordingly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10391) Make accounting entry configurable
[ https://issues.apache.org/jira/browse/OFBIZ-10391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16467145#comment-16467145 ] Aman Agrawal commented on OFBIZ-10391: -- Hello, In this, I have added one field 'enableAccounting' in the PartyAcctgPreference entity. By this field added a check whether accounting is enable or not in the services used to create accounting transaction entries. I have uploaded the patch for the same. > Make accounting entry configurable > -- > > Key: OFBIZ-10391 > URL: https://issues.apache.org/jira/browse/OFBIZ-10391 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Reporter: Aman Agrawal >Assignee: Aman Agrawal >Priority: Major > Fix For: Trunk > > Attachments: OFBIZ-10391.patch > > > In current flow, if we want to disable the accounting then we need to disable > the set of seca's. We don't have any configurable setting to disable > accounting. > We can manage this by adding a new field 'enableAccounting' in the > 'PartyAcctgPreference' entity. Accounting transaction entries will be > entertained accordingly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10391) Make accounting entry configurable
[ https://issues.apache.org/jira/browse/OFBIZ-10391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Agrawal updated OFBIZ-10391: - Attachment: OFBIZ-10391.patch > Make accounting entry configurable > -- > > Key: OFBIZ-10391 > URL: https://issues.apache.org/jira/browse/OFBIZ-10391 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Reporter: Aman Agrawal >Assignee: Aman Agrawal >Priority: Major > Fix For: Trunk > > Attachments: OFBIZ-10391.patch > > > In current flow, if we want to disable the accounting then we need to disable > the set of seca's. We don't have any configurable setting to disable > accounting. > We can manage this by adding a new field 'enableAccounting' in the > 'PartyAcctgPreference' entity. Accounting transaction entries will be > entertained accordingly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10391) Make accounting entry configurable
Aman Agrawal created OFBIZ-10391: Summary: Make accounting entry configurable Key: OFBIZ-10391 URL: https://issues.apache.org/jira/browse/OFBIZ-10391 Project: OFBiz Issue Type: Improvement Components: ALL APPLICATIONS Reporter: Aman Agrawal Assignee: Aman Agrawal Fix For: Trunk In current flow, if we want to disable the accounting then we need to disable the set of seca's. We don't have any configurable setting to disable accounting. We can manage this by adding a new field 'enableAccounting' in the 'PartyAcctgPreference' entity. Accounting transaction entries will be entertained accordingly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10006) Exception Error rendering on all View Category pages
[ https://issues.apache.org/jira/browse/OFBIZ-10006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16360585#comment-16360585 ] Aman Agrawal commented on OFBIZ-10006: -- Thanks [~jacques.le.roux] for your feedback. We will cover this issue in OFBIZ-10219 > Exception Error rendering on all View Category pages > > > Key: OFBIZ-10006 > URL: https://issues.apache.org/jira/browse/OFBIZ-10006 > Project: OFBiz > Issue Type: Bug > Components: ecommerce > Environment: > https://demo-trunk.ofbiz.apache.org/ecommerce/control/main >Reporter: Archana Asthana >Assignee: Jacques Le Roux >Priority: Major > Attachments: ExceptionErrorOnCategory.jpg, OFBIZ-10006.patch > > > Steps to regenerate: > 1. Open https://demo-trunk.ofbiz.apache.org/ecommerce/control/main > 2. Go to Category section > 3. Click any category > Actual: > Exception Error renders -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10219) Category tree items are not rendering on ecommerce screen
Aman Agrawal created OFBIZ-10219: Summary: Category tree items are not rendering on ecommerce screen Key: OFBIZ-10219 URL: https://issues.apache.org/jira/browse/OFBIZ-10219 Project: OFBiz Issue Type: Bug Components: ecommerce Affects Versions: Trunk Reporter: Aman Agrawal Steps to regenerate: 1. Open https://demo-trunk.ofbiz.apache.org/ecommerce/control/main 2. Go to Category section 3. Click any category from the category tree. 4. Nothing happens Actual: Category items should be displayed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10170) Creating new contactMechId while it can be available in service context
[ https://issues.apache.org/jira/browse/OFBIZ-10170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16331755#comment-16331755 ] Aman Agrawal commented on OFBIZ-10170: -- Thanks Anil and Deepak for your feedback. > Creating new contactMechId while it can be available in service context > --- > > Key: OFBIZ-10170 > URL: https://issues.apache.org/jira/browse/OFBIZ-10170 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: Trunk, Release Branch 16.11 >Reporter: Aman Agrawal >Assignee: Aman Agrawal >Priority: Major > Attachments: OFBIZ-10170-16.12.patch, OFBIZ-10170.patch > > > In applications/party/minilang/contact/ContactMechServices.xml file. > Service name: > # createPostalAddress > # createTelecomNumber > In both of these services, when we have contactMechId in parameters then no > need to create new contactMech for the same. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10170) Creating new contactMechId while it can be available in service context
[ https://issues.apache.org/jira/browse/OFBIZ-10170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16330487#comment-16330487 ] Aman Agrawal commented on OFBIZ-10170: -- Attached the patch for trunk and 16.12 versions. > Creating new contactMechId while it can be available in service context > --- > > Key: OFBIZ-10170 > URL: https://issues.apache.org/jira/browse/OFBIZ-10170 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: Trunk, Release Branch 16.11 >Reporter: Aman Agrawal >Assignee: Aman Agrawal >Priority: Major > Attachments: OFBIZ-10170-16.12.patch, OFBIZ-10170.patch > > > In applications/party/minilang/contact/ContactMechServices.xml file. > Service name: > # createPostalAddress > # createTelecomNumber > In both of these services, when we have contactMechId in parameters then no > need to create new contactMech for the same. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10170) Creating new contactMechId while it can be available in service context
[ https://issues.apache.org/jira/browse/OFBIZ-10170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Agrawal updated OFBIZ-10170: - Attachment: OFBIZ-10170-16.12.patch > Creating new contactMechId while it can be available in service context > --- > > Key: OFBIZ-10170 > URL: https://issues.apache.org/jira/browse/OFBIZ-10170 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: Trunk, Release Branch 16.11 >Reporter: Aman Agrawal >Assignee: Aman Agrawal >Priority: Major > Attachments: OFBIZ-10170-16.12.patch, OFBIZ-10170.patch > > > In applications/party/minilang/contact/ContactMechServices.xml file. > Service name: > # createPostalAddress > # createTelecomNumber > In both of these services, when we have contactMechId in parameters then no > need to create new contactMech for the same. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10170) Creating new contactMechId while it can be available in service context
[ https://issues.apache.org/jira/browse/OFBIZ-10170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Agrawal updated OFBIZ-10170: - Attachment: OFBIZ-10170.patch > Creating new contactMechId while it can be available in service context > --- > > Key: OFBIZ-10170 > URL: https://issues.apache.org/jira/browse/OFBIZ-10170 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: Trunk, Release Branch 16.11 >Reporter: Aman Agrawal >Assignee: Aman Agrawal >Priority: Major > Attachments: OFBIZ-10170.patch > > > In applications/party/minilang/contact/ContactMechServices.xml file. > Service name: > # createPostalAddress > # createTelecomNumber > In both of these services, when we have contactMechId in parameters then no > need to create new contactMech for the same. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10170) Creating new contactMechId while it can be available in service context
Aman Agrawal created OFBIZ-10170: Summary: Creating new contactMechId while it can be available in service context Key: OFBIZ-10170 URL: https://issues.apache.org/jira/browse/OFBIZ-10170 Project: OFBiz Issue Type: Bug Components: party Affects Versions: Release Branch 16.11, Trunk Reporter: Aman Agrawal Assignee: Aman Agrawal In applications/party/minilang/contact/ContactMechServices.xml file. Service name: # createPostalAddress # createTelecomNumber In both of these services, when we have contactMechId in parameters then no need to create new contactMech for the same. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (OFBIZ-8848) Search operation on ' OrderPurchaseProductSummary' entity causing exception.
[ https://issues.apache.org/jira/browse/OFBIZ-8848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16303840#comment-16303840 ] Aman Agrawal edited comment on OFBIZ-8848 at 12/26/17 2:23 PM: --- Hi Humera, IMO, this entity is used only for data fetching purpose. This entity is used to generate Purchases by Product Report from OrderPurchaseReportProduct and its working properly. Hence we can close this ticket. was (Author: aman.agrawal): Hi Pallavi, IMO, this entity is used only for data fetching purpose. This entity is used to generate Purchases by Product Report from OrderPurchaseReportProduct and its working properly. Hence we can close this ticket. > Search operation on ' OrderPurchaseProductSummary' entity causing exception. > > > Key: OFBIZ-8848 > URL: https://issues.apache.org/jira/browse/OFBIZ-8848 > Project: OFBiz > Issue Type: Bug > Components: framework/webtools >Affects Versions: Trunk >Reporter: Humera Khan > Attachments: OFBIZ-8848.patch, OrderPurchase_Actual.png, > OrderPurchase_Expected.png > > > Steps to regenerate : > 1. Go to Entity Data Maintenance in webtools. > 2. Search entity ' OrderPurchaseProductSummary'. Click on it and go to the > overview page. > 3. Click on the Find button. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-8848) Search operation on ' OrderPurchaseProductSummary' entity causing exception.
[ https://issues.apache.org/jira/browse/OFBIZ-8848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16303840#comment-16303840 ] Aman Agrawal commented on OFBIZ-8848: - Hi Pallavi, IMO, this entity is used only for data fetching purpose. This entity is used to generate Purchases by Product Report from OrderPurchaseReportProduct and its working properly. Hence we can close this ticket. > Search operation on ' OrderPurchaseProductSummary' entity causing exception. > > > Key: OFBIZ-8848 > URL: https://issues.apache.org/jira/browse/OFBIZ-8848 > Project: OFBiz > Issue Type: Bug > Components: framework/webtools >Affects Versions: Trunk >Reporter: Humera Khan > Attachments: OFBIZ-8848.patch, OrderPurchase_Actual.png, > OrderPurchase_Expected.png > > > Steps to regenerate : > 1. Go to Entity Data Maintenance in webtools. > 2. Search entity ' OrderPurchaseProductSummary'. Click on it and go to the > overview page. > 3. Click on the Find button. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-10006) Exception Error rendering on all View Category pages
[ https://issues.apache.org/jira/browse/OFBIZ-10006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Agrawal updated OFBIZ-10006: - Attachment: OFBIZ-10006.patch Changed the fetching logic for getting visualThemeResources. Instead of using getVisualThemeResources service, now using getVisualThemeFromId method. Provided patch for review. > Exception Error rendering on all View Category pages > > > Key: OFBIZ-10006 > URL: https://issues.apache.org/jira/browse/OFBIZ-10006 > Project: OFBiz > Issue Type: Bug > Components: ecommerce > Environment: > https://demo-trunk.ofbiz.apache.org/ecommerce/control/main >Reporter: Archana Asthana >Assignee: Aman Agrawal > Attachments: ExceptionErrorOnCategory.jpg, OFBIZ-10006.patch > > > Steps to regenerate: > 1. Open https://demo-trunk.ofbiz.apache.org/ecommerce/control/main > 2. Go to Category section > 3. Click any category > Actual: > Exception Error renders -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-10006) Exception Error rendering on all View Category pages
[ https://issues.apache.org/jira/browse/OFBIZ-10006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Agrawal reassigned OFBIZ-10006: Assignee: Aman Agrawal > Exception Error rendering on all View Category pages > > > Key: OFBIZ-10006 > URL: https://issues.apache.org/jira/browse/OFBIZ-10006 > Project: OFBiz > Issue Type: Bug > Components: ecommerce > Environment: > https://demo-trunk.ofbiz.apache.org/ecommerce/control/main >Reporter: Archana Asthana >Assignee: Aman Agrawal > Attachments: ExceptionErrorOnCategory.jpg > > > Steps to regenerate: > 1. Open https://demo-trunk.ofbiz.apache.org/ecommerce/control/main > 2. Go to Category section > 3. Click any category > Actual: > Exception Error renders -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-10109) Encoding issue while exporting CSV
[ https://issues.apache.org/jira/browse/OFBIZ-10109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Agrawal updated OFBIZ-10109: - Attachment: OFBIZ-10109.patch Removed the encoder for the screencsv template. Now, special characters are rendering properly. Attached the patch for review. > Encoding issue while exporting CSV > -- > > Key: OFBIZ-10109 > URL: https://issues.apache.org/jira/browse/OFBIZ-10109 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Trunk >Reporter: Aman Agrawal >Assignee: Aman Agrawal > Fix For: Trunk > > Attachments: OFBIZ-10109.patch > > > While migrating widget.properties values in ThemeData.xml, "xml" encoder is > added for template "screencsv" which was not persent in the properties file. > By this, special character are not supported in CSV file. > Steps to generate: > 1. Go to [Accounting > section|https://demo-trunk-ofbiz.apache.org:8443/accounting/control/main?externalLoginKey=EL3ee4435c-a117-4670-bc4b-c3f5d8b0c3f0]. > 2. Go to [Organization GL > Settings|https://demo-trunk-ofbiz.apache.org:8443/accounting/control/ListCompanies]. > 3. Click on accounting in [companies > section|https://demo-trunk-ofbiz.apache.org:8443/accounting/control/PartyAccountsSummary]. > 4. Click on [Reports submenu > tab|https://demo-trunk-ofbiz.apache.org:8443/accounting/control/TrialBalance?organizationPartyId=Company]. > 5. Click on Inventory Valuation report. > 6. Export report as CSV. > This is committed under revision number r1806076. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-10109) Encoding issue while exporting CSV
Aman Agrawal created OFBIZ-10109: Summary: Encoding issue while exporting CSV Key: OFBIZ-10109 URL: https://issues.apache.org/jira/browse/OFBIZ-10109 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: Trunk Reporter: Aman Agrawal Assignee: Aman Agrawal Fix For: Trunk While migrating widget.properties values in ThemeData.xml, "xml" encoder is added for template "screencsv" which was not persent in the properties file. By this, special character are not supported in CSV file. Steps to generate: 1. Go to [Accounting section|https://demo-trunk-ofbiz.apache.org:8443/accounting/control/main?externalLoginKey=EL3ee4435c-a117-4670-bc4b-c3f5d8b0c3f0]. 2. Go to [Organization GL Settings|https://demo-trunk-ofbiz.apache.org:8443/accounting/control/ListCompanies]. 3. Click on accounting in [companies section|https://demo-trunk-ofbiz.apache.org:8443/accounting/control/PartyAccountsSummary]. 4. Click on [Reports submenu tab|https://demo-trunk-ofbiz.apache.org:8443/accounting/control/TrialBalance?organizationPartyId=Company]. 5. Click on Inventory Valuation report. 6. Export report as CSV. This is committed under revision number r1806076. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-10007) Party Classification Groups are not listing on FindParty screen.
[ https://issues.apache.org/jira/browse/OFBIZ-10007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Agrawal updated OFBIZ-10007: - Attachment: OFBIZ-10007.patch Fixed issue in which classification is not listed in the dropdown. First value is undefined in the list, this is because of asmSelect Jquery which will cover in another ticket. > Party Classification Groups are not listing on FindParty screen. > > > Key: OFBIZ-10007 > URL: https://issues.apache.org/jira/browse/OFBIZ-10007 > Project: OFBiz > Issue Type: Bug > Components: party >Reporter: Sonal Patwari >Assignee: Aman Agrawal > Attachments: FindPartyPageClassificationGroupsNotListing.png, > OFBIZ-10007.patch > > > - Navigate to [Find > Party|https://demo-trunk.ofbiz.apache.org/partymgr/control/findparty] Screen. > - Check Classification group dropdown > List is empty.. > - Refer attached screenshot for more clarity of the issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-10007) Party Classification Groups are not listing on FindParty screen.
[ https://issues.apache.org/jira/browse/OFBIZ-10007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Agrawal reassigned OFBIZ-10007: Assignee: Aman Agrawal > Party Classification Groups are not listing on FindParty screen. > > > Key: OFBIZ-10007 > URL: https://issues.apache.org/jira/browse/OFBIZ-10007 > Project: OFBiz > Issue Type: Bug > Components: party >Reporter: Sonal Patwari >Assignee: Aman Agrawal > Attachments: FindPartyPageClassificationGroupsNotListing.png > > > - Navigate to [Find > Party|https://demo-trunk.ofbiz.apache.org/partymgr/control/findparty] Screen. > - Check Classification group dropdown > List is empty.. > - Refer attached screenshot for more clarity of the issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9227) Violation of foreign key constraint
[ https://issues.apache.org/jira/browse/OFBIZ-9227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265596#comment-16265596 ] Aman Agrawal commented on OFBIZ-9227: - Hi Michael, I think this issue is fixed on svn revision no: r1772880. I think we can close this ticket. > Violation of foreign key constraint > --- > > Key: OFBIZ-9227 > URL: https://issues.apache.org/jira/browse/OFBIZ-9227 > Project: OFBiz > Issue Type: Bug > Components: workeffort >Affects Versions: Release Branch 16.11 > Environment: Win 7 >Reporter: Michael Clifton >Assignee: Aman Agrawal >Priority: Minor > Labels: database, tasks, workeffort > > Trying to add a task to a project phase, I receive the below error. > 2017-02-21 09:23:54,189 |http-nio-8443-exec-1 |ServiceDispatcher |E| Error in > Service [createProjectTask]: Exception thrown while creating the "newEntity" > GenericValue: org.apache.ofbiz.entity.GenericEntityException: Error while > inserting: > [GenericEntity:WorkEffort][createdByUserLogin,admin(java.lang.String)][createdDate,2017-02-21 > 09:23:52.876(java.sql.Timestamp)][createdStamp,2017-02-21 > 09:23:52.876(java.sql.Timestamp)][createdTxStamp,2017-02-21 > 09:23:51.627(java.sql.Timestamp)][currentStatusId,PTS_CREATED(java.lang.String)][description,Test(java.lang.String)][estimatedCompletionDate,2017-02-24 > 00:00:00.0(java.sql.Timestamp)][estimatedStartDate,2017-02-21 > 00:00:00.0(java.sql.Timestamp)][lastModifiedByUserLogin,admin(java.lang.String)][lastModifiedDate,2017-02-21 > 09:23:52.876(java.sql.Timestamp)][lastStatusUpdate,2017-02-21 > 09:23:52.876(java.sql.Timestamp)][lastUpdatedStamp,2017-02-21 > 09:23:52.876(java.sql.Timestamp)][lastUpdatedTxStamp,2017-02-21 > 09:23:51.627(java.sql.Timestamp)][priority,1(java.lang.Long)][revisionNumber,1(java.lang.Long)][scopeEnumId,WES_PRIVATE(java.lang.String)][sequenceNum,1(java.lang.Long)][workEffortId,10090(java.lang.String)][workEffortName,Test(java.lang.String)][workEffortParentId,10048(java.lang.String)][workEffortTypeId,Task(java.lang.String)] > (SQL Exception while executing the following:INSERT INTO OFBIZ.WORK_EFFORT > (WORK_EFFORT_ID, WORK_EFFORT_TYPE_ID, CURRENT_STATUS_ID, LAST_STATUS_UPDATE, > WORK_EFFORT_PURPOSE_TYPE_ID, WORK_EFFORT_PARENT_ID, SCOPE_ENUM_ID, PRIORITY, > PERCENT_COMPLETE, WORK_EFFORT_NAME, SHOW_AS_ENUM_ID, SEND_NOTIFICATION_EMAIL, > DESCRIPTION, LOCATION_DESC, ESTIMATED_START_DATE, ESTIMATED_COMPLETION_DATE, > ACTUAL_START_DATE, ACTUAL_COMPLETION_DATE, ESTIMATED_MILLI_SECONDS, > ESTIMATED_SETUP_MILLIS, ESTIMATE_CALC_METHOD, ACTUAL_MILLI_SECONDS, > ACTUAL_SETUP_MILLIS, TOTAL_MILLI_SECONDS_ALLOWED, TOTAL_MONEY_ALLOWED, > MONEY_UOM_ID, SPECIAL_TERMS, TIME_TRANSPARENCY, UNIVERSAL_ID, > SOURCE_REFERENCE_ID, FIXED_ASSET_ID, FACILITY_ID, INFO_URL, > RECURRENCE_INFO_ID, TEMP_EXPR_ID, RUNTIME_DATA_ID, NOTE_ID, > SERVICE_LOADER_NAME, QUANTITY_TO_PRODUCE, QUANTITY_PRODUCED, > QUANTITY_REJECTED, RESERV_PERSONS, RESERV2ND_P_P_PERC, RESERV_NTH_P_P_PERC, > ACCOMMODATION_MAP_ID, ACCOMMODATION_SPOT_ID, REVISION_NUMBER, CREATED_DATE, > CREATED_BY_USER_LOGIN, LAST_MODIFIED_DATE, LAST_MODIFIED_BY_USER_LOGIN, > LAST_UPDATED_STAMP, LAST_UPDATED_TX_STAMP, CREATED_STAMP, CREATED_TX_STAMP, > SEQUENCE_NUM) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, > ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, > ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) (INSERT on table 'WORK_EFFORT' caused a > violation of foreign key constraint 'WK_EFFRT_TYPE' for key (Task). The > statement has been rolled back.)) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9227) Violation of foreign key constraint
[ https://issues.apache.org/jira/browse/OFBIZ-9227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Agrawal reassigned OFBIZ-9227: --- Assignee: Aman Agrawal > Violation of foreign key constraint > --- > > Key: OFBIZ-9227 > URL: https://issues.apache.org/jira/browse/OFBIZ-9227 > Project: OFBiz > Issue Type: Bug > Components: workeffort >Affects Versions: Release Branch 16.11 > Environment: Win 7 >Reporter: Michael Clifton >Assignee: Aman Agrawal >Priority: Minor > Labels: database, tasks, workeffort > > Trying to add a task to a project phase, I receive the below error. > 2017-02-21 09:23:54,189 |http-nio-8443-exec-1 |ServiceDispatcher |E| Error in > Service [createProjectTask]: Exception thrown while creating the "newEntity" > GenericValue: org.apache.ofbiz.entity.GenericEntityException: Error while > inserting: > [GenericEntity:WorkEffort][createdByUserLogin,admin(java.lang.String)][createdDate,2017-02-21 > 09:23:52.876(java.sql.Timestamp)][createdStamp,2017-02-21 > 09:23:52.876(java.sql.Timestamp)][createdTxStamp,2017-02-21 > 09:23:51.627(java.sql.Timestamp)][currentStatusId,PTS_CREATED(java.lang.String)][description,Test(java.lang.String)][estimatedCompletionDate,2017-02-24 > 00:00:00.0(java.sql.Timestamp)][estimatedStartDate,2017-02-21 > 00:00:00.0(java.sql.Timestamp)][lastModifiedByUserLogin,admin(java.lang.String)][lastModifiedDate,2017-02-21 > 09:23:52.876(java.sql.Timestamp)][lastStatusUpdate,2017-02-21 > 09:23:52.876(java.sql.Timestamp)][lastUpdatedStamp,2017-02-21 > 09:23:52.876(java.sql.Timestamp)][lastUpdatedTxStamp,2017-02-21 > 09:23:51.627(java.sql.Timestamp)][priority,1(java.lang.Long)][revisionNumber,1(java.lang.Long)][scopeEnumId,WES_PRIVATE(java.lang.String)][sequenceNum,1(java.lang.Long)][workEffortId,10090(java.lang.String)][workEffortName,Test(java.lang.String)][workEffortParentId,10048(java.lang.String)][workEffortTypeId,Task(java.lang.String)] > (SQL Exception while executing the following:INSERT INTO OFBIZ.WORK_EFFORT > (WORK_EFFORT_ID, WORK_EFFORT_TYPE_ID, CURRENT_STATUS_ID, LAST_STATUS_UPDATE, > WORK_EFFORT_PURPOSE_TYPE_ID, WORK_EFFORT_PARENT_ID, SCOPE_ENUM_ID, PRIORITY, > PERCENT_COMPLETE, WORK_EFFORT_NAME, SHOW_AS_ENUM_ID, SEND_NOTIFICATION_EMAIL, > DESCRIPTION, LOCATION_DESC, ESTIMATED_START_DATE, ESTIMATED_COMPLETION_DATE, > ACTUAL_START_DATE, ACTUAL_COMPLETION_DATE, ESTIMATED_MILLI_SECONDS, > ESTIMATED_SETUP_MILLIS, ESTIMATE_CALC_METHOD, ACTUAL_MILLI_SECONDS, > ACTUAL_SETUP_MILLIS, TOTAL_MILLI_SECONDS_ALLOWED, TOTAL_MONEY_ALLOWED, > MONEY_UOM_ID, SPECIAL_TERMS, TIME_TRANSPARENCY, UNIVERSAL_ID, > SOURCE_REFERENCE_ID, FIXED_ASSET_ID, FACILITY_ID, INFO_URL, > RECURRENCE_INFO_ID, TEMP_EXPR_ID, RUNTIME_DATA_ID, NOTE_ID, > SERVICE_LOADER_NAME, QUANTITY_TO_PRODUCE, QUANTITY_PRODUCED, > QUANTITY_REJECTED, RESERV_PERSONS, RESERV2ND_P_P_PERC, RESERV_NTH_P_P_PERC, > ACCOMMODATION_MAP_ID, ACCOMMODATION_SPOT_ID, REVISION_NUMBER, CREATED_DATE, > CREATED_BY_USER_LOGIN, LAST_MODIFIED_DATE, LAST_MODIFIED_BY_USER_LOGIN, > LAST_UPDATED_STAMP, LAST_UPDATED_TX_STAMP, CREATED_STAMP, CREATED_TX_STAMP, > SEQUENCE_NUM) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, > ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, > ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) (INSERT on table 'WORK_EFFORT' caused a > violation of foreign key constraint 'WK_EFFRT_TYPE' for key (Task). The > statement has been rolled back.)) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9696) Fix type entities to follow convention of hasTable
[ https://issues.apache.org/jira/browse/OFBIZ-9696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16177659#comment-16177659 ] Aman Agrawal commented on OFBIZ-9696: - Update SQL queries for ShipmentGatewayConfig and PaymentGatewayConfig entity modifications. UPDATE Shipment_Gateway_Config SET shipment_gateway_conf_type_id = 'SHIP_GATEWAY_DHL' WHERE shipment_gateway_conf_type_id = 'DHL'; UPDATE Shipment_Gateway_Config SET shipment_gateway_conf_type_id = 'SHIP_GATEWAY_FEDEX' WHERE shipment_gateway_conf_type_id = 'FEDEX'; UPDATE Shipment_Gateway_Config SET shipment_gateway_conf_type_id = 'SHIP_GATEWAY_UPS' WHERE shipment_gateway_conf_type_id = 'UPS'; UPDATE Shipment_Gateway_Config SET shipment_gateway_conf_type_id = 'SHIP_GATEWAY_USPS' WHERE shipment_gateway_conf_type_id = 'USPS'; UPDATE Payment_Gateway_Config SET payment_gateway_config_type_id = 'PAY_GATWY_SAGEPAY' WHERE payment_gateway_config_type_id = 'SAGEPAY'; UPDATE Payment_Gateway_Config SET payment_gateway_config_type_id = 'PAY_GATWY_AUTH_NET' WHERE payment_gateway_config_type_id = 'AUTHORIZE_NET'; UPDATE Payment_Gateway_Config SET payment_gateway_config_type_id = 'PAY_GATWY_CYBERSRC' WHERE payment_gateway_config_type_id = 'CYBERSOURCE'; UPDATE Payment_Gateway_Config SET payment_gateway_config_type_id = 'PAY_GATWY_EWAY' WHERE payment_gateway_config_type_id = 'EWAY'; UPDATE Payment_Gateway_Config SET payment_gateway_config_type_id = 'PAY_GATWY_PAYFLOWPRO' WHERE payment_gateway_config_type_id = 'PAYFLOWPRO'; UPDATE Payment_Gateway_Config SET payment_gateway_config_type_id = 'PAY_GATWY_PAYPAL' WHERE payment_gateway_config_type_id = 'PAYPAL'; UPDATE Payment_Gateway_Config SET payment_gateway_config_type_id = 'PAY_GATWY_CLRCOMRC' WHERE payment_gateway_config_type_id = 'CLEARCOMMERCE'; UPDATE Payment_Gateway_Config SET payment_gateway_config_type_id = 'PAY_GATWY_WORLDPAY' WHERE payment_gateway_config_type_id = 'WORLDPAY'; UPDATE Payment_Gateway_Config SET payment_gateway_config_type_id = 'PAY_GATWY_ORBITAL' WHERE payment_gateway_config_type_id = 'ORBITAL'; UPDATE Payment_Gateway_Config SET payment_gateway_config_type_id = 'PAY_GATWY_SECUREPAY' WHERE payment_gateway_config_type_id = 'SECUREPAY'; UPDATE Payment_Gateway_Config SET payment_gateway_config_type_id = 'PAY_GATWY_IDEAL' WHERE payment_gateway_config_type_id = 'IDEAL'; > Fix type entities to follow convention of hasTable > -- > > Key: OFBIZ-9696 > URL: https://issues.apache.org/jira/browse/OFBIZ-9696 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Arun Patidar >Assignee: Arun Patidar > Attachments: OFBIZ-9696-2.patch, OFBIZ-9696.patch > > > 'hasTable' field of 'Type' entities is used to give an idea that detail > entity exists or not. We generally get the name of detail entity on the basis > of typeId field value. > For example : > ContactMechType,contactMechTypeId = "POSTAL_ADDRESS" then we go to > PostalAddress for detail. > similarly, > ContactMechType,contactMechTypeId = "TELECOM_NUMBER" then we go to > TelecomNumber for detail. > We should follow the naming convention. > Below are some entities that are not following the pattern. Some of them are: >- ShipmentGatewayConfigType >- PaymentGatewayConfigType -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (OFBIZ-9696) Fix type entities to follow convention of hasTable
[ https://issues.apache.org/jira/browse/OFBIZ-9696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16177594#comment-16177594 ] Aman Agrawal edited comment on OFBIZ-9696 at 9/23/17 6:29 AM: -- Patch available for PaymentGatewayConfigType entity. In this changed the type field like: "SAGEPAY" -> "PAY_GATWY_SAGEPAY" and made changes in PaymentGatewayConfig entity. Also made changes in the code base. was (Author: aman.agrawal): Patch available for PaymentGatewayConfigType entity. In this changed the type field like: "SAGEPAY" -> "PAY_GATWY_SAGEPAY" and also made changes in PaymentGatewayConfig entity. > Fix type entities to follow convention of hasTable > -- > > Key: OFBIZ-9696 > URL: https://issues.apache.org/jira/browse/OFBIZ-9696 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Arun Patidar >Assignee: Arun Patidar > Attachments: OFBIZ-9696-2.patch, OFBIZ-9696.patch > > > 'hasTable' field of 'Type' entities is used to give an idea that detail > entity exists or not. We generally get the name of detail entity on the basis > of typeId field value. > For example : > ContactMechType,contactMechTypeId = "POSTAL_ADDRESS" then we go to > PostalAddress for detail. > similarly, > ContactMechType,contactMechTypeId = "TELECOM_NUMBER" then we go to > TelecomNumber for detail. > We should follow the naming convention. > Below are some entities that are not following the pattern. Some of them are: >- ShipmentGatewayConfigType >- PaymentGatewayConfigType -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9696) Fix type entities to follow convention of hasTable
[ https://issues.apache.org/jira/browse/OFBIZ-9696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Agrawal updated OFBIZ-9696: Attachment: OFBIZ-9696-2.patch Patch available for PaymentGatewayConfigType entity. In this changed the type field like: "SAGEPAY" -> "PAY_GATWY_SAGEPAY" and also made changes in PaymentGatewayConfig entity. > Fix type entities to follow convention of hasTable > -- > > Key: OFBIZ-9696 > URL: https://issues.apache.org/jira/browse/OFBIZ-9696 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Arun Patidar >Assignee: Arun Patidar > Attachments: OFBIZ-9696-2.patch, OFBIZ-9696.patch > > > 'hasTable' field of 'Type' entities is used to give an idea that detail > entity exists or not. We generally get the name of detail entity on the basis > of typeId field value. > For example : > ContactMechType,contactMechTypeId = "POSTAL_ADDRESS" then we go to > PostalAddress for detail. > similarly, > ContactMechType,contactMechTypeId = "TELECOM_NUMBER" then we go to > TelecomNumber for detail. > We should follow the naming convention. > Below are some entities that are not following the pattern. Some of them are: >- ShipmentGatewayConfigType >- PaymentGatewayConfigType -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9696) Fix type entities to follow convention of hasTable
[ https://issues.apache.org/jira/browse/OFBIZ-9696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Agrawal updated OFBIZ-9696: Attachment: OFBIZ-9696.patch Patch available for ShipmentGatewayConfigType entity. In this changed the type field like: "FEDEX" -> "SHIP_GATEWAY_FEDEX" and also made changes in ShipmentGatewayConfig entity. > Fix type entities to follow convention of hasTable > -- > > Key: OFBIZ-9696 > URL: https://issues.apache.org/jira/browse/OFBIZ-9696 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Arun Patidar >Assignee: Arun Patidar > Attachments: OFBIZ-9696.patch > > > 'hasTable' field of 'Type' entities is used to give an idea that detail > entity exists or not. We generally get the name of detail entity on the basis > of typeId field value. > For example : > ContactMechType,contactMechTypeId = "POSTAL_ADDRESS" then we go to > PostalAddress for detail. > similarly, > ContactMechType,contactMechTypeId = "TELECOM_NUMBER" then we go to > TelecomNumber for detail. > We should follow the naming convention. > Below are some entities that are not following the pattern. Some of them are: >- ShipmentGatewayConfigType >- PaymentGatewayConfigType -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OFBIZ-9646) User should be notified with success message on creating fixed asset in accounting component
[ https://issues.apache.org/jira/browse/OFBIZ-9646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Agrawal resolved OFBIZ-9646. - Resolution: Fixed > User should be notified with success message on creating fixed asset in > accounting component > > > Key: OFBIZ-9646 > URL: https://issues.apache.org/jira/browse/OFBIZ-9646 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Upcoming Release >Reporter: Aditya Sharma >Assignee: Aman Agrawal >Priority: Trivial > > Steps to regenerate: > 1. Go to Accounting component (https://localhost:8443/accounting/control/main) > 2. Click on Fixed Assets submenu > (https://localhost:8443/accounting/control/ListFixedAssets) > 3. Click on New Fixed Asset button > (https://localhost:8443/accounting/control/EditFixedAsset). > 4. Add required fields and Click on Submit button. > No success message. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OFBIZ-9646) User should be notified with success message on creating fixed asset in accounting component
[ https://issues.apache.org/jira/browse/OFBIZ-9646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Agrawal closed OFBIZ-9646. --- > User should be notified with success message on creating fixed asset in > accounting component > > > Key: OFBIZ-9646 > URL: https://issues.apache.org/jira/browse/OFBIZ-9646 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Upcoming Release >Reporter: Aditya Sharma >Assignee: Aman Agrawal >Priority: Trivial > > Steps to regenerate: > 1. Go to Accounting component (https://localhost:8443/accounting/control/main) > 2. Click on Fixed Assets submenu > (https://localhost:8443/accounting/control/ListFixedAssets) > 3. Click on New Fixed Asset button > (https://localhost:8443/accounting/control/EditFixedAsset). > 4. Add required fields and Click on Submit button. > No success message. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9646) User should be notified with success message on creating fixed asset in accounting component
[ https://issues.apache.org/jira/browse/OFBIZ-9646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16159769#comment-16159769 ] Aman Agrawal commented on OFBIZ-9646: - This issue has been fixed under ticket [OFBIZ-7597|https://issues.apache.org/jira/browse/OFBIZ-7597]. Hence, closing this ticket. > User should be notified with success message on creating fixed asset in > accounting component > > > Key: OFBIZ-9646 > URL: https://issues.apache.org/jira/browse/OFBIZ-9646 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Upcoming Release >Reporter: Aditya Sharma >Assignee: Aman Agrawal >Priority: Trivial > > Steps to regenerate: > 1. Go to Accounting component (https://localhost:8443/accounting/control/main) > 2. Click on Fixed Assets submenu > (https://localhost:8443/accounting/control/ListFixedAssets) > 3. Click on New Fixed Asset button > (https://localhost:8443/accounting/control/EditFixedAsset). > 4. Add required fields and Click on Submit button. > No success message. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9646) User should be notified with success message on creating fixed asset in accounting component
[ https://issues.apache.org/jira/browse/OFBIZ-9646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Agrawal reassigned OFBIZ-9646: --- Assignee: Aman Agrawal > User should be notified with success message on creating fixed asset in > accounting component > > > Key: OFBIZ-9646 > URL: https://issues.apache.org/jira/browse/OFBIZ-9646 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Upcoming Release >Reporter: Aditya Sharma >Assignee: Aman Agrawal >Priority: Trivial > > Steps to regenerate: > 1. Go to Accounting component (https://localhost:8443/accounting/control/main) > 2. Click on Fixed Assets submenu > (https://localhost:8443/accounting/control/ListFixedAssets) > 3. Click on New Fixed Asset button > (https://localhost:8443/accounting/control/EditFixedAsset). > 4. Add required fields and Click on Submit button. > No success message. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-7189) Forgot password new password reset email content is not understandable.
[
https://issues.apache.org/jira/browse/OFBIZ-7189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aman Agrawal reassigned OFBIZ-7189:
---
Assignee: Aman Agrawal (was: Amardeep Singh Jhajj)
> Forgot password new password reset email content is not understandable.
> ---
>
> Key: OFBIZ-7189
> URL: https://issues.apache.org/jira/browse/OFBIZ-7189
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL APPLICATIONS
>Affects Versions: Release Branch 14.12
>Reporter: Amardeep Singh Jhajj
>Assignee: Aman Agrawal
>
> New password email content is not understandable. Please refer:
> {code}
> SecurityExtThisEmailIsInResponseToYourRequestToHave SecurityExtANew
> SecurityExtPasswordSentToYou.
> SecurityExtNewPasswordMssgEncryptionOn "jupZW"
> {code}
> The problem is missing UiLabels. I will provide patch for it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OFBIZ-8091) Clean up commented out code in XML for Common component
[ https://issues.apache.org/jira/browse/OFBIZ-8091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Agrawal updated OFBIZ-8091: Attachment: OFBIZ-8091.patch Patch provided for trunk. > Clean up commented out code in XML for Common component > --- > > Key: OFBIZ-8091 > URL: https://issues.apache.org/jira/browse/OFBIZ-8091 > Project: OFBiz > Issue Type: Sub-task > Components: commonext/setup >Affects Versions: Trunk >Reporter: Aman Agrawal >Assignee: Aman Agrawal >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-8091.patch > > > Clean up commented out code in XML for Common component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-8091) Clean up commented out code in XML for Common component
Aman Agrawal created OFBIZ-8091: --- Summary: Clean up commented out code in XML for Common component Key: OFBIZ-8091 URL: https://issues.apache.org/jira/browse/OFBIZ-8091 Project: OFBiz Issue Type: Sub-task Components: commonext/setup Affects Versions: Trunk Reporter: Aman Agrawal Assignee: Aman Agrawal Priority: Minor Clean up commented out code in XML for Common component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8071) Clean up commented out code in Groovy for Manufacturing
[ https://issues.apache.org/jira/browse/OFBIZ-8071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Agrawal updated OFBIZ-8071: Attachment: OFBIZ-8071.patch Patch provided for trunk. > Clean up commented out code in Groovy for Manufacturing > --- > > Key: OFBIZ-8071 > URL: https://issues.apache.org/jira/browse/OFBIZ-8071 > Project: OFBiz > Issue Type: Sub-task > Components: manufacturing >Affects Versions: Trunk >Reporter: Aman Agrawal >Assignee: Aman Agrawal >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-8071.patch > > > Clean up commented out code in Groovy for Manufacturing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8069) Clean up commented out code in Groovy for Accounting
[ https://issues.apache.org/jira/browse/OFBIZ-8069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Agrawal updated OFBIZ-8069: Attachment: OFBIZ-8069.patch Patch provided for trunk. > Clean up commented out code in Groovy for Accounting > > > Key: OFBIZ-8069 > URL: https://issues.apache.org/jira/browse/OFBIZ-8069 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk >Reporter: Aman Agrawal >Assignee: Aman Agrawal >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-8069.patch > > > Clean up commented out code in Groovy for Accounting. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8072) Clean up commented out code in Groovy for Marketing
[ https://issues.apache.org/jira/browse/OFBIZ-8072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Agrawal updated OFBIZ-8072: Attachment: OFBIZ-8072.patch Patch provided for trunk. > Clean up commented out code in Groovy for Marketing > --- > > Key: OFBIZ-8072 > URL: https://issues.apache.org/jira/browse/OFBIZ-8072 > Project: OFBiz > Issue Type: Sub-task > Components: marketing >Affects Versions: Trunk >Reporter: Aman Agrawal >Assignee: Aman Agrawal >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-8072.patch > > > Clean up commented out code in Groovy for Marketing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8070) Clean up commented out code in Groovy for Content
[ https://issues.apache.org/jira/browse/OFBIZ-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Agrawal updated OFBIZ-8070: Attachment: OFBIZ-8070.patch Patch provided for trunk. > Clean up commented out code in Groovy for Content > - > > Key: OFBIZ-8070 > URL: https://issues.apache.org/jira/browse/OFBIZ-8070 > Project: OFBiz > Issue Type: Sub-task > Components: content >Affects Versions: Trunk >Reporter: Aman Agrawal >Assignee: Aman Agrawal >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-8070.patch > > > Clean up commented out code in Groovy for Content. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8073) Clean up commented out code in Groovy for WorkEffort
[ https://issues.apache.org/jira/browse/OFBIZ-8073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Agrawal updated OFBIZ-8073: Attachment: OFBIZ-8073.patch Patch provided for trunk. > Clean up commented out code in Groovy for WorkEffort > > > Key: OFBIZ-8073 > URL: https://issues.apache.org/jira/browse/OFBIZ-8073 > Project: OFBiz > Issue Type: Sub-task > Components: workeffort >Affects Versions: Trunk >Reporter: Aman Agrawal >Assignee: Aman Agrawal >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-8073.patch > > > Clean up commented out code in Groovy for WorkEffort. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8074) Clean up commented out code in Groovy for Order
[ https://issues.apache.org/jira/browse/OFBIZ-8074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Agrawal updated OFBIZ-8074: Attachment: OFBIZ-8074.patch Patch provided for trunk. > Clean up commented out code in Groovy for Order > --- > > Key: OFBIZ-8074 > URL: https://issues.apache.org/jira/browse/OFBIZ-8074 > Project: OFBiz > Issue Type: Sub-task > Components: order >Affects Versions: Trunk >Reporter: Aman Agrawal >Assignee: Aman Agrawal >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-8074.patch > > > Clean up commented out code in Groovy for Order. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8075) Clean up commented out code in Groovy for Product
[ https://issues.apache.org/jira/browse/OFBIZ-8075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Agrawal updated OFBIZ-8075: Attachment: OFBIZ-8075.patch Patch provided for trunk. > Clean up commented out code in Groovy for Product > - > > Key: OFBIZ-8075 > URL: https://issues.apache.org/jira/browse/OFBIZ-8075 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Aman Agrawal >Assignee: Aman Agrawal >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-8075.patch > > > Clean up commented out code in Groovy for Product. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-8075) Clean up commented out code in Groovy for Product
Aman Agrawal created OFBIZ-8075: --- Summary: Clean up commented out code in Groovy for Product Key: OFBIZ-8075 URL: https://issues.apache.org/jira/browse/OFBIZ-8075 Project: OFBiz Issue Type: Sub-task Components: product Affects Versions: Trunk Reporter: Aman Agrawal Assignee: Aman Agrawal Priority: Minor Clean up commented out code in Groovy for Product. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-8074) Clean up commented out code in Groovy for Order
Aman Agrawal created OFBIZ-8074: --- Summary: Clean up commented out code in Groovy for Order Key: OFBIZ-8074 URL: https://issues.apache.org/jira/browse/OFBIZ-8074 Project: OFBiz Issue Type: Sub-task Components: order Affects Versions: Trunk Reporter: Aman Agrawal Assignee: Aman Agrawal Priority: Minor Clean up commented out code in Groovy for Order. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-8073) Clean up commented out code in Groovy for WorkEffort
Aman Agrawal created OFBIZ-8073: --- Summary: Clean up commented out code in Groovy for WorkEffort Key: OFBIZ-8073 URL: https://issues.apache.org/jira/browse/OFBIZ-8073 Project: OFBiz Issue Type: Sub-task Components: workeffort Affects Versions: Trunk Reporter: Aman Agrawal Assignee: Aman Agrawal Priority: Minor Clean up commented out code in Groovy for WorkEffort. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-8071) Clean up commented out code in Groovy for Manufacturing
Aman Agrawal created OFBIZ-8071: --- Summary: Clean up commented out code in Groovy for Manufacturing Key: OFBIZ-8071 URL: https://issues.apache.org/jira/browse/OFBIZ-8071 Project: OFBiz Issue Type: Sub-task Components: manufacturing Affects Versions: Trunk Reporter: Aman Agrawal Assignee: Aman Agrawal Priority: Minor Clean up commented out code in Groovy for Manufacturing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-8072) Clean up commented out code in Groovy for Marketing
Aman Agrawal created OFBIZ-8072: --- Summary: Clean up commented out code in Groovy for Marketing Key: OFBIZ-8072 URL: https://issues.apache.org/jira/browse/OFBIZ-8072 Project: OFBiz Issue Type: Sub-task Components: marketing Affects Versions: Trunk Reporter: Aman Agrawal Assignee: Aman Agrawal Priority: Minor Clean up commented out code in Groovy for Marketing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-8070) Clean up commented out code in Groovy for Content
Aman Agrawal created OFBIZ-8070: --- Summary: Clean up commented out code in Groovy for Content Key: OFBIZ-8070 URL: https://issues.apache.org/jira/browse/OFBIZ-8070 Project: OFBiz Issue Type: Sub-task Components: content Affects Versions: Trunk Reporter: Aman Agrawal Assignee: Aman Agrawal Priority: Minor Clean up commented out code in Groovy for Content. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-8069) Clean up commented out code in Groovy for Accounting
Aman Agrawal created OFBIZ-8069: --- Summary: Clean up commented out code in Groovy for Accounting Key: OFBIZ-8069 URL: https://issues.apache.org/jira/browse/OFBIZ-8069 Project: OFBiz Issue Type: Sub-task Components: accounting Affects Versions: Trunk Reporter: Aman Agrawal Assignee: Aman Agrawal Priority: Minor Clean up commented out code in Groovy for Accounting. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8066) Clean up commented out code in Free Marker Template for Product
[ https://issues.apache.org/jira/browse/OFBIZ-8066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Agrawal updated OFBIZ-8066: Attachment: OFBIZ-8066.patch Patch provided for trunk. > Clean up commented out code in Free Marker Template for Product > --- > > Key: OFBIZ-8066 > URL: https://issues.apache.org/jira/browse/OFBIZ-8066 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Aman Agrawal >Assignee: Aman Agrawal >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-8066.patch > > > Clean up commented out code in Free Marker Template for Product. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-8066) Clean up commented out code in Free Marker Template for Product
Aman Agrawal created OFBIZ-8066: --- Summary: Clean up commented out code in Free Marker Template for Product Key: OFBIZ-8066 URL: https://issues.apache.org/jira/browse/OFBIZ-8066 Project: OFBiz Issue Type: Sub-task Components: product Affects Versions: Trunk Reporter: Aman Agrawal Assignee: Aman Agrawal Priority: Minor Clean up commented out code in Free Marker Template for Product. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8065) Clean up commented out code in Free Marker Template for WorkEffort
[ https://issues.apache.org/jira/browse/OFBIZ-8065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Agrawal updated OFBIZ-8065: Attachment: OFBIZ-8065.patch Patch provided for trunk. > Clean up commented out code in Free Marker Template for WorkEffort > -- > > Key: OFBIZ-8065 > URL: https://issues.apache.org/jira/browse/OFBIZ-8065 > Project: OFBiz > Issue Type: Sub-task > Components: workeffort >Affects Versions: Trunk >Reporter: Aman Agrawal >Assignee: Aman Agrawal >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-8065.patch > > > Clean up commented out code in Free Marker Template for WorkEffort. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-8065) Clean up commented out code in Free Marker Template for WorkEffort
Aman Agrawal created OFBIZ-8065: --- Summary: Clean up commented out code in Free Marker Template for WorkEffort Key: OFBIZ-8065 URL: https://issues.apache.org/jira/browse/OFBIZ-8065 Project: OFBiz Issue Type: Sub-task Components: workeffort Affects Versions: Trunk Reporter: Aman Agrawal Assignee: Aman Agrawal Priority: Minor Clean up commented out code in Free Marker Template for WorkEffort. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8064) Clean up commented out code in Free Marker Template for Party
[ https://issues.apache.org/jira/browse/OFBIZ-8064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Agrawal updated OFBIZ-8064: Attachment: OFBIZ-8064.patch Patch provided for trunk. > Clean up commented out code in Free Marker Template for Party > - > > Key: OFBIZ-8064 > URL: https://issues.apache.org/jira/browse/OFBIZ-8064 > Project: OFBiz > Issue Type: Sub-task > Components: party >Affects Versions: Trunk >Reporter: Aman Agrawal >Assignee: Aman Agrawal >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-8064.patch > > > Clean up commented out code in Free Marker Template for Order. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-8064) Clean up commented out code in Free Marker Template for Party
Aman Agrawal created OFBIZ-8064: --- Summary: Clean up commented out code in Free Marker Template for Party Key: OFBIZ-8064 URL: https://issues.apache.org/jira/browse/OFBIZ-8064 Project: OFBiz Issue Type: Sub-task Components: party Affects Versions: Trunk Reporter: Aman Agrawal Assignee: Aman Agrawal Priority: Minor Clean up commented out code in Free Marker Template for Order. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8035) Clean up commented out code in Free Marker Template for Order
[ https://issues.apache.org/jira/browse/OFBIZ-8035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Agrawal updated OFBIZ-8035: Attachment: OFBIZ-8035.patch Patch provided for trunk. > Clean up commented out code in Free Marker Template for Order > - > > Key: OFBIZ-8035 > URL: https://issues.apache.org/jira/browse/OFBIZ-8035 > Project: OFBiz > Issue Type: Sub-task > Components: order >Affects Versions: Trunk >Reporter: Aman Agrawal >Assignee: Aman Agrawal >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-8035.patch > > > Clean up commented out code in Free Marker Template for Order. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-8035) Clean up commented out code in Free Marker Template for Order
Aman Agrawal created OFBIZ-8035: --- Summary: Clean up commented out code in Free Marker Template for Order Key: OFBIZ-8035 URL: https://issues.apache.org/jira/browse/OFBIZ-8035 Project: OFBiz Issue Type: Sub-task Components: order Affects Versions: Trunk Reporter: Aman Agrawal Assignee: Aman Agrawal Priority: Minor Clean up commented out code in Free Marker Template for Order. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8023) Clean up commented out code in Free Marker Template for SecurityExt
[ https://issues.apache.org/jira/browse/OFBIZ-8023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Agrawal updated OFBIZ-8023: Attachment: OFBIZ-8023.patch Patch provided for trunk. > Clean up commented out code in Free Marker Template for SecurityExt > --- > > Key: OFBIZ-8023 > URL: https://issues.apache.org/jira/browse/OFBIZ-8023 > Project: OFBiz > Issue Type: Sub-task > Components: securityext >Affects Versions: Trunk >Reporter: Aman Agrawal >Assignee: Aman Agrawal >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-8023.patch > > > Clean up commented out code in Free Marker Template for SecurityExt. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-8023) Clean up commented out code in Free Marker Template for SecurityExt
Aman Agrawal created OFBIZ-8023: --- Summary: Clean up commented out code in Free Marker Template for SecurityExt Key: OFBIZ-8023 URL: https://issues.apache.org/jira/browse/OFBIZ-8023 Project: OFBiz Issue Type: Sub-task Components: securityext Affects Versions: Trunk Reporter: Aman Agrawal Assignee: Aman Agrawal Priority: Minor Clean up commented out code in Free Marker Template for SecurityExt. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7894) Clean up commented out code in Free Marker Template for Manufacturing
[ https://issues.apache.org/jira/browse/OFBIZ-7894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Agrawal updated OFBIZ-7894: Attachment: OFBIZ-7894.patch Patch available for trunk. > Clean up commented out code in Free Marker Template for Manufacturing > - > > Key: OFBIZ-7894 > URL: https://issues.apache.org/jira/browse/OFBIZ-7894 > Project: OFBiz > Issue Type: Sub-task > Components: manufacturing >Affects Versions: Trunk >Reporter: Aman Agrawal >Assignee: Aman Agrawal >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-7894.patch > > > Clean up commented out code in Free Marker Template for Manufacturing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
