[jira] [Commented] (OFBIZ-7456) Introduce the option to add the new Customer/Supplier while placing the quotes in system if they don't exist already
[ https://issues.apache.org/jira/browse/OFBIZ-7456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17476600#comment-17476600 ] Pierre Smits commented on OFBIZ-7456: - Hi Jacques, I won't go commenting such in a PR already merged. We have a solution in play already. Which has been for years. It is such functionality in the PARTY application. Diluting a special group of functionalities (like the quote solution is, which could easily live as a plugin) with functionalities to create parties, addresses, products, inventory items and invoice payments is something best left to downstream parties. > Introduce the option to add the new Customer/Supplier while placing the > quotes in system if they don't exist already > > > Key: OFBIZ-7456 > URL: https://issues.apache.org/jira/browse/OFBIZ-7456 > Project: OFBiz > Issue Type: New Feature > Components: order >Affects Versions: 14.12.01, 15.12.01 >Reporter: Swapnil Shah >Priority: Major > > On numerous occasions while placing Sales or Purchase quote in system, the > business is conducted first time with given party and its quite possible that > given party don't pre-exist in system. > At that point of time user could be allowed to create the party in either > Customer or Supplier role by asking few primary details as follows: > # Party Name > # Billing/Shipping Address > Rest of the details can be later added/update with respect to added party > from Party screens. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (OFBIZ-12499) Quote - Action Triggers, Permissions & ux
Pierre Smits created OFBIZ-12499: Summary: Quote - Action Triggers, Permissions & ux Key: OFBIZ-12499 URL: https://issues.apache.org/jira/browse/OFBIZ-12499 Project: OFBiz Issue Type: Improvement Components: order Affects Versions: Upcoming Branch Reporter: Pierre Smits Assignee: Pierre Smits Currently, as can be seen in [https://localhost:8443/ordermgr/control/ViewQuote?quoteId=CQ0001,] action triggers (for users with CREATE/UPDATE permissions are located within screens instead of the action menu for quotes. Also triggers can be seen and invoked by users with VIEW permissions. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (OFBIZ-12497) Routing Screens - remove redundant action triggers
[ https://issues.apache.org/jira/browse/OFBIZ-12497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed OFBIZ-12497. Fix Version/s: Upcoming Branch Resolution: Implemented Thanks to Jacques for his assistance to get this into the codebase. > Routing Screens - remove redundant action triggers > -- > > Key: OFBIZ-12497 > URL: https://issues.apache.org/jira/browse/OFBIZ-12497 > Project: OFBiz > Issue Type: Improvement > Components: manufacturing >Affects Versions: Upcoming Branch >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: permission, trust, usability, ux > Fix For: Upcoming Branch > > > With the inclusion of the MainActionMenu for the Manufacturing application, > several screens in RoutingScreens.xml now have redundant and obsolete action > triggers also available in the MainActionMenu. > These obsolete action triggers must be removed, as these don't adhere to > common permission conventions. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (OFBIZ-12498) Invoice Screens - consistency in ux
[ https://issues.apache.org/jira/browse/OFBIZ-12498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed OFBIZ-12498. Resolution: Implemented Thanks to Jacques for his assistance to get this into the codebase. > Invoice Screens - consistency in ux > --- > > Key: OFBIZ-12498 > URL: https://issues.apache.org/jira/browse/OFBIZ-12498 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Upcoming Branch >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: consistency, ux > > The majority of the invoice screens have grids encapsulated by a screenlet > widget with a title. However some do not have this. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (OFBIZ-12498) Invoice Screens - consistency in ux
Pierre Smits created OFBIZ-12498: Summary: Invoice Screens - consistency in ux Key: OFBIZ-12498 URL: https://issues.apache.org/jira/browse/OFBIZ-12498 Project: OFBiz Issue Type: Improvement Components: accounting Affects Versions: Upcoming Branch Reporter: Pierre Smits Assignee: Pierre Smits The majority of the invoice screens have grids encapsulated by a screenlet widget with a title. However some do not have this. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (OFBIZ-12497) Routing Screens - remove redundant action triggers
Pierre Smits created OFBIZ-12497: Summary: Routing Screens - remove redundant action triggers Key: OFBIZ-12497 URL: https://issues.apache.org/jira/browse/OFBIZ-12497 Project: OFBiz Issue Type: Improvement Components: manufacturing Affects Versions: Upcoming Branch Reporter: Pierre Smits Assignee: Pierre Smits With the inclusion of the MainActionMenu for the Manufacturing application, several screens in RoutingScreens.xml now have redundant and obsolete action triggers also available in the MainActionMenu. These obsolete action triggers must be removed, as these don't adhere to common permission conventions. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-12496) Webapp Position overrides older entries
[ https://issues.apache.org/jira/browse/OFBIZ-12496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17475549#comment-17475549 ] Pierre Smits commented on OFBIZ-12496: -- Hi [~bjugl] First of all: Happy New Year to you too. May this year bring lots of health, happiness and interesting moments. Before going into your question, could you elaborate on where the current functionality resides? In other words which component c.q. function (file)? > Webapp Position overrides older entries > --- > > Key: OFBIZ-12496 > URL: https://issues.apache.org/jira/browse/OFBIZ-12496 > Project: OFBiz > Issue Type: Bug > Components: ALL COMPONENTS >Reporter: Benjamin Jugl >Assignee: Benjamin Jugl >Priority: Minor > > The Algorithm deciding where the actual position is in the menu is faulty. If > a later plugin is defined with position=1, the Party Manager that is defined > as position=1 by default is overwritten and does not appear in the menu > anymore. > I can provide a quick fix that shifts the newer app to the end of the line, > so no entry is lost. Ultimately we should find a solution that offers more > control. > One possible solution might be, to leave the current implementation but add a > functionality that enables themes to override this and establish their own > order. > What Do you think? -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (OFBIZ-12495) Request Roles - VIEW permission
Pierre Smits created OFBIZ-12495: Summary: Request Roles - VIEW permission Key: OFBIZ-12495 URL: https://issues.apache.org/jira/browse/OFBIZ-12495 Project: OFBiz Issue Type: Improvement Components: order Affects Versions: Upcoming Branch Reporter: Pierre Smits Assignee: Pierre Smits Currently, a user with only 'VIEW' permissions, as demonstrated in trunk demo with userId = auditor, accessing the Request Roles screen, sees editable fields and/or triggers (to requests) reserved for users with 'CREATE' or 'UPDATE' permissions. https://localhost:8443/ordermgr/control/requestroles?custRequestId=9000 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (OFBIZ-12494) Move edit of Request RequestSubTabBar
Pierre Smits created OFBIZ-12494: Summary: Move edit of Request RequestSubTabBar Key: OFBIZ-12494 URL: https://issues.apache.org/jira/browse/OFBIZ-12494 Project: OFBiz Issue Type: Improvement Components: order Affects Versions: Upcoming Branch Reporter: Pierre Smits Assignee: Pierre Smits n general, a TabBar menu is intended to give users access to overviews related to the . And a SubTabBar menu is intended to give users access to actions to be performed on the , like status changes, adding new related records, etc. The menu-item for editing a request is currently located in the RequestTabBar menu in OrderMenus.xml. Given that this menu-item is intended for users with UPDATE permissions and to give those users access to a screen to edit the data, this menu-item must move to the RequestSubTabBar menu. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (OFBIZ-12493) Config Screen - VIEW permissionn
Pierre Smits created OFBIZ-12493: Summary: Config Screen - VIEW permissionn Key: OFBIZ-12493 URL: https://issues.apache.org/jira/browse/OFBIZ-12493 Project: OFBiz Issue Type: Improvement Components: product/catalog Affects Versions: Upcoming Branch Reporter: Pierre Smits Assignee: Pierre Smits Currently, a user with only 'VIEW' permissions, as demonstrated in trunk demo with userId = auditor, accessing the config item screen, sees editable fields and/or triggers (to requests) reserved for users with 'CREATE' or 'UPDATE' permissions. See (test with): https://localhost:8443/catalog/control/EditProductConfigItem?configItemId=SC0 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (OFBIZ-12492) Store Screen - VIEW permission
Pierre Smits created OFBIZ-12492: Summary: Store Screen - VIEW permission Key: OFBIZ-12492 URL: https://issues.apache.org/jira/browse/OFBIZ-12492 Project: OFBiz Issue Type: Improvement Components: product/catalog Affects Versions: Upcoming Branch Reporter: Pierre Smits Assignee: Pierre Smits Currently, a user with only 'VIEW' permissions, as demonstrated in trunk demo with userId = auditor, accessing the store screen, sees editable fields and/or triggers (to requests) reserved for users with 'CREATE' or 'UPDATE' permissions. See (test with): https://localhost:8443/catalog/control/EditProductStore?productStoreId=9000 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (OFBIZ-12491) Catalog Screen - VIEW permission
Pierre Smits created OFBIZ-12491: Summary: Catalog Screen - VIEW permission Key: OFBIZ-12491 URL: https://issues.apache.org/jira/browse/OFBIZ-12491 Project: OFBiz Issue Type: Improvement Components: product/catalog Affects Versions: Upcoming Branch Reporter: Pierre Smits Assignee: Pierre Smits Currently, a user with only 'VIEW' permissions, as demonstrated in trunk demo with userId = auditor, accessing the catalog screen, sees editable fields and/or triggers (to requests) reserved for users with 'CREATE' or 'UPDATE' permissions. See (test with): https://localhost:8443/catalog/control/EditProdCatalog?prodCatalogId=DemoCatalog -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (OFBIZ-12490) Category Products - VIEW permissions
Pierre Smits created OFBIZ-12490: Summary: Category Products - VIEW permissions Key: OFBIZ-12490 URL: https://issues.apache.org/jira/browse/OFBIZ-12490 Project: OFBiz Issue Type: Improvement Components: product/catalog Affects Versions: Upcoming Branch Reporter: Pierre Smits Assignee: Pierre Smits Currently, a user with only 'VIEW' permissions, as demonstrated in trunk demo with userId = auditor, accessing the category products screen, sees editable fields and/or triggers (to requests) reserved for users with 'CREATE' or 'UPDATE' permissions. See (test with): https://localhost:8443/catalog/control/EditCategoryProducts?productCategoryId=100 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (OFBIZ-12489) Product Prices - VIEW permissions
Pierre Smits created OFBIZ-12489: Summary: Product Prices - VIEW permissions Key: OFBIZ-12489 URL: https://issues.apache.org/jira/browse/OFBIZ-12489 Project: OFBiz Issue Type: Improvement Components: product/catalog Affects Versions: Upcoming Branch Reporter: Pierre Smits Assignee: Pierre Smits Currently, a user with only 'VIEW' permissions, as demonstrated in trunk demo with userId = auditor, accessing the product prices screen, sees editable fields and/or triggers (to requests) reserved for users with 'CREATE' or 'UPDATE' permissions. See (test with): https://localhost:8443/catalog/control/EditProductPrices?productId=WG-9943 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (OFBIZ-12440) Move edit of invoice header to InvoiceSubTabBar
[ https://issues.apache.org/jira/browse/OFBIZ-12440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed OFBIZ-12440. Resolution: Implemented Thanks to Jacques for his assistance to get this into the codebase. Merged. See https://github.com/apache/ofbiz-framework/commit/bbe64fa19e037149d8c310c171dec0491a7e4994 > Move edit of invoice header to InvoiceSubTabBar > --- > > Key: OFBIZ-12440 > URL: https://issues.apache.org/jira/browse/OFBIZ-12440 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk, Upcoming Branch >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: consistency, invoice, permissions,, usability > > In general, a TabBar menu is intended to give users access to > overview related to the . And a SubTabBar menu is intended to > give users to actions to be performed on the , like status changes, > adding new records, etc. > The menu-item for editing the invoice header (aptly translated as 'Header') > is currently located in the InvoiceTabBar menu in AccountingMenus.xml. > Given that this menu-item is intended for users with UPDATE permissions and > to give those users access to a screen to edit the data, this menu-item must > move to the InvoiceSubTabBar menu. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (OFBIZ-12488) VIEW permissions - Agreement
Pierre Smits created OFBIZ-12488: Summary: VIEW permissions - Agreement Key: OFBIZ-12488 URL: https://issues.apache.org/jira/browse/OFBIZ-12488 Project: OFBiz Issue Type: Improvement Components: accounting Affects Versions: Upcoming Branch Reporter: Pierre Smits Assignee: Pierre Smits Currently, a user with only 'VIEW' permissions, as demonstrated in trunk demo with userId = auditor, accessing the agreement screen, sees editable fields and/or triggers (to requests) reserved for users with 'CREATE' or 'UPDATE' permissions. See (test with): https://localhost:8443/accounting/control/EditAgreement?agreementId=DS-1000-SALES -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (OFBIZ-12487) VIEW permissions - BillingAccount roles
Pierre Smits created OFBIZ-12487: Summary: VIEW permissions - BillingAccount roles Key: OFBIZ-12487 URL: https://issues.apache.org/jira/browse/OFBIZ-12487 Project: OFBiz Issue Type: Improvement Components: accounting Affects Versions: Upcoming Branch Reporter: Pierre Smits Assignee: Pierre Smits Currently, a user with only 'VIEW' permissions, as demonstrated in trunk demo with userId = auditor, accessing the billing account roles screen, sees editable fields and/or triggers (to requests) reserved for users with 'CREATE' or 'UPDATE' permissions. See (test with): https://localhost:8443/accounting/control/EditBillingAccountRoles?billingAccountId=9010 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (OFBIZ-12486) PaymentGroup - action items visible to viewer
Pierre Smits created OFBIZ-12486: Summary: PaymentGroup - action items visible to viewer Key: OFBIZ-12486 URL: https://issues.apache.org/jira/browse/OFBIZ-12486 Project: OFBiz Issue Type: Improvement Components: accounting Affects Versions: Upcoming Branch Reporter: Pierre Smits Assignee: Pierre Smits Menu items to perform actions in PaymentGroupSubTabBar are visible to users with only VIEW permissions. As shows when logged in with userId = auditor. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (OFBIZ-12485) AssetMaint not accessible by user with 'VIEW' permission
Pierre Smits created OFBIZ-12485: Summary: AssetMaint not accessible by user with 'VIEW' permission Key: OFBIZ-12485 URL: https://issues.apache.org/jira/browse/OFBIZ-12485 Project: OFBiz Issue Type: Bug Components: assetmaint/assetmaint Affects Versions: Upcoming Branch Reporter: Pierre Smits Assignee: Pierre Smits Currently the AssetMaint application is not accessible by a user with the VIEW permission, as demonstrated with userLoginId = 'auditor'. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (OFBIZ-12484) Project - MainActionMenu
Pierre Smits created OFBIZ-12484: Summary: Project - MainActionMenu Key: OFBIZ-12484 URL: https://issues.apache.org/jira/browse/OFBIZ-12484 Project: OFBiz Issue Type: Improvement Components: projectmgr Affects Versions: Upcoming Branch Reporter: Pierre Smits Assignee: Pierre Smits Currently the create buttons for the main objects of the project mgt plugin are located within the find and other widgets/templates of those objects. In order to improve the usability of OFBiz (and thus the appeal of it for adopters and users) these create buttons/links/etc. should be in a main action menu visible at all times when a user is working within the component. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (OFBIZ-12483) AssetMaint - MainActionMenu
Pierre Smits created OFBIZ-12483: Summary: AssetMaint - MainActionMenu Key: OFBIZ-12483 URL: https://issues.apache.org/jira/browse/OFBIZ-12483 Project: OFBiz Issue Type: Improvement Components: assetmaint Affects Versions: Upcoming Branch Reporter: Pierre Smits Assignee: Pierre Smits Currently the create buttons for the main objects of the assetmainty plugin are located within the find and other widgets/templates of those objects. In order to improve the usability of OFBiz (and thus the appeal of it for adopters and users) these create buttons/links/etc. should be in a main action menu visible at all times when a user is working within the component. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (OFBIZ-12482) Party - MainActionMenu
Pierre Smits created OFBIZ-12482: Summary: Party - MainActionMenu Key: OFBIZ-12482 URL: https://issues.apache.org/jira/browse/OFBIZ-12482 Project: OFBiz Issue Type: Improvement Components: party Affects Versions: Upcoming Branch Reporter: Pierre Smits Assignee: Pierre Smits Currently the create buttons for the main objects of the party component are located within the find and other widgets/templates of those objects. In order to improve the usability of OFBiz (and thus the appeal of it for adopters and users) these create buttons/links/etc. should be in a main action menu visible at all times when a user is working within the component. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (OFBIZ-11774) Have a Menu in Catalog featuring actions to create the main objects
[ https://issues.apache.org/jira/browse/OFBIZ-11774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed OFBIZ-11774. Fix Version/s: Upcoming Branch Resolution: Implemented Thanks to Jacques for his assistance to get this into the codebase. > Have a Menu in Catalog featuring actions to create the main objects > --- > > Key: OFBIZ-11774 > URL: https://issues.apache.org/jira/browse/OFBIZ-11774 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: menus, refactoring, usability > Fix For: Upcoming Branch > > > Currently the create buttons for the main objects of the catalog components > are located within the find and profile widgets/templates of those object. > In order to improve the usability of OFBiz (and thus the appeal of it for > adopters and users) these create buttons/links/etc. should be in a main > action menu visible at all times when a user is working within the component. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (OFBIZ-12481) Store Group screen don't connect with grids
[ https://issues.apache.org/jira/browse/OFBIZ-12481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed OFBIZ-12481. Resolution: Fixed Thanks to Jacques for his assistance to get this into the codebase. > Store Group screen don't connect with grids > --- > > Key: OFBIZ-12481 > URL: https://issues.apache.org/jira/browse/OFBIZ-12481 > Project: OFBiz > Issue Type: Bug > Components: product/catalog >Affects Versions: Upcoming Branch >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > > Screen EditProductStoreGroupAndAssoc does not connect with grid forms > referenced. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (OFBIZ-12481) Store Group screen don't connect with grids
[ https://issues.apache.org/jira/browse/OFBIZ-12481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-12481: - Affects Version/s: Upcoming Branch > Store Group screen don't connect with grids > --- > > Key: OFBIZ-12481 > URL: https://issues.apache.org/jira/browse/OFBIZ-12481 > Project: OFBiz > Issue Type: Bug > Components: product/catalog >Affects Versions: Upcoming Branch >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > > Screen EditProductStoreGroupAndAssoc does not connect with grid forms > referenced. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (OFBIZ-12481) Store Group screen don't connect with grids
[ https://issues.apache.org/jira/browse/OFBIZ-12481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-12481: - Summary: Store Group screen don't connect with grids (was: Store Group screens don't connect with grids) > Store Group screen don't connect with grids > --- > > Key: OFBIZ-12481 > URL: https://issues.apache.org/jira/browse/OFBIZ-12481 > Project: OFBiz > Issue Type: Bug > Components: product/catalog >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > > Screen EditProductStoreGroupAndAssoc does not connect with grid forms > referenced. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (OFBIZ-12481) Store Group screens don't connect with grids
Pierre Smits created OFBIZ-12481: Summary: Store Group screens don't connect with grids Key: OFBIZ-12481 URL: https://issues.apache.org/jira/browse/OFBIZ-12481 Project: OFBiz Issue Type: Bug Components: product/catalog Reporter: Pierre Smits Assignee: Pierre Smits Screen EditProductStoreGroupAndAssoc does not connect with grid forms referenced. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-11345) Lists and grids
[ https://issues.apache.org/jira/browse/OFBIZ-11345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17471299#comment-17471299 ] Pierre Smits commented on OFBIZ-11345: -- Thanks to Jacques for his assistance to get this into the codebase > Lists and grids > --- > > Key: OFBIZ-11345 > URL: https://issues.apache.org/jira/browse/OFBIZ-11345 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: cleanup, refactoring, widget > Fix For: Upcoming Branch > > > According to the definition in widget-form.xsd the use of a combination of a > form with type="list" is deprecated in favour of a grid. > Refactor various list forms into grids. > Refactor various list form references in screens. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-11345) Lists and grids
[ https://issues.apache.org/jira/browse/OFBIZ-11345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17471026#comment-17471026 ] Pierre Smits commented on OFBIZ-11345: -- Thanks to Jacques for his assistance to get this into the codebase. > Lists and grids > --- > > Key: OFBIZ-11345 > URL: https://issues.apache.org/jira/browse/OFBIZ-11345 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: cleanup, refactoring, widget > Fix For: Upcoming Branch > > > According to the definition in widget-form.xsd the use of a combination of a > form with type="list" is deprecated in favour of a grid. > Refactor various list forms into grids. > Refactor various list form references in screens. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-11345) Lists and grids
[ https://issues.apache.org/jira/browse/OFBIZ-11345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17470453#comment-17470453 ] Pierre Smits commented on OFBIZ-11345: -- Thanks to Jacques for his assistance to get this into the codebase. > Lists and grids > --- > > Key: OFBIZ-11345 > URL: https://issues.apache.org/jira/browse/OFBIZ-11345 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: cleanup, refactoring, widget > Fix For: Upcoming Branch > > > According to the definition in widget-form.xsd the use of a combination of a > form with type="list" is deprecated in favour of a grid. > Refactor various list forms into grids. > Refactor various list form references in screens. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-10093) Replace ELRTE plugin with Trumbowyg
[ https://issues.apache.org/jira/browse/OFBIZ-10093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17470410#comment-17470410 ] Pierre Smits commented on OFBIZ-10093: -- Thanks, Jacques, for the advice. Maybe I will when I can find the time and don't forget. > Replace ELRTE plugin with Trumbowyg > --- > > Key: OFBIZ-10093 > URL: https://issues.apache.org/jira/browse/OFBIZ-10093 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: Aditya Sharma >Assignee: Aditya Sharma >Priority: Major > Fix For: Upcoming Branch > > > As there is no support for elrte since elrte-1.3 > [https://github.com/Studio-42/elRTE] it is to be replaced with some other > good editor & we found Quill Js editor as quite suitable: > * 139 releases > * Good community support of 101 contributors > * Licence - BSD 3-Clause "New" or "Revised" License > Links for reference: > [https://quilljs.com/] > [https://github.com/quilljs/quill] > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (OFBIZ-12451) VIEW permissions FinAccount mutations
[ https://issues.apache.org/jira/browse/OFBIZ-12451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed OFBIZ-12451. Resolution: Implemented Thanks to Jacques for his assistance to get this into the codebase > VIEW permissions FinAccount mutations > - > > Key: OFBIZ-12451 > URL: https://issues.apache.org/jira/browse/OFBIZ-12451 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: financial_account, permissions, usability > > Currently, a user with only 'VIEW' permissions, as demonstrated in trunk demo > with userId = auditor, accessing the Financial Account mutations screen sees > editable fields and/or triggers (to requests) reserved for users with > 'CREATE' or 'UPDATE' permissions. > See (test with): > * > [https://demo-trunk.ofbiz.apache.org/accounting/control/EditFinAccount?finAccountId=ABN_CHECKING] > * > [https://demo-trunk.ofbiz.apache.org/accounting/control/FindPaymentsForDepositOrWithdraw] -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-10093) Replace ELRTE plugin with Trumbowyg
[ https://issues.apache.org/jira/browse/OFBIZ-10093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17470377#comment-17470377 ] Pierre Smits commented on OFBIZ-10093: -- As this (Trumbowyg) is now included in the code base, the description of this ticket should reflect what is actually changed. When this appears in a release, (potential) adopters will look at release notes, and when the release notes references this ticket, the reader will look at the description to get a feel for the change and not necessarily at (all) the comments here or those associated with the PR. > Replace ELRTE plugin with Trumbowyg > --- > > Key: OFBIZ-10093 > URL: https://issues.apache.org/jira/browse/OFBIZ-10093 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: Aditya Sharma >Assignee: Aditya Sharma >Priority: Major > Fix For: Upcoming Branch > > > As there is no support for elrte since elrte-1.3 > [https://github.com/Studio-42/elRTE] it is to be replaced with some other > good editor & we found Quill Js editor as quite suitable: > * 139 releases > * Good community support of 101 contributors > * Licence - BSD 3-Clause "New" or "Revised" License > Links for reference: > [https://quilljs.com/] > [https://github.com/quilljs/quill] > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-9352) Remove unused labels from AccountingUiLabels.xml
[ https://issues.apache.org/jira/browse/OFBIZ-9352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17470025#comment-17470025 ] Pierre Smits commented on OFBIZ-9352: - Thanks to Jacques for his assistance to get this into the codebase. > Remove unused labels from AccountingUiLabels.xml > > > Key: OFBIZ-9352 > URL: https://issues.apache.org/jira/browse/OFBIZ-9352 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Minor > Labels: cleanup > Fix For: Upcoming Branch > > Attachments: OFBIZ-9352-not-used.png > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (OFBIZ-12457) VIEW permissions BillingAccount
[ https://issues.apache.org/jira/browse/OFBIZ-12457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed OFBIZ-12457. Resolution: Implemented Thanks to Jacques for his assistance to get this into the codebase. > VIEW permissions BillingAccount > --- > > Key: OFBIZ-12457 > URL: https://issues.apache.org/jira/browse/OFBIZ-12457 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: billing-account, permissions, usability > > Currently, a user with only 'VIEW' permissions, as demonstrated in trunk demo > with userId = auditor, accessing the billing account screen, sees editable > fields and/or triggers (to requests) reserved for users with 'CREATE' or > 'UPDATE' permissions. > See (test with): > https://demo-trunk.ofbiz.apache.org/accounting/control/EditBillingAccount?billingAccountId=9010 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (OFBIZ-12458) Invoice - CommonInvoiceDecorator
[ https://issues.apache.org/jira/browse/OFBIZ-12458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed OFBIZ-12458. Resolution: Implemented Thanks to Jacques for his assistance to get this into the codebase. > Invoice - CommonInvoiceDecorator > > > Key: OFBIZ-12458 > URL: https://issues.apache.org/jira/browse/OFBIZ-12458 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: invoice, usability > > label for invoice is shown below Invoice menus -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (OFBIZ-12462) Agreement - CommonAgreementDecorator
[ https://issues.apache.org/jira/browse/OFBIZ-12462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed OFBIZ-12462. Resolution: Implemented Thanks to Jacques for his assistance to get this into the codebase > Agreement - CommonAgreementDecorator > > > Key: OFBIZ-12462 > URL: https://issues.apache.org/jira/browse/OFBIZ-12462 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: agreement(s), user-experience > > title of an agreement is shown below its menu(s). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-11345) Lists and grids
[ https://issues.apache.org/jira/browse/OFBIZ-11345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17469865#comment-17469865 ] Pierre Smits commented on OFBIZ-11345: -- Thanks to Jacques for his assistance to get this into the codebase. > Lists and grids > --- > > Key: OFBIZ-11345 > URL: https://issues.apache.org/jira/browse/OFBIZ-11345 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: cleanup, refactoring, widget > Fix For: Upcoming Branch > > > According to the definition in widget-form.xsd the use of a combination of a > form with type="list" is deprecated in favour of a grid. > Refactor various list forms into grids. > Refactor various list form references in screens. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (OFBIZ-11783) Have a Menu in Marketing featuring actions to create the main objects
[ https://issues.apache.org/jira/browse/OFBIZ-11783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed OFBIZ-11783. Resolution: Implemented Thanks to Jacques to get this into the codebase > Have a Menu in Marketing featuring actions to create the main objects > - > > Key: OFBIZ-11783 > URL: https://issues.apache.org/jira/browse/OFBIZ-11783 > Project: OFBiz > Issue Type: Improvement > Components: marketing >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: menus, refactoring, usability > > Currently the create buttons for the main objects of the marketing > application are located within find and profile widgets/templates of those > objects. > In order to improve the usability of this application, OFBiz and thus the > appeal of it for adopters and users, these create buttons/links/etc. should > be in a main action menu visible at all times when a user is working within > the appliclation of the component. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (OFBIZ-11777) Have a Menu in Humanres featuring actions to create the main objects
[ https://issues.apache.org/jira/browse/OFBIZ-11777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed OFBIZ-11777. Resolution: Implemented Thanks to Jacques for getting this into the repository. > Have a Menu in Humanres featuring actions to create the main objects > > > Key: OFBIZ-11777 > URL: https://issues.apache.org/jira/browse/OFBIZ-11777 > Project: OFBiz > Issue Type: Improvement > Components: humanres >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: menus, refactoring, usability > > Currently the create buttons for the main objects of the humanres plugin are > located within find and profile widgets/templates of those objects. > In order to improve the usability of this plugin, OFBiz (and thus the appeal > of it for adopters and users) these create buttons/links/etc. should be in a > main action menu visible at all times when a user is working within the web > appliclation of the component. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-10363) Improve Dutch translations
[ https://issues.apache.org/jira/browse/OFBIZ-10363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17469830#comment-17469830 ] Pierre Smits commented on OFBIZ-10363: -- Thanks to Jacques for his assistance to get this into the repository. > Improve Dutch translations > -- > > Key: OFBIZ-10363 > URL: https://issues.apache.org/jira/browse/OFBIZ-10363 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Minor > Attachments: ofbiz-10363-AccountingUiLabels.xml.patch > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-11774) Have a Menu in Catalog featuring actions to create the main objects
[ https://issues.apache.org/jira/browse/OFBIZ-11774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468010#comment-17468010 ] Pierre Smits commented on OFBIZ-11774: -- Thanks Jacques. And I plan to look forward to see such plans come to fruition. :D(y) > Have a Menu in Catalog featuring actions to create the main objects > --- > > Key: OFBIZ-11774 > URL: https://issues.apache.org/jira/browse/OFBIZ-11774 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: menus, refactoring, usability > > Currently the create buttons for the main objects of the catalog components > are located within the find and profile widgets/templates of those object. > In order to improve the usability of OFBiz (and thus the appeal of it for > adopters and users) these create buttons/links/etc. should be in a main > action menu visible at all times when a user is working within the component. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-9498) Improve DevOps using environment variable configuration
[ https://issues.apache.org/jira/browse/OFBIZ-9498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17467951#comment-17467951 ] Pierre Smits commented on OFBIZ-9498: - HI [~marco_adeti] , First let me wish you a healthy, happy, interesting and prosperous New Year too. Thanks for your apologies for not providing additional details before. We all appreciate this, and understand that (more) pressing/interesting things get in the way. For sure, an overhaul of how OFBiz is currently configured (through EntityUtilProperties for runtime configuration, UtilProperties for configuration through property files, and this PR for configuration via environment variables as in e.g. Docker containers) appears to be warranted. Only the 'nobody' contributor could be against that. And equally obvious is that such will take a significant amount of time. Not only the investigation what it will impact, and how it will be implemented. The remarks in your posted comment suggests that. As such it is symptomatic for the entire state of OFBiz: a continuous state of Work In Progress/Improvement. Nonetheless, we need not have that (continuous state of WIP) delay that what will work now (the PR) going into the codebase. As always, more pressing/interesting things can be expected to pop up. As is commonly understood: don't delay what can be achieved now! > Improve DevOps using environment variable configuration > --- > > Key: OFBIZ-9498 > URL: https://issues.apache.org/jira/browse/OFBIZ-9498 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Gil Portenseigne >Assignee: Gil Portenseigne >Priority: Minor > Attachments: OFBIZ-9498.patch > > > Discussed in thread : https://s.apache.org/Mh3q > This Jira will present the improvment proposal giving a way to configure > OFBiz using environment variable. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (OFBIZ-11774) Have a Menu in Catalog featuring actions to create the main objects
[ https://issues.apache.org/jira/browse/OFBIZ-11774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17467896#comment-17467896 ] Pierre Smits edited comment on OFBIZ-11774 at 1/3/22, 10:36 AM: Hi Jacques, it is 'old' the day after the submission (like bread, the day after it has been baked/bought). And growing more stale with each day passing. Till the point that it indeed isn't mergeable anymore. What has changed that it won't happen again? If I do all the work again, what ensures that it will be merged in in time? was (Author: pfm.smits): Hi Jacques, it is 'old' the day after the submission. And growing more stale each day overlooked. Till the point that it indeed isn't mergeable anymore. What has changed that it won't happen again? If I do all the work again, what ensures that it will be merged in in time? > Have a Menu in Catalog featuring actions to create the main objects > --- > > Key: OFBIZ-11774 > URL: https://issues.apache.org/jira/browse/OFBIZ-11774 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: menus, refactoring, usability > > Currently the create buttons for the main objects of the catalog components > are located within the find and profile widgets/templates of those object. > In order to improve the usability of OFBiz (and thus the appeal of it for > adopters and users) these create buttons/links/etc. should be in a main > action menu visible at all times when a user is working within the component. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-11774) Have a Menu in Catalog featuring actions to create the main objects
[ https://issues.apache.org/jira/browse/OFBIZ-11774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17467896#comment-17467896 ] Pierre Smits commented on OFBIZ-11774: -- Hi Jacques, it is 'old' the day after the submission. And growing more stale each day overlooked. Till the point that it indeed isn't mergeable anymore. What has changed that it won't happen again? If I do all the work again, what ensures that it will be merged in in time? > Have a Menu in Catalog featuring actions to create the main objects > --- > > Key: OFBIZ-11774 > URL: https://issues.apache.org/jira/browse/OFBIZ-11774 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: menus, refactoring, usability > > Currently the create buttons for the main objects of the catalog components > are located within the find and profile widgets/templates of those object. > In order to improve the usability of OFBiz (and thus the appeal of it for > adopters and users) these create buttons/links/etc. should be in a main > action menu visible at all times when a user is working within the component. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-9498) Improve DevOps using environment variable configuration
[ https://issues.apache.org/jira/browse/OFBIZ-9498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17467893#comment-17467893 ] Pierre Smits commented on OFBIZ-9498: - Thanks [~marco_adeti] , Working on a 'more' complete version implies that current version (PR355) works. (And this has not been contested). Any improvements to that (the current PR) can be handled in due time as subsequent PRs. There is no argument to delay/postponing merging this PR, other than this 'there is more in the pipeline' comment. > Improve DevOps using environment variable configuration > --- > > Key: OFBIZ-9498 > URL: https://issues.apache.org/jira/browse/OFBIZ-9498 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Gil Portenseigne >Assignee: Gil Portenseigne >Priority: Minor > Attachments: OFBIZ-9498.patch > > > Discussed in thread : https://s.apache.org/Mh3q > This Jira will present the improvment proposal giving a way to configure > OFBiz using environment variable. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-9498) Improve DevOps using environment variable configuration
[ https://issues.apache.org/jira/browse/OFBIZ-9498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17467883#comment-17467883 ] Pierre Smits commented on OFBIZ-9498: - Hi Gil, What is missing in this PR? Can this 'enhancement' not be addressed in a subsequent improvement commit/merge? > Improve DevOps using environment variable configuration > --- > > Key: OFBIZ-9498 > URL: https://issues.apache.org/jira/browse/OFBIZ-9498 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Gil Portenseigne >Assignee: Gil Portenseigne >Priority: Minor > Attachments: OFBIZ-9498.patch > > > Discussed in thread : https://s.apache.org/Mh3q > This Jira will present the improvment proposal giving a way to configure > OFBiz using environment variable. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-11774) Have a Menu in Catalog featuring actions to create the main objects
[ https://issues.apache.org/jira/browse/OFBIZ-11774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17467857#comment-17467857 ] Pierre Smits commented on OFBIZ-11774: -- Bonjour Jacques, Bonne année. Tja. How did that happen? What do you suggest to move forward? > Have a Menu in Catalog featuring actions to create the main objects > --- > > Key: OFBIZ-11774 > URL: https://issues.apache.org/jira/browse/OFBIZ-11774 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: menus, refactoring, usability > > Currently the create buttons for the main objects of the catalog components > are located within the find and profile widgets/templates of those object. > In order to improve the usability of OFBiz (and thus the appeal of it for > adopters and users) these create buttons/links/etc. should be in a main > action menu visible at all times when a user is working within the component. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Reopened] (OFBIZ-10363) Improve Dutch translations
[ https://issues.apache.org/jira/browse/OFBIZ-10363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reopened OFBIZ-10363: -- Ongoing > Improve Dutch translations > -- > > Key: OFBIZ-10363 > URL: https://issues.apache.org/jira/browse/OFBIZ-10363 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Minor > Attachments: ofbiz-10363-AccountingUiLabels.xml.patch > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (OFBIZ-10363) Improve Dutch translations
[ https://issues.apache.org/jira/browse/OFBIZ-10363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-10363: - Summary: Improve Dutch translations (was: Improve Dutch UiLabels) > Improve Dutch translations > -- > > Key: OFBIZ-10363 > URL: https://issues.apache.org/jira/browse/OFBIZ-10363 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Nicolas Malin >Priority: Minor > Attachments: ofbiz-10363-AccountingUiLabels.xml.patch > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (OFBIZ-10363) Improve Dutch translations
[ https://issues.apache.org/jira/browse/OFBIZ-10363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-10363: Assignee: Pierre Smits (was: Nicolas Malin) > Improve Dutch translations > -- > > Key: OFBIZ-10363 > URL: https://issues.apache.org/jira/browse/OFBIZ-10363 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Minor > Attachments: ofbiz-10363-AccountingUiLabels.xml.patch > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-11345) Lists and grids
[ https://issues.apache.org/jira/browse/OFBIZ-11345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17466333#comment-17466333 ] Pierre Smits commented on OFBIZ-11345: -- Thanks to Jacques for his assistance to get this into the codebase. > Lists and grids > --- > > Key: OFBIZ-11345 > URL: https://issues.apache.org/jira/browse/OFBIZ-11345 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: cleanup, refactoring, widget > Fix For: Upcoming Branch > > > According to the definition in widget-form.xsd the use of a combination of a > form with type="list" is deprecated in favour of a grid. > Refactor various list forms into grids. > Refactor various list form references in screens. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (OFBIZ-10955) field type Integer is missing in definitions
[ https://issues.apache.org/jira/browse/OFBIZ-10955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-10955: Assignee: Pierre Smits (was: Michael Brohl) > field type Integer is missing in definitions > > > Key: OFBIZ-10955 > URL: https://issues.apache.org/jira/browse/OFBIZ-10955 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: 16.11.07, 17.12.01, Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Fix For: Upcoming Branch > > Time Spent: 20m > Remaining Estimate: 0h > > The field type for integer values is missing in definitions for various RDBMS > variants -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-4310) Conversion for complex-alias needs to be implemented
[
https://issues.apache.org/jira/browse/OFBIZ-4310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17466122#comment-17466122
]
Pierre Smits commented on OFBIZ-4310:
-
Is this still an issue (that we want/need to pursue)|?
> Conversion for complex-alias needs to be implemented
> -
>
> Key: OFBIZ-4310
> URL: https://issues.apache.org/jira/browse/OFBIZ-4310
> Project: OFBiz
> Issue Type: New Feature
> Components: framework
>Affects Versions: Release 4.0, Trunk
>Reporter: Jacques Le Roux
>Assignee: Deepak Nigam
>Priority: Minor
>
> There is a TODO in ModelViewEntity.populateReverseLinks()
> // TODO: conversion for complex-alias needs to be implemented for cache and
> in-memory eval stuff to work correctly
> This throws WARNING at OFBiz startup:
> {code}
> 2011-05-27 13:23:53,161 (main) [ModelViewEntity.java:538:WARN ]
> Conversion for complex-alias needs to be implemented for cache and in-memory
> eval stuff to work correctly, will not work for alias: quantityOrdered of
> view-entity OrderItemQuantityReportGroupByItem
> 2011-05-27 13:23:53,162 (main) [ModelViewEntity.java:538:WARN ]
> Conversion for complex-alias needs to be implemented for cache and in-memory
> eval stuff to work correctly, will not work for alias: quantityOpen of
> view-entity OrderItemQuantityReportGroupByItem
> 2011-05-27 13:23:53,162 (main) [ModelViewEntity.java:538:WARN ]
> Conversion for complex-alias needs to be implemented for cache and in-memory
> eval stuff to work correctly, will not work for alias: quantityOrdered of
> view-entity OrderItemQuantityReportGroupByProduct
> 2011-05-27 13:23:53,162 (main) [ModelViewEntity.java:538:WARN ]
> Conversion for complex-alias needs to be implemented for cache and in-memory
> eval stuff to work correctly, will not work for alias: quantityOpen of
> view-entity OrderItemQuantityReportGroupByProduct
> 2011-05-27 13:23:53,169 (main) [ModelViewEntity.java:538:WARN ]
> Conversion for complex-alias needs to be implemented for cache and in-memory
> eval stuff to work correctly, will not work for alias: quantityOrdered of
> view-entity OrderReportSalesGroupByProduct
> 2011-05-27 13:23:53,176 (main) [ModelViewEntity.java:538:WARN ]
> Conversion for complex-alias needs to be implemented for cache and in-memory
> eval stuff to work correctly, will not work for alias: quantityOrdered of
> view-entity OrderItemAndShipGrpInvResAndItemSum
> 2011-05-27 13:23:53,176 (main) [ModelViewEntity.java:538:WARN ]
> Conversion for complex-alias needs to be implemented for cache and in-memory
> eval stuff to work correctly, will not work for alias: totQuantityAvailable
> of view-entity OrderItemAndShipGrpInvResAndItemSum
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (OFBIZ-3856) quicker picklist option functionality
[
https://issues.apache.org/jira/browse/OFBIZ-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17466121#comment-17466121
]
Pierre Smits commented on OFBIZ-3856:
-
Is this still an issue (that we want/need to pursue)|?
> quicker picklist option functionality
> -
>
> Key: OFBIZ-3856
> URL: https://issues.apache.org/jira/browse/OFBIZ-3856
> Project: OFBiz
> Issue Type: Improvement
> Components: product
>Affects Versions: Release 4.0, Release 09.04, Trunk
>Reporter: Albert Mayo
>Priority: Minor
> Attachments: FindOrdersToPick.groovy, PickListServices.java,
> entitymodel.xml, quicker picklist.diff
>
>
> I am noticing as our OFBiz database grows larger, it is taking the
> PicklistOptions longer to load. Even for a batch as small as 50 orders it can
> take up to a couple minutes to load. 300 orders can take upwards of 5-10
> minutes. My development system with much lesser hardware can get through a
> hundred orders in seconds, so I have a feeling it has to do with the
> process/code inefficiency.
> For instance, the picklistoptions function does the following (abbreviated):
> select * from OrderHeader
> for each orderHeader {
> select * from OrderItemShipGroup where orderId = orderHeader.orderId
> for each orderItemShipGroup in orderItemShipGroupList {
> select * from OrderItemShipGrpInvRes where orderId =
> orderItemShipGroup.orderId;
> for each orderItemShipGrpInvRes in orderItemShipGrpInvResList {
> etc
> }
> }
> }
> These kind of loops can create many hits to the database and greatly slow
> down the process, especially if the database tables have many records. Our
> database is now almost 8 gigs. The PicklistOptions process took ~4 minutes
> for 40 pickable orders.
> I am using OFBiz 4.0, but the trunk version has a lot of the same code. I am
> opening this ticket to start a conversation of a quicker method to create
> picklists, like with the use of views or DynamicViewEntitys.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (OFBIZ-4467) Improve auto-fields-entity (select include field and auto drop-down)
[ https://issues.apache.org/jira/browse/OFBIZ-4467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17466119#comment-17466119 ] Pierre Smits commented on OFBIZ-4467: - Is this still an issue (that we want/need to pursue)? > Improve auto-fields-entity (select include field and auto drop-down) > > > Key: OFBIZ-4467 > URL: https://issues.apache.org/jira/browse/OFBIZ-4467 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Screen Widget Redesign, Trunk >Reporter: Nicolas Malin >Assignee: Nicolas Malin >Priority: Minor > Attachments: OFBIZ-4467-example.patch, OFBIZ-4467-example.patch, > OFBIZ-4467.patch, OFBIZ-4467.patch, OFBIZ-4467.patch, OFBIZ-4467.png > > > Hi > Here are two improvments to complete the element 'auto-fields-entity' of > forms. > The first one consists in adding one fields allowing to select which fields > are include in the form (same way as what is made on the definitions of > service): > For example: > default-field-type="display"/> > => To display only the primary key fields of the Example entity > default-field-type="edit"> > => To display only the non primary key fields of the Example entity > > => To exclude one precise fields of an entity > The second one consists in including for fields with relation a drop-down or > a display entity according to EntityType > Any comments are welcome -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-3981) List form using jquery
[ https://issues.apache.org/jira/browse/OFBIZ-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17466118#comment-17466118 ] Pierre Smits commented on OFBIZ-3981: - Is this still an issue (that we want to pursue)? > List form using jquery > -- > > Key: OFBIZ-3981 > URL: https://issues.apache.org/jira/browse/OFBIZ-3981 > Project: OFBiz > Issue Type: New Feature > Components: framework >Affects Versions: jQuery >Reporter: Michael Xu >Priority: Major > > Replace/enhance current list form with jquery table, which allow users to: > # show/hide any columns > # group by any column > # change the position of columns by drag > # export table to csv/excel -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (OFBIZ-11772) Have a Menu in Order featuring actions to create the main objects
[ https://issues.apache.org/jira/browse/OFBIZ-11772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed OFBIZ-11772. Resolution: Implemented Thanks to Jacques for his assistance to get this into the codebase. > Have a Menu in Order featuring actions to create the main objects > - > > Key: OFBIZ-11772 > URL: https://issues.apache.org/jira/browse/OFBIZ-11772 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: menus, refactoring, usability > Attachments: Screen Shot 2020-05-30 at 12.48.21.png > > > Currently the create buttons for the main objects of the order components are > located within the find and profile widgets/templates of those object. > In order to improve the usability of OFBiz (and thus the appeal of it for > adopters and users) these create buttons/links/etc. should be in a main > action menu visible at all times when a user is working within the component. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-11345) Lists and grids
[ https://issues.apache.org/jira/browse/OFBIZ-11345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17465312#comment-17465312 ] Pierre Smits commented on OFBIZ-11345: -- Thanks to Jacques for his assistance to the this into the codebase. > Lists and grids > --- > > Key: OFBIZ-11345 > URL: https://issues.apache.org/jira/browse/OFBIZ-11345 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: cleanup, refactoring, widget > Fix For: Upcoming Branch > > > According to the definition in widget-form.xsd the use of a combination of a > form with type="list" is deprecated in favour of a grid. > Refactor various list forms into grids. > Refactor various list form references in screens. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (OFBIZ-12450) Price Rules: Price rules configurations are not syncing with eCommerce storefront
[ https://issues.apache.org/jira/browse/OFBIZ-12450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed OFBIZ-12450. Fix Version/s: Upcoming Branch Resolution: Fixed Thanks to Jacques for his assistance to get this into the codebase. > Price Rules: Price rules configurations are not syncing with eCommerce > storefront > - > > Key: OFBIZ-12450 > URL: https://issues.apache.org/jira/browse/OFBIZ-12450 > Project: OFBiz > Issue Type: Bug > Components: product/catalog >Affects Versions: Trunk >Reporter: Justine Nowak >Assignee: Pierre Smits >Priority: Major > Labels: price-rule, user-experience > Fix For: Upcoming Branch > > > When adding a Price Rule, whether it be a Product Category, Product, Party, > Party Classification, the system doesn't show a price difference. > The price rules work with the Database as they do get changed when saved. But > their functionality doesn't work, it won't give a price increase or decrease > or restriction. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-12466) Solr generates an error
[
https://issues.apache.org/jira/browse/OFBIZ-12466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17461825#comment-17461825
]
Pierre Smits commented on OFBIZ-12466:
--
Good morning Jacques,
Tja...
Luckily there are lots of other and easier fish to fry.
> Solr generates an error
> ---
>
> Key: OFBIZ-12466
> URL: https://issues.apache.org/jira/browse/OFBIZ-12466
> Project: OFBiz
> Issue Type: Bug
> Components: solr
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Priority: Major
>
> Following error is shown:
> {code:java}
> 2021-12-17 12:45:37,676 |main |SolrDispatchFilter
> |E| Could not start Solr. Check solr/home property and the logs
> 2021-12-17 12:45:37,707 |main |SolrCore
> |E| null:java.lang.NoClassDefFoundError: Could not initialize class
> org.slf4j.impl.StaticLoggerBinder
> at
> org.apache.solr.util.StartupLoggingUtils.(StartupLoggingUtils.java:45)
> at
> org.apache.solr.servlet.SolrDispatchFilter.init(SolrDispatchFilter.java:158)
> at
> org.apache.ofbiz.solr.webapp.OFBizSolrContextFilter.init(OFBizSolrContextFilter.java:100)
> at
> org.apache.catalina.core.ApplicationFilterConfig.initFilter(ApplicationFilterConfig.java:270)
> at
> org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:251)
> at
> org.apache.catalina.core.ApplicationFilterConfig.(ApplicationFilterConfig.java:101)
> at
> org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4613)
> at
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5256)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1396)
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1386)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
> at
> java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134)
> at
> org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:919)
> at
> org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:835)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1396)
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1386)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
> at
> java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134)
> at
> org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:919)
> at
> org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:263)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
> at
> org.apache.catalina.core.StandardService.startInternal(StandardService.java:432)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
> at
> org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:927)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
> at org.apache.catalina.startup.Tomcat.start(Tomcat.java:486)
> at
> org.apache.ofbiz.catalina.container.CatalinaContainer.start(CatalinaContainer.java:134)
> at
> org.apache.ofbiz.base.container.ContainerLoader.startLoadedContainers(ContainerLoader.java:153)
> at
> org.apache.ofbiz.base.container.ContainerLoader.load(ContainerLoader.java:77)
> at
> org.apache.ofbiz.base.start.StartupControlPanel.loadContainers(StartupControlPanel.java:146)
> at
> org.apache.ofbiz.base.start.StartupControlPanel.start(StartupControlPanel.java:70)
> at org.apache.ofbiz.base.start.Start.main(Start.java:89)
> Dec 17, 2021 12:45:37 PM org.apache.catalina.core.StandardContext filterStart
> SEVERE: Exception starting filter [SolrFilter]
> java.lang.NoClassDefFoundError: Could not initialize class
> org.slf4j.impl.StaticLoggerBinder
> at
> org.apache.solr.util.StartupLoggingUtils.(StartupLoggingUtils.java:45)
> at
> org.apache.solr.servlet.SolrDispatchFilter.init(SolrDispatchFilter.java:158)
> at
> org.apache.ofbiz.solr.webapp.OFBizSolrContextFilter.init(OFBizSolrContextFilter.java:100)
> at
> org.apache.catalina.core.ApplicationFilterConfig.initFilter(ApplicationFilterConfig.java:270)
> at
>
[jira] [Commented] (OFBIZ-12450) Price Rules: Price rules configurations are not syncing with eCommerce storefront
[ https://issues.apache.org/jira/browse/OFBIZ-12450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17461813#comment-17461813 ] Pierre Smits commented on OFBIZ-12450: -- Thanks to Jacques for his assistance to merge PR 420 into the codebase. > Price Rules: Price rules configurations are not syncing with eCommerce > storefront > - > > Key: OFBIZ-12450 > URL: https://issues.apache.org/jira/browse/OFBIZ-12450 > Project: OFBiz > Issue Type: Bug > Components: product/catalog >Affects Versions: Trunk >Reporter: Justine Nowak >Assignee: Pierre Smits >Priority: Critical > Labels: price-rule, user-experience > > When adding a Price Rule, whether it be a Product Category, Product, Party, > Party Classification, the system doesn't show a price difference. > The price rules work with the Database as they do get changed when saved. But > their functionality doesn't work, it won't give a price increase or decrease > or restriction. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (OFBIZ-12467) PriceRule - values of existing ProductPriceCond record not shown
[ https://issues.apache.org/jira/browse/OFBIZ-12467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed OFBIZ-12467. Fix Version/s: Upcoming Branch Resolution: Fixed Thanks to Jacques for his assistance to get this into the codebase. > PriceRule - values of existing ProductPriceCond record not shown > > > Key: OFBIZ-12467 > URL: https://issues.apache.org/jira/browse/OFBIZ-12467 > Project: OFBiz > Issue Type: Bug > Components: product/catalog >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: price-rule, usability > Fix For: Upcoming Branch > > > When a price rule is shown in the screen, the associated existing conditions > are not shown in the overview for the conditions -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (OFBIZ-12467) PriceRule - values of existing ProductPriceCond record not shown
Pierre Smits created OFBIZ-12467: Summary: PriceRule - values of existing ProductPriceCond record not shown Key: OFBIZ-12467 URL: https://issues.apache.org/jira/browse/OFBIZ-12467 Project: OFBiz Issue Type: Bug Components: product/catalog Affects Versions: Trunk Reporter: Pierre Smits Assignee: Pierre Smits When a price rule is shown in the screen, the associated existing conditions are not shown in the overview for the conditions -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-12466) Solr generates an error
[
https://issues.apache.org/jira/browse/OFBIZ-12466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17461430#comment-17461430
]
Pierre Smits commented on OFBIZ-12466:
--
Tja
I remember having it brought up before (here in Jira, somewhere else), but
would it not be smart to integrate both lucence and solr extensions into one?
Solr uses lucence, and it seems that the redundant parts makes us having to
maintain both
> Solr generates an error
> ---
>
> Key: OFBIZ-12466
> URL: https://issues.apache.org/jira/browse/OFBIZ-12466
> Project: OFBiz
> Issue Type: Bug
> Components: solr
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Priority: Major
>
> Following error is shown:
> {code:java}
> 2021-12-17 12:45:37,676 |main |SolrDispatchFilter
> |E| Could not start Solr. Check solr/home property and the logs
> 2021-12-17 12:45:37,707 |main |SolrCore
> |E| null:java.lang.NoClassDefFoundError: Could not initialize class
> org.slf4j.impl.StaticLoggerBinder
> at
> org.apache.solr.util.StartupLoggingUtils.(StartupLoggingUtils.java:45)
> at
> org.apache.solr.servlet.SolrDispatchFilter.init(SolrDispatchFilter.java:158)
> at
> org.apache.ofbiz.solr.webapp.OFBizSolrContextFilter.init(OFBizSolrContextFilter.java:100)
> at
> org.apache.catalina.core.ApplicationFilterConfig.initFilter(ApplicationFilterConfig.java:270)
> at
> org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:251)
> at
> org.apache.catalina.core.ApplicationFilterConfig.(ApplicationFilterConfig.java:101)
> at
> org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4613)
> at
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5256)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1396)
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1386)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
> at
> java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134)
> at
> org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:919)
> at
> org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:835)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1396)
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1386)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
> at
> java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134)
> at
> org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:919)
> at
> org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:263)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
> at
> org.apache.catalina.core.StandardService.startInternal(StandardService.java:432)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
> at
> org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:927)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
> at org.apache.catalina.startup.Tomcat.start(Tomcat.java:486)
> at
> org.apache.ofbiz.catalina.container.CatalinaContainer.start(CatalinaContainer.java:134)
> at
> org.apache.ofbiz.base.container.ContainerLoader.startLoadedContainers(ContainerLoader.java:153)
> at
> org.apache.ofbiz.base.container.ContainerLoader.load(ContainerLoader.java:77)
> at
> org.apache.ofbiz.base.start.StartupControlPanel.loadContainers(StartupControlPanel.java:146)
> at
> org.apache.ofbiz.base.start.StartupControlPanel.start(StartupControlPanel.java:70)
> at org.apache.ofbiz.base.start.Start.main(Start.java:89)
> Dec 17, 2021 12:45:37 PM org.apache.catalina.core.StandardContext filterStart
> SEVERE: Exception starting filter [SolrFilter]
> java.lang.NoClassDefFoundError: Could not initialize class
> org.slf4j.impl.StaticLoggerBinder
> at
> org.apache.solr.util.StartupLoggingUtils.(StartupLoggingUtils.java:45)
> at
> org.apache.solr.servlet.SolrDispatchFilter.init(SolrDispatchFilter.java:158)
> at
>
[jira] [Updated] (OFBIZ-12450) Price Rules: Price rules configurations are not syncing with eCommerce storefront
[ https://issues.apache.org/jira/browse/OFBIZ-12450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-12450: - Labels: price-rule user-experience (was: user-experience) > Price Rules: Price rules configurations are not syncing with eCommerce > storefront > - > > Key: OFBIZ-12450 > URL: https://issues.apache.org/jira/browse/OFBIZ-12450 > Project: OFBiz > Issue Type: Bug > Components: product/catalog >Affects Versions: Trunk >Reporter: Justine Nowak >Assignee: Pierre Smits >Priority: Critical > Labels: price-rule, user-experience > > When adding a Price Rule, whether it be a Product Category, Product, Party, > Party Classification, the system doesn't show a price difference. > The price rules work with the Database as they do get changed when saved. But > their functionality doesn't work, it won't give a price increase or decrease > or restriction. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-12450) Price Rules: Price rules configurations are not syncing with eCommerce storefront
[ https://issues.apache.org/jira/browse/OFBIZ-12450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17461412#comment-17461412 ] Pierre Smits commented on OFBIZ-12450: -- Additional observations: * function 'makeProducePriceRuleList' is used in function 'calculateProductPrice' * function 'calculateProductPrice' is used in ** service 'calculateProductPrice' in services_pricePromo.xml * service 'calculateProductPrice' is used in the ecommerce component in: ** MiniProductSummary.groovy ** EditShoppingList.groovy > Price Rules: Price rules configurations are not syncing with eCommerce > storefront > - > > Key: OFBIZ-12450 > URL: https://issues.apache.org/jira/browse/OFBIZ-12450 > Project: OFBiz > Issue Type: Bug > Components: product/catalog >Affects Versions: Trunk >Reporter: Justine Nowak >Assignee: Pierre Smits >Priority: Critical > Labels: user-experience > > When adding a Price Rule, whether it be a Product Category, Product, Party, > Party Classification, the system doesn't show a price difference. > The price rules work with the Database as they do get changed when saved. But > their functionality doesn't work, it won't give a price increase or decrease > or restriction. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-12466) Solr generates an error
[
https://issues.apache.org/jira/browse/OFBIZ-12466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17461402#comment-17461402
]
Pierre Smits commented on OFBIZ-12466:
--
Hi Jacques,
Thanks for the reaction.
Looking at [https://github.com/apache/solr/commits/main,] I see that yesterday
the Sole team committed changes to the repo regarding 8.11.1. So we just have
to monitor that repo (and maven central ?) to see that changes come through.
I guess, the combo of Lucene and Solr extensions in the plugins repo makes this
harder for us. Correct?
> Solr generates an error
> ---
>
> Key: OFBIZ-12466
> URL: https://issues.apache.org/jira/browse/OFBIZ-12466
> Project: OFBiz
> Issue Type: Bug
> Components: solr
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Priority: Major
>
> Following error is shown:
> {code:java}
> 2021-12-17 12:45:37,676 |main |SolrDispatchFilter
> |E| Could not start Solr. Check solr/home property and the logs
> 2021-12-17 12:45:37,707 |main |SolrCore
> |E| null:java.lang.NoClassDefFoundError: Could not initialize class
> org.slf4j.impl.StaticLoggerBinder
> at
> org.apache.solr.util.StartupLoggingUtils.(StartupLoggingUtils.java:45)
> at
> org.apache.solr.servlet.SolrDispatchFilter.init(SolrDispatchFilter.java:158)
> at
> org.apache.ofbiz.solr.webapp.OFBizSolrContextFilter.init(OFBizSolrContextFilter.java:100)
> at
> org.apache.catalina.core.ApplicationFilterConfig.initFilter(ApplicationFilterConfig.java:270)
> at
> org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:251)
> at
> org.apache.catalina.core.ApplicationFilterConfig.(ApplicationFilterConfig.java:101)
> at
> org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4613)
> at
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5256)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1396)
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1386)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
> at
> java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134)
> at
> org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:919)
> at
> org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:835)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1396)
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1386)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
> at
> java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134)
> at
> org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:919)
> at
> org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:263)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
> at
> org.apache.catalina.core.StandardService.startInternal(StandardService.java:432)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
> at
> org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:927)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
> at org.apache.catalina.startup.Tomcat.start(Tomcat.java:486)
> at
> org.apache.ofbiz.catalina.container.CatalinaContainer.start(CatalinaContainer.java:134)
> at
> org.apache.ofbiz.base.container.ContainerLoader.startLoadedContainers(ContainerLoader.java:153)
> at
> org.apache.ofbiz.base.container.ContainerLoader.load(ContainerLoader.java:77)
> at
> org.apache.ofbiz.base.start.StartupControlPanel.loadContainers(StartupControlPanel.java:146)
> at
> org.apache.ofbiz.base.start.StartupControlPanel.start(StartupControlPanel.java:70)
> at org.apache.ofbiz.base.start.Start.main(Start.java:89)
> Dec 17, 2021 12:45:37 PM org.apache.catalina.core.StandardContext filterStart
> SEVERE: Exception starting filter [SolrFilter]
> java.lang.NoClassDefFoundError: Could not initialize class
> org.slf4j.impl.StaticLoggerBinder
> at
> org.apache.solr.util.StartupLoggingUtils.(StartupLoggingUtils.java:45)
> at
>
[jira] [Commented] (OFBIZ-12450) Price Rules: Price rules configurations are not syncing with eCommerce storefront
[ https://issues.apache.org/jira/browse/OFBIZ-12450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17461395#comment-17461395 ] Pierre Smits commented on OFBIZ-12450: -- There is also a 'getAssociatedPriceRulesConds' in PriceServices.groovy that does something with a price rule for the aforementioned conditions. > Price Rules: Price rules configurations are not syncing with eCommerce > storefront > - > > Key: OFBIZ-12450 > URL: https://issues.apache.org/jira/browse/OFBIZ-12450 > Project: OFBiz > Issue Type: Bug > Components: product/catalog >Affects Versions: Trunk >Reporter: Justine Nowak >Assignee: Pierre Smits >Priority: Critical > Labels: user-experience > > When adding a Price Rule, whether it be a Product Category, Product, Party, > Party Classification, the system doesn't show a price difference. > The price rules work with the Database as they do get changed when saved. But > their functionality doesn't work, it won't give a price increase or decrease > or restriction. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (OFBIZ-12450) Price Rules: Price rules configurations are not syncing with eCommerce storefront
[ https://issues.apache.org/jira/browse/OFBIZ-12450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17461321#comment-17461321 ] Pierre Smits edited comment on OFBIZ-12450 at 12/17/21, 12:03 PM: -- Price calculations working with price rules is done through PriceServices.java in function makeProducePriceRuleList According to the code price calculations should work for following conditions (as referenced in the description): * Product Category (productCateogryId * Product Id (both productId and pvirtualProductId) * Party (partyId) And there are others referenced (based on records in the Enumeration table with enumTypeId="PROD_PRICE_IN_PARAM") was (Author: pfm.smits): Price calculations working with price rules is done through PriceServices.java According to the code price calculations should work for following conditions (as referenced in the description): * Product Category (productCateogryId * Product Id (both productId and pvirtualProductId) * Party (partyId) And there are others referenced (based on records in the Enumeration table with enumTypeId="PROD_PRICE_IN_PARAM") > Price Rules: Price rules configurations are not syncing with eCommerce > storefront > - > > Key: OFBIZ-12450 > URL: https://issues.apache.org/jira/browse/OFBIZ-12450 > Project: OFBiz > Issue Type: Bug > Components: product/catalog >Affects Versions: Trunk >Reporter: Justine Nowak >Assignee: Pierre Smits >Priority: Critical > Labels: user-experience > > When adding a Price Rule, whether it be a Product Category, Product, Party, > Party Classification, the system doesn't show a price difference. > The price rules work with the Database as they do get changed when saved. But > their functionality doesn't work, it won't give a price increase or decrease > or restriction. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (OFBIZ-12450) Price Rules: Price rules configurations are not syncing with eCommerce storefront
[ https://issues.apache.org/jira/browse/OFBIZ-12450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-12450: - Description: When adding a Price Rule, whether it be a Product Category, Product, Party, Party Classification, the system doesn't show a price difference. The price rules work with the Database as they do get changed when saved. But their functionality doesn't work, it won't give a price increase or decrease or restriction. was: When adding a Price Rule, whether it be a Product Category, Product, Party, Party Classification, the system doesn't show a price difference. The price rules work with the Database as they do get changed when saved. But their functionality doesn't work, it won't give a price increase or decrease or restriction. > Price Rules: Price rules configurations are not syncing with eCommerce > storefront > - > > Key: OFBIZ-12450 > URL: https://issues.apache.org/jira/browse/OFBIZ-12450 > Project: OFBiz > Issue Type: Bug > Components: product/catalog >Affects Versions: Trunk >Reporter: Justine Nowak >Assignee: Pierre Smits >Priority: Critical > Labels: user-experience > > When adding a Price Rule, whether it be a Product Category, Product, Party, > Party Classification, the system doesn't show a price difference. > The price rules work with the Database as they do get changed when saved. But > their functionality doesn't work, it won't give a price increase or decrease > or restriction. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-12450) Price Rules: Price rules configurations are not syncing with eCommerce storefront
[ https://issues.apache.org/jira/browse/OFBIZ-12450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17461385#comment-17461385 ] Pierre Smits commented on OFBIZ-12450: -- Is a bit hard to demonstrate without proper data in our datasets. > Price Rules: Price rules configurations are not syncing with eCommerce > storefront > - > > Key: OFBIZ-12450 > URL: https://issues.apache.org/jira/browse/OFBIZ-12450 > Project: OFBiz > Issue Type: Bug > Components: product/catalog >Affects Versions: Trunk >Reporter: Justine Nowak >Assignee: Pierre Smits >Priority: Critical > Labels: user-experience > > When adding a Price Rule, whether it be a Product Category, Product, Party, > Party Classification, the system doesn't show a price difference. > > The price rules work with the Database as they do get changed when saved. But > their functionality doesn't work, it won't give a price increase or decrease > or restriction. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (OFBIZ-12466) Solr generates an error
Pierre Smits created OFBIZ-12466:
Summary: Solr generates an error
Key: OFBIZ-12466
URL: https://issues.apache.org/jira/browse/OFBIZ-12466
Project: OFBiz
Issue Type: Bug
Components: solr
Affects Versions: Trunk
Reporter: Pierre Smits
Following error is shown:
{code:java}
2021-12-17 12:45:37,676 |main |SolrDispatchFilter
|E| Could not start Solr. Check solr/home property and the logs
2021-12-17 12:45:37,707 |main |SolrCore
|E| null:java.lang.NoClassDefFoundError: Could not initialize class
org.slf4j.impl.StaticLoggerBinder
at
org.apache.solr.util.StartupLoggingUtils.(StartupLoggingUtils.java:45)
at
org.apache.solr.servlet.SolrDispatchFilter.init(SolrDispatchFilter.java:158)
at
org.apache.ofbiz.solr.webapp.OFBizSolrContextFilter.init(OFBizSolrContextFilter.java:100)
at
org.apache.catalina.core.ApplicationFilterConfig.initFilter(ApplicationFilterConfig.java:270)
at
org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:251)
at
org.apache.catalina.core.ApplicationFilterConfig.(ApplicationFilterConfig.java:101)
at
org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4613)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5256)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1396)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1386)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
at
java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134)
at
org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:919)
at
org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:835)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1396)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1386)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
at
java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134)
at
org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:919)
at
org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:263)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at
org.apache.catalina.core.StandardService.startInternal(StandardService.java:432)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at
org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:927)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at org.apache.catalina.startup.Tomcat.start(Tomcat.java:486)
at
org.apache.ofbiz.catalina.container.CatalinaContainer.start(CatalinaContainer.java:134)
at
org.apache.ofbiz.base.container.ContainerLoader.startLoadedContainers(ContainerLoader.java:153)
at
org.apache.ofbiz.base.container.ContainerLoader.load(ContainerLoader.java:77)
at
org.apache.ofbiz.base.start.StartupControlPanel.loadContainers(StartupControlPanel.java:146)
at
org.apache.ofbiz.base.start.StartupControlPanel.start(StartupControlPanel.java:70)
at org.apache.ofbiz.base.start.Start.main(Start.java:89)
Dec 17, 2021 12:45:37 PM org.apache.catalina.core.StandardContext filterStart
SEVERE: Exception starting filter [SolrFilter]
java.lang.NoClassDefFoundError: Could not initialize class
org.slf4j.impl.StaticLoggerBinder
at
org.apache.solr.util.StartupLoggingUtils.(StartupLoggingUtils.java:45)
at
org.apache.solr.servlet.SolrDispatchFilter.init(SolrDispatchFilter.java:158)
at
org.apache.ofbiz.solr.webapp.OFBizSolrContextFilter.init(OFBizSolrContextFilter.java:100)
at
org.apache.catalina.core.ApplicationFilterConfig.initFilter(ApplicationFilterConfig.java:270)
at
org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:251)
at
org.apache.catalina.core.ApplicationFilterConfig.(ApplicationFilterConfig.java:101)
at
org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4613)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5256)
at
[jira] [Commented] (OFBIZ-12459) Cybersource - configuration
[ https://issues.apache.org/jira/browse/OFBIZ-12459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17461369#comment-17461369 ] Pierre Smits commented on OFBIZ-12459: -- [~mbrohl] Switching over to using SystemProperty records for runtime configuration is an ongoing effort since it was introduced way back when in 2012, effected by contributors of all kinds. Never before somewhere in 2018, in your 20 years of history with OFBiz (or even the 15 years of this project being part of the ASF) have you 'collaborated' on this subject. And even when you started providing comments/suggestions to the subject, you couldn't convince the community to change directions. Here, elsewhere, you keep circling back, or referring to creating a mess for users. But the thing is that by insisting (like you do) on not moving forward you perpetuate the mess. Not only regarding this aspects, but others as well. A while back I advised you to read the header of OFBiz code files. Apparently you did not learn anything from those files, still thinking that the project must ensure any kind of compatibility. You claim to know what OFBiz users want/need from the project. I suggest you wake up. You're no OFBiz user! And what you know about what OFBiz users wanted/needed is from the limited few that paid you regarding the implementations you worked on. You talk about destroying trust? You made me both cringe and laugh when you mentioned that. In an other ticket discussion, you insist on not improving just that trust by rejecting that fields like createdByUserLogin and modifiedByUserLogin should be part of the metadata fields automatically added and populated. Fields that are included in every piece of serious software (like SalesForce, Microsoft Dynamics 365, SAP, etc.). If you're so dissatisfied about the direction of the project, I suggest you follow the route other (privileged) contributors embarked on and start working on and promoting your own derivative. And, if you're dissatisfied with how contributors react to your kind of collaboration I suggest you take a hard look at your own actions and [those tickets | https://issues.apache.org/jira/issues/?jql=project%20%3D%20OFBIZ%20AND%20resolution%20%3D%20Unresolved%20AND%20assignee%20in%20(mbrohl)%20ORDER%20BY%20updated%20DESC] you're 'collaborating on'. I appreciate suggestions, but nowhere is it stated that any other contributor (or I) *must* follow that, or adhere your kind of collaboration, blindly. I object to your kind of collaboration. I reject your kind of collaboration. Your kind of collaboration moves (contributions to) the project to a grinding halt. You can't even seem to able to collaborate with the contributors from your own company to get their contributions to move the project forward. I rather have you 'collaborate' similarly to the dozens of other privileged contributors than you injecting your unwanted kind of collaboration into tickets. So you ask yourself what else can you do... Here are a few suggestions (how you can adjust your kind of collaborating for the good of the project, its users and its contributors): * go 'collaborate' with someone else, and stop stalking me, * go take any of the tickets you have assigned yourself to and work those to a satisfactory resolution, instead of 'managing' the status, * go take any PR that is good enough and merge that into the code base, * go take any other open ticket and work that to a satisfactory resolution, * go take any Confluence page that is WIP and work that to an acceptable level. > Cybersource - configuration > --- > > Key: OFBIZ-12459 > URL: https://issues.apache.org/jira/browse/OFBIZ-12459 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: 3rdParty, cybersource, fintech, integration > > Move 3rd party Fintech integration configuration for Cybersource from > initialisation configuration to runtime configuration. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (OFBIZ-12450) Price Rules: Price rules configurations are not syncing with eCommerce storefront
[ https://issues.apache.org/jira/browse/OFBIZ-12450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17461324#comment-17461324 ] Pierre Smits edited comment on OFBIZ-12450 at 12/17/21, 10:19 AM: -- According to the code, price calculations for Party Classification (PRIP_PARTY_CLAS) is still marked as TODO. At line 1197 PRIP_PARTY_CLASS is evaluated as an inputParamEnumId of productPricCond was (Author: pfm.smits): According to the code, price calculations for Party Classification is still marked as TODO. > Price Rules: Price rules configurations are not syncing with eCommerce > storefront > - > > Key: OFBIZ-12450 > URL: https://issues.apache.org/jira/browse/OFBIZ-12450 > Project: OFBiz > Issue Type: Bug > Components: product/catalog >Affects Versions: Trunk >Reporter: Justine Nowak >Assignee: Pierre Smits >Priority: Critical > Labels: user-experience > > When adding a Price Rule, whether it be a Product Category, Product, Party, > Party Classification, the system doesn't show a price difference. > > The price rules work with the Database as they do get changed when saved. But > their functionality doesn't work, it won't give a price increase or decrease > or restriction. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-12450) Price Rules: Price rules configurations are not syncing with eCommerce storefront
[ https://issues.apache.org/jira/browse/OFBIZ-12450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17461324#comment-17461324 ] Pierre Smits commented on OFBIZ-12450: -- According to the code, price calculations for Party Classification is still marked as TODO. > Price Rules: Price rules configurations are not syncing with eCommerce > storefront > - > > Key: OFBIZ-12450 > URL: https://issues.apache.org/jira/browse/OFBIZ-12450 > Project: OFBiz > Issue Type: Bug > Components: product/catalog >Affects Versions: Trunk >Reporter: Justine Nowak >Assignee: Pierre Smits >Priority: Critical > Labels: user-experience > > When adding a Price Rule, whether it be a Product Category, Product, Party, > Party Classification, the system doesn't show a price difference. > > The price rules work with the Database as they do get changed when saved. But > their functionality doesn't work, it won't give a price increase or decrease > or restriction. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-12450) Price Rules: Price rules configurations are not syncing with eCommerce storefront
[ https://issues.apache.org/jira/browse/OFBIZ-12450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17461321#comment-17461321 ] Pierre Smits commented on OFBIZ-12450: -- Price calculations working with price rules is done through PriceServices.java According to the code price calculations should work for following conditions (as referenced in the description): * Product Category (productCateogryId * Product Id (both productId and pvirtualProductId) * Party (partyId) And there are others referenced (based on records in the Enumeration table with enumTypeId="PROD_PRICE_IN_PARAM") > Price Rules: Price rules configurations are not syncing with eCommerce > storefront > - > > Key: OFBIZ-12450 > URL: https://issues.apache.org/jira/browse/OFBIZ-12450 > Project: OFBiz > Issue Type: Bug > Components: product/catalog >Affects Versions: Trunk >Reporter: Justine Nowak >Assignee: Pierre Smits >Priority: Critical > Labels: user-experience > > When adding a Price Rule, whether it be a Product Category, Product, Party, > Party Classification, the system doesn't show a price difference. > > The price rules work with the Database as they do get changed when saved. But > their functionality doesn't work, it won't give a price increase or decrease > or restriction. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (OFBIZ-12450) Price Rules: Price rules configurations are not syncing with eCommerce storefront
[ https://issues.apache.org/jira/browse/OFBIZ-12450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-12450: Assignee: Pierre Smits > Price Rules: Price rules configurations are not syncing with eCommerce > storefront > - > > Key: OFBIZ-12450 > URL: https://issues.apache.org/jira/browse/OFBIZ-12450 > Project: OFBiz > Issue Type: Bug > Components: product/catalog >Affects Versions: Trunk >Reporter: Justine Nowak >Assignee: Pierre Smits >Priority: Critical > Labels: user-experience > > When adding a Price Rule, whether it be a Product Category, Product, Party, > Party Classification, the system doesn't show a price difference. > > The price rules work with the Database as they do get changed when saved. But > their functionality doesn't work, it won't give a price increase or decrease > or restriction. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (OFBIZ-12465) PriceScreens.xml - incorrect reference in screen
[ https://issues.apache.org/jira/browse/OFBIZ-12465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed OFBIZ-12465. Fix Version/s: Upcoming Branch Resolution: Fixed Thanks to Jacques for his assistance to get this into the codebase. > PriceScreens.xml - incorrect reference in screen > > > Key: OFBIZ-12465 > URL: https://issues.apache.org/jira/browse/OFBIZ-12465 > Project: OFBiz > Issue Type: Bug > Components: product/catalog >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Fix For: Upcoming Branch > > > With commit > [92533b5|https://github.com/apache/ofbiz-framework/commit/92533b5651af6cd9f10db1e429b4eed0fee55aae] > the reference in screen FindProductPriceRule was not changed when the > relating object in PriceForms.xml changed from form to grid. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (OFBIZ-12465) PriceScreens.xml - incorrect reference in screen
Pierre Smits created OFBIZ-12465: Summary: PriceScreens.xml - incorrect reference in screen Key: OFBIZ-12465 URL: https://issues.apache.org/jira/browse/OFBIZ-12465 Project: OFBiz Issue Type: Bug Components: product/catalog Affects Versions: Trunk Reporter: Pierre Smits Assignee: Pierre Smits With commit [92533b5|https://github.com/apache/ofbiz-framework/commit/92533b5651af6cd9f10db1e429b4eed0fee55aae] the reference in screen FindProductPriceRule was not changed when the relating object in PriceForms.xml changed from form to grid. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (OFBIZ-1151) Passwords are not salted
[ https://issues.apache.org/jira/browse/OFBIZ-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed OFBIZ-1151. --- Assignee: (was: Adam Heath) Resolution: Not A Problem Closing as it is either already resolved in another way or due to lack of interest of the community. > Passwords are not salted > > > Key: OFBIZ-1151 > URL: https://issues.apache.org/jira/browse/OFBIZ-1151 > Project: OFBiz > Issue Type: Sub-task > Components: party >Affects Versions: Release Branch 4.0, Trunk >Reporter: Wickersheimer Jeremy >Priority: Minor > > Password are currently hashed but not seeded which may be a security issue. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-10333) Improve Party
[ https://issues.apache.org/jira/browse/OFBIZ-10333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17460560#comment-17460560 ] Pierre Smits commented on OFBIZ-10333: -- IMO, action triggers should - as much as possible - be rendered through menus. We have ample possibilities (with various styles to apply) to achieve this, with appropriate permission handling, in an easy widget way. Menus can also be included in ftl templates. > Improve Party > - > > Key: OFBIZ-10333 > URL: https://issues.apache.org/jira/browse/OFBIZ-10333 > Project: OFBiz > Issue Type: Sub-task > Components: party >Affects Versions: Trunk >Reporter: Dennis Balkir >Assignee: Deepak Dixit >Priority: Minor > Attachments: OFBIZ-10221-party.template-party.AddCheckForParty.patch, > OFBIZ-10221-party.template-party.profileBlocks.ProductStores.patch, > OFBIZ-10221-party.template-party.profileBlocks.Visits.patch, > OFBIZ-10221-party.template.party.EditShoppingList.patch, > OFBIZ-10221-party.template.party.profileblocks.Attributes.patch, > OFBIZ-10221-party.template.party.profileblocks.Contact.patch, > OFBIZ-10221-party.template.party.profileblocks.Content.patch, > OFBIZ-10221-party.template.party.profileblocks.ContentList.patch, > OFBIZ-10221-party.template.party.profileblocks.Notes.patch, > OFBIZ-10221-party.template.party.profileblocks.UserLogin.patch > > > All improvements for layout and structure for the Order-Application -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-10470) Inconsistent screenlet-title containers
[
https://issues.apache.org/jira/browse/OFBIZ-10470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17460556#comment-17460556
]
Pierre Smits commented on OFBIZ-10470:
--
IMO, ftl templates should only be used for screen elements where a definition
in a Forms.xml file (form or grid) is either
* impossible to achieve, or
* too complex to be understood easily by a contributor (or a downstream)
developer, or
* javascript code cannot be included in a javascript file that is referenced
in a screen definition where it is needed
Definitions of the type screenlet (or rather anything that can be a screen
level), however, are not part of a form or grid definition, and should
therefore not be part of the ftl template.
> Inconsistent screenlet-title containers
> ---
>
> Key: OFBIZ-10470
> URL: https://issues.apache.org/jira/browse/OFBIZ-10470
> Project: OFBiz
> Issue Type: Improvement
>Reporter: Dennis Balkir
>Priority: Minor
>
> Through the OFBiz-Backend there is some inconsistency in the use of
> screenlet-titles.
> The title is normally nested inside this:
> {code:html}
>
>
>
> {code}
> But the title itself differs throughout the. backend quite often.
> As far as I have seen, there are 3 main kinds of title:
> # {code:html}
>
>
> Title
> {code}
> # {code:html}
>
>
> Title
> {code}
> # {code:html}
>
>
>
> Title
> {code}
> All three variants can be found right here:
> https://demo-trunk.ofbiz.apache.org/ordermgr/control/orderentry
> ({{li}} is used in the {{left}}-container, {{h3}} is used for "Create Sales
> Order" and {{div}} is used for the other screenlets)
> Wouldn't it be better to limit this to one kind of container, and maybe style
> the differences (if wanted) through classes?
> Or maybe two containers, which then can be styled differently?
> The way it is now, with most of them looking the same anyway, it seems rather
> confusing than useful
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (OFBIZ-12450) Price Rules: Price rules configurations are not syncing with eCommerce storefront
[ https://issues.apache.org/jira/browse/OFBIZ-12450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-12450: - Labels: user-experience (was: ) > Price Rules: Price rules configurations are not syncing with eCommerce > storefront > - > > Key: OFBIZ-12450 > URL: https://issues.apache.org/jira/browse/OFBIZ-12450 > Project: OFBiz > Issue Type: Bug > Components: product/catalog >Affects Versions: Trunk >Reporter: Justine Nowak >Priority: Critical > Labels: user-experience > > When adding a Price Rule, whether it be a Product Category, Product, Party, > Party Classification, the system doesn't show a price difference. > > The price rules work with the Database as they do get changed when saved. But > their functionality doesn't work, it won't give a price increase or decrease > or restriction. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (OFBIZ-12450) Price Rules: Price rules configurations are not syncing with eCommerce storefront
[ https://issues.apache.org/jira/browse/OFBIZ-12450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-12450: - Component/s: product/catalog (was: product) > Price Rules: Price rules configurations are not syncing with eCommerce > storefront > - > > Key: OFBIZ-12450 > URL: https://issues.apache.org/jira/browse/OFBIZ-12450 > Project: OFBiz > Issue Type: Bug > Components: product/catalog >Affects Versions: Trunk >Reporter: Justine Nowak >Priority: Critical > > When adding a Price Rule, whether it be a Product Category, Product, Party, > Party Classification, the system doesn't show a price difference. > > The price rules work with the Database as they do get changed when saved. But > their functionality doesn't work, it won't give a price increase or decrease > or restriction. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (OFBIZ-12463) Payment Group Common Decorator
Pierre Smits created OFBIZ-12463: Summary: Payment Group Common Decorator Key: OFBIZ-12463 URL: https://issues.apache.org/jira/browse/OFBIZ-12463 Project: OFBiz Issue Type: Improvement Components: accounting Affects Versions: Trunk Reporter: Pierre Smits Assignee: Pierre Smits title of a payment group is shown below its menu(s) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (OFBIZ-12458) Invoice - CommonInvoiceDecorator
[ https://issues.apache.org/jira/browse/OFBIZ-12458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-12458: - Environment: (was: label for invoice is shown below Invoice menus) > Invoice - CommonInvoiceDecorator > > > Key: OFBIZ-12458 > URL: https://issues.apache.org/jira/browse/OFBIZ-12458 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: invoice, usability > > label for invoice is shown below Invoice menus -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (OFBIZ-12462) Agreement - CommonAgreementDecorator
Pierre Smits created OFBIZ-12462: Summary: Agreement - CommonAgreementDecorator Key: OFBIZ-12462 URL: https://issues.apache.org/jira/browse/OFBIZ-12462 Project: OFBiz Issue Type: Improvement Components: accounting Affects Versions: Trunk Reporter: Pierre Smits Assignee: Pierre Smits title of an agreement is shown below its menu(s). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-12459) Cybersource - configuration
[
https://issues.apache.org/jira/browse/OFBIZ-12459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17460048#comment-17460048
]
Pierre Smits commented on OFBIZ-12459:
--
[~mbrohl]
As it stands now, the only thing I see you doing is commenting/complaining from
the back bench, twisting and turning - and providing (IMO) politically
motivated arguments - to get your way. Which is, as I see it, to *not* improve
OFBiz in favour of that being left in the hands of OFBiz integrators, and is
rather intended to influence others from collaborating with me and merging (my)
contributions into the codebase.
As soon as you actually start merging my contributions into the codebase,
actually start collaborating with me on improvements, actually start
recognising my merit, my way (of reacting to your comments) may change.
A suggestion: if you're so keen on OFBiz users working with having
SystemProperty configuration records as .property file elements (as you
remarked in OFBIZ-6670 regarding OFBiz DEVOPS work being a nightmare), why
don't you contribute e.g. a Confluence page called:
{noformat}
How To Convert SystemProperty Data Elements to '.property'File Elements - For
OFBiz DEVOPS{noformat}
> Cybersource - configuration
> ---
>
> Key: OFBIZ-12459
> URL: https://issues.apache.org/jira/browse/OFBIZ-12459
> Project: OFBiz
> Issue Type: Improvement
> Components: accounting
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Pierre Smits
>Priority: Major
> Labels: 3rdParty, cybersource, fintech, integration
>
> Move 3rd party Fintech integration configuration for Cybersource from
> initialisation configuration to runtime configuration.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (OFBIZ-12461) Missing attribute 'description' on element 'entity-options'
[
https://issues.apache.org/jira/browse/OFBIZ-12461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17459990#comment-17459990
]
Pierre Smits commented on OFBIZ-12461:
--
Ahh. Yes. An older release of OFBiz could have that issue still.
Thanks for the follow-up, Danny. Much obliged.
> Missing attribute 'description' on element 'entity-options'
> ---
>
> Key: OFBIZ-12461
> URL: https://issues.apache.org/jira/browse/OFBIZ-12461
> Project: OFBiz
> Issue Type: Improvement
> Components: product/catalog
>Affects Versions: Trunk
>Reporter: Danny Trunk
>Priority: Minor
>
> Log Warning:
> {code:java}
> XmlFileLoader: File
> file:/.../applications/product/widget/catalog/ProductForms.xml process error.
> Line: 131. Error message: cvc-complex-type.4: Attribute 'description' must
> appear on element 'entity-options'.{code}
> There are several other places in that XML file and maybe other XML files
> where the description attribute is missing on entity-options elements.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (OFBIZ-12459) Cybersource - configuration
[
https://issues.apache.org/jira/browse/OFBIZ-12459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17459981#comment-17459981
]
Pierre Smits commented on OFBIZ-12459:
--
[~mbrohl]
Please stop your silly complaints.
when
{noformat}
forces the user to use SystemProperty{noformat}
is unreasonable, then the opposite (forcing the user to use a .property file
for a runtime configuration) is equally so. This project is
> Cybersource - configuration
> ---
>
> Key: OFBIZ-12459
> URL: https://issues.apache.org/jira/browse/OFBIZ-12459
> Project: OFBiz
> Issue Type: Improvement
> Components: accounting
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Pierre Smits
>Priority: Major
> Labels: 3rdParty, cybersource, fintech, integration
>
> Move 3rd party Fintech integration configuration for Cybersource from
> initialisation configuration to runtime configuration.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (OFBIZ-12461) Missing attribute 'description' on element 'entity-options'
[
https://issues.apache.org/jira/browse/OFBIZ-12461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17459970#comment-17459970
]
Pierre Smits commented on OFBIZ-12461:
--
Hi [~dtrunk90],
Can you elaborate a bit more on when this is happening? I tried today against
trunk. And this
Attribute 'description' must appear on element 'entity-options'
didn't appear in my logs, nor in my IDE.
What is the release of OFBiz that you are using? What platform?
> Missing attribute 'description' on element 'entity-options'
> ---
>
> Key: OFBIZ-12461
> URL: https://issues.apache.org/jira/browse/OFBIZ-12461
> Project: OFBiz
> Issue Type: Improvement
> Components: product/catalog
>Affects Versions: Trunk
>Reporter: Danny Trunk
>Priority: Minor
>
> Log Warning:
> {code:java}
> XmlFileLoader: File
> file:/.../applications/product/widget/catalog/ProductForms.xml process error.
> Line: 131. Error message: cvc-complex-type.4: Attribute 'description' must
> appear on element 'entity-options'.{code}
> There are several other places in that XML file and maybe other XML files
> where the description attribute is missing on entity-options elements.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (OFBIZ-12461) Missing attribute 'description' on element 'entity-options'
[
https://issues.apache.org/jira/browse/OFBIZ-12461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Smits updated OFBIZ-12461:
-
Labels: (was: catalog)
> Missing attribute 'description' on element 'entity-options'
> ---
>
> Key: OFBIZ-12461
> URL: https://issues.apache.org/jira/browse/OFBIZ-12461
> Project: OFBiz
> Issue Type: Improvement
> Components: product/catalog
>Affects Versions: Trunk
>Reporter: Danny Trunk
>Priority: Minor
>
> Log Warning:
> {code:java}
> XmlFileLoader: File
> file:/.../applications/product/widget/catalog/ProductForms.xml process error.
> Line: 131. Error message: cvc-complex-type.4: Attribute 'description' must
> appear on element 'entity-options'.{code}
> There are several other places in that XML file and maybe other XML files
> where the description attribute is missing on entity-options elements.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (OFBIZ-12461) Missing attribute 'description' on element 'entity-options'
[
https://issues.apache.org/jira/browse/OFBIZ-12461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Smits updated OFBIZ-12461:
-
Component/s: product/catalog
(was: product)
> Missing attribute 'description' on element 'entity-options'
> ---
>
> Key: OFBIZ-12461
> URL: https://issues.apache.org/jira/browse/OFBIZ-12461
> Project: OFBiz
> Issue Type: Improvement
> Components: product/catalog
>Affects Versions: Trunk
>Reporter: Danny Trunk
>Priority: Minor
> Labels: catalog
>
> Log Warning:
> {code:java}
> XmlFileLoader: File
> file:/.../applications/product/widget/catalog/ProductForms.xml process error.
> Line: 131. Error message: cvc-complex-type.4: Attribute 'description' must
> appear on element 'entity-options'.{code}
> There are several other places in that XML file and maybe other XML files
> where the description attribute is missing on entity-options elements.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (OFBIZ-12461) Missing attribute 'description' on element 'entity-options'
[
https://issues.apache.org/jira/browse/OFBIZ-12461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Smits updated OFBIZ-12461:
-
Labels: catalog (was: )
> Missing attribute 'description' on element 'entity-options'
> ---
>
> Key: OFBIZ-12461
> URL: https://issues.apache.org/jira/browse/OFBIZ-12461
> Project: OFBiz
> Issue Type: Improvement
> Components: product
>Affects Versions: Trunk
>Reporter: Danny Trunk
>Priority: Minor
> Labels: catalog
>
> Log Warning:
> {code:java}
> XmlFileLoader: File
> file:/.../applications/product/widget/catalog/ProductForms.xml process error.
> Line: 131. Error message: cvc-complex-type.4: Attribute 'description' must
> appear on element 'entity-options'.{code}
> There are several other places in that XML file and maybe other XML files
> where the description attribute is missing on entity-options elements.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (OFBIZ-12460) Unable to build in M1 Mac
[
https://issues.apache.org/jira/browse/OFBIZ-12460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Smits updated OFBIZ-12460:
-
Environment:
Apple Mac: M1 processor
Java version:
Ofbiz release/branche
> Unable to build in M1 Mac
> -
>
> Key: OFBIZ-12460
> URL: https://issues.apache.org/jira/browse/OFBIZ-12460
> Project: OFBiz
> Issue Type: Bug
> Components: themes
>Affects Versions: Upcoming Branch
> Environment: Apple Mac: M1 processor
> Java version:
> Ofbiz release/branche
>Reporter: James Yong
>Assignee: James Yong
>Priority: Minor
> Fix For: Upcoming Branch
>
>
> Following error occurs when building in M1 Mac
> {code:java}
> Could not determine the dependencies of task ':nodeSetup'.
> > Failed to query the value of task ':nodeSetup' property 'nodeArchiveFile'.
>> Could not resolve all files for configuration ':detachedConfiguration1'.
> > Could not find node-12.18.1-darwin-arm64.tar.gz
> (org.nodejs:node:12.18.1).
> Searched in the following locations:
> https://nodejs.org/dist/v12.18.1/node-v12.18.1-darwin-arm64.tar.gz
> {code}
> Need to upgrade Node.js version from 12.x.x to 16.x.x as 16.x.x has support
> for M1 Mac.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (OFBIZ-12460) Unable to build in M1 Mac
[
https://issues.apache.org/jira/browse/OFBIZ-12460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Smits updated OFBIZ-12460:
-
Labels: build-failure (was: )
> Unable to build in M1 Mac
> -
>
> Key: OFBIZ-12460
> URL: https://issues.apache.org/jira/browse/OFBIZ-12460
> Project: OFBiz
> Issue Type: Bug
> Components: themes
>Affects Versions: Upcoming Branch
> Environment: Apple Mac: M1 processor
> Java version:
> Ofbiz release/branche
>Reporter: James Yong
>Assignee: James Yong
>Priority: Minor
> Labels: build-failure
> Fix For: Upcoming Branch
>
>
> Following error occurs when building in M1 Mac
> {code:java}
> Could not determine the dependencies of task ':nodeSetup'.
> > Failed to query the value of task ':nodeSetup' property 'nodeArchiveFile'.
>> Could not resolve all files for configuration ':detachedConfiguration1'.
> > Could not find node-12.18.1-darwin-arm64.tar.gz
> (org.nodejs:node:12.18.1).
> Searched in the following locations:
> https://nodejs.org/dist/v12.18.1/node-v12.18.1-darwin-arm64.tar.gz
> {code}
> Need to upgrade Node.js version from 12.x.x to 16.x.x as 16.x.x has support
> for M1 Mac.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (OFBIZ-12459) Cybersource - configuration
[ https://issues.apache.org/jira/browse/OFBIZ-12459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-12459: - Summary: Cybersource - configuration (was: Cybersource - from payment.properties to SystemProperty) > Cybersource - configuration > --- > > Key: OFBIZ-12459 > URL: https://issues.apache.org/jira/browse/OFBIZ-12459 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: 3rdParty, cybersource, fintech, integration > > Move 3rd party Fintech integration configuration for Cybersource from > initialisation configuration to runtime configuration. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (OFBIZ-12459) Cybersource - from payment.properties to SystemProperty
Pierre Smits created OFBIZ-12459: Summary: Cybersource - from payment.properties to SystemProperty Key: OFBIZ-12459 URL: https://issues.apache.org/jira/browse/OFBIZ-12459 Project: OFBiz Issue Type: Improvement Components: accounting Affects Versions: Trunk Reporter: Pierre Smits Assignee: Pierre Smits Move 3rd party Fintech integration configuration for Cybersource from initialisation configuration to runtime configuration. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (OFBIZ-3278) Improvement in Cybersource integration to better handle a sale transaction response
[ https://issues.apache.org/jira/browse/OFBIZ-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-3278: Labels: 3rdParty cybersource integration (was: ) > Improvement in Cybersource integration to better handle a sale transaction > response > --- > > Key: OFBIZ-3278 > URL: https://issues.apache.org/jira/browse/OFBIZ-3278 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Pranay Pandey >Assignee: Ashish Vijaywargiya >Priority: Minor > Labels: 3rdParty, cybersource, integration > Fix For: Trunk > > Attachments: OFBIZ-3278.patch > > > For running the sale transaction that is auth+capture in a single transaction > we set field autoBill to true in PaymentGatewayCyberSource entity or > payment.cybersource.autoBill to true in payment.properties. > Improvement in code for Cybersource integration to handle better sale > transaction response is needed. Sale transaction is used in Cybersource > integration to provide payment authorization and capture together. Its > already supported but improvement is needed so that transaction can be better > entered in the system for further review for a specific order. -- This message was sent by Atlassian Jira (v8.20.1#820001)
