[jira] [Closed] (OFBIZ-8831) Typo in error message when OFBiz is unable to connect to database.
[ https://issues.apache.org/jira/browse/OFBIZ-8831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Dixit closed OFBIZ-8831. --- Resolution: Implemented Fix Version/s: (was: Trunk) Upcoming Release > Typo in error message when OFBiz is unable to connect to database. > -- > > Key: OFBIZ-8831 > URL: https://issues.apache.org/jira/browse/OFBIZ-8831 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Humera Khan >Assignee: Deepak Dixit >Priority: Minor > Fix For: Upcoming Release > > Attachments: OFBIZ-8831.patch > > > Steps to regenerate : > 1. Go to entityengine.xml file of framework component. > 2. Change the name of the database in entityengine.xml to random which does > not exists in your database. > 3. Restart the OFBiz and check the error message on console. > 4.It shows "Unable to esablish connection to database". > Expected : It should show "Unable to establish connection to database". -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-8831) Typo in error message when OFBiz is unable to connect to database.
[ https://issues.apache.org/jira/browse/OFBIZ-8831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079490#comment-16079490 ] Deepak Dixit commented on OFBIZ-8831: - This has been already fixed at r#1768808 > Typo in error message when OFBiz is unable to connect to database. > -- > > Key: OFBIZ-8831 > URL: https://issues.apache.org/jira/browse/OFBIZ-8831 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Humera Khan >Assignee: Deepak Dixit >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-8831.patch > > > Steps to regenerate : > 1. Go to entityengine.xml file of framework component. > 2. Change the name of the database in entityengine.xml to random which does > not exists in your database. > 3. Restart the OFBiz and check the error message on console. > 4.It shows "Unable to esablish connection to database". > Expected : It should show "Unable to establish connection to database". -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (OFBIZ-9254) Inconsistent String Comparisons
[
https://issues.apache.org/jira/browse/OFBIZ-9254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079101#comment-16079101
]
Arun Patidar edited comment on OFBIZ-9254 at 7/9/17 6:53 AM:
-
OFBIZ-9254_FTL-I.patch :- Committed revision 1801268
OFBIZ-9254_ftl_themes.patch :- Committed revision 1801278
OFBIZ-9254_ftl_product.patch: -Committed revision 1801280
OFBIZ-9254_ftl_plugins_pricat_projmgr.patch: Committed revision 1801282
OFBIZ-9254_ftl_plugins_ecommerce.patch:Committed revision 1801284
was (Author: arunpati):
OFBIZ-9254_FTL-I.patch :- Committed revision 1801268
OFBIZ-9254_ftl_themes.patch :- Committed revision 1801278
OFBIZ-9254_ftl_product.patch: -Committed revision 1801280
> Inconsistent String Comparisons
> ---
>
> Key: OFBIZ-9254
> URL: https://issues.apache.org/jira/browse/OFBIZ-9254
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: Devanshu Vyas
>Assignee: Deepak Dixit
>Priority: Minor
> Attachments: OFBIZ-9251_ftl_accounting.patch,
> OFBIZ-9251_ftl_framework.patch, OFBIZ-9251_ftl_manuf_workeffrt.patch,
> OFBIZ-9251_ftl_order.patch, OFBIZ-9251_ftl_party_content.patch,
> OFBIZ-9251_ftl_plugins_ebay_ebaystore.patch,
> OFBIZ-9251_ftl_plugins_ecommerce.patch,
> OFBIZ-9251_ftl_plugins_pricat_projmgr.patch, OFBIZ-9251_ftl_product.patch,
> OFBIZ-9251_ftl_themes.patch, OFBIZ-9254_FTL-I.patch,
> OFBIZ-9254_groovy_applications.patch, OFBIZ-9254_groovy_framework.patch,
> OFBIZ-9254_java_accounting.patch, OFBIZ-9254_java_base.patch,
> OFBIZ-9254_java_content.patch, OFBIZ-9254_java_entity.patch,
> OFBIZ-9254_java_order.patch, OFBIZ-9254_java_Party_WE_MFC.patch,
> OFBIZ-9254_java_product.patch, OFBIZ-9254_java_service.patch,
> OFBIZ-9254_java_test_entityext_common_cattalina_datafile.patch,
> OFBIZ-9254_java_webapp.patch, OFBIZ-9254_java_webtools.patch,
> OFBIZ-9254_java_widget.patch, OFBIZ-9254_plugins_groovy.patch,
> OFBIZ-9254_plugins_java.patch
>
>
> I found an inconsistency in the code for string comparison
> statusId.equals("PRUN_COMPLETED") whereas it should be written as
> "PRUN_COMPLETED".equals(statusId)
> cause the former can throw NullPointerException if the variable found to be
> NULL.
> This pattern should be applied to
> - Java Files
> - Groovy Files
> - FTL Files
> Here is the reference for the discussion done on the dev list.
> http://markmail.org/message/iqfaab3fl3ukxchy
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (OFBIZ-8831) Typo in error message when OFBiz is unable to connect to database.
[ https://issues.apache.org/jira/browse/OFBIZ-8831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Dixit reassigned OFBIZ-8831: --- Assignee: Deepak Dixit (was: Pritam Kute) > Typo in error message when OFBiz is unable to connect to database. > -- > > Key: OFBIZ-8831 > URL: https://issues.apache.org/jira/browse/OFBIZ-8831 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Humera Khan >Assignee: Deepak Dixit >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-8831.patch > > > Steps to regenerate : > 1. Go to entityengine.xml file of framework component. > 2. Change the name of the database in entityengine.xml to random which does > not exists in your database. > 3. Restart the OFBiz and check the error message on console. > 4.It shows "Unable to esablish connection to database". > Expected : It should show "Unable to establish connection to database". -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OFBIZ-9317) WorkEffort shows error on adding party with specific role to Timesheet.
[ https://issues.apache.org/jira/browse/OFBIZ-9317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Patidar closed OFBIZ-9317. --- Resolution: Fixed Fix Version/s: Upcoming Release Committed revision 1801350. Thanks Jagpreet for your contribution. > WorkEffort shows error on adding party with specific role to Timesheet. > > > Key: OFBIZ-9317 > URL: https://issues.apache.org/jira/browse/OFBIZ-9317 > Project: OFBiz > Issue Type: Bug > Components: workeffort >Reporter: Jagpreet Kaur >Assignee: Arun Patidar > Fix For: Upcoming Release > > Attachments: OFBIZ-9317.patch, screenshot-1.png > > > 1) Go to WorkEffort component. > 2) Click on Timesheet tab > [https://localhost:8443/workeffort/control/FindTimesheet]. > 3) Click on Find button. > 4) Choose any timesheet > [https://localhost:8443/workeffort/control/EditTimesheet?timesheetId=1] > 5) Click on Parties Tab > [https://localhost:8443/workeffort/control/EditTimesheetRoles?timesheetId=1] > 6) Choose any party from look up and click on Add. > 7) Error will be displayed on screen. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-8849) Search operation on 'OrderReportPurchasesGroupByProduct' entity causing exception.
[ https://issues.apache.org/jira/browse/OFBIZ-8849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079488#comment-16079488 ] Deepak Dixit commented on OFBIZ-8849: - Hi Pallavi, Its not good idea to set group-by true for all fields. This entity is used to generate Purchases by Organization Report from [OrderPurchaseReportOptions|https://localhost:8443/ordermgr/control/OrderPurchaseReportOptions] and its working properly. > Search operation on 'OrderReportPurchasesGroupByProduct' entity causing > exception. > -- > > Key: OFBIZ-8849 > URL: https://issues.apache.org/jira/browse/OFBIZ-8849 > Project: OFBiz > Issue Type: Bug > Components: framework/webtools >Affects Versions: Trunk >Reporter: Pallavi Goyal > Fix For: Trunk > > Attachments: OFBIZ-8849.patch, OrderReport_Actual.png, > OrderReport_Expected.png > > > Steps to regenerate : > 1. Go to Entity Data Maintenance in webtools. > 2. Search entity 'OrderReportPurchasesGroupByProduct'. Click on it and go to > the overview page. > 3. Click on the Find button. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9317) WorkEffort shows error on adding party with specific role to Timesheet.
[ https://issues.apache.org/jira/browse/OFBIZ-9317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Patidar reassigned OFBIZ-9317: --- Assignee: Arun Patidar > WorkEffort shows error on adding party with specific role to Timesheet. > > > Key: OFBIZ-9317 > URL: https://issues.apache.org/jira/browse/OFBIZ-9317 > Project: OFBiz > Issue Type: Bug > Components: workeffort >Reporter: Jagpreet Kaur >Assignee: Arun Patidar > Attachments: OFBIZ-9317.patch, screenshot-1.png > > > 1) Go to WorkEffort component. > 2) Click on Timesheet tab > [https://localhost:8443/workeffort/control/FindTimesheet]. > 3) Click on Find button. > 4) Choose any timesheet > [https://localhost:8443/workeffort/control/EditTimesheet?timesheetId=1] > 5) Click on Parties Tab > [https://localhost:8443/workeffort/control/EditTimesheetRoles?timesheetId=1] > 6) Choose any party from look up and click on Add. > 7) Error will be displayed on screen. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OFBIZ-9316) Error displayed while adding WorkEffort Contact Mechs.
[ https://issues.apache.org/jira/browse/OFBIZ-9316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Patidar closed OFBIZ-9316. --- Resolution: Fixed Fix Version/s: Upcoming Release Committed revision 1801349. Modified patch. Returned error message from service if both contactMechId and ContactMechTypeId are empty. Thanks Jagpreet for your contribution. > Error displayed while adding WorkEffort Contact Mechs. > -- > > Key: OFBIZ-9316 > URL: https://issues.apache.org/jira/browse/OFBIZ-9316 > Project: OFBiz > Issue Type: Bug > Components: workeffort >Reporter: Jagpreet Kaur >Assignee: Arun Patidar > Fix For: Upcoming Release > > Attachments: OFBIZ-9316.patch, screenshot-1.png > > > 1) Go to workEffort component. > 2) Navigate to Task List tab. > [https://localhost:8443/workeffort/control/mytasks] > 3) Select any task from the list. > 4) Navigate to Contact Mechs tab and try to add any contact mech id after > choosing from look up. > 5) Error will be displayed on screen. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9475) Refactor serialize and non-serialize inventory item implementaion
[ https://issues.apache.org/jira/browse/OFBIZ-9475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Renuka Srishti reassigned OFBIZ-9475: - Assignee: Renuka Srishti > Refactor serialize and non-serialize inventory item implementaion > - > > Key: OFBIZ-9475 > URL: https://issues.apache.org/jira/browse/OFBIZ-9475 > Project: OFBiz > Issue Type: Improvement >Reporter: Deepak Dixit >Assignee: Renuka Srishti > > As discussed on dev mailing list [1][2] we need to refactor serialize and > non-serialize inventory item design. > As per current implementation serialize inventory item work on status and > non-serialized inventory item work on inventory item detail. > Proposed Design: > - Use inventory item detail for both serialize and non-serialize inventory > item. Only one additional condition for serialized inventory item that qoh > can't be greater then one. > - We can maintain inventory item status record for both type > [1] http://markmail.org/thread/bd2bpiv6c5wvl7km > [2] http://ofbiz.markmail.org/thread/kro5kcggp4fcose7 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9358) Integrating google phone number library for validating telecom numbers
[ https://issues.apache.org/jira/browse/OFBIZ-9358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Renuka Srishti updated OFBIZ-9358: -- Attachment: OFBIZ-9358.patch Add one more point to the available patch: Use @Deprecated annotation to deprecate isUSPhoneNumber, isUSPhoneAreaCode, isUSPhoneMainNumber and isInternationalPhoneNumber methods of class UtilValidate. > Integrating google phone number library for validating telecom numbers > -- > > Key: OFBIZ-9358 > URL: https://issues.apache.org/jira/browse/OFBIZ-9358 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Upcoming Release >Reporter: Suraj Khurana >Assignee: Renuka Srishti > Attachments: OFBIZ-9358.patch, OFBIZ-9358.patch > > > As per discussion at > https://lists.apache.org/list.html?d...@ofbiz.apache.org:lte=1M:Validating%20telecom%20numbers > Need to integrate Google telephone number to validate telephone numbers > formats of various countries. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OFBIZ-9111) Service "deletePayHistory" does not have correct implementation
[ https://issues.apache.org/jira/browse/OFBIZ-9111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Dixit closed OFBIZ-9111. --- Resolution: Done Fix Version/s: Upcoming Release This has been done at ofbiz framework at r#1801348 Thanks Pawan Vemra for your contribution. > Service "deletePayHistory" does not have correct implementation > --- > > Key: OFBIZ-9111 > URL: https://issues.apache.org/jira/browse/OFBIZ-9111 > Project: OFBiz > Issue Type: Improvement > Components: humanres >Affects Versions: Trunk >Reporter: Pawan Verma >Assignee: Deepak Dixit >Priority: Minor > Fix For: Upcoming Release > > Attachments: OFBIZ-9111.patch, OFBIZ-9111.patch > > > Service "deletePayHistory" does not have correct implementation.This service > set thru_date then remove record of PayHistory.This should be corrected. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9111) Service "deletePayHistory" does not have correct implementation
[ https://issues.apache.org/jira/browse/OFBIZ-9111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Dixit updated OFBIZ-9111: Issue Type: Improvement (was: Bug) > Service "deletePayHistory" does not have correct implementation > --- > > Key: OFBIZ-9111 > URL: https://issues.apache.org/jira/browse/OFBIZ-9111 > Project: OFBiz > Issue Type: Improvement > Components: humanres >Affects Versions: Trunk >Reporter: Pawan Verma >Assignee: Deepak Dixit >Priority: Minor > Attachments: OFBIZ-9111.patch, OFBIZ-9111.patch > > > Service "deletePayHistory" does not have correct implementation.This service > set thru_date then remove record of PayHistory.This should be corrected. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9111) Service "deletePayHistory" does not have correct implementation
[ https://issues.apache.org/jira/browse/OFBIZ-9111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079465#comment-16079465 ] Deepak Dixit commented on OFBIZ-9111: - I think instead of delete it should call expirePayHistory. > Service "deletePayHistory" does not have correct implementation > --- > > Key: OFBIZ-9111 > URL: https://issues.apache.org/jira/browse/OFBIZ-9111 > Project: OFBiz > Issue Type: Bug > Components: humanres >Affects Versions: Trunk >Reporter: Pawan Verma >Assignee: Deepak Dixit >Priority: Minor > Attachments: OFBIZ-9111.patch, OFBIZ-9111.patch > > > Service "deletePayHistory" does not have correct implementation.This service > set thru_date then remove record of PayHistory.This should be corrected. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9316) Error displayed while adding WorkEffort Contact Mechs.
[ https://issues.apache.org/jira/browse/OFBIZ-9316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Patidar reassigned OFBIZ-9316: --- Assignee: Arun Patidar > Error displayed while adding WorkEffort Contact Mechs. > -- > > Key: OFBIZ-9316 > URL: https://issues.apache.org/jira/browse/OFBIZ-9316 > Project: OFBiz > Issue Type: Bug > Components: workeffort >Reporter: Jagpreet Kaur >Assignee: Arun Patidar > Attachments: OFBIZ-9316.patch, screenshot-1.png > > > 1) Go to workEffort component. > 2) Navigate to Task List tab. > [https://localhost:8443/workeffort/control/mytasks] > 3) Select any task from the list. > 4) Navigate to Contact Mechs tab and try to add any contact mech id after > choosing from look up. > 5) Error will be displayed on screen. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9111) Service "deletePayHistory" does not have correct implementation
[ https://issues.apache.org/jira/browse/OFBIZ-9111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Dixit reassigned OFBIZ-9111: --- Assignee: Deepak Dixit (was: Michael Brohl) > Service "deletePayHistory" does not have correct implementation > --- > > Key: OFBIZ-9111 > URL: https://issues.apache.org/jira/browse/OFBIZ-9111 > Project: OFBiz > Issue Type: Bug > Components: humanres >Affects Versions: Trunk >Reporter: Pawan Verma >Assignee: Deepak Dixit >Priority: Minor > Attachments: OFBIZ-9111.patch, OFBIZ-9111.patch > > > Service "deletePayHistory" does not have correct implementation.This service > set thru_date then remove record of PayHistory.This should be corrected. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OFBIZ-9473) Status of communication event role is marked "Read" on View Communication Event page.
[ https://issues.apache.org/jira/browse/OFBIZ-9473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Patidar closed OFBIZ-9473. --- Resolution: Fixed Committed revision 1801347 Thanks Pallavi for your contribution. > Status of communication event role is marked "Read" on View Communication > Event page. > - > > Key: OFBIZ-9473 > URL: https://issues.apache.org/jira/browse/OFBIZ-9473 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: Trunk >Reporter: Pallavi Goyal >Assignee: Arun Patidar > Fix For: Upcoming Release > > Attachments: OFBIZ-9473.patch > > > *Steps to regenerate -* > 1. Go to "Party" component. > 2. Click on [ Communications ] menu tab. > 3. Find communication events. > 4. Open any communication event view page for "Addressee" role from Find > Communication Event page. > Actual - The role status of communication is marked "Read" on viewing > communication. > Expected - There is no change in the role status of the communication event. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9473) Status of communication event role is marked "Read" on View Communication Event page.
[ https://issues.apache.org/jira/browse/OFBIZ-9473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Patidar reassigned OFBIZ-9473: --- Assignee: Arun Patidar > Status of communication event role is marked "Read" on View Communication > Event page. > - > > Key: OFBIZ-9473 > URL: https://issues.apache.org/jira/browse/OFBIZ-9473 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: Trunk >Reporter: Pallavi Goyal >Assignee: Arun Patidar > Fix For: Upcoming Release > > Attachments: OFBIZ-9473.patch > > > *Steps to regenerate -* > 1. Go to "Party" component. > 2. Click on [ Communications ] menu tab. > 3. Find communication events. > 4. Open any communication event view page for "Addressee" role from Find > Communication Event page. > Actual - The role status of communication is marked "Read" on viewing > communication. > Expected - There is no change in the role status of the communication event. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OFBIZ-9459) Wrong screen redirection after adding note on Lead profile screen
[ https://issues.apache.org/jira/browse/OFBIZ-9459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Patidar closed OFBIZ-9459. --- Resolution: Fixed Fix Version/s: Upcoming Release Committed revision 1801346. Thanks Jagpreet and Priya for your contribution. > Wrong screen redirection after adding note on Lead profile screen > - > > Key: OFBIZ-9459 > URL: https://issues.apache.org/jira/browse/OFBIZ-9459 > Project: OFBiz > Issue Type: Bug > Components: marketing >Reporter: Jagpreet Kaur >Assignee: Arun Patidar > Fix For: Upcoming Release > > Attachments: Create Note.png, OFBIZ-9459.patch, Screenredirection.png > > > 1) Go to SFA component. > 2) Click on Leads tab > [https://demo-trunk-ofbiz.apache.org:8443/sfa/control/FindLeads|https://demo-trunk-ofbiz.apache.org:8443/sfa/control/FindLeads]. > 3) Choose any partyId from All Lead list, you will be navigated to Lead > profile. > [https://demo-trunk-ofbiz.apache.org:8443/sfa/control/viewprofile?roleTypeId=LEAD&partyId=DemoLead|https://demo-trunk-ofbiz.apache.org:8443/sfa/control/viewprofile?roleTypeId=LEAD&partyId=DemoLead] > 4) Click on "Create New" button in the Notes section. > 5) Add the Note content. > 6) Click on "Save Button". > View redirection should be profile but it shows the blank screen. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9459) Wrong screen redirection after adding note on Lead profile screen
[ https://issues.apache.org/jira/browse/OFBIZ-9459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Patidar reassigned OFBIZ-9459: --- Assignee: Arun Patidar > Wrong screen redirection after adding note on Lead profile screen > - > > Key: OFBIZ-9459 > URL: https://issues.apache.org/jira/browse/OFBIZ-9459 > Project: OFBiz > Issue Type: Bug > Components: marketing >Reporter: Jagpreet Kaur >Assignee: Arun Patidar > Attachments: Create Note.png, OFBIZ-9459.patch, Screenredirection.png > > > 1) Go to SFA component. > 2) Click on Leads tab > [https://demo-trunk-ofbiz.apache.org:8443/sfa/control/FindLeads|https://demo-trunk-ofbiz.apache.org:8443/sfa/control/FindLeads]. > 3) Choose any partyId from All Lead list, you will be navigated to Lead > profile. > [https://demo-trunk-ofbiz.apache.org:8443/sfa/control/viewprofile?roleTypeId=LEAD&partyId=DemoLead|https://demo-trunk-ofbiz.apache.org:8443/sfa/control/viewprofile?roleTypeId=LEAD&partyId=DemoLead] > 4) Click on "Create New" button in the Notes section. > 5) Add the Note content. > 6) Click on "Save Button". > View redirection should be profile but it shows the blank screen. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9143) The copyAgreement service fails
[ https://issues.apache.org/jira/browse/OFBIZ-9143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079390#comment-16079390 ] Renuka Srishti commented on OFBIZ-9143: --- Hii Jacques, Please share the steps to regenerate this issue. > The copyAgreement service fails > --- > > Key: OFBIZ-9143 > URL: https://issues.apache.org/jira/browse/OFBIZ-9143 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk >Reporter: Jacques Le Roux > > Error (in French) > Le service dispatcher a renvoyé une exception :Outgoing result (in runSync : > copyAgreement) does not match expected requirements (Le paramètre requis > suivant manque : [OUT] [copyAgreement.agreementId]) > In other words, [copyAgreement.agreementId [OUT] parameter misses -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9459) Wrong screen redirection after adding note on Lead profile screen
[ https://issues.apache.org/jira/browse/OFBIZ-9459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] priya sharma updated OFBIZ-9459: Attachment: OFBIZ-9459.patch Resolved the issue by directing the response to backHome request, as viewprofile request uses save-home-view attribute.Thus home can be relocated and the request can be directed accordingly. > Wrong screen redirection after adding note on Lead profile screen > - > > Key: OFBIZ-9459 > URL: https://issues.apache.org/jira/browse/OFBIZ-9459 > Project: OFBiz > Issue Type: Bug > Components: marketing >Reporter: Jagpreet Kaur > Attachments: Create Note.png, OFBIZ-9459.patch, Screenredirection.png > > > 1) Go to SFA component. > 2) Click on Leads tab > [https://demo-trunk-ofbiz.apache.org:8443/sfa/control/FindLeads|https://demo-trunk-ofbiz.apache.org:8443/sfa/control/FindLeads]. > 3) Choose any partyId from All Lead list, you will be navigated to Lead > profile. > [https://demo-trunk-ofbiz.apache.org:8443/sfa/control/viewprofile?roleTypeId=LEAD&partyId=DemoLead|https://demo-trunk-ofbiz.apache.org:8443/sfa/control/viewprofile?roleTypeId=LEAD&partyId=DemoLead] > 4) Click on "Create New" button in the Notes section. > 5) Add the Note content. > 6) Click on "Save Button". > View redirection should be profile but it shows the blank screen. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9135) popup info about image in ordermgr shows html markup
[ https://issues.apache.org/jira/browse/OFBIZ-9135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079380#comment-16079380 ] Renuka Srishti commented on OFBIZ-9135: --- Hi Wai, I have performed the mentioned steps and I think the issue is no more exist. Please check once, if there is any issue. we can discuss further. > popup info about image in ordermgr shows html markup > > > Key: OFBIZ-9135 > URL: https://issues.apache.org/jira/browse/OFBIZ-9135 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk >Reporter: Wai > > -use https://localhost:8443/ordermgr/control/orderentry > -fill all necessary required order info > -select productId=WG-9943 > -click 'Add to Order' > -Notice the images in the 'You might be interested in these as well:' section. > -hover mouse over the image. > -the popup shows html markup -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OFBIZ-9402) Cut of unnecessary auto-stamp fields from Visit, ServerHit and ServerHitBin
[ https://issues.apache.org/jira/browse/OFBIZ-9402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Patidar closed OFBIZ-9402. --- Resolution: Fixed Fix Version/s: Upcoming Release Committed revision 1801343. Thanks Martin for your contribution. > Cut of unnecessary auto-stamp fields from Visit, ServerHit and ServerHitBin > --- > > Key: OFBIZ-9402 > URL: https://issues.apache.org/jira/browse/OFBIZ-9402 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Martin Becker >Assignee: Arun Patidar >Priority: Minor > Fix For: Upcoming Release > > Attachments: OFBIZ-9402-Visit_ServerHit_ServerHitBin_auto-stamps.patch > > > Set no-auto-stamp flag for entities Visit, ServerHit and ServerHitBin in > entitymodel.xml to "true" since automatically created timestamps take up > space and hold nonessential time information for this statistic entities with > their more precise business time fields (e.g. fromDate and thruDate from > Visit) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9402) Cut of unnecessary auto-stamp fields from Visit, ServerHit and ServerHitBin
[ https://issues.apache.org/jira/browse/OFBIZ-9402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Patidar reassigned OFBIZ-9402: --- Assignee: Arun Patidar > Cut of unnecessary auto-stamp fields from Visit, ServerHit and ServerHitBin > --- > > Key: OFBIZ-9402 > URL: https://issues.apache.org/jira/browse/OFBIZ-9402 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Martin Becker >Assignee: Arun Patidar >Priority: Minor > Attachments: OFBIZ-9402-Visit_ServerHit_ServerHitBin_auto-stamps.patch > > > Set no-auto-stamp flag for entities Visit, ServerHit and ServerHitBin in > entitymodel.xml to "true" since automatically created timestamps take up > space and hold nonessential time information for this statistic entities with > their more precise business time fields (e.g. fromDate and thruDate from > Visit) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OFBIZ-9460) Convert AgreementServices.xml mini-lang to groovyDSL
[ https://issues.apache.org/jira/browse/OFBIZ-9460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Patidar closed OFBIZ-9460. --- Resolution: Fixed Fix Version/s: Upcoming Release Committed revision 1801342. Thanks Rishi Solanki for your contribution. > Convert AgreementServices.xml mini-lang to groovyDSL > > > Key: OFBIZ-9460 > URL: https://issues.apache.org/jira/browse/OFBIZ-9460 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk >Reporter: Rishi Solanki >Assignee: Arun Patidar > Fix For: Upcoming Release > > Attachments: OFBIZ-9460.patch, OFBIZ-9460.patch > > > This file covers two services as cancelAgreement and copyAgreement. > Need to follow practices in the parent ticket for this conversion. Ticket Id: > OFBIZ-9350. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9460) Convert AgreementServices.xml mini-lang to groovyDSL
[ https://issues.apache.org/jira/browse/OFBIZ-9460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Patidar reassigned OFBIZ-9460: --- Assignee: Arun Patidar (was: Rishi Solanki) > Convert AgreementServices.xml mini-lang to groovyDSL > > > Key: OFBIZ-9460 > URL: https://issues.apache.org/jira/browse/OFBIZ-9460 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk >Reporter: Rishi Solanki >Assignee: Arun Patidar > Attachments: OFBIZ-9460.patch, OFBIZ-9460.patch > > > This file covers two services as cancelAgreement and copyAgreement. > Need to follow practices in the parent ticket for this conversion. Ticket Id: > OFBIZ-9350. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OFBIZ-9404) Insufficient checking of checkOutPaymentId in CheckOutEvents.getSelectedPaymentMethods
[ https://issues.apache.org/jira/browse/OFBIZ-9404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Patidar closed OFBIZ-9404. --- Resolution: Fixed Fix Version/s: Upcoming Release Committed revision 1801340. Thanks Martin for your contribution. > Insufficient checking of checkOutPaymentId in > CheckOutEvents.getSelectedPaymentMethods > -- > > Key: OFBIZ-9404 > URL: https://issues.apache.org/jira/browse/OFBIZ-9404 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk >Reporter: Martin Becker >Assignee: Arun Patidar > Fix For: Upcoming Release > > Attachments: OFBIZ-9404_empty-check_checkOutPaymentId.patch > > > The following patch fixes a bug where the paymentMethod in > CheckOutEvents.getSelectedPaymentMethods might be filled with a phantom > payment method. > It checks for an empty parameter, not only NULL, to avoid a phantom > paymentMethod with ID "" in selectedPaymentMethods, that causes subsequent > errors in payment handling (e.g. ShoppingCart.getValueObject). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9404) Insufficient checking of checkOutPaymentId in CheckOutEvents.getSelectedPaymentMethods
[ https://issues.apache.org/jira/browse/OFBIZ-9404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Patidar reassigned OFBIZ-9404: --- Assignee: Arun Patidar > Insufficient checking of checkOutPaymentId in > CheckOutEvents.getSelectedPaymentMethods > -- > > Key: OFBIZ-9404 > URL: https://issues.apache.org/jira/browse/OFBIZ-9404 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk >Reporter: Martin Becker >Assignee: Arun Patidar > Attachments: OFBIZ-9404_empty-check_checkOutPaymentId.patch > > > The following patch fixes a bug where the paymentMethod in > CheckOutEvents.getSelectedPaymentMethods might be filled with a phantom > payment method. > It checks for an empty parameter, not only NULL, to avoid a phantom > paymentMethod with ID "" in selectedPaymentMethods, that causes subsequent > errors in payment handling (e.g. ShoppingCart.getValueObject). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-6760) Move all entity definitions from the applications components into a separate one
[ https://issues.apache.org/jira/browse/OFBIZ-6760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079358#comment-16079358 ] Deepak Dixit commented on OFBIZ-6760: - Removed deprecated (entitymodel_old) entities under OFBIZ-9327 > Move all entity definitions from the applications components into a separate > one > > > Key: OFBIZ-6760 > URL: https://issues.apache.org/jira/browse/OFBIZ-6760 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: Jacques Le Roux > Fix For: Upcoming Release > > > See this thread for a previous discussion: > http://markmail.org/message/sfdm22wfy3fulpyb -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9327) Remove Deprecated Entities
[ https://issues.apache.org/jira/browse/OFBIZ-9327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Dixit updated OFBIZ-9327: Issue Type: Sub-task (was: Improvement) Parent: OFBIZ-6760 > Remove Deprecated Entities > -- > > Key: OFBIZ-9327 > URL: https://issues.apache.org/jira/browse/OFBIZ-9327 > Project: OFBiz > Issue Type: Sub-task > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Deepak Dixit >Assignee: Deepak Dixit >Priority: Minor > Fix For: Upcoming Release > > > We have deprecated entities define in entitymodel suffix with "Old", we can > remove these entities as they are too old. > [Deprecated Entities|https://cwiki.apache.org/confluence/x/KYBr] > [Dev list > discussion|https://lists.apache.org/thread.html/45081cf2c344f2e0de709a3e987749798ad60390bb93cab3a6ab6c25@%3Cdev.ofbiz.apache.org%3E] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9327) Remove Deprecated Entities
[ https://issues.apache.org/jira/browse/OFBIZ-9327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Dixit updated OFBIZ-9327: Description: We have deprecated entities define in entitymodel suffix with "Old", we can remove these entities as they are too old. [Deprecated Entities|https://cwiki.apache.org/confluence/x/KYBr] [Dev list discussion|https://lists.apache.org/thread.html/45081cf2c344f2e0de709a3e987749798ad60390bb93cab3a6ab6c25@%3Cdev.ofbiz.apache.org%3E] was: We have deprecated entities define in entitymodel prefix with "Old", we can remove these entities as they are too old. [Deprecated Entities|https://cwiki.apache.org/confluence/x/KYBr] [Dev list discussion|https://lists.apache.org/thread.html/45081cf2c344f2e0de709a3e987749798ad60390bb93cab3a6ab6c25@%3Cdev.ofbiz.apache.org%3E] > Remove Deprecated Entities > -- > > Key: OFBIZ-9327 > URL: https://issues.apache.org/jira/browse/OFBIZ-9327 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Deepak Dixit >Assignee: Deepak Dixit >Priority: Minor > Fix For: Upcoming Release > > > We have deprecated entities define in entitymodel suffix with "Old", we can > remove these entities as they are too old. > [Deprecated Entities|https://cwiki.apache.org/confluence/x/KYBr] > [Dev list > discussion|https://lists.apache.org/thread.html/45081cf2c344f2e0de709a3e987749798ad60390bb93cab3a6ab6c25@%3Cdev.ofbiz.apache.org%3E] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (OFBIZ-9327) Remove Deprecated Entities
[ https://issues.apache.org/jira/browse/OFBIZ-9327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15985313#comment-15985313 ] Deepak Dixit edited comment on OFBIZ-9327 at 7/8/17 11:07 PM: -- Removed old data migration service at r#1792788 Added note on Data Migration doc as well. was (Author: deepak.dixit): Removed old data migration service at r#1792788 Added not on Data Migration doc as well. > Remove Deprecated Entities > -- > > Key: OFBIZ-9327 > URL: https://issues.apache.org/jira/browse/OFBIZ-9327 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Deepak Dixit >Assignee: Deepak Dixit >Priority: Minor > Fix For: Upcoming Release > > > We have deprecated entities define in entitymodel suffix with "Old", we can > remove these entities as they are too old. > [Deprecated Entities|https://cwiki.apache.org/confluence/x/KYBr] > [Dev list > discussion|https://lists.apache.org/thread.html/45081cf2c344f2e0de709a3e987749798ad60390bb93cab3a6ab6c25@%3Cdev.ofbiz.apache.org%3E] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OFBIZ-9377) fix tag "disable-if-empty" in menus if field has no value
[ https://issues.apache.org/jira/browse/OFBIZ-9377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Dixit closed OFBIZ-9377. --- Resolution: Fixed Fix Version/s: 16.11.04 > fix tag "disable-if-empty" in menus if field has no value > - > > Key: OFBIZ-9377 > URL: https://issues.apache.org/jira/browse/OFBIZ-9377 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Trunk >Reporter: Gaudin Pierre >Assignee: Deepak Dixit >Priority: Minor > Fix For: 16.11.04 > > Attachments: menu-disable-if-empty.patch > > > The purpose of this patch is to correct the behavior of the tag > "disable-if-empty" in menus. Indeed in certain cases it happens that the > value defines in "disable-if-empty" is present in the context but with no > valuee. In this case the menu item is shown while it should be masked. This > patch corrects it by testing if emptie and without value. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9377) fix tag "disable-if-empty" in menus if field has no value
[ https://issues.apache.org/jira/browse/OFBIZ-9377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079354#comment-16079354 ] Deepak Dixit commented on OFBIZ-9377: - Thanks Gaudin Pierre and Humera Khan for your contribution. This has been committed at ofbiz framework trunk at r#1801336 R16.11 at r#1801337 > fix tag "disable-if-empty" in menus if field has no value > - > > Key: OFBIZ-9377 > URL: https://issues.apache.org/jira/browse/OFBIZ-9377 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Trunk >Reporter: Gaudin Pierre >Assignee: Deepak Dixit >Priority: Minor > Attachments: menu-disable-if-empty.patch > > > The purpose of this patch is to correct the behavior of the tag > "disable-if-empty" in menus. Indeed in certain cases it happens that the > value defines in "disable-if-empty" is present in the context but with no > valuee. In this case the menu item is shown while it should be masked. This > patch corrects it by testing if emptie and without value. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9377) fix tag "disable-if-empty" in menus if field has no value
[ https://issues.apache.org/jira/browse/OFBIZ-9377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Dixit reassigned OFBIZ-9377: --- Assignee: Deepak Dixit > fix tag "disable-if-empty" in menus if field has no value > - > > Key: OFBIZ-9377 > URL: https://issues.apache.org/jira/browse/OFBIZ-9377 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Trunk >Reporter: Gaudin Pierre >Assignee: Deepak Dixit >Priority: Minor > Attachments: menu-disable-if-empty.patch > > > The purpose of this patch is to correct the behavior of the tag > "disable-if-empty" in menus. Indeed in certain cases it happens that the > value defines in "disable-if-empty" is present in the context but with no > valuee. In this case the menu item is shown while it should be masked. This > patch corrects it by testing if emptie and without value. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9377) fix tag "disable-if-empty" in menus if field has no value
[ https://issues.apache.org/jira/browse/OFBIZ-9377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079352#comment-16079352 ] Humera Khan commented on OFBIZ-9377: I have reviewed the patch and it looks good to me, Thank you for your work. > fix tag "disable-if-empty" in menus if field has no value > - > > Key: OFBIZ-9377 > URL: https://issues.apache.org/jira/browse/OFBIZ-9377 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Trunk >Reporter: Gaudin Pierre >Priority: Minor > Attachments: menu-disable-if-empty.patch > > > The purpose of this patch is to correct the behavior of the tag > "disable-if-empty" in menus. Indeed in certain cases it happens that the > value defines in "disable-if-empty" is present in the context but with no > valuee. In this case the menu item is shown while it should be masked. This > patch corrects it by testing if emptie and without value. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9460) Convert AgreementServices.xml mini-lang to groovyDSL
[ https://issues.apache.org/jira/browse/OFBIZ-9460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rishi Solanki updated OFBIZ-9460: - Attachment: OFBIZ-9460.patch Updated patch uses the groovy engine. Tested and verified the process. > Convert AgreementServices.xml mini-lang to groovyDSL > > > Key: OFBIZ-9460 > URL: https://issues.apache.org/jira/browse/OFBIZ-9460 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk >Reporter: Rishi Solanki >Assignee: Rishi Solanki > Attachments: OFBIZ-9460.patch, OFBIZ-9460.patch > > > This file covers two services as cancelAgreement and copyAgreement. > Need to follow practices in the parent ticket for this conversion. Ticket Id: > OFBIZ-9350. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9362) Screen rendering error on ViewForumMessage page
[ https://issues.apache.org/jira/browse/OFBIZ-9362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] priya sharma updated OFBIZ-9362: Attachment: OFBIz-9362.patch 1) Adding proper null check in the service in RenderSubContentCache.java, to avoid null pointer exceptions. 2) Removed the dataTemplateTypeId attribute from the TEMPLATE_TEXT_ONLY data resource for forum. The issue has been resolved. Please verify and let me know in case of any concerns. > Screen rendering error on ViewForumMessage page > --- > > Key: OFBIZ-9362 > URL: https://issues.apache.org/jira/browse/OFBIZ-9362 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Reporter: Aditya Sharma >Priority: Trivial > Attachments: OFBIz-9362.patch > > > Steps to reproduce: > 1. Go to Ecommerce component > (https://demo-trunk.ofbiz.apache.org/ecommerce/control/main) > 2. Click on Gizmos from Browse Forum > section.(https://demo-trunk.ofbiz.apache.org/ecommerce/control/showforum?forumId=GIZMOS) > 3. Click on View button > (https://demo-trunk.ofbiz.apache.org/ecommerce/control/ViewForumMessage?forumId=GIZMOS&responseContentId=thread10021&threadContentId=thread10021), > the message box shows an error message with ScreenRendererException. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-9475) Refactor serialize and non-serialize inventory item implementaion
Deepak Dixit created OFBIZ-9475: --- Summary: Refactor serialize and non-serialize inventory item implementaion Key: OFBIZ-9475 URL: https://issues.apache.org/jira/browse/OFBIZ-9475 Project: OFBiz Issue Type: Improvement Reporter: Deepak Dixit As discussed on dev mailing list [1][2] we need to refactor serialize and non-serialize inventory item design. As per current implementation serialize inventory item work on status and non-serialized inventory item work on inventory item detail. Proposed Design: - Use inventory item detail for both serialize and non-serialize inventory item. Only one additional condition for serialized inventory item that qoh can't be greater then one. - We can maintain inventory item status record for both type [1] http://markmail.org/thread/bd2bpiv6c5wvl7km [2] http://ofbiz.markmail.org/thread/kro5kcggp4fcose7 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9460) Convert AgreementServices.xml mini-lang to groovyDSL
[ https://issues.apache.org/jira/browse/OFBIZ-9460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rishi Solanki updated OFBIZ-9460: - Attachment: OFBIZ-9460.patch Here is the patch for the same. Need to do separate commit to remove the AgreementServices.xml > Convert AgreementServices.xml mini-lang to groovyDSL > > > Key: OFBIZ-9460 > URL: https://issues.apache.org/jira/browse/OFBIZ-9460 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk >Reporter: Rishi Solanki >Assignee: Rishi Solanki > Attachments: OFBIZ-9460.patch > > > This file covers two services as cancelAgreement and copyAgreement. > Need to follow practices in the parent ticket for this conversion. Ticket Id: > OFBIZ-9350. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9460) Convert AgreementServices.xml mini-lang to groovyDSL
[ https://issues.apache.org/jira/browse/OFBIZ-9460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rishi Solanki reassigned OFBIZ-9460: Assignee: Rishi Solanki (was: Saurabh Dixit) > Convert AgreementServices.xml mini-lang to groovyDSL > > > Key: OFBIZ-9460 > URL: https://issues.apache.org/jira/browse/OFBIZ-9460 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk >Reporter: Rishi Solanki >Assignee: Rishi Solanki > > This file covers two services as cancelAgreement and copyAgreement. > Need to follow practices in the parent ticket for this conversion. Ticket Id: > OFBIZ-9350. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9474) Set default value of max-retry to zero.
[ https://issues.apache.org/jira/browse/OFBIZ-9474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Patidar reassigned OFBIZ-9474: --- Assignee: Arun Patidar > Set default value of max-retry to zero. > --- > > Key: OFBIZ-9474 > URL: https://issues.apache.org/jira/browse/OFBIZ-9474 > Project: OFBiz > Issue Type: Improvement >Reporter: Ritesh Kumar >Assignee: Arun Patidar >Priority: Minor > Attachments: OFBIZ-9474.patch > > > Currently, the default value of the max-retry attribute (sets the max number > of times this service will retry when failed - persisted async only) of > service element is -1 which makes the service to retry unlimited times when > failed. > This has to be set to zero, so when the service fails, it does not retry. > However, it can be manually set to any value. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OFBIZ-9471) Set autocomplete to off for all the password fields.
[ https://issues.apache.org/jira/browse/OFBIZ-9471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Patidar closed OFBIZ-9471. --- Resolution: Fixed Fix Version/s: Upcoming Release Committed in plugin at revision 1801325 Committed in ofbiz-framework at revision 1801324 Thanks Ritesh Kumar for your contribution. > Set autocomplete to off for all the password fields. > > > Key: OFBIZ-9471 > URL: https://issues.apache.org/jira/browse/OFBIZ-9471 > Project: OFBiz > Issue Type: Bug > Components: framework >Reporter: Ritesh Kumar >Assignee: Arun Patidar >Priority: Minor > Fix For: Upcoming Release > > Attachments: OFBIZ-9471-FRAMEWORK.patch, OFBIZ-9471-PLUGIN.patch > > > The login and Forget password screens have password inputs. It is a best > practice to disable autocomplete on the password field as it will avoid > caching sensitive data on client site (CC numbers) and avoid storing the > password in an insecure and hackable client-site database. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9358) Integrating google phone number library for validating telecom numbers
[ https://issues.apache.org/jira/browse/OFBIZ-9358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Renuka Srishti updated OFBIZ-9358: -- Attachment: OFBIZ-9358.patch This patch contains following methods: splitPhoneNumber(String phoneNumber, Delegator delegator): It accepts a phoneNumber as a string and split the phoneNumber into countryCode, areaCode, and contactNumber. It returns a map which contains countryCode, areaCode, and contactNumber. isValidPhoneNumber(String phoneNumber, Delegator delegator): It returns true if parsed number is valid, or the number is either a possible fully-qualified number (containing the area code and country code), or if the number could be a possible local number (with a country code, but missing an area code). > Integrating google phone number library for validating telecom numbers > -- > > Key: OFBIZ-9358 > URL: https://issues.apache.org/jira/browse/OFBIZ-9358 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Upcoming Release >Reporter: Suraj Khurana >Assignee: Renuka Srishti > Attachments: OFBIZ-9358.patch > > > As per discussion at > https://lists.apache.org/list.html?d...@ofbiz.apache.org:lte=1M:Validating%20telecom%20numbers > Need to integrate Google telephone number to validate telephone numbers > formats of various countries. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9471) Set autocomplete to off for all the password fields.
[ https://issues.apache.org/jira/browse/OFBIZ-9471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Patidar reassigned OFBIZ-9471: --- Assignee: Arun Patidar > Set autocomplete to off for all the password fields. > > > Key: OFBIZ-9471 > URL: https://issues.apache.org/jira/browse/OFBIZ-9471 > Project: OFBiz > Issue Type: Bug > Components: framework >Reporter: Ritesh Kumar >Assignee: Arun Patidar >Priority: Minor > Attachments: OFBIZ-9471-FRAMEWORK.patch, OFBIZ-9471-PLUGIN.patch > > > The login and Forget password screens have password inputs. It is a best > practice to disable autocomplete on the password field as it will avoid > caching sensitive data on client site (CC numbers) and avoid storing the > password in an insecure and hackable client-site database. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9358) Integrating google phone number library for validating telecom numbers
[ https://issues.apache.org/jira/browse/OFBIZ-9358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Renuka Srishti reassigned OFBIZ-9358: - Assignee: Renuka Srishti > Integrating google phone number library for validating telecom numbers > -- > > Key: OFBIZ-9358 > URL: https://issues.apache.org/jira/browse/OFBIZ-9358 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Upcoming Release >Reporter: Suraj Khurana >Assignee: Renuka Srishti > > As per discussion at > https://lists.apache.org/list.html?d...@ofbiz.apache.org:lte=1M:Validating%20telecom%20numbers > Need to integrate Google telephone number to validate telephone numbers > formats of various countries. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OFBIZ-6774) ACCTG TRANS ENTRIES PDF link on invoiceOverview does not work
[
https://issues.apache.org/jira/browse/OFBIZ-6774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepak Dixit closed OFBIZ-6774.
---
Resolution: Fixed
Fix Version/s: 16.11.04
> ACCTG TRANS ENTRIES PDF link on invoiceOverview does not work
> -
>
> Key: OFBIZ-6774
> URL: https://issues.apache.org/jira/browse/OFBIZ-6774
> Project: OFBiz
> Issue Type: Bug
> Components: birt, order
>Affects Versions: Release Branch 13.07
> Environment: Ubuntu linux 15.04, JVM 7u91-2.6.3-0ubuntu0.15.04.1
>Reporter: Morten Jensen
>Assignee: Deepak Dixit
>Priority: Minor
> Fix For: 16.11.04
>
> Attachments: OFBIZ-6774_16.11.patch, OFBIZ-6774_trunk.patch
>
>
> Whenever I click on the ACCTG TRANS ENTRIES PDF link in the invoice overview
> screen I get the following error:
> org.ofbiz.webapp.control.RequestHandlerException: Unknown request
> [InvoiceAcctgTransEntriesPdf]; this request does not exist or cannot be
> called directly.
> A grep through the full ofbiz repo yields no results for an implementation or
> freemarker template - only the link itself in accounting menus xml:
> git checkout release13.07
> find . -type f -exec grep -i InvoiceAcctgTransEntriesPdf {} \; -ls
>
> 528005 72 -rw-rw-r-- 1 xxx xxx 70103 Dec 17 07:05
> ./applications/accounting/widget/AccountingMenus.xml
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OFBIZ-6774) ACCTG TRANS ENTRIES PDF link on invoiceOverview does not work
[
https://issues.apache.org/jira/browse/OFBIZ-6774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079306#comment-16079306
]
Deepak Dixit commented on OFBIZ-6774:
-
Backported to R16.11 at r#1801321
> ACCTG TRANS ENTRIES PDF link on invoiceOverview does not work
> -
>
> Key: OFBIZ-6774
> URL: https://issues.apache.org/jira/browse/OFBIZ-6774
> Project: OFBiz
> Issue Type: Bug
> Components: birt, order
>Affects Versions: Release Branch 13.07
> Environment: Ubuntu linux 15.04, JVM 7u91-2.6.3-0ubuntu0.15.04.1
>Reporter: Morten Jensen
>Assignee: Deepak Dixit
>Priority: Minor
> Fix For: 16.11.04
>
> Attachments: OFBIZ-6774_16.11.patch, OFBIZ-6774_trunk.patch
>
>
> Whenever I click on the ACCTG TRANS ENTRIES PDF link in the invoice overview
> screen I get the following error:
> org.ofbiz.webapp.control.RequestHandlerException: Unknown request
> [InvoiceAcctgTransEntriesPdf]; this request does not exist or cannot be
> called directly.
> A grep through the full ofbiz repo yields no results for an implementation or
> freemarker template - only the link itself in accounting menus xml:
> git checkout release13.07
> find . -type f -exec grep -i InvoiceAcctgTransEntriesPdf {} \; -ls
>
> 528005 72 -rw-rw-r-- 1 xxx xxx 70103 Dec 17 07:05
> ./applications/accounting/widget/AccountingMenus.xml
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OFBIZ-9471) Set autocomplete to off for all the password fields.
[ https://issues.apache.org/jira/browse/OFBIZ-9471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ritesh Kumar updated OFBIZ-9471: Description: The login and Forget password screens have password inputs. It is a best practice to disable autocomplete on the password field as it will avoid caching sensitive data on client site (CC numbers) and avoid storing the password in an insecure and hackable client-site database. (was: The login and Forget password screens have password inputs. It is a best practice to disable autocomplete on the password field as it will avoid caching sensitive data on client site (CC numbers) and avoid storing the password in an insecure and hackable client-site database) > Set autocomplete to off for all the password fields. > > > Key: OFBIZ-9471 > URL: https://issues.apache.org/jira/browse/OFBIZ-9471 > Project: OFBiz > Issue Type: Bug > Components: framework >Reporter: Ritesh Kumar >Priority: Minor > Attachments: OFBIZ-9471-FRAMEWORK.patch, OFBIZ-9471-PLUGIN.patch > > > The login and Forget password screens have password inputs. It is a best > practice to disable autocomplete on the password field as it will avoid > caching sensitive data on client site (CC numbers) and avoid storing the > password in an insecure and hackable client-site database. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9471) Set autocomplete to off for all the password fields.
[ https://issues.apache.org/jira/browse/OFBIZ-9471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ritesh Kumar updated OFBIZ-9471: Description: The login and Forget password screens have password inputs. It is a best practice to disable autocomplete on the password field as it will avoid caching sensitive data on client site (CC numbers) and avoid storing the password in an insecure and hackable client-site database (was: The login and Forget password screens have password inputs. It is a best practice to disable autocomplete on the password field.) > Set autocomplete to off for all the password fields. > > > Key: OFBIZ-9471 > URL: https://issues.apache.org/jira/browse/OFBIZ-9471 > Project: OFBiz > Issue Type: Bug > Components: framework >Reporter: Ritesh Kumar >Priority: Minor > Attachments: OFBIZ-9471-FRAMEWORK.patch, OFBIZ-9471-PLUGIN.patch > > > The login and Forget password screens have password inputs. It is a best > practice to disable autocomplete on the password field as it will avoid > caching sensitive data on client site (CC numbers) and avoid storing the > password in an insecure and hackable client-site database -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-6774) ACCTG TRANS ENTRIES PDF link on invoiceOverview does not work
[
https://issues.apache.org/jira/browse/OFBIZ-6774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079302#comment-16079302
]
Arun Patidar commented on OFBIZ-6774:
-
Committed in ofbiz framework trunk at revision 1801320.
Thanks Morten and Ankit Joshi for your contribution.
> ACCTG TRANS ENTRIES PDF link on invoiceOverview does not work
> -
>
> Key: OFBIZ-6774
> URL: https://issues.apache.org/jira/browse/OFBIZ-6774
> Project: OFBiz
> Issue Type: Bug
> Components: birt, order
>Affects Versions: Release Branch 13.07
> Environment: Ubuntu linux 15.04, JVM 7u91-2.6.3-0ubuntu0.15.04.1
>Reporter: Morten Jensen
>Assignee: Deepak Dixit
>Priority: Minor
> Attachments: OFBIZ-6774_16.11.patch, OFBIZ-6774_trunk.patch
>
>
> Whenever I click on the ACCTG TRANS ENTRIES PDF link in the invoice overview
> screen I get the following error:
> org.ofbiz.webapp.control.RequestHandlerException: Unknown request
> [InvoiceAcctgTransEntriesPdf]; this request does not exist or cannot be
> called directly.
> A grep through the full ofbiz repo yields no results for an implementation or
> freemarker template - only the link itself in accounting menus xml:
> git checkout release13.07
> find . -type f -exec grep -i InvoiceAcctgTransEntriesPdf {} \; -ls
>
> 528005 72 -rw-rw-r-- 1 xxx xxx 70103 Dec 17 07:05
> ./applications/accounting/widget/AccountingMenus.xml
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OFBIZ-9470) Missing productId in input field after Atp/Qoh button is clicked on create PO screen
[ https://issues.apache.org/jira/browse/OFBIZ-9470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Patidar closed OFBIZ-9470. --- Resolution: Fixed Committed in ofbiz framework at revision 1801319. Thanks Pallavi for your contribution. > Missing productId in input field after Atp/Qoh button is clicked on create PO > screen > > > Key: OFBIZ-9470 > URL: https://issues.apache.org/jira/browse/OFBIZ-9470 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk >Reporter: Pallavi Goyal >Assignee: Arun Patidar >Priority: Minor > Fix For: Upcoming Release > > Attachments: missing-productId.png, OFBIZ-9470.patch > > > *Steps to regenerate -* > 1. Go to "Order" component. > 2. Click on [ Order Entry ] menu button. > 3. Fill the details in "Purchase Order" section and click on continue. > 4. Fill the required order details and click on continue. > 5. Open the product lookup table and select a product. > 6. Click on [ Atp/Qoh ] button. > The issue generated is - > The productId vanishes from the input field. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9474) Set default value of max-retry to zero.
[ https://issues.apache.org/jira/browse/OFBIZ-9474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ritesh Kumar updated OFBIZ-9474: Attachment: OFBIZ-9474.patch > Set default value of max-retry to zero. > --- > > Key: OFBIZ-9474 > URL: https://issues.apache.org/jira/browse/OFBIZ-9474 > Project: OFBiz > Issue Type: Improvement >Reporter: Ritesh Kumar >Priority: Minor > Attachments: OFBIZ-9474.patch > > > Currently, the default value of the max-retry attribute (sets the max number > of times this service will retry when failed - persisted async only) of > service element is -1 which makes the service to retry unlimited times when > failed. > This has to be set to zero, so when the service fails, it does not retry. > However, it can be manually set to any value. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9470) Missing productId in input field after Atp/Qoh button is clicked on create PO screen
[ https://issues.apache.org/jira/browse/OFBIZ-9470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Patidar reassigned OFBIZ-9470: --- Assignee: Arun Patidar > Missing productId in input field after Atp/Qoh button is clicked on create PO > screen > > > Key: OFBIZ-9470 > URL: https://issues.apache.org/jira/browse/OFBIZ-9470 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk >Reporter: Pallavi Goyal >Assignee: Arun Patidar >Priority: Minor > Fix For: Upcoming Release > > Attachments: missing-productId.png, OFBIZ-9470.patch > > > *Steps to regenerate -* > 1. Go to "Order" component. > 2. Click on [ Order Entry ] menu button. > 3. Fill the details in "Purchase Order" section and click on continue. > 4. Fill the required order details and click on continue. > 5. Open the product lookup table and select a product. > 6. Click on [ Atp/Qoh ] button. > The issue generated is - > The productId vanishes from the input field. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OFBIZ-9468) UI issue in ATP/QOH table on Create Purchase Order screen
[ https://issues.apache.org/jira/browse/OFBIZ-9468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Patidar closed OFBIZ-9468. --- Resolution: Fixed Committed revision 1801318. Thanks Pallavi for your contribution. > UI issue in ATP/QOH table on Create Purchase Order screen > - > > Key: OFBIZ-9468 > URL: https://issues.apache.org/jira/browse/OFBIZ-9468 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk >Reporter: Pallavi Goyal >Assignee: Arun Patidar >Priority: Minor > Fix For: Upcoming Release > > Attachments: atp-qoh-table-issue.png, OFBIZ-9468.patch > > > *Steps to regenerate -* > 1. Go to "Order" component. > 2. Click on [ Order Entry ] menu button. > 3. Fill the details in "Purchase Order" section and click on continue. > 4. Fill the required order details and click on continue. > 5. Open the product lookup table and select a product. > 6. Click on [ Atp/Qoh ] button. > The issue generated is- > The table showing ATP and QOH is not in proper format. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9468) UI issue in ATP/QOH table on Create Purchase Order screen
[ https://issues.apache.org/jira/browse/OFBIZ-9468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Patidar reassigned OFBIZ-9468: --- Assignee: Arun Patidar > UI issue in ATP/QOH table on Create Purchase Order screen > - > > Key: OFBIZ-9468 > URL: https://issues.apache.org/jira/browse/OFBIZ-9468 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk >Reporter: Pallavi Goyal >Assignee: Arun Patidar >Priority: Minor > Fix For: Upcoming Release > > Attachments: atp-qoh-table-issue.png, OFBIZ-9468.patch > > > *Steps to regenerate -* > 1. Go to "Order" component. > 2. Click on [ Order Entry ] menu button. > 3. Fill the details in "Purchase Order" section and click on continue. > 4. Fill the required order details and click on continue. > 5. Open the product lookup table and select a product. > 6. Click on [ Atp/Qoh ] button. > The issue generated is- > The table showing ATP and QOH is not in proper format. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-9474) Set default value of max-retry to zero.
Ritesh Kumar created OFBIZ-9474: --- Summary: Set default value of max-retry to zero. Key: OFBIZ-9474 URL: https://issues.apache.org/jira/browse/OFBIZ-9474 Project: OFBiz Issue Type: Improvement Reporter: Ritesh Kumar Priority: Minor Currently, the default value of the max-retry attribute (sets the max number of times this service will retry when failed - persisted async only) of service element is -1 which makes the service to retry unlimited times when failed. This has to be set to zero, so when the service fails, it does not retry. However, it can be manually set to any value. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9469) POC: Using JSF
[ https://issues.apache.org/jira/browse/OFBIZ-9469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079287#comment-16079287 ] James Yong commented on OFBIZ-9469: --- Hi [~mbrohl], I wanted to do complex forms like the picture below. Since JSF is also using declarative UI and has functions similar to OFBiz Widget's decorator-screen & action tags, I think it may get better acceptance from the developer community than using a purely javascript framework. Another good thing is that there is no request/view mapping required for JSF. I am also open to other alternatives to allow OFBiz to build forms that are on par with other ERP system. At the end of the day, I hope to focus more on contributing business-related functionality rather than the UI framework. Best Regards, James !https://smist08.files.wordpress.com/2015/07/cna2arinv.png|width=600px! > POC: Using JSF > -- > > Key: OFBIZ-9469 > URL: https://issues.apache.org/jira/browse/OFBIZ-9469 > Project: OFBiz > Issue Type: New Feature >Reporter: James Yong >Priority: Minor > Attachments: OFBIZ-9469.patch > > > JavaServerFaces (JSF) can be used to build Rich Internet Applications which > is suitable for business-facing part of an ERP system. > Some Advantages > == > JSF is similar to OFBiz widget; both can use declarative XML UI. > JSF can map directly to a backing bean and doesn't requires any request > mapping. > JSF also allows the direct coding of HTML within the XML, while OFBiz widgets > need to link to external FTL file. > I have done some initial work to add JSF capabilities for developers to > evaluate its suitability further. It is also possible to render OFBiz Widgets > (for reuse) and programmatically placed within JSF, but I haven't go into it > yet. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OFBIZ-9461) Alignment issue at Catalog Manager page
[ https://issues.apache.org/jira/browse/OFBIZ-9461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Patidar closed OFBIZ-9461. --- Resolution: Fixed Fix Version/s: Upcoming Release Committed in ofbiz framework revision 1801316. Thanks Sanjay Yadav and Humera Khan for your contribution. > Alignment issue at Catalog Manager page > > > Key: OFBIZ-9461 > URL: https://issues.apache.org/jira/browse/OFBIZ-9461 > Project: OFBiz > Issue Type: Bug >Reporter: Sanjay Yadav >Assignee: Arun Patidar >Priority: Minor > Labels: catalog > Fix For: Upcoming Release > > Attachments: AlignmentAfterAddingConditionAndAction.png, > AlignmentBugAtCatalogPriceRuleSection.png, AlignmentWithRemoveButton.png, > OFBIZ-9461.patch > > > Go to: > Application -> Catalog Manager -> Price Rule > Actual - From Date, Through Date and Update section is not properly aligned. > Also due this horizontal scroll appearing at page. > Expected - Fix this alignment issue and Horizontal scroll should not be > appear. > Please refer attached screen shot. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9473) Status of communication event role is marked "Read" on View Communication Event page.
[ https://issues.apache.org/jira/browse/OFBIZ-9473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Goyal updated OFBIZ-9473: - Attachment: OFBIZ-9473.patch *Steps to verify -* 1. Follow the steps in description. 2. On view communication page, in "Communication Event Role" section, the statuses should be- "Addressee" --> "Created" "Originator" --> "Closed" Removed the service "setCommEventRoleToRead" from the screens "ViewCommunicationEvent" and "MyCommunicationEvents". > Status of communication event role is marked "Read" on View Communication > Event page. > - > > Key: OFBIZ-9473 > URL: https://issues.apache.org/jira/browse/OFBIZ-9473 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: Trunk >Reporter: Pallavi Goyal > Fix For: Upcoming Release > > Attachments: OFBIZ-9473.patch > > > *Steps to regenerate -* > 1. Go to "Party" component. > 2. Click on [ Communications ] menu tab. > 3. Find communication events. > 4. Open any communication event view page for "Addressee" role from Find > Communication Event page. > Actual - The role status of communication is marked "Read" on viewing > communication. > Expected - There is no change in the role status of the communication event. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9461) Alignment issue at Catalog Manager page
[ https://issues.apache.org/jira/browse/OFBIZ-9461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Patidar reassigned OFBIZ-9461: --- Assignee: Arun Patidar > Alignment issue at Catalog Manager page > > > Key: OFBIZ-9461 > URL: https://issues.apache.org/jira/browse/OFBIZ-9461 > Project: OFBiz > Issue Type: Bug >Reporter: Sanjay Yadav >Assignee: Arun Patidar >Priority: Minor > Labels: catalog > Attachments: AlignmentAfterAddingConditionAndAction.png, > AlignmentBugAtCatalogPriceRuleSection.png, AlignmentWithRemoveButton.png, > OFBIZ-9461.patch > > > Go to: > Application -> Catalog Manager -> Price Rule > Actual - From Date, Through Date and Update section is not properly aligned. > Also due this horizontal scroll appearing at page. > Expected - Fix this alignment issue and Horizontal scroll should not be > appear. > Please refer attached screen shot. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OFBIZ-9466) Use serviceUtil() in place of hard-coded error/success messages.
[ https://issues.apache.org/jira/browse/OFBIZ-9466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Patidar closed OFBIZ-9466. --- Resolution: Fixed Fix Version/s: Upcoming Release Committed changes in ofbiz -framework revision 1801313. Thanks Pawan for your contribution. > Use serviceUtil() in place of hard-coded error/success messages. > > > Key: OFBIZ-9466 > URL: https://issues.apache.org/jira/browse/OFBIZ-9466 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Pawan Verma >Assignee: Arun Patidar >Priority: Minor > Fix For: Upcoming Release > > Attachments: OFBIZ-9466.patch > > > Use serviceUtil() in place of hard-coded error/success messages. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9471) Set autocomplete to off for all the password fields.
[ https://issues.apache.org/jira/browse/OFBIZ-9471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ritesh Kumar updated OFBIZ-9471: Attachment: OFBIZ-9471-FRAMEWORK.patch OFBIZ-9471-PLUGIN.patch > Set autocomplete to off for all the password fields. > > > Key: OFBIZ-9471 > URL: https://issues.apache.org/jira/browse/OFBIZ-9471 > Project: OFBiz > Issue Type: Bug > Components: framework >Reporter: Ritesh Kumar >Priority: Minor > Attachments: OFBIZ-9471-FRAMEWORK.patch, OFBIZ-9471-PLUGIN.patch > > > The login and Forget password screens have password inputs. It is a best > practice to disable autocomplete on the password field. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OFBIZ-9413) Update Currency Uom data
[ https://issues.apache.org/jira/browse/OFBIZ-9413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Dixit resolved OFBIZ-9413. - Resolution: Fixed > Update Currency Uom data > - > > Key: OFBIZ-9413 > URL: https://issues.apache.org/jira/browse/OFBIZ-9413 > Project: OFBiz > Issue Type: Improvement >Reporter: Deepak Dixit >Assignee: Deepak Dixit > Fix For: 16.11.03, Release Branch 15.12, Release Branch 14.12 > > Attachments: list_three.xls, OFBIZ-9413.patch > > > While adding numericCode to currency UOM, I found that we need to update > some old currency UOM, as uomId has been updated. > https://www.currency-iso.org/en/home/tables/table-a1.html > https://www.currency-iso.org/en/home/amendments.html > Here is the short summary > *Following UomId not found* > * Santo Domiongo(CDP) > * Brazil (BRR) > * Argentinian Austral(ARA) > * Andoran peseta(ADP) > * Maltese Lira (MTL) > * Mexican Peso (old)(MXP) > * Peruvian Inti(PEI) > * Peruvian Sol(PES) > * Tadzhikistani Ruble(TJR) > *Following UOM using other currency* > Used Other > * ANDORRA == Euro > * Cyprus Pound(CYP) == Euro > * Ecuador Sucre(ECS) = USD > * Estonian Krone(EEK) = EURO > * Lithuanian Lita(LTL) == EURO > * Latvian Lat(LVL) == EURO > * Timor Escudo(TPE) == US Dollor > *Following UOM has been changed* > ||Old||New|| > |Belorussian Ruble(BYR)|Belarusian Ruble(BYN)| > |Bosnia-Herzogovinian Dinar(BAD)|Convertible Mark(BAM)| > |Azerbaijan Manat (AZM)|Azerbaijan Manat(AZN)| > |Angolan Kwanza (AOK)|Kwanza (AOA)| > |Afghani (AFA)|Afghani(AFN)| > |Dominican Republic Peso(DRP)|Dominican Peso (DOP)| > |Ghanian Cedi(GHC)|Ghana Cedi(GHS)| > |Guinea Peso(GWP)| Guinean Franc(GNF)| > |Kirghizstan Som(KIS)|KYRGYZSTAN Som (KGS)| > |Madagascan Franc(MGF)|Malagasy Ariary(MGA)| > |Mozambique Metical(MZM)|Mozambique Metical(MZN)| > |Nicaragua (NIC)|Cordoba Oro (NIO)| > |New Israeli Shekel(NIS)|New Israeli Sheqel (ILS)| > |Poland(PLZ)|Zloty (PLN)| > |Romanian Leu(ROL)|Romanian Leu(RON)| > |Russian Rouble(RUR)|Russian Ruble(RUB)| > |Sudanese Pound(SDP)|Sudanese Pound(SDG)| > |Peru (SOL)|Sol (PEN)| > |Surinam Guilder(SRG)|Surinam Dollar (SRD)| > |Turkmenistani Manat(TMM)|Turkmenistan New Manat(TMT)| > |Uganda Shilling(UGS)|Uganda Shilling(UGX)| > |Uruguayan New Peso(UYP)|Uruguay Peso en Unidades Indexadas (URUIURUI)(UYI)| > |Venezuelan Bolivar(VEB)|Bolívar(VEF)| > |Zambian Kwacha(ZMK)|Zambian Kwacha(ZMW)| > |Zimbabwean Dollar(ZWD)|Zimbabwe Dollar(ZWL)| > |Georgian Kupon (GEK)|GEORGIA Lari (GEL)| > Some currency codes moved to historic denominations, we can remove them from > data. > https://www.currency-iso.org/en/home/tables/table-a3.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9413) Update Currency Uom data
[ https://issues.apache.org/jira/browse/OFBIZ-9413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079274#comment-16079274 ] Deepak Dixit commented on OFBIZ-9413: - Thanks Jacques, This has been fixed at ofbiz framework trunk at r#1801311 and r#1801312 > Update Currency Uom data > - > > Key: OFBIZ-9413 > URL: https://issues.apache.org/jira/browse/OFBIZ-9413 > Project: OFBiz > Issue Type: Improvement >Reporter: Deepak Dixit >Assignee: Deepak Dixit > Fix For: Release Branch 14.12, Release Branch 15.12, 16.11.03 > > Attachments: list_three.xls, OFBIZ-9413.patch > > > While adding numericCode to currency UOM, I found that we need to update > some old currency UOM, as uomId has been updated. > https://www.currency-iso.org/en/home/tables/table-a1.html > https://www.currency-iso.org/en/home/amendments.html > Here is the short summary > *Following UomId not found* > * Santo Domiongo(CDP) > * Brazil (BRR) > * Argentinian Austral(ARA) > * Andoran peseta(ADP) > * Maltese Lira (MTL) > * Mexican Peso (old)(MXP) > * Peruvian Inti(PEI) > * Peruvian Sol(PES) > * Tadzhikistani Ruble(TJR) > *Following UOM using other currency* > Used Other > * ANDORRA == Euro > * Cyprus Pound(CYP) == Euro > * Ecuador Sucre(ECS) = USD > * Estonian Krone(EEK) = EURO > * Lithuanian Lita(LTL) == EURO > * Latvian Lat(LVL) == EURO > * Timor Escudo(TPE) == US Dollor > *Following UOM has been changed* > ||Old||New|| > |Belorussian Ruble(BYR)|Belarusian Ruble(BYN)| > |Bosnia-Herzogovinian Dinar(BAD)|Convertible Mark(BAM)| > |Azerbaijan Manat (AZM)|Azerbaijan Manat(AZN)| > |Angolan Kwanza (AOK)|Kwanza (AOA)| > |Afghani (AFA)|Afghani(AFN)| > |Dominican Republic Peso(DRP)|Dominican Peso (DOP)| > |Ghanian Cedi(GHC)|Ghana Cedi(GHS)| > |Guinea Peso(GWP)| Guinean Franc(GNF)| > |Kirghizstan Som(KIS)|KYRGYZSTAN Som (KGS)| > |Madagascan Franc(MGF)|Malagasy Ariary(MGA)| > |Mozambique Metical(MZM)|Mozambique Metical(MZN)| > |Nicaragua (NIC)|Cordoba Oro (NIO)| > |New Israeli Shekel(NIS)|New Israeli Sheqel (ILS)| > |Poland(PLZ)|Zloty (PLN)| > |Romanian Leu(ROL)|Romanian Leu(RON)| > |Russian Rouble(RUR)|Russian Ruble(RUB)| > |Sudanese Pound(SDP)|Sudanese Pound(SDG)| > |Peru (SOL)|Sol (PEN)| > |Surinam Guilder(SRG)|Surinam Dollar (SRD)| > |Turkmenistani Manat(TMM)|Turkmenistan New Manat(TMT)| > |Uganda Shilling(UGS)|Uganda Shilling(UGX)| > |Uruguayan New Peso(UYP)|Uruguay Peso en Unidades Indexadas (URUIURUI)(UYI)| > |Venezuelan Bolivar(VEB)|Bolívar(VEF)| > |Zambian Kwacha(ZMK)|Zambian Kwacha(ZMW)| > |Zimbabwean Dollar(ZWD)|Zimbabwe Dollar(ZWL)| > |Georgian Kupon (GEK)|GEORGIA Lari (GEL)| > Some currency codes moved to historic denominations, we can remove them from > data. > https://www.currency-iso.org/en/home/tables/table-a3.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OFBIZ-9413) Update Currency Uom data
[ https://issues.apache.org/jira/browse/OFBIZ-9413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Dixit closed OFBIZ-9413. --- > Update Currency Uom data > - > > Key: OFBIZ-9413 > URL: https://issues.apache.org/jira/browse/OFBIZ-9413 > Project: OFBiz > Issue Type: Improvement >Reporter: Deepak Dixit >Assignee: Deepak Dixit > Fix For: Release Branch 14.12, Release Branch 15.12, 16.11.03 > > Attachments: list_three.xls, OFBIZ-9413.patch > > > While adding numericCode to currency UOM, I found that we need to update > some old currency UOM, as uomId has been updated. > https://www.currency-iso.org/en/home/tables/table-a1.html > https://www.currency-iso.org/en/home/amendments.html > Here is the short summary > *Following UomId not found* > * Santo Domiongo(CDP) > * Brazil (BRR) > * Argentinian Austral(ARA) > * Andoran peseta(ADP) > * Maltese Lira (MTL) > * Mexican Peso (old)(MXP) > * Peruvian Inti(PEI) > * Peruvian Sol(PES) > * Tadzhikistani Ruble(TJR) > *Following UOM using other currency* > Used Other > * ANDORRA == Euro > * Cyprus Pound(CYP) == Euro > * Ecuador Sucre(ECS) = USD > * Estonian Krone(EEK) = EURO > * Lithuanian Lita(LTL) == EURO > * Latvian Lat(LVL) == EURO > * Timor Escudo(TPE) == US Dollor > *Following UOM has been changed* > ||Old||New|| > |Belorussian Ruble(BYR)|Belarusian Ruble(BYN)| > |Bosnia-Herzogovinian Dinar(BAD)|Convertible Mark(BAM)| > |Azerbaijan Manat (AZM)|Azerbaijan Manat(AZN)| > |Angolan Kwanza (AOK)|Kwanza (AOA)| > |Afghani (AFA)|Afghani(AFN)| > |Dominican Republic Peso(DRP)|Dominican Peso (DOP)| > |Ghanian Cedi(GHC)|Ghana Cedi(GHS)| > |Guinea Peso(GWP)| Guinean Franc(GNF)| > |Kirghizstan Som(KIS)|KYRGYZSTAN Som (KGS)| > |Madagascan Franc(MGF)|Malagasy Ariary(MGA)| > |Mozambique Metical(MZM)|Mozambique Metical(MZN)| > |Nicaragua (NIC)|Cordoba Oro (NIO)| > |New Israeli Shekel(NIS)|New Israeli Sheqel (ILS)| > |Poland(PLZ)|Zloty (PLN)| > |Romanian Leu(ROL)|Romanian Leu(RON)| > |Russian Rouble(RUR)|Russian Ruble(RUB)| > |Sudanese Pound(SDP)|Sudanese Pound(SDG)| > |Peru (SOL)|Sol (PEN)| > |Surinam Guilder(SRG)|Surinam Dollar (SRD)| > |Turkmenistani Manat(TMM)|Turkmenistan New Manat(TMT)| > |Uganda Shilling(UGS)|Uganda Shilling(UGX)| > |Uruguayan New Peso(UYP)|Uruguay Peso en Unidades Indexadas (URUIURUI)(UYI)| > |Venezuelan Bolivar(VEB)|Bolívar(VEF)| > |Zambian Kwacha(ZMK)|Zambian Kwacha(ZMW)| > |Zimbabwean Dollar(ZWD)|Zimbabwe Dollar(ZWL)| > |Georgian Kupon (GEK)|GEORGIA Lari (GEL)| > Some currency codes moved to historic denominations, we can remove them from > data. > https://www.currency-iso.org/en/home/tables/table-a3.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OFBIZ-9457) Improvements in OrderHeader entity definition and services
[ https://issues.apache.org/jira/browse/OFBIZ-9457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Patidar closed OFBIZ-9457. --- Resolution: Fixed Assignee: Arun Patidar Fix Version/s: Upcoming Release Committed changes in ofbiz framework at revision 1801310. Thanks Rishi Solanki and Aishwary for your contribution. > Improvements in OrderHeader entity definition and services > -- > > Key: OFBIZ-9457 > URL: https://issues.apache.org/jira/browse/OFBIZ-9457 > Project: OFBiz > Issue Type: Sub-task > Components: order >Affects Versions: Trunk >Reporter: Rishi Solanki >Assignee: Arun Patidar >Priority: Minor > Fix For: Upcoming Release > > Attachments: OFBIZ-9457.diff, OFBIZ-9457.patch > > > Fix entity definition of OrderHeader and do the following changes in the > implementation; > - Remove relations with OrderHeaderNoteView and OrderItemAndShipGroupAssoc > from the entity definition. > - Check for the both views used at any place as getRelated() generic value > methods on OrderHeader then change them with appropriate EntityQuery method > or delegaor or other script as applicable. > - Few find areas are; > -- AddItemsFromOrder.groovy > -- ReceiveInventoryAgainstPurchaseOrder.groovy > Note: As we are removing relation from OrderHeader so only need to work on > the items where we are trying to get related data by using the relations. We > need to rewrite only those lines of code. Reverse in not true. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9472) Human Resource page throwing unwanted exceptions
[ https://issues.apache.org/jira/browse/OFBIZ-9472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Yadav reassigned OFBIZ-9472: --- Assignee: Sanjay Yadav > Human Resource page throwing unwanted exceptions > > > Key: OFBIZ-9472 > URL: https://issues.apache.org/jira/browse/OFBIZ-9472 > Project: OFBiz > Issue Type: Bug > Components: humanres >Reporter: Sanjay Yadav >Assignee: Sanjay Yadav > Attachments: UnwantedExceptionsatHRpage.PNG > > > Go to: > Application Url -> HR > Actual - Human Resource page throwing unwanted exceptions. > Expected - Please fix unwanted exception bug. > Please refer attached screen shot for quick reference. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OFBIZ-9472) Human Resource page throwing unwanted exceptions
[ https://issues.apache.org/jira/browse/OFBIZ-9472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Yadav closed OFBIZ-9472. --- Resolution: Cannot Reproduce > Human Resource page throwing unwanted exceptions > > > Key: OFBIZ-9472 > URL: https://issues.apache.org/jira/browse/OFBIZ-9472 > Project: OFBiz > Issue Type: Bug > Components: humanres >Reporter: Sanjay Yadav >Assignee: Sanjay Yadav > Attachments: UnwantedExceptionsatHRpage.PNG > > > Go to: > Application Url -> HR > Actual - Human Resource page throwing unwanted exceptions. > Expected - Please fix unwanted exception bug. > Please refer attached screen shot for quick reference. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9472) Human Resource page throwing unwanted exceptions
[ https://issues.apache.org/jira/browse/OFBIZ-9472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079269#comment-16079269 ] Sanjay Yadav commented on OFBIZ-9472: - Sure, Devanshu. Unable to recreate it at trunk. Hence, closing it. thanks! > Human Resource page throwing unwanted exceptions > > > Key: OFBIZ-9472 > URL: https://issues.apache.org/jira/browse/OFBIZ-9472 > Project: OFBiz > Issue Type: Bug > Components: humanres >Reporter: Sanjay Yadav > Attachments: UnwantedExceptionsatHRpage.PNG > > > Go to: > Application Url -> HR > Actual - Human Resource page throwing unwanted exceptions. > Expected - Please fix unwanted exception bug. > Please refer attached screen shot for quick reference. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OFBIZ-9328) Create New button is misplaced on Party Content Screen
[ https://issues.apache.org/jira/browse/OFBIZ-9328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Patidar closed OFBIZ-9328. --- Resolution: Fixed Fix Version/s: Upcoming Release Committed in ofbiz framework at revision 1801308 Thanks Devanshu and Humera for your contribution. > Create New button is misplaced on Party Content Screen > -- > > Key: OFBIZ-9328 > URL: https://issues.apache.org/jira/browse/OFBIZ-9328 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: Trunk >Reporter: Devanshu Vyas >Assignee: Arun Patidar >Priority: Minor > Fix For: Upcoming Release > > Attachments: CreateNewButton.png, OFBIZ-9328.patch, OFBIZ-9328.patch > > > The Create New button is wrongly placed on the Party Content screen(navigated > from a Party Profile screen). The button should be placed outside of the > Content List section instead of inside. (CreateNewButton.png) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9472) Human Resource page throwing unwanted exceptions
[ https://issues.apache.org/jira/browse/OFBIZ-9472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079267#comment-16079267 ] Devanshu Vyas commented on OFBIZ-9472: -- This issue is not regenerating on trunk. I think we can close this ticket. > Human Resource page throwing unwanted exceptions > > > Key: OFBIZ-9472 > URL: https://issues.apache.org/jira/browse/OFBIZ-9472 > Project: OFBiz > Issue Type: Bug > Components: humanres >Reporter: Sanjay Yadav > Attachments: UnwantedExceptionsatHRpage.PNG > > > Go to: > Application Url -> HR > Actual - Human Resource page throwing unwanted exceptions. > Expected - Please fix unwanted exception bug. > Please refer attached screen shot for quick reference. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (OFBIZ-9413) Update Currency Uom data
[
https://issues.apache.org/jira/browse/OFBIZ-9413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux reopened OFBIZ-9413:
Hi Deepak,
This introduced duplicates for "Uom.description.ILS" which is the right ISO
code (https://www.quora.com/Israeli-currency-is-NIS-or-ILS)
It seems to me that the ones under the same label than "New Israeli Shekel"
should be kept, but for instance the French one need to be amended (wrong
translation). I suggest this patch:
{code}
Index: framework/common/config/CommonEntityLabels.xml
===
--- framework/common/config/CommonEntityLabels.xml (revision 1801301)
+++ framework/common/config/CommonEntityLabels.xml (working copy)
@@ -18862,21 +18862,6 @@
爱尔兰镑
愛爾è˜éŽŠ
-
-شكيل إسرائيلي
-Scheckel Israel
-Israeli Scheckel
-Scheckel israélien
-Scheckel Israeliano
-イスラエル・シェケル
-Israeli Scheckel
-Israel Scheckel
-Scheckel Israelian
-Израиль�кий шекель
-เชคเ�ิล
à¸à¸´à¸ªà¸£à¸²à¹€à¸à¸¥
-以色列谢克尔
-以色列�克爾
-
روبية هندية
Rupie Indien
@@ -19889,7 +19874,7 @@
الشيكل الإسرائيلي
الجديد
New Israeli Shekel
-Shekel du nouvel Israël
+Nouveau shekel
Shekel Nuovo Israele
イスラエル・新シェケル
New Israeli Shekel
{code}
> Update Currency Uom data
> -
>
> Key: OFBIZ-9413
> URL: https://issues.apache.org/jira/browse/OFBIZ-9413
> Project: OFBiz
> Issue Type: Improvement
>Reporter: Deepak Dixit
>Assignee: Deepak Dixit
> Fix For: Release Branch 14.12, Release Branch 15.12, 16.11.03
>
> Attachments: list_three.xls, OFBIZ-9413.patch
>
>
> While adding numericCode to currency UOM, I found that we need to update
> some old currency UOM, as uomId has been updated.
> https://www.currency-iso.org/en/home/tables/table-a1.html
> https://www.currency-iso.org/en/home/amendments.html
> Here is the short summary
> *Following UomId not found*
> * Santo Domiongo(CDP)
> * Brazil (BRR)
> * Argentinian Austral(ARA)
> * Andoran peseta(ADP)
> * Maltese Lira (MTL)
> * Mexican Peso (old)(MXP)
> * Peruvian Inti(PEI)
> * Peruvian Sol(PES)
> * Tadzhikistani Ruble(TJR)
> *Following UOM using other currency*
> Used Other
> * ANDORRA == Euro
> * Cyprus Pound(CYP) == Euro
> * Ecuador Sucre(ECS) = USD
> * Estonian Krone(EEK) = EURO
> * Lithuanian Lita(LTL) == EURO
> * Latvian Lat(LVL) == EURO
> * Timor Escudo(TPE) == US Dollor
> *Following UOM has been changed*
> ||Old||New||
> |Belorussian Ruble(BYR)|Belarusian Ruble(BYN)|
> |Bosnia-Herzogovinian Dinar(BAD)|Convertible Mark(BAM)|
> |Azerbaijan Manat (AZM)|Azerbaijan Manat(AZN)|
> |Angolan Kwanza (AOK)|Kwanza (AOA)|
> |Afghani (AFA)|Afghani(AFN)|
> |Dominican Republic Peso(DRP)|Dominican Peso (DOP)|
> |Ghanian Cedi(GHC)|Ghana Cedi(GHS)|
> |Guinea Peso(GWP)| Guinean Franc(GNF)|
> |Kirghizstan Som(KIS)|KYRGYZSTAN Som (KGS)|
> |Madagascan Franc(MGF)|Malagasy Ariary(MGA)|
> |Mozambique Metical(MZM)|Mozambique Metical(MZN)|
> |Nicaragua (NIC)|Cordoba Oro (NIO)|
> |New Israeli Shekel(NIS)|New Israeli Sheqel (ILS)|
> |Poland(PLZ)|Zloty (PLN)|
> |Romanian Leu(ROL)|Romanian Leu(RON)|
> |Russian Rouble(RUR)|Russian Ruble(RUB)|
> |Sudanese Pound(SDP)|Sudanese Pound(SDG)|
> |Peru (SOL)|Sol (PEN)|
> |Surinam Guilder(SRG)|Surinam Dollar (SRD)|
> |Turkmenistani Manat(TMM)|Turkmenistan New Manat(TMT)|
> |Uganda Shilling(UGS)|Uganda Shilling(UGX)|
> |Uruguayan New Peso(UYP)|Uruguay Peso en Unidades Indexadas (URUIURUI)(UYI)|
> |Venezuelan Bolivar(VEB)|Bolívar(VEF)|
> |Zambian Kwacha(ZMK)|Zambian Kwacha(ZMW)|
> |Zimbabwean Dollar(ZWD)|Zimbabwe Dollar(ZWL)|
> |Georgian Kupon (GEK)|GEORGIA Lari (GEL)|
> Some currency codes moved to historic denominations, we can remove them from
> data.
> https://www.currency-iso.org/en/home/tables/table-a3.html
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (OFBIZ-9473) Status of communication event role is marked "Read" on View Communication Event page.
Pallavi Goyal created OFBIZ-9473: Summary: Status of communication event role is marked "Read" on View Communication Event page. Key: OFBIZ-9473 URL: https://issues.apache.org/jira/browse/OFBIZ-9473 Project: OFBiz Issue Type: Bug Components: party Affects Versions: Trunk Reporter: Pallavi Goyal Fix For: Upcoming Release *Steps to regenerate -* 1. Go to "Party" component. 2. Click on [ Communications ] menu tab. 3. Find communication events. 4. Open any communication event view page for "Addressee" role from Find Communication Event page. Actual - The role status of communication is marked "Read" on viewing communication. Expected - There is no change in the role status of the communication event. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-6774) ACCTG TRANS ENTRIES PDF link on invoiceOverview does not work
[
https://issues.apache.org/jira/browse/OFBIZ-6774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepak Dixit reassigned OFBIZ-6774:
---
Assignee: Deepak Dixit
> ACCTG TRANS ENTRIES PDF link on invoiceOverview does not work
> -
>
> Key: OFBIZ-6774
> URL: https://issues.apache.org/jira/browse/OFBIZ-6774
> Project: OFBiz
> Issue Type: Bug
> Components: birt, order
>Affects Versions: Release Branch 13.07
> Environment: Ubuntu linux 15.04, JVM 7u91-2.6.3-0ubuntu0.15.04.1
>Reporter: Morten Jensen
>Assignee: Deepak Dixit
>Priority: Minor
> Attachments: OFBIZ-6774_16.11.patch, OFBIZ-6774_trunk.patch
>
>
> Whenever I click on the ACCTG TRANS ENTRIES PDF link in the invoice overview
> screen I get the following error:
> org.ofbiz.webapp.control.RequestHandlerException: Unknown request
> [InvoiceAcctgTransEntriesPdf]; this request does not exist or cannot be
> called directly.
> A grep through the full ofbiz repo yields no results for an implementation or
> freemarker template - only the link itself in accounting menus xml:
> git checkout release13.07
> find . -type f -exec grep -i InvoiceAcctgTransEntriesPdf {} \; -ls
>
> 528005 72 -rw-rw-r-- 1 xxx xxx 70103 Dec 17 07:05
> ./applications/accounting/widget/AccountingMenus.xml
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OFBIZ-9328) Create New button is misplaced on Party Content Screen
[ https://issues.apache.org/jira/browse/OFBIZ-9328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Humera Khan updated OFBIZ-9328: --- Attachment: OFBIZ-9328.patch > Create New button is misplaced on Party Content Screen > -- > > Key: OFBIZ-9328 > URL: https://issues.apache.org/jira/browse/OFBIZ-9328 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: Trunk >Reporter: Devanshu Vyas >Assignee: Arun Patidar >Priority: Minor > Attachments: CreateNewButton.png, OFBIZ-9328.patch, OFBIZ-9328.patch > > > The Create New button is wrongly placed on the Party Content screen(navigated > from a Party Profile screen). The button should be placed outside of the > Content List section instead of inside. (CreateNewButton.png) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9472) Human Resource page throwing unwanted exceptions
[ https://issues.apache.org/jira/browse/OFBIZ-9472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Yadav updated OFBIZ-9472: Attachment: UnwantedExceptionsatHRpage.PNG > Human Resource page throwing unwanted exceptions > > > Key: OFBIZ-9472 > URL: https://issues.apache.org/jira/browse/OFBIZ-9472 > Project: OFBiz > Issue Type: Bug > Components: humanres >Reporter: Sanjay Yadav > Attachments: UnwantedExceptionsatHRpage.PNG > > > Go to: > Application Url -> HR > Actual - Human Resource page throwing unwanted exceptions. > Expected - Please fix unwanted exception bug. > Please refer attached screen shot for quick reference. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-9472) Human Resource page throwing unwanted exceptions
Sanjay Yadav created OFBIZ-9472: --- Summary: Human Resource page throwing unwanted exceptions Key: OFBIZ-9472 URL: https://issues.apache.org/jira/browse/OFBIZ-9472 Project: OFBiz Issue Type: Bug Components: humanres Reporter: Sanjay Yadav Go to: Application Url -> HR Actual - Human Resource page throwing unwanted exceptions. Expected - Please fix unwanted exception bug. Please refer attached screen shot for quick reference. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-7877) Set the default value for Html Menu Macro Library
[ https://issues.apache.org/jira/browse/OFBIZ-7877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079252#comment-16079252 ] Deepak Dixit commented on OFBIZ-7877: - Thanks Renuka this has been done at ofbiz framework trunk at r#1801306 > Set the default value for Html Menu Macro Library > - > > Key: OFBIZ-7877 > URL: https://issues.apache.org/jira/browse/OFBIZ-7877 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Affects Versions: Trunk >Reporter: Renuka Srishti >Assignee: Deepak Dixit > Fix For: Upcoming Release > > Attachments: OFBIZ-7877.patch > > > Need to set the default value for all the macros in html menu macro library > file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OFBIZ-7877) Set the default value for Html Menu Macro Library
[ https://issues.apache.org/jira/browse/OFBIZ-7877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Dixit closed OFBIZ-7877. --- Resolution: Done Fix Version/s: Upcoming Release > Set the default value for Html Menu Macro Library > - > > Key: OFBIZ-7877 > URL: https://issues.apache.org/jira/browse/OFBIZ-7877 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Affects Versions: Trunk >Reporter: Renuka Srishti >Assignee: Deepak Dixit > Fix For: Upcoming Release > > Attachments: OFBIZ-7877.patch > > > Need to set the default value for all the macros in html menu macro library > file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-9471) Set autocomplete to off for all the password fields.
Ritesh Kumar created OFBIZ-9471: --- Summary: Set autocomplete to off for all the password fields. Key: OFBIZ-9471 URL: https://issues.apache.org/jira/browse/OFBIZ-9471 Project: OFBiz Issue Type: Bug Components: framework Reporter: Ritesh Kumar Priority: Minor The login and Forget password screens have password inputs. It is a best practice to disable autocomplete on the password field. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-6949) Week and day overview of calendar doesn't show entries
[ https://issues.apache.org/jira/browse/OFBIZ-6949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079240#comment-16079240 ] Renuka Srishti commented on OFBIZ-6949: --- Hii Pierre, I have done following steps: 1. I have created one party of type person and added ASSETMAINTTECH and VIEWADMIN security groups from its profile. 2. Go to ASSET MAINT component then click on Fixed Assets label which will show the list of Fixed Assets. 3. Clik on any one fixed asset Id, there you can see calendar label. 4. Click on calendar label where you can see week view, day view, and month view also. 5. Try to switch them all, its working fine. Please check once, if you get any issue, we can discuss further. > Week and day overview of calendar doesn't show entries > --- > > Key: OFBIZ-6949 > URL: https://issues.apache.org/jira/browse/OFBIZ-6949 > Project: OFBiz > Issue Type: Bug > Components: workeffort >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Renuka Srishti > Labels: calendar, entry > Attachments: Screen Shot 2016-03-21 at 20.00.17.png, Screen Shot > 2016-03-21 at 20.00.40.png, Screen Shot 2016-03-21 at 20.00.59.png > > > In WorkEffort, the calendar overview the month overview shows all entries. > This not only applies to users with the WORKEFFORTMGR_ADMIN permission, but > also to users with the WORKEFFORTMGR_VIEW permission. > However, when switching to the week view or or day view, the user with > permission WORKEFFORTMGR_VIEW permission doesn't see the entries for that > week or day view. While the user with permission WORKEFFORTMGR_ADMIN does. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9461) Alignment issue at Catalog Manager page
[ https://issues.apache.org/jira/browse/OFBIZ-9461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Humera Khan updated OFBIZ-9461: --- Attachment: OFBIZ-9461.patch AlignmentAfterAddingConditionAndAction.png AlignmentWithRemoveButton.png Done following:- 1. Improved text size value of 'Name' and 'Description' field under 'Edit Price Rule' section. 2. If the 'Condition' or 'Action' is not added to price rule then [ Remove ] button is also shown in 'Edit Price Rule' section, hence also check the alignment in that case. > Alignment issue at Catalog Manager page > > > Key: OFBIZ-9461 > URL: https://issues.apache.org/jira/browse/OFBIZ-9461 > Project: OFBiz > Issue Type: Bug >Reporter: Sanjay Yadav >Priority: Minor > Labels: catalog > Attachments: AlignmentAfterAddingConditionAndAction.png, > AlignmentBugAtCatalogPriceRuleSection.png, AlignmentWithRemoveButton.png, > OFBIZ-9461.patch > > > Go to: > Application -> Catalog Manager -> Price Rule > Actual - From Date, Through Date and Update section is not properly aligned. > Also due this horizontal scroll appearing at page. > Expected - Fix this alignment issue and Horizontal scroll should not be > appear. > Please refer attached screen shot. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-7877) Set the default value for Html Menu Macro Library
[ https://issues.apache.org/jira/browse/OFBIZ-7877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Dixit reassigned OFBIZ-7877: --- Assignee: Deepak Dixit (was: Renuka Srishti) > Set the default value for Html Menu Macro Library > - > > Key: OFBIZ-7877 > URL: https://issues.apache.org/jira/browse/OFBIZ-7877 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Affects Versions: Trunk >Reporter: Renuka Srishti >Assignee: Deepak Dixit > Attachments: OFBIZ-7877.patch > > > Need to set the default value for all the macros in html menu macro library > file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-6949) Week and day overview of calendar doesn't show entries
[ https://issues.apache.org/jira/browse/OFBIZ-6949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Renuka Srishti reassigned OFBIZ-6949: - Assignee: Renuka Srishti (was: Gopal Yadav) > Week and day overview of calendar doesn't show entries > --- > > Key: OFBIZ-6949 > URL: https://issues.apache.org/jira/browse/OFBIZ-6949 > Project: OFBiz > Issue Type: Bug > Components: workeffort >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Renuka Srishti > Labels: calendar, entry > Attachments: Screen Shot 2016-03-21 at 20.00.17.png, Screen Shot > 2016-03-21 at 20.00.40.png, Screen Shot 2016-03-21 at 20.00.59.png > > > In WorkEffort, the calendar overview the month overview shows all entries. > This not only applies to users with the WORKEFFORTMGR_ADMIN permission, but > also to users with the WORKEFFORTMGR_VIEW permission. > However, when switching to the week view or or day view, the user with > permission WORKEFFORTMGR_VIEW permission doesn't see the entries for that > week or day view. While the user with permission WORKEFFORTMGR_ADMIN does. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9464) Accounting quantity transfer should not be zero while transferring inventory from one facility to another
[ https://issues.apache.org/jira/browse/OFBIZ-9464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079236#comment-16079236 ] Deepak Dixit commented on OFBIZ-9464: - Backported to release 16.11 at r#1801304 > Accounting quantity transfer should not be zero while transferring inventory > from one facility to another > - > > Key: OFBIZ-9464 > URL: https://issues.apache.org/jira/browse/OFBIZ-9464 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Vaibhav Jain >Assignee: Divesh Dutta > Fix For: 16.11.04 > > Attachments: OFBIZ_9464.patch > > > when we transfer inventory, the accountingQuantityTotal field of > _InventoryItem_ entity is always ZERO. There is no reflection of ATP/QOH in > accountingQuantityTotal. > This will create following issues in the system. > # Accounting quantity total will mismatch with the original quantity in the > facility which shows the wrong result when we calculate facility specific > inventory valuation. > # Inventory reservation also throws an error in some specific case like when > AQT of respective product is zero in the specific facility from when > reservation happens. > As we manage 5 different statuses of inventory transfer in OFBiz and > according to my current understanding these processes are associated with the > respective statuses, which are as show below > Requested: As inventory transfer is requested for another facility. > a)ATP, QOH and AQT should decrease from the inventory item of From Facility > and QOH of To Facility should increase. > b)ATP and AQT should be Zero in To Facility as inventory is not transferred > yet. But QOH should increase at To Facility because QOH shows the > xferquantity later. At the time of the completion of the transfer > ATP = ATP + (QOH - ATP) (Adjustment in case of backorder) > AQT = QOH > b)AQT should not decrease because AQT is used for accounting purpose and as > of now quantity is still in From Facility as the transfer is not done yet. > which shows the xferQuantity later > Scheduled: As inventory transfer is Scheduled for another facility. ATP, QOH > and AQT should not affect in both From Facility and To Facility. > En-route: As inventory is routed to reach at To Facility. Even in this case > ATP, QOH and AQT should not affect in both From Facility and To Facility. > Complete: As inventory transfer is completed > a)ATP, QOH and AQT should not affect at From Facility. > b)QOH will be same but ATP and AQT should affect respectively > ATP = ATP + (QOH - ATP) > AQT = QOH > Cancelled: As inventory transfer is cancelled and inventory item record is > already created so > a) ATP, QOH and AQT should decrease from old inventory item and ATP, QOH and > AQT should increase in the newly created inventory item. > Key points: > If the whole ATP and QOH is moved then new inventory item will not create. > Only Facility and location are changed for existing inventory item. > Before Changes:- > As I know there are following processes are associated with respective > statuses > **Note: ATP-> Available to promiseQOH-> Quantity on handAQT-> > Accounting quantity total > 1. Requested:- > ATP =0QOH=Transferred quantity >AQT=0 > 2. Scheduled:- > ATP =0QOH=Transferred quantity >AQT=0 > 3.En-Route:- > ATP =0QOH=Transferred quantity >AQT=0 > 4.Complete:- > If the partial quantity of any inventory item is transferred. > ATP =Transferred quantity QOH=Transferred quantity AQT=0 > If the whole quantity is transferred then only facility id and location > will change no new inventory item record will create. > 5.Cancelled:- > No new inventory item record will create. An inventory transfer record is > created with whole ATP/QOH in cancelled status. > After Changes:- > As shown above, accounting quantity transfer will not affect in transfer > inventory. After the following changes, records will be updated a shown below. > 1. Requested:- > ATP =0QOH=Transferred quantity >AQT=0 > 2. Scheduled:- > ATP =0QOH=Transferred quantity >AQT=0 > 3.En-Route:- > ATP =0QOH=Transferred quantity >AQT=0 > 4.Complete:- > If the partial quantity of any inventory item is transferred. > ATP =Transferred quantity QOH=Transferred quantity > AQT=Transferred quantity > If the whole quantity is transferred then only facility id and location > will change no new inventory item record
[jira] [Closed] (OFBIZ-9464) Accounting quantity transfer should not be zero while transferring inventory from one facility to another
[ https://issues.apache.org/jira/browse/OFBIZ-9464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Dixit closed OFBIZ-9464. --- > Accounting quantity transfer should not be zero while transferring inventory > from one facility to another > - > > Key: OFBIZ-9464 > URL: https://issues.apache.org/jira/browse/OFBIZ-9464 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Vaibhav Jain >Assignee: Divesh Dutta > Fix For: 16.11.04 > > Attachments: OFBIZ_9464.patch > > > when we transfer inventory, the accountingQuantityTotal field of > _InventoryItem_ entity is always ZERO. There is no reflection of ATP/QOH in > accountingQuantityTotal. > This will create following issues in the system. > # Accounting quantity total will mismatch with the original quantity in the > facility which shows the wrong result when we calculate facility specific > inventory valuation. > # Inventory reservation also throws an error in some specific case like when > AQT of respective product is zero in the specific facility from when > reservation happens. > As we manage 5 different statuses of inventory transfer in OFBiz and > according to my current understanding these processes are associated with the > respective statuses, which are as show below > Requested: As inventory transfer is requested for another facility. > a)ATP, QOH and AQT should decrease from the inventory item of From Facility > and QOH of To Facility should increase. > b)ATP and AQT should be Zero in To Facility as inventory is not transferred > yet. But QOH should increase at To Facility because QOH shows the > xferquantity later. At the time of the completion of the transfer > ATP = ATP + (QOH - ATP) (Adjustment in case of backorder) > AQT = QOH > b)AQT should not decrease because AQT is used for accounting purpose and as > of now quantity is still in From Facility as the transfer is not done yet. > which shows the xferQuantity later > Scheduled: As inventory transfer is Scheduled for another facility. ATP, QOH > and AQT should not affect in both From Facility and To Facility. > En-route: As inventory is routed to reach at To Facility. Even in this case > ATP, QOH and AQT should not affect in both From Facility and To Facility. > Complete: As inventory transfer is completed > a)ATP, QOH and AQT should not affect at From Facility. > b)QOH will be same but ATP and AQT should affect respectively > ATP = ATP + (QOH - ATP) > AQT = QOH > Cancelled: As inventory transfer is cancelled and inventory item record is > already created so > a) ATP, QOH and AQT should decrease from old inventory item and ATP, QOH and > AQT should increase in the newly created inventory item. > Key points: > If the whole ATP and QOH is moved then new inventory item will not create. > Only Facility and location are changed for existing inventory item. > Before Changes:- > As I know there are following processes are associated with respective > statuses > **Note: ATP-> Available to promiseQOH-> Quantity on handAQT-> > Accounting quantity total > 1. Requested:- > ATP =0QOH=Transferred quantity >AQT=0 > 2. Scheduled:- > ATP =0QOH=Transferred quantity >AQT=0 > 3.En-Route:- > ATP =0QOH=Transferred quantity >AQT=0 > 4.Complete:- > If the partial quantity of any inventory item is transferred. > ATP =Transferred quantity QOH=Transferred quantity AQT=0 > If the whole quantity is transferred then only facility id and location > will change no new inventory item record will create. > 5.Cancelled:- > No new inventory item record will create. An inventory transfer record is > created with whole ATP/QOH in cancelled status. > After Changes:- > As shown above, accounting quantity transfer will not affect in transfer > inventory. After the following changes, records will be updated a shown below. > 1. Requested:- > ATP =0QOH=Transferred quantity >AQT=0 > 2. Scheduled:- > ATP =0QOH=Transferred quantity >AQT=0 > 3.En-Route:- > ATP =0QOH=Transferred quantity >AQT=0 > 4.Complete:- > If the partial quantity of any inventory item is transferred. > ATP =Transferred quantity QOH=Transferred quantity > AQT=Transferred quantity > If the whole quantity is transferred then only facility id and location > will change no new inventory item record will create. > 5.Cancelled:- > No new inventory item record will create. An inventory transfer r
[jira] [Updated] (OFBIZ-9464) Accounting quantity transfer should not be zero while transferring inventory from one facility to another
[ https://issues.apache.org/jira/browse/OFBIZ-9464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Dixit updated OFBIZ-9464: Fix Version/s: (was: Upcoming Release) 16.11.04 > Accounting quantity transfer should not be zero while transferring inventory > from one facility to another > - > > Key: OFBIZ-9464 > URL: https://issues.apache.org/jira/browse/OFBIZ-9464 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Vaibhav Jain >Assignee: Divesh Dutta > Fix For: 16.11.04 > > Attachments: OFBIZ_9464.patch > > > when we transfer inventory, the accountingQuantityTotal field of > _InventoryItem_ entity is always ZERO. There is no reflection of ATP/QOH in > accountingQuantityTotal. > This will create following issues in the system. > # Accounting quantity total will mismatch with the original quantity in the > facility which shows the wrong result when we calculate facility specific > inventory valuation. > # Inventory reservation also throws an error in some specific case like when > AQT of respective product is zero in the specific facility from when > reservation happens. > As we manage 5 different statuses of inventory transfer in OFBiz and > according to my current understanding these processes are associated with the > respective statuses, which are as show below > Requested: As inventory transfer is requested for another facility. > a)ATP, QOH and AQT should decrease from the inventory item of From Facility > and QOH of To Facility should increase. > b)ATP and AQT should be Zero in To Facility as inventory is not transferred > yet. But QOH should increase at To Facility because QOH shows the > xferquantity later. At the time of the completion of the transfer > ATP = ATP + (QOH - ATP) (Adjustment in case of backorder) > AQT = QOH > b)AQT should not decrease because AQT is used for accounting purpose and as > of now quantity is still in From Facility as the transfer is not done yet. > which shows the xferQuantity later > Scheduled: As inventory transfer is Scheduled for another facility. ATP, QOH > and AQT should not affect in both From Facility and To Facility. > En-route: As inventory is routed to reach at To Facility. Even in this case > ATP, QOH and AQT should not affect in both From Facility and To Facility. > Complete: As inventory transfer is completed > a)ATP, QOH and AQT should not affect at From Facility. > b)QOH will be same but ATP and AQT should affect respectively > ATP = ATP + (QOH - ATP) > AQT = QOH > Cancelled: As inventory transfer is cancelled and inventory item record is > already created so > a) ATP, QOH and AQT should decrease from old inventory item and ATP, QOH and > AQT should increase in the newly created inventory item. > Key points: > If the whole ATP and QOH is moved then new inventory item will not create. > Only Facility and location are changed for existing inventory item. > Before Changes:- > As I know there are following processes are associated with respective > statuses > **Note: ATP-> Available to promiseQOH-> Quantity on handAQT-> > Accounting quantity total > 1. Requested:- > ATP =0QOH=Transferred quantity >AQT=0 > 2. Scheduled:- > ATP =0QOH=Transferred quantity >AQT=0 > 3.En-Route:- > ATP =0QOH=Transferred quantity >AQT=0 > 4.Complete:- > If the partial quantity of any inventory item is transferred. > ATP =Transferred quantity QOH=Transferred quantity AQT=0 > If the whole quantity is transferred then only facility id and location > will change no new inventory item record will create. > 5.Cancelled:- > No new inventory item record will create. An inventory transfer record is > created with whole ATP/QOH in cancelled status. > After Changes:- > As shown above, accounting quantity transfer will not affect in transfer > inventory. After the following changes, records will be updated a shown below. > 1. Requested:- > ATP =0QOH=Transferred quantity >AQT=0 > 2. Scheduled:- > ATP =0QOH=Transferred quantity >AQT=0 > 3.En-Route:- > ATP =0QOH=Transferred quantity >AQT=0 > 4.Complete:- > If the partial quantity of any inventory item is transferred. > ATP =Transferred quantity QOH=Transferred quantity > AQT=Transferred quantity > If the whole quantity is transferred then only facility id and location > will change no new inventory item record will create. > 5.Cancel
[jira] [Assigned] (OFBIZ-9328) Create New button is misplaced on Party Content Screen
[ https://issues.apache.org/jira/browse/OFBIZ-9328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Patidar reassigned OFBIZ-9328: --- Assignee: Arun Patidar > Create New button is misplaced on Party Content Screen > -- > > Key: OFBIZ-9328 > URL: https://issues.apache.org/jira/browse/OFBIZ-9328 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: Trunk >Reporter: Devanshu Vyas >Assignee: Arun Patidar >Priority: Minor > Attachments: CreateNewButton.png, OFBIZ-9328.patch > > > The Create New button is wrongly placed on the Party Content screen(navigated > from a Party Profile screen). The button should be placed outside of the > Content List section instead of inside. (CreateNewButton.png) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OFBIZ-9344) Incorrect MimeTypeId value shown if the form is submitted
[ https://issues.apache.org/jira/browse/OFBIZ-9344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Patidar closed OFBIZ-9344. --- Resolution: Fixed Fix Version/s: Upcoming Release Committed in Ofbiz framework trunk at revision 1801303 Thanks Devanshu for your contribution. > Incorrect MimeTypeId value shown if the form is submitted > -- > > Key: OFBIZ-9344 > URL: https://issues.apache.org/jira/browse/OFBIZ-9344 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: Trunk >Reporter: Devanshu Vyas >Assignee: Arun Patidar >Priority: Minor > Fix For: Upcoming Release > > Attachments: IncorrectMimeTypeId.png, OFBIZ-9344.patch > > > The 'Add Party Content' form shows incorrect Mime Type Id value if Submit > button is clicked without uploading any content. (IncorrectMimeTypeId.png) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (OFBIZ-9464) Accounting quantity transfer should not be zero while transferring inventory from one facility to another
[ https://issues.apache.org/jira/browse/OFBIZ-9464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079199#comment-16079199 ] Divesh Dutta edited comment on OFBIZ-9464 at 7/8/17 5:07 PM: - Fixed this issue in revision number 1801300 in ofbiz-framework/trunk. Thanks [~vaibhav.jain] for providing the fix was (Author: diveshdut): Fixed this issue in revision number 1801300. Thanks [~vaibhav.jain] for providing the fix > Accounting quantity transfer should not be zero while transferring inventory > from one facility to another > - > > Key: OFBIZ-9464 > URL: https://issues.apache.org/jira/browse/OFBIZ-9464 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Vaibhav Jain >Assignee: Divesh Dutta > Fix For: Upcoming Release > > Attachments: OFBIZ_9464.patch > > > when we transfer inventory, the accountingQuantityTotal field of > _InventoryItem_ entity is always ZERO. There is no reflection of ATP/QOH in > accountingQuantityTotal. > This will create following issues in the system. > # Accounting quantity total will mismatch with the original quantity in the > facility which shows the wrong result when we calculate facility specific > inventory valuation. > # Inventory reservation also throws an error in some specific case like when > AQT of respective product is zero in the specific facility from when > reservation happens. > As we manage 5 different statuses of inventory transfer in OFBiz and > according to my current understanding these processes are associated with the > respective statuses, which are as show below > Requested: As inventory transfer is requested for another facility. > a)ATP, QOH and AQT should decrease from the inventory item of From Facility > and QOH of To Facility should increase. > b)ATP and AQT should be Zero in To Facility as inventory is not transferred > yet. But QOH should increase at To Facility because QOH shows the > xferquantity later. At the time of the completion of the transfer > ATP = ATP + (QOH - ATP) (Adjustment in case of backorder) > AQT = QOH > b)AQT should not decrease because AQT is used for accounting purpose and as > of now quantity is still in From Facility as the transfer is not done yet. > which shows the xferQuantity later > Scheduled: As inventory transfer is Scheduled for another facility. ATP, QOH > and AQT should not affect in both From Facility and To Facility. > En-route: As inventory is routed to reach at To Facility. Even in this case > ATP, QOH and AQT should not affect in both From Facility and To Facility. > Complete: As inventory transfer is completed > a)ATP, QOH and AQT should not affect at From Facility. > b)QOH will be same but ATP and AQT should affect respectively > ATP = ATP + (QOH - ATP) > AQT = QOH > Cancelled: As inventory transfer is cancelled and inventory item record is > already created so > a) ATP, QOH and AQT should decrease from old inventory item and ATP, QOH and > AQT should increase in the newly created inventory item. > Key points: > If the whole ATP and QOH is moved then new inventory item will not create. > Only Facility and location are changed for existing inventory item. > Before Changes:- > As I know there are following processes are associated with respective > statuses > **Note: ATP-> Available to promiseQOH-> Quantity on handAQT-> > Accounting quantity total > 1. Requested:- > ATP =0QOH=Transferred quantity >AQT=0 > 2. Scheduled:- > ATP =0QOH=Transferred quantity >AQT=0 > 3.En-Route:- > ATP =0QOH=Transferred quantity >AQT=0 > 4.Complete:- > If the partial quantity of any inventory item is transferred. > ATP =Transferred quantity QOH=Transferred quantity AQT=0 > If the whole quantity is transferred then only facility id and location > will change no new inventory item record will create. > 5.Cancelled:- > No new inventory item record will create. An inventory transfer record is > created with whole ATP/QOH in cancelled status. > After Changes:- > As shown above, accounting quantity transfer will not affect in transfer > inventory. After the following changes, records will be updated a shown below. > 1. Requested:- > ATP =0QOH=Transferred quantity >AQT=0 > 2. Scheduled:- > ATP =0QOH=Transferred quantity >AQT=0 > 3.En-Route:- > ATP =0QOH=Transferred quantity >AQT=0 > 4.Complete:- > If the partial quantity of any in
[jira] [Commented] (OFBIZ-6510) Replace webtools/control/view/ModelInduceFromDb with widgets
[ https://issues.apache.org/jira/browse/OFBIZ-6510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079218#comment-16079218 ] Jacques Le Roux commented on OFBIZ-6510: I hoped Christian would, but it seems he is out or reach now. It's not a priority for me, but yes maybe I'll in the future... > Replace webtools/control/view/ModelInduceFromDb with widgets > > > Key: OFBIZ-6510 > URL: https://issues.apache.org/jira/browse/OFBIZ-6510 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Christian Carlow >Assignee: Michael Brohl > Attachments: OFBIZ-6510.patch, OFBIZ-6510.patch > > > The page is written in JSP probably from very long ago when FTL and widgets > didn't even exist yet. It should be implemented in widgets now that they are > available. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9464) Accounting quantity transfer should not be zero while transferring inventory from one facility to another
[ https://issues.apache.org/jira/browse/OFBIZ-9464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Divesh Dutta updated OFBIZ-9464: Fix Version/s: (was: Trunk) Upcoming Release > Accounting quantity transfer should not be zero while transferring inventory > from one facility to another > - > > Key: OFBIZ-9464 > URL: https://issues.apache.org/jira/browse/OFBIZ-9464 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Vaibhav Jain >Assignee: Divesh Dutta > Fix For: Upcoming Release > > Attachments: OFBIZ_9464.patch > > > when we transfer inventory, the accountingQuantityTotal field of > _InventoryItem_ entity is always ZERO. There is no reflection of ATP/QOH in > accountingQuantityTotal. > This will create following issues in the system. > # Accounting quantity total will mismatch with the original quantity in the > facility which shows the wrong result when we calculate facility specific > inventory valuation. > # Inventory reservation also throws an error in some specific case like when > AQT of respective product is zero in the specific facility from when > reservation happens. > As we manage 5 different statuses of inventory transfer in OFBiz and > according to my current understanding these processes are associated with the > respective statuses, which are as show below > Requested: As inventory transfer is requested for another facility. > a)ATP, QOH and AQT should decrease from the inventory item of From Facility > and QOH of To Facility should increase. > b)ATP and AQT should be Zero in To Facility as inventory is not transferred > yet. But QOH should increase at To Facility because QOH shows the > xferquantity later. At the time of the completion of the transfer > ATP = ATP + (QOH - ATP) (Adjustment in case of backorder) > AQT = QOH > b)AQT should not decrease because AQT is used for accounting purpose and as > of now quantity is still in From Facility as the transfer is not done yet. > which shows the xferQuantity later > Scheduled: As inventory transfer is Scheduled for another facility. ATP, QOH > and AQT should not affect in both From Facility and To Facility. > En-route: As inventory is routed to reach at To Facility. Even in this case > ATP, QOH and AQT should not affect in both From Facility and To Facility. > Complete: As inventory transfer is completed > a)ATP, QOH and AQT should not affect at From Facility. > b)QOH will be same but ATP and AQT should affect respectively > ATP = ATP + (QOH - ATP) > AQT = QOH > Cancelled: As inventory transfer is cancelled and inventory item record is > already created so > a) ATP, QOH and AQT should decrease from old inventory item and ATP, QOH and > AQT should increase in the newly created inventory item. > Key points: > If the whole ATP and QOH is moved then new inventory item will not create. > Only Facility and location are changed for existing inventory item. > Before Changes:- > As I know there are following processes are associated with respective > statuses > **Note: ATP-> Available to promiseQOH-> Quantity on handAQT-> > Accounting quantity total > 1. Requested:- > ATP =0QOH=Transferred quantity >AQT=0 > 2. Scheduled:- > ATP =0QOH=Transferred quantity >AQT=0 > 3.En-Route:- > ATP =0QOH=Transferred quantity >AQT=0 > 4.Complete:- > If the partial quantity of any inventory item is transferred. > ATP =Transferred quantity QOH=Transferred quantity AQT=0 > If the whole quantity is transferred then only facility id and location > will change no new inventory item record will create. > 5.Cancelled:- > No new inventory item record will create. An inventory transfer record is > created with whole ATP/QOH in cancelled status. > After Changes:- > As shown above, accounting quantity transfer will not affect in transfer > inventory. After the following changes, records will be updated a shown below. > 1. Requested:- > ATP =0QOH=Transferred quantity >AQT=0 > 2. Scheduled:- > ATP =0QOH=Transferred quantity >AQT=0 > 3.En-Route:- > ATP =0QOH=Transferred quantity >AQT=0 > 4.Complete:- > If the partial quantity of any inventory item is transferred. > ATP =Transferred quantity QOH=Transferred quantity > AQT=Transferred quantity > If the whole quantity is transferred then only facility id and location > will change no new inventory item record will create. > 5.C
[jira] [Resolved] (OFBIZ-9464) Accounting quantity transfer should not be zero while transferring inventory from one facility to another
[ https://issues.apache.org/jira/browse/OFBIZ-9464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Divesh Dutta resolved OFBIZ-9464. - Resolution: Fixed Fixed this issue in revision number 1801300. Thanks [~vaibhav.jain] for providing the fix > Accounting quantity transfer should not be zero while transferring inventory > from one facility to another > - > > Key: OFBIZ-9464 > URL: https://issues.apache.org/jira/browse/OFBIZ-9464 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Vaibhav Jain >Assignee: Divesh Dutta > Fix For: Trunk > > Attachments: OFBIZ_9464.patch > > > when we transfer inventory, the accountingQuantityTotal field of > _InventoryItem_ entity is always ZERO. There is no reflection of ATP/QOH in > accountingQuantityTotal. > This will create following issues in the system. > # Accounting quantity total will mismatch with the original quantity in the > facility which shows the wrong result when we calculate facility specific > inventory valuation. > # Inventory reservation also throws an error in some specific case like when > AQT of respective product is zero in the specific facility from when > reservation happens. > As we manage 5 different statuses of inventory transfer in OFBiz and > according to my current understanding these processes are associated with the > respective statuses, which are as show below > Requested: As inventory transfer is requested for another facility. > a)ATP, QOH and AQT should decrease from the inventory item of From Facility > and QOH of To Facility should increase. > b)ATP and AQT should be Zero in To Facility as inventory is not transferred > yet. But QOH should increase at To Facility because QOH shows the > xferquantity later. At the time of the completion of the transfer > ATP = ATP + (QOH - ATP) (Adjustment in case of backorder) > AQT = QOH > b)AQT should not decrease because AQT is used for accounting purpose and as > of now quantity is still in From Facility as the transfer is not done yet. > which shows the xferQuantity later > Scheduled: As inventory transfer is Scheduled for another facility. ATP, QOH > and AQT should not affect in both From Facility and To Facility. > En-route: As inventory is routed to reach at To Facility. Even in this case > ATP, QOH and AQT should not affect in both From Facility and To Facility. > Complete: As inventory transfer is completed > a)ATP, QOH and AQT should not affect at From Facility. > b)QOH will be same but ATP and AQT should affect respectively > ATP = ATP + (QOH - ATP) > AQT = QOH > Cancelled: As inventory transfer is cancelled and inventory item record is > already created so > a) ATP, QOH and AQT should decrease from old inventory item and ATP, QOH and > AQT should increase in the newly created inventory item. > Key points: > If the whole ATP and QOH is moved then new inventory item will not create. > Only Facility and location are changed for existing inventory item. > Before Changes:- > As I know there are following processes are associated with respective > statuses > **Note: ATP-> Available to promiseQOH-> Quantity on handAQT-> > Accounting quantity total > 1. Requested:- > ATP =0QOH=Transferred quantity >AQT=0 > 2. Scheduled:- > ATP =0QOH=Transferred quantity >AQT=0 > 3.En-Route:- > ATP =0QOH=Transferred quantity >AQT=0 > 4.Complete:- > If the partial quantity of any inventory item is transferred. > ATP =Transferred quantity QOH=Transferred quantity AQT=0 > If the whole quantity is transferred then only facility id and location > will change no new inventory item record will create. > 5.Cancelled:- > No new inventory item record will create. An inventory transfer record is > created with whole ATP/QOH in cancelled status. > After Changes:- > As shown above, accounting quantity transfer will not affect in transfer > inventory. After the following changes, records will be updated a shown below. > 1. Requested:- > ATP =0QOH=Transferred quantity >AQT=0 > 2. Scheduled:- > ATP =0QOH=Transferred quantity >AQT=0 > 3.En-Route:- > ATP =0QOH=Transferred quantity >AQT=0 > 4.Complete:- > If the partial quantity of any inventory item is transferred. > ATP =Transferred quantity QOH=Transferred quantity > AQT=Transferred quantity > If the whole quantity is transferred then only facility id and location > will change no new inventor
[jira] [Assigned] (OFBIZ-9464) Accounting quantity transfer should not be zero while transferring inventory from one facility to another
[ https://issues.apache.org/jira/browse/OFBIZ-9464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Divesh Dutta reassigned OFBIZ-9464: --- Assignee: Divesh Dutta (was: Vaibhav Jain) > Accounting quantity transfer should not be zero while transferring inventory > from one facility to another > - > > Key: OFBIZ-9464 > URL: https://issues.apache.org/jira/browse/OFBIZ-9464 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Vaibhav Jain >Assignee: Divesh Dutta > Fix For: Trunk > > Attachments: OFBIZ_9464.patch > > > when we transfer inventory, the accountingQuantityTotal field of > _InventoryItem_ entity is always ZERO. There is no reflection of ATP/QOH in > accountingQuantityTotal. > This will create following issues in the system. > # Accounting quantity total will mismatch with the original quantity in the > facility which shows the wrong result when we calculate facility specific > inventory valuation. > # Inventory reservation also throws an error in some specific case like when > AQT of respective product is zero in the specific facility from when > reservation happens. > As we manage 5 different statuses of inventory transfer in OFBiz and > according to my current understanding these processes are associated with the > respective statuses, which are as show below > Requested: As inventory transfer is requested for another facility. > a)ATP, QOH and AQT should decrease from the inventory item of From Facility > and QOH of To Facility should increase. > b)ATP and AQT should be Zero in To Facility as inventory is not transferred > yet. But QOH should increase at To Facility because QOH shows the > xferquantity later. At the time of the completion of the transfer > ATP = ATP + (QOH - ATP) (Adjustment in case of backorder) > AQT = QOH > b)AQT should not decrease because AQT is used for accounting purpose and as > of now quantity is still in From Facility as the transfer is not done yet. > which shows the xferQuantity later > Scheduled: As inventory transfer is Scheduled for another facility. ATP, QOH > and AQT should not affect in both From Facility and To Facility. > En-route: As inventory is routed to reach at To Facility. Even in this case > ATP, QOH and AQT should not affect in both From Facility and To Facility. > Complete: As inventory transfer is completed > a)ATP, QOH and AQT should not affect at From Facility. > b)QOH will be same but ATP and AQT should affect respectively > ATP = ATP + (QOH - ATP) > AQT = QOH > Cancelled: As inventory transfer is cancelled and inventory item record is > already created so > a) ATP, QOH and AQT should decrease from old inventory item and ATP, QOH and > AQT should increase in the newly created inventory item. > Key points: > If the whole ATP and QOH is moved then new inventory item will not create. > Only Facility and location are changed for existing inventory item. > Before Changes:- > As I know there are following processes are associated with respective > statuses > **Note: ATP-> Available to promiseQOH-> Quantity on handAQT-> > Accounting quantity total > 1. Requested:- > ATP =0QOH=Transferred quantity >AQT=0 > 2. Scheduled:- > ATP =0QOH=Transferred quantity >AQT=0 > 3.En-Route:- > ATP =0QOH=Transferred quantity >AQT=0 > 4.Complete:- > If the partial quantity of any inventory item is transferred. > ATP =Transferred quantity QOH=Transferred quantity AQT=0 > If the whole quantity is transferred then only facility id and location > will change no new inventory item record will create. > 5.Cancelled:- > No new inventory item record will create. An inventory transfer record is > created with whole ATP/QOH in cancelled status. > After Changes:- > As shown above, accounting quantity transfer will not affect in transfer > inventory. After the following changes, records will be updated a shown below. > 1. Requested:- > ATP =0QOH=Transferred quantity >AQT=0 > 2. Scheduled:- > ATP =0QOH=Transferred quantity >AQT=0 > 3.En-Route:- > ATP =0QOH=Transferred quantity >AQT=0 > 4.Complete:- > If the partial quantity of any inventory item is transferred. > ATP =Transferred quantity QOH=Transferred quantity > AQT=Transferred quantity > If the whole quantity is transferred then only facility id and location > will change no new inventory item record will create. > 5.Cancelled:- > No new inve
[jira] [Assigned] (OFBIZ-9466) Use serviceUtil() in place of hard-coded error/success messages.
[ https://issues.apache.org/jira/browse/OFBIZ-9466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Patidar reassigned OFBIZ-9466: --- Assignee: Arun Patidar (was: Aditi Patidar) > Use serviceUtil() in place of hard-coded error/success messages. > > > Key: OFBIZ-9466 > URL: https://issues.apache.org/jira/browse/OFBIZ-9466 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Pawan Verma >Assignee: Arun Patidar >Priority: Minor > Attachments: OFBIZ-9466.patch > > > Use serviceUtil() in place of hard-coded error/success messages. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OFBIZ-9344) Incorrect MimeTypeId value shown if the form is submitted
[ https://issues.apache.org/jira/browse/OFBIZ-9344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Patidar reassigned OFBIZ-9344: --- Assignee: Arun Patidar > Incorrect MimeTypeId value shown if the form is submitted > -- > > Key: OFBIZ-9344 > URL: https://issues.apache.org/jira/browse/OFBIZ-9344 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: Trunk >Reporter: Devanshu Vyas >Assignee: Arun Patidar >Priority: Minor > Attachments: IncorrectMimeTypeId.png, OFBIZ-9344.patch > > > The 'Add Party Content' form shows incorrect Mime Type Id value if Submit > button is clicked without uploading any content. (IncorrectMimeTypeId.png) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-7356) OFBIZ-6964: Document finalized design to support replenishment planning through any inter-company facility
[
https://issues.apache.org/jira/browse/OFBIZ-7356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079175#comment-16079175
]
Divesh Dutta commented on OFBIZ-7356:
-
I liked the overall design. The only improvement I would suggest is to extend
Facility tables instead of ProductStoreFacility for recording RMEI
(requirementhMethodEnumId)
Also from data preparation point of view, it might be a tedious job to manage
data of ProductFacilityAssoc table for each product. For example, assume below
given situation:
1) requirementhMethodEnumId is set to XFERRQM_STOCK_ATP for Store
StoreWarehouse_01 in Facility table
2) MRP engine runs for StoreWarehouse_01
3) GZ-8544 is below safety stock in StoreWarehouse_01
4) ProductFacilityAssoc record for 8544 is not created
Then system should pick parentFacilityID from Facility table and propose
transfer request from parentFacilityID. This way if all the products of
facility are replenished from one warehouse, then user will not have to create
ProductFacilityAssoc records for each products.
> OFBIZ-6964: Document finalized design to support replenishment planning
> through any inter-company facility
> --
>
> Key: OFBIZ-7356
> URL: https://issues.apache.org/jira/browse/OFBIZ-7356
> Project: OFBiz
> Issue Type: Sub-task
> Components: manufacturing, order, product
>Reporter: Swapnil Shah
>Assignee: Swapnil Shah
>
> Here are high level design notes to based on the requirement specified under
> OFBIZ-7355 to support the product level replenishment from any inter-company
> facility before raising the ordering from an outside vendor.
> * We could extend the MRP logic (MrpEvent,Requirenent) to honor these new
> types and create corresponding event & requirement for Stock transfer between
> facilities.
> * Introduce two new entities ProductFacilityAssoc & FacilityAssocType and use
> them in conjunction with MrpEventType and corresponding RequirementType to
> serve the requirement for replenishing the store's via Inter-facility
> transfers mode. The data model & UI could be extended as follows:
> {code}
>
> title="Define associations between Product facilities">
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> rel-entity-name="Facility">
>
>
> rel-entity-name="Facility">
>
>
> rel-entity-name="FacilityAssocType">
>
>
>
>
> title="Define associations between facilities">
>
>
>
>
>
>
>
>
>
>
>
> description="Facility that serves another facility in terms of inventory"/>
>
> facilityIdTo="StoreWarehouse_01" facilityAssocTypeId="BACKUP_WAREHOUSE"
> sequenceNum="01" fromDate="2001-01-01 12:00:00"/>
> facilityIdTo="StoreWarehouse_01" facilityAssocTypeId="BACKUP_WAREHOUSE"
> sequenceNum="02" fromDate="2001-01-01 12:00:00"/>
> facilityIdTo="StoreWarehouse_01" facilityAssocTypeId="BACKUP_WAREHOUSE"
> sequenceNum="03" fromDate="2001-01-01 12:00:00"/>
> facilityIdTo="RegionalWarehouse_01" facilityAssocTypeId="BACKUP_WAREHOUSE"
> sequenceNum="01" fromDate="2001-01-01 12:00:00"/>
> facilityIdTo="RegionalWarehouse_02" facilityAssocTypeId="BACKUP_WAREHOUSE"
> sequenceNum="01" fromDate="2001-01-01 12:00:00"/>
>
>
>
>
> requirementTypeId="TRANSFER_REQUIREMENT"/>
>
> enumTypeId="PROD_REQ_METHOD"/>
>
> checkInventory="N" oneInventoryFacility="N" requireInventory="N"
> reserveInventory="Y" reserveOrderEnumId="INVRO_FIFO_REC" />
>
> requirementMethodEnumId="XFERRQM_STOCK_ATP" fromDate="2001-04-13 12:00:00"/>
>
> lastInventoryCount="20.00" minimumStock="100.00" productId="GZ-8544"/>
> lastInventoryCount="40.00" minimumStock="200.00" productId="GZ-8544"/>
> lastInventoryCount="60.00" minimumStock="200.00" productId="GZ-8544"/>
> lastInventoryCount="200.00" minimumStock="300.00"
> productId="GZ-8544"/>
> {code}
> MRP engine would start creating event beginning with store's primary facility
> based on set RMEI under ProductStoreFacility e.g, XFERRQM_STOCK_ATP for
> StoreWarehouse_01, In other words if MinStock < ATP , then MRP algorithm
> would:
> # Look up and consume the respective ATP from all the eligible "facilityIdTo"
> (based on ProductFacilityAssoc), from where given product is transferable.
> Based on their priorities start allocating ATP unless it meet the
> (MinStock-ATP) requirement for a given store e.g., 'StoreWarehouse_01' .
> # Create new MRP Event with Event type "PROP_ATP_STOCK_TRANSFER" with
> Proposed Quantity = MINIMUM STOCK - ATP from the facility (with highest
> priority i.e.,RegionalWarehouse_01) to the destination facility.
> ## If demand for (MinStock-ATP) is still not fully met by any facility with
> higher priority then repeat step#1 for all the associated facilities in
> descending order
[jira] [Updated] (OFBIZ-9470) Missing productId in input field after Atp/Qoh button is clicked on create PO screen
[ https://issues.apache.org/jira/browse/OFBIZ-9470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Goyal updated OFBIZ-9470: - Attachment: OFBIZ-9470.patch *Steps to regenerate -* 1. Follow the steps in description. 2. Click the button [ Atp/Qoh ], the table is generated and the "Product Id" input field will have productId of selected product. > Missing productId in input field after Atp/Qoh button is clicked on create PO > screen > > > Key: OFBIZ-9470 > URL: https://issues.apache.org/jira/browse/OFBIZ-9470 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk >Reporter: Pallavi Goyal >Priority: Minor > Fix For: Upcoming Release > > Attachments: missing-productId.png, OFBIZ-9470.patch > > > *Steps to regenerate -* > 1. Go to "Order" component. > 2. Click on [ Order Entry ] menu button. > 3. Fill the details in "Purchase Order" section and click on continue. > 4. Fill the required order details and click on continue. > 5. Open the product lookup table and select a product. > 6. Click on [ Atp/Qoh ] button. > The issue generated is - > The productId vanishes from the input field. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9470) Missing productId in input field after Atp/Qoh button is clicked on create PO screen
[ https://issues.apache.org/jira/browse/OFBIZ-9470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallavi Goyal updated OFBIZ-9470: - Attachment: missing-productId.png Attaching screenshot for the issue. > Missing productId in input field after Atp/Qoh button is clicked on create PO > screen > > > Key: OFBIZ-9470 > URL: https://issues.apache.org/jira/browse/OFBIZ-9470 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk >Reporter: Pallavi Goyal >Priority: Minor > Fix For: Upcoming Release > > Attachments: missing-productId.png > > > *Steps to regenerate -* > 1. Go to "Order" component. > 2. Click on [ Order Entry ] menu button. > 3. Fill the details in "Purchase Order" section and click on continue. > 4. Fill the required order details and click on continue. > 5. Open the product lookup table and select a product. > 6. Click on [ Atp/Qoh ] button. > The issue generated is - > The productId vanishes from the input field. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
