[jira] [Assigned] (OFBIZ-11457) Expected arrival of Incoming Shipment needs to be reflected over back-order
[ https://issues.apache.org/jira/browse/OFBIZ-11457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankush Upadhyay reassigned OFBIZ-11457: --- Assignee: Ankush Upadhyay > Expected arrival of Incoming Shipment needs to be reflected over back-order > --- > > Key: OFBIZ-11457 > URL: https://issues.apache.org/jira/browse/OFBIZ-11457 > Project: OFBiz > Issue Type: New Feature > Components: order >Reporter: Swapnil Shah >Assignee: Ankush Upadhyay >Priority: Major > Fix For: Upcoming Branch > > > *Business Case* > Many a times its required to promise the delivery date to customers for her > sales orders that are back-order (BO) based on the expected arrival of future > incoming/purchase shipments. Currently its not possible without either > manually pegging the supply to demand or having the MRP run. > *Scope* > The scope of demand versus supply pegging is limited to purchase shipments > only assuming that shipment data would be synced back in Ofbiz and > procurement/replenishment would be external to OFbiz universe. If that is not > the case then MRP run might be preferred way to achieve the same. > *Possible Solution* > To solve for this problem on real time basis, the Reservation flow can be > leveraged as that makes the determination whether the punched in sales order > (or demand for production run for that matter) is going to be backordered or > not. > If and when there is SHIPMENT.ESTIMATED_ARRIVAL_DATE available against the > scheduled or incoming receipts in the system say with > SHIPMENT_TYPE_ID=PURCHASE_SHIPMENT (or INCOMING_SHIPMENT) then the > reservation or post-reservation run can be triggered to peg and allocate the > expected shipment volume to backorders on FIFO basis and inherit the earliest > SHIPMENT.ESTIMATED_ARRIVAL_DATE over > ORDER_ITEM_SHIP_GRP_INV_RES.PROMISED_DATETIME which can be promised and > communicated to customer. > *Use Cases* > 1. Product GZ-2644 has 50 units backordered across 2 sales order placed on > different dates: > ORDER_1 : Placed as BO on 01/01/2020 with Order Qty = 30 units with all > units backordered > ORDER_2 : Placed as BO on 01/03/2020 with Order Qty = 20 units with all > units backordered > Two Shipments for Product GZ-2644 scheduled to arrive on different dates as > follows: > SHIPMENT_1 : Estimated Arrival Date on 01/25/2020 with Qty=20 units > SHIPMENT_2 : Estimated Arrival Date on 01/31/2020 with Qty=40 units > _*Expected Result*_ > Upon reservation, here is how they would get their promised date: > ORDER_1: Although its pegged to both the shipment (i.e., 20 units from > SHIPMENT_1 and 10 units from SHIPMENT_2) but gets the Promise Date of > 01/25/2020 (as shortness takes precedence over lateness) > ORDER_2: It gets pegged to second shipment (20 units from SHIPMENT_2) and > gets the Promise Date of 01/31/2020 > 2. Product GZ-2644 has 50 units backordered across 2 sales order placed on > different dates but also has Safety Stock threshold of 30 units to be > maintained: > ORDER_1 : Placed as BO on 01/01/2020 with Order Qty = 30 units with all > units backordered > ORDER_2 : Placed as BO on 01/03/2020 with Order Qty = 20 units with all > units backordered > Two Shipments for Product GZ-2644 scheduled to arrive on different dates as > follows: > SHIPMENT_1 : Estimated Arrival Date on 01/25/2020 with Qty=20 units > SHIPMENT_2 : Estimated Arrival Date on 01/31/2020 with Qty=40 units > _*Expected Result*_ > Upon reservation, here is how they would get their promised date: > ORDER_1: After allocating 30 units for Safety Stock (i,e., 20 units from > SHIPMENT_1 and 10 units from SHIPMENT_2), its pegged to the second shipment > (i.e., 20 units left from SHIPMENT_2) and gets the Promise Date of 01/31/2020 > (as Safety Stock takes precedence over sales orders) > ORDER_2: It gets no shipment left to peg to and hence no promised date or > can be defaulted based on average lead time from supplier. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-641) Integrate Mondrian OLAP
[ https://issues.apache.org/jira/browse/OFBIZ-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-641: --- Labels: Fact birt dimension dwh olap rolap starschema (was: ) > Integrate Mondrian OLAP > --- > > Key: OFBIZ-641 > URL: https://issues.apache.org/jira/browse/OFBIZ-641 > Project: OFBiz > Issue Type: New Feature > Components: bi >Affects Versions: Trunk >Reporter: Chris Howe >Priority: Minor > Labels: Fact, birt, dimension, dwh, olap, rolap, starschema > Attachments: FoodMart2-drill-fail.zip, create-foodmart-mysql.zip, > datawarehouse1.patch, datawarehouse1.patch, freemrkrTransform.patch, > mth-drill-fail.jpg, mth-drill-ok.jpg, screenshot-1.jpg, screenshot-2.jpg > > > I'm currently working on integrating Mondrian OLAP using services and > simple-methods. I plan on doing this in a simliar manner that the Trixbox > (Asterisk) issue was done. I'm creating this issue now instead of when I > have something to add for collaboration reasons and so that I can play with > Mylar around this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-641) Integrate Mondrian OLAP
[ https://issues.apache.org/jira/browse/OFBIZ-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-641: --- Component/s: (was: framework) bi > Integrate Mondrian OLAP > --- > > Key: OFBIZ-641 > URL: https://issues.apache.org/jira/browse/OFBIZ-641 > Project: OFBiz > Issue Type: New Feature > Components: bi >Affects Versions: Trunk >Reporter: Chris Howe >Priority: Minor > Attachments: FoodMart2-drill-fail.zip, create-foodmart-mysql.zip, > datawarehouse1.patch, datawarehouse1.patch, freemrkrTransform.patch, > mth-drill-fail.jpg, mth-drill-ok.jpg, screenshot-1.jpg, screenshot-2.jpg > > > I'm currently working on integrating Mondrian OLAP using services and > simple-methods. I plan on doing this in a simliar manner that the Trixbox > (Asterisk) issue was done. I'm creating this issue now instead of when I > have something to add for collaboration reasons and so that I can play with > Mylar around this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11414) Improve the BI component
[ https://issues.apache.org/jira/browse/OFBIZ-11414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061692#comment-17061692 ] Pierre Smits commented on OFBIZ-11414: -- Adding the associated wiki page > Improve the BI component > > > Key: OFBIZ-11414 > URL: https://issues.apache.org/jira/browse/OFBIZ-11414 > Project: OFBiz > Issue Type: Improvement > Components: bi >Affects Versions: Upcoming Branch, Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: birt, dwh > Time Spent: 10m > Remaining Estimate: 0h > > Improving the BI component enhances the feature set of OFBiz. > The BI component is essential for doing analysis (trend and otherwise) on > data captured from transactions, while avoiding heavy (query) loads on the > transaction system. An additional benefit is that data analysts don't need > access/permissions to the transaction system. > This is a placeholder ticket to capture all underlying tickets (tasks) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11310) JSON renderer for screen/menu/form
[ https://issues.apache.org/jira/browse/OFBIZ-11310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Heintz updated OFBIZ-11310: --- Issue Type: New Feature (was: Improvement) > JSON renderer for screen/menu/form > --- > > Key: OFBIZ-11310 > URL: https://issues.apache.org/jira/browse/OFBIZ-11310 > Project: OFBiz > Issue Type: New Feature > Components: framework >Affects Versions: Trunk >Reporter: Olivier Heintz >Priority: Minor > Attachments: FrontJsFormRenderer.java, FrontJsMenuRenderer.java, > FrontJsOutput.java, FrontJsScreenRenderer.java, > FrontJsScreenViewHandler.java, FrontJsTreeRenderer.java, OFBIZ-11310.patch > > > In a POC approach for using a SPA framework for GUI in OFBiz, json renderer > have been developed. > This Jira could be used to do code review on these renderer. > Currently, these renderer are on a V0 situation, it's a work in process > situation. After mailing-list discussion with mathieu we decide to go to a > V0.1 by 2-3 tasks > * add some javadoc each time it's necessary or needed > * remove all comment code or explain the decision waiting to activate or > remove the code > * do checkstyle > On first step, code will be with only what is used in a use case (no code for > tag not currently manage). > Json renderer are part of vuejs-portal plugin, in ofbizextra gitlab > (https://gitlab.ofbizextra.org/ofbizextra/ofbizplugins/vuejsPortal), so > commit are done on it, and mailing-list with these commit [are > ofbizextra-com...@lists.sourceforge.net.|mailto:are%c2%a0ofbizextra-com...@lists.sourceforge.net.] > But we will publish an update on this Jira each week there are some > modifications on renderer files > This task will take some time because it will used to do a complete code > review, not only in renderer but in vuejs component too, and so complete > documentation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11310) JSON renderer for screen/menu/form
[ https://issues.apache.org/jira/browse/OFBIZ-11310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061638#comment-17061638 ] Olivier Heintz commented on OFBIZ-11310: clearly a new feature, even if it's only new renderer, a json renderer usable without vuejsPortal plugin > JSON renderer for screen/menu/form > --- > > Key: OFBIZ-11310 > URL: https://issues.apache.org/jira/browse/OFBIZ-11310 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Olivier Heintz >Priority: Minor > Attachments: FrontJsFormRenderer.java, FrontJsMenuRenderer.java, > FrontJsOutput.java, FrontJsScreenRenderer.java, > FrontJsScreenViewHandler.java, FrontJsTreeRenderer.java, OFBIZ-11310.patch > > > In a POC approach for using a SPA framework for GUI in OFBiz, json renderer > have been developed. > This Jira could be used to do code review on these renderer. > Currently, these renderer are on a V0 situation, it's a work in process > situation. After mailing-list discussion with mathieu we decide to go to a > V0.1 by 2-3 tasks > * add some javadoc each time it's necessary or needed > * remove all comment code or explain the decision waiting to activate or > remove the code > * do checkstyle > On first step, code will be with only what is used in a use case (no code for > tag not currently manage). > Json renderer are part of vuejs-portal plugin, in ofbizextra gitlab > (https://gitlab.ofbizextra.org/ofbizextra/ofbizplugins/vuejsPortal), so > commit are done on it, and mailing-list with these commit [are > ofbizextra-com...@lists.sourceforge.net.|mailto:are%c2%a0ofbizextra-com...@lists.sourceforge.net.] > But we will publish an update on this Jira each week there are some > modifications on renderer files > This task will take some time because it will used to do a complete code > review, not only in renderer but in vuejs component too, and so complete > documentation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11082) Improve the SalesInvoiceItemFact regarding dimensions
[ https://issues.apache.org/jira/browse/OFBIZ-11082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061577#comment-17061577 ] Pierre Smits commented on OFBIZ-11082: -- Patch available via https://github.com/apache/ofbiz-plugins/pull/11 See OFBIZ-11414 > Improve the SalesInvoiceItemFact regarding dimensions > - > > Key: OFBIZ-11082 > URL: https://issues.apache.org/jira/browse/OFBIZ-11082 > Project: OFBiz > Issue Type: Sub-task > Components: bi >Affects Versions: Release Branch 18.12, Release Branch 17.12, Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: Fact, SalesInvoiceItemFact, birt, dwh > > Improve the SIIF to include various dimensions, e.g. > * OrganisationDimension > * CustomerDimension > * etc > Have it working with dateDimeId as integer. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11081) Have a service to load records in the supplier dimension
[ https://issues.apache.org/jira/browse/OFBIZ-11081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061576#comment-17061576 ] Pierre Smits commented on OFBIZ-11081: -- Patch available via https://github.com/apache/ofbiz-plugins/pull/11 See OFBIZ-11414 > Have a service to load records in the supplier dimension > > > Key: OFBIZ-11081 > URL: https://issues.apache.org/jira/browse/OFBIZ-11081 > Project: OFBiz > Issue Type: Sub-task > Components: bi >Affects Versions: Release Branch 18.12, Release Branch 17.12, Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: SupplierDimension, birt, dimension, dwh, initialisation, > service, supplier > > for dwh initialisation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11031) Improve SalesOrderItemFact table
[ https://issues.apache.org/jira/browse/OFBIZ-11031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061575#comment-17061575 ] Pierre Smits commented on OFBIZ-11031: -- Patch available via https://github.com/apache/ofbiz-plugins/pull/11 See OFBIZ-11414 > Improve SalesOrderItemFact table > > > Key: OFBIZ-11031 > URL: https://issues.apache.org/jira/browse/OFBIZ-11031 > Project: OFBiz > Issue Type: Sub-task > Components: bi >Affects Versions: Release Branch 18.12, Release Branch 17.12, Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: Fact, SalesOrder, SalesOrderItemFact, birt, dwh > > Improve the SalesOrderFactTable to include additional dimensions, such as: > * AccountDimension > * CustomerDimension > * OrganisationDimension > * StoreDimension > * SalesChannelDimension > * SalesRepDimension > Have the entity work with dateDimId as integer. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-10953) have CurrencyDimension have a dimensionId that is based on the natural key
[ https://issues.apache.org/jira/browse/OFBIZ-10953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061573#comment-17061573 ] Pierre Smits commented on OFBIZ-10953: -- Patch available via https://github.com/apache/ofbiz-plugins/pull/11 See OFBIZ-11414 > have CurrencyDimension have a dimensionId that is based on the natural key > -- > > Key: OFBIZ-10953 > URL: https://issues.apache.org/jira/browse/OFBIZ-10953 > Project: OFBiz > Issue Type: Sub-task > Components: bi >Affects Versions: Release Branch 18.12, Release Branch 17.12, Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: CurrencyDimension, birt, currency, dimension, dwh > Attachments: 20200208_094840.jpg > > > Currently the record sequencer (delegator.getNextSeqId) is used to determine > the dimensionId for the CurrencyDimension. This is unnecessary as the uomId > from the UOM table can be used for currency. > It also makes it easier to set the foreign-key in fact tables by generating > it based on the date provided, than by retrieving the dimensionId based on a > retrieval through the getDimensionIdFromNaturalKey service. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (OFBIZ-10956) Have a service to load records in the CountryDimension
[ https://issues.apache.org/jira/browse/OFBIZ-10956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-10956: Assignee: Pierre Smits (was: Ankit Joshi) > Have a service to load records in the CountryDimension > -- > > Key: OFBIZ-10956 > URL: https://issues.apache.org/jira/browse/OFBIZ-10956 > Project: OFBiz > Issue Type: Sub-task > Components: bi >Affects Versions: Release Branch 18.12, Release Branch 17.12, Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: CountryDimension, birt, country, dimension, dwh, service > Attachments: OFBIZ-10956.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Depending on [OFBIZ-10954|https://issues.apache.org/jira/browse/OFBIZ-10954] > The service should be invoked on initialisation of the data warehouse. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-10956) Have a service to load records in the CountryDimension
[ https://issues.apache.org/jira/browse/OFBIZ-10956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061572#comment-17061572 ] Pierre Smits commented on OFBIZ-10956: -- Patch available via https://github.com/apache/ofbiz-plugins/pull/11 See OFBIZ-11414 > Have a service to load records in the CountryDimension > -- > > Key: OFBIZ-10956 > URL: https://issues.apache.org/jira/browse/OFBIZ-10956 > Project: OFBiz > Issue Type: Sub-task > Components: bi >Affects Versions: Release Branch 18.12, Release Branch 17.12, Trunk >Reporter: Pierre Smits >Assignee: Ankit Joshi >Priority: Major > Labels: CountryDimension, birt, country, dimension, dwh, service > Attachments: OFBIZ-10956.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Depending on [OFBIZ-10954|https://issues.apache.org/jira/browse/OFBIZ-10954] > The service should be invoked on initialisation of the data warehouse. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-10947) Have DateDimension have a dimensionId that is based on the natural key
[ https://issues.apache.org/jira/browse/OFBIZ-10947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061571#comment-17061571 ] Pierre Smits commented on OFBIZ-10947: -- Patch available via https://github.com/apache/ofbiz-plugins/pull/11 See OFBIZ-11414 > Have DateDimension have a dimensionId that is based on the natural key > -- > > Key: OFBIZ-10947 > URL: https://issues.apache.org/jira/browse/OFBIZ-10947 > Project: OFBiz > Issue Type: Sub-task > Components: bi >Affects Versions: Release Branch 16.11, Release Branch 18.12, Release > Branch 17.12, Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: DateDimension, birt, dimension, dwh > > Currently the record sequencer (delegator.getNextSeqId) is used to determine > the dimensionId for the DateDimension. This is unnecessary as the date (when > correctly formatted) can be used. > When formatted as 'MMdd' a dimensionId could be 20190423, which is a > correctly 'sequenced' primary key. > It also makes it easier to set the foreign-key in fact tables by generating > it based on the date, than by retrieving the dimensionId based on a retrieval > through the getDimensionIdFromNaturalKey service. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11438) Improve InventoryItemStarSchema
[ https://issues.apache.org/jira/browse/OFBIZ-11438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061569#comment-17061569 ] Pierre Smits commented on OFBIZ-11438: -- Patch available via https://github.com/apache/ofbiz-plugins/pull/11 See OFBIZ-11414 > Improve InventoryItemStarSchema > --- > > Key: OFBIZ-11438 > URL: https://issues.apache.org/jira/browse/OFBIZ-11438 > Project: OFBiz > Issue Type: Sub-task > Components: bi >Affects Versions: Release Branch 18.12, Release Branch 17.12, Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: birt, dwh, inventory, starschema > > Improve the InventoryItemStarSchema to include additional dimensions, such as: > * OrganisationDimension > * FacilityDimension > and work with integer based dimensionIds of the DateDimension -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11459) Improve the InventoryItemFact regarding dimensions
[ https://issues.apache.org/jira/browse/OFBIZ-11459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061568#comment-17061568 ] Pierre Smits commented on OFBIZ-11459: -- Patch available via https://github.com/apache/ofbiz-plugins/pull/11 See OFBIZ-11414 > Improve the InventoryItemFact regarding dimensions > -- > > Key: OFBIZ-11459 > URL: https://issues.apache.org/jira/browse/OFBIZ-11459 > Project: OFBiz > Issue Type: Sub-task > Components: bi >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: Fact, InventoryItemFact, birt, dwh > > Improve the IIF to include various dimensions, e.g. > FacilityDimension > OrganisationDimension > etc > Have it working with DateDimension based on dimensionId as integer -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-10944) Have a Customer Dimension
[ https://issues.apache.org/jira/browse/OFBIZ-10944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061570#comment-17061570 ] Pierre Smits commented on OFBIZ-10944: -- Patch available via https://github.com/apache/ofbiz-plugins/pull/11 See OFBIZ-11414 > Have a Customer Dimension > - > > Key: OFBIZ-10944 > URL: https://issues.apache.org/jira/browse/OFBIZ-10944 > Project: OFBiz > Issue Type: Sub-task > Components: bi >Affects Versions: Release Branch 16.11, Release Branch 18.12, Release > Branch 17.12, Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: CustomerDimension, birt, customer, dimension, dwh > > The component would benefit from a customer dimension for future fact tables > and star schema view entities -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11460) Make ReportBuilder more dynamic
[ https://issues.apache.org/jira/browse/OFBIZ-11460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061567#comment-17061567 ] Pierre Smits commented on OFBIZ-11460: -- Patch available via https://github.com/apache/ofbiz-plugins/pull/11 See OFBIZ-11414 > Make ReportBuilder more dynamic > --- > > Key: OFBIZ-11460 > URL: https://issues.apache.org/jira/browse/OFBIZ-11460 > Project: OFBiz > Issue Type: Sub-task > Components: bi >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: bi, birt, dwh, reporting, starschema > Attachments: BI-ReportBuilder-DynamicReport.png, > BI-ReportBuilder-DynamicSelection-Resuult.png, > BI-ReportBuilder-StartScreen.png > > > Currently the ReportBuilder requires that users must go back and forth when > they want to: > * switch star schemas > * select different fields > This can be made more user friendly by having a one-page solution. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-10990) Improve the SalesInvoiceItemStarSchema
[ https://issues.apache.org/jira/browse/OFBIZ-10990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061565#comment-17061565 ] Pierre Smits commented on OFBIZ-10990: -- Patch available via https://github.com/apache/ofbiz-plugins/pull/11 See OFBIZ-11414 > Improve the SalesInvoiceItemStarSchema > -- > > Key: OFBIZ-10990 > URL: https://issues.apache.org/jira/browse/OFBIZ-10990 > Project: OFBiz > Issue Type: Sub-task > Components: bi >Affects Versions: Release Branch 18.12, Release Branch 17.12, Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: SalesInvoiceItemStarSchema, birt, dwh, star, starschema > > The star schema should be improved to include elements from: > * Customer dimension -for aggregations per customer > * Country dimension - for aggregations per country > * Date dimension - for aggregations per date > * Store dimension - for aggregations per store > * Channel dimension - for aggregations per sales channel > * Time dimensions - for aggregations per time slot -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-10989) Have a Facility dimension
[ https://issues.apache.org/jira/browse/OFBIZ-10989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061564#comment-17061564 ] Pierre Smits commented on OFBIZ-10989: -- Patch available via https://github.com/apache/ofbiz-plugins/pull/11 See OFBIZ-11414 > Have a Facility dimension > - > > Key: OFBIZ-10989 > URL: https://issues.apache.org/jira/browse/OFBIZ-10989 > Project: OFBiz > Issue Type: Sub-task > Components: bi >Affects Versions: Release Branch 18.12, Release Branch 17.12, Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: FacilityDimension, birt, dimension, dwh, facility > > The component would benefit from a facility dimension for future fact tables > and star schema view entities. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-10996) Have a Supplier dimension
[ https://issues.apache.org/jira/browse/OFBIZ-10996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061563#comment-17061563 ] Pierre Smits commented on OFBIZ-10996: -- Patch available via https://github.com/apache/ofbiz-plugins/pull/11 See OFBIZ-11414 > Have a Supplier dimension > - > > Key: OFBIZ-10996 > URL: https://issues.apache.org/jira/browse/OFBIZ-10996 > Project: OFBiz > Issue Type: Sub-task > Components: bi >Affects Versions: Release Branch 18.12, Release Branch 17.12, Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: SupplierDimension, birt, dimension, dww, supplier > > The component would benefit from a Supplier dimension for future fact tables > and star schema view entities. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11066) Have a service to load records in the organisation dimension
[ https://issues.apache.org/jira/browse/OFBIZ-11066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061562#comment-17061562 ] Pierre Smits commented on OFBIZ-11066: -- Patch available via https://github.com/apache/ofbiz-plugins/pull/11 See OFBIZ-11414 > Have a service to load records in the organisation dimension > > > Key: OFBIZ-11066 > URL: https://issues.apache.org/jira/browse/OFBIZ-11066 > Project: OFBiz > Issue Type: Sub-task > Components: bi >Affects Versions: Release Branch 18.12, Release Branch 17.12, Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: OrganisationDimension, birt, dimension, dwh, > initialisation, service > > For dwh initialisation. Applicable to internal (accounting) organisations. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11072) Have a service to load records in the customer dimension
[ https://issues.apache.org/jira/browse/OFBIZ-11072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061557#comment-17061557 ] Pierre Smits commented on OFBIZ-11072: -- Patch available via https://github.com/apache/ofbiz-plugins/pull/11 See OFBIZ-11414 > Have a service to load records in the customer dimension > > > Key: OFBIZ-11072 > URL: https://issues.apache.org/jira/browse/OFBIZ-11072 > Project: OFBiz > Issue Type: Sub-task > Components: bi >Affects Versions: Release Branch 18.12, Release Branch 17.12 >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: CustomerDimension, birt, customer, dimension, dwh, > initialisation, service > > for dwh initialisation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11054) Have an Organisation Dimension
[ https://issues.apache.org/jira/browse/OFBIZ-11054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061559#comment-17061559 ] Pierre Smits commented on OFBIZ-11054: -- Patch available via https://github.com/apache/ofbiz-plugins/pull/11 See OFBIZ-11414 > Have an Organisation Dimension > -- > > Key: OFBIZ-11054 > URL: https://issues.apache.org/jira/browse/OFBIZ-11054 > Project: OFBiz > Issue Type: Sub-task > Components: bi >Affects Versions: Release Branch 18.12, Release Branch 17.12 >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: OrganisationDimension, birt, dimension, dwh > > The component would benefit from an organisation dimension for future fact > tables and star schema view entities. This dimension captures the attributes > of the internal (accounting) parties. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11065) Have a service to load records in the facility dimension
[ https://issues.apache.org/jira/browse/OFBIZ-11065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061561#comment-17061561 ] Pierre Smits commented on OFBIZ-11065: -- Patch available via https://github.com/apache/ofbiz-plugins/pull/11 See OFBIZ-11414 > Have a service to load records in the facility dimension > > > Key: OFBIZ-11065 > URL: https://issues.apache.org/jira/browse/OFBIZ-11065 > Project: OFBiz > Issue Type: Sub-task > Components: bi >Affects Versions: Release Branch 18.12, Release Branch 17.12, Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: FacilityDimension, birt, dimension, dwh, facility, > initialisation, service > > for dwh initialisation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11310) JSON renderer for screen/menu/form
[ https://issues.apache.org/jira/browse/OFBIZ-11310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061556#comment-17061556 ] Jacques Le Roux commented on OFBIZ-11310: - +1 with Pierre's remark > JSON renderer for screen/menu/form > --- > > Key: OFBIZ-11310 > URL: https://issues.apache.org/jira/browse/OFBIZ-11310 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Olivier Heintz >Priority: Minor > Attachments: FrontJsFormRenderer.java, FrontJsMenuRenderer.java, > FrontJsOutput.java, FrontJsScreenRenderer.java, > FrontJsScreenViewHandler.java, FrontJsTreeRenderer.java, OFBIZ-11310.patch > > > In a POC approach for using a SPA framework for GUI in OFBiz, json renderer > have been developed. > This Jira could be used to do code review on these renderer. > Currently, these renderer are on a V0 situation, it's a work in process > situation. After mailing-list discussion with mathieu we decide to go to a > V0.1 by 2-3 tasks > * add some javadoc each time it's necessary or needed > * remove all comment code or explain the decision waiting to activate or > remove the code > * do checkstyle > On first step, code will be with only what is used in a use case (no code for > tag not currently manage). > Json renderer are part of vuejs-portal plugin, in ofbizextra gitlab > (https://gitlab.ofbizextra.org/ofbizextra/ofbizplugins/vuejsPortal), so > commit are done on it, and mailing-list with these commit [are > ofbizextra-com...@lists.sourceforge.net.|mailto:are%c2%a0ofbizextra-com...@lists.sourceforge.net.] > But we will publish an update on this Jira each week there are some > modifications on renderer files > This task will take some time because it will used to do a complete code > review, not only in renderer but in vuejs component too, and so complete > documentation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-10998) Have a Time dimension
[ https://issues.apache.org/jira/browse/OFBIZ-10998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061554#comment-17061554 ] Pierre Smits commented on OFBIZ-10998: -- Patch available via https://github.com/apache/ofbiz-plugins/pull/11 See OFBIZ-11414 > Have a Time dimension > - > > Key: OFBIZ-10998 > URL: https://issues.apache.org/jira/browse/OFBIZ-10998 > Project: OFBiz > Issue Type: Sub-task > Components: bi >Affects Versions: Release Branch 18.12, Release Branch 17.12, Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: TimeDimension, birt, dimension, dwh, time > > The component would benefit from a time dimension for future fact tables and > star schema view entities. > Per comments in OFBIZ-10990: > As for time. yes we can add a static time dimension having are all time > increments between 00:00:00 and 23:59:59. If only using the minute > discriminator this would be a table consisting of 1440 records. > Businesses are not that much interested in sales/purchases/etc. per second, > whereas IT more often is (transactions per second), but at least the time > dimension will allow doing that in fact tables and star schemas. Businesses > are interested in stuff like: how do our sales in the morning compare to > sales in the afternoon, and how do our morning sales trend over time -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11465) prepareProductDimensionData does not load correct fields in ProductDimension
[
https://issues.apache.org/jira/browse/OFBIZ-11465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061553#comment-17061553
]
Pierre Smits commented on OFBIZ-11465:
--
Patch available via https://github.com/apache/ofbiz-plugins/pull/11 See
OFBIZ-11414
> prepareProductDimensionData does not load correct fields in ProductDimension
>
>
> Key: OFBIZ-11465
> URL: https://issues.apache.org/jira/browse/OFBIZ-11465
> Project: OFBiz
> Issue Type: Sub-task
> Components: bi
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Pierre Smits
>Priority: Major
> Labels: ProductDimension, birt, dimension, dwh, product, service
>
> With the implementation of the patch ofOFBIZ-10948 an error was introduced
> that led to fields in the ProductDimension to be populated in a wrong way.
> The replaced minilang code encompassed:
> {code:xml}
>
>
>
>
> property="ProductProductNotFoundWithProduct"/>
>
>
>
> value-field="productDimension"/>
>
> to-value-field="productType"/>
> from-field="productType.description"/>
>
>
> {code}
> This was replace with groovy code:
> {code:java}
> def prepareProductDimensionData() {
> GenericValue product = from("Product").where("productId",
> parameters.productId).queryOne()
> if (product == null) {
> return error(UtilProperties.getMessage('ProductUiLabels',
> 'ProductProductNotFoundWithProduct', locale))
> }
> productDimension = delegator.makeValue("ProductDimension")
> productDimension.setNonPKFields(parameters)
> GenericValue productType =
> select("description").from("Product").where("productId",
> parameters.productId).queryOne()
> productDimension.productType = productType.description
> Map result = success()
> result.productDimension = productDimension
> return result
> }
> {code}
> 2 things happened:
> * the key-value pairs of the product were not injected into the
> projectDimension object, but rather only parameters (not including these
> parse);
> * the description of the productType associated with the product was not
> injected into the productDimension object, but rather the description of the
> product.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (OFBIZ-11465) prepareProductDimensionData does not load correct fields in ProductDimension
Pierre Smits created OFBIZ-11465:
Summary: prepareProductDimensionData does not load correct fields
in ProductDimension
Key: OFBIZ-11465
URL: https://issues.apache.org/jira/browse/OFBIZ-11465
Project: OFBiz
Issue Type: Sub-task
Components: bi
Affects Versions: Trunk
Reporter: Pierre Smits
Assignee: Pierre Smits
With the implementation of the patch ofOFBIZ-10948 an error was introduced that
led to fields in the ProductDimension to be populated in a wrong way.
The replaced minilang code encompassed:
{code:xml}
{code}
This was replace with groovy code:
{code:java}
def prepareProductDimensionData() {
GenericValue product = from("Product").where("productId",
parameters.productId).queryOne()
if (product == null) {
return error(UtilProperties.getMessage('ProductUiLabels',
'ProductProductNotFoundWithProduct', locale))
}
productDimension = delegator.makeValue("ProductDimension")
productDimension.setNonPKFields(parameters)
GenericValue productType =
select("description").from("Product").where("productId",
parameters.productId).queryOne()
productDimension.productType = productType.description
Map result = success()
result.productDimension = productDimension
return result
}
{code}
2 things happened:
* the key-value pairs of the product were not injected into the
projectDimension object, but rather only parameters (not including these parse);
* the description of the productType associated with the product was not
injected into the productDimension object, but rather the description of the
product.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OFBIZ-11310) JSON renderer for screen/menu/form
[ https://issues.apache.org/jira/browse/OFBIZ-11310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061533#comment-17061533 ] Pierre Smits commented on OFBIZ-11310: -- Is it correct that this is not just an improvement, but rather a new feature, given the introduction of a new plugin (vuejsPortal)? > JSON renderer for screen/menu/form > --- > > Key: OFBIZ-11310 > URL: https://issues.apache.org/jira/browse/OFBIZ-11310 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Olivier Heintz >Priority: Minor > Attachments: FrontJsFormRenderer.java, FrontJsMenuRenderer.java, > FrontJsOutput.java, FrontJsScreenRenderer.java, > FrontJsScreenViewHandler.java, FrontJsTreeRenderer.java, OFBIZ-11310.patch > > > In a POC approach for using a SPA framework for GUI in OFBiz, json renderer > have been developed. > This Jira could be used to do code review on these renderer. > Currently, these renderer are on a V0 situation, it's a work in process > situation. After mailing-list discussion with mathieu we decide to go to a > V0.1 by 2-3 tasks > * add some javadoc each time it's necessary or needed > * remove all comment code or explain the decision waiting to activate or > remove the code > * do checkstyle > On first step, code will be with only what is used in a use case (no code for > tag not currently manage). > Json renderer are part of vuejs-portal plugin, in ofbizextra gitlab > (https://gitlab.ofbizextra.org/ofbizextra/ofbizplugins/vuejsPortal), so > commit are done on it, and mailing-list with these commit [are > ofbizextra-com...@lists.sourceforge.net.|mailto:are%c2%a0ofbizextra-com...@lists.sourceforge.net.] > But we will publish an update on this Jira each week there are some > modifications on renderer files > This task will take some time because it will used to do a complete code > review, not only in renderer but in vuejs component too, and so complete > documentation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11310) JSON renderer for screen/menu/form
[ https://issues.apache.org/jira/browse/OFBIZ-11310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061531#comment-17061531 ] Olivier Heintz commented on OFBIZ-11310: James, OFBIZ-11310.patch is not currently up to date. We are working to clean code in renderer and in vuejs, so vuejsPortal in gitlab.ofbizextra.org is the right place. To be able to test, the best way is to follow install documentation [https://ofbizextra.org/ofbizextra_adocs/docs/asciidoc/developer-manual.html#_poc_vuejs_portal] or you can test directly on the two "demo" site : * [https://ofbiz-selenium.ofbizextra.org/examplefjs/control/main] <= vuejs is build with dev to be able to look component and store in vuejs console but it's our integration plateform so with the cleaning sometime bugs are present ;) * [https://demo-vuejs.ofbizextra.org/examplefjs/control/main] more stable version but npm build with prod If you need, I can update the patch. > JSON renderer for screen/menu/form > --- > > Key: OFBIZ-11310 > URL: https://issues.apache.org/jira/browse/OFBIZ-11310 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Olivier Heintz >Priority: Minor > Attachments: FrontJsFormRenderer.java, FrontJsMenuRenderer.java, > FrontJsOutput.java, FrontJsScreenRenderer.java, > FrontJsScreenViewHandler.java, FrontJsTreeRenderer.java, OFBIZ-11310.patch > > > In a POC approach for using a SPA framework for GUI in OFBiz, json renderer > have been developed. > This Jira could be used to do code review on these renderer. > Currently, these renderer are on a V0 situation, it's a work in process > situation. After mailing-list discussion with mathieu we decide to go to a > V0.1 by 2-3 tasks > * add some javadoc each time it's necessary or needed > * remove all comment code or explain the decision waiting to activate or > remove the code > * do checkstyle > On first step, code will be with only what is used in a use case (no code for > tag not currently manage). > Json renderer are part of vuejs-portal plugin, in ofbizextra gitlab > (https://gitlab.ofbizextra.org/ofbizextra/ofbizplugins/vuejsPortal), so > commit are done on it, and mailing-list with these commit [are > ofbizextra-com...@lists.sourceforge.net.|mailto:are%c2%a0ofbizextra-com...@lists.sourceforge.net.] > But we will publish an update on this Jira each week there are some > modifications on renderer files > This task will take some time because it will used to do a complete code > review, not only in renderer but in vuejs component too, and so complete > documentation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11453) repository ofbiz-tools does not have a license
[ https://issues.apache.org/jira/browse/OFBIZ-11453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061497#comment-17061497 ] Jacques Le Roux commented on OFBIZ-11453: - As you can read here: http://www.apache.org/dev/licensing-howto.html#mod-notice it's needed, that's why we have it in framework and plugins repos bq. Aside from Apache-licensed dependencies which supply NOTICE files of their own > repository ofbiz-tools does not have a license > -- > > Key: OFBIZ-11453 > URL: https://issues.apache.org/jira/browse/OFBIZ-11453 > Project: OFBiz > Issue Type: Bug > Components: tools >Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Major > Labels: license > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11452) repository ofbiz-site does not have a license
[ https://issues.apache.org/jira/browse/OFBIZ-11452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061498#comment-17061498 ] Jacques Le Roux commented on OFBIZ-11452: - As you can read here: http://www.apache.org/dev/licensing-howto.html#mod-notice it's needed, that's why we have it in framework and plugins repos bq. Aside from Apache-licensed dependencies which supply NOTICE files of their own > repository ofbiz-site does not have a license > - > > Key: OFBIZ-11452 > URL: https://issues.apache.org/jira/browse/OFBIZ-11452 > Project: OFBiz > Issue Type: Bug > Components: site >Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Major > Labels: license > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OFBIZ-11464) Improve the ProductDimension
Pierre Smits created OFBIZ-11464: Summary: Improve the ProductDimension Key: OFBIZ-11464 URL: https://issues.apache.org/jira/browse/OFBIZ-11464 Project: OFBiz Issue Type: Sub-task Components: bi Affects Versions: Trunk Reporter: Pierre Smits Assignee: Pierre Smits Improve the ProductDimension to have more attributes for filter and roll-up purposes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (OFBIZ-11309) Styles some clickable fields of backend tables as buttons
[ https://issues.apache.org/jira/browse/OFBIZ-11309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl closed OFBIZ-11309. - Fix Version/s: Upcoming Branch Resolution: Implemented Thanks [~uHeidfeld] , your work is committed. > Styles some clickable fields of backend tables as buttons > - > > Key: OFBIZ-11309 > URL: https://issues.apache.org/jira/browse/OFBIZ-11309 > Project: OFBiz > Issue Type: Improvement > Components: accounting, content, party, product >Affects Versions: Trunk >Reporter: Ulrich Heidfeld >Assignee: Michael Brohl >Priority: Minor > Fix For: Upcoming Branch > > Attachments: > OFBIZ-11309_Styles_some_clickable_fields_of_backend_tables_as_buttons.patch > > > In some tables of OFBiz backend are clickable fields that are not styled as > buttons. To improve UI, i would reccommend to style them as buttons. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11309) Styles some clickable fields of backend tables as buttons
[ https://issues.apache.org/jira/browse/OFBIZ-11309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061458#comment-17061458 ] ASF subversion and git services commented on OFBIZ-11309: - Commit e4e32a1a64739638ce7692a898d662b523bc2991 in ofbiz-framework's branch refs/heads/trunk from Michael Brohl [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=e4e32a1 ] Improved: Styles some clickable fields of backend tables as buttons. (OFBIZ-11309) Thanks Ulrich Heidfeld for reporting and providing the patch, James Yong for additional review. > Styles some clickable fields of backend tables as buttons > - > > Key: OFBIZ-11309 > URL: https://issues.apache.org/jira/browse/OFBIZ-11309 > Project: OFBiz > Issue Type: Improvement > Components: accounting, content, party, product >Affects Versions: Trunk >Reporter: Ulrich Heidfeld >Assignee: Michael Brohl >Priority: Minor > Attachments: > OFBIZ-11309_Styles_some_clickable_fields_of_backend_tables_as_buttons.patch > > > In some tables of OFBiz backend are clickable fields that are not styled as > buttons. To improve UI, i would reccommend to style them as buttons. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11310) JSON renderer for screen/menu/form
[ https://issues.apache.org/jira/browse/OFBIZ-11310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061457#comment-17061457 ] James Yong commented on OFBIZ-11310: Encountered compilation errors after I applied [^OFBIZ-11310.patch] and added vuejs-portal plugin from [https://gitlab.ofbizextra.org/ofbizextra/ofbizplugins/vuejsPortal] > JSON renderer for screen/menu/form > --- > > Key: OFBIZ-11310 > URL: https://issues.apache.org/jira/browse/OFBIZ-11310 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Olivier Heintz >Priority: Minor > Attachments: FrontJsFormRenderer.java, FrontJsMenuRenderer.java, > FrontJsOutput.java, FrontJsScreenRenderer.java, > FrontJsScreenViewHandler.java, FrontJsTreeRenderer.java, OFBIZ-11310.patch > > > In a POC approach for using a SPA framework for GUI in OFBiz, json renderer > have been developed. > This Jira could be used to do code review on these renderer. > Currently, these renderer are on a V0 situation, it's a work in process > situation. After mailing-list discussion with mathieu we decide to go to a > V0.1 by 2-3 tasks > * add some javadoc each time it's necessary or needed > * remove all comment code or explain the decision waiting to activate or > remove the code > * do checkstyle > On first step, code will be with only what is used in a use case (no code for > tag not currently manage). > Json renderer are part of vuejs-portal plugin, in ofbizextra gitlab > (https://gitlab.ofbizextra.org/ofbizextra/ofbizplugins/vuejsPortal), so > commit are done on it, and mailing-list with these commit [are > ofbizextra-com...@lists.sourceforge.net.|mailto:are%c2%a0ofbizextra-com...@lists.sourceforge.net.] > But we will publish an update on this Jira each week there are some > modifications on renderer files > This task will take some time because it will used to do a complete code > review, not only in renderer but in vuejs component too, and so complete > documentation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (OFBIZ-11309) Styles some clickable fields of backend tables as buttons
[ https://issues.apache.org/jira/browse/OFBIZ-11309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl reassigned OFBIZ-11309: - Assignee: Michael Brohl (was: Ulrich Heidfeld) > Styles some clickable fields of backend tables as buttons > - > > Key: OFBIZ-11309 > URL: https://issues.apache.org/jira/browse/OFBIZ-11309 > Project: OFBiz > Issue Type: Improvement > Components: accounting, content, party, product >Affects Versions: Trunk >Reporter: Ulrich Heidfeld >Assignee: Michael Brohl >Priority: Minor > Attachments: > OFBIZ-11309_Styles_some_clickable_fields_of_backend_tables_as_buttons.patch > > > In some tables of OFBiz backend are clickable fields that are not styled as > buttons. To improve UI, i would reccommend to style them as buttons. -- This message was sent by Atlassian Jira (v8.3.4#803005)
