[jira] [Assigned] (OFBIZ-7207) Refactor XML shared dependencies between accounting and order
[ https://issues.apache.org/jira/browse/OFBIZ-7207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pranay Pandey reassigned OFBIZ-7207: Assignee: (was: Pranay Pandey) > Refactor XML shared dependencies between accounting and order > - > > Key: OFBIZ-7207 > URL: https://issues.apache.org/jira/browse/OFBIZ-7207 > Project: OFBiz > Issue Type: Improvement > Components: accounting, order >Affects Versions: Trunk >Reporter: Pranay Pandey >Priority: Major > > Many shared dependencies exist bi-directionally between accounting and order > including screens, entities and other items. All such XML should propagate > down to the commonext component. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-9320) User should be notified with success message on subscribing newsletter from ecommerce
[ https://issues.apache.org/jira/browse/OFBIZ-9320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pranay Pandey reassigned OFBIZ-9320: Assignee: Aditya Sharma (was: Pranay Pandey) > User should be notified with success message on subscribing newsletter from > ecommerce > - > > Key: OFBIZ-9320 > URL: https://issues.apache.org/jira/browse/OFBIZ-9320 > Project: OFBiz > Issue Type: Sub-task > Components: ecommerce >Reporter: Aditya Sharma >Assignee: Aditya Sharma >Priority: Minor > Attachments: OFBIZ-9320.patch > > > Steps to regenerate: > 1. Go to Ecommerce component (https://localhost:8443/ecommerce/control/main) > 2. In Sign Up For Contact List section from the left panel, select > contactList for Newsletter. > 3. Fill out email and Click on subscribe button. > There is no success message displayed to end user stating success of the > action. > At Service level, success message should also be there in the result. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-7711) Label not showing properly on 'Add EFT Account' screen of scrum
[ https://issues.apache.org/jira/browse/OFBIZ-7711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pranay Pandey reassigned OFBIZ-7711: Assignee: (was: Pranay Pandey) > Label not showing properly on 'Add EFT Account' screen of scrum > --- > > Key: OFBIZ-7711 > URL: https://issues.apache.org/jira/browse/OFBIZ-7711 > Project: OFBiz > Issue Type: Improvement > Components: scrum >Affects Versions: Trunk >Reporter: Chandan Khandelwal >Priority: Trivial > Attachments: OFBIZ-7711-Add-New-Check-Account.png, > OFBIZ-7711-Add-New-Credit-Card.png, > OFBIZ-7711-Add-New-EFT-Account-Scrum-Profile-View.png, > OFBIZ-7711-Payment-Method-Block-Scrum-Profile-View.png, OFBIZ-7711.patch > > > Accounting Uilabel resource not added in scrum main decorator. > URL : > https://localhost:8443/scrum/control/editeftaccount?partyId=DemoScrumCompany -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-7150) Character encoding issue on field Question in Survey Questions List
[ https://issues.apache.org/jira/browse/OFBIZ-7150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pranay Pandey reassigned OFBIZ-7150: Assignee: (was: Pranay Pandey) > Character encoding issue on field Question in Survey Questions List > --- > > Key: OFBIZ-7150 > URL: https://issues.apache.org/jira/browse/OFBIZ-7150 > Project: OFBiz > Issue Type: Bug > Components: content >Affects Versions: Release Branch 14.12, Trunk, Release Branch 15.12 >Reporter: Pranay Pandey >Priority: Minor > Attachments: Image 005.png, OFBIZ-7150-Screenshot.png, > OFBIZ-7150.patch > > > Character encoding issue found on field Question in Survey Questions List. > Please refer attached screenshot for the same. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-9596) Documentation: Business Process Reference Book
[ https://issues.apache.org/jira/browse/OFBIZ-9596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pranay Pandey reassigned OFBIZ-9596: Assignee: (was: Pranay Pandey) > Documentation: Business Process Reference Book > -- > > Key: OFBIZ-9596 > URL: https://issues.apache.org/jira/browse/OFBIZ-9596 > Project: OFBiz > Issue Type: Task >Reporter: Pranay Pandey >Priority: Major > Labels: BPRB, OBPRB, book, business, documentation, ofbiz, > process, reference > > All the documentation to be done for latest Release 16.11. > Rename and restructure the documentation on OFBiz Wiki page- [Business > Process Stories and Use Cases > Library|https://cwiki.apache.org/confluence/x/1gm8Ag]. > The idea will still be the same i.e. to help OFBiz Evaluators. All the people > who are more interested in written content to prove the implementation. > Provide a robust process documentation that supports decision-makers to > choose OFBiz over any other proprietary software. To help them take this > content to a wider audience who take the decision for choosing a business > automation software. > Parent page will be renamed as: "OFBiz Business Process Reference Book". > Then review and overhaul the overall content on this page to clarify the > purpose of all the documents in this tree(Directory). > Now restructure the child pages with new names with business significance > i.e. the process names that industry people refer e.g. CRM, Product > Information Management(PIM), Procurement, Fulfilment etc. > Now every module page will have two child pages so the structure would be > changed like this- > - Catalog Management > -- Product Information Management (PIM) > --- PIM Process Overview (Content: Process Overview, Business Purpose, > Level-1,2, and 3 Activity Diagrams as applicable to demonstrate the process > flow) > --- PIM User Stories, Use Cases and Test Cases (Content: Review, refine and > add missing user stories, use cases, and test cases) > -- Merchandising > --- Merchandising Process Overview (Content: Process Overview, Business > Purpose, Level-1,2, and 3 Activity Diagrams as applicable to demonstrate the > process flow) > --- Merchandising User Stories, Use Cases and Test Cases > -- Store Management > --- Store Management Process Overview > --- Store Management User Stories, Use Cases and Test Cases > ... > ... > ... > To maintain consistency for all the process diagrams, let's use Draw.io, this > plugin is now enabled for OFBiz Confluence. The user manual for the same is > available > [here|https://support.draw.io/display/DO/Draw.io+Online+User+Manual]. > A new child ticket should be added here for every document that's being > created or being refactored under this > [document|https://cwiki.apache.org/confluence/x/1gm8Ag]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-8459) InventoryItemStatus is not updated to INV_PROMISED status while creating sales order for serialized product
[ https://issues.apache.org/jira/browse/OFBIZ-8459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pranay Pandey reassigned OFBIZ-8459: Assignee: (was: Pranay Pandey) > InventoryItemStatus is not updated to INV_PROMISED status while creating > sales order for serialized product > --- > > Key: OFBIZ-8459 > URL: https://issues.apache.org/jira/browse/OFBIZ-8459 > Project: OFBiz > Issue Type: Bug > Components: product >Affects Versions: Release Branch 14.12, Trunk, Release Branch 15.12 >Reporter: Vaibhav Jain >Priority: Major > Attachments: OFBIZ-8459.patch, OFBIZ-8459.patch > > > Steps to regenerate the issue: > # Create a serialized product and receive single inventory item (feed serial > number) of the specific product. > # Check the status of the inventory item in InventoryItem and > InventoryItemStatus entities it should be INV_AVAILABLE. > # Create sales order of this serialized product. > # Status of the inventory item in InventoryItem entity is changed to > 'INV_PROMISED' but InventoryItemStatus entity still shows 'INV_AVAILABLE'. > Expected : > In InventoryItemStatus current status should also be 'INV_PROMISED' as of > InventoryItem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10959) Enable entity timestamp fields
[
https://issues.apache.org/jira/browse/OFBIZ-10959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827756#comment-16827756
]
Mathieu Lirzin commented on OFBIZ-10959:
Hello Pawan,
The "include-internal" name has no obvious semantics attached to it, so some
documentation explaining what it meant by "internal" and what is the effect of
setting the attribute to {{true}} would help alot. Documentation should ideally
be added in the {{xsd}} at the minimum.
Regarding the code you wrote, in the following snippet you can remove:
{code:java}
if ((modelField.getIsAutoCreatedInternal() &&
!autoFieldsEntity.includeInternal)) {
{code}
Thanks.
> Enable entity timestamp fields
> --
>
> Key: OFBIZ-10959
> URL: https://issues.apache.org/jira/browse/OFBIZ-10959
> Project: OFBiz
> Issue Type: Improvement
> Components: framework/webtools
>Affects Versions: Trunk
>Reporter: Pawan Verma
>Assignee: Suraj Khurana
>Priority: Minor
> Attachments: OFBIZ-10959.patch, OFBIZ-10959.patch
>
>
> MarkMail link for the discussion:
> [https://markmail.org/thread/x7paa3ulljns6awh]
>
> While working on a Production environment, I have found that for some reason
> entity timestamp fields are disabled at Search Results screen in Trunk and
> the previous release branch. It is available at View Value screen. It was
> enabled in Release 16.11.
>
> These fields are helpful for developers to get the idea about when the row in
> the entity is created/updated. Extremely helpful while working on the
> Production environment.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (OFBIZ-10959) Enable entity timestamp fields
[
https://issues.apache.org/jira/browse/OFBIZ-10959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827756#comment-16827756
]
Mathieu Lirzin edited comment on OFBIZ-10959 at 4/27/19 9:37 PM:
-
Hello Pawan,
The "include-internal" name has no obvious semantics attached to it, so some
documentation explaining what it meant by "internal" and what is the effect of
setting the attribute to {{true}} would help alot. Documentation should ideally
be added in the {{xsd}} at the minimum.
Regarding the code you wrote, in the following snippet you can remove the extra
parenthesis:
{code:java}
if ((modelField.getIsAutoCreatedInternal() &&
!autoFieldsEntity.includeInternal)) {
{code}
Thanks.
was (Author: mthl):
Hello Pawan,
The "include-internal" name has no obvious semantics attached to it, so some
documentation explaining what it meant by "internal" and what is the effect of
setting the attribute to {{true}} would help alot. Documentation should ideally
be added in the {{xsd}} at the minimum.
Regarding the code you wrote, in the following snippet you can remove:
{code:java}
if ((modelField.getIsAutoCreatedInternal() &&
!autoFieldsEntity.includeInternal)) {
{code}
Thanks.
> Enable entity timestamp fields
> --
>
> Key: OFBIZ-10959
> URL: https://issues.apache.org/jira/browse/OFBIZ-10959
> Project: OFBiz
> Issue Type: Improvement
> Components: framework/webtools
>Affects Versions: Trunk
>Reporter: Pawan Verma
>Assignee: Suraj Khurana
>Priority: Minor
> Attachments: OFBIZ-10959.patch, OFBIZ-10959.patch
>
>
> MarkMail link for the discussion:
> [https://markmail.org/thread/x7paa3ulljns6awh]
>
> While working on a Production environment, I have found that for some reason
> entity timestamp fields are disabled at Search Results screen in Trunk and
> the previous release branch. It is available at View Value screen. It was
> enabled in Release 16.11.
>
> These fields are helpful for developers to get the idea about when the row in
> the entity is created/updated. Extremely helpful while working on the
> Production environment.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (OFBIZ-7586) Error in Create Billing Account From HR
[ https://issues.apache.org/jira/browse/OFBIZ-7586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pranay Pandey reassigned OFBIZ-7586: Assignee: (was: Pranay Pandey) > Error in Create Billing Account From HR > --- > > Key: OFBIZ-7586 > URL: https://issues.apache.org/jira/browse/OFBIZ-7586 > Project: OFBiz > Issue Type: Sub-task > Components: humanres >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, > Release Branch 15.12 >Reporter: Chandan Khandelwal >Priority: Major > Attachments: OFBIZ-7586.patch > > > # Go To HR > # Select Comapny > # Create Billing Account > # Save > URL : > https://ofbiz-vm.apache.org:8443/humanres/control/EditBillingAccount?partyId=MARKETING > getting error "org.ofbiz.webapp.control.RequestHandlerException: Unknown > request [createBillingAccountAndRole]; this request does not exist or cannot > be called directly." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-7208) Refactor XML shared dependencies between accounting and HR
[ https://issues.apache.org/jira/browse/OFBIZ-7208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pranay Pandey reassigned OFBIZ-7208: Assignee: (was: Pranay Pandey) > Refactor XML shared dependencies between accounting and HR > -- > > Key: OFBIZ-7208 > URL: https://issues.apache.org/jira/browse/OFBIZ-7208 > Project: OFBiz > Issue Type: Improvement > Components: accounting, commonext, humanres >Reporter: Pranay Pandey >Priority: Major > > Many shared dependencies exist bi-directionally between accounting and HR > including screens, entities and other items. All such XML should propagate > down to the commonext component. > List of dependencies of HR on Accounting : > # UI Label > # Lookup > # Screens > # Requests > # Forms -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10992) No pre-filled value while selecting "facilityId To" on Transfer Inventory Item screen
[ https://issues.apache.org/jira/browse/OFBIZ-10992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aishwary Shrivastava updated OFBIZ-10992: - Flags: Patch > No pre-filled value while selecting "facilityId To" on Transfer Inventory > Item screen > - > > Key: OFBIZ-10992 > URL: https://issues.apache.org/jira/browse/OFBIZ-10992 > Project: OFBiz > Issue Type: Bug > Components: product >Affects Versions: Trunk >Reporter: Aishwary Shrivastava >Assignee: Swapnil M Mane >Priority: Minor > Attachments: NewFacility.png, OFBIZ-10992.patch, > TransferInventoryItem.png > > > While creating Transfer Inventory Item from warehouse, there are no prefiled > values in selecting FacilityId To. > Steps to regenerate: > # Go to Facilities. > # Select Inventory Xfers. > # Create Transfer Inventory Item From any Warehouse. > # Fill values in the feilds. > # Try to click on FacilityIdTo field > Attached the screenshots for creating new inventory item transfer screen and > new facility screen. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10992) No pre-filled value while selecting "facilityId To" on Transfer Inventory Item screen
[ https://issues.apache.org/jira/browse/OFBIZ-10992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil M Mane reassigned OFBIZ-10992: -- Assignee: Swapnil M Mane (was: Aishwary Shrivastava) > No pre-filled value while selecting "facilityId To" on Transfer Inventory > Item screen > - > > Key: OFBIZ-10992 > URL: https://issues.apache.org/jira/browse/OFBIZ-10992 > Project: OFBiz > Issue Type: Bug > Components: product >Affects Versions: Trunk >Reporter: Aishwary Shrivastava >Assignee: Swapnil M Mane >Priority: Minor > Attachments: NewFacility.png, OFBIZ-10992.patch, > TransferInventoryItem.png > > > While creating Transfer Inventory Item from warehouse, there are no prefiled > values in selecting FacilityId To. > Steps to regenerate: > # Go to Facilities. > # Select Inventory Xfers. > # Create Transfer Inventory Item From any Warehouse. > # Fill values in the feilds. > # Try to click on FacilityIdTo field > Attached the screenshots for creating new inventory item transfer screen and > new facility screen. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10992) No pre-filled value while selecting "facilityId To" on Transfer Inventory Item screen
[ https://issues.apache.org/jira/browse/OFBIZ-10992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827752#comment-16827752 ] Aishwary Shrivastava commented on OFBIZ-10992: -- Added patch for the fix, thanks [~pawan.verma] for the help. Changed parameter from "facilityIdTo" to "facilityId" in the form "CreateInventoryTransfer". > No pre-filled value while selecting "facilityId To" on Transfer Inventory > Item screen > - > > Key: OFBIZ-10992 > URL: https://issues.apache.org/jira/browse/OFBIZ-10992 > Project: OFBiz > Issue Type: Bug > Components: product >Affects Versions: Trunk >Reporter: Aishwary Shrivastava >Assignee: Aishwary Shrivastava >Priority: Minor > Attachments: NewFacility.png, OFBIZ-10992.patch, > TransferInventoryItem.png > > > While creating Transfer Inventory Item from warehouse, there are no prefiled > values in selecting FacilityId To. > Steps to regenerate: > # Go to Facilities. > # Select Inventory Xfers. > # Create Transfer Inventory Item From any Warehouse. > # Fill values in the feilds. > # Try to click on FacilityIdTo field > Attached the screenshots for creating new inventory item transfer screen and > new facility screen. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10992) No pre-filled value while selecting "facilityId To" on Transfer Inventory Item screen
[ https://issues.apache.org/jira/browse/OFBIZ-10992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aishwary Shrivastava updated OFBIZ-10992: - Attachment: OFBIZ-10992.patch > No pre-filled value while selecting "facilityId To" on Transfer Inventory > Item screen > - > > Key: OFBIZ-10992 > URL: https://issues.apache.org/jira/browse/OFBIZ-10992 > Project: OFBiz > Issue Type: Bug > Components: product >Affects Versions: Trunk >Reporter: Aishwary Shrivastava >Assignee: Aishwary Shrivastava >Priority: Minor > Attachments: NewFacility.png, OFBIZ-10992.patch, > TransferInventoryItem.png > > > While creating Transfer Inventory Item from warehouse, there are no prefiled > values in selecting FacilityId To. > Steps to regenerate: > # Go to Facilities. > # Select Inventory Xfers. > # Create Transfer Inventory Item From any Warehouse. > # Fill values in the feilds. > # Try to click on FacilityIdTo field > Attached the screenshots for creating new inventory item transfer screen and > new facility screen. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827750#comment-16827750
]
Rishi Solanki commented on OFBIZ-10966:
---
[~jayansh]
+1 for proposal and proposed design looks good to me. Still would like to
review when you submit the basic conversion service.
> JSON entity data import and export utility
> --
>
> Key: OFBIZ-10966
> URL: https://issues.apache.org/jira/browse/OFBIZ-10966
> Project: OFBiz
> Issue Type: New Feature
> Components: framework
>Reporter: Jayansh Shinde
>Priority: Minor
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (OFBIZ-10992) No pre-filled value while selecting "facilityId To" on Transfer Inventory Item screen
Aishwary Shrivastava created OFBIZ-10992: Summary: No pre-filled value while selecting "facilityId To" on Transfer Inventory Item screen Key: OFBIZ-10992 URL: https://issues.apache.org/jira/browse/OFBIZ-10992 Project: OFBiz Issue Type: Bug Components: product Affects Versions: Trunk Reporter: Aishwary Shrivastava Assignee: Aishwary Shrivastava Attachments: NewFacility.png, TransferInventoryItem.png While creating Transfer Inventory Item from warehouse, there are no prefiled values in selecting FacilityId To. Steps to regenerate: # Go to Facilities. # Select Inventory Xfers. # Create Transfer Inventory Item From any Warehouse. # Fill values in the feilds. # Try to click on FacilityIdTo field Attached the screenshots for creating new inventory item transfer screen and new facility screen. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10959) Enable entity timestamp fields
[ https://issues.apache.org/jira/browse/OFBIZ-10959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pawan Verma updated OFBIZ-10959: Attachment: OFBIZ-10959.patch > Enable entity timestamp fields > -- > > Key: OFBIZ-10959 > URL: https://issues.apache.org/jira/browse/OFBIZ-10959 > Project: OFBiz > Issue Type: Improvement > Components: framework/webtools >Affects Versions: Trunk >Reporter: Pawan Verma >Assignee: Suraj Khurana >Priority: Minor > Attachments: OFBIZ-10959.patch, OFBIZ-10959.patch > > > MarkMail link for the discussion: > [https://markmail.org/thread/x7paa3ulljns6awh] > > While working on a Production environment, I have found that for some reason > entity timestamp fields are disabled at Search Results screen in Trunk and > the previous release branch. It is available at View Value screen. It was > enabled in Release 16.11. > > These fields are helpful for developers to get the idea about when the row in > the entity is created/updated. Extremely helpful while working on the > Production environment. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10959) Enable entity timestamp fields
[ https://issues.apache.org/jira/browse/OFBIZ-10959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827749#comment-16827749 ] Pawan Verma commented on OFBIZ-10959: - Thanks [~gil portenseigne] for the review. I have modified the patch. Thanks! > Enable entity timestamp fields > -- > > Key: OFBIZ-10959 > URL: https://issues.apache.org/jira/browse/OFBIZ-10959 > Project: OFBiz > Issue Type: Improvement > Components: framework/webtools >Affects Versions: Trunk >Reporter: Pawan Verma >Assignee: Suraj Khurana >Priority: Minor > Attachments: OFBIZ-10959.patch, OFBIZ-10959.patch > > > MarkMail link for the discussion: > [https://markmail.org/thread/x7paa3ulljns6awh] > > While working on a Production environment, I have found that for some reason > entity timestamp fields are disabled at Search Results screen in Trunk and > the previous release branch. It is available at View Value screen. It was > enabled in Release 16.11. > > These fields are helpful for developers to get the idea about when the row in > the entity is created/updated. Extremely helpful while working on the > Production environment. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde updated OFBIZ-10966:
---
Comment: was deleted
(was: Reference [https://www.jsonschemavalidator.net/] for json validation
against json schema.
Tried data:
{"Party":
{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED"},
"Product": {"productId":"654321", "productName": "Round Hat"}}
)
> JSON entity data import and export utility
> --
>
> Key: OFBIZ-10966
> URL: https://issues.apache.org/jira/browse/OFBIZ-10966
> Project: OFBiz
> Issue Type: New Feature
> Components: framework
>Reporter: Jayansh Shinde
>Priority: Minor
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde updated OFBIZ-10966:
---
Description:
Currently, we support import/export entity data in XML format.
Nowadays JSON is widely used in industry, we can have support for JSON format
which looks quite similar to XML support.
Here is example of XML data and it's JSON version
{code:java}
{code}
{code:java}
{“Party”:
{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
{code}
*Design Proposal*
We can write *entityImportJson* and *entityImportDirJson* services for
importing JSON from screen and directory respectively.
And the *entityExportAllJson* service for exporting entity data in JSON.
*Import Design*
The import service will perform following operations:
1.) Validate the input JSON data (I am in process of exploring the way for
this)
2.) On successful validation, convert JSON to OFBiz's entity model
(GenericValue)
3.) The GenericValue will be inserted in database by some handler class for
e.g we can write JsonDataHandler, it will convert given JSON to
List, and finally write it to database (Similar pattern is used
in XML import).
*Export Design*
Based on existing XML pattern the writeXmlText method of GenericEntity class
write the exported data in XML format.
In the similar way, we can implement writeJsonText to export data in JSON
format.
Please free feel to share your thought.
was:
Currently, we support import/export entity data in XML format.
Nowadays JSON is widely used in industry, we can have support for JSON format
which looks quite similar to XML support.
Here is example of XML data and it's JSON version
{code:java}
{code}
will look like this in JSON format
{code:json}
{“Party”:
{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
{code}
Here is design proposal
We can write entityImportJson and entityImportDirJson services for importing
JSON from screen and directory respectively. And entityExportAllJson for
exporting entity data in XML.
*Import Design*
We may validate the JSON schema during upload (I am in process of exploring it)
The import service will read the JSON data, validate it, then convert it to
OFBiz's entity data model (GenericEntity) and finally commit to database using
some handler class.
Like, we can write JsonDataHandler, this convert given JSON data to
List and write it to database.
{code:java}
private void writeValues(List valuesToWrite) throws
GenericEntityException {
if (this.checkDataOnly) {
EntityDataAssert.checkValueList(valuesToWrite, delegator,
this.getMessageList());
} else {
delegator.storeAll(valuesToWrite, new
EntityStoreOptions(createDummyFks));
}
}
{code}
*Export Design*
> JSON entity data import and export utility
> --
>
> Key: OFBIZ-10966
> URL: https://issues.apache.org/jira/browse/OFBIZ-10966
> Project: OFBiz
> Issue Type: New Feature
> Components: framework
>Reporter: Jayansh Shinde
>Priority: Minor
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde updated OFBIZ-10966:
---
Comment: was deleted
(was: The import service will read the json data and validate it and then
convert same to ofbiz’s entity data(GenericEntity) and commit to database using
some handler class. e.g. JsonDataHandler convert given json data to
List and write it to DB. Similar to:
private void writeValues(List valuesToWrite) throws
GenericEntityException {
if (this.checkDataOnly) {
EntityDataAssert.checkValueList(valuesToWrite, delegator,
this.getMessageList());
} else {
delegator.storeAll(valuesToWrite, new
EntityStoreOptions(createDummyFks));
}
}
Export service may require new method
(org.apache.ofbiz.entity.GenericEntity#writeJsonText) similar to existing
org.apache.ofbiz.entity.GenericEntity#writeXmlText )
> JSON entity data import and export utility
> --
>
> Key: OFBIZ-10966
> URL: https://issues.apache.org/jira/browse/OFBIZ-10966
> Project: OFBiz
> Issue Type: New Feature
> Components: framework
>Reporter: Jayansh Shinde
>Priority: Minor
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde updated OFBIZ-10966:
---
Comment: was deleted
(was: Lets have a look at main services used during Xml data import:
entityImport[WebtoolsServices.java]
entityImportDir[WebtoolsServices.java]
parseEntityXmlFile[WebtoolsServices.java]
Above services are responsible for importing parsing and validating xml data
using SAX XML parser class org.apache.ofbiz.entity.util.EntitySaxReader
Similarly export is done by entityExportAll service.
org.apache.ofbiz.entity.GenericEntity#writeXmlText is ultimately responsible
for converting entity data to xml data.
Please refer service definition file for more
details:../framework/webtools/servicedef/services.xml)
> JSON entity data import and export utility
> --
>
> Key: OFBIZ-10966
> URL: https://issues.apache.org/jira/browse/OFBIZ-10966
> Project: OFBiz
> Issue Type: New Feature
> Components: framework
>Reporter: Jayansh Shinde
>Priority: Minor
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-10959) Enable entity timestamp fields
[
https://issues.apache.org/jira/browse/OFBIZ-10959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827735#comment-16827735
]
Gil Portenseigne commented on OFBIZ-10959:
--
Hello,
Please rather use primitive boolean :) instead of object Boolean in :
{code:java}
public final Boolean includeInternal;
{code}
+1 and Thanks
> Enable entity timestamp fields
> --
>
> Key: OFBIZ-10959
> URL: https://issues.apache.org/jira/browse/OFBIZ-10959
> Project: OFBiz
> Issue Type: Improvement
> Components: framework/webtools
>Affects Versions: Trunk
>Reporter: Pawan Verma
>Assignee: Suraj Khurana
>Priority: Minor
> Attachments: OFBIZ-10959.patch
>
>
> MarkMail link for the discussion:
> [https://markmail.org/thread/x7paa3ulljns6awh]
>
> While working on a Production environment, I have found that for some reason
> entity timestamp fields are disabled at Search Results screen in Trunk and
> the previous release branch. It is available at View Value screen. It was
> enabled in Release 16.11.
>
> These fields are helpful for developers to get the idea about when the row in
> the entity is created/updated. Extremely helpful while working on the
> Production environment.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde updated OFBIZ-10966:
---
Description:
Currently, we support import/export entity data in XML format.
Nowadays JSON is widely used in industry, we can have support for JSON format
which looks quite similar to XML support.
Here is example of XML data and it's JSON version
{code:java}
{code}
will look like this in JSON format
{code:json}
{“Party”:
{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
{code}
Here is design proposal
We can write entityImportJson and entityImportDirJson services for importing
JSON from screen and directory respectively. And entityExportAllJson for
exporting entity data in XML.
*Import Design*
We may validate the JSON schema during upload (I am in process of exploring it)
The import service will read the JSON data, validate it, then convert it to
OFBiz's entity data model (GenericEntity) and finally commit to database using
some handler class.
Like, we can write JsonDataHandler, this convert given JSON data to
List and write it to database.
{code:java}
private void writeValues(List valuesToWrite) throws
GenericEntityException {
if (this.checkDataOnly) {
EntityDataAssert.checkValueList(valuesToWrite, delegator,
this.getMessageList());
} else {
delegator.storeAll(valuesToWrite, new
EntityStoreOptions(createDummyFks));
}
}
{code}
*Export Design*
was:
*Entity data import/export in JSON format*
Currently, we have support to import/export entity data in XML format. We are
required to have support for JSON format which looks quite similar to XML
support. I am summarising how current data looks and how its done in current
system and proposing how it should be done.
Just an example the existing xml data may look like:
{color:#008080}<{color}{color:#3f7f7f}Party{color}
{color:#7f007f}partyId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"_{color}{color:#2a00ff}_123456_{color}{color:#2a00ff}_"_{color}
{color:#7f007f}partyTypeId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PERSON"_{color}
{color:#7f007f}statusId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PARTY_ENABLED"_{color}{color:#008080}/>{color}
same proposed JSON data will look like:
{color:#00}_{“Party”:
\{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}_{color}
{color:#00}*Proposal:*{color}
_Services can be *entityImportJson* and *entityImportDirJson* for importing
json from screen and directory respectively. And *entityExportAllJson* for
exporting entity data in JSON, similar to existing services for xml.
{color:#00}My suggestion that Json data must be validated via a json schema
during upload.{color}{color:#00}R{color}{color:#00}efer
{color}{color:#00}[https://json-schema.org/] {color}{color:#00}for more
information on json schema.{color}_
> JSON entity data import and export utility
> --
>
> Key: OFBIZ-10966
> URL: https://issues.apache.org/jira/browse/OFBIZ-10966
> Project: OFBiz
> Issue Type: New Feature
> Components: framework
>Reporter: Jayansh Shinde
>Priority: Minor
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON format
> which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> will look like this in JSON format
> {code:json}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
> Here is design proposal
> We can write entityImportJson and entityImportDirJson services for importing
> JSON from screen and directory respectively. And entityExportAllJson for
> exporting entity data in XML.
> *Import Design*
> We may validate the JSON schema during upload (I am in process of exploring
> it)
> The import service will read the JSON data, validate it, then convert it to
> OFBiz's entity data model (GenericEntity) and finally commit to database
> using some handler class.
> Like, we can write JsonDataHandler, this convert given JSON data to
> List and write it to database.
> {code:java}
> private void writeValues(List valuesToWrite) throws
> GenericEntityException {
> if (this.checkDataOnly) {
> EntityDataAssert.checkValueList(valuesToWrite, delegator,
> this.getMessageList());
> } else {
> delegator.storeAll(valuesToWrite, new
> EntityStoreOptions(createDummyFks));
> }
> }
> {code}
> *Export Design*
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde updated OFBIZ-10966:
---
Description:
*Entity data import/export in JSON format*
Currently, we have support to import/export entity data in XML format. We are
required to have support for JSON format which looks quite similar to XML
support. I am summarising how current data looks and how its done in current
system and proposing how it should be done.
Just an example the existing xml data may look like:
{color:#008080}<{color}{color:#3f7f7f}Party{color}
{color:#7f007f}partyId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"_{color}{color:#2a00ff}_123456_{color}{color:#2a00ff}_"_{color}
{color:#7f007f}partyTypeId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PERSON"_{color}
{color:#7f007f}statusId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PARTY_ENABLED"_{color}{color:#008080}/>{color}
same proposed JSON data will look like:
{color:#00}_{“Party”:
\{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}_{color}
{color:#00}*Proposal:*{color}
_Services can be *entityImportJson* and *entityImportDirJson* for importing
json from screen and directory respectively. And *entityExportAllJson* for
exporting entity data in JSON, similar to existing services for xml.
{color:#00}My suggestion that Json data must be validated via a json schema
during upload.{color}{color:#00}R{color}{color:#00}efer
{color}{color:#00}[https://json-schema.org/] {color}{color:#00}for more
information on json schema.{color}_
was:
*Entity data import/export in JSON format*
Currently, we have support to import/export entity data in XML format. We are
required to have support for JSON format which looks quite similar to XML
support. We are summarizing how current data looks and how its done in current
system and proposing how it should be done.
Just an example the existing xml data may look like:
{color:#008080}<{color}{color:#3f7f7f}Party{color}
{color:#7f007f}partyId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"_{color}{color:#2a00ff}_123456_{color}{color:#2a00ff}_"_{color}
{color:#7f007f}partyTypeId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PERSON"_{color}
{color:#7f007f}statusId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PARTY_ENABLED"_{color}{color:#008080}/>{color}
same proposed JSON data will look like:
{color:#00}_{“Party”:
\{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}_{color}
{color:#00}*Proposal:*{color}
_Services can be *entityImportJson* and *entityImportDirJson* for importing
json from screen and directory respectively. And *entityExportAllJson* for
exporting entity data in JSON, similar to existing services for xml.
{color:#00}My suggestion that Json data must be validated via a json schema
during upload.{color}{color:#00}R{color}{color:#00}efer
{color}{color:#00}[https://json-schema.org/] {color}{color:#00}for more
information on json schema.{color}_
> JSON entity data import and export utility
> --
>
> Key: OFBIZ-10966
> URL: https://issues.apache.org/jira/browse/OFBIZ-10966
> Project: OFBiz
> Issue Type: New Feature
> Components: framework
>Reporter: Jayansh Shinde
>Priority: Minor
>
> *Entity data import/export in JSON format*
>
> Currently, we have support to import/export entity data in XML format. We are
> required to have support for JSON format which looks quite similar to XML
> support. I am summarising how current data looks and how its done in current
> system and proposing how it should be done.
>
> Just an example the existing xml data may look like:
> {color:#008080}<{color}{color:#3f7f7f}Party{color}
> {color:#7f007f}partyId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"_{color}{color:#2a00ff}_123456_{color}{color:#2a00ff}_"_{color}
>
> {color:#7f007f}partyTypeId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PERSON"_{color}
>
> {color:#7f007f}statusId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PARTY_ENABLED"_{color}{color:#008080}/>{color}
> same proposed JSON data will look like:
>
> {color:#00}_{“Party”:
> \{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}_{color}
>
> {color:#00}*Proposal:*{color}
> _Services can be *entityImportJson* and *entityImportDirJson* for importing
> json from screen and directory respectively. And *entityExportAllJson* for
> exporting entity data in JSON, similar to existing services for xml.
> {color:#00}My suggestion that Json data must be validated via a json
> schema during upload.{color}{color:#00}R{color}{color:#00}efer
> {color}{color:#00}[https://json-schema.org/] {color}{color:#00}for
> more information on json
[jira] [Updated] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde updated OFBIZ-10966:
---
Description:
*Entity data import/export in JSON format*
Currently, we have support to import/export entity data in XML format. We are
required to have support for JSON format which looks quite similar to XML
support. We are summarizing how current data looks and how its done in current
system and proposing how it should be done.
Just an example the existing xml data may look like:
{color:#008080}<{color}{color:#3f7f7f}Party{color}
{color:#7f007f}partyId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"_{color}{color:#2a00ff}_123456_{color}{color:#2a00ff}_"_{color}
{color:#7f007f}partyTypeId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PERSON"_{color}
{color:#7f007f}statusId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PARTY_ENABLED"_{color}{color:#008080}/>{color}
same proposed JSON data will look like:
{color:#00}_{“Party”:
\{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}_{color}
{color:#00}*Proposal:*{color}
_Services can be *entityImportJson* and *entityImportDirJson* for importing
json from screen and directory respectively. And *entityExportAllJson* for
exporting entity data in JSON, similar to existing services for xml.
{color:#00}My suggestion that Json data must be validated via a json schema
during upload.{color}{color:#00}R{color}{color:#00}efer
{color}{color:#00}[https://json-schema.org/] {color}{color:#00}for more
information on json schema.{color}_
was:
*Entity data import/export in JSON format*
Currently, we have support to import/export entity data in XML format. We are
required to have support for JSON format which looks quite similar to XML
support. We are summarizing how current data looks and how its done in current
system and proposing how it should be done.
Just an example the existing xml data may look like:
{color:#008080}<{color}{color:#3f7f7f}Party{color}
{color:#7f007f}partyId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"_{color}{color:#2a00ff}_123456_{color}{color:#2a00ff}_"_{color}
{color:#7f007f}partyTypeId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PERSON"_{color}
{color:#7f007f}statusId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PARTY_ENABLED"_{color}{color:#008080}/>{color}
same proposed JSON data will look like:
{color:#00}_{“Party”:
\{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}_{color}
{color:#00}*Proposal:*{color}
_Services can be *entityImportJson* and *entityImportDirJson* for importing
json from screen and directory respectively. And *entityExportAllJson* for
exporting entity data in JSON, similar to existing services for xml.
{color:#00}Our suggestion that Json data must be validated via a json
schema during upload.{color}{color:#00}R{color}{color:#00}efer
{color}{color:#00}[https://json-schema.org/] {color}{color:#00}for more
information on json schema.{color}_
> JSON entity data import and export utility
> --
>
> Key: OFBIZ-10966
> URL: https://issues.apache.org/jira/browse/OFBIZ-10966
> Project: OFBiz
> Issue Type: New Feature
> Components: framework
>Reporter: Jayansh Shinde
>Priority: Minor
>
> *Entity data import/export in JSON format*
>
> Currently, we have support to import/export entity data in XML format. We are
> required to have support for JSON format which looks quite similar to XML
> support. We are summarizing how current data looks and how its done in
> current system and proposing how it should be done.
>
> Just an example the existing xml data may look like:
> {color:#008080}<{color}{color:#3f7f7f}Party{color}
> {color:#7f007f}partyId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"_{color}{color:#2a00ff}_123456_{color}{color:#2a00ff}_"_{color}
>
> {color:#7f007f}partyTypeId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PERSON"_{color}
>
> {color:#7f007f}statusId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PARTY_ENABLED"_{color}{color:#008080}/>{color}
> same proposed JSON data will look like:
>
> {color:#00}_{“Party”:
> \{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}_{color}
>
> {color:#00}*Proposal:*{color}
> _Services can be *entityImportJson* and *entityImportDirJson* for importing
> json from screen and directory respectively. And *entityExportAllJson* for
> exporting entity data in JSON, similar to existing services for xml.
> {color:#00}My suggestion that Json data must be validated via a json
> schema during upload.{color}{color:#00}R{color}{color:#00}efer
> {color}{color:#00}[https://json-schema.org/] {color}{color:#00}for
> more information on json
[jira] [Commented] (OFBIZ-10933) Insertion order of ‘LinkedHashMap’ is not preserved by ‘MapContext’
[
https://issues.apache.org/jira/browse/OFBIZ-10933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827727#comment-16827727
]
Mathieu Lirzin commented on OFBIZ-10933:
Hello Jacques,
I see this warnings when compiling with IcedTea 3.7 (jdk8), but not with
OpenJDK 11 neither with Eclipse compiler, which is why I overlooked them. I
suspect this is a false positive where {{@safevarargs}} and generics don't play
well together.
Since in that particular case no genericity required by the tests, we can
workaround the warning by removing the generic types. If you agree with the
strategy I will commit a fix.
Thanks.
> Insertion order of ‘LinkedHashMap’ is not preserved by ‘MapContext’
> ---
>
> Key: OFBIZ-10933
> URL: https://issues.apache.org/jira/browse/OFBIZ-10933
> Project: OFBiz
> Issue Type: Bug
> Components: framework
>Affects Versions: Release Branch 18.12
>Reporter: Mathieu Lirzin
>Assignee: Mathieu Lirzin
>Priority: Major
> Fix For: Trunk, Release Branch 18.12
>
> Attachments:
> OFBIZ-10933_0001-Improved-Add-UtilMisc-toMap-Supplier-Map-K-V-Object.patch,
> OFBIZ-10933_0002-Fixed-Ensure-that-MapContext-preserves-insertion-ord.patch
>
>
> Since revision 1837462, when pushing a ‘LinkedHashMap’ inside a ‘MapContext’,
> the iteration order of the ‘MapContext’ values is not corresponding to the
> insertion order of the embedded ‘LinkedHashMap’ which is important in the
> ‘ControllerConfig’ case where configuration elements are stored in
> ‘LinkedHashMap’ objects and the ‘include’ mechanism relies on ‘MapContext’.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-10904) Creating custom Time Period does not show in party time period
[ https://issues.apache.org/jira/browse/OFBIZ-10904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827726#comment-16827726 ] Pawan Verma commented on OFBIZ-10904: - Hey [~jacques.le.roux], I have created a new custom time period *10001(Test Period 27 Apr)* at [1] on stable demo. And it is not showing under [2] because field 'isClosed' is not set. On TimePeriods screen code is written to fetch Open and Closed Time Periods based on isClosed Y or N. Hope it is clear now. [1] [https://demo-stable.ofbiz.apache.org/accounting/control/EditCustomTimePeriod] [2] [https://demo-stable.ofbiz.apache.org/accounting/control/TimePeriods?organizationPartyId=Company] > Creating custom Time Period does not show in party time period > -- > > Key: OFBIZ-10904 > URL: https://issues.apache.org/jira/browse/OFBIZ-10904 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, > Release Branch 15.12, Release Branch 16.11, Release Branch 17.12, Release > Branch 18.12 >Reporter: Pierre Smits >Assignee: Pawan Verma >Priority: Major > Attachments: OFBIZ-10904.patch > > > When a new time period is added in screen [1] the result does not show up in > [2]. > [1] > [https://demo-stable.ofbiz.apache.org/accounting/control/EditCustomTimePeriod] > [2] > [https://demo-stable.ofbiz.apache.org/accounting/control/TimePeriods?organizationPartyId=Company] > This is due to the fact that the field 'isClosed' is not set. Appropriate > values are: Y or N. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10935) Do not use deprecated method in ‘DBCPConnectionFactory’
[ https://issues.apache.org/jira/browse/OFBIZ-10935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827712#comment-16827712 ] Jacques Le Roux commented on OFBIZ-10935: - Thanks Mathieu, Actually took me a moment to get it [when Jacopo made this proposition|https://markmail.org/message/v3yswhnusu4elta5] :D > Do not use deprecated method in ‘DBCPConnectionFactory’ > --- > > Key: OFBIZ-10935 > URL: https://issues.apache.org/jira/browse/OFBIZ-10935 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Mathieu Lirzin >Assignee: Mathieu Lirzin >Priority: Minor > Fix For: Upcoming Branch > > Attachments: > OFBIZ-10935_Do-not-use-deprecated-method-in-DBCPConnect.patch > > > ‘PoolableConnectionFactory#setAutoCommitOnReturn’ should be used instead of > ‘PoolableConnectionFactory#setEnableAutoCommitOnReturn’ from > ‘org.apache.commons.dbcp2’ package. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OFBIZ-9905) Use "Create" instead of "Create New" on the various screens of all components
[ https://issues.apache.org/jira/browse/OFBIZ-9905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-9905. -- Resolution: Done Fix Version/s: Upcoming Branch Thanks Sourabh, Your patch is in trunk at revision: 1858291 > Use "Create" instead of "Create New" on the various screens of all components > - > > Key: OFBIZ-9905 > URL: https://issues.apache.org/jira/browse/OFBIZ-9905 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk > Environment: > https://demo-trunk.ofbiz.apache.org/accounting/control/EditAgreement >Reporter: Aayush jain >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-9905.patch, OFBIZ-9905.patch, OFBIZ-9905.patch, > UI_label .png > > > Following issues found: > 1. Create Agreement opens an edit agreement window > 2. Able to Create Agreement without any detail (empty Agreement) > Steps: > 1. Open URL > https://demo-trunk.ofbiz.apache.org/accounting/control/FindAgreement > 2. Navigate to Agreement section > 3. Click on create Agreement > 4. Click submit button > Actual: Agreement id is generated for empty agreement and when create window > opens, it's redirection is wrong to edit window > Expected: Proper redirection should be there (create agreement) and if an > agreement is created without any details its of no use. > Note: Same Issue exist with following screens: > 1. Billing Account > 2. Tax Authority > 3. Agreement > 4. Fixed Asset > 5. Vendor > 6. WebSite > 7. Blog > 8. Employment > 9. Employee Position > 10.Performance Review > 11.Job Requisition > 12. Party Resume -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10935) Do not use deprecated method in ‘DBCPConnectionFactory’
[ https://issues.apache.org/jira/browse/OFBIZ-10935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827690#comment-16827690 ] Mathieu Lirzin commented on OFBIZ-10935: Hello Jacques, Sure I will follow that rather counter-intuitive convention. :-) > Do not use deprecated method in ‘DBCPConnectionFactory’ > --- > > Key: OFBIZ-10935 > URL: https://issues.apache.org/jira/browse/OFBIZ-10935 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Mathieu Lirzin >Assignee: Mathieu Lirzin >Priority: Minor > Fix For: Upcoming Branch > > Attachments: > OFBIZ-10935_Do-not-use-deprecated-method-in-DBCPConnect.patch > > > ‘PoolableConnectionFactory#setAutoCommitOnReturn’ should be used instead of > ‘PoolableConnectionFactory#setEnableAutoCommitOnReturn’ from > ‘org.apache.commons.dbcp2’ package. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10961) Shortkeys missing on WebPOS
[ https://issues.apache.org/jira/browse/OFBIZ-10961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827686#comment-16827686 ] Jacques Le Roux commented on OFBIZ-10961: - Thanks Suraj! > Shortkeys missing on WebPOS > --- > > Key: OFBIZ-10961 > URL: https://issues.apache.org/jira/browse/OFBIZ-10961 > Project: OFBiz > Issue Type: Bug > Components: webpos >Affects Versions: Trunk, Release Branch 18.12 >Reporter: Padmavati Rawat >Assignee: Suraj Khurana >Priority: Major > Fix For: 18.12.01 > > Attachments: OFBIZ-10961.patch, shortkeysmissing.png > > > Steps: > 1. Visit the demo-trunk.ofbiz.apache.org link. > 2. Login to the Web POS terminal. > 2. Check the Keyboard Shortcuts section. > Actual: > Keyboard short key options are missing on demo-trunk. > Expected: > Keyboard shortcuts should be visible on the Keyboard shortcut section. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10853) AutoDescription of promotion showing invalid text
[ https://issues.apache.org/jira/browse/OFBIZ-10853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-10853: Description: Steps to replicate 1. Navigate to [https://demo-trunk.ofbiz.apache.org/ecommerce/control/main] 2. Click on view all promotion in special offer section. 3. click on the detail of promotion. 4. Promotion detail will be shown. See the generated description. 5. [https://demo-trunk.ofbiz.apache.org/ecommerce/control/showPromotionDetails?productPromoId=9019] was: Steps to replicate 1. Navigate to https://demo-trunk.ofbiz.apache.org/ecommerce/control/main 2. Click on view all promotion in special offer section. 3. click on the detail of promotion. 4. Promotion detail will be shown. See the generated description. 5. [#https://demo-trunk.ofbiz.apache.org/ecommerce/control/showPromotionDetails?productPromoId=9019] > AutoDescription of promotion showing invalid text > - > > Key: OFBIZ-10853 > URL: https://issues.apache.org/jira/browse/OFBIZ-10853 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Upcoming Branch, Release Branch 18.12 >Reporter: Lalit Dashora >Assignee: Suraj Khurana >Priority: Major > Attachments: OFBIZ-10853-issue-in-promo-autoDescription.patch > > > Steps to replicate > 1. Navigate to [https://demo-trunk.ofbiz.apache.org/ecommerce/control/main] > 2. Click on view all promotion in special offer section. > 3. click on the detail of promotion. > 4. Promotion detail will be shown. See the generated description. > 5. > [https://demo-trunk.ofbiz.apache.org/ecommerce/control/showPromotionDetails?productPromoId=9019] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10949) Move display of page title in accounting screens to location above (action) menu(s)
[
https://issues.apache.org/jira/browse/OFBIZ-10949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827664#comment-16827664
]
Pierre Smits commented on OFBIZ-10949:
--
The duplication should not be happen, as the diff includes the removal from the
lower level.
{code:java}
- ${uiLabelMap[labelTitleProperty]} ${uiLabelMap.CommonFor}:
${currentOrganization.groupName} [${organizationPartyId}]
{code}
> Move display of page title in accounting screens to location above
> (action) menu(s)
> ---
>
> Key: OFBIZ-10949
> URL: https://issues.apache.org/jira/browse/OFBIZ-10949
> Project: OFBiz
> Issue Type: Bug
> Components: accounting
>Affects Versions: Trunk, Release Branch 16.11, Release Branch 17.12,
> Release Branch 18.12
>Reporter: Pierre Smits
>Assignee: Pierre Smits
>Priority: Major
> Labels: usability
> Attachments: Image 005.png, OFBIZ-10949-accounting.patch, Screen Shot
> 2019-04-27 at 11.15.55.png
>
>
> See [1] and [2] and other accounting party screens.
> Currently the page title of the screen(s) is shown below the (various)
> menu(s). In order to improve usability the title of the page should be shown
> the menu(s).
> # [https://demo-stable.ofbiz.apache.org/accounting/control/AdminMain]
> # https://demo-trunk.ofbiz.apache.org/accounting/control/AdminMain
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (OFBIZ-10961) Shortkeys missing on WebPOS
[ https://issues.apache.org/jira/browse/OFBIZ-10961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suraj Khurana closed OFBIZ-10961. - Thanks Padmavati Rawat for reporting the issue and Rohit Koushal for providing the patch. > Shortkeys missing on WebPOS > --- > > Key: OFBIZ-10961 > URL: https://issues.apache.org/jira/browse/OFBIZ-10961 > Project: OFBiz > Issue Type: Bug > Components: webpos >Affects Versions: Trunk, Release Branch 18.12 >Reporter: Padmavati Rawat >Assignee: Suraj Khurana >Priority: Major > Fix For: 18.12.01 > > Attachments: OFBIZ-10961.patch, shortkeysmissing.png > > > Steps: > 1. Visit the demo-trunk.ofbiz.apache.org link. > 2. Login to the Web POS terminal. > 2. Check the Keyboard Shortcuts section. > Actual: > Keyboard short key options are missing on demo-trunk. > Expected: > Keyboard shortcuts should be visible on the Keyboard shortcut section. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OFBIZ-10961) Shortkeys missing on WebPOS
[ https://issues.apache.org/jira/browse/OFBIZ-10961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suraj Khurana resolved OFBIZ-10961. --- Resolution: Fixed Fix Version/s: 18.12.01 This has been fixed on OFBiz plugins at: Trunk at rev #1858289 Release18.12 at rev#1858290 > Shortkeys missing on WebPOS > --- > > Key: OFBIZ-10961 > URL: https://issues.apache.org/jira/browse/OFBIZ-10961 > Project: OFBiz > Issue Type: Bug > Components: webpos >Affects Versions: Trunk, Release Branch 18.12 >Reporter: Padmavati Rawat >Assignee: Suraj Khurana >Priority: Major > Fix For: 18.12.01 > > Attachments: OFBIZ-10961.patch, shortkeysmissing.png > > > Steps: > 1. Visit the demo-trunk.ofbiz.apache.org link. > 2. Login to the Web POS terminal. > 2. Check the Keyboard Shortcuts section. > Actual: > Keyboard short key options are missing on demo-trunk. > Expected: > Keyboard shortcuts should be visible on the Keyboard shortcut section. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10949) Move display of page title in accounting screens to location above (action) menu(s)
[ https://issues.apache.org/jira/browse/OFBIZ-10949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827658#comment-16827658 ] Jacques Le Roux commented on OFBIZ-10949: - After applyhing your patch I get !Image 005.png! not sure what's better, notably the duplication > Move display of page title in accounting screens to location above > (action) menu(s) > --- > > Key: OFBIZ-10949 > URL: https://issues.apache.org/jira/browse/OFBIZ-10949 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk, Release Branch 16.11, Release Branch 17.12, > Release Branch 18.12 >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: usability > Attachments: Image 005.png, OFBIZ-10949-accounting.patch, Screen Shot > 2019-04-27 at 11.15.55.png > > > See [1] and [2] and other accounting party screens. > Currently the page title of the screen(s) is shown below the (various) > menu(s). In order to improve usability the title of the page should be shown > the menu(s). > # [https://demo-stable.ofbiz.apache.org/accounting/control/AdminMain] > # https://demo-trunk.ofbiz.apache.org/accounting/control/AdminMain -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10949) Move display of page title in accounting screens to location above (action) menu(s)
[ https://issues.apache.org/jira/browse/OFBIZ-10949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-10949: Attachment: Image 005.png > Move display of page title in accounting screens to location above > (action) menu(s) > --- > > Key: OFBIZ-10949 > URL: https://issues.apache.org/jira/browse/OFBIZ-10949 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk, Release Branch 16.11, Release Branch 17.12, > Release Branch 18.12 >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Labels: usability > Attachments: Image 005.png, OFBIZ-10949-accounting.patch, Screen Shot > 2019-04-27 at 11.15.55.png > > > See [1] and [2] and other accounting party screens. > Currently the page title of the screen(s) is shown below the (various) > menu(s). In order to improve usability the title of the page should be shown > the menu(s). > # [https://demo-stable.ofbiz.apache.org/accounting/control/AdminMain] > # https://demo-trunk.ofbiz.apache.org/accounting/control/AdminMain -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10985) UI issue on View Order page
[ https://issues.apache.org/jira/browse/OFBIZ-10985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-10985: Affects Version/s: Release Branch 18.12 Release Branch 17.12 Priority: Trivial (was: Minor) Issue Type: Improvement (was: Bug) Thank you Rashi and Garima, I just change the type and priority, this is not a bug but an improvement (most UI changes are) > UI issue on View Order page > --- > > Key: OFBIZ-10985 > URL: https://issues.apache.org/jira/browse/OFBIZ-10985 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk, Release Branch 16.11, Release Branch 17.12, > Release Branch 18.12 >Reporter: Rashi Dhagat >Assignee: Garima jain >Priority: Trivial > Attachments: ViewOrderPage.jpg > > > Steps to regenerate: > # Open URL [https://demo-trunk.ofbiz.apache.org/ordermgr/control/main] > # Click on any order in Approved status > Actual: > # In Contact Information section, admin (username) is a button > # "Send confirmation email" button in brackets > Expected: > # Username should not be a button > # The button should not be in brackets. > Please refer attachment for same. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10988) Have a ProductCategory Dimension
[ https://issues.apache.org/jira/browse/OFBIZ-10988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-10988: - Summary: Have a ProductCategory Dimension (was: Have a ProductProCategory Dimension) > Have a ProductCategory Dimension > > > Key: OFBIZ-10988 > URL: https://issues.apache.org/jira/browse/OFBIZ-10988 > Project: OFBiz > Issue Type: Improvement > Components: bi >Affects Versions: Trunk, Release Branch 17.12, Release Branch 18.12 >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > > The component would benefit from a product category dimension for future fact > tables and star schema view entities. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10991) Have a SalesChannel dimension
Pierre Smits created OFBIZ-10991: Summary: Have a SalesChannel dimension Key: OFBIZ-10991 URL: https://issues.apache.org/jira/browse/OFBIZ-10991 Project: OFBiz Issue Type: Improvement Components: bi Affects Versions: Trunk, Release Branch 17.12, Release Branch 18.12 Reporter: Pierre Smits Assignee: Pierre Smits The component would benefit from a sales channel dimension for future fact tables and star schema view entities -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10990) Improve the SalesInvoiceItemStarSchema
Pierre Smits created OFBIZ-10990: Summary: Improve the SalesInvoiceItemStarSchema Key: OFBIZ-10990 URL: https://issues.apache.org/jira/browse/OFBIZ-10990 Project: OFBiz Issue Type: Improvement Components: bi Affects Versions: Trunk, Release Branch 17.12, Release Branch 18.12 Reporter: Pierre Smits The star schema should be improved to include elements from: * Customer dimension * Country dimension * Store dimension * Catalog dimension * Channel dimension -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OFBIZ-10913) FindTask does not allow for all statuses possible to be selected
[ https://issues.apache.org/jira/browse/OFBIZ-10913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suraj Khurana closed OFBIZ-10913. - Thanks Pierre Smits for reporting, Deepak Dixit for comments/findings and Pawan Verma for providing the patch. > FindTask does not allow for all statuses possible to be selected > > > Key: OFBIZ-10913 > URL: https://issues.apache.org/jira/browse/OFBIZ-10913 > Project: OFBiz > Issue Type: Bug > Components: projectmgr >Affects Versions: Trunk, Release Branch 16.11, Release Branch 17.12, > Release Branch 18.12 >Reporter: Pierre Smits >Assignee: Suraj Khurana >Priority: Major > Fix For: 17.12.01, 16.11.06, 18.12.01 > > Attachments: OFBIZ-10913.patch > > > When searching for tasks in [1] the options available are: > * Cancelled > * Completed > * Created > * On hold > However, project task records can also exist with a different status than the > list above (e.g. In Progress). > At the moment it is not possible to do a search/find on tasks with other > statuses. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10365) Document design approaches for Inventory Transfer
[ https://issues.apache.org/jira/browse/OFBIZ-10365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pawan Verma updated OFBIZ-10365: Description: h2. Here is the link for the [discussion|https://markmail.org/message/7qrjhpuvkc3n6hk4]. h2. *Design Approach #1:* * Create Header entity *InventoryTransferHeader (ITH)* ** inventoryTransferId* ** statusId ** facilityId ** locationSeqId ** facilityIdTo ** locationSeqIdTo ** primaryShipmentId * Refactor existing *InventoryTransfer* entity to *InventoryTransferItem* so as to support item level details as follows: ** inventoryTransferId* ** invTransferItemSeqId* ** productId ** shipmentId ** shipmentItemSeqId ** quantity ** unitPrice * Create new entity *TransferItemInvRes* ** inventoryTransferId* ** invTransferItemSeqId* ** inventoryItemId* ** quantity ** quantityNotAvailable ** reserverEnumId ** createdDateTime ** reservedDateTime ** promisedDateTime ** priority Having *TransferItemInvRes* entity will help us to manage multiple Items under same InventoryTransfer and each InventoryTransferItem can be fulfilled via multiple Inventory items and/or multiple Shipments. *TransferItemInvRes* will trigger update in *InventoryItemDetail* * Create *TransferItemBilling* entity to support invoicing (if needed) ** inventoryTransferId* ** invTransferItemSeqId* ** invoiceId* ** invoiceItemSeqId* ** itemIssuanceId ** shipmentReceiptId ** quantity ** amount * Create *InventoryTransferContanctMech* entity to support InventoryTransfer Contact Mechanism ** inventoryTransferId* ** contactMechPurposeTypeId* ** contactMechId* * Create *RequirementInventoryTransfer* entity ** requirementId* ** inventoryTransferId* * Refactor existing *InventoryItemDetail* entity ** inventoryTransferId ** invTransferItemSeqId *Screenflow for Approach #1:* * Add a new *Find Transfer Requirements* screen. ** Transfer Requirements can be searched with following parameters: *** Requirement ID *** Status ID *** Shipment ID *** Origin Facility ID *** Destination Facility ID *** Product ID *** Description *** Requirement Start Date *** Required By Date * Option for creating Inventory Transfer for Un-approved requirements will be disabled. * User can select multiple Approved Transfer Requirements between any two given facilities to create Single Inventory Transfer between them. * When user hit ‘Create Inventory Transfer’ option new Inventory Transfers would be created by consolidating all products/items requirements between any two given locations. * Add a new *View Inventory Transfer* screen * ** After assigning InventoryItems user can Approve the Inventory Transfer. ** Upon Approval ATP would get reduced to the tune of assigned quantity from each inventory item. ** From here user can manually override the auto-assigned InventoryItems against each product. ** User can Add/Edit/Delete the Transfer Items. * Refactor the ‘Packing’ screen and allow to submit the Approved Inventory Transfer Id (aka OrderId). Only Approved Inventory Transfer will be available to pack. * Upon completion of packing reduce the QOH from assigned inventory items to the tune of packed quantity. * After completing packing, shipment will be created in shipped status and Inventory Transfer will be marked as 'SENT'. * Once received at destination location the ATP/QOH would be increased up to the transferred quantity per product and shipment will be marked as 'RECEIVED' and Inventory Transfer will be marked as 'COMPLETED'. *To Be Business Process for Approach #1:* *!InventoryTransferModelLevel1.png!* h2. *Design Approach #2:* * Alter *InventoryTransfer* entity as header entity as follows: ** Add primaryShipmentId ** Remove inventoryItemId * Add new entity *InventoryTransferItem* ** inventoryTransferId* ** invTransferItemSeqId* ** inventoryItemId ** shipmentId ** shipmentItemSeqId ** quantity ** unitPrice Having InventoryItem detail at InventoryTransferItem level will help us to manage multiple Items for same InventoryTransfer and each InventoryTransferItem can be fulfilled via multiple Inventory items and/or multiple Shipments. * Create TransferItemBilling entity to support tax invoice ** inventoryTransferId* ** invTransferItemSeqId* ** invoiceId* ** invoiceItemSeqId* ** itemIssuanceId ** shipmentReceiptId ** quantity ** amount * Create *InventoryTransferContanctMech* entity to support InventoryTransfer Contact Mechanism ** inventoryTransferId* ** contactMechPurposeTypeId* ** contactMechId* * Create *RequirementInventoryTransfer* entity ** requirementId* ** inventoryTransferId* * Refactor existing *InventoryItemDetail* entity ** inventoryTransferId ** invTransferItemSeqId *Screenflow for Approach #2:* * Add a new *Find Transfer Requirements* screen. ** Transfer Requirements can be searched with following
[jira] [Created] (OFBIZ-10989) Have a facility dimension
Pierre Smits created OFBIZ-10989: Summary: Have a facility dimension Key: OFBIZ-10989 URL: https://issues.apache.org/jira/browse/OFBIZ-10989 Project: OFBiz Issue Type: Improvement Components: bi Affects Versions: Trunk, Release Branch 17.12, Release Branch 18.12 Reporter: Pierre Smits Assignee: Pierre Smits The component would benefit from a facility dimension for future fact tables and star schema view entities. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10988) Have a ProductProCategory Dimension
Pierre Smits created OFBIZ-10988: Summary: Have a ProductProCategory Dimension Key: OFBIZ-10988 URL: https://issues.apache.org/jira/browse/OFBIZ-10988 Project: OFBiz Issue Type: Improvement Components: bi Affects Versions: Trunk, Release Branch 17.12, Release Branch 18.12 Reporter: Pierre Smits Assignee: Pierre Smits The component would benefit from a product category dimension for future fact tables and star schema view entities. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10987) Have a Catalog Dimension
Pierre Smits created OFBIZ-10987: Summary: Have a Catalog Dimension Key: OFBIZ-10987 URL: https://issues.apache.org/jira/browse/OFBIZ-10987 Project: OFBiz Issue Type: Improvement Components: bi Affects Versions: Trunk, Release Branch 17.12, Release Branch 18.12 Reporter: Pierre Smits Assignee: Pierre Smits The component would benefit from a catalog dimension for future fact tables and star schema view entities. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10986) Have a Store Dimension
Pierre Smits created OFBIZ-10986: Summary: Have a Store Dimension Key: OFBIZ-10986 URL: https://issues.apache.org/jira/browse/OFBIZ-10986 Project: OFBiz Issue Type: Improvement Components: bi Affects Versions: Trunk, Release Branch 17.12, Release Branch 18.12 Reporter: Pierre Smits Assignee: Pierre Smits The component would benefit from a store dimension for future fact tables and star schema view entities. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OFBIZ-9086) Unit test case for service - quickSendPayment
[ https://issues.apache.org/jira/browse/OFBIZ-9086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suraj Khurana closed OFBIZ-9086. Thanks Deepak Nigam for reporting the ticket and Anushi Gupta for providing the patch. > Unit test case for service - quickSendPayment > -- > > Key: OFBIZ-9086 > URL: https://issues.apache.org/jira/browse/OFBIZ-9086 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk >Reporter: Deepak Nigam >Assignee: Suraj Khurana >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-9086.patch, OFBIZ-9086.patch > > > Unit test case for service - quickSendPayment -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OFBIZ-9086) Unit test case for service - quickSendPayment
[ https://issues.apache.org/jira/browse/OFBIZ-9086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suraj Khurana resolved OFBIZ-9086. -- Resolution: Implemented Fix Version/s: Upcoming Branch This has been committed to trunk at rev #1858283 > Unit test case for service - quickSendPayment > -- > > Key: OFBIZ-9086 > URL: https://issues.apache.org/jira/browse/OFBIZ-9086 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk >Reporter: Deepak Nigam >Assignee: Suraj Khurana >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-9086.patch, OFBIZ-9086.patch > > > Unit test case for service - quickSendPayment -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10965) Error while checkout from WebPOS
[ https://issues.apache.org/jira/browse/OFBIZ-10965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil M Mane reassigned OFBIZ-10965: -- Assignee: Swapnil M Mane > Error while checkout from WebPOS > - > > Key: OFBIZ-10965 > URL: https://issues.apache.org/jira/browse/OFBIZ-10965 > Project: OFBiz > Issue Type: Bug > Components: webpos >Affects Versions: 17.12.01 >Reporter: Padmavati Rawat >Assignee: Swapnil M Mane >Priority: Major > Attachments: Errorwhilecheckout.png, OFBIZ-10965 > > > Steps: > 1. Login to the POS Terminal. > 2. Add item to the cart. > 3. Set payment by pay cash "F3 PAY CASH" > 4. click on checkout key "F8 CHECKOUT" > Actual: > System showing an error on the cart section while checkout. > Expected: > The order should be successfully placed. > Please refer screenshot: -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10356) Display of entities in text input field for Product Name
[
https://issues.apache.org/jira/browse/OFBIZ-10356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827622#comment-16827622
]
Swapnil M Mane commented on OFBIZ-10356:
Thank you [~rmallah], [~jacques.le.roux] and [~ankit.joshi] !
> Display of entities in text input field for Product Name
>
>
> Key: OFBIZ-10356
> URL: https://issues.apache.org/jira/browse/OFBIZ-10356
> Project: OFBiz
> Issue Type: Bug
> Components: product
>Reporter: Rajesh Kumar Mallah
>Assignee: Jacques Le Roux
>Priority: Minor
> Fix For: 17.12.01, 16.11.06, 18.12.01
>
> Attachments: OFBIZ-10356.patch
>
>
> In the url:
> https://demo-stable.ofbiz.apache.org/catalog/control/EditProductContent?productId=GZ-1006-1
> the "Product Name" under "Override Simple Fields" is unnecessarily
> expressed in entity format . The string displayed in product name
> field is:{code}"Open Gizmo LGPL" {code} it could have been a
> simple "Open Gizmo (LGPL)"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10365) Document design approaches for Inventory Transfer
[ https://issues.apache.org/jira/browse/OFBIZ-10365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pawan Verma updated OFBIZ-10365: Description: h2. Here is the link for the [discussion|https://markmail.org/message/7qrjhpuvkc3n6hk4]. h2. *Design Approach #1:* * Create Header entity *InventoryTransferHeader (ITH)* ** inventoryTransferId* ** statusId ** facilityId ** locationSeqId ** facilityIdTo ** locationSeqIdTo ** primaryShipmentId * Refactor existing *InventoryTransfer* entity to *InventoryTransferItem* so as to support item level details as follows: ** inventoryTransferId* ** invTransferItemSeqId* ** productId ** shipmentId ** shipmentItemSeqId ** quantity ** unitPrice * Create new entity *TransferItemInvRes* ** inventoryTransferId* ** invTransferItemSeqId* ** **inventoryItemId ** quantity ** quantityNotAvailable ** reserverEnumId ** createdDateTime ** reservedDateTime ** promisedDateTime ** priority Having *TransferItemInvRes* entity will help us to manage multiple Items under same InventoryTransfer and each InventoryTransferItem can be fulfilled via multiple Inventory items and/or multiple Shipments. *TransferItemInvRes* will trigger update in *InventoryItemDetail* * Create *TransferItemBilling* entity to support invoicing (if needed) ** inventoryTransferId* ** invTransferItemSeqId* ** invoiceId* ** invoiceItemSeqId* ** itemIssuanceId ** shipmentReceiptId ** quantity ** amount * Create *InventoryTransferContanctMech* entity to support InventoryTransfer Contact Mechanism ** inventoryTransferId* ** contactMechPurposeTypeId* ** contactMechId* * Create *RequirementInventoryTransfer* entity ** requirementId* ** inventoryTransferId* * Refactor existing *InventoryItemDetail* entity ** inventoryTransferId ** invTransferItemSeqId *Screenflow for Approach #1:* * Add a new *Find Transfer Requirements* screen. ** Transfer Requirements can be searched with following parameters: *** Requirement ID *** Status ID *** Shipment ID *** Origin Facility ID *** Destination Facility ID *** Product ID *** Description *** Requirement Start Date *** Required By Date * Option for creating Inventory Transfer for Un-approved requirements will be disabled. * User can select multiple Approved Transfer Requirements between any two given facilities to create Single Inventory Transfer between them. * When user hit ‘Create Inventory Transfer’ option new Inventory Transfers would be created by consolidating all products/items requirements between any two given locations. * Add a new *View Inventory Transfer* screen * ** After assigning InventoryItems user can Approve the Inventory Transfer. ** Upon Approval ATP would get reduced to the tune of assigned quantity from each inventory item. ** From here user can manually override the auto-assigned InventoryItems against each product. ** User can Add/Edit/Delete the Transfer Items. * Refactor the ‘Packing’ screen and allow to submit the Approved Inventory Transfer Id (aka OrderId). Only Approved Inventory Transfer will be available to pack. * Upon completion of packing reduce the QOH from assigned inventory items to the tune of packed quantity. * After completing packing, shipment will be created in shipped status and Inventory Transfer will be marked as 'SENT'. * Once received at destination location the ATP/QOH would be increased up to the transferred quantity per product and shipment will be marked as 'RECEIVED' and Inventory Transfer will be marked as 'COMPLETED'. *To Be Business Process for Approach #1:* *!InventoryTransferModelLevel1.png!* h2. *Design Approach #2:* * Alter *InventoryTransfer* entity as header entity as follows: ** Add primaryShipmentId ** Remove inventoryItemId * Add new entity *InventoryTransferItem* ** inventoryTransferId* ** invTransferItemSeqId* ** inventoryItemId ** shipmentId ** shipmentItemSeqId ** quantity ** unitPrice Having InventoryItem detail at InventoryTransferItem level will help us to manage multiple Items for same InventoryTransfer and each InventoryTransferItem can be fulfilled via multiple Inventory items and/or multiple Shipments. * Create TransferItemBilling entity to support tax invoice ** inventoryTransferId* ** invTransferItemSeqId* ** invoiceId* ** invoiceItemSeqId* ** itemIssuanceId ** shipmentReceiptId ** quantity ** amount * Create *InventoryTransferContanctMech* entity to support InventoryTransfer Contact Mechanism ** inventoryTransferId* ** contactMechPurposeTypeId* ** contactMechId* * Create *RequirementInventoryTransfer* entity ** requirementId* ** inventoryTransferId* * Refactor existing *InventoryItemDetail* entity ** inventoryTransferId ** invTransferItemSeqId *Screenflow for Approach #2:* * Add a new *Find Transfer Requirements* screen. ** Transfer Requirements can be searched with following
[jira] [Updated] (OFBIZ-10365) Document design approaches for Inventory Transfer
[ https://issues.apache.org/jira/browse/OFBIZ-10365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pawan Verma updated OFBIZ-10365: Description: h2. Here is the link for the [discussion|https://markmail.org/message/7qrjhpuvkc3n6hk4]. h2. *Design Approach #1:* * Create Header entity *InventoryTransferHeader (ITH)* ** inventoryTransferId* ** statusId ** facilityId ** locationSeqId ** facilityIdTo ** locationSeqIdTo ** primaryShipmentId * Refactor existing *InventoryTransfer* entity to *InventoryTransferItem* so as to support item level details as follows: ** inventoryTransferId* ** invTransferItemSeqId* ** productId ** shipmentId ** shipmentItemSeqId ** quantity ** unitPrice * Create new entity *TransferItemInvRes* ** inventoryTransferId* ** invTransferItemSeqId* ** **inventoryItemId ** quantity ** quantityNotAvailable ** reserverEnumId ** createdDateTime ** reservedDateTime ** promisedDateTime ** priority Having *TransferItemInvRes* entity will help us to manage multiple Items under same InventoryTransfer and each InventoryTransferItem can be fulfilled via multiple Inventory items and/or multiple Shipments. *TransferItemInvRes* will trigger update in *InventoryItemDetail* * Create *TransferItemBilling* entity to support invoicing (if needed) ** inventoryTransferId* ** invTransferItemSeqId* ** invoiceId* ** invoiceItemSeqId* ** itemIssuanceId ** shipmentReceiptId ** quantity ** amount * Create *InventoryTransferContanctMech* entity to support InventoryTransfer Contact Mechanism ** inventoryTransferId* ** contactMechPurposeTypeId* ** contactMechId* * Create *RequirementInventoryTransfer* entity ** requirementId* ** inventoryTransferId* * Refactor existing *InventoryItemDetail* entity ** inventoryTransferId ** invTransferItemSeqId *Screenflow for Approach #1:* * Add a new *Find Transfer Requirements* screen. ** Transfer Requirements can be searched with following parameters: *** Requirement ID *** Status ID *** Shipment ID *** Origin Facility ID *** Destination Facility ID *** Product ID *** Description *** Requirement Start Date *** Required By Date * Option for creating Inventory Transfer for Un-approved requirements will be disabled. * User can select multiple Approved Transfer Requirements between any two given facilities to create Single Inventory Transfer between them. * When user hit ‘Create Inventory Transfer’ option new Inventory Transfers would be created by consolidating all products/items requirements between any two given locations. * System would auto-assign the required quantity from existing inventoryItems based on FIFO. * Add a new *Items* screen for Inventory Transfer ** From here user can manually override the auto-assigned InventoryItems against each product. ** User can Add/Edit/Delete the Transfer Items. ** User can merge transfer requirement of Created status of same facilities as Inventory Transfer Item. * Add a new *View Inventory Transfer* screen * ** After assigning InventoryItems user can Approve the Inventory Transfer. ** Upon Approval ATP would get reduced to the tune of assigned quantity from each inventory item. * Refactor the ‘Packing’ screen and allow to submit the Approved Inventory Transfer Id (aka OrderId). Only Approved Inventory Transfer will be available to pack. * Upon completion of packing reduce the QOH from assigned inventory items to the tune of packed quantity. * After completing packing, shipment will be created in shipped status and Inventory Transfer will be marked as 'SENT'. * Once received at destination location the ATP/QOH would be increased up to the transferred quantity per product and shipment will be marked as 'RECEIVED' and Inventory Transfer will be marked as 'COMPLETED'. *To Be Business Process for Approach #1:* *!InventoryTransferModelLevel1.png!* h2. *Design Approach #2:* * Alter *InventoryTransfer* entity as header entity as follows: ** Add primaryShipmentId ** Remove inventoryItemId * Add new entity *InventoryTransferItem* ** inventoryTransferId* ** invTransferItemSeqId* ** inventoryItemId ** shipmentId ** shipmentItemSeqId ** quantity ** unitPrice Having InventoryItem detail at InventoryTransferItem level will help us to manage multiple Items for same InventoryTransfer and each InventoryTransferItem can be fulfilled via multiple Inventory items and/or multiple Shipments. * Create TransferItemBilling entity to support tax invoice ** inventoryTransferId* ** invTransferItemSeqId* ** invoiceId* ** invoiceItemSeqId* ** itemIssuanceId ** shipmentReceiptId ** quantity ** amount * Create *InventoryTransferContanctMech* entity to support InventoryTransfer Contact Mechanism ** inventoryTransferId* ** contactMechPurposeTypeId* ** contactMechId* * Create *RequirementInventoryTransfer* entity ** requirementId* **
[jira] [Commented] (OFBIZ-10974) Stock Watch List Report
[ https://issues.apache.org/jira/browse/OFBIZ-10974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827611#comment-16827611 ] Ratnesh Upadhyay commented on OFBIZ-10974: -- Thanks for your inputs [~pfm.smits]. No, we will not offer date filters it's always meant to return current stock/availability status against the listed products. To generate this report user has to select facility first. Currently this report is intended for merchandiser/sales manager/planners and if we move it to facility component then this set of role might not have the required permissions always. Thanks! > Stock Watch List Report > --- > > Key: OFBIZ-10974 > URL: https://issues.apache.org/jira/browse/OFBIZ-10974 > Project: OFBiz > Issue Type: New Feature > Components: product >Affects Versions: Trunk >Reporter: Ratnesh Upadhyay >Assignee: Ritesh Kumar >Priority: Major > > Add the Stock Watch List report to track the availability of items and > assortment. So that sales manager can keep a watch on current stock and sales > performance of all the product lines and can get their current inventory > status like Available, Low, Out of Stock and when the inbound shipment is > planned to receive. This information can help merchandiser to analyse > differentiation in fast moving and slow moving items. > Report should have following filters : > * User should be able to filter the report by availability status like > Available, Highly Available, Low, Out of Stock items. > * User should be able filter the products by category. > * User should be able to choose all or any of these filters to generate the > report. > Report Matrix should be- > lets say we have to product X in category Y in system that have multiple > variants like product-X has following size variants XS, S, M, L, XL in RED > colour.. And it also have same size variants in BLUE colour..then resultant > report should be like this.. > ||Product Name||XXS||XS||S||M||L||XL|| > ||Product-X (RED)||A||A+||L > ||O||A||A|| > ||Product-X (BLUE)||L||A||A+||A||O||L > || > > Availability Codes: > *(A) - Available* _i.e_. product has more number of quantity then safety > stock. > *(A+) - Highly Available* _i.e_ product has more number of quantities than > max limit. > *(L) - Low* _i.e._ product has less quantity than safety stock. > *(O) - Out of Stock* _i.e_ product is not in stock. > > Tagging [~swash78] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OFBIZ-10356) Display of entities in text input field for Product Name
[
https://issues.apache.org/jira/browse/OFBIZ-10356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux closed OFBIZ-10356.
---
Resolution: Fixed
Fix Version/s: 18.12.01
16.11.06
17.12.01
Thank you Rajesh Kumar Mallah for report, Swapnil M Mane for discussion, and
Ankit Joshi for the fix
This was due to OFBIZ-248 when StringUtil.wrapString() was not yet available
(IIRW)
Fixed in
trunk r1858275
R18 r1858276
R17 r1858277
R16 r r1858278
> Display of entities in text input field for Product Name
>
>
> Key: OFBIZ-10356
> URL: https://issues.apache.org/jira/browse/OFBIZ-10356
> Project: OFBiz
> Issue Type: Bug
> Components: product
>Reporter: Rajesh Kumar Mallah
>Assignee: Jacques Le Roux
>Priority: Minor
> Fix For: 17.12.01, 16.11.06, 18.12.01
>
> Attachments: OFBIZ-10356.patch
>
>
> In the url:
> https://demo-stable.ofbiz.apache.org/catalog/control/EditProductContent?productId=GZ-1006-1
> the "Product Name" under "Override Simple Fields" is unnecessarily
> expressed in entity format . The string displayed in product name
> field is:{code}"Open Gizmo LGPL" {code} it could have been a
> simple "Open Gizmo (LGPL)"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10356) Display of entities in text input field for Product Name
[
https://issues.apache.org/jira/browse/OFBIZ-10356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux updated OFBIZ-10356:
Summary: Display of entities in text input field for Product Name (was:
display of entities in text input field)
> Display of entities in text input field for Product Name
>
>
> Key: OFBIZ-10356
> URL: https://issues.apache.org/jira/browse/OFBIZ-10356
> Project: OFBiz
> Issue Type: Bug
> Components: product
>Reporter: Rajesh Kumar Mallah
>Assignee: Jacques Le Roux
>Priority: Minor
> Attachments: OFBIZ-10356.patch
>
>
> In the url:
> https://demo-stable.ofbiz.apache.org/catalog/control/EditProductContent?productId=GZ-1006-1
> the "Product Name" under "Override Simple Fields" is unnecessarily
> expressed in entity format . The string displayed in product name
> field is:{code}"Open Gizmo LGPL" {code} it could have been a
> simple "Open Gizmo (LGPL)"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-10356) display of entities in text input field
[
https://issues.apache.org/jira/browse/OFBIZ-10356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827600#comment-16827600
]
Jacques Le Roux commented on OFBIZ-10356:
-
Though it's only an UI issue, it's quite annoying. So as it's a simple and
clean solution I decided to backport and make this a bug.
> display of entities in text input field
> ---
>
> Key: OFBIZ-10356
> URL: https://issues.apache.org/jira/browse/OFBIZ-10356
> Project: OFBiz
> Issue Type: Bug
> Components: product
>Reporter: Rajesh Kumar Mallah
>Assignee: Jacques Le Roux
>Priority: Minor
> Attachments: OFBIZ-10356.patch
>
>
> In the url:
> https://demo-stable.ofbiz.apache.org/catalog/control/EditProductContent?productId=GZ-1006-1
> the "Product Name" under "Override Simple Fields" is unnecessarily
> expressed in entity format . The string displayed in product name
> field is:{code}"Open Gizmo LGPL" {code} it could have been a
> simple "Open Gizmo (LGPL)"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10356) display of entities in text input field
[
https://issues.apache.org/jira/browse/OFBIZ-10356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux updated OFBIZ-10356:
Issue Type: Bug (was: Improvement)
> display of entities in text input field
> ---
>
> Key: OFBIZ-10356
> URL: https://issues.apache.org/jira/browse/OFBIZ-10356
> Project: OFBiz
> Issue Type: Bug
> Components: product
>Reporter: Rajesh Kumar Mallah
>Assignee: Jacques Le Roux
>Priority: Minor
> Attachments: OFBIZ-10356.patch
>
>
> In the url:
> https://demo-stable.ofbiz.apache.org/catalog/control/EditProductContent?productId=GZ-1006-1
> the "Product Name" under "Override Simple Fields" is unnecessarily
> expressed in entity format . The string displayed in product name
> field is:{code}"Open Gizmo LGPL" {code} it could have been a
> simple "Open Gizmo (LGPL)"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10356) display of entities in text input field
[
https://issues.apache.org/jira/browse/OFBIZ-10356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux updated OFBIZ-10356:
Description:
In the url:
https://demo-stable.ofbiz.apache.org/catalog/control/EditProductContent?productId=GZ-1006-1
the "Product Name" under "Override Simple Fields" is unnecessarily
expressed in entity format . The string displayed in product name
field is:{code}"Open Gizmo LGPL" {code} it could have been a
simple "Open Gizmo (LGPL)"
was:
In the url:
[https://demo-stable.ofbiz.apache.org/catalog/control/EditProductContent?productId=GZ-1006-1]
the "Product Name" under "Override Simple Fields" is unnecessarily
expressed in entity format . The string displayed in product name
field is:{code}"Open Gizmo LGPL" {code} it could have been a
simple "Open Gizmo (LGPL)"
> display of entities in text input field
> ---
>
> Key: OFBIZ-10356
> URL: https://issues.apache.org/jira/browse/OFBIZ-10356
> Project: OFBiz
> Issue Type: Improvement
> Components: product
>Reporter: Rajesh Kumar Mallah
>Assignee: Jacques Le Roux
>Priority: Minor
> Attachments: OFBIZ-10356.patch
>
>
> In the url:
> https://demo-stable.ofbiz.apache.org/catalog/control/EditProductContent?productId=GZ-1006-1
> the "Product Name" under "Override Simple Fields" is unnecessarily
> expressed in entity format . The string displayed in product name
> field is:{code}"Open Gizmo LGPL" {code} it could have been a
> simple "Open Gizmo (LGPL)"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10973) Rename custom component for SMS gateway integration
[
https://issues.apache.org/jira/browse/OFBIZ-10973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux updated OFBIZ-10973:
Description:
As per the comment by [~jacques.le.roux] on the commit log of the SMS gateway
integration:
{quote}
"In understand that this component currently uses "msg91 services to send sms".
But could we not have another name, more explicit, for this component, like sms
or sendsms for instance?
Services tend to disappear or change (Google is the best example). So I'd not
associate the name of an open source component to a commercial services
provider (with a free SMS quota option). Even if hopefully it will stay as
is..."
{quote}
Need to rename the custom component and replace all occurrences in code level.
was:
As per the comment by [~jacques.le.roux] on the commit log of the SMS gateway
integration:
"In understand that this component currently uses "msg91 services to send sms".
But could we not have another name, more explicit, for this component, like sms
or sendsms for instance?
Services tend to disappear or change (Google is the best example). So I'd not
associate the name of an open source component to a commercial services
provider (with a free SMS quota option). Even if hopefully it will stay as
is..."
Need to rename the custom component and replace all occurrences in code level.
> Rename custom component for SMS gateway integration
> ---
>
> Key: OFBIZ-10973
> URL: https://issues.apache.org/jira/browse/OFBIZ-10973
> Project: OFBiz
> Issue Type: Sub-task
>Affects Versions: Trunk
>Reporter: Pritam Kute
>Assignee: vivek singh bisen
>Priority: Major
>
> As per the comment by [~jacques.le.roux] on the commit log of the SMS gateway
> integration:
> {quote}
> "In understand that this component currently uses "msg91 services to send
> sms".
> But could we not have another name, more explicit, for this component, like
> sms or sendsms for instance?
> Services tend to disappear or change (Google is the best example). So I'd not
> associate the name of an open source component to a commercial services
> provider (with a free SMS quota option). Even if hopefully it will stay as
> is..."
> {quote}
> Need to rename the custom component and replace all occurrences in code level.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10356) display of entities in text input field
[
https://issues.apache.org/jira/browse/OFBIZ-10356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux reassigned OFBIZ-10356:
---
Assignee: Jacques Le Roux
> display of entities in text input field
> ---
>
> Key: OFBIZ-10356
> URL: https://issues.apache.org/jira/browse/OFBIZ-10356
> Project: OFBiz
> Issue Type: Improvement
> Components: product
>Reporter: Rajesh Kumar Mallah
>Assignee: Jacques Le Roux
>Priority: Minor
> Attachments: OFBIZ-10356.patch
>
>
>
> In the url:
> [https://demo-stable.ofbiz.apache.org/catalog/control/EditProductContent?productId=GZ-1006-1]
>
> the "Product Name" under "Override Simple Fields" is unnecessarily
> expressed in entity format . The string displayed in product name
> field is:{code}"Open Gizmo LGPL" {code} it could have been a
> simple "Open Gizmo (LGPL)"
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (OFBIZ-7935) Move 3rd party shipping integrations from product application to plugins
[ https://issues.apache.org/jira/browse/OFBIZ-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak reassigned OFBIZ-7935: Assignee: Mridul Pathak > Move 3rd party shipping integrations from product application to plugins > > > Key: OFBIZ-7935 > URL: https://issues.apache.org/jira/browse/OFBIZ-7935 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: Trunk >Reporter: Mridul Pathak >Assignee: Mridul Pathak >Priority: Major > > This is a placeholder issue to capture all sub tasks for removing 3rd party > shipping integrations from product application and moving to a new component > in special purpose. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-7415) Move 3rd party payment integrations from accounting application to plugins
[ https://issues.apache.org/jira/browse/OFBIZ-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak reassigned OFBIZ-7415: Assignee: Mridul Pathak > Move 3rd party payment integrations from accounting application to plugins > -- > > Key: OFBIZ-7415 > URL: https://issues.apache.org/jira/browse/OFBIZ-7415 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Mridul Pathak >Priority: Major > Attachments: OFBIZ_7415.patch > > > This is a placeholder issue to capture all sub tasks for removing 3rd party > payment integrations from accounting application and moving to a new > component in special purpose. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827555#comment-16827555
]
Jayansh Shinde edited comment on OFBIZ-10966 at 4/27/19 1:17 PM:
-
Reference [https://www.jsonschemavalidator.net/] for json validation against
json schema.
Tried data:
{"Party":
{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED"},
"Product": {"productId":"654321", "productName": "Round Hat"}}
was (Author: jayansh):
Reference [https://www.jsonschemavalidator.net/] for json validation against
json schema
> JSON entity data import and export utility
> --
>
> Key: OFBIZ-10966
> URL: https://issues.apache.org/jira/browse/OFBIZ-10966
> Project: OFBiz
> Issue Type: New Feature
> Components: framework
>Reporter: Jayansh Shinde
>Priority: Minor
>
> *Entity data import/export in JSON format*
>
> Currently, we have support to import/export entity data in XML format. We are
> required to have support for JSON format which looks quite similar to XML
> support. We are summarizing how current data looks and how its done in
> current system and proposing how it should be done.
>
> Just an example the existing xml data may look like:
> {color:#008080}<{color}{color:#3f7f7f}Party{color}
> {color:#7f007f}partyId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"_{color}{color:#2a00ff}_123456_{color}{color:#2a00ff}_"_{color}
>
> {color:#7f007f}partyTypeId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PERSON"_{color}
>
> {color:#7f007f}statusId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PARTY_ENABLED"_{color}{color:#008080}/>{color}
> same proposed JSON data will look like:
>
> {color:#00}_{“Party”:
> \{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}_{color}
>
> {color:#00}*Proposal:*{color}
> _Services can be *entityImportJson* and *entityImportDirJson* for importing
> json from screen and directory respectively. And *entityExportAllJson* for
> exporting entity data in JSON, similar to existing services for xml.
> {color:#00}Our suggestion that Json data must be validated via a json
> schema during upload.{color}{color:#00}R{color}{color:#00}efer
> {color}{color:#00}[https://json-schema.org/] {color}{color:#00}for
> more information on json schema.{color}_
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827555#comment-16827555
]
Jayansh Shinde edited comment on OFBIZ-10966 at 4/27/19 1:15 PM:
-
Reference [https://www.jsonschemavalidator.net/] for json validation against
json schema
was (Author: jayansh):
Reference [https://jsonschema.net/] for json validation against json schema
> JSON entity data import and export utility
> --
>
> Key: OFBIZ-10966
> URL: https://issues.apache.org/jira/browse/OFBIZ-10966
> Project: OFBiz
> Issue Type: New Feature
> Components: framework
>Reporter: Jayansh Shinde
>Priority: Minor
>
> *Entity data import/export in JSON format*
>
> Currently, we have support to import/export entity data in XML format. We are
> required to have support for JSON format which looks quite similar to XML
> support. We are summarizing how current data looks and how its done in
> current system and proposing how it should be done.
>
> Just an example the existing xml data may look like:
> {color:#008080}<{color}{color:#3f7f7f}Party{color}
> {color:#7f007f}partyId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"_{color}{color:#2a00ff}_123456_{color}{color:#2a00ff}_"_{color}
>
> {color:#7f007f}partyTypeId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PERSON"_{color}
>
> {color:#7f007f}statusId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PARTY_ENABLED"_{color}{color:#008080}/>{color}
> same proposed JSON data will look like:
>
> {color:#00}_{“Party”:
> \{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}_{color}
>
> {color:#00}*Proposal:*{color}
> _Services can be *entityImportJson* and *entityImportDirJson* for importing
> json from screen and directory respectively. And *entityExportAllJson* for
> exporting entity data in JSON, similar to existing services for xml.
> {color:#00}Our suggestion that Json data must be validated via a json
> schema during upload.{color}{color:#00}R{color}{color:#00}efer
> {color}{color:#00}[https://json-schema.org/] {color}{color:#00}for
> more information on json schema.{color}_
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (OFBIZ-7936) Move 3rd party tax integrations from order application to plugins
[ https://issues.apache.org/jira/browse/OFBIZ-7936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak reassigned OFBIZ-7936: Assignee: Mridul Pathak > Move 3rd party tax integrations from order application to plugins > - > > Key: OFBIZ-7936 > URL: https://issues.apache.org/jira/browse/OFBIZ-7936 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk >Reporter: Mridul Pathak >Assignee: Mridul Pathak >Priority: Major > > This is a placeholder issue to capture all sub tasks for removing 3rd party > tax integrations from order application and moving to a new component in > special purpose. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-7529) Delete stale java files from applications and framework
[ https://issues.apache.org/jira/browse/OFBIZ-7529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak reassigned OFBIZ-7529: Assignee: Mridul Pathak > Delete stale java files from applications and framework > --- > > Key: OFBIZ-7529 > URL: https://issues.apache.org/jira/browse/OFBIZ-7529 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Mridul Pathak >Assignee: Mridul Pathak >Priority: Major > > As per the discussions on the thread - > http://ofbiz.135035.n4.nabble.com/Proposal-to-delete-stale-java-files-tt4683855.html, > following files and their references needs to be deleted from applications > and framework, > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeByteArrayInputStream.java > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeByteArrayOutputStream.java > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeServices.java > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeWorker.java > applications/content/src/org/ofbiz/content/report > applications/content/src/org/ofbiz/content/report/JREntityListIteratorDataSource.java > applications/content/src/org/ofbiz/content/report/JRMapCollectionDataSource.java > applications/product/src/ShipmentScaleApplet.java > applications/securityext/src/org/ofbiz/securityext/thirdparty/truition/TruitionCoReg.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsJXlsViewHandler.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsPdfViewHandler.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsPoiXlsViewHandler.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsXmlViewHandler.java -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-7210) Redesign org.ofbiz.entity.datasource
[ https://issues.apache.org/jira/browse/OFBIZ-7210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak reassigned OFBIZ-7210: Assignee: (was: Mridul Pathak) > Redesign org.ofbiz.entity.datasource > > > Key: OFBIZ-7210 > URL: https://issues.apache.org/jira/browse/OFBIZ-7210 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Mridul Pathak >Priority: Major > > All objects under org.ofbiz.entity.datasource need to be redesigned into an > interface model and implemented with concrete classes. Things like the > GenericDao should be broken down to many pieces as it is massive, complex, > and overly designed (Interface Segregation principle violated) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10853) AutoDescription of promotion showing invalid text
[ https://issues.apache.org/jira/browse/OFBIZ-10853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suraj Khurana reassigned OFBIZ-10853: - Assignee: Suraj Khurana > AutoDescription of promotion showing invalid text > - > > Key: OFBIZ-10853 > URL: https://issues.apache.org/jira/browse/OFBIZ-10853 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Upcoming Branch, Release Branch 18.12 >Reporter: Lalit Dashora >Assignee: Suraj Khurana >Priority: Major > Attachments: OFBIZ-10853-issue-in-promo-autoDescription.patch > > > Steps to replicate > 1. Navigate to https://demo-trunk.ofbiz.apache.org/ecommerce/control/main > 2. Click on view all promotion in special offer section. > 3. click on the detail of promotion. > 4. Promotion detail will be shown. See the generated description. > 5. > [#https://demo-trunk.ofbiz.apache.org/ecommerce/control/showPromotionDetails?productPromoId=9019] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-7935) Move 3rd party shipping integrations from product application to plugins
[ https://issues.apache.org/jira/browse/OFBIZ-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak reassigned OFBIZ-7935: Assignee: (was: Mridul Pathak) > Move 3rd party shipping integrations from product application to plugins > > > Key: OFBIZ-7935 > URL: https://issues.apache.org/jira/browse/OFBIZ-7935 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: Trunk >Reporter: Mridul Pathak >Priority: Major > > This is a placeholder issue to capture all sub tasks for removing 3rd party > shipping integrations from product application and moving to a new component > in special purpose. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-7415) Move 3rd party payment integrations from accounting application to plugins
[ https://issues.apache.org/jira/browse/OFBIZ-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak reassigned OFBIZ-7415: Assignee: (was: Mridul Pathak) > Move 3rd party payment integrations from accounting application to plugins > -- > > Key: OFBIZ-7415 > URL: https://issues.apache.org/jira/browse/OFBIZ-7415 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Pierre Smits >Priority: Major > Attachments: OFBIZ_7415.patch > > > This is a placeholder issue to capture all sub tasks for removing 3rd party > payment integrations from accounting application and moving to a new > component in special purpose. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-7529) Delete stale java files from applications and framework
[ https://issues.apache.org/jira/browse/OFBIZ-7529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak reassigned OFBIZ-7529: Assignee: (was: Mridul Pathak) > Delete stale java files from applications and framework > --- > > Key: OFBIZ-7529 > URL: https://issues.apache.org/jira/browse/OFBIZ-7529 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Mridul Pathak >Priority: Major > > As per the discussions on the thread - > http://ofbiz.135035.n4.nabble.com/Proposal-to-delete-stale-java-files-tt4683855.html, > following files and their references needs to be deleted from applications > and framework, > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeByteArrayInputStream.java > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeByteArrayOutputStream.java > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeServices.java > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeWorker.java > applications/content/src/org/ofbiz/content/report > applications/content/src/org/ofbiz/content/report/JREntityListIteratorDataSource.java > applications/content/src/org/ofbiz/content/report/JRMapCollectionDataSource.java > applications/product/src/ShipmentScaleApplet.java > applications/securityext/src/org/ofbiz/securityext/thirdparty/truition/TruitionCoReg.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsJXlsViewHandler.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsPdfViewHandler.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsPoiXlsViewHandler.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsXmlViewHandler.java -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-7936) Move 3rd party tax integrations from order application to plugins
[ https://issues.apache.org/jira/browse/OFBIZ-7936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak reassigned OFBIZ-7936: Assignee: (was: Mridul Pathak) > Move 3rd party tax integrations from order application to plugins > - > > Key: OFBIZ-7936 > URL: https://issues.apache.org/jira/browse/OFBIZ-7936 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk >Reporter: Mridul Pathak >Priority: Major > > This is a placeholder issue to capture all sub tasks for removing 3rd party > tax integrations from order application and moving to a new component in > special purpose. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OFBIZ-10849) UI issue on ecommerce main page
[ https://issues.apache.org/jira/browse/OFBIZ-10849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-10849. --- Not sure how to verify/test that, but I'm closing anyway > UI issue on ecommerce main page > --- > > Key: OFBIZ-10849 > URL: https://issues.apache.org/jira/browse/OFBIZ-10849 > Project: OFBiz > Issue Type: Sub-task > Components: ecommerce >Reporter: Garima jain >Assignee: Deepak Dixit >Priority: Minor > Fix For: 18.12.01 > > Attachments: OFBIZ-10849.patch, OFBIZ-10849.patch, Screenshot > 2019-03-09 at 11.43.10 AM.png, ViewCartAfter.png, ViewCartBefore.png > > > Steps to generate > # Navigate to [demo-trunk > ecom|https://demo-trunk.ofbiz.apache.org/ecommerce/control/main] > # scroll the page and see the last category section in the right column of > the screen. > # The last category section seems to be distorted because of the empty list > Screenshot attached for the same. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suraj Khurana closed OFBIZ-10518. - Thanks Deepak Nigam for initiating this feature and providing the patches, Arun Patidar for review and Swapnil Shah for design discussions. > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Suraj Khurana >Priority: Major > Fix For: Upcoming Branch > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, CreateAllocationPlanEditMode-Step2.png, > EditAllocationPlan.png, FindAllocationPlan.png, OFBiz-10518-UI.patch, > OFBiz-10518-data.patch, OFBiz-10518-entity-model.patch, > OFBiz-10518-secas.patch, OFBiz-10518-services.patch, > OFBiz-10518-ui-labels.patch, OFBiz-10518.patch, OFBiz-10518.patch, > OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, > ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-7936) Move 3rd party tax integrations from order application to plugins
[ https://issues.apache.org/jira/browse/OFBIZ-7936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak updated OFBIZ-7936: - Summary: Move 3rd party tax integrations from order application to plugins (was: Move 3rd party tax integrations from order application to specialpurpose) > Move 3rd party tax integrations from order application to plugins > - > > Key: OFBIZ-7936 > URL: https://issues.apache.org/jira/browse/OFBIZ-7936 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk >Reporter: Mridul Pathak >Assignee: Mridul Pathak >Priority: Major > > This is a placeholder issue to capture all sub tasks for removing 3rd party > tax integrations from order application and moving to a new component in > special purpose. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suraj Khurana resolved OFBIZ-10518. --- Resolution: Implemented Fix Version/s: (was: Trunk) Upcoming Branch This has been committed to OFBiz trunk at revision #1858270. > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Suraj Khurana >Priority: Major > Fix For: Upcoming Branch > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, CreateAllocationPlanEditMode-Step2.png, > EditAllocationPlan.png, FindAllocationPlan.png, OFBiz-10518-UI.patch, > OFBiz-10518-data.patch, OFBiz-10518-entity-model.patch, > OFBiz-10518-secas.patch, OFBiz-10518-services.patch, > OFBiz-10518-ui-labels.patch, OFBiz-10518.patch, OFBiz-10518.patch, > OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, > ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-7935) Move 3rd party shipping integrations from product application to plugins
[ https://issues.apache.org/jira/browse/OFBIZ-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak updated OFBIZ-7935: - Summary: Move 3rd party shipping integrations from product application to plugins (was: Move 3rd party shipping integrations from product application to specialpurpose) > Move 3rd party shipping integrations from product application to plugins > > > Key: OFBIZ-7935 > URL: https://issues.apache.org/jira/browse/OFBIZ-7935 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: Trunk >Reporter: Mridul Pathak >Assignee: Mridul Pathak >Priority: Major > > This is a placeholder issue to capture all sub tasks for removing 3rd party > shipping integrations from product application and moving to a new component > in special purpose. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-7415) Move 3rd party payment integrations from accounting application to plugins
[ https://issues.apache.org/jira/browse/OFBIZ-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak updated OFBIZ-7415: - Summary: Move 3rd party payment integrations from accounting application to plugins (was: Move 3rd party payment integrations from accounting application to specialpurpose) > Move 3rd party payment integrations from accounting application to plugins > -- > > Key: OFBIZ-7415 > URL: https://issues.apache.org/jira/browse/OFBIZ-7415 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Mridul Pathak >Priority: Major > Attachments: OFBIZ_7415.patch > > > This is a placeholder issue to capture all sub tasks for removing 3rd party > payment integrations from accounting application and moving to a new > component in special purpose. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-5438) Virtual feature selection and selected variant price inconsistencies
[ https://issues.apache.org/jira/browse/OFBIZ-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak reassigned OFBIZ-5438: Assignee: (was: Mridul Pathak) > Virtual feature selection and selected variant price inconsistencies > > > Key: OFBIZ-5438 > URL: https://issues.apache.org/jira/browse/OFBIZ-5438 > Project: OFBiz > Issue Type: Improvement > Components: order >Reporter: Christian Carlow >Priority: Minor > > To reproduce this issue: > 1. Create a sales order for DemoCustCompany > 2. Add WG-9944 to the cart > 3. Select Black (notice +$4.30) and 4-Wheels and click "Add to Cart" > 4. Click the check mark for the WG-9944 variant item that was added to the > cart and then click the "Remove Selected" button > 5. Navigate to the WG-9944 product features page > 6. Click feature 9000 to edit the Black Color feature > 7. Update the feature price from 4.3 to 1.3 > 8. Add WG-9944 to the cart again by selecting the Black (notice now +$1.30) > and 4-Wheel feature options > After step 9, notice that the item price is actually calculated using the > previous feature default price value even though the new feature price is > listed with the option. > A similar problem occurs if the virtual product default price is changed. > The feature selection page shows the updated virtual product price but once > the features are selected, the default price of the variant product which was > set when the variant was initially created is still set to the previous > default price that existed before the variant default price was changed. > Maybe some logic should exist to check that the selected features prices add > up to the variant default price value and if they do not, then the previous > variant default price thruDate should be set and a new default price > consistent with the feature price sum created. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10980) Billing Information UI getting distorted
[ https://issues.apache.org/jira/browse/OFBIZ-10980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827590#comment-16827590 ] Suraj Khurana commented on OFBIZ-10980: --- Hello Sourabh, Please check and update Affect version. Thanks in advance !! > Billing Information UI getting distorted > > > Key: OFBIZ-10980 > URL: https://issues.apache.org/jira/browse/OFBIZ-10980 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Trunk >Reporter: Padmavati Rawat >Assignee: Sourabh Punyani >Priority: Major > Attachments: ImprovetheUI.png, OFBIZ-10980.patch > > > Steps: > 1. Visit the https://demo-trunk.ofbiz.apache.org/ecommerce/control/main page. > 2. Open customer profile page from navbar menu. > 3. In Payment method information click on the Update button of EFT account. > 4. Scroll the page and check the UI of Billing Information. > Actual: > Radio button UI distorted on the Billing Information section of EFT Account. > Please refer screenshot: -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10890) Requesthandler exception is showing after clicking cancel/done button on editPerson screen
[ https://issues.apache.org/jira/browse/OFBIZ-10890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Choudhary reassigned OFBIZ-10890: - Assignee: Aditya Sharma (was: Pradeep Choudhary) > Requesthandler exception is showing after clicking cancel/done button on > editPerson screen > -- > > Key: OFBIZ-10890 > URL: https://issues.apache.org/jira/browse/OFBIZ-10890 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: Trunk >Reporter: Phalak Minal Yuvraj >Assignee: Aditya Sharma >Priority: Major > Attachments: OFBIZ-10890.patch > > > Steps to regenerate: > 1) Open [https://demo-trunk.ofbiz.apache.org/partymgr/control/main] > 2) Create new customer > 3) Update Personal Information > 4) Now click on Cancel/Done > Actual: Error is occurring while clicking on cancel/done button. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10890) Requesthandler exception is showing after clicking cancel/done button on editPerson screen
[ https://issues.apache.org/jira/browse/OFBIZ-10890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Choudhary reassigned OFBIZ-10890: - Assignee: Pradeep Choudhary (was: Phalak Minal Yuvraj) > Requesthandler exception is showing after clicking cancel/done button on > editPerson screen > -- > > Key: OFBIZ-10890 > URL: https://issues.apache.org/jira/browse/OFBIZ-10890 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: Trunk >Reporter: Phalak Minal Yuvraj >Assignee: Pradeep Choudhary >Priority: Major > Attachments: OFBIZ-10890.patch > > > Steps to regenerate: > 1) Open [https://demo-trunk.ofbiz.apache.org/partymgr/control/main] > 2) Create new customer > 3) Update Personal Information > 4) Now click on Cancel/Done > Actual: Error is occurring while clicking on cancel/done button. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10794) Promotion condition/action type of few promotion not showing
[ https://issues.apache.org/jira/browse/OFBIZ-10794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lalit Dashora reassigned OFBIZ-10794: - Assignee: (was: Lalit Dashora) > Promotion condition/action type of few promotion not showing > > > Key: OFBIZ-10794 > URL: https://issues.apache.org/jira/browse/OFBIZ-10794 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk, Release Branch 18.12 >Reporter: Lalit Dashora >Priority: Major > Attachments: OFBIZ-10794.patch > > > Steps to replicate: > 1. Open > https://demo-trunk.ofbiz.apache.org/catalog/control/EditProductPromoRules?productPromoId=9000 > with login credentials admin/ofbiz > 2. Validate that the condition type and action type is not shown in dropdown. > 3. Now validate the inputParamEnumId, productPromoActionEnumId of > productPromoAction and productPromoCond entity. > 4. Also try to change the condition type and click on update button. Error is > rendering on screen. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10853) AutoDescription of promotion showing invalid text
[ https://issues.apache.org/jira/browse/OFBIZ-10853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lalit Dashora reassigned OFBIZ-10853: - Assignee: (was: Lalit Dashora) > AutoDescription of promotion showing invalid text > - > > Key: OFBIZ-10853 > URL: https://issues.apache.org/jira/browse/OFBIZ-10853 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Upcoming Branch, Release Branch 18.12 >Reporter: Lalit Dashora >Priority: Major > Attachments: OFBIZ-10853-issue-in-promo-autoDescription.patch > > > Steps to replicate > 1. Navigate to https://demo-trunk.ofbiz.apache.org/ecommerce/control/main > 2. Click on view all promotion in special offer section. > 3. click on the detail of promotion. > 4. Promotion detail will be shown. See the generated description. > 5. > [#https://demo-trunk.ofbiz.apache.org/ecommerce/control/showPromotionDetails?productPromoId=9019] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10890) Requesthandler exception is showing after clicking cancel/done button on editPerson screen
[ https://issues.apache.org/jira/browse/OFBIZ-10890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Minal Phalak updated OFBIZ-10890: - Attachment: OFBIZ-10890.patch > Requesthandler exception is showing after clicking cancel/done button on > editPerson screen > -- > > Key: OFBIZ-10890 > URL: https://issues.apache.org/jira/browse/OFBIZ-10890 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: Trunk >Reporter: Phalak Minal Yuvraj >Assignee: Phalak Minal Yuvraj >Priority: Major > Attachments: OFBIZ-10890.patch > > > Steps to regenerate: > 1) Open [https://demo-trunk.ofbiz.apache.org/partymgr/control/main] > 2) Create new customer > 3) Update Personal Information > 4) Now click on Cancel/Done > Actual: Error is occurring while clicking on cancel/done button. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827589#comment-16827589 ] Deepak Nigam commented on OFBIZ-10518: -- For enabling this feature productStore.allocateInventory should be equal to Y. > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Suraj Khurana >Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, CreateAllocationPlanEditMode-Step2.png, > EditAllocationPlan.png, FindAllocationPlan.png, OFBiz-10518-UI.patch, > OFBiz-10518-data.patch, OFBiz-10518-entity-model.patch, > OFBiz-10518-secas.patch, OFBiz-10518-services.patch, > OFBiz-10518-ui-labels.patch, OFBiz-10518.patch, OFBiz-10518.patch, > OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, > ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-9086) Unit test case for service - quickSendPayment
[ https://issues.apache.org/jira/browse/OFBIZ-9086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suraj Khurana reassigned OFBIZ-9086: Assignee: Suraj Khurana (was: Anushi Gupta) > Unit test case for service - quickSendPayment > -- > > Key: OFBIZ-9086 > URL: https://issues.apache.org/jira/browse/OFBIZ-9086 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk >Reporter: Deepak Nigam >Assignee: Suraj Khurana >Priority: Minor > Attachments: OFBIZ-9086.patch, OFBIZ-9086.patch > > > Unit test case for service - quickSendPayment -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10883) Picklist is in Input status even after order is completed
[ https://issues.apache.org/jira/browse/OFBIZ-10883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shikha Jaiswal reassigned OFBIZ-10883: -- Assignee: (was: Shikha Jaiswal) > Picklist is in Input status even after order is completed > - > > Key: OFBIZ-10883 > URL: https://issues.apache.org/jira/browse/OFBIZ-10883 > Project: OFBiz > Issue Type: Bug >Affects Versions: 16.11.04 >Reporter: Rashi Dhagat >Priority: Major > Attachments: OFBIZ-10883.patch, OrderStatus.jpg, PicklistStatus.jpg > > > Steps to regenerate: > 1. Open https://demo-stable.ofbiz.apache.org/ordermgr/control/main > 2. Create order > 3. Open > https://demo-stable.ofbiz.apache.org/facility/control/PicklistOptions?facilityId=WebStoreWarehouse > 4. Create Picking > 5. Click on Packing under the facility > 6. Enter order id and click on pack order > 7. Enter package detail and complete packaging > 8. Open > https://demo-trunk.ofbiz.apache.org/facility/control/PicklistManage?facilityId=WebStoreWarehouse > Actual: Picklist is in the input status > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10883) Picklist is in Input status even after order is completed
[ https://issues.apache.org/jira/browse/OFBIZ-10883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827588#comment-16827588 ] Shikha Jaiswal commented on OFBIZ-10883: Completed the task and attached the patch > Picklist is in Input status even after order is completed > - > > Key: OFBIZ-10883 > URL: https://issues.apache.org/jira/browse/OFBIZ-10883 > Project: OFBiz > Issue Type: Bug >Affects Versions: 16.11.04 >Reporter: Rashi Dhagat >Assignee: Shikha Jaiswal >Priority: Major > Attachments: OFBIZ-10883.patch, OrderStatus.jpg, PicklistStatus.jpg > > > Steps to regenerate: > 1. Open https://demo-stable.ofbiz.apache.org/ordermgr/control/main > 2. Create order > 3. Open > https://demo-stable.ofbiz.apache.org/facility/control/PicklistOptions?facilityId=WebStoreWarehouse > 4. Create Picking > 5. Click on Packing under the facility > 6. Enter order id and click on pack order > 7. Enter package detail and complete packaging > 8. Open > https://demo-trunk.ofbiz.apache.org/facility/control/PicklistManage?facilityId=WebStoreWarehouse > Actual: Picklist is in the input status > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10883) Picklist is in Input status even after order is completed
[ https://issues.apache.org/jira/browse/OFBIZ-10883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shikha Jaiswal updated OFBIZ-10883: --- Attachment: OFBIZ-10883.patch > Picklist is in Input status even after order is completed > - > > Key: OFBIZ-10883 > URL: https://issues.apache.org/jira/browse/OFBIZ-10883 > Project: OFBiz > Issue Type: Bug >Affects Versions: 16.11.04 >Reporter: Rashi Dhagat >Assignee: Shikha Jaiswal >Priority: Major > Attachments: OFBIZ-10883.patch, OrderStatus.jpg, PicklistStatus.jpg > > > Steps to regenerate: > 1. Open https://demo-stable.ofbiz.apache.org/ordermgr/control/main > 2. Create order > 3. Open > https://demo-stable.ofbiz.apache.org/facility/control/PicklistOptions?facilityId=WebStoreWarehouse > 4. Create Picking > 5. Click on Packing under the facility > 6. Enter order id and click on pack order > 7. Enter package detail and complete packaging > 8. Open > https://demo-trunk.ofbiz.apache.org/facility/control/PicklistManage?facilityId=WebStoreWarehouse > Actual: Picklist is in the input status > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10985) UI issue on View Order page
[ https://issues.apache.org/jira/browse/OFBIZ-10985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garima jain reassigned OFBIZ-10985: --- Assignee: Garima jain > UI issue on View Order page > --- > > Key: OFBIZ-10985 > URL: https://issues.apache.org/jira/browse/OFBIZ-10985 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk, Release Branch 16.11 >Reporter: Rashi Dhagat >Assignee: Garima jain >Priority: Minor > Attachments: ViewOrderPage.jpg > > > Steps to regenerate: > # Open URL [https://demo-trunk.ofbiz.apache.org/ordermgr/control/main] > # Click on any order in Approved status > Actual: > # In Contact Information section, admin (username) is a button > # "Send confirmation email" button in brackets > Expected: > # Username should not be a button > # The button should not be in brackets. > Please refer attachment for same. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10985) Ui issue on View Order page
Rashi Dhagat created OFBIZ-10985: Summary: Ui issue on View Order page Key: OFBIZ-10985 URL: https://issues.apache.org/jira/browse/OFBIZ-10985 Project: OFBiz Issue Type: Bug Affects Versions: Release Branch 16.11, Trunk Reporter: Rashi Dhagat Attachments: ViewOrderPage.jpg Steps to regenerate: # Open URL [https://demo-trunk.ofbiz.apache.org/ordermgr/control/main] # Click on any order in Approved status Actual: # In Contact Information section, admin (username) is a button # "Send confirmation email" button in brackets Expected: # Username should not be a button # The button should not be in brackets. Please refer attachment for same. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10985) UI issue on View Order page
[ https://issues.apache.org/jira/browse/OFBIZ-10985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rashi Dhagat updated OFBIZ-10985: - Summary: UI issue on View Order page (was: Ui issue on View Order page) > UI issue on View Order page > --- > > Key: OFBIZ-10985 > URL: https://issues.apache.org/jira/browse/OFBIZ-10985 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk, Release Branch 16.11 >Reporter: Rashi Dhagat >Priority: Minor > Attachments: ViewOrderPage.jpg > > > Steps to regenerate: > # Open URL [https://demo-trunk.ofbiz.apache.org/ordermgr/control/main] > # Click on any order in Approved status > Actual: > # In Contact Information section, admin (username) is a button > # "Send confirmation email" button in brackets > Expected: > # Username should not be a button > # The button should not be in brackets. > Please refer attachment for same. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-5426) mysql: ERROR 1071 (42000): Specified key was too long; max key length is 767 bytes
[ https://issues.apache.org/jira/browse/OFBIZ-5426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827586#comment-16827586 ] Deepak Dixit commented on OFBIZ-5426: - Hi Pawan, Your patch looks good to me, only one suggestion, I think we can remove the createProductPromoCodeEmail this is not used anywhere in the code. We can mark this service as deprecated > mysql: ERROR 1071 (42000): Specified key was too long; max key length is 767 > bytes > -- > > Key: OFBIZ-5426 > URL: https://issues.apache.org/jira/browse/OFBIZ-5426 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Trunk >Reporter: Leon >Assignee: Deepak Dixit >Priority: Major > Attachments: OFBIZ-5426.patch, OFBIZ-5426.patch, OFBIZ-5426.patch > > > Due to revision 1529838, the length of data type "email" was increased from > 254 to 320. But It makes the ofbiz failed to create tables such as > "PRODUCT_PROMO_CODE_EMAIL" which includes an email fields as its primary key. > The database is mysql, innodb engine and utf8 charset. The error msg: > ERROR 1071 (42000): Specified key was too long; max key length is 767 bytes. > I suggest to revert change of r1529838. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10984) User can create Incoming shipment with wrong status
Ravi Lodhi created OFBIZ-10984:
--
Summary: User can create Incoming shipment with wrong status
Key: OFBIZ-10984
URL: https://issues.apache.org/jira/browse/OFBIZ-10984
Project: OFBiz
Issue Type: Bug
Affects Versions: Trunk
Reporter: Ravi Lodhi
User can create Incoming Purchase Shipment with wrong status e.g. Input (Status
to track Outbound shipments)
Steps to reproduce:
1. Login to facility component
[https://demo-trunk.ofbiz.apache.org/facility/control/main
]2. Go to Shipments screen
(https://demo-trunk.ofbiz.apache.org/facility/control/FindShipment)
3. Click on New Shipment button to create a new Shipment.
4. Here all the statuses displayed are of outbound shipments but the user can
also select any incoming shipment type from Shipment type ID dropdown it can be
"Incoming Shipment", "Incoming Purchase Shipment" etc.
5. Select any status and Shipment type ID as "Incoming Purchase Shipment".
6. Shipment get's created successfully.
As per my knowledge, there is a different set of status to track the incoming
and outgoing shipment. Here is the list of shipment status for the reference.
*Outbound Shipment Status:*
{code:java}
{code}
*Inbound Shipment Status:*
{code:java}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10965) Error while checkout from WebPOS
[ https://issues.apache.org/jira/browse/OFBIZ-10965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sasikant Biswal reassigned OFBIZ-10965: --- Assignee: (was: Sasikant Biswal) > Error while checkout from WebPOS > - > > Key: OFBIZ-10965 > URL: https://issues.apache.org/jira/browse/OFBIZ-10965 > Project: OFBiz > Issue Type: Bug > Components: webpos >Affects Versions: 17.12.01 >Reporter: Padmavati Rawat >Priority: Major > Attachments: Errorwhilecheckout.png, OFBIZ-10965 > > > Steps: > 1. Login to the POS Terminal. > 2. Add item to the cart. > 3. Set payment by pay cash "F3 PAY CASH" > 4. click on checkout key "F8 CHECKOUT" > Actual: > System showing an error on the cart section while checkout. > Expected: > The order should be successfully placed. > Please refer screenshot: -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10965) Error while checkout from WebPOS
[ https://issues.apache.org/jira/browse/OFBIZ-10965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sasikant Biswal updated OFBIZ-10965: Attachment: OFBIZ-10965 > Error while checkout from WebPOS > - > > Key: OFBIZ-10965 > URL: https://issues.apache.org/jira/browse/OFBIZ-10965 > Project: OFBiz > Issue Type: Bug > Components: webpos >Affects Versions: 17.12.01 >Reporter: Padmavati Rawat >Assignee: Sasikant Biswal >Priority: Major > Attachments: Errorwhilecheckout.png, OFBIZ-10965 > > > Steps: > 1. Login to the POS Terminal. > 2. Add item to the cart. > 3. Set payment by pay cash "F3 PAY CASH" > 4. click on checkout key "F8 CHECKOUT" > Actual: > System showing an error on the cart section while checkout. > Expected: > The order should be successfully placed. > Please refer screenshot: -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (OFBIZ-10961) Shortkeys missing on WebPOS
[ https://issues.apache.org/jira/browse/OFBIZ-10961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827524#comment-16827524 ] Rohit Koushal edited comment on OFBIZ-10961 at 4/27/19 12:20 PM: - During Jquery update, depricated bind() function is replaced by on() but accidentally in commit r*1850712* custom user define bind() function also get replaced and causes this issue I am attaching the patch to fix this problem. was (Author: rohit.koushal): During Jquery update, depricated bind() function is replaced by on() but accedentally in on commit r*1850712* custom user define bind() function also get relaced and causes this issue I am attaching the patch to fix this problem. > Shortkeys missing on WebPOS > --- > > Key: OFBIZ-10961 > URL: https://issues.apache.org/jira/browse/OFBIZ-10961 > Project: OFBiz > Issue Type: Bug > Components: webpos >Affects Versions: Trunk, Release Branch 18.12 >Reporter: Padmavati Rawat >Assignee: Suraj Khurana >Priority: Major > Attachments: OFBIZ-10961.patch, shortkeysmissing.png > > > Steps: > 1. Visit the demo-trunk.ofbiz.apache.org link. > 2. Login to the Web POS terminal. > 2. Check the Keyboard Shortcuts section. > Actual: > Keyboard short key options are missing on demo-trunk. > Expected: > Keyboard shortcuts should be visible on the Keyboard shortcut section. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
