[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* ** inventoryItemId ** shipmentId ** shipmentItemSeqId ** quantity ** unitPrice Having InventoryItem detail at InventoryTransferItem level will help us to manage multiple Items under same InventoryTransfer and each InventoryTransferItem can be fulfilled via multiple Inventory items and/or multiple Shipments. * 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* ** 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 parameters: *** Requirement
[jira] [Assigned] (OFBIZ-9552) Unable to change facility Id in Facility lookup under Inventory Transfer section
[ https://issues.apache.org/jira/browse/OFBIZ-9552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Choudhary reassigned OFBIZ-9552: Assignee: Pradeep Choudhary > Unable to change facility Id in Facility lookup under Inventory Transfer > section > > > Key: OFBIZ-9552 > URL: https://issues.apache.org/jira/browse/OFBIZ-9552 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Renuka Srishti >Assignee: Pradeep Choudhary >Priority: Major > > 1. Go to Facility component. > 2. Select facility Id and click on submit button. > 3. Here you can see "InventoryXfers" label, click on it. > 4. Now you will redirect to > [https://demo-trunk.ofbiz.apache.org/facility/control/FindFacilityTransfers?facilityId=WebStoreWarehouse] > 5. Click on "Inventory Transfer" button. You will redirect to > [https://demo-trunk.ofbiz.apache.org/facility/control/TransferInventoryItem?facilityId=WebStoreWarehouse] > 6. Here enter inventory item id in the input box which is labeled as > inventory item id and press enter. > 7. Now you will "Inventory Transfer" section. Here click on "To Location" > look up. > First time look up will show "facility Id" label and if you want to change > the facility Id, after one-time search you can't change it. You need to > reopen the look up. > The proposed solution: Facility Id label should remain there after clicking > on Find button in Facility Lookup. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10835) In the main interface of the HR module, when the organization structure is displayed in a tree, the name of the person is not displayed.
[
https://issues.apache.org/jira/browse/OFBIZ-10835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arvind Singh Tomar reassigned OFBIZ-10835:
--
Assignee: Arvind Singh Tomar
> In the main interface of the HR module, when the organization structure is
> displayed in a tree, the name of the person is not displayed.
>
>
> Key: OFBIZ-10835
> URL: https://issues.apache.org/jira/browse/OFBIZ-10835
> Project: OFBiz
> Issue Type: Bug
> Components: humanres
>Affects Versions: 16.11.04
>Reporter: zhangqing
>Assignee: Arvind Singh Tomar
>Priority: Trivial
>
> HR模块的Main界面中，以树状显示组织结构时，没有显示出人员的名称
> 原因是：
> /ofbiz/applications/humanres/src/main/java/org/apache/ofbiz/humanres/HumanResEvents.java中的getCurrentEmployeeDetails方法中有2个参数错误。
> GenericValue memCtx =
> EntityQuery.use(delegator).from("Person").where("partyId",
> partyId).queryOne();
> 应为：
> GenericValue memCtx =
> EntityQuery.use(delegator).from("Person").where("partyId",
> memberId).queryOne();
> GenericValue memGroupCtx =
> EntityQuery.use(delegator).from("PartyGroup").where("partyId",
> partyId).queryOne();
> 应为：
> GenericValue memGroupCtx =
> EntityQuery.use(delegator).from("PartyGroup").where("partyId",
> memberId).queryOne();
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (OFBIZ-10846) In AddFinAccountTrans selectable glAccountId values are sorted on glAccountId
[
https://issues.apache.org/jira/browse/OFBIZ-10846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suraj Khurana closed OFBIZ-10846.
-
Thanks Pierre Smits for reporting, Pawan Verma for the patch and Jacques Le
Roux for comment.
> In AddFinAccountTrans selectable glAccountId values are sorted on glAccountId
> -
>
> Key: OFBIZ-10846
> URL: https://issues.apache.org/jira/browse/OFBIZ-10846
> Project: OFBiz
> Issue Type: Improvement
> Components: accounting
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Suraj Khurana
>Priority: Major
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-10846.patch
>
>
> In the AddFinAccountTrans form in FinAccountForms.xml the values in the field
> glAccountId are sorted on the primary key, per
> {code:java}
>
>
> key-field-name="glAccountId" description="${accountCode} - ${accountName}
> [${glAccountId}]">
> operator="equals" env-name="defaultOrganizationPartyId"/>
>
>
>
>
> {code}
> The sort order should however be on the accountCode field of the entity
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10846) In AddFinAccountTrans selectable glAccountId values are sorted on glAccountId
[
https://issues.apache.org/jira/browse/OFBIZ-10846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suraj Khurana updated OFBIZ-10846:
--
Affects Version/s: (was: 18.12.01)
(was: Release Branch 18.12)
(was: 16.11.06)
(was: Release Branch 17.12)
(was: 16.11.05)
(was: 16.11.04)
(was: Release Branch 16.11)
(was: 17.12.01)
(was: Release Branch 15.12)
(was: Release Branch 14.12)
(was: Release Branch 13.07)
> In AddFinAccountTrans selectable glAccountId values are sorted on glAccountId
> -
>
> Key: OFBIZ-10846
> URL: https://issues.apache.org/jira/browse/OFBIZ-10846
> Project: OFBiz
> Issue Type: Improvement
> Components: accounting
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Suraj Khurana
>Priority: Major
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-10846.patch
>
>
> In the AddFinAccountTrans form in FinAccountForms.xml the values in the field
> glAccountId are sorted on the primary key, per
> {code:java}
>
>
> key-field-name="glAccountId" description="${accountCode} - ${accountName}
> [${glAccountId}]">
> operator="equals" env-name="defaultOrganizationPartyId"/>
>
>
>
>
> {code}
> The sort order should however be on the accountCode field of the entity
--
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
]
Ankit Joshi reassigned OFBIZ-10356:
---
Assignee: Ankit Joshi
> 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: Ankit Joshi
>Priority: Minor
>
>
> 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-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: 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 >Assignee: Shikha Jaiswal >Priority: Major > Attachments: 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] [Closed] (OFBIZ-10811) PaymentGatewayServices should be using ObjectType.simpleTypeConvert for all amount variables
[ https://issues.apache.org/jira/browse/OFBIZ-10811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suraj Khurana closed OFBIZ-10811. - Thanks Jacques Le Roux for the review and Deepak Dixit for the initial idea. > PaymentGatewayServices should be using ObjectType.simpleTypeConvert for all > amount variables > > > Key: OFBIZ-10811 > URL: https://issues.apache.org/jira/browse/OFBIZ-10811 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Suraj Khurana >Assignee: Suraj Khurana >Priority: Major > Fix For: Upcoming Branch > > Attachments: OFBIZ-10811.patch > > > Currently, it is direct typecasting into BigDecimal and it could throw > exception regarding string to BigDecimal typecasting. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-9084) Unit test case for service - setPaymentStatus
[ https://issues.apache.org/jira/browse/OFBIZ-9084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anushi Gupta reassigned OFBIZ-9084: --- Assignee: Anushi Gupta > Unit test case for service - setPaymentStatus > -- > > Key: OFBIZ-9084 > URL: https://issues.apache.org/jira/browse/OFBIZ-9084 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk >Reporter: Deepak Nigam >Assignee: Anushi Gupta >Priority: Minor > Attachments: OFBIZ-9084.patch > > > Unit test case for service - setPaymentStatus -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10660) Similar values reflecting twice on Add Action Type dropdown in Pricerule
[ https://issues.apache.org/jira/browse/OFBIZ-10660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prakhar Kumar reassigned OFBIZ-10660: - Assignee: Prakhar Kumar > Similar values reflecting twice on Add Action Type dropdown in Pricerule > > > Key: OFBIZ-10660 > URL: https://issues.apache.org/jira/browse/OFBIZ-10660 > Project: OFBiz > Issue Type: Bug > Environment: > https://demo-trunk.ofbiz.apache.org/catalog/control/createProductPriceCond >Reporter: Archana Asthana >Assignee: Prakhar Kumar >Priority: Major > Attachments: ActionTypeDropdown.png > > > Steps to Regenerate > 1. Open > https://demo-trunk.ofbiz.apache.org/catalog/control/createProductPriceCond > 2. Add the name for a new Price Rule > 3. Add Condition and go to Add Action panel > 4. Check the dropdown values under Action Type > *Actual: * > Same value reflecting twice in the dropdown ( Flat Amount Modify) > The Image is attached for reference -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-9522) User should be notified with success message on creating shopping list in ecommerce component
[ https://issues.apache.org/jira/browse/OFBIZ-9522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandrashekhar Dhakad reassigned OFBIZ-9522: Assignee: Chandrashekhar Dhakad > User should be notified with success message on creating shopping list in > ecommerce component > - > > Key: OFBIZ-9522 > URL: https://issues.apache.org/jira/browse/OFBIZ-9522 > Project: OFBiz > Issue Type: Sub-task > Components: ALL COMPONENTS >Reporter: Aditya Sharma >Assignee: Chandrashekhar Dhakad >Priority: Trivial > > Steps to regenerate: > 1. Login to Ecommerce component > (https://demo-trunk.ofbiz.apache.org/ecommerce/control/main). > 2. Go to > Shoppinglists.(https://localhost:8443/ecommerce/control/editShoppingList). > 3. Click on Create new. > 4. Fill all required fields and Click Save button > No success message on the successful action. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10895) Unknown request [images]; this request does not exist or cannot be called directly.
[
https://issues.apache.org/jira/browse/OFBIZ-10895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827458#comment-16827458
]
Deepak Dixit commented on OFBIZ-10895:
--
Hi Jacques,
I think we need to fix the image url in css file, it should start with /images,
else browser append this in request info. There is nothing related to java or
tomcat code.
> Unknown request [images]; this request does not exist or cannot be called
> directly.
> ---
>
> Key: OFBIZ-10895
> URL: https://issues.apache.org/jira/browse/OFBIZ-10895
> Project: OFBiz
> Issue Type: Bug
> Components: framework
>Affects Versions: Trunk, Release Branch 16.11, Release Branch 17.12,
> Release Branch 18.12
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Minor
> Fix For: 18.12.01
>
>
> This error happens in many occasions:
> Inside another request (here LookupProduct)
> {noformat}
> 2019-03-31 12:32:26,215 |jsse-nio-8443-exec-2 |ControlServlet
> |T| [[[LookupProduct(Domain:https://localhost)] Request Begun,
> encoding=[UTF-8]- total:0.0,since last(Begin):0.0]]
> 2019-03-31 12:32:26,222 |jsse-nio-8443-exec-7 |ControlServlet
> |T| [[[images(Domain:https://localhost)] Request Begun, encoding=[UTF-8]-
> total:0.0,since last(Begin):0.0]]
> 2019-03-31 12:32:26,222 |jsse-nio-8443-exec-7 |ControlServlet
> |E| Error in request handler:
> org.apache.ofbiz.webapp.control.RequestHandlerException: Unknown request
> [images]; this request does not exist or cannot be called directly.
> at
> org.apache.ofbiz.webapp.control.RequestHandler.doRequest(RequestHandler.java:277)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.control.ControlServlet.doGet(ControlServlet.java:212)
> [ofbiz.jar:?]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:645)
> [javax.servlet-api-4.0.1.jar:4.0.1]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:750)
> [javax.servlet-api-4.0.1.jar:4.0.1]
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
> [tomcat-embed-websocket-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.ofbiz.webapp.control.ContextFilter.doFilter(ContextFilter.java:191)
> [ofbiz.jar:?]
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.ofbiz.webapp.control.ControlFilter.doFilter(ControlFilter.java:156)
> [ofbiz.jar:?]
> at javax.servlet.http.HttpFilter.doFilter(HttpFilter.java:127)
> [javax.servlet-api-4.0.1.jar:4.0.1]
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:200)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:490)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:668)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343)
>
[jira] [Assigned] (OFBIZ-9747) Error while updating Agreement
[ https://issues.apache.org/jira/browse/OFBIZ-9747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sourabh jain reassigned OFBIZ-9747: --- Assignee: sourabh jain > Error while updating Agreement > --- > > Key: OFBIZ-9747 > URL: https://issues.apache.org/jira/browse/OFBIZ-9747 > Project: OFBiz > Issue Type: Bug > Components: accounting > Environment: > https://demo-trunk.ofbiz.apache.org/accounting/control/updateAgreement >Reporter: Padmavati Rawat >Assignee: sourabh jain >Priority: Major > Attachments: ErroronAgreement.png > > > Steps: > 1. Search any existing Agreement. > 2. Click on the update button. > 3. Try to change the Role Type Id From, Role Type Id To and Agreement Type Id. > 4. Click on submit button. > Actual: > Error displayed on the screen on clicking submit button. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10887) Improve UX of the compareProducts page in the eCommerce store
[ https://issues.apache.org/jira/browse/OFBIZ-10887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sasikant Biswal reassigned OFBIZ-10887: --- Assignee: Sasikant Biswal > Improve UX of the compareProducts page in the eCommerce store > - > > Key: OFBIZ-10887 > URL: https://issues.apache.org/jira/browse/OFBIZ-10887 > Project: OFBiz > Issue Type: Improvement > Components: ecommerce >Reporter: Chandrashekhar Dhakad >Assignee: Sasikant Biswal >Priority: Minor > Attachments: CompareProducts1.png, CompareProducts2.png, > CompareProducts3.png, CompareProducts4.png, CompareProducts5.png, > CompareProducts6.png > > > *Steps:* > 1) Open URL: [https://demo-trunk.ofbiz.apache.org/ecommerce/control/main] > 2) Click on the Add To Compare link for any product(refer the screenshot > CompareProducts1.png). > 3) Click on the Compare Products button in the Compare Products section(refer > the screenshot CompareProducts2.png). > 4) Click on the Add to Cart link on the *CompareProducts* page(refer the > screenshot CompareProducts3.png). > 5) Again click on the Add to Cart link on the *add item* page(refer the > screenshot CompareProducts4.png). > 6) Click on the back button of the browser and verify the cart without > refreshing the page(refer the screenshot CompareProducts5.png). > 7) Then refresh the page and check the cart(refer the screenshot > CompareProducts6.png). > > *Actual:* > The cart is not updated without refreshing the page whenever the user clicks > on the browser's back button from the add item page. > *Suggestions:* > 1) There should be a link on the *add item* page to navigate to the home page > so that the user will not have to click on the browser's back button and the > cart also will be updated properly without refreshing the page. > 2) A success message should be displayed while clicking on the Add to Cart > link. > > Please provide more suggestions or other opinions for the same. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10775) Remove 'PageTitle' from label and occurrences
[ https://issues.apache.org/jira/browse/OFBIZ-10775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sourabh jain reassigned OFBIZ-10775: Assignee: sourabh jain > Remove 'PageTitle' from label and occurrences > - > > Key: OFBIZ-10775 > URL: https://issues.apache.org/jira/browse/OFBIZ-10775 > Project: OFBiz > Issue Type: Sub-task > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: sourabh jain >Priority: Minor > > This also include occurrences in screenlet, label and other widgets and > templates -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10774) Remove 'FormFieldTitle_' requirement in FrameWork code
[ https://issues.apache.org/jira/browse/OFBIZ-10774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sourabh jain reassigned OFBIZ-10774: Assignee: sourabh jain > Remove 'FormFieldTitle_' requirement in FrameWork code > -- > > Key: OFBIZ-10774 > URL: https://issues.apache.org/jira/browse/OFBIZ-10774 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Reporter: Pierre Smits >Assignee: sourabh jain >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OFBIZ-5402) Incorrect contact information displayed on purchase order view page
[ https://issues.apache.org/jira/browse/OFBIZ-5402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suraj Khurana closed OFBIZ-5402. Thanks Christian Carlow for reporting, Prakhar Kumar for the patch and everyone else for discussions and suggestions. > Incorrect contact information displayed on purchase order view page > --- > > Key: OFBIZ-5402 > URL: https://issues.apache.org/jira/browse/OFBIZ-5402 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk >Reporter: Christian Carlow >Assignee: Suraj Khurana >Priority: Trivial > Fix For: Upcoming Branch > > Attachments: OFBIZ-5402.patch, OFBiz-5402-UX-Improvement.png > > > Ship group destinations are listed in the contact information screen on the > purchase order view page but the party is set to the supplier. It seems like > the address information listed should relate to the party of the screen, so > the supplier contact information should probably appear. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-9533) User should be notified with success message on MRP run in manufacturing component
[ https://issues.apache.org/jira/browse/OFBIZ-9533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Humera Khan reassigned OFBIZ-9533: -- Assignee: Humera Khan > User should be notified with success message on MRP run in manufacturing > component > -- > > Key: OFBIZ-9533 > URL: https://issues.apache.org/jira/browse/OFBIZ-9533 > Project: OFBiz > Issue Type: Sub-task > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Aditya Sharma >Assignee: Humera Khan >Priority: Trivial > > Steps to regenerate: > 1. Go to Manufacturing component > (https://demo-trunk.ofbiz.apache.org/manufacturing/control/main) > 2. Click on Mrp sub menu > (https://demo-trunk.ofbiz.apache.org/manufacturing/control/FindInventoryEventPlan) > 3. Click on Run Mrp > button.(https://demo-trunk.ofbiz.apache.org/manufacturing/control/RunMrp) > 4. Select Facility/Facility Group and Click Submit button. > On success, the user should be notified with success message like "Mrp run is > scheduled". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10518: - Attachment: (was: OFBiz-10518.patch) > 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] [Updated] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10518: - Attachment: OFBiz-10518.patch > 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] [Updated] (OFBIZ-10891) Send me this every month link is not working in order items section.
[ https://issues.apache.org/jira/browse/OFBIZ-10891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Sharma updated OFBIZ-10891: -- Attachment: OFBIZ-10891.png > Send me this every month link is not working in order items section. > > > Key: OFBIZ-10891 > URL: https://issues.apache.org/jira/browse/OFBIZ-10891 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Ashish Sharma >Priority: Minor > Attachments: OFBIZ-10891.png > > > *Steps to Reproduce* > 1. Login with valid username and password. > 2. Navigate to ecommerce. > 3. Place a order. > 4. Navigate to order history and click on view link. > 5. Click on link “send me this every month” in order items section. > *Actual Result:* Error message is displayed. > *Screen print attached* -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10518: - Attachment: (was: OFBiz-10518-services.patch) > 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] [Updated] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10518: - Attachment: OFBiz-10518-services.patch > 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-10885) Blank page appears after using Tell-A-Friend functionality while adding item to cart
[ https://issues.apache.org/jira/browse/OFBIZ-10885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitish Mishra reassigned OFBIZ-10885: - Assignee: Nitish Mishra > Blank page appears after using Tell-A-Friend functionality while adding item > to cart > > > Key: OFBIZ-10885 > URL: https://issues.apache.org/jira/browse/OFBIZ-10885 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Trunk >Reporter: Ravi Lodhi >Assignee: Nitish Mishra >Priority: Minor > > Steps to reproduce: > 1) Go to [https://demo-trunk.ofbiz.apache.org/ecomseo > ]2) Click on any products from the Popular categories section. I clicked on > Tiny Gizmo. > 3) You will be redirected to the product detail page. You can see a link > "Tell-A-Friend" just below the product's pricing detail. > 4) Click on "Tell-A-Friend" link. A model will appear. Fill the necessary > detail and submit the form. > 5) Now add that item into the cart by clicking the "Add To Cart" button. > 6) A blank page with a message "Tell A Friend Sorry" appears. > Expected: User should be redirected to the same product detail page after > successfully adding an item. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-9579) Required field indicator (*) is missing on some forms
[ https://issues.apache.org/jira/browse/OFBIZ-9579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sasikant Biswal reassigned OFBIZ-9579: -- Assignee: (was: Sasikant Biswal) > Required field indicator (*) is missing on some forms > - > > Key: OFBIZ-9579 > URL: https://issues.apache.org/jira/browse/OFBIZ-9579 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Jacques Le Roux >Priority: Trivial > > This is an umbrella issue, work to be done in sub-tasks or here if it's only > in one form -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10921) Marital Status not managed properly in Person entity
[ https://issues.apache.org/jira/browse/OFBIZ-10921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827446#comment-16827446 ] Suraj Khurana commented on OFBIZ-10921: --- Thanks Jacques and Nicolas for your inputs. I have added the updated patch for the same. Please have a look. > Marital Status not managed properly in Person entity > > > Key: OFBIZ-10921 > URL: https://issues.apache.org/jira/browse/OFBIZ-10921 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Trunk >Reporter: Suraj Khurana >Assignee: Suraj Khurana >Priority: Major > Attachments: OFBIZ-10921.patch, OFBIZ-10921.patch > > > Currently, *maritalStatus* is managed as an indicator (Y/N) in *Person* > entity. I think we can enhance it and make it derived from *Enumeration* > pattern. > > *Classification of legal marital status* > > - 1 - Married (and not separated) ... > - 2 - Widowed (including living common law) ... > - 3 - Separated (and not Divorced) ... > - 4 - Divorced (including living common law) ... > - 5 - Single (including living common law) > Please refer discussion over ML: > [https://markmail.org/message/5b33qm3osy76if24] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10921) Marital Status not managed properly in Person entity
[ https://issues.apache.org/jira/browse/OFBIZ-10921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suraj Khurana updated OFBIZ-10921: -- Attachment: OFBIZ-10921.patch > Marital Status not managed properly in Person entity > > > Key: OFBIZ-10921 > URL: https://issues.apache.org/jira/browse/OFBIZ-10921 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Trunk >Reporter: Suraj Khurana >Assignee: Suraj Khurana >Priority: Major > Attachments: OFBIZ-10921.patch, OFBIZ-10921.patch > > > Currently, *maritalStatus* is managed as an indicator (Y/N) in *Person* > entity. I think we can enhance it and make it derived from *Enumeration* > pattern. > > *Classification of legal marital status* > > - 1 - Married (and not separated) ... > - 2 - Widowed (including living common law) ... > - 3 - Separated (and not Divorced) ... > - 4 - Divorced (including living common law) ... > - 5 - Single (including living common law) > Please refer discussion over ML: > [https://markmail.org/message/5b33qm3osy76if24] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10705) Replace DateFormat and Simple DateFormat by FastDateFormat
[ https://issues.apache.org/jira/browse/OFBIZ-10705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kumar Rahul reassigned OFBIZ-10705: --- Assignee: Kumar Rahul > Replace DateFormat and Simple DateFormat by FastDateFormat > --- > > Key: OFBIZ-10705 > URL: https://issues.apache.org/jira/browse/OFBIZ-10705 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Kumar Rahul >Priority: Minor > > This is a performance improvement and was suggested by [Adrian 6 years > ago|https://markmail.org/message/zbuaef7aaueij5w2] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-9611) Documentation: Accounts Payable (AP) User Stories, Use Cases and Test Cases
[ https://issues.apache.org/jira/browse/OFBIZ-9611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Humera Khan reassigned OFBIZ-9611: -- Assignee: (was: Humera Khan) > Documentation: Accounts Payable (AP) User Stories, Use Cases and Test Cases > --- > > Key: OFBIZ-9611 > URL: https://issues.apache.org/jira/browse/OFBIZ-9611 > Project: OFBiz > Issue Type: Sub-task >Reporter: Shivangi Tanwar >Priority: Major > Labels: Accounts, BPRB, OBPRB, Payable > > Accounts Payable business process user stories, use cases and test cases to > be documented. > *Doc Content:* > Every AP business activity to be covered under below-given headings- > - User Story (Write, if doesn't exist already OR review and refine as > required) > - Use Cases (Write, if don't exist already OR review and refine as required) > - Test Cases (Write, if don't exist already OR review and refine as required. > Verify every test case and mark it with appropriate status- PASS, FAIL). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-9610) Documentation: Accounts Payable(AP) Process Overview
[ https://issues.apache.org/jira/browse/OFBIZ-9610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Humera Khan reassigned OFBIZ-9610: -- Assignee: (was: Humera Khan) > Documentation: Accounts Payable(AP) Process Overview > > > Key: OFBIZ-9610 > URL: https://issues.apache.org/jira/browse/OFBIZ-9610 > Project: OFBiz > Issue Type: Sub-task >Reporter: Shivangi Tanwar >Priority: Major > Labels: Accounts, BPRB, OBPRB, Payable > > Accounts Payable process overview to be documented. > *Doc Content* > Every AP business activity to be covered with below-given headings- > - Process Overview > - Business Purpose (significance of having efficient Accounts Payable > capabilities in real world) > - Activity Diagrams (Level-1,2, and 3 as applicable to demonstrate the > process flow) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10518: - Attachment: (was: OFBiz-10518-entity-model.patch) > 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] [Commented] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827441#comment-16827441 ] Deepak Nigam commented on OFBIZ-10518: -- Updated the patches wrt latest codebase of trunk. > 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-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-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10518: - Attachment: OFBiz-10518-entity-model.patch > 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-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] [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=16827440#comment-16827440 ] Pawan Verma commented on OFBIZ-10904: - Hey [~jacques.le.roux], I have retested my patch and it is working fine on my end, I have tested it on Trunk and release branch. [~pfm.smits], Any update from your side, Did you get time to test it again? > 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] [Assigned] (OFBIZ-9579) Required field indicator (*) is missing on some forms
[ https://issues.apache.org/jira/browse/OFBIZ-9579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sasikant Biswal reassigned OFBIZ-9579: -- Assignee: Sasikant Biswal > Required field indicator (*) is missing on some forms > - > > Key: OFBIZ-9579 > URL: https://issues.apache.org/jira/browse/OFBIZ-9579 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Sasikant Biswal >Priority: Trivial > > This is an umbrella issue, work to be done in sub-tasks or here if it's only > in one form -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (OFBIZ-10936) Java code contains unnecessary semicolons
[ https://issues.apache.org/jira/browse/OFBIZ-10936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827182#comment-16827182 ] Jacques Le Roux edited comment on OFBIZ-10936 at 4/26/19 6:54 PM: -- Oops in previous commit missed that OFBizPricatUtil is a Java not a Groovy file :/ Fixed at r1858223 was (Author: jacques.le.roux): Oops in previous commit missed that OFBizPricatUtil a Java not Groovy file :/ Fixed at r1858223 > Java code contains unnecessary semicolons > - > > Key: OFBIZ-10936 > URL: https://issues.apache.org/jira/browse/OFBIZ-10936 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Trunk >Reporter: Mathieu Lirzin >Assignee: Mathieu Lirzin >Priority: Trivial > Fix For: Upcoming Branch > > Attachments: > OFBIZ-10936_Remove-unnecessary-semicolons-in-Java-code.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (OFBIZ-10936) Java code contains unnecessary semicolons
[ https://issues.apache.org/jira/browse/OFBIZ-10936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827182#comment-16827182 ] Jacques Le Roux edited comment on OFBIZ-10936 at 4/26/19 6:52 PM: -- Oops in previous commit missed that OFBizPricatUtil a Java not Groovy file :/ Fixed at r1858223 was (Author: jacques.le.roux): Thanks Mathieu, At revision: 1858220 I also removed them in Groovy (no semicolons at all there) > Java code contains unnecessary semicolons > - > > Key: OFBIZ-10936 > URL: https://issues.apache.org/jira/browse/OFBIZ-10936 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Trunk >Reporter: Mathieu Lirzin >Assignee: Mathieu Lirzin >Priority: Trivial > Fix For: Upcoming Branch > > Attachments: > OFBIZ-10936_Remove-unnecessary-semicolons-in-Java-code.patch > > -- 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=16827199#comment-16827199 ] Jacques Le Roux commented on OFBIZ-10904: - Hi Guys, Any update? > 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-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=16827195#comment-16827195 ] Jacques Le Roux commented on OFBIZ-10949: - Hi Pierre, I don't get it, could you explain more please, maybe images? > 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: OFBIZ-10949-accounting.patch > > > 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] [Commented] (OFBIZ-10938) Unnecessary declared exceptions should be removed
[ https://issues.apache.org/jira/browse/OFBIZ-10938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827193#comment-16827193 ] Jacques Le Roux commented on OFBIZ-10938: - Ah, I see now it contains OFBIZ-10091, sorry for the noise :) > Unnecessary declared exceptions should be removed > - > > Key: OFBIZ-10938 > URL: https://issues.apache.org/jira/browse/OFBIZ-10938 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Mathieu Lirzin >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-10938_ContainerException.patch, > OFBIZ-10938_RequestHandlerTests.patch > > > There are multiple places in the framework where exceptions are declared even > when they shouldn't. > Eclipse static analysis tool currently detects 1504 occurrences of those > mistakenly declared thrown exceptions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10955) field type Integer is missing in definitions
[ https://issues.apache.org/jira/browse/OFBIZ-10955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827190#comment-16827190 ] Jacques Le Roux commented on OFBIZ-10955: - Hi Pierre, There is a typo in your patch:"INTEGEr". Moreover, should we define all possible types: https://docs.oracle.com/javase/7/docs/api/java/sql/Types.html ? I wonder why only BigInt was defined "initially" > field type Integer is missing in definitions > > > Key: OFBIZ-10955 > URL: https://issues.apache.org/jira/browse/OFBIZ-10955 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk, Release Branch 16.11, Release Branch 17.12, > Release Branch 18.12 >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Attachments: OFBIZ-10955.patch > > > The field type for integer values is missing in definitions for various RDBMS > variants -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10955) field type Integer is missing in definitions
[ https://issues.apache.org/jira/browse/OFBIZ-10955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-10955: Summary: field type Integer is missing in definitions (was: field type Integer is mission in definitions) > field type Integer is missing in definitions > > > Key: OFBIZ-10955 > URL: https://issues.apache.org/jira/browse/OFBIZ-10955 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk, Release Branch 16.11, Release Branch 17.12, > Release Branch 18.12 >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > Attachments: OFBIZ-10955.patch > > > The field type for integer values is missing in definitions for various RDBMS > variants -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10938) Unnecessary declared exceptions should be removed
[ https://issues.apache.org/jira/browse/OFBIZ-10938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827185#comment-16827185 ] Jacques Le Roux commented on OFBIZ-10938: - Hi Mathieu, Is that done? Should we close? > Unnecessary declared exceptions should be removed > - > > Key: OFBIZ-10938 > URL: https://issues.apache.org/jira/browse/OFBIZ-10938 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Mathieu Lirzin >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-10938_ContainerException.patch, > OFBIZ-10938_RequestHandlerTests.patch > > > There are multiple places in the framework where exceptions are declared even > when they shouldn't. > Eclipse static analysis tool currently detects 1504 occurrences of those > mistakenly declared thrown exceptions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OFBIZ-10937) Redundant types declarations should be removed
[ https://issues.apache.org/jira/browse/OFBIZ-10937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-10937. --- > Redundant types declarations should be removed > -- > > Key: OFBIZ-10937 > URL: https://issues.apache.org/jira/browse/OFBIZ-10937 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Mathieu Lirzin >Assignee: Mathieu Lirzin >Priority: Trivial > Fix For: Upcoming Branch > > Attachments: > OFBIZ-10937_Redundant-specification-of-type-arguments.patch > > > Since Java 1.7, when defining generic types it is unnecessary to redefine > those types in the constructor when it is already done in the declared type. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10937) Redundant types declarations should be removed
[ https://issues.apache.org/jira/browse/OFBIZ-10937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-10937: Fix Version/s: (was: Trunk) Upcoming Branch > Redundant types declarations should be removed > -- > > Key: OFBIZ-10937 > URL: https://issues.apache.org/jira/browse/OFBIZ-10937 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Mathieu Lirzin >Assignee: Mathieu Lirzin >Priority: Trivial > Fix For: Upcoming Branch > > Attachments: > OFBIZ-10937_Redundant-specification-of-type-arguments.patch > > > Since Java 1.7, when defining generic types it is unnecessary to redefine > those types in the constructor when it is already done in the declared type. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OFBIZ-10936) Java code contains unnecessary semicolons
[ https://issues.apache.org/jira/browse/OFBIZ-10936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-10936. --- Thanks Mathieu, At revision: 1858220 I also removed them in Groovy (no semicolons at all there) > Java code contains unnecessary semicolons > - > > Key: OFBIZ-10936 > URL: https://issues.apache.org/jira/browse/OFBIZ-10936 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Trunk >Reporter: Mathieu Lirzin >Assignee: Mathieu Lirzin >Priority: Trivial > Fix For: Upcoming Branch > > Attachments: > OFBIZ-10936_Remove-unnecessary-semicolons-in-Java-code.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (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=16827181#comment-16827181 ] Jacques Le Roux edited comment on OFBIZ-10935 at 4/26/19 6:13 PM: -- Hi Mathieu, For the sake of the blog but mostly releasing: we use Upcoming Branch in Fix version field, please refer to https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Committers+Roles+and+Responsibilities#OFBizCommittersRolesandResponsibilities-ManageJIRA%27sissues, thanks was (Author: jacques.le.roux): Hi Mathieu, For the sake of the blog but mostly releasing: we use Upcoming Branch in Fix version field, please refer to https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Committers+Roles+and+Responsibilities#OFBizCommittersRolesandResponsibilities-ManageJIRA%27sissues > 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] [Updated] (OFBIZ-10911) Redundant null checks should be removed
[ https://issues.apache.org/jira/browse/OFBIZ-10911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-10911: Fix Version/s: (was: Trunk) > Redundant null checks should be removed > --- > > Key: OFBIZ-10911 > URL: https://issues.apache.org/jira/browse/OFBIZ-10911 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Mathieu Lirzin >Assignee: Mathieu Lirzin >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-10911_Remove-redundant-null-checks.patch > > > Redundant null checks are detected by Eclipse statically. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10935) Do not use deprecated method in ‘DBCPConnectionFactory’
[ https://issues.apache.org/jira/browse/OFBIZ-10935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-10935: Fix Version/s: (was: Trunk) Upcoming Branch Hi Mathieu, For the sake of the blog but mostly releasing: we use Upcoming Branch in Fix version field, please refer to https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Committers+Roles+and+Responsibilities#OFBizCommittersRolesandResponsibilities-ManageJIRA%27sissues > 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] [Updated] (OFBIZ-10911) Redundant null checks should be removed
[ https://issues.apache.org/jira/browse/OFBIZ-10911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-10911: Fix Version/s: Upcoming Branch > Redundant null checks should be removed > --- > > Key: OFBIZ-10911 > URL: https://issues.apache.org/jira/browse/OFBIZ-10911 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Mathieu Lirzin >Assignee: Mathieu Lirzin >Priority: Minor > Fix For: Trunk, Upcoming Branch > > Attachments: OFBIZ-10911_Remove-redundant-null-checks.patch > > > Redundant null checks are detected by Eclipse statically. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10936) Java code contains unnecessary semicolons
[ https://issues.apache.org/jira/browse/OFBIZ-10936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-10936: Fix Version/s: (was: Trunk) Upcoming Branch > Java code contains unnecessary semicolons > - > > Key: OFBIZ-10936 > URL: https://issues.apache.org/jira/browse/OFBIZ-10936 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Trunk >Reporter: Mathieu Lirzin >Assignee: Mathieu Lirzin >Priority: Trivial > Fix For: Upcoming Branch > > Attachments: > OFBIZ-10936_Remove-unnecessary-semicolons-in-Java-code.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OFBIZ-10935) Do not use deprecated method in ‘DBCPConnectionFactory’
[ https://issues.apache.org/jira/browse/OFBIZ-10935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-10935. --- > 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: Trunk > > 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-10911) Redundant null checks should be removed
[ https://issues.apache.org/jira/browse/OFBIZ-10911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-10911. --- This seems OK to me, closing > Redundant null checks should be removed > --- > > Key: OFBIZ-10911 > URL: https://issues.apache.org/jira/browse/OFBIZ-10911 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Mathieu Lirzin >Assignee: Mathieu Lirzin >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-10911_Remove-redundant-null-checks.patch > > > Redundant null checks are detected by Eclipse statically. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10895) Unknown request [images]; this request does not exist or cannot be called directly.
[
https://issues.apache.org/jira/browse/OFBIZ-10895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827124#comment-16827124
]
Jacques Le Roux commented on OFBIZ-10895:
-
OK, this is hard to debug. If we refer to the stack trace in the description,
already at
{noformat}
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:408)
[tomcat-coyote-9.0.16.jar:9.0.16]
{noformat}
the request contains the URL {{/ordermgr/control/images/cal.gif}}. So it seems
it has nothing to do with Java code changes in OFBiz but maybe a Tomcat, or
related, configuration change. With versions previous to R17 this request does
not exist.
It would be easy to caught all URLs containing {{/control/images/}} and avoid
logging an error message. But again it would hide the reason which is yet not
clear to me, to say the least.
> Unknown request [images]; this request does not exist or cannot be called
> directly.
> ---
>
> Key: OFBIZ-10895
> URL: https://issues.apache.org/jira/browse/OFBIZ-10895
> Project: OFBiz
> Issue Type: Bug
> Components: framework
>Affects Versions: Trunk, Release Branch 16.11, Release Branch 17.12,
> Release Branch 18.12
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Minor
> Fix For: 18.12.01
>
>
> This error happens in many occasions:
> Inside another request (here LookupProduct)
> {noformat}
> 2019-03-31 12:32:26,215 |jsse-nio-8443-exec-2 |ControlServlet
> |T| [[[LookupProduct(Domain:https://localhost)] Request Begun,
> encoding=[UTF-8]- total:0.0,since last(Begin):0.0]]
> 2019-03-31 12:32:26,222 |jsse-nio-8443-exec-7 |ControlServlet
> |T| [[[images(Domain:https://localhost)] Request Begun, encoding=[UTF-8]-
> total:0.0,since last(Begin):0.0]]
> 2019-03-31 12:32:26,222 |jsse-nio-8443-exec-7 |ControlServlet
> |E| Error in request handler:
> org.apache.ofbiz.webapp.control.RequestHandlerException: Unknown request
> [images]; this request does not exist or cannot be called directly.
> at
> org.apache.ofbiz.webapp.control.RequestHandler.doRequest(RequestHandler.java:277)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.control.ControlServlet.doGet(ControlServlet.java:212)
> [ofbiz.jar:?]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:645)
> [javax.servlet-api-4.0.1.jar:4.0.1]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:750)
> [javax.servlet-api-4.0.1.jar:4.0.1]
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
> [tomcat-embed-websocket-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.ofbiz.webapp.control.ContextFilter.doFilter(ContextFilter.java:191)
> [ofbiz.jar:?]
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.ofbiz.webapp.control.ControlFilter.doFilter(ControlFilter.java:156)
> [ofbiz.jar:?]
> at javax.servlet.http.HttpFilter.doFilter(HttpFilter.java:127)
> [javax.servlet-api-4.0.1.jar:4.0.1]
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:200)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:490)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
>
[jira] [Commented] (OFBIZ-10093) Replace ELRTE plugin with Quill.
[ https://issues.apache.org/jira/browse/OFBIZ-10093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827043#comment-16827043 ] Jacques Le Roux commented on OFBIZ-10093: - Thanks Aditya > Replace ELRTE plugin with Quill. > > > Key: OFBIZ-10093 > URL: https://issues.apache.org/jira/browse/OFBIZ-10093 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: Aditya Sharma >Assignee: Aditya Sharma >Priority: Major > > As there is no support for elrte since elrte-1.3 > [https://github.com/Studio-42/elRTE] it is to be replaced with some other > good editor & we found Quill Js editor as quite suitable: > * 139 releases > * Good community support of 101 contributors > * Licence - BSD 3-Clause "New" or "Revised" License > Links for reference: > [https://quilljs.com/] > [https://github.com/quilljs/quill] > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (OFBIZ-10895) Unknown request [images]; this request does not exist or cannot be called directly.
[
https://issues.apache.org/jira/browse/OFBIZ-10895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827028#comment-16827028
]
Jacques Le Roux edited comment on OFBIZ-10895 at 4/26/19 3:10 PM:
--
I compared the block around requestMissingErrorMessage between R15 and R16 and
they are the same. Moreover there is no error in R16 for
ordermgr/control/request. The only error I could spot is
{noformat}
2019-04-26 16:18:33,888 |jsse-nio-8459-exec-6 |ControlServlet
|E| Error in request handler:
org.apache.ofbiz.webapp.control.RequestHandlerException: Unknown request
[d.png]; this request does not exist or cannot be called directly.
at
org.apache.ofbiz.webapp.control.RequestHandler.doRequest(RequestHandler.java:196)
~[ofbiz.jar:?]
at
org.apache.ofbiz.webapp.control.ControlServlet.doGet(ControlServlet.java:210)
[ofbiz.jar:?]
{noformat}
I was unable to find to what it relates exactly (unable to reproduce actually).
I'll neglect it for now and only focus on the images URL issue which is only
present since R17
was (Author: jacques.le.roux):
I compared the block around requestMissingErrorMessage between R15 and R16 and
they are the same. Moreover there is no error in R16 for
ordermgr/control/request. The only error I could spot is
{noformat}
2019-04-26 16:18:33,888 |jsse-nio-8459-exec-6 |ControlServlet
|E| Error in request handler:
org.apache.ofbiz.webapp.control.RequestHandlerException: Unknown request
[d.png]; this request does not exist or cannot be called directly.
at
org.apache.ofbiz.webapp.control.RequestHandler.doRequest(RequestHandler.java:196)
~[ofbiz.jar:?]
at
org.apache.ofbiz.webapp.control.ControlServlet.doGet(ControlServlet.java:210)
[ofbiz.jar:?]
{noformat}
I was unable to find to what it relates exactly (unable to reproduce actually)
and I'll neglect it for now and only focus on the images URL issue.
> Unknown request [images]; this request does not exist or cannot be called
> directly.
> ---
>
> Key: OFBIZ-10895
> URL: https://issues.apache.org/jira/browse/OFBIZ-10895
> Project: OFBiz
> Issue Type: Bug
> Components: framework
>Affects Versions: Trunk, Release Branch 16.11, Release Branch 17.12,
> Release Branch 18.12
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Minor
> Fix For: 18.12.01
>
>
> This error happens in many occasions:
> Inside another request (here LookupProduct)
> {noformat}
> 2019-03-31 12:32:26,215 |jsse-nio-8443-exec-2 |ControlServlet
> |T| [[[LookupProduct(Domain:https://localhost)] Request Begun,
> encoding=[UTF-8]- total:0.0,since last(Begin):0.0]]
> 2019-03-31 12:32:26,222 |jsse-nio-8443-exec-7 |ControlServlet
> |T| [[[images(Domain:https://localhost)] Request Begun, encoding=[UTF-8]-
> total:0.0,since last(Begin):0.0]]
> 2019-03-31 12:32:26,222 |jsse-nio-8443-exec-7 |ControlServlet
> |E| Error in request handler:
> org.apache.ofbiz.webapp.control.RequestHandlerException: Unknown request
> [images]; this request does not exist or cannot be called directly.
> at
> org.apache.ofbiz.webapp.control.RequestHandler.doRequest(RequestHandler.java:277)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.control.ControlServlet.doGet(ControlServlet.java:212)
> [ofbiz.jar:?]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:645)
> [javax.servlet-api-4.0.1.jar:4.0.1]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:750)
> [javax.servlet-api-4.0.1.jar:4.0.1]
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
> [tomcat-embed-websocket-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.ofbiz.webapp.control.ContextFilter.doFilter(ContextFilter.java:191)
> [ofbiz.jar:?]
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
>
[jira] [Commented] (OFBIZ-10895) Unknown request [images]; this request does not exist or cannot be called directly.
[
https://issues.apache.org/jira/browse/OFBIZ-10895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827028#comment-16827028
]
Jacques Le Roux commented on OFBIZ-10895:
-
I compared the block around requestMissingErrorMessage between R15 and R16 and
they are the same. Moreover there is no error in R16 for
ordermgr/control/request. The only error I could spot is
{noformat}
2019-04-26 16:18:33,888 |jsse-nio-8459-exec-6 |ControlServlet
|E| Error in request handler:
org.apache.ofbiz.webapp.control.RequestHandlerException: Unknown request
[d.png]; this request does not exist or cannot be called directly.
at
org.apache.ofbiz.webapp.control.RequestHandler.doRequest(RequestHandler.java:196)
~[ofbiz.jar:?]
at
org.apache.ofbiz.webapp.control.ControlServlet.doGet(ControlServlet.java:210)
[ofbiz.jar:?]
{noformat}
I was unable to find to what it relates exactly (unable to reproduce actually)
and I'll neglect it for now and only focus on the images URL issue.
> Unknown request [images]; this request does not exist or cannot be called
> directly.
> ---
>
> Key: OFBIZ-10895
> URL: https://issues.apache.org/jira/browse/OFBIZ-10895
> Project: OFBiz
> Issue Type: Bug
> Components: framework
>Affects Versions: Trunk, Release Branch 16.11, Release Branch 17.12,
> Release Branch 18.12
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Minor
> Fix For: 18.12.01
>
>
> This error happens in many occasions:
> Inside another request (here LookupProduct)
> {noformat}
> 2019-03-31 12:32:26,215 |jsse-nio-8443-exec-2 |ControlServlet
> |T| [[[LookupProduct(Domain:https://localhost)] Request Begun,
> encoding=[UTF-8]- total:0.0,since last(Begin):0.0]]
> 2019-03-31 12:32:26,222 |jsse-nio-8443-exec-7 |ControlServlet
> |T| [[[images(Domain:https://localhost)] Request Begun, encoding=[UTF-8]-
> total:0.0,since last(Begin):0.0]]
> 2019-03-31 12:32:26,222 |jsse-nio-8443-exec-7 |ControlServlet
> |E| Error in request handler:
> org.apache.ofbiz.webapp.control.RequestHandlerException: Unknown request
> [images]; this request does not exist or cannot be called directly.
> at
> org.apache.ofbiz.webapp.control.RequestHandler.doRequest(RequestHandler.java:277)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.control.ControlServlet.doGet(ControlServlet.java:212)
> [ofbiz.jar:?]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:645)
> [javax.servlet-api-4.0.1.jar:4.0.1]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:750)
> [javax.servlet-api-4.0.1.jar:4.0.1]
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
> [tomcat-embed-websocket-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.ofbiz.webapp.control.ContextFilter.doFilter(ContextFilter.java:191)
> [ofbiz.jar:?]
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.ofbiz.webapp.control.ControlFilter.doFilter(ControlFilter.java:156)
> [ofbiz.jar:?]
> at javax.servlet.http.HttpFilter.doFilter(HttpFilter.java:127)
> [javax.servlet-api-4.0.1.jar:4.0.1]
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:200)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:490)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
>
[jira] [Commented] (OFBIZ-10921) Marital Status not managed properly in Person entity
[ https://issues.apache.org/jira/browse/OFBIZ-10921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826995#comment-16826995 ] Jacques Le Roux commented on OFBIZ-10921: - Yes thanks Nicolas, Please Suraj refer to https://cwiki.apache.org/confluence/display/OFBIZ/General+Entity+Overview#GeneralEntityOverview-DeprecatedEntities, thanks. > Marital Status not managed properly in Person entity > > > Key: OFBIZ-10921 > URL: https://issues.apache.org/jira/browse/OFBIZ-10921 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Trunk >Reporter: Suraj Khurana >Assignee: Suraj Khurana >Priority: Major > Attachments: OFBIZ-10921.patch > > > Currently, *maritalStatus* is managed as an indicator (Y/N) in *Person* > entity. I think we can enhance it and make it derived from *Enumeration* > pattern. > > *Classification of legal marital status* > > - 1 - Married (and not separated) ... > - 2 - Widowed (including living common law) ... > - 3 - Separated (and not Divorced) ... > - 4 - Divorced (including living common law) ... > - 5 - Single (including living common law) > Please refer discussion over ML: > [https://markmail.org/message/5b33qm3osy76if24] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10720) How to integrate OfBiz framework with spring micro service
[ https://issues.apache.org/jira/browse/OFBIZ-10720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826952#comment-16826952 ] Swapnil M Mane commented on OFBIZ-10720: Hi [~vemulabujji] , I am closing this ticket. As mentioned above, please use mailing list to ask your questions. Thanks! > How to integrate OfBiz framework with spring micro service > -- > > Key: OFBIZ-10720 > URL: https://issues.apache.org/jira/browse/OFBIZ-10720 > Project: OFBiz > Issue Type: Bug > Components: ALL APPLICATIONS >Affects Versions: 16.11.05 >Reporter: Bojjanna >Assignee: Swapnil M Mane >Priority: Major > > Dear, > I would like to integrate the OfBiz framework with Spring micro service. > Please help to provide best solution,how i can invoke the OfBiz server from > my application. > > Thanks > Vemula > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OFBIZ-10720) How to integrate OfBiz framework with spring micro service
[ https://issues.apache.org/jira/browse/OFBIZ-10720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil M Mane closed OFBIZ-10720. -- Resolution: Invalid > How to integrate OfBiz framework with spring micro service > -- > > Key: OFBIZ-10720 > URL: https://issues.apache.org/jira/browse/OFBIZ-10720 > Project: OFBiz > Issue Type: Bug > Components: ALL APPLICATIONS >Affects Versions: 16.11.05 >Reporter: Bojjanna >Assignee: Swapnil M Mane >Priority: Major > > Dear, > I would like to integrate the OfBiz framework with Spring micro service. > Please help to provide best solution,how i can invoke the OfBiz server from > my application. > > Thanks > Vemula > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10720) How to integrate OfBiz framework with spring micro service
[ https://issues.apache.org/jira/browse/OFBIZ-10720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil M Mane reassigned OFBIZ-10720: -- Assignee: Swapnil M Mane > How to integrate OfBiz framework with spring micro service > -- > > Key: OFBIZ-10720 > URL: https://issues.apache.org/jira/browse/OFBIZ-10720 > Project: OFBiz > Issue Type: Bug > Components: ALL APPLICATIONS >Affects Versions: 16.11.05 >Reporter: Bojjanna >Assignee: Swapnil M Mane >Priority: Major > > Dear, > I would like to integrate the OfBiz framework with Spring micro service. > Please help to provide best solution,how i can invoke the OfBiz server from > my application. > > Thanks > Vemula > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10237) The leads which are converted is displayed on the Find lead page.
[ https://issues.apache.org/jira/browse/OFBIZ-10237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil M Mane reassigned OFBIZ-10237: -- Assignee: Swapnil M Mane > The leads which are converted is displayed on the Find lead page. > - > > Key: OFBIZ-10237 > URL: https://issues.apache.org/jira/browse/OFBIZ-10237 > Project: OFBiz > Issue Type: Bug >Reporter: Rubia Elza Joshep >Assignee: Swapnil M Mane >Priority: Major > Attachments: OFBIZ-10237.patch > > > Steps to regenerate: > 1) Open URL > [https://demo-trunk.ofbiz.apache.org/sfa/control/FindLeads|http://example.com/] > 2) Create a lead. Check for the lead in Find lead page. > 3) Convert the lead by clicking on "Create Lead" button. The lead is > successfully converted to contact/ Account. > Actual: The lead which is converted is displayed on the Find lead page. > Expected: Since the lead is converted to contact/Account it should not be > displayed on the Find lead page. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10749) Unable to submit set Billing form in order manager when payment method is EFT
[ https://issues.apache.org/jira/browse/OFBIZ-10749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil M Mane reassigned OFBIZ-10749: -- Assignee: Swapnil M Mane > Unable to submit set Billing form in order manager when payment method is EFT > - > > Key: OFBIZ-10749 > URL: https://issues.apache.org/jira/browse/OFBIZ-10749 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk >Reporter: Arpit Mor >Assignee: Swapnil M Mane >Priority: Major > Attachments: 1-SetCustomer.png, 10-ConsoleError.png, 2-Continue.png, > 3-AddProduct.png, 4-QuickFinalizeOrder.png, 5-EftAccount.png, > 6-TelecomNumber.png, 7-Address.png, 8-EFT.png, 9-BillingAddress.png, > OFBIZ-10749.patch > > > Steps to regenerate: > # Login to URL: [https://demo-trunk.ofbiz.apache.org/ordermgr/control/main] > # Click on order entry > # Set customer and click on continue (Please refer attachment: 1-SetCustomer) > # Click continue on Enter Order Currency, Agreements, and Ship Dates page > (Please refer attachment: 2-Continue) > # Add product and click on Quick Finalize Order (Please refer attachment: > 3-AddProduct) > # On Quick Finalize Order page select UPS Air and click on EFT Account > (Please refer attachment: 4-QuickFinalizeOrder) > # Enter account details but do not select billing address and click on Save > button(Please refer attachment: 5-EftAccount) > # Add phone and email address and click on continue (Please refer > attachment: 6-TelecomNumber) > # Enter address (Please refer attachment: 7-Address) > # Click continue on Sales Order : Order Entry Order Terms page > # Select Electronic Fund Transfer on Sales Order : Order Entry Payment > Settings and click continue (Please refer attachment: 8-EFT) > # Enter billing address and click on continue (Please refer attachment: > 9-BillingAddress) > Actual: Unable to Submit form and error message was displayed on console > (Please refer attachment: 10-ConsoleError) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10847) Issue in order history promotion
[ https://issues.apache.org/jira/browse/OFBIZ-10847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suraj Khurana reassigned OFBIZ-10847: - Assignee: Suraj Khurana > Issue in order history promotion > > > Key: OFBIZ-10847 > URL: https://issues.apache.org/jira/browse/OFBIZ-10847 > Project: OFBiz > Issue Type: Bug > Components: product >Affects Versions: Release Branch 16.11, Upcoming Branch, Release Branch > 17.12, Release Branch 18.12 >Reporter: Lalit Dashora >Assignee: Suraj Khurana >Priority: Major > Attachments: OFBIZ-10847.patch > > > Instance: [#https://demo-trunk.ofbiz.apache.org/ecommerce/control/main] > Reference promotion Id: 9019 > Promo Description: Spend more than $1000 in any 12 months on our fabulous > Widgets and Gizmos and get a 5% discount. > PromoName: Test Percent off when Customer Orders over $1000 in 12 months > Issue: According to the promotion customer should spend $1000 in any 12 > months to avail 5% discount. The system is providing the discount even if the > customer is not logged in. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10921) Marital Status not managed properly in Person entity
[
https://issues.apache.org/jira/browse/OFBIZ-10921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826930#comment-16826930
]
Nicolas Malin commented on OFBIZ-10921:
---
I would tend to improve the patch with deprecated martialStatus like this :
{code:java}
-
+ Deprecated since branch release: use
martialStatusEnumId
+ {code}
I think it's important to have a good relation between the attribute name and
the value content.
> Marital Status not managed properly in Person entity
>
>
> Key: OFBIZ-10921
> URL: https://issues.apache.org/jira/browse/OFBIZ-10921
> Project: OFBiz
> Issue Type: Improvement
> Components: party
>Affects Versions: Trunk
>Reporter: Suraj Khurana
>Assignee: Suraj Khurana
>Priority: Major
> Attachments: OFBIZ-10921.patch
>
>
> Currently, *maritalStatus* is managed as an indicator (Y/N) in *Person*
> entity. I think we can enhance it and make it derived from *Enumeration*
> pattern.
>
> *Classification of legal marital status*
>
> - 1 - Married (and not separated) ...
> - 2 - Widowed (including living common law) ...
> - 3 - Separated (and not Divorced) ...
> - 4 - Divorced (including living common law) ...
> - 5 - Single (including living common law)
> Please refer discussion over ML:
> [https://markmail.org/message/5b33qm3osy76if24]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-10921) Marital Status not managed properly in Person entity
[
https://issues.apache.org/jira/browse/OFBIZ-10921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826918#comment-16826918
]
Suraj Khurana commented on OFBIZ-10921:
---
Thanks everyone for your inputs,
I have attached patch with only two enums as of now, Single and Married.
Also, here is the alter query:
{code:java}
alter table person change MARITAL_STATUS MARITAL_STATUS VARCHAR(20);{code}
> Marital Status not managed properly in Person entity
>
>
> Key: OFBIZ-10921
> URL: https://issues.apache.org/jira/browse/OFBIZ-10921
> Project: OFBiz
> Issue Type: Improvement
> Components: party
>Affects Versions: Trunk
>Reporter: Suraj Khurana
>Assignee: Suraj Khurana
>Priority: Major
> Attachments: OFBIZ-10921.patch
>
>
> Currently, *maritalStatus* is managed as an indicator (Y/N) in *Person*
> entity. I think we can enhance it and make it derived from *Enumeration*
> pattern.
>
> *Classification of legal marital status*
>
> - 1 - Married (and not separated) ...
> - 2 - Widowed (including living common law) ...
> - 3 - Separated (and not Divorced) ...
> - 4 - Divorced (including living common law) ...
> - 5 - Single (including living common law)
> Please refer discussion over ML:
> [https://markmail.org/message/5b33qm3osy76if24]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10921) Marital Status not managed properly in Person entity
[ https://issues.apache.org/jira/browse/OFBIZ-10921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suraj Khurana updated OFBIZ-10921: -- Attachment: OFBIZ-10921.patch > Marital Status not managed properly in Person entity > > > Key: OFBIZ-10921 > URL: https://issues.apache.org/jira/browse/OFBIZ-10921 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Trunk >Reporter: Suraj Khurana >Assignee: Suraj Khurana >Priority: Major > Attachments: OFBIZ-10921.patch > > > Currently, *maritalStatus* is managed as an indicator (Y/N) in *Person* > entity. I think we can enhance it and make it derived from *Enumeration* > pattern. > > *Classification of legal marital status* > > - 1 - Married (and not separated) ... > - 2 - Widowed (including living common law) ... > - 3 - Separated (and not Divorced) ... > - 4 - Divorced (including living common law) ... > - 5 - Single (including living common law) > Please refer discussion over ML: > [https://markmail.org/message/5b33qm3osy76if24] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-5402) Incorrect contact information displayed on purchase order view page
[ https://issues.apache.org/jira/browse/OFBIZ-5402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suraj Khurana reassigned OFBIZ-5402: Assignee: Suraj Khurana (was: Prakhar Kumar) > Incorrect contact information displayed on purchase order view page > --- > > Key: OFBIZ-5402 > URL: https://issues.apache.org/jira/browse/OFBIZ-5402 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk >Reporter: Christian Carlow >Assignee: Suraj Khurana >Priority: Trivial > Attachments: OFBIZ-5402.patch, OFBiz-5402-UX-Improvement.png > > > Ship group destinations are listed in the contact information screen on the > purchase order view page but the party is set to the supplier. It seems like > the address information listed should relate to the party of the screen, so > the supplier contact information should probably appear. -- 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=16826903#comment-16826903 ] Deepak Nigam commented on OFBIZ-10518: -- Thanks [~suraj.khurana]. Yes, we can commit patches in chunks. > 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, > 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] [Commented] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826901#comment-16826901 ] Suraj Khurana commented on OFBIZ-10518: --- Thanks [~deepak.nigam], These patches looks good to me, I am checking some things on my local box, will let you know in case of anything else required. I think by then we can commit patches which are straight forward in nature, like entity def, uiLabels etc etc. Once again, thanks for your contribution !! > 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, > 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-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suraj Khurana reassigned OFBIZ-10518: - Assignee: Suraj Khurana (was: Deepak Nigam) > 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, > 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-10252) Making the use of the "button-style-2" class for backend menus consistent
[ https://issues.apache.org/jira/browse/OFBIZ-10252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garima jain reassigned OFBIZ-10252: --- Assignee: Garima jain > Making the use of the "button-style-2" class for backend menus consistent > - > > Key: OFBIZ-10252 > URL: https://issues.apache.org/jira/browse/OFBIZ-10252 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Dennis Balkir >Assignee: Garima jain >Priority: Minor > > While doing some work on the backend of OFBiz, I noticed, that in some cases > the functional buttons of the application I am using are styled with the > class "button-bar button-style-2" and in some other cases are only styled > with "button-bar". > Here are some suggenstions: > * The use of the class "button-bar button-style-2" should be consistent > * The class should get another name, "button-style-2" doesn't really fit its > purpose, I would suggest to name the whole class "button-bar > functional-button-bar" > * If the class "button-style-2" is used for different buttons too, I would > suggest making a new class "functional-button-bar" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10093) Replace ELRTE plugin with Quill.
[ https://issues.apache.org/jira/browse/OFBIZ-10093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826802#comment-16826802 ] Aditya Sharma commented on OFBIZ-10093: --- Indeed, [~jacques.le.roux] at cursory view I can't find way to preview the content (I will look further). Though I will definitely look for its possibility for solving OFBIZ-5537. > Replace ELRTE plugin with Quill. > > > Key: OFBIZ-10093 > URL: https://issues.apache.org/jira/browse/OFBIZ-10093 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: Aditya Sharma >Assignee: Aditya Sharma >Priority: Major > > As there is no support for elrte since elrte-1.3 > [https://github.com/Studio-42/elRTE] it is to be replaced with some other > good editor & we found Quill Js editor as quite suitable: > * 139 releases > * Good community support of 101 contributors > * Licence - BSD 3-Clause "New" or "Revised" License > Links for reference: > [https://quilljs.com/] > [https://github.com/quilljs/quill] > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (OFBIZ-10895) Unknown request [images]; this request does not exist or cannot be called directly.
[
https://issues.apache.org/jira/browse/OFBIZ-10895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux reopened OFBIZ-10895:
-
Partially reverted in
trunk r1858180
R18 r1858181
just replaces "rmaps == null" by "rmaps.isEmpty()"
As Mathieu mentioned in dev:
<>
As I said in r1858094:
<>
We need now to review/check how it worked in R15 where it's OK, and possibly
implements the same
> Unknown request [images]; this request does not exist or cannot be called
> directly.
> ---
>
> Key: OFBIZ-10895
> URL: https://issues.apache.org/jira/browse/OFBIZ-10895
> Project: OFBiz
> Issue Type: Bug
> Components: framework
>Affects Versions: Trunk, Release Branch 16.11, Release Branch 17.12,
> Release Branch 18.12
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Minor
> Fix For: 18.12.01
>
>
> This error happens in many occasions:
> Inside another request (here LookupProduct)
> {noformat}
> 2019-03-31 12:32:26,215 |jsse-nio-8443-exec-2 |ControlServlet
> |T| [[[LookupProduct(Domain:https://localhost)] Request Begun,
> encoding=[UTF-8]- total:0.0,since last(Begin):0.0]]
> 2019-03-31 12:32:26,222 |jsse-nio-8443-exec-7 |ControlServlet
> |T| [[[images(Domain:https://localhost)] Request Begun, encoding=[UTF-8]-
> total:0.0,since last(Begin):0.0]]
> 2019-03-31 12:32:26,222 |jsse-nio-8443-exec-7 |ControlServlet
> |E| Error in request handler:
> org.apache.ofbiz.webapp.control.RequestHandlerException: Unknown request
> [images]; this request does not exist or cannot be called directly.
> at
> org.apache.ofbiz.webapp.control.RequestHandler.doRequest(RequestHandler.java:277)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.control.ControlServlet.doGet(ControlServlet.java:212)
> [ofbiz.jar:?]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:645)
> [javax.servlet-api-4.0.1.jar:4.0.1]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:750)
> [javax.servlet-api-4.0.1.jar:4.0.1]
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
> [tomcat-embed-websocket-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.ofbiz.webapp.control.ContextFilter.doFilter(ContextFilter.java:191)
> [ofbiz.jar:?]
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.ofbiz.webapp.control.ControlFilter.doFilter(ControlFilter.java:156)
> [ofbiz.jar:?]
> at javax.servlet.http.HttpFilter.doFilter(HttpFilter.java:127)
> [javax.servlet-api-4.0.1.jar:4.0.1]
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:200)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:490)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
> org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:668)
> [tomcat-catalina-9.0.16.jar:9.0.16]
> at
>
[jira] [Created] (OFBIZ-10959) Enable entity timestamp fields
Pawan Verma created OFBIZ-10959: --- Summary: Enable entity timestamp fields Key: OFBIZ-10959 URL: https://issues.apache.org/jira/browse/OFBIZ-10959 Project: OFBiz Issue Type: Bug Components: framework/webtools Affects Versions: Trunk, Release Branch 17.12, Release Branch 18.12 Reporter: Pawan Verma Assignee: Pawan Verma 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)
