[jira] [Assigned] (OFBIZ-5432) Improvement of Dutch localization of OrderEntityLabels.xml
[ https://issues.apache.org/jira/browse/OFBIZ-5432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-5432: --- Assignee: Pierre Smits (was: Jacques Le Roux) > Improvement of Dutch localization of OrderEntityLabels.xml > -- > > Key: OFBIZ-5432 > URL: https://issues.apache.org/jira/browse/OFBIZ-5432 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Fix For: Trunk > > Attachments: OFBIZ-5432-ORDER_OrderEntityLabels.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-5435) Improvement of Dutch localization in WorkEffortMgr
[ https://issues.apache.org/jira/browse/OFBIZ-5435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-5435: --- Assignee: Pierre Smits (was: Jacques Le Roux) > Improvement of Dutch localization in WorkEffortMgr > -- > > Key: OFBIZ-5435 > URL: https://issues.apache.org/jira/browse/OFBIZ-5435 > Project: OFBiz > Issue Type: Improvement > Components: workeffort >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Fix For: Trunk > > Attachments: OFBIZ-5435-WORK_Labels.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-5431) Improving Dutch localization of OrderUiLabel.xml
[ https://issues.apache.org/jira/browse/OFBIZ-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-5431: --- Assignee: Pierre Smits (was: Jacques Le Roux) > Improving Dutch localization of OrderUiLabel.xml > > > Key: OFBIZ-5431 > URL: https://issues.apache.org/jira/browse/OFBIZ-5431 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Fix For: 14.12.01 > > Attachments: OFBIZ-5431-ORDER_OrderUiLabels.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-5300) ProductionRunServices doens't set UoM of goods in inventoryItems
[ https://issues.apache.org/jira/browse/OFBIZ-5300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-5300: --- Assignee: Pierre Smits (was: Jacques Le Roux) > ProductionRunServices doens't set UoM of goods in inventoryItems > > > Key: OFBIZ-5300 > URL: https://issues.apache.org/jira/browse/OFBIZ-5300 > Project: OFBiz > Issue Type: Bug > Components: manufacturing, product >Affects Versions: Release Branch 11.04, Release Branch 12.04, Release > Branch 13.07, Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Fix For: Release Branch 12.04, Release Branch 13.07, Trunk > > Attachments: OFBIZ-5300-ManufacturingServices.patch > > > When releasing a good to inventory from a production run (both declare and > return material) the uom of the good returned isn't set in the inventory item. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-5433) Improvement of Dutch localization in PartyMgr
[ https://issues.apache.org/jira/browse/OFBIZ-5433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-5433: --- Assignee: Pierre Smits (was: Jacques Le Roux) > Improvement of Dutch localization in PartyMgr > - > > Key: OFBIZ-5433 > URL: https://issues.apache.org/jira/browse/OFBIZ-5433 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Fix For: Trunk > > Attachments: OFBIZ-5433-PARTY_Labels.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-6333) Replacing bsh code with groovy Code in SCRUM screens, forms and menus
[ https://issues.apache.org/jira/browse/OFBIZ-6333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6333: --- Assignee: Pierre Smits (was: Jacques Le Roux) > Replacing bsh code with groovy Code in SCRUM screens, forms and menus > - > > Key: OFBIZ-6333 > URL: https://issues.apache.org/jira/browse/OFBIZ-6333 > Project: OFBiz > Issue Type: Sub-task > Components: scrum >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Fix For: 16.11.01 > > Attachments: OFBIZ-6333-BSH2Groovy-Scrum.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-6338) Replacing bsh code with groovy Code in EBAYStore screens, forms and menus
[ https://issues.apache.org/jira/browse/OFBIZ-6338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6338: --- Assignee: Pierre Smits (was: Jacques Le Roux) > Replacing bsh code with groovy Code in EBAYStore screens, forms and menus > - > > Key: OFBIZ-6338 > URL: https://issues.apache.org/jira/browse/OFBIZ-6338 > Project: OFBiz > Issue Type: Sub-task > Components: ebaystore >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Fix For: 16.11.01 > > Attachments: OFBIZ-6338-BSH2Groovy-EbayStore.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-6339) Replacing bsh code with groovy Code in HUMANRES screens, forms and menus
[ https://issues.apache.org/jira/browse/OFBIZ-6339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6339: --- Assignee: Pierre Smits (was: Jacques Le Roux) > Replacing bsh code with groovy Code in HUMANRES screens, forms and menus > > > Key: OFBIZ-6339 > URL: https://issues.apache.org/jira/browse/OFBIZ-6339 > Project: OFBiz > Issue Type: Sub-task > Components: humanres >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Fix For: 16.11.01 > > Attachments: OFBIZ-6339-BSH2Groovy-HumanRes.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-6342) Replacing bsh code with groovy Code in Party screens, forms and menus
[ https://issues.apache.org/jira/browse/OFBIZ-6342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6342: --- Assignee: Pierre Smits (was: Jacques Le Roux) > Replacing bsh code with groovy Code in Party screens, forms and menus > - > > Key: OFBIZ-6342 > URL: https://issues.apache.org/jira/browse/OFBIZ-6342 > Project: OFBiz > Issue Type: Sub-task > Components: party >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Fix For: 16.11.01 > > Attachments: OFBIZ-6342-BSH2Groovy-Party.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-6344) Replacing bsh code with groovy Code in Content screens, forms and menus
[ https://issues.apache.org/jira/browse/OFBIZ-6344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6344: --- Assignee: Pierre Smits (was: Jacques Le Roux) > Replacing bsh code with groovy Code in Content screens, forms and menus > --- > > Key: OFBIZ-6344 > URL: https://issues.apache.org/jira/browse/OFBIZ-6344 > Project: OFBiz > Issue Type: Sub-task > Components: content >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Fix For: 16.11.01 > > Attachments: OFBIZ-6344-BSH2Groovy-Content.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-6341) Replacing bsh code with groovy Code in Product screens, forms and menus
[ https://issues.apache.org/jira/browse/OFBIZ-6341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6341: --- Assignee: Pierre Smits (was: Jacques Le Roux) > Replacing bsh code with groovy Code in Product screens, forms and menus > --- > > Key: OFBIZ-6341 > URL: https://issues.apache.org/jira/browse/OFBIZ-6341 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Fix For: 16.11.01 > > Attachments: OFBIZ-6341-BSH2Groovy-Product.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-6337) Replacing bsh code with groovy Code in EBAY screens, forms and menus
[ https://issues.apache.org/jira/browse/OFBIZ-6337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6337: --- Assignee: Pierre Smits (was: Jacques Le Roux) > Replacing bsh code with groovy Code in EBAY screens, forms and menus > > > Key: OFBIZ-6337 > URL: https://issues.apache.org/jira/browse/OFBIZ-6337 > Project: OFBiz > Issue Type: Sub-task > Components: ebay >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Fix For: 16.11.01 > > Attachments: OFBIZ-6337-BSH2Groovy-Ebay.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-6340) Replacing bsh code with groovy Code in ORDER screens, forms and menus
[ https://issues.apache.org/jira/browse/OFBIZ-6340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6340: --- Assignee: Pierre Smits (was: Jacques Le Roux) > Replacing bsh code with groovy Code in ORDER screens, forms and menus > - > > Key: OFBIZ-6340 > URL: https://issues.apache.org/jira/browse/OFBIZ-6340 > Project: OFBiz > Issue Type: Sub-task > Components: order >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Fix For: 14.12.01, 12.04.06, 13.07.02, 16.11.01 > > Attachments: OFBIZ-6340-BSH2Groovy-Order.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-6335) Replacing bsh code with groovy code in PROJECTMGR screens, forms and menus
[ https://issues.apache.org/jira/browse/OFBIZ-6335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6335: --- Assignee: Pierre Smits (was: Jacques Le Roux) > Replacing bsh code with groovy code in PROJECTMGR screens, forms and menus > -- > > Key: OFBIZ-6335 > URL: https://issues.apache.org/jira/browse/OFBIZ-6335 > Project: OFBiz > Issue Type: Sub-task > Components: projectmgr >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Fix For: 16.11.01 > > Attachments: OFBIZ-6335-BSH2Groovy-ProjectMgr.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-5434) Improvement of Dutch localization in Product
[ https://issues.apache.org/jira/browse/OFBIZ-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-5434: --- Assignee: Pierre Smits (was: Jacques Le Roux) > Improvement of Dutch localization in Product > > > Key: OFBIZ-5434 > URL: https://issues.apache.org/jira/browse/OFBIZ-5434 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Fix For: 14.12.01 > > Attachments: OFBIZ-5434-PRODUCT-Labels_NL.patch, > OFBIZ-5434-PRODUCT_Labels.patch, OFBIZ-5434-PRODUCT_Labels.patch.1.rej, > OFBIZ-5434-PRODUCT_Labels.patch.2.rej, OFBIZ-5434-PRODUCT_Labels.patch.3.rej, > OFBIZ-5434-PRODUCT-UiLabels-1.patch.rej, OFBIZ-5434-PRODUCT-UiLabels.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-5456) Party logo images not stored in SystemProperty location
[ https://issues.apache.org/jira/browse/OFBIZ-5456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-5456: --- Assignee: Pierre Smits (was: Anil K Patel) > Party logo images not stored in SystemProperty location > --- > > Key: OFBIZ-5456 > URL: https://issues.apache.org/jira/browse/OFBIZ-5456 > Project: OFBiz > Issue Type: Bug > Components: content, party > Environment: multi-server, multi-tenant >Reporter: Pierre Smits >Assignee: Pierre Smits > Fix For: 14.12.01, 13.07.01 > > Attachments: OFBIZ-5456.patch > > > In a multi-server setup we have defined a shared location for storage of > tenant specific images etc. > We have set this location in table SystemProperty as an override to the > default location in content.properties. > Our definition is: > createdTxStamp="2014-01-03 13:55:07.124" description="Default location for > party logo images etc" lastUpdatedStamp="2014-01-03 13:55:07.124" > lastUpdatedTxStamp="2014-01-03 13:55:07.124" > systemPropertyId="content.upload.path.prefix" > systemPropertyValue="/test-data/tenant1/images" systemResourceId="content"/> > However, this setting is not used when when uploading a logo image in > partymgr of the tenant. In stead the default location (as in > content.properties) is used. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-6107) Quote report should open in a new window
[ https://issues.apache.org/jira/browse/OFBIZ-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6107: --- Assignee: Pierre Smits (was: Deepak Dixit) > Quote report should open in a new window > > > Key: OFBIZ-6107 > URL: https://issues.apache.org/jira/browse/OFBIZ-6107 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Labels: quote > Fix For: 16.11.01 > > Attachments: OFBIZ-6107-OrderQuotePDF.patch > > > Currently the quote report (or print) opens in the same window. This should > be in a new window(target = _BLANK) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-6019) Adding and improving some Dutch translations to ORDER labels
[ https://issues.apache.org/jira/browse/OFBIZ-6019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6019: --- Assignee: Pierre Smits (was: Jacques Le Roux) > Adding and improving some Dutch translations to ORDER labels > > > Key: OFBIZ-6019 > URL: https://issues.apache.org/jira/browse/OFBIZ-6019 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Minor > Fix For: 16.11.01 > > Attachments: OFBIZ-6019-OrderLabels.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-6016) Adding som Dutch translations to common labels.
[ https://issues.apache.org/jira/browse/OFBIZ-6016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6016: --- Assignee: Pierre Smits (was: Jacques Le Roux) > Adding som Dutch translations to common labels. > --- > > Key: OFBIZ-6016 > URL: https://issues.apache.org/jira/browse/OFBIZ-6016 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Minor > Fix For: 16.11.01 > > Attachments: OFBIZ-6016-CommonLabels-correction.patch, > OFBIZ-6016-FrameworkCommonLabels.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-6020) PartyLabels - adding and improving
[ https://issues.apache.org/jira/browse/OFBIZ-6020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6020: --- Assignee: Pierre Smits (was: Jacques Le Roux) > PartyLabels - adding and improving > -- > > Key: OFBIZ-6020 > URL: https://issues.apache.org/jira/browse/OFBIZ-6020 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Minor > Fix For: 16.11.01 > > Attachments: OFBIZ-6020-PartyEntityLabels.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-6030) ViewQuoteItemInfo.ftl has at the wrong place
[ https://issues.apache.org/jira/browse/OFBIZ-6030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6030: --- Assignee: Pierre Smits (was: Jacques Le Roux) > ViewQuoteItemInfo.ftl has at the wrong place > -- > > Key: OFBIZ-6030 > URL: https://issues.apache.org/jira/browse/OFBIZ-6030 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Release Branch 12.04, Release Branch 13.07, Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Trivial > Fix For: 14.12.01, 12.04.06, 13.07.02, 16.11.01 > > Attachments: OFBIZ-6030-ViewQuoteItemInfo.patch > > > When a product has been added to a quote and subsequently looking at > http://demo-trunk-ofbiz.apache.org/ordermgr/control/ViewQuote it shows that > the quantity and sel. amount are positioned wrong (1 column to the right of > where they should be). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-6018) Adding some Dutch translations to Manufacturing Entity labels
[ https://issues.apache.org/jira/browse/OFBIZ-6018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6018: --- Assignee: Pierre Smits (was: Jacques Le Roux) > Adding some Dutch translations to Manufacturing Entity labels > - > > Key: OFBIZ-6018 > URL: https://issues.apache.org/jira/browse/OFBIZ-6018 > Project: OFBiz > Issue Type: Improvement > Components: manufacturing >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Minor > Fix For: 16.11.01 > > Attachments: OFBIZ-6018-ManufacturingEntityLabels.xml.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-6793) Have configuration options for the ecommerce component.
[ https://issues.apache.org/jira/browse/OFBIZ-6793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6793: --- Assignee: Pierre Smits (was: Michael Brohl) > Have configuration options for the ecommerce component. > --- > > Key: OFBIZ-6793 > URL: https://issues.apache.org/jira/browse/OFBIZ-6793 > Project: OFBiz > Issue Type: Sub-task > Components: ALL APPLICATIONS, ALL COMPONENTS >Reporter: Pierre Smits >Assignee: Pierre Smits > Fix For: 15.12.01 > > Attachments: OFBIZ-6793-ecommerce.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OFBIZ-9352) Remove unused labels from AccountingUiLabels.xml
[ https://issues.apache.org/jira/browse/OFBIZ-9352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-9352: Attachment: OFBIZ-9352-AccountingUiLabels.xml.patch This patch addresses this issue. > Remove unused labels from AccountingUiLabels.xml > > > Key: OFBIZ-9352 > URL: https://issues.apache.org/jira/browse/OFBIZ-9352 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Minor > Attachments: OFBIZ-9352-AccountingUiLabels.xml.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OFBIZ-9352) Remove unused labels from AccountingUiLabels.xml
Pierre Smits created OFBIZ-9352: --- Summary: Remove unused labels from AccountingUiLabels.xml Key: OFBIZ-9352 URL: https://issues.apache.org/jira/browse/OFBIZ-9352 Project: OFBiz Issue Type: Improvement Components: accounting Reporter: Pierre Smits Assignee: Pierre Smits Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OFBIZ-9346) Maximise utilisation of common labels in AccountingMenus.xml
Pierre Smits created OFBIZ-9346: --- Summary: Maximise utilisation of common labels in AccountingMenus.xml Key: OFBIZ-9346 URL: https://issues.apache.org/jira/browse/OFBIZ-9346 Project: OFBiz Issue Type: Improvement Components: accounting Affects Versions: Trunk Reporter: Pierre Smits Assignee: Pierre Smits -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OFBIZ-9346) Maximise utilisation of common labels in AccountingMenus.xml
[ https://issues.apache.org/jira/browse/OFBIZ-9346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-9346: Attachment: OFBIZ-9346-AccountingMenus.xml.patch This patch addresses the issue. > Maximise utilisation of common labels in AccountingMenus.xml > > > Key: OFBIZ-9346 > URL: https://issues.apache.org/jira/browse/OFBIZ-9346 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Attachments: OFBIZ-9346-AccountingMenus.xml.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-6738) Enhance PartyTypeAttr with a description field
[ https://issues.apache.org/jira/browse/OFBIZ-6738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6738: --- Assignee: Pierre Smits (was: Jacques Le Roux) > Enhance PartyTypeAttr with a description field > -- > > Key: OFBIZ-6738 > URL: https://issues.apache.org/jira/browse/OFBIZ-6738 > Project: OFBiz > Issue Type: Improvement > Components: party >Reporter: Pierre Smits >Assignee: Pierre Smits > Fix For: 16.11.01 > > Attachments: OFBIZ-6738-datamodel.patch, > OFBIZ-6738-entitymodel.xml.patch > > > Currently the PartyTypeAttr entity doesn't have a means to store a > description for a PartyTypeAttr record. Having it enhances the user > experience. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-6470) Adding a Postal Address templates for the Netherlands
[ https://issues.apache.org/jira/browse/OFBIZ-6470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6470: --- Assignee: Pierre Smits (was: Jacques Le Roux) > Adding a Postal Address templates for the Netherlands > - > > Key: OFBIZ-6470 > URL: https://issues.apache.org/jira/browse/OFBIZ-6470 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Fix For: 16.11.01 > > Attachments: OFBIZ-6470-contactmechtemplates-NLD.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-6577) Incorporate the readme for the Lucene component
[ https://issues.apache.org/jira/browse/OFBIZ-6577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6577: --- Assignee: Pierre Smits (was: Jacques Le Roux) > Incorporate the readme for the Lucene component > --- > > Key: OFBIZ-6577 > URL: https://issues.apache.org/jira/browse/OFBIZ-6577 > Project: OFBiz > Issue Type: Sub-task > Components: lucene >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Fix For: 16.11.01 > > Attachments: OFBIZ-6577-README.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-6454) Label manager generates an error when searching for unused labels
[
https://issues.apache.org/jira/browse/OFBIZ-6454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Smits reassigned OFBIZ-6454:
---
Assignee: Pierre Smits (was: Deepak Dixit)
> Label manager generates an error when searching for unused labels
> -
>
> Key: OFBIZ-6454
> URL: https://issues.apache.org/jira/browse/OFBIZ-6454
> Project: OFBiz
> Issue Type: Bug
> Components: framework
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Pierre Smits
> Fix For: 14.12.01, 16.11.01
>
> Attachments: Screen Shot 2015-06-05 at 15.41.49.png
>
>
> When searching for unused labels in a component the function returns
> following error:
> {code}
> org.ofbiz.widget.renderer.ScreenRenderException: Error rendering screen
> [component://webtools/widget/LabelManagerScreens.xml#SearchLabels]:
> java.lang.IllegalArgumentException: Error running script at location
> [component://webtools/webapp/webtools/WEB-INF/actions/labelmanager/LabelManager.groovy]:
> org.xml.sax.SAXParseException; lineNumber: 58; columnNumber: 103; Attribute
> "title" was already specified for element "field". (Error running script at
> location
> [component://webtools/webapp/webtools/WEB-INF/actions/labelmanager/LabelManager.groovy]:
> org.xml.sax.SAXParseException; lineNumber: 58; columnNumber: 103; Attribute
> "title" was already specified for element "field".)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (OFBIZ-6362) Move js & css references from CommonDecorator(s) to themes
[ https://issues.apache.org/jira/browse/OFBIZ-6362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6362: --- Assignee: Pierre Smits (was: Deepak Dixit) > Move js & css references from CommonDecorator(s) to themes > -- > > Key: OFBIZ-6362 > URL: https://issues.apache.org/jira/browse/OFBIZ-6362 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Affects Versions: Trunk, 16.11.01 >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Minor > Fix For: 16.11.01 > > Attachments: bbasic.zip, OFBIZ-6263-BlueLight-header.ftl.patch, > OFBIZ-6362-bbasic-theme.patch, OFBIZ-6362-BizznessTime-header.ftl.patch, > OFBIZ-6362-BizznessTimeThemeData.xml.patch, > OFBIZ-6362-BlueLightThemeData.xml.patch, OFBIZ-6362-CommonScreens.xml.patch, > OFBIZ-6362-DroppingCrumbs-header.ftl.patch, > OFBIZ-6362-DroppingCrumbsThemeData.xml.patch, > OFBIZ-6362-FlatGrey-header.ftl.patch, OFBIZ-6362-FlatGreyThemeData.xml.patch, > OFBIZ-6362-sunrise-theme.patch, OFBIZ-6362-Tomahawk-header.ftl.patch, > OFBIZ-6362-TomahawkThemeData.xml.patch, sunrise.zip > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-6345) Replacing bsh code with groovy Code in Webtools screens, forms and menus
[ https://issues.apache.org/jira/browse/OFBIZ-6345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6345: --- Assignee: Pierre Smits (was: Jacques Le Roux) > Replacing bsh code with groovy Code in Webtools screens, forms and menus > > > Key: OFBIZ-6345 > URL: https://issues.apache.org/jira/browse/OFBIZ-6345 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Labels: webtools > Fix For: 16.11.01 > > Attachments: OFBIZ-6345-BSH2Groovy-Webtools.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-6343) Replacing bsh code with groovy Code in WorkEffort screens, forms and menus
[ https://issues.apache.org/jira/browse/OFBIZ-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6343: --- Assignee: Pierre Smits (was: Jacques Le Roux) > Replacing bsh code with groovy Code in WorkEffort screens, forms and menus > -- > > Key: OFBIZ-6343 > URL: https://issues.apache.org/jira/browse/OFBIZ-6343 > Project: OFBiz > Issue Type: Sub-task > Components: workeffort >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Fix For: 16.11.01 > > Attachments: OFBIZ-6343-BSH2Groovy-WorkEffort.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-6171) Replace 'Open for Business' references with 'Apache OFBiz'
[ https://issues.apache.org/jira/browse/OFBIZ-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6171: --- Assignee: Pierre Smits (was: Arun Patidar) > Replace 'Open for Business' references with 'Apache OFBiz' > -- > > Key: OFBIZ-6171 > URL: https://issues.apache.org/jira/browse/OFBIZ-6171 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk, 14.12.01 >Reporter: Pierre Smits >Assignee: Pierre Smits > Fix For: 14.12.01, 16.11.01 > > Attachments: OFBIZ-6171-OpenForBusiness.patch > > > Currently the project is referenced in various files with 'Open For > Business'. This should be 'Apache OFBiz' -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-6191) Have configuration options for ordermgr
[ https://issues.apache.org/jira/browse/OFBIZ-6191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6191: --- Assignee: Pierre Smits (was: Jacques Le Roux) > Have configuration options for ordermgr > --- > > Key: OFBIZ-6191 > URL: https://issues.apache.org/jira/browse/OFBIZ-6191 > Project: OFBiz > Issue Type: Sub-task > Components: order >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Labels: configuration, multi-tenant > Fix For: 16.11.01 > > Attachments: OFBIZ-6191-OrderOfbizComponent.patch, > OFBIZ-6191-OrderSystemPropertyData.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-6240) Incorporate the readme for the scrum component
[ https://issues.apache.org/jira/browse/OFBIZ-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6240: --- Assignee: Pierre Smits (was: Jacques Le Roux) > Incorporate the readme for the scrum component > -- > > Key: OFBIZ-6240 > URL: https://issues.apache.org/jira/browse/OFBIZ-6240 > Project: OFBiz > Issue Type: Sub-task > Components: scrum >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Fix For: 16.11.01 > > Attachments: OFBIZ-6240-Scrum-README.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-6190) Have configuration options for sfa
[ https://issues.apache.org/jira/browse/OFBIZ-6190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6190: --- Assignee: Pierre Smits (was: Jacques Le Roux) > Have configuration options for sfa > -- > > Key: OFBIZ-6190 > URL: https://issues.apache.org/jira/browse/OFBIZ-6190 > Project: OFBiz > Issue Type: Sub-task > Components: marketing >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Labels: configuration, multi-tenant, sfa > Fix For: 16.11.01 > > Attachments: OFBIZ-6190-SfaOFBizComponent.patch, > OFBIZ-6190-SfaSystemPropertyData.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-6193) Have configuration options for bi
[ https://issues.apache.org/jira/browse/OFBIZ-6193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6193: --- Assignee: Pierre Smits (was: Jacques Le Roux) > Have configuration options for bi > - > > Key: OFBIZ-6193 > URL: https://issues.apache.org/jira/browse/OFBIZ-6193 > Project: OFBiz > Issue Type: Sub-task > Components: bi >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Labels: bi, configuration, multi-tenant > Fix For: 16.11.01 > > Attachments: OFBIZ-6193-BiOFBizController.patch, > OFBIZ-6193-BiSystemPropertyData.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-6192) Have configuration options for catalog webapp
[ https://issues.apache.org/jira/browse/OFBIZ-6192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6192: --- Assignee: Pierre Smits (was: Jacques Le Roux) > Have configuration options for catalog webapp > - > > Key: OFBIZ-6192 > URL: https://issues.apache.org/jira/browse/OFBIZ-6192 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Labels: catalog, configuration, multi-tenant > Fix For: 16.11.01 > > Attachments: OFBIZ-6192-CatalogOfbizComponent.patch, > OFBIZ-6192-ProductSystemPropertyData.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-5812) Move Portal Mgt functions in MyPortal
[ https://issues.apache.org/jira/browse/OFBIZ-5812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-5812: --- Assignee: Pierre Smits (was: Jacques Le Roux) > Move Portal Mgt functions in MyPortal > - > > Key: OFBIZ-5812 > URL: https://issues.apache.org/jira/browse/OFBIZ-5812 > Project: OFBiz > Issue Type: Improvement > Components: framework, myportal >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Labels: admin, portalPage > Fix For: 16.11.01 > > Attachments: OFBIZ-5812-MyPortalAdmin.patch, > OFBIZ-5812-MyPortalMenus.xml.patch, OFBIZ-5812MyPortalUiLabels.patch > > > Portal page admin functionalities are included in WebTools, but should be > also in MyPortal for those users that don't have access to WebTools. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-5757) Remove tenant data from the demo data set
[ https://issues.apache.org/jira/browse/OFBIZ-5757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-5757: --- Assignee: Pierre Smits (was: Jacques Le Roux) > Remove tenant data from the demo data set > - > > Key: OFBIZ-5757 > URL: https://issues.apache.org/jira/browse/OFBIZ-5757 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Minor > Labels: tenant > Fix For: 16.11.01 > > Attachments: OFBIZ-5757-TenantCleanup.patch > > > The demo data set (in location /framework/entity/data/TenantDemoData.xml) > contains elements to load the tenants DEMO1 and DEMO2 into the implemented > OFBiz setup. > This data set is intended to be loaded into the master tables when a user > wants to explore multity tenancy. However, when a user also wants/needs to > load demo data into the tenant DEMO1 or DEMO2 OFBiz also tries to upload the > demo setup data for each tenant. This is not allowed as tenants do not have > access to tables: > # Tenant > # Tenantdatasource > # etc -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-5707) AddEmplPositionFulfillment allows selection of partygroups and external persons to be selected
[ https://issues.apache.org/jira/browse/OFBIZ-5707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-5707: --- Assignee: Pierre Smits (was: Jacques Le Roux) > AddEmplPositionFulfillment allows selection of partygroups and external > persons to be selected > -- > > Key: OFBIZ-5707 > URL: https://issues.apache.org/jira/browse/OFBIZ-5707 > Project: OFBiz > Issue Type: Bug > Components: humanres >Affects Versions: Release Branch 11.04, Release Branch 12.04, Release > Branch 13.07, Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Fix For: 11.04.06, 12.04.05, 14.12.01, 13.07.01 > > > The selection of a party to fulfill a position within the company or a > department of the company includes all parties in stead of just persons > associated with the internal organisations (and with role EMPLOYEE). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-5673) user in securityPermissionGroup "CONTENT_USER" can't access content application
[ https://issues.apache.org/jira/browse/OFBIZ-5673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-5673: --- Assignee: Pierre Smits (was: Jacques Le Roux) > user in securityPermissionGroup "CONTENT_USER" can't access content > application > --- > > Key: OFBIZ-5673 > URL: https://issues.apache.org/jira/browse/OFBIZ-5673 > Project: OFBiz > Issue Type: Bug > Components: content >Affects Versions: Release Branch 11.04, Release Branch 12.04, Release > Branch 13.07, Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Fix For: 14.12.01, 13.07.01 > > Attachments: OFBiz-5673-Content-Permissions.patch > > > When assigning a user to securityPermissionGroup 'CONTENT_USER' this user > can't log into the content application. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-5814) Move PartyRelationshipAndPartyDetail entity to Party component
[ https://issues.apache.org/jira/browse/OFBIZ-5814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-5814: --- Assignee: Pierre Smits (was: Jacques Le Roux) > Move PartyRelationshipAndPartyDetail entity to Party component > --- > > Key: OFBIZ-5814 > URL: https://issues.apache.org/jira/browse/OFBIZ-5814 > Project: OFBiz > Issue Type: Improvement > Components: scrum >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Fix For: 16.11.01 > > Attachments: OFBIZ-5814-ScrumMoveViewEntity.patch > > > The PartyRelationshipAndPartyDetail is currently in the Scrum component. It > seems to me that this belongs in the Party component. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-5676) User with update permission can't access screens in content application
[ https://issues.apache.org/jira/browse/OFBIZ-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-5676: --- Assignee: Pierre Smits (was: Jacques Le Roux) > User with update permission can't access screens in content application > --- > > Key: OFBIZ-5676 > URL: https://issues.apache.org/jira/browse/OFBIZ-5676 > Project: OFBiz > Issue Type: Bug > Components: content >Affects Versions: Release Branch 11.04, Release Branch 12.04, Release > Branch 13.07, Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Fix For: 11.04.05, 12.04.04, 14.12.01, 13.07.01 > > Attachments: OFBiz-5676-Content-ScreenPermissions.patch > > > When a user has security permission 'CONTENTMGR_UPDATE' he should be able to > access various screens in the content application, but he can't. > This applies to screens associated to menu-items: > Content > DataSource > Content Setup > DataResource Setup > Template > CMS -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OFBIZ-5456) Party logo images not stored in SystemProperty location
[ https://issues.apache.org/jira/browse/OFBIZ-5456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-5456: --- Assignee: Anil K Patel (was: Pierre Smits) > Party logo images not stored in SystemProperty location > --- > > Key: OFBIZ-5456 > URL: https://issues.apache.org/jira/browse/OFBIZ-5456 > Project: OFBiz > Issue Type: Bug > Components: content, party > Environment: multi-server, multi-tenant >Reporter: Pierre Smits >Assignee: Anil K Patel > Fix For: 14.12.01, 13.07.01 > > Attachments: OFBIZ-5456.patch > > > In a multi-server setup we have defined a shared location for storage of > tenant specific images etc. > We have set this location in table SystemProperty as an override to the > default location in content.properties. > Our definition is: > createdTxStamp="2014-01-03 13:55:07.124" description="Default location for > party logo images etc" lastUpdatedStamp="2014-01-03 13:55:07.124" > lastUpdatedTxStamp="2014-01-03 13:55:07.124" > systemPropertyId="content.upload.path.prefix" > systemPropertyValue="/test-data/tenant1/images" systemResourceId="content"/> > However, this setting is not used when when uploading a logo image in > partymgr of the tenant. In stead the default location (as in > content.properties) is used. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OFBIZ-9343) Broken link in page regarding Apache OFBiz PMC Members and Committers
Pierre Smits created OFBIZ-9343: --- Summary: Broken link in page regarding Apache OFBiz PMC Members and Committers Key: OFBIZ-9343 URL: https://issues.apache.org/jira/browse/OFBIZ-9343 Project: OFBiz Issue Type: Bug Components: Confluence Reporter: Pierre Smits Currently the page shows a broken link to the image associated with the late Adrian Crum. Please remove. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OFBIZ-5682) Hardcoded stylesheets and javascript resources
[ https://issues.apache.org/jira/browse/OFBIZ-5682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16193611#comment-16193611 ] Pierre Smits commented on OFBIZ-5682: - It is great to see that this old issue I created still attracts some attention.. > Hardcoded stylesheets and javascript resources > -- > > Key: OFBIZ-5682 > URL: https://issues.apache.org/jira/browse/OFBIZ-5682 > Project: OFBiz > Issue Type: Improvement > Components: cmssite >Affects Versions: Release Branch 11.04, Release Branch 12.04, Release > Branch 13.07, Trunk >Reporter: Pierre Smits >Assignee: Deepak Dixit > > The 'HtmlHead.ftl' file of the cmssite component contains following hardcoded > style sheet and javascript resources: > * /images/fieldlookup.js > * /images/selectall.js > * /images/ecommain.css > * /ecommerce/images/blog.css > * /content/images/contentForum.css -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-10012) Alert message : "Developer: for lookups to work you must provide a form name!" appears when try to select contentId from Lookup
[ https://issues.apache.org/jira/browse/OFBIZ-10012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16265949#comment-16265949 ] Pierre Smits commented on OFBIZ-10012: -- Nah.I just wonder when and by whom this was introduced. And which committer allowed this to pass. (but that is just my curiosity). > Alert message : "Developer: for lookups to work you must provide a form > name!" appears when try to select contentId from Lookup > --- > > Key: OFBIZ-10012 > URL: https://issues.apache.org/jira/browse/OFBIZ-10012 > Project: OFBiz > Issue Type: Bug > Components: content >Affects Versions: Trunk >Reporter: Sonal Patwari > Attachments: ContentSearchOptionsAlertShowing (1).png > > > Steps to reproduce: > 1. Go to [Content > Component|https://demo-trunk.ofbiz.apache.org/content/control/main] > 2. Click on Content from > [submenu|https://demo-trunk.ofbiz.apache.org/content/control/findContent]. > 3. Click on the Advanced Search button > [https://demo-trunk.ofbiz.apache.org/content/control/ContentSearchOptions]. > 4. Provide Content Id. > 5. User should be able to see the alert message. > 6. For reference screenshot is attached. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-10012) Alert message : "Developer: for lookups to work you must provide a form name!" appears when try to select contentId from Lookup
[ https://issues.apache.org/jira/browse/OFBIZ-10012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16265808#comment-16265808 ] Pierre Smits commented on OFBIZ-10012: -- Great! > Alert message : "Developer: for lookups to work you must provide a form > name!" appears when try to select contentId from Lookup > --- > > Key: OFBIZ-10012 > URL: https://issues.apache.org/jira/browse/OFBIZ-10012 > Project: OFBiz > Issue Type: Bug > Components: content >Affects Versions: Trunk >Reporter: Sonal Patwari > Attachments: ContentSearchOptionsAlertShowing (1).png > > > Steps to reproduce: > 1. Go to [Content > Component|https://demo-trunk.ofbiz.apache.org/content/control/main] > 2. Click on Content from > [submenu|https://demo-trunk.ofbiz.apache.org/content/control/findContent]. > 3. Click on the Advanced Search button > [https://demo-trunk.ofbiz.apache.org/content/control/ContentSearchOptions]. > 4. Provide Content Id. > 5. User should be able to see the alert message. > 6. For reference screenshot is attached. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-3894) Refactor Email handling
[
https://issues.apache.org/jira/browse/OFBIZ-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16265685#comment-16265685
]
Pierre Smits commented on OFBIZ-3894:
-
HI [~swapnilmmane], all,
All good suggestions.
{quote}I would suggest, we should go in baby steps for implementing this by
creating sub tickets. This will be helpful for reviewing and reduce the chances
of breaking anything.
We can follow proceed with these steps{quote}
Baby steps can be initiated, traced, and concluded through sub-tasks.
{quote}1.) Entity related changes
Update the existing entities by adding new required attributes.
(We will remove the unused fields in the 4rth step){quote}
Per entity a list of (intended) additions, and a list of (intended) removals
will help regarding communications about future release plans, releases,
impact, etc.
{quote}e.g. ProductStoreEmailSetting will have following more attributes
emailTemplateSettingId
fromDate
thruDate
{quote}
The discussion on adding lifespan fields (fromDate and thruDate) to various
entities was already started back in January /2015. It is good to see that it
is still alive. See:
* http://ofbiz.markmail.org/search/?q=lifespan%20field
* https://issues.apache.org/jira/issues/?jql=text%20~%20%22lifespan%22
{quote}4.) Will remove the unused fields from the entity. {quote}
See my comment regarding the quote #1
{quote}5.) Document the migration steps.{quote}
Great to see that this is an integral part of the total implementation. Would
love to see that in place, before mere entity and code changes are released to
adopters.
> Refactor Email handling
> ---
>
> Key: OFBIZ-3894
> URL: https://issues.apache.org/jira/browse/OFBIZ-3894
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: BJ Freeman
>Assignee: Erwan de FERRIERES
>Priority: Minor
> Attachments: OFBIZ-3894.patch, OFBIZ-3894.patch, OFBIZ-3894.patch,
> OFBIZ-3894.patch
>
> Original Estimate: 1,344h
> Remaining Estimate: 1,344h
>
> with the addition of the Website for each component
> 1) create product store for Order entry, or use the B2C product store.
> 2) move the email widgets from ecommerce to order compontent.
> 3) modify the seed data so that Order entry has it own emails from order
> component.this would be to add emails to
> note: as I go through the different items this is turning out to be a bigger
> project than I first anticipated.
> so consider this so far just ideas.
> Maybe break down in to small tasks as I have time to do something.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OFBIZ-9998) Remove paymentId, orderId and orderItemSeqId from finAccountTrans entity
[ https://issues.apache.org/jira/browse/OFBIZ-9998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16265688#comment-16265688 ] Pierre Smits commented on OFBIZ-9998: - I feel it is a pity that the gist of the discussions is not captured in the description of this ticket. And that a reference to a thread seems to be sufficient. So, it is expected that # the developer will ## go through the discussion(s), ## extract the final actionable items (that have the consensus of the community), ## implement the changes; # any reviewer will ## go through the discussions(s), ## extract the final actionable items (that have the consensus of the community) ## review the implemented changes This will introduce a lot of of risk points leading failure. > Remove paymentId, orderId and orderItemSeqId from finAccountTrans entity > > > Key: OFBIZ-9998 > URL: https://issues.apache.org/jira/browse/OFBIZ-9998 > Project: OFBiz > Issue Type: Bug > Components: accounting >Reporter: Vaibhav Jain >Assignee: Ayushi Rathod > > As per the discussion int respective mail thread > [http://ofbiz.markmail.org/message/i2wk2anzrhacbltq?q=%5BPROPOSAL%5D+Extend+returnId+and+shipmentId+in+FinAccountTrans+entity] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9980) Add ability to store latitude and longitude as well while creating postal address
[ https://issues.apache.org/jira/browse/OFBIZ-9980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16265691#comment-16265691 ] Pierre Smits commented on OFBIZ-9980: - Great to know that we *can* do this. But is it something that we *want* to have OOTB and as a default feature regarding the (physical/postal/etc. address) contact mechs? While reviewing the patch, I see only changes to services? I have the feeling that this is just 1 part of a greater set. I wonder what else is needed. > Add ability to store latitude and longitude as well while creating postal > address > - > > Key: OFBIZ-9980 > URL: https://issues.apache.org/jira/browse/OFBIZ-9980 > Project: OFBiz > Issue Type: Improvement >Reporter: Suraj Khurana >Assignee: Suraj Khurana > Attachments: OFBIZ-9980.patch > > > While creating a postal address for any party or facility, we can enable > service to store its latitude and longitude if available and create a geo > point for the same. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9971) Inventory transfer creates unnecessary record with 0
[ https://issues.apache.org/jira/browse/OFBIZ-9971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16265697#comment-16265697 ] Pierre Smits commented on OFBIZ-9971: - An inventory transfer (between 2 locations) can be broken down into multiple transactions (physical and accounting - financial - related). The accounting transaction(s) should always have two records: # one for the location where it is transferred from, e.g.: 1221 Goods in transfer +1000 3001 Inventory Location X -1000 # one for the location where it is transferred into, e.g.: 3002 Inventory Location Y +1000 1221 Goods in transfer - 1000 > Inventory transfer creates unnecessary record with 0 > > > Key: OFBIZ-9971 > URL: https://issues.apache.org/jira/browse/OFBIZ-9971 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk, Release Branch 16.11 >Reporter: Suraj Khurana >Assignee: Akash Jain > Fix For: 16.11.04 > > Attachments: OFBIZ-9971.patch > > > While using inventory transfer for a product having multiple inventory items, > it creates an unnecessary record with 0 transfer quantity. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-10035) Accounting AP and Accounting AR should be removed from Rainbow Top Menu
[ https://issues.apache.org/jira/browse/OFBIZ-10035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16275492#comment-16275492 ] Pierre Smits commented on OFBIZ-10035: -- That can be done through a simple rework of the main menu of Acounting or the the main page of Accounting. > Accounting AP and Accounting AR should be removed from Rainbow Top Menu > --- > > Key: OFBIZ-10035 > URL: https://issues.apache.org/jira/browse/OFBIZ-10035 > Project: OFBiz > Issue Type: Bug >Reporter: Pierre Smits > > Currently the top menu in the Rainbow theme shows" > Accounting > Accounting - AP > Accounting - AR > AP and AR are sub-functions of Accounting and should not be shown. Like we > don't show SalesOrder and PurchaseOrder sub-functions, or IncomingGoods and > OutgoingGoods functions. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-10035) Accounting AP and Accounting AR should be removed from Rainbow Top Menu
Pierre Smits created OFBIZ-10035: Summary: Accounting AP and Accounting AR should be removed from Rainbow Top Menu Key: OFBIZ-10035 URL: https://issues.apache.org/jira/browse/OFBIZ-10035 Project: OFBiz Issue Type: Bug Reporter: Pierre Smits Currently the top menu in the Rainbow theme shows" Accounting Accounting - AP Accounting - AR AP and AR are sub-functions of Accounting and should not be shown. Like we don't show SalesOrder and PurchaseOrder sub-functions, or IncomingGoods and OutgoingGoods functions. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-10032) Move the hhfacility application to Attic
[ https://issues.apache.org/jira/browse/OFBIZ-10032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16275466#comment-16275466 ] Pierre Smits commented on OFBIZ-10032: -- What a pity this did not attract more love since the inception. This is an essential set of functions/services extremely useful in larger warehouses. > Move the hhfacility application to Attic > > > Key: OFBIZ-10032 > URL: https://issues.apache.org/jira/browse/OFBIZ-10032 > Project: OFBiz > Issue Type: Task > Components: hhfacility >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux > Labels: attic > Fix For: Upcoming Release > > > As announced last week on OFBIZ-9978: > bq. Without answers in a week, I'll remove the hhfacility application and > jQuery mobile -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9990) The main logo in screen upper part shows distorted
[ https://issues.apache.org/jira/browse/OFBIZ-9990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16275508#comment-16275508 ] Pierre Smits commented on OFBIZ-9990: - What the logo should be (for best experience) is determined by the house style used. This may be different for: * the website * the wiki * the various themes provided as (options) components of our main product. The themes for the above should be aligned to the house style in play (in general shown via the website); it can be so that little adjustments are required to get a proper fit. The themes provided may deviate from the house style (and do), but the adjusted logos for each should be retained in their appropriate theme component. > The main logo in screen upper part shows distorted > -- > > Key: OFBIZ-9990 > URL: https://issues.apache.org/jira/browse/OFBIZ-9990 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: Upcoming Release > > Attachments: Image 004.png, Image 005.png > > > This is easily checked on trunk demo using > https://demo-trunk.ofbiz.apache.org/catalog/control/main?USERNAME=admin=ofbiz=Y > and Tomahawk theme -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9415) Refactor list related form widgets in various WorkEffort screens
[ https://issues.apache.org/jira/browse/OFBIZ-9415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251177#comment-16251177 ] Pierre Smits commented on OFBIZ-9415: - Thanks Jacques. > Refactor list related form widgets in various WorkEffort screens > > > Key: OFBIZ-9415 > URL: https://issues.apache.org/jira/browse/OFBIZ-9415 > Project: OFBiz > Issue Type: Improvement > Components: workeffort >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Jacques Le Roux > Labels: refactor, widgets > Fix For: Upcoming Release > > Attachments: OFBIZ-9414-WorkEffort-widget.patch > > > Refactoring various list forms into grids > Refactoring various list form references in screens -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9415) Refactor list related form widgets in various WorkEffort screens
[ https://issues.apache.org/jira/browse/OFBIZ-9415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-9415: --- Assignee: Pierre Smits (was: Jacques Le Roux) > Refactor list related form widgets in various WorkEffort screens > > > Key: OFBIZ-9415 > URL: https://issues.apache.org/jira/browse/OFBIZ-9415 > Project: OFBiz > Issue Type: Improvement > Components: workeffort >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Labels: refactor, widgets > Fix For: Upcoming Release > > Attachments: OFBIZ-9414-WorkEffort-widget.patch > > > Refactoring various list forms into grids > Refactoring various list form references in screens -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9269) Check embedded Javascript libs vulnerabilities using retire.js
[
https://issues.apache.org/jira/browse/OFBIZ-9269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259573#comment-16259573
]
Pierre Smits commented on OFBIZ-9269:
-
Hey Jacques,
What is the issue with OpenStreetMap? Does it warrant a separate ticket?
Best regards,
Pierre
> Check embedded Javascript libs vulnerabilities using retire.js
> --
>
> Key: OFBIZ-9269
> URL: https://issues.apache.org/jira/browse/OFBIZ-9269
> Project: OFBiz
> Issue Type: Sub-task
> Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
> Labels: Javascript, retire.js, vulnerabilities
>
> 1+ years ago I created the page
> https://cwiki.apache.org/confluence/display/OFBIZ/About+retire.js
> I just checked again and here are the results
> {code}
> C:\projectsASF\ofbiz-framework\framework\images\webapp\images\jquery\jquery-1.11.0.js
> ? jquery 1.11.0 has known vulnerabilities: severity: medium; issue: 2432,
> summary: 3rd party CORS request may execute;
> https://github.com/jquery/jquery/issues/2432
> http://blog.jquery.com/2016/01/08/jquery-2-2-and-1-12-released/
>
> C:\projectsASF\ofbiz-framework\framework\images\webapp\images\jquery\jquery-migrate-1.2.1.js
> ? jquery-migrate 1.2.1 has known vulnerabilities: severity: medium; bug:
> 11290, summary: Selector interpreted as HTML;
> http://bugs.jquery.com/ticket/11290
> http://research.insecurelabs.org/jquery/test/
> C:\projectsASF\ofbiz-framework\framework\images\webapp\images\jquery\jquery-1.11.0.min.js
> ? jquery 1.11.0.min has known vulnerabilities: severity: medium; issue:
> 2432, summary: 3rd party CORS request may execute;
> https://github.com/jquery/jquery/issues/2432
> http://blog.jquery.com/2016/01/08/jquery-2-2-and-1-12-released/
> C:\projectsASF\ofbiz-framework\plugins\solr\webapp\solr\js\require.js
> ? jquery 1.7.1 has known vulnerabilities: severity: medium; bug: 11290,
> summary: Selector interpreted as HTML; http://bugs.jquery.com/ticket/11290
> http://research.insecurelabs.org/jquery/test/ severity: medium; issue: 2432,
> summary: 3rd party CORS request may execute;
> https://github.com/jquery/jquery/issues/2432
> http://blog.jquery.com/2016/01/08/jquery-2-2-and-1-12-released/
> C:\projectsASF\ofbiz-framework\plugins\solr\webapp\solr\libs\angular.min.js
> ? angularjs 1.3.8 has known vulnerabilities: severity: medium; summary: The
> attribute usemap can be used as a security exploit;
> https://github.com/angular/angular.js/blob/master/CHANGELOG.md severity:
> medium; summary: Universal CSP bypass via add-on in Firefox;
> https://github.com/mozilla/addons-linter/issues/1000#issuecomment-282083435
> http://pastebin.com/raw/kGrdaypP severity: medium; summary: DOS in $sanitize;
> https://github.com/angular/angular.js/blob/master/CHANGELOG.md
> C:\projectsASF\ofbiz-framework\plugins\solr\webapp\solr\libs\angular.js
> ? angularjs 1.3.8 has known vulnerabilities: severity: medium; summary: The
> attribute usemap can be used as a security exploit;
> https://github.com/angular/angular.js/blob/master/CHANGELOG.md severity:
> medium; summary: Universal CSP bypass via add-on in Firefox;
> https://github.com/mozilla/addons-linter/issues/1000#issuecomment-282083435
> http://pastebin.com/raw/kGrdaypP severity: medium; summary: DOS in $sanitize;
> https://github.com/angular/angular.js/blob/master/CHANGELOG.md
> C:\projectsASF\ofbiz-framework\plugins\solr\webapp\solr\libs\jquery-2.1.3.min.js
> ? jquery 2.1.3.min has known vulnerabilities: severity: medium; issue: 2432,
> summary: 3rd party CORS request may execute;
> https://github.com/jquery/jquery/issues/2432
> http://blog.jquery.com/2016/01/08/jquery-2-2-and-1-12-released/
> C:\projectsASF\ofbiz-framework\framework\images\webapp\images\jquery\jquery.mobile\jquery.mobile-1.4.0.js
> ? jquery-mobile 1.4.0 has known vulnerabilities: severity: medium; summary:
> open redirect leads to cross site scripting;
> http://sirdarckcat.blogspot.no/2017/02/unpatched-0day-jquery-mobile-xss.html
>
> C:\projectsASF\ofbiz-framework\framework\images\webapp\images\jquery\jquery.mobile\jquery.mobile-1.4.0.min.js
> ? jquery-mobile 1.4.0.min has known vulnerabilities: severity: medium;
> summary: open redirect leads to cross site scripting;
> http://sirdarckcat.blogspot.no/2017/02/unpatched-0day-jquery-mobile-xss.html
>
> C:\projectsASF\ofbiz-framework\plugins\solr\webapp\solr\js\lib\jquery-1.7.2.min.js
> ? jquery 1.7.2.min has known vulnerabilities: severity: medium; bug: 11290,
> summary: Selector interpreted as HTML; http://bugs.jquery.com/ticket/11290
> http://research.insecurelabs.org/jquery/test/ severity:medium; issue: 2432,
> summary: 3rd party CORS request may execute;
> https://github.com/jquery/jquery/issues/2432
>
[jira] [Commented] (OFBIZ-9990) The main logo in screen upper part shows distorted
[ https://issues.apache.org/jira/browse/OFBIZ-9990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259567#comment-16259567 ] Pierre Smits commented on OFBIZ-9990: - Hi Jacques, This must be related to a particular theme or screen. When looking at demo-trunk (flat-grey theme) in https://demo-trunk.ofbiz.apache.org/webtools/control/FindGeneric?entityName=FinAccountTrans it seems ok. Can you provide screenshots? Best regards, Pierre > The main logo in screen upper part shows distorted > -- > > Key: OFBIZ-9990 > URL: https://issues.apache.org/jira/browse/OFBIZ-9990 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Jacques Le Roux >Priority: Trivial > > This is easily checked on trunk demo -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9991) OpenStreetMap geolocation no longer works
[ https://issues.apache.org/jira/browse/OFBIZ-9991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-9991: Attachment: Screen Shot 2017-11-20 at 19.08.29.png This screenshot shows an OpenStreetMap image in Safari. > OpenStreetMap geolocation no longer works > - > > Key: OFBIZ-9991 > URL: https://issues.apache.org/jira/browse/OFBIZ-9991 > Project: OFBiz > Issue Type: Bug > Components: example >Affects Versions: Trunk >Reporter: Jacques Le Roux >Priority: Minor > Attachments: Screen Shot 2017-11-20 at 19.08.29.png > > > Easily checked at > https://demo-trunk.ofbiz.apache.org/example/control/ExampleOsmGeoLocationPointSet1 > It "works" but OpenStreetMap images are not showing. Locally there are no > errors in log. So hopefully it could be just an OpenStreetMap setting change > we need to do -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9958) Sales by Store report calculates Value Sold incorrectly
[ https://issues.apache.org/jira/browse/OFBIZ-9958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16239498#comment-16239498 ] Pierre Smits commented on OFBIZ-9958: - I believe this ticket can be closed. It is small enough to be considered atomic. > Sales by Store report calculates Value Sold incorrectly > > > Key: OFBIZ-9958 > URL: https://issues.apache.org/jira/browse/OFBIZ-9958 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, > Release Branch 15.12, Release Branch 16.11 >Reporter: Oleg Andreyev >Assignee: Jacques Le Roux > Fix For: Trunk, Release Branch 16.11 > > Attachments: report.diff, sales_by_store_after.png, > sales_by_store_before.png > > > Sales by Store report calculate Value Sold without taking into account order > item quantity. See the first screenshot. It was 2 orders for the same product > priced at $10. One order had 1 of the product, second has 2 of the product. > Sales by Store report display correct quantity sold 3 and incorrect value > sold $20. I guess it should be $30. > The Second screenshot illustrates result after the patch. > Patch is tested with trunk and 16.11. This bug exists from the very > beginning. Perhaps this is not too valuable report if the issue left > unnoticed for so long time. But I have been asked about it twice recently and > I think it's time to fix it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9958) Sales by Store report calculates Value Sold incorrectly
[ https://issues.apache.org/jira/browse/OFBIZ-9958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16239497#comment-16239497 ] Pierre Smits commented on OFBIZ-9958: - Hi [~redcat], Great work, taking on this low hanging fruit to improve the usability of our product. Simple, yet essential reports like these influence businesses to adopt it. And it could be improved even further with: * a split out of total value into gross value, discount and net value. * totals (gross, net, per type of discount) It is one of many small improvements I had in place before offering our ORRTIZ BMS solutions. > Sales by Store report calculates Value Sold incorrectly > > > Key: OFBIZ-9958 > URL: https://issues.apache.org/jira/browse/OFBIZ-9958 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, > Release Branch 15.12, Release Branch 16.11 >Reporter: Oleg Andreyev >Assignee: Jacques Le Roux > Fix For: Trunk, Release Branch 16.11 > > Attachments: report.diff, sales_by_store_after.png, > sales_by_store_before.png > > > Sales by Store report calculate Value Sold without taking into account order > item quantity. See the first screenshot. It was 2 orders for the same product > priced at $10. One order had 1 of the product, second has 2 of the product. > Sales by Store report display correct quantity sold 3 and incorrect value > sold $20. I guess it should be $30. > The Second screenshot illustrates result after the patch. > Patch is tested with trunk and 16.11. This bug exists from the very > beginning. Perhaps this is not too valuable report if the issue left > unnoticed for so long time. But I have been asked about it twice recently and > I think it's time to fix it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-10044) Refactor and cleanup DhlServices.java
[ https://issues.apache.org/jira/browse/OFBIZ-10044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285162#comment-16285162 ] Pierre Smits commented on OFBIZ-10044: -- This, together with all the functions (screens/services/etc.) should move out of the OFBiz-Framework code base and move as a separate component into OFBiz-Plugins. > Refactor and cleanup DhlServices.java > - > > Key: OFBIZ-10044 > URL: https://issues.apache.org/jira/browse/OFBIZ-10044 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: Trunk >Reporter: Michael Brohl >Assignee: Michael Brohl >Priority: Minor > > The DhlServices class contains many TODO comments and needs > refactoring/cleanup. > Hard coded defaults should be moved out to properties or database entries. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-7439) Required field indicator (*) is missing on Project Manager -> My Task Screen
[ https://issues.apache.org/jira/browse/OFBIZ-7439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213891#comment-16213891 ] Pierre Smits commented on OFBIZ-7439: - Please link the discussion on dev ML. > Required field indicator (*) is missing on Project Manager -> My Task Screen > > > Key: OFBIZ-7439 > URL: https://issues.apache.org/jira/browse/OFBIZ-7439 > Project: OFBiz > Issue Type: Sub-task > Components: projectmgr >Affects Versions: Trunk >Reporter: Deepak Nigam >Assignee: Rohit Rai >Priority: Trivial > > Required field indicator (*) is missing for field 'Parent Phase' on screen > Project Manager -> My Task Screen -> Add a new task to one of my projects . -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9555) OFBiz 12 to 16 Migration - Problem in balanceInventoryItems service getting timeout
[ https://issues.apache.org/jira/browse/OFBIZ-9555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213882#comment-16213882 ] Pierre Smits commented on OFBIZ-9555: - Hi [~murugeswari], Unfortunately not many have shared their migration from OFBiz-OlderVersion to OFBiz-NewerVersion. I hope that you reporting on your experiences will trigger others to share, so that the project can extract improvements. Best regards, Pierre > OFBiz 12 to 16 Migration - Problem in balanceInventoryItems service getting > timeout > --- > > Key: OFBIZ-9555 > URL: https://issues.apache.org/jira/browse/OFBIZ-9555 > Project: OFBiz > Issue Type: Bug > Components: manufacturing >Affects Versions: 16.11.01 >Reporter: Murugeswari >Priority: Blocker > > Hi Folks, > We are in the process of Migrating OFBiz 12 to 16 version, other than > "balanceInventoryItems" service everything is working fine. There are 600+ > sales orders for same config product with approved status, when we are trying > to quick complete Production for the same product it getting looping through > and going timeout and taking more than 90 mins for the the > balanceInventoryItems service. No idea why its happening even when we use 12 > code to 16 for this service, its working fine for the same amount of data > set. > Did anybody face the same issue?... and internally its calling some other > service?... > Please any comments will helpful. > Thanks & Regards. > Murugeswari. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9555) OFBiz 12 to 16 Migration - Problem in balanceInventoryItems service getting timeout
[ https://issues.apache.org/jira/browse/OFBIZ-9555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213884#comment-16213884 ] Pierre Smits commented on OFBIZ-9555: - Nevertheless, this should have been raised as a question in the user@ofbiz.a.o. ML > OFBiz 12 to 16 Migration - Problem in balanceInventoryItems service getting > timeout > --- > > Key: OFBIZ-9555 > URL: https://issues.apache.org/jira/browse/OFBIZ-9555 > Project: OFBiz > Issue Type: Bug > Components: manufacturing >Affects Versions: 16.11.01 >Reporter: Murugeswari >Priority: Blocker > > Hi Folks, > We are in the process of Migrating OFBiz 12 to 16 version, other than > "balanceInventoryItems" service everything is working fine. There are 600+ > sales orders for same config product with approved status, when we are trying > to quick complete Production for the same product it getting looping through > and going timeout and taking more than 90 mins for the the > balanceInventoryItems service. No idea why its happening even when we use 12 > code to 16 for this service, its working fine for the same amount of data > set. > Did anybody face the same issue?... and internally its calling some other > service?... > Please any comments will helpful. > Thanks & Regards. > Murugeswari. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (OFBIZ-9555) OFBiz 12 to 16 Migration - Problem in balanceInventoryItems service getting timeout
[ https://issues.apache.org/jira/browse/OFBIZ-9555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213882#comment-16213882 ] Pierre Smits edited comment on OFBIZ-9555 at 10/21/17 12:31 PM: Hi [~muruges] Unfortunately not many have shared their migration from OFBiz-OlderVersion to OFBiz-NewerVersion. I hope that you reporting on your experiences will trigger others to share, so that the project can extract improvements. Best regards, Pierre was (Author: pfm.smits): Hi [~murugeswari], Unfortunately not many have shared their migration from OFBiz-OlderVersion to OFBiz-NewerVersion. I hope that you reporting on your experiences will trigger others to share, so that the project can extract improvements. Best regards, Pierre > OFBiz 12 to 16 Migration - Problem in balanceInventoryItems service getting > timeout > --- > > Key: OFBIZ-9555 > URL: https://issues.apache.org/jira/browse/OFBIZ-9555 > Project: OFBiz > Issue Type: Bug > Components: manufacturing >Affects Versions: 16.11.01 >Reporter: Murugeswari >Priority: Blocker > > Hi Folks, > We are in the process of Migrating OFBiz 12 to 16 version, other than > "balanceInventoryItems" service everything is working fine. There are 600+ > sales orders for same config product with approved status, when we are trying > to quick complete Production for the same product it getting looping through > and going timeout and taking more than 90 mins for the the > balanceInventoryItems service. No idea why its happening even when we use 12 > code to 16 for this service, its working fine for the same amount of data > set. > Did anybody face the same issue?... and internally its calling some other > service?... > Please any comments will helpful. > Thanks & Regards. > Murugeswari. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9677) In packing, only use reservations with stock on hand
[ https://issues.apache.org/jira/browse/OFBIZ-9677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213885#comment-16213885 ] Pierre Smits commented on OFBIZ-9677: - I agree. You can only pick/pack what is on Hand (QoH). > In packing, only use reservations with stock on hand > > > Key: OFBIZ-9677 > URL: https://issues.apache.org/jira/browse/OFBIZ-9677 > Project: OFBiz > Issue Type: Bug > Components: product >Affects Versions: Trunk >Reporter: Paul Foxworthy >Assignee: Paul Foxworthy > Labels: pack, reservation > Attachments: OFBIZ-9677_PackingIgnoreBackorderReservations.patch > > > During packing, OFBiz looks for reservations (OrderItemShipGrpInvRes) for the > order item. Some reservations are for back ordered items not on hand. These > reservations should not be used during packing, but they are. > The attached patch fixes this. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9756) Required field indicator (*) is missing from create contact list.
[ https://issues.apache.org/jira/browse/OFBIZ-9756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213899#comment-16213899 ] Pierre Smits commented on OFBIZ-9756: - Clean, simple patch. Looking forward to seeing it committed. > Required field indicator (*) is missing from create contact list. > - > > Key: OFBIZ-9756 > URL: https://issues.apache.org/jira/browse/OFBIZ-9756 > Project: OFBiz > Issue Type: Sub-task > Components: content >Reporter: Rohit Rai >Assignee: Rohit Rai > Attachments: OFBIZ-9756.patch > > > 1. go to content -> website > 2. find websites -> select a website from the link > 3. Click on contact lists from the submenu. > contact list id is a required field, > Quick link to test the issue, > https://demo-trunk.ofbiz.apache.org/content/control/createWebSiteContactList -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9757) Required field indicator (*) is missing on edit data resource role
[ https://issues.apache.org/jira/browse/OFBIZ-9757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213898#comment-16213898 ] Pierre Smits commented on OFBIZ-9757: - Looking forward to seeing it committed. > Required field indicator (*) is missing on edit data resource role > -- > > Key: OFBIZ-9757 > URL: https://issues.apache.org/jira/browse/OFBIZ-9757 > Project: OFBiz > Issue Type: Sub-task > Components: content >Reporter: Rohit Rai >Assignee: Rohit Rai > Attachments: OFBIZ-9757.patch > > > go to, > content -> dataresource -> Find DataResource -> select a data resource from > the list -> role > no required symbol for the required parameters, as a result, service throws > missing parameter error. > direct link to test the issue, > https://localhost:8443/content/control/addDataResourceRole -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-8014) Introduce the "Product" Screen under Party app to manage the products supplied by any supplier
[ https://issues.apache.org/jira/browse/OFBIZ-8014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213905#comment-16213905 ] Pierre Smits commented on OFBIZ-8014: - I agree that in smaller organisation an OFBiz user can have multiple roles. But that should not have us, as a project, combine multiple functions from different components into one... > Introduce the "Product" Screen under Party app to manage the products > supplied by any supplier > -- > > Key: OFBIZ-8014 > URL: https://issues.apache.org/jira/browse/OFBIZ-8014 > Project: OFBiz > Issue Type: New Feature >Affects Versions: Release Branch 14.12, 16.11.01, Release Branch 15.12 >Reporter: Swapnil Shah >Assignee: Yashwant Dhakad > Attachments: SupplierProduct.png > > > Currently, upon logging into the Party application (or login as supplier > itself) and go to any specific supplier view then there is no way to manage > the list of supplied products. > # We can try introducing the "Product" tab/screen along with other tabs. (to > begin with we can simply mimic the Supplier screen from Catalog app e.g., > https://ofbiz-vm.apache.org:8443/catalog/control/EditProductSuppliers?productId=MAT_A_COST) > > # We can also choose to show the "Products" tab for only Parties in supplier > role and later can try to extend for other roles with further needed > refinements. > Please refer to attached screenshot for the same. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-6964) Support for replenishment of a secondary warehouse from a main warehouse
[
https://issues.apache.org/jira/browse/OFBIZ-6964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213857#comment-16213857
]
Pierre Smits commented on OFBIZ-6964:
-
Capturing ongoing and related discussion in dev@ofbiz.a.o
https://lists.apache.org/thread.html/7ef4d562aaf7ebbe793cdc96ae5fc3805dce608ec02a3007c7bffe39@%3Cdev.ofbiz.apache.org%3E
> Support for replenishment of a secondary warehouse from a main warehouse
>
>
> Key: OFBIZ-6964
> URL: https://issues.apache.org/jira/browse/OFBIZ-6964
> Project: OFBiz
> Issue Type: New Feature
> Components: manufacturing, product
>Reporter: Shrenik Bhura
>Assignee: Swapnil Shah
> Labels: features
> Fix For: Upcoming Release
>
> Attachments: screenshot-1.png
>
>
> At the onset let me define a few terms clearly as I mean it in the story
> description below :
> Requirement - A request generated for a particular product for a specific
> quantity that needs to be purchased from a supplier for satisfying certain
> inventory needs of a particular facility.
> Replenishment - A request generated for a particular product for a specific
> quantity that needs to be transferred from a "backup facility" for satisfying
> certain inventory needs of a particular facility.
> Fulfilment - The process of reserving, picking, packing and shipping the
> ordered quantity of product(s) as per a sales order.
> Terms 'warehouse' and 'facility' have been used interchangeably.
> *The Use Case:*
> Consider a scenario wherein there is a website and a physical retail store of
> the same Company.
> Each having its own facility i.e. 1:1 mapping.
> {{Store A (webstore) -> associated with facility 1 (webstore facility)}}
> {{Store B (retailstore) -> associated with facility 2 (retailstore facility)}}
> However, both the stores share the same catalog/products. But both have
> independent inventory requirement and replenishment rules for the same
> product.
> There is a Requirement Method Enum ID (RMEI) of each product which is
> applicable irrespective of the store and supersedes the RMEI defined, if any,
> on a store.
> A product's inventory thresholds (Minimum Stock, Reorder Quantity) are
> independently managed via the facilities tab for the product. A product has
> its ATP and QOH levels on a per facility basis. _Do note that all these
> inventory numbers are at a facility level and has no bearing at a store
> level._
> Where the difficulty crops up with the current implementation is the way
> requirements are generated. A product can have only one RMEI. When an order
> is placed from any store, then based on the combination of a product's RMEI
> and the store mapped facility's inventory threshold, requirements are
> generated. This is without consideration of the inventory status (surplus or
> otherwise) at another facility of the same Company. If a store has multiple
> facilities associated with it then the one defined in the ProductStore entity
> -> inventoryFacilityId field would be considered for picking the inventory
> threshold values and thus for requirement generation.
> Most typical real-world facility arrangements:
> 1. Usually an organisation would have a main facility/warehouse where
> all the purchases are received and sub-facilities which are replenished from
> the main facility after QA, internal processes, etc. OR
> 2. For each product there would be a primary facility where the product
> is received from the supplier (to derive benefits of demographic convenience
> and consumption patterns) and then replenished to other facilities on a
> demand based pull basis.
> To drive efficiencies across an organisation they need methods to consider
> open fulfilment needs, in process purchase orders and inventory levels across
> multiple facilities and thereafter propose inventory transfers across them to
> facilitate better stocking and thus order fulfilment.
> Coming back to our use case, the webstore warehouse is the main facility at
> which incoming shipments from suppliers are received for the entire Company
> but sales order fulfilment happens only for the webstore. The retail
> warehouse is primarily 're-stocked' via replenishment requests raised upon
> the webstore warehouse and thus need not issue direct purchase orders to
> suppliers. However, if the need be, requirement generated based on the
> product's RMEI and the retail facility's inventory thresholds can also be
> approved, converted into Purchase order and issued.
> *Proposed Solution:*
> There doesn't seem to be an out of the box solution for this in OFBiz. This
> could work if either we think of -
> Approach A: Setting RMEI at a ProductFacility level as well which shall
> supersede the Product level RMEI
[jira] [Commented] (OFBIZ-9500) Maintain accountingQuantity for all COGS valuation methods
[ https://issues.apache.org/jira/browse/OFBIZ-9500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213868#comment-16213868 ] Pierre Smits commented on OFBIZ-9500: - I agree. Without any other requirements/scenarios/use cases brought forward, this should be fixed rather sooner than later. Keep up the good work, Paul. > Maintain accountingQuantity for all COGS valuation methods > -- > > Key: OFBIZ-9500 > URL: https://issues.apache.org/jira/browse/OFBIZ-9500 > Project: OFBiz > Issue Type: Improvement > Components: accounting, order, product >Affects Versions: Trunk >Reporter: Paul Foxworthy >Assignee: Paul Foxworthy > Labels: accounting, inventory, stock, valuation > > From > http://ofbiz.135035.n4.nabble.com/AccountingQuantity-COGS-method-and-inventory-valuation-td4700867.html > *Why accounting quantity?* > When inventory is shipped, there's an accounting transaction that debits the > inventory on hand value and credits Cost of Goods Sold (COGS). > There's more than one way of deciding what value is added to COGS. > First and most obvious is the actual cost of the inventory item. But > companies may prefer other strategies. OFBiz has the option of three others: > average cost, first-in-first-out or last-in-first-out. There's a nice survey > of _why_ you might choose one of these at > http://www.dummies.com/business/operations-management/choosing-an-accounting-method-for-the-cost-of-goods-sold-expense/, > > http://www.dummies.com/business/accounting/the-fifo-method-for-cost-of-goods-sold/, > > http://www.dummies.com/business/accounting/the-lifo-method-for-cost-of-goods-sold/ > > Note that if you choose anything other than inventory item cost, the money > amount transferred to the COGS account may be *different* to the cost price > of the inventory items being shipped. When you choose FIFO or LIFO, the > amount may have originated from a different inventory item, received at a > different time. > *Current situation in OFBiz* > The cogsMethodId field in the PartyAcctgPreference entity is a enum with four > possible values: COGS_INV_COST, COGS_AVG_COST, COGS_FIFO, COGS_LIFO.. > The accountingQuantity field in the InventoryItem entity and > accountingQuantityDiff in the InventoryItemDetail entity track the quantity > of an item still "live" for the purpose of inventory valuation and COGS. > In the service createAcctgTransForShipmentReceipt implemented in > /applications/accounting/minilang/ledger/GeneralLedgerServices.xml > (http://svn.apache.org/viewvc/ofbiz/ofbiz-framework/trunk/applications/accounting/minilang/ledger/GeneralLedgerServices.xml?view=markup#l1306) > > the accountingQuantity is always set to the same value as the quantity > received (i.e. the same as the quantityOnHand) for a newly received inventory > item regardless of the COGS method. > When items are shipped, the service createAcctgTransForSalesShipmentIssuance > will only reduce the accounting quantity if the COGS method is FIFO or LIFO > (http://svn.apache.org/viewvc/ofbiz/ofbiz-framework/trunk/applications/accounting/minilang/ledger/GeneralLedgerServices.xml?view=markup#l1127). > With FIFO, when an item is shipped, inventory items for the product with a > non-zero accounting quantity are found sorted from earliest to latest > received. The quantity of the item shipped must be decremented from the > accounting quantities, starting with the earliest. Similarly, with LIFO, > items are sorted from latest to earliest, and the latest item or items are > decremented. > In other words, if you have chosen a COGS method of COGS_INV_COST or > COGS_AVG_COST, the accounting quantity is meaningless and in OFBiz as of > now, should be ignored. > And yet, the Inventory Valuation report uses accounting quantity, regardless > of the the COGS method > (http://svn.apache.org/viewvc/ofbiz/ofbiz-framework/trunk/applications/accounting/widget/ReportFinancialSummaryForms.xml?view=markup#l535). > In other words, the Inventory Valuation report is broken for COGS methods of > COGS_INV_COST or COGS_AVG_COST. > *What should happen* > The Inventory Valuation report, and anybody else who cares, should always be > able to trust the accounting quantity. For COGS_INV_COST and COGS_AVG_COST, > maintaining the accounting quantity is simple - > createAcctgTransForSalesShipmentIssuance should just adjust it to match the > remaining quantity on hand for the InventoryItem. > So shipping an InventoryItem may cause adjustments to accounting quantities > in other items for FIFO and LIFO, but when the COGS method is actual or > average cost, the adjustment is always in-place - the actual InventoryItem > being shipped. > No matter what the COGS method, the total accounting quantity for a product >
[jira] [Commented] (OFBIZ-5321) Facility main screen relies on demo data
[ https://issues.apache.org/jira/browse/OFBIZ-5321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213888#comment-16213888 ] Pierre Smits commented on OFBIZ-5321: - Maybe this ticket should be closed? > Facility main screen relies on demo data > > > Key: OFBIZ-5321 > URL: https://issues.apache.org/jira/browse/OFBIZ-5321 > Project: OFBiz > Issue Type: Bug > Components: product >Affects Versions: Release Branch 11.04, Release Branch 12.04, Release > Branch 13.07, Trunk >Reporter: Jacques Le Roux >Priority: Minor > > In facility you are normally supposed to choose a facility on main page. > Because the POS component was removed in 13.07 it had a small side effect. > You can't anymore choose one facility. Because there is only one so you get > directly to the update page of the web facility, which is confusing. > Moreover, to see the Report menu (and maybe others) you need to "update" (no > changes) the facility. > The Facility main screen was not designed to support a system with just one > facility defined and the issue is now evident in 13.07 because the demo > facility defined in the POS component (facilityId="MyRetailStore") is no more > loaded. We should not rely on demo data for the proper functioning of the > system. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9595) Move config data related to PaymentGateway configuration from seed-initial to demo
[ https://issues.apache.org/jira/browse/OFBIZ-9595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213887#comment-16213887 ] Pierre Smits commented on OFBIZ-9595: - The best practice with demo data files is to have the file name include 'Demo'. Please rename to PayGatewayDemoData.xml. > Move config data related to PaymentGateway configuration from seed-initial to > demo > -- > > Key: OFBIZ-9595 > URL: https://issues.apache.org/jira/browse/OFBIZ-9595 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Deepak Dixit >Assignee: Deepak Dixit > Fix For: Upcoming Release > > Attachments: OFBIZ-9595.patch > > > We have different config data related to PaymentGateway configuration in > PaymentGatewayConfData.xml, This should be part of demo data, > these kind of data may change as per staging/production account. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9154) Allow developer to load up-to-date and industry-specific demo data
[ https://issues.apache.org/jira/browse/OFBIZ-9154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213901#comment-16213901 ] Pierre Smits commented on OFBIZ-9154: - There are ample ways to have industry-specific data incorporated into an implementation. Users can manually type in via functions under web tools, can upload via xml files in web tools, can insert/update directly into the underlying rdbms, etc. This ticket is not a project issue, without more - specific - details and can be closed. > Allow developer to load up-to-date and industry-specific demo data > -- > > Key: OFBIZ-9154 > URL: https://issues.apache.org/jira/browse/OFBIZ-9154 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: James Yong >Priority: Minor > > 1) Allow developer to load demo data that are relevant to an industry. For > example, if the developer is targeting on the food industry, there is no need > to load demo products relating to IT parts. > 2) Review outdated demo data as discussed in OFBIZ-7766 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9747) Error while updating Agreement
[ https://issues.apache.org/jira/browse/OFBIZ-9747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213908#comment-16213908 ] Pierre Smits commented on OFBIZ-9747: - +1 on having a more user-friendly error message -1 on having calling ensurePartyRole, as this would mean that every mistake leads to the mistaken party having the role which could have serious ramifications down the line. > Error while updating Agreement > --- > > Key: OFBIZ-9747 > URL: https://issues.apache.org/jira/browse/OFBIZ-9747 > Project: OFBiz > Issue Type: Bug > Components: accounting > Environment: > https://demo-trunk.ofbiz.apache.org/accounting/control/updateAgreement >Reporter: Padmavati Rawat > Attachments: ErroronAgreement.png > > > Steps: > 1. Search any existing Agreement. > 2. Click on the update button. > 3. Try to change the Role Type Id From, Role Type Id To and Agreement Type Id. > 4. Click on submit button. > Actual: > Error displayed on the screen on clicking submit button. -- 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=16213909#comment-16213909 ] Pierre Smits commented on OFBIZ-9696: - Please list the thread of the discussion. > 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 > Fix For: Upcoming Release > > 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] [Commented] (OFBIZ-9761) Update regex used for validating credit cards
[ https://issues.apache.org/jira/browse/OFBIZ-9761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213911#comment-16213911 ] Pierre Smits commented on OFBIZ-9761: - I guess that new credit cards pop up frequently. A page in confluence where to find additional information on credit cards and their regex would be highly appreciated by adopters/developers, etc. > Update regex used for validating credit cards > -- > > Key: OFBIZ-9761 > URL: https://issues.apache.org/jira/browse/OFBIZ-9761 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Amit Gadaley >Assignee: Amit Gadaley > Fix For: Trunk > > Attachments: OFBIZ-9761.patch > > > Update regex used for validating credit cards: > MasterCard numbers either start with the numbers 51 through 55 or with the > numbers 2221 through 2720. All have 16 digits. > Discover card numbers begin with 6011 or 65. All have 16 digits. > JCB cards beginning with 2131 or 1800 have 15 digits. JCB cards beginning > with 35 have 16 digits. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-7741) Address scope peculiarities within search/find functionality of projectmgr
[ https://issues.apache.org/jira/browse/OFBIZ-7741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16457484#comment-16457484 ] Pierre Smits commented on OFBIZ-7741: - See attached screenshot 'projectmgr-projectsearch-admin.png' showing that a project with scopeEnumId = "WES_CONFIDENTIAL" is visibility to a party not assigned to the project (see screenshot 'projectmgr-summary-admin.png'). Having confidential project visible to parties outside of the scope (parties assigned) defies the definition of confidential. > Address scope peculiarities within search/find functionality of projectmgr > -- > > Key: OFBIZ-7741 > URL: https://issues.apache.org/jira/browse/OFBIZ-7741 > Project: OFBiz > Issue Type: Improvement > Components: projectmgr >Reporter: Pierre Smits >Priority: Critical > Attachments: projectmgr-projectsearch-admin.png, > projectmgr-summary-admin.png > > > Currently the search/find functions in the projectmgr component also > retrieves projects a user is not a participant in. This is especially > critical regarding projects with scope 'WES_PRIVATE - private' or > 'WES_CONFIDENTIAL - confidential'. > These project may only be search for/found by users that are exlicit > participants of the projects. This over ruless the generic permissions of > 'PROJECTMGR_ADMIN' or 'PROJECTMGR_VIEW'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-7741) Address scope peculiarities within search/find functionality of projectmgr
[ https://issues.apache.org/jira/browse/OFBIZ-7741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-7741: Affects Version/s: 16.11.05 17.12.01 Trunk 16.11.04 > Address scope peculiarities within search/find functionality of projectmgr > -- > > Key: OFBIZ-7741 > URL: https://issues.apache.org/jira/browse/OFBIZ-7741 > Project: OFBiz > Issue Type: Improvement > Components: projectmgr >Affects Versions: Trunk, 17.12.01, 16.11.04, 16.11.05 >Reporter: Pierre Smits >Priority: Critical > Attachments: projectmgr-projectsearch-admin.png, > projectmgr-summary-admin.png > > > Currently the search/find functions in the projectmgr component also > retrieves projects a user is not a participant in. This is especially > critical regarding projects with scope 'WES_PRIVATE - private' or > 'WES_CONFIDENTIAL - confidential'. > These project may only be search for/found by users that are exlicit > participants of the projects. This over ruless the generic permissions of > 'PROJECTMGR_ADMIN' or 'PROJECTMGR_VIEW'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-7741) Address scope peculiarities within search/find functionality of projectmgr
[ https://issues.apache.org/jira/browse/OFBIZ-7741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-7741: Attachment: projectmgr-summary-admin.png > Address scope peculiarities within search/find functionality of projectmgr > -- > > Key: OFBIZ-7741 > URL: https://issues.apache.org/jira/browse/OFBIZ-7741 > Project: OFBiz > Issue Type: Improvement > Components: projectmgr >Reporter: Pierre Smits >Priority: Critical > Attachments: projectmgr-projectsearch-admin.png, > projectmgr-summary-admin.png > > > Currently the search/find functions in the projectmgr component also > retrieves projects a user is not a participant in. This is especially > critical regarding projects with scope 'WES_PRIVATE - private' or > 'WES_CONFIDENTIAL - confidential'. > These project may only be search for/found by users that are exlicit > participants of the projects. This over ruless the generic permissions of > 'PROJECTMGR_ADMIN' or 'PROJECTMGR_VIEW'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-7741) Address scope peculiarities within search/find functionality of projectmgr
[ https://issues.apache.org/jira/browse/OFBIZ-7741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16457442#comment-16457442 ] Pierre Smits commented on OFBIZ-7741: - Hello [~mleila], I experienced this issue almost 2 years ago. It might have been resolved since then. Best regards, Pierre > Address scope peculiarities within search/find functionality of projectmgr > -- > > Key: OFBIZ-7741 > URL: https://issues.apache.org/jira/browse/OFBIZ-7741 > Project: OFBiz > Issue Type: Improvement > Components: projectmgr >Reporter: Pierre Smits >Priority: Critical > > Currently the search/find functions in the projectmgr component also > retrieves projects a user is not a participant in. This is especially > critical regarding projects with scope 'WES_PRIVATE - private' or > 'WES_CONFIDENTIAL - confidential'. > These project may only be search for/found by users that are exlicit > participants of the projects. This over ruless the generic permissions of > 'PROJECTMGR_ADMIN' or 'PROJECTMGR_VIEW'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10382) Scope of project is not shown
[ https://issues.apache.org/jira/browse/OFBIZ-10382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-10382: - Attachment: projectmgr-projectsearch-DemoEmployee1.png > Scope of project is not shown > - > > Key: OFBIZ-10382 > URL: https://issues.apache.org/jira/browse/OFBIZ-10382 > Project: OFBiz > Issue Type: Improvement > Components: projectmgr >Affects Versions: Trunk, 17.12.01, 16.11.04, 16.11.05 >Reporter: Pierre Smits >Priority: Minor > Attachments: projectmgr-main-DemoEmployee1.png, > projectmgr-projectsearch-DemoEmployee1.png, projectmgr-summary-admin.png > > > Currently the scope of a project is not shown in the main overview, the > projectmgr search/find function for projects, and the project summary. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10382) Scope of project is not shown
Pierre Smits created OFBIZ-10382: Summary: Scope of project is not shown Key: OFBIZ-10382 URL: https://issues.apache.org/jira/browse/OFBIZ-10382 Project: OFBiz Issue Type: Improvement Components: projectmgr Affects Versions: 16.11.04, Trunk, 17.12.01, 16.11.05 Reporter: Pierre Smits Attachments: projectmgr-main-DemoEmployee1.png, projectmgr-summary-admin.png Currently the scope of a project is not shown in the main overview, the projectmgr search/find function for projects, and the project summary. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10382) Scope of project is not shown
[ https://issues.apache.org/jira/browse/OFBIZ-10382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-10382: - Attachment: projectmgr-main-DemoEmployee1.png > Scope of project is not shown > - > > Key: OFBIZ-10382 > URL: https://issues.apache.org/jira/browse/OFBIZ-10382 > Project: OFBiz > Issue Type: Improvement > Components: projectmgr >Affects Versions: Trunk, 17.12.01, 16.11.04, 16.11.05 >Reporter: Pierre Smits >Priority: Minor > Attachments: projectmgr-main-DemoEmployee1.png, > projectmgr-summary-admin.png > > > Currently the scope of a project is not shown in the main overview, the > projectmgr search/find function for projects, and the project summary. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10382) Scope of project is not shown
[ https://issues.apache.org/jira/browse/OFBIZ-10382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-10382: - Attachment: projectmgr-summary-admin.png > Scope of project is not shown > - > > Key: OFBIZ-10382 > URL: https://issues.apache.org/jira/browse/OFBIZ-10382 > Project: OFBiz > Issue Type: Improvement > Components: projectmgr >Affects Versions: Trunk, 17.12.01, 16.11.04, 16.11.05 >Reporter: Pierre Smits >Priority: Minor > Attachments: projectmgr-main-DemoEmployee1.png, > projectmgr-summary-admin.png > > > Currently the scope of a project is not shown in the main overview, the > projectmgr search/find function for projects, and the project summary. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-7741) Address scope peculiarities within search/find functionality of projectmgr
[ https://issues.apache.org/jira/browse/OFBIZ-7741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-7741: Attachment: projectmgr-projectsearch-admin.png > Address scope peculiarities within search/find functionality of projectmgr > -- > > Key: OFBIZ-7741 > URL: https://issues.apache.org/jira/browse/OFBIZ-7741 > Project: OFBiz > Issue Type: Improvement > Components: projectmgr >Reporter: Pierre Smits >Priority: Critical > Attachments: projectmgr-projectsearch-admin.png > > > Currently the search/find functions in the projectmgr component also > retrieves projects a user is not a participant in. This is especially > critical regarding projects with scope 'WES_PRIVATE - private' or > 'WES_CONFIDENTIAL - confidential'. > These project may only be search for/found by users that are exlicit > participants of the projects. This over ruless the generic permissions of > 'PROJECTMGR_ADMIN' or 'PROJECTMGR_VIEW'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10398) Rename deletePartyContactMechPurpose* services
[ https://issues.apache.org/jira/browse/OFBIZ-10398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16473005#comment-16473005 ] Pierre Smits commented on OFBIZ-10398: -- Thanks [~deepak.dixit], So you feel this ticket should be closed with resolution 'Won't Implement'? > Rename deletePartyContactMechPurpose* services > -- > > Key: OFBIZ-10398 > URL: https://issues.apache.org/jira/browse/OFBIZ-10398 > Project: OFBiz > Issue Type: Improvement > Components: order, party >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Attachments: OFBIZ-10398-rename.patch > > > Both deletePartyContactMechPurposeIfExists and deletePartyContactMechPurpose > are misnomers, as these functions don't delete records but expires those by > setting the thruDate. The misnomers creates unnecessary confusion. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10398) Rename deletePartyContactMechPurpose* services
[ https://issues.apache.org/jira/browse/OFBIZ-10398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-10398: - Attachment: OFBIZ-10398-rename.patch > Rename deletePartyContactMechPurpose* services > -- > > Key: OFBIZ-10398 > URL: https://issues.apache.org/jira/browse/OFBIZ-10398 > Project: OFBiz > Issue Type: Improvement > Components: order, party >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Attachments: OFBIZ-10398-rename.patch > > > Both deletePartyContactMechPurposeIfExists and deletePartyContactMechPurpose > are misnomers, as these functions don't delete records but expires those by > setting the thruDate. The misnomers creates unnecessary confusion. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10398) Rename deletePartyContactMechPurpose* services
[ https://issues.apache.org/jira/browse/OFBIZ-10398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16473055#comment-16473055 ] Pierre Smits commented on OFBIZ-10398: -- The patch does not pass scrutiny? > Rename deletePartyContactMechPurpose* services > -- > > Key: OFBIZ-10398 > URL: https://issues.apache.org/jira/browse/OFBIZ-10398 > Project: OFBiz > Issue Type: Improvement > Components: order, party >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Attachments: OFBIZ-10398-rename.patch > > > Both deletePartyContactMechPurposeIfExists and deletePartyContactMechPurpose > are misnomers, as these functions don't delete records but expires those by > setting the thruDate. The misnomers creates unnecessary confusion. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10398) Rename deletePartyContactMechPurpose* services
[ https://issues.apache.org/jira/browse/OFBIZ-10398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16473078#comment-16473078 ] Pierre Smits commented on OFBIZ-10398: -- We can also, when the patch passes scrutiny, commit it as is. And address the suggestions in subsequent tickets. > Rename deletePartyContactMechPurpose* services > -- > > Key: OFBIZ-10398 > URL: https://issues.apache.org/jira/browse/OFBIZ-10398 > Project: OFBiz > Issue Type: Improvement > Components: order, party >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Attachments: OFBIZ-10398-rename.patch > > > Both deletePartyContactMechPurposeIfExists and deletePartyContactMechPurpose > are misnomers, as these functions don't delete records but expires those by > setting the thruDate. The misnomers creates unnecessary confusion. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10398) Rename deletePartyContactMechPurpose* services
Pierre Smits created OFBIZ-10398: Summary: Rename deletePartyContactMechPurpose* services Key: OFBIZ-10398 URL: https://issues.apache.org/jira/browse/OFBIZ-10398 Project: OFBiz Issue Type: Improvement Components: order, party Affects Versions: Trunk Reporter: Pierre Smits Assignee: Pierre Smits Both deletePartyContactMechPurposeIfExists and deletePartyContactMechPurpose are misnomers, as these functions don't delete records but expires those by setting the thruDate. The misnomers creates unnecessary confusion. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10396) All party contact mech should be deleted before creating new one
[ https://issues.apache.org/jira/browse/OFBIZ-10396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472974#comment-16472974 ] Pierre Smits commented on OFBIZ-10396: -- I have create https://issues.apache.org/jira/browse/OFBIZ-10398 and provided a patch there to address the misnomers. > All party contact mech should be deleted before creating new one > > > Key: OFBIZ-10396 > URL: https://issues.apache.org/jira/browse/OFBIZ-10396 > Project: OFBiz > Issue Type: Improvement >Reporter: Suraj Khurana >Assignee: Suraj Khurana >Priority: Major > Attachments: OFBIZ-10396.patch > > > Currently, everywhere in code base, before creating new party contact mech > record, we use > deletePartyContactMechPurposeIfExists service to delete old records. But, > problem is > All previous records should also gets deleted before creating new party > contact mech purpose for a specific purpose type. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-6204) createProductionRunsForOrder to create OrderItemWorkFulfillment for all mandatory preceeding production runs
[ https://issues.apache.org/jira/browse/OFBIZ-6204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6204: --- Assignee: (was: Pierre Smits) > createProductionRunsForOrder to create OrderItemWorkFulfillment for all > mandatory preceeding production runs > > > Key: OFBIZ-6204 > URL: https://issues.apache.org/jira/browse/OFBIZ-6204 > Project: OFBiz > Issue Type: New Feature > Components: manufacturing >Affects Versions: Trunk >Reporter: Christian Carlow >Priority: Major > Attachments: OFBIZ-6204.patch > > > createProductionRunsForOrder service creates OrderItemWorkFulfillment for the > top level production run to fulfill and OrderItemShipGroupAssoc but not for > the child mandatory preceeding ones. I need OrderItemWorkFulfillments > created for all mandatory production runs as well to generate a department > load report which determines the work that must be done based on orders. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-9140) Adding 'navigation-grid-name' to widget-screen.xsd
[ https://issues.apache.org/jira/browse/OFBIZ-9140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-9140: --- Assignee: (was: Pierre Smits) > Adding 'navigation-grid-name' to widget-screen.xsd > -- > > Key: OFBIZ-9140 > URL: https://issues.apache.org/jira/browse/OFBIZ-9140 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Priority: Major > Labels: widget > Attachments: OFBIZ-9140-widget-screen.xsd.patch > > > In screenlets in screen widgets we have the option to set the > 'navigation-form-name' which is used for pagination and list length changes > when the associated form of type='list' warrants such. > As there is also the possibility to use a grid definition as an alternative > to the form definition with type='list', there should also be the ability to > set such grid navigation option in the screenlet. > In order to be able to work with this while developing widget oriented > solutions, there should be a reference included in the widget-screen.xsd. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
