[jira] [Updated] (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:all-tabpanel ] Pierre Smits updated OFBIZ-10953: - Attachment: (was: OFBIZ-10953-BI.patch) > 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] [Updated] (OFBIZ-11076) Have a service to load records in the project dimension
[ https://issues.apache.org/jira/browse/OFBIZ-11076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-11076: - Attachment: (was: OFBIZ-11076-ProjectDimService.diff) > Have a service to load records in the project dimension > --- > > Key: OFBIZ-11076 > URL: https://issues.apache.org/jira/browse/OFBIZ-11076 > 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: ProjectDimension, birt, dwh, initialisation, project, > service > > For dwh initialisation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11076) Have a service to load records in the project dimension
[ https://issues.apache.org/jira/browse/OFBIZ-11076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-11076: - Attachment: (was: OFBIZ-11076-ProjectDimService.diff) > Have a service to load records in the project dimension > --- > > Key: OFBIZ-11076 > URL: https://issues.apache.org/jira/browse/OFBIZ-11076 > 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: ProjectDimension, birt, dwh, initialisation, project, > service > > For dwh initialisation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-10997) Have an Employee dimension
[ https://issues.apache.org/jira/browse/OFBIZ-10997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-10997: - Attachment: (was: OFBIZ-10997-EmployeeDimension.patch) > Have an Employee dimension > -- > > Key: OFBIZ-10997 > URL: https://issues.apache.org/jira/browse/OFBIZ-10997 > 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: EmployeeDimension, birt, dimension, dwh, employee > > The component would benefit from an employee dimension for future fact tables > and star schema view entities. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11077) Have a service to load records in the pos terminal dimension
[ https://issues.apache.org/jira/browse/OFBIZ-11077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-11077: - Attachment: (was: OFBIZ-11077-PosTerminalDimService.diff) > Have a service to load records in the pos terminal dimension > > > Key: OFBIZ-11077 > URL: https://issues.apache.org/jira/browse/OFBIZ-11077 > 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: PosTerminalDimension, birt, dwh, initialisation, pos, > service > > For dwh initialisation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11073) Have a PoSTerminal Dimension
[ https://issues.apache.org/jira/browse/OFBIZ-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-11073: - Attachment: (was: OFBIZ-11073-PosDimension.patch) > Have a PoSTerminal Dimension > > > Key: OFBIZ-11073 > URL: https://issues.apache.org/jira/browse/OFBIZ-11073 > 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: PosTerminalDimension, birt, dimension, dwh > > The component would benefit from a PoS terminal dimension for future fact > tables and star schema view entities. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11073) Have a PoSTerminal Dimension
[ https://issues.apache.org/jira/browse/OFBIZ-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-11073: - Attachment: (was: OFBIZ-11073-PosDimension.patch) > Have a PoSTerminal Dimension > > > Key: OFBIZ-11073 > URL: https://issues.apache.org/jira/browse/OFBIZ-11073 > 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: PosTerminalDimension, birt, dimension, dwh > > The component would benefit from a PoS terminal dimension for future fact > tables and star schema view entities. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11077) Have a service to load records in the pos terminal dimension
[ https://issues.apache.org/jira/browse/OFBIZ-11077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-11077: - Attachment: (was: OFBIZ-11077-PosTerminalDimService.diff) > Have a service to load records in the pos terminal dimension > > > Key: OFBIZ-11077 > URL: https://issues.apache.org/jira/browse/OFBIZ-11077 > 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: PosTerminalDimension, birt, dwh, initialisation, pos, > service > > For dwh initialisation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-10996) Have a Supplier dimension
[ https://issues.apache.org/jira/browse/OFBIZ-10996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-10996: - Attachment: (was: OFBIZ-10996-SupplierDimension.patch) > 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] [Updated] (OFBIZ-10986) Have a Store Dimension
[ https://issues.apache.org/jira/browse/OFBIZ-10986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-10986: - Attachment: (was: OFBIZ-10986-StoreDimension.patch) > Have a Store Dimension > -- > > Key: OFBIZ-10986 > URL: https://issues.apache.org/jira/browse/OFBIZ-10986 > 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: StoreDimension, birt, dimension, dwh, store > > The component would benefit from a store dimension for future fact tables and > star schema view entities. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11034) Have a Carrier dimension
[ https://issues.apache.org/jira/browse/OFBIZ-11034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-11034: - Attachment: (was: OFBIZ-11034-CarrierDimension.patch) > Have a Carrier dimension > > > Key: OFBIZ-11034 > URL: https://issues.apache.org/jira/browse/OFBIZ-11034 > 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: CarrierDimension, birt, carrier, dimension, dwh > > The component would benefit from a Carrier dimension for future fact tables > and star schema view entities. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11055) Have a Project Dimension
[ https://issues.apache.org/jira/browse/OFBIZ-11055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-11055: - Attachment: (was: OFBIZ-11055-Project.patch) > Have a Project Dimension > > > Key: OFBIZ-11055 > URL: https://issues.apache.org/jira/browse/OFBIZ-11055 > 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: ProjectDimension, birt, dimension, dwh > > The component would benefit from a project dimension for future fact tables > and star schema view entities. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-10986) Have a Store Dimension
[ https://issues.apache.org/jira/browse/OFBIZ-10986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-10986: - Attachment: (was: OFBIZ-10986-StoreDimension.patch) > Have a Store Dimension > -- > > Key: OFBIZ-10986 > URL: https://issues.apache.org/jira/browse/OFBIZ-10986 > 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: StoreDimension, birt, dimension, dwh, store > > The component would benefit from a store dimension for future fact tables and > star schema view entities. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11083) Have an Account Dimension
[ https://issues.apache.org/jira/browse/OFBIZ-11083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-11083: - Attachment: (was: OFBIZ-11083-AccountDimension.diff) > Have an Account Dimension > - > > Key: OFBIZ-11083 > URL: https://issues.apache.org/jira/browse/OFBIZ-11083 > 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: AccountDimension, account, birt, dimension, dwh > > The component would benefit from an account dimension for future fact tables > and star schema view entities. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11075) Have a service to load records in the store dimension
[ https://issues.apache.org/jira/browse/OFBIZ-11075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-11075: - Attachment: (was: OFBIZ-11075-StoreDimService.diff) > Have a service to load records in the store dimension > - > > Key: OFBIZ-11075 > URL: https://issues.apache.org/jira/browse/OFBIZ-11075 > 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: StoreDimension, birt, dwh, initialisation, service, store > > For dwh initialisation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (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:all-tabpanel ] Pierre Smits updated OFBIZ-11081: - Attachment: (was: OFBIZ-11081-SupplierDimService.diff) > 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] [Updated] (OFBIZ-11086) Have a ProjectTask Dimension
[ https://issues.apache.org/jira/browse/OFBIZ-11086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-11086: - Attachment: (was: OFBIZ-11086-ProjectTaskDimension.diff) > Have a ProjectTask Dimension > > > Key: OFBIZ-11086 > URL: https://issues.apache.org/jira/browse/OFBIZ-11086 > 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: ProjectTaskDimension, birt, dimension, dwh > > The component would benefit from a project task dimension for future fact > tables and star schema view entities. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11085) Have a service to load records in the carrier dimension
[ https://issues.apache.org/jira/browse/OFBIZ-11085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-11085: - Attachment: (was: OFBIZ-11085-CarrierDimService.diff) > Have a service to load records in the carrier dimension > --- > > Key: OFBIZ-11085 > URL: https://issues.apache.org/jira/browse/OFBIZ-11085 > 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: CarrierDimension, birt, carrier, dimension, dwh, service > > for dwh initialisation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11084) Have a service to load records in the account dimension
[ https://issues.apache.org/jira/browse/OFBIZ-11084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-11084: - Attachment: (was: OFBIZ-11084-AccountDimService.diff) > Have a service to load records in the account dimension > --- > > Key: OFBIZ-11084 > URL: https://issues.apache.org/jira/browse/OFBIZ-11084 > 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: AccountDimension, account, birt, dimension, dwh, service > > for dwh initialisation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11085) Have a service to load records in the carrier dimension
[ https://issues.apache.org/jira/browse/OFBIZ-11085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-11085: - Attachment: (was: OFBIZ-11085-CarrierDimService.diff) > Have a service to load records in the carrier dimension > --- > > Key: OFBIZ-11085 > URL: https://issues.apache.org/jira/browse/OFBIZ-11085 > 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: CarrierDimension, birt, carrier, dimension, dwh, service > > for dwh initialisation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11088) Have a SalesPromo Dimension
[ https://issues.apache.org/jira/browse/OFBIZ-11088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-11088: - Attachment: (was: OFBIZ-11088-SalesPromoDimension.diff) > Have a SalesPromo Dimension > --- > > Key: OFBIZ-11088 > URL: https://issues.apache.org/jira/browse/OFBIZ-11088 > 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: SalesPromoDimension, birt, dimension, dwh > > The component would benefit from a project task dimension for future fact > tables and star schema view entities. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11087) Have a service to load records in the project task dimension
[ https://issues.apache.org/jira/browse/OFBIZ-11087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-11087: - Attachment: (was: OFBIZ-11087-ProjectTaskDimService.diff) > Have a service to load records in the project task dimension > > > Key: OFBIZ-11087 > URL: https://issues.apache.org/jira/browse/OFBIZ-11087 > 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: ProjectTaskDimension, birt, dimension, dwh, service > > For dwh initialisation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11087) Have a service to load records in the project task dimension
[ https://issues.apache.org/jira/browse/OFBIZ-11087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-11087: - Attachment: (was: OFBIZ-11087-ProjectTaskDimService.diff) > Have a service to load records in the project task dimension > > > Key: OFBIZ-11087 > URL: https://issues.apache.org/jira/browse/OFBIZ-11087 > 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: ProjectTaskDimension, birt, dimension, dwh, service > > For dwh initialisation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11089) Have a service to load records in the sales promo dimension
[ https://issues.apache.org/jira/browse/OFBIZ-11089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-11089: - Attachment: (was: OFBIZ-11089-SalesPromoDimService.diff) > Have a service to load records in the sales promo dimension > --- > > Key: OFBIZ-11089 > URL: https://issues.apache.org/jira/browse/OFBIZ-11089 > 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: SalesPromoDimension, birt, dimension, dwh, service > > For dwh initialisation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11089) Have a service to load records in the sales promo dimension
[ https://issues.apache.org/jira/browse/OFBIZ-11089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-11089: - Attachment: (was: OFBIZ-11089-SalesPromoDimService.diff) > Have a service to load records in the sales promo dimension > --- > > Key: OFBIZ-11089 > URL: https://issues.apache.org/jira/browse/OFBIZ-11089 > 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: SalesPromoDimension, birt, dimension, dwh, service > > For dwh initialisation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11092) Have a service to load records in the asset dimension
[ https://issues.apache.org/jira/browse/OFBIZ-11092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-11092: - Attachment: (was: OFBIZ-11091-AssetDimService.diff) > Have a service to load records in the asset dimension > - > > Key: OFBIZ-11092 > URL: https://issues.apache.org/jira/browse/OFBIZ-11092 > 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: AssetDimension, asset, birt, dimension, dwh, service > > For dwh initialisation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11031) Improve SalesOrderItemFact table
[ https://issues.apache.org/jira/browse/OFBIZ-11031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-11031: - Description: Improve the SalesOrderFactTable to include additional dimensions, such as: * AccountDimension * CustomerDimension * OrganisationDimension * StoreDimension * SalesChannelDimension * SalesRepDimension Have the entity work with dateDimId as integer. was: Improve the SalesOrderFactTable to include additional dimensions, such as: * AccountDimension * CustomerDimension * OrganisationDimension * StoreDimension * SalesChannelDimension * SalesRepDimension > 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] [Updated] (OFBIZ-11082) Improve the SalesInvoiceItemFact regarding dimensions
[ https://issues.apache.org/jira/browse/OFBIZ-11082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-11082: - Description: Improve the SIIF to include various dimensions, e.g. * OrganisationDimension * CustomerDimension * etc Have it working with dateDimeId as integer. was: Improve the SIIF to include various dimensions, e.g. * OrganisationDimension * CustomerDimension * sales channel * etc > 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] [Updated] (OFBIZ-11438) Improve InventoryItemStarSchema
[ https://issues.apache.org/jira/browse/OFBIZ-11438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-11438: - Description: Improve the InventoryItemStarSchema to include additional dimensions, such as: * OrganisationDimension * FacilityDimension and work with integer based dimensionIds of the DateDimension was: Improve the InventoryItemSchema to include additional dimensions, such as: * OrganisationDimension * FacilityDimension > 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] [Created] (OFBIZ-11459) Improve the InventoryItemFact regarding dimensions
Pierre Smits created OFBIZ-11459: Summary: 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 Improve the SIIF to include various dimensions, e.g. FacilityDimension OrganisationDimension etc -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (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:all-tabpanel ] Pierre Smits updated OFBIZ-11072: - Attachment: (was: OFBIZ-11072-CustomerDimService.diff) > 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] [Updated] (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 ] Swapnil Shah updated OFBIZ-11457: - Affects Version/s: (was: 17.12.02) > 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 >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-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 ] Swapnil Shah updated OFBIZ-11457: - Description: *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. was: *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 running the whole MRP engine. *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
[jira] [Updated] (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 ] Swapnil Shah updated OFBIZ-11457: - Fix Version/s: Upcoming Branch > 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 >Affects Versions: 17.12.02 >Reporter: Swapnil Shah >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 running the whole MRP engine. > *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] [Commented] (OFBIZ-11438) Improve InventoryItemStarSchema
[ https://issues.apache.org/jira/browse/OFBIZ-11438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17059723#comment-17059723 ] Pierre Smits commented on OFBIZ-11438: -- Adding appropriate 'depends on' links > 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 InventoryItemSchema to include additional dimensions, such as: > * OrganisationDimension > * FacilityDimension -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (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:all-tabpanel ] Pierre Smits updated OFBIZ-11065: - Attachment: (was: OFBIZ-11065-FacilityService.patch) > 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] [Closed] (OFBIZ-4361) Any ecommerce user has the ability to reset anothers password (including admin) via "Forget Your Password"
[ https://issues.apache.org/jira/browse/OFBIZ-4361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-4361. -- Resolution: Fixed I close, if someone wants to backport to R17 just reopen... > Any ecommerce user has the ability to reset anothers password (including > admin) via "Forget Your Password" > -- > > Key: OFBIZ-4361 > URL: https://issues.apache.org/jira/browse/OFBIZ-4361 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Affects Versions: Release Branch 11.04, Release Branch 13.07, Release > Branch 14.12, Release Branch 15.12, Release Branch 16.11, Release Branch > 17.12, Trunk > Environment: Ubuntu and others >Reporter: mz4wheeler >Assignee: Jacques Le Roux >Priority: Major > Labels: security > Fix For: 18.12.01, Upcoming Branch > > Attachments: OFBIZ-4361.patch, OFBIZ-4361_OneScreen.patch, > OFBIZ-4361_ReworkPasswordLogic.patch, OFBIZ-4361_ReworkPasswordLogic.patch, > OFBIZ-4361_Token-Password-Registration.patch > > > Currently, any user (via ecommerce "Forget Your Password") has the ability to > reset another users password, including "admin" without permission. By > simply entering "admin" and clicking "Email Password", the following is > displayed. > The following occurred: > A new password has been created and sent to you. Please check your Email. > This now forces the user of the ERP to change their password. It is also > possible to generate a dictionary attack against ofbiz because there is no > capta code required. This is serious security risk. > This feature could be reduced to a certain sub-set of users, whose login name > is optionally in the format of an email address, and maybe require a capta > code to prevent dictionary attacks. > For example, limit the feature to role "Customer" of type "Person" which was > generated via an ecommerce transaction. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11244) Remove the user login security question
[ https://issues.apache.org/jira/browse/OFBIZ-11244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17059654#comment-17059654 ] Jacques Le Roux commented on OFBIZ-11244: - Thanks Guys! > Remove the user login security question > --- > > Key: OFBIZ-11244 > URL: https://issues.apache.org/jira/browse/OFBIZ-11244 > Project: OFBiz > Issue Type: Improvement > Components: ecommerce, framework, party >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Michael Brohl >Priority: Major > Fix For: Upcoming Branch > > Attachments: OFBIZ-11244-framework.patch, OFBIZ-11244-plugins.patch > > > After our discussion in dev ML at > https://markmail.org/message/2dhc4al4adwgvl7z we will remove this feature. > This [~paulfoxworthy]'s remark is notably important: > bq. Security is only as good as its weakest link ( > https://www.schneier.com/essays/archives/2005/02/the_curse_of_the_sec.html) , > and security questions can be a real weakness. Any organisation using OFBiz > that really hates passwords could look at security keys from Yubico or the > like. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (OFBIZ-10587) _WARNING_MESSAGE_
[ https://issues.apache.org/jira/browse/OFBIZ-10587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl closed OFBIZ-10587. - Fix Version/s: Upcoming Branch Resolution: Implemented Thanks [~Dennis Balkir] , this is now commited in commit 2895da2220fabc81c9bcf8e0436486288e398b6f > _WARNING_MESSAGE_ > - > > Key: OFBIZ-10587 > URL: https://issues.apache.org/jira/browse/OFBIZ-10587 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Niklas Fallik >Assignee: Michael Brohl >Priority: Major > Fix For: Upcoming Branch > > Time Spent: 20m > Remaining Estimate: 0h > > Hi there, > I am looking for a way to display warning messages. We are using > EVENT_MESSAGE and ERROR_MESSAGE which we can pass to the frontend to display > to the user, but it turned out that it would be nice to have a type for > warnings like WARNING_MESSAGE. > I figured out that the java classes ServiceEventHandler and > ScriptEventHandler deal with those message types. > I really would appreciate if anyone already had a solution for this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-10587) _WARNING_MESSAGE_
[ https://issues.apache.org/jira/browse/OFBIZ-10587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl updated OFBIZ-10587: -- Issue Type: Improvement (was: Wish) > _WARNING_MESSAGE_ > - > > Key: OFBIZ-10587 > URL: https://issues.apache.org/jira/browse/OFBIZ-10587 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Reporter: Niklas Fallik >Assignee: Michael Brohl >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Hi there, > I am looking for a way to display warning messages. We are using > EVENT_MESSAGE and ERROR_MESSAGE which we can pass to the frontend to display > to the user, but it turned out that it would be nice to have a type for > warnings like WARNING_MESSAGE. > I figured out that the java classes ServiceEventHandler and > ScriptEventHandler deal with those message types. > I really would appreciate if anyone already had a solution for this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-10587) _WARNING_MESSAGE_
[ https://issues.apache.org/jira/browse/OFBIZ-10587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brohl updated OFBIZ-10587: -- Affects Version/s: Trunk > _WARNING_MESSAGE_ > - > > Key: OFBIZ-10587 > URL: https://issues.apache.org/jira/browse/OFBIZ-10587 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Niklas Fallik >Assignee: Michael Brohl >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Hi there, > I am looking for a way to display warning messages. We are using > EVENT_MESSAGE and ERROR_MESSAGE which we can pass to the frontend to display > to the user, but it turned out that it would be nice to have a type for > warnings like WARNING_MESSAGE. > I figured out that the java classes ServiceEventHandler and > ScriptEventHandler deal with those message types. > I really would appreciate if anyone already had a solution for this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11458) Alignment of style.css across themes regarding 'alignment properties'.
[ https://issues.apache.org/jira/browse/OFBIZ-11458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-11458: - Description: Simplifying the code base regarding css style properties applied. (was: Currently the 'align-text' is used in several places in the widgets of various components, and is defined to display the object having this to show in a right aligned manner. In order to simplify this (remove unclarity), it is better to use 'align-right'.) > Alignment of style.css across themes regarding 'alignment properties'. > -- > > Key: OFBIZ-11458 > URL: https://issues.apache.org/jira/browse/OFBIZ-11458 > Project: OFBiz > Issue Type: Sub-task > Components: themes >Affects Versions: Trunk >Reporter: Pierre Smits >Priority: Major > Labels: refactoring > Time Spent: 10m > Remaining Estimate: 0h > > Simplifying the code base regarding css style properties applied. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (OFBIZ-11458) Alignment of style.css across themes regarding 'alignment properties'.
[ https://issues.apache.org/jira/browse/OFBIZ-11458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-11458: Assignee: (was: Pierre Smits) > Alignment of style.css across themes regarding 'alignment properties'. > -- > > Key: OFBIZ-11458 > URL: https://issues.apache.org/jira/browse/OFBIZ-11458 > Project: OFBiz > Issue Type: Sub-task > Components: themes >Affects Versions: Trunk >Reporter: Pierre Smits >Priority: Major > Labels: refactoring > Time Spent: 10m > Remaining Estimate: 0h > > Currently the 'align-text' is used in several places in the widgets of > various components, and is defined to display the object having this to show > in a right aligned manner. > In order to simplify this (remove unclarity), it is better to use > 'align-right'. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11458) Alignment of style.css across themes regarding 'alignment properties'.
[ https://issues.apache.org/jira/browse/OFBIZ-11458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-11458: - Component/s: (was: product) (was: order) (was: bi) (was: accounting) > Alignment of style.css across themes regarding 'alignment properties'. > -- > > Key: OFBIZ-11458 > URL: https://issues.apache.org/jira/browse/OFBIZ-11458 > Project: OFBiz > Issue Type: Sub-task > Components: themes >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: refactoring > Time Spent: 10m > Remaining Estimate: 0h > > Currently the 'align-text' is used in several places in the widgets of > various components, and is defined to display the object having this to show > in a right aligned manner. > In order to simplify this (remove unclarity), it is better to use > 'align-right'. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11458) Alignment of style.css across themes regarding 'alignment properties'.
[ https://issues.apache.org/jira/browse/OFBIZ-11458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-11458: - Summary: Alignment of style.css across themes regarding 'alignment properties'. (was: Move from "align-text" to "align-right") > Alignment of style.css across themes regarding 'alignment properties'. > -- > > Key: OFBIZ-11458 > URL: https://issues.apache.org/jira/browse/OFBIZ-11458 > Project: OFBiz > Issue Type: Sub-task > Components: accounting, bi, order, product, themes >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: refactoring > Time Spent: 10m > Remaining Estimate: 0h > > Currently the 'align-text' is used in several places in the widgets of > various components, and is defined to display the object having this to show > in a right aligned manner. > In order to simplify this (remove unclarity), it is better to use > 'align-right'. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OFBIZ-11458) Move from "align-text" to "align-right"
Pierre Smits created OFBIZ-11458: Summary: Move from "align-text" to "align-right" Key: OFBIZ-11458 URL: https://issues.apache.org/jira/browse/OFBIZ-11458 Project: OFBiz Issue Type: Sub-task Components: accounting, bi, order, product, themes Affects Versions: Trunk Reporter: Pierre Smits Assignee: Pierre Smits Currently the 'align-text' is used in several places in the widgets of various components, and is defined to display the object having this to show in a right aligned manner. In order to simplify this (remove unclarity), it is better to use 'align-right'. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-5040) Backend widget & application HTML clean-up
[ https://issues.apache.org/jira/browse/OFBIZ-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-5040: Labels: css ftl html webapp widget widgetrendering (was: css html webapp widget widgetrendering) > Backend widget & application HTML clean-up > -- > > Key: OFBIZ-5040 > URL: https://issues.apache.org/jira/browse/OFBIZ-5040 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Reporter: Paul Piper >Priority: Major > Labels: css, ftl, html, webapp, widget, widgetrendering > > I am sure that this is a common thing to know: the current backoffice > application relies heavily on widgets. This is good, but the current > standard-html-structure is not flexible enough and often lacks proper w3c > implementation. > To make matters worse, you can often find applications avoiding widgets at > all and rather overriding the standards with custom ftl implementations. It > is these customizations that break the html on numerous screens and make it > difficult, if not tedious to create new themes for the backoffice. > This task is hence to: > * Find a consensus on a new widget standard > * Go over each of the application ftls and convert these to the new standard > * Recreate the themes and simplify/clean-up special rules > Since redoing the theme is a rather large task, we should consider to add an > additional css for now which stylises the replacement html instead of working > with the old. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-5040) Backend widget & application HTML clean-up
[ https://issues.apache.org/jira/browse/OFBIZ-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-5040: Labels: css html webapp widget widgetrendering (was: html webapp widget widgetrendering) > Backend widget & application HTML clean-up > -- > > Key: OFBIZ-5040 > URL: https://issues.apache.org/jira/browse/OFBIZ-5040 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Reporter: Paul Piper >Priority: Major > Labels: css, html, webapp, widget, widgetrendering > > I am sure that this is a common thing to know: the current backoffice > application relies heavily on widgets. This is good, but the current > standard-html-structure is not flexible enough and often lacks proper w3c > implementation. > To make matters worse, you can often find applications avoiding widgets at > all and rather overriding the standards with custom ftl implementations. It > is these customizations that break the html on numerous screens and make it > difficult, if not tedious to create new themes for the backoffice. > This task is hence to: > * Find a consensus on a new widget standard > * Go over each of the application ftls and convert these to the new standard > * Recreate the themes and simplify/clean-up special rules > Since redoing the theme is a rather large task, we should consider to add an > additional css for now which stylises the replacement html instead of working > with the old. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OFBIZ-11457) Expected arrival of Incoming Shipment needs to be reflected over back-order
Swapnil Shah created OFBIZ-11457: Summary: 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 Affects Versions: 17.12.02 Reporter: Swapnil Shah *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 running the whole MRP engine. *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)
