[jira] [Closed] (OFBIZ-11209) Serbian CommonEntityLabels for geo entity
[ https://issues.apache.org/jira/browse/OFBIZ-11209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam closed OFBIZ-11209. Resolution: Fixed > Serbian CommonEntityLabels for geo entity > - > > Key: OFBIZ-11209 > URL: https://issues.apache.org/jira/browse/OFBIZ-11209 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Ulrich Heidfeld >Assignee: Deepak Nigam >Priority: Minor > Fix For: Trunk > > Attachments: > OFBIZ-11209_Serbian_CommonEntityLabels_for_geo_entity.patch > > > There is no entry 'Geo.geoName.SRB' in CommonEntityLabels.xml. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11209) Serbian CommonEntityLabels for geo entity
[ https://issues.apache.org/jira/browse/OFBIZ-11209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16939932#comment-16939932 ] Deepak Nigam commented on OFBIZ-11209: -- Fixed: Serbian CommonEntityLabels for geo entity. Added missing entity label for Serbia. Thanks, Ulrich Heidfeld for your contribution, your patch has been committed at -r1867663 in trunk. > Serbian CommonEntityLabels for geo entity > - > > Key: OFBIZ-11209 > URL: https://issues.apache.org/jira/browse/OFBIZ-11209 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Ulrich Heidfeld >Assignee: Deepak Nigam >Priority: Minor > Fix For: Trunk > > Attachments: > OFBIZ-11209_Serbian_CommonEntityLabels_for_geo_entity.patch > > > There is no entry 'Geo.geoName.SRB' in CommonEntityLabels.xml. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (OFBIZ-11209) Serbian CommonEntityLabels for geo entity
[ https://issues.apache.org/jira/browse/OFBIZ-11209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam reassigned OFBIZ-11209: Assignee: Deepak Nigam (was: Ulrich Heidfeld) > Serbian CommonEntityLabels for geo entity > - > > Key: OFBIZ-11209 > URL: https://issues.apache.org/jira/browse/OFBIZ-11209 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Ulrich Heidfeld >Assignee: Deepak Nigam >Priority: Minor > Fix For: Trunk > > Attachments: > OFBIZ-11209_Serbian_CommonEntityLabels_for_geo_entity.patch > > > There is no entry 'Geo.geoName.SRB' in CommonEntityLabels.xml. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (OFBIZ-7257) View Image button on order detail page is not working
[ https://issues.apache.org/jira/browse/OFBIZ-7257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam closed OFBIZ-7257. --- Thanks, Avnindra Sharma for reporting the original issue, Devanshu Vyas for providing the patch and Jacques for review and suggestions. > View Image button on order detail page is not working > - > > Key: OFBIZ-7257 > URL: https://issues.apache.org/jira/browse/OFBIZ-7257 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk >Reporter: Avnindra Sharma >Assignee: Deepak Nigam >Priority: Major > Fix For: Upcoming Branch > > Attachments: OFBIZ-7257.patch, OFBIZ-7257.patch, OFBIZ-7257.patch > > > Item image is not getting open on clicking ViewImage on order detail page. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OFBIZ-7257) View Image button on order detail page is not working
[ https://issues.apache.org/jira/browse/OFBIZ-7257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam resolved OFBIZ-7257. - Resolution: Implemented > View Image button on order detail page is not working > - > > Key: OFBIZ-7257 > URL: https://issues.apache.org/jira/browse/OFBIZ-7257 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk >Reporter: Avnindra Sharma >Assignee: Deepak Nigam >Priority: Major > Fix For: Upcoming Branch > > Attachments: OFBIZ-7257.patch, OFBIZ-7257.patch, OFBIZ-7257.patch > > > Item image is not getting open on clicking ViewImage on order detail page. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-7257) View Image button on order detail page is not working
[ https://issues.apache.org/jira/browse/OFBIZ-7257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-7257: Fix Version/s: Upcoming Branch > View Image button on order detail page is not working > - > > Key: OFBIZ-7257 > URL: https://issues.apache.org/jira/browse/OFBIZ-7257 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk >Reporter: Avnindra Sharma >Assignee: Deepak Nigam >Priority: Major > Fix For: Upcoming Branch > > Attachments: OFBIZ-7257.patch, OFBIZ-7257.patch, OFBIZ-7257.patch > > > Item image is not getting open on clicking ViewImage on order detail page. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-7257) View Image button on order detail page is not working
[ https://issues.apache.org/jira/browse/OFBIZ-7257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-7257: Affects Version/s: Trunk > View Image button on order detail page is not working > - > > Key: OFBIZ-7257 > URL: https://issues.apache.org/jira/browse/OFBIZ-7257 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk >Reporter: Avnindra Sharma >Assignee: Deepak Nigam >Priority: Major > Attachments: OFBIZ-7257.patch, OFBIZ-7257.patch, OFBIZ-7257.patch > > > Item image is not getting open on clicking ViewImage on order detail page. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-7257) View Image button on order detail page is not working
[ https://issues.apache.org/jira/browse/OFBIZ-7257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16870241#comment-16870241 ] Deepak Nigam commented on OFBIZ-7257: - Implemented: The feature where a user will be able to add different types of content(image, document, URL, etc.) to an order. Committed at -r1861853 in the trunk. > View Image button on order detail page is not working > - > > Key: OFBIZ-7257 > URL: https://issues.apache.org/jira/browse/OFBIZ-7257 > Project: OFBiz > Issue Type: Bug > Components: order >Reporter: Avnindra Sharma >Assignee: Deepak Nigam >Priority: Major > Attachments: OFBIZ-7257.patch, OFBIZ-7257.patch, OFBIZ-7257.patch > > > Item image is not getting open on clicking ViewImage on order detail page. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-7257) View Image button on order detail page is not working
[ https://issues.apache.org/jira/browse/OFBIZ-7257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam reassigned OFBIZ-7257: --- Assignee: Deepak Nigam (was: Avnindra Sharma) > View Image button on order detail page is not working > - > > Key: OFBIZ-7257 > URL: https://issues.apache.org/jira/browse/OFBIZ-7257 > Project: OFBiz > Issue Type: Bug > Components: order >Reporter: Avnindra Sharma >Assignee: Deepak Nigam >Priority: Major > Attachments: OFBIZ-7257.patch, OFBIZ-7257.patch, OFBIZ-7257.patch > > > Item image is not getting open on clicking ViewImage on order detail page. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-7257) View Image button on order detail page is not working
[ https://issues.apache.org/jira/browse/OFBIZ-7257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16870186#comment-16870186 ] Deepak Nigam commented on OFBIZ-7257: - [~devanshu.vyas], I tested your patch on my local machine and it is looking good to me. Just a small improvement, change the description to 'Document' in the OrderContentType you have added. > View Image button on order detail page is not working > - > > Key: OFBIZ-7257 > URL: https://issues.apache.org/jira/browse/OFBIZ-7257 > Project: OFBiz > Issue Type: Bug > Components: order >Reporter: Avnindra Sharma >Assignee: Avnindra Sharma >Priority: Major > Attachments: OFBIZ-7257.patch, OFBIZ-7257.patch > > > Item image is not getting open on clicking ViewImage on order detail page. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (OFBIZ-10639) Cookie Consent In E-Commerce
[ https://issues.apache.org/jira/browse/OFBIZ-10639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16870147#comment-16870147 ] Deepak Nigam edited comment on OFBIZ-10639 at 6/22/19 8:52 AM: --- Thank you, [~jacques.le.roux] and [~aditya.sharma]. [bsgdprcookies|https://github.com/Aleksander98/bsgdprcookies] plugin looks good to me also. [~aditya.sharma], you can assign this ticket to yourself and start work on [bsgdprcookies|https://github.com/Aleksander98/bsgdprcookies]. If you have some other engagements, let me know, I will pick this. [~jacques.le.roux], I will remove my old Jira account with the help for infra. Thanks for pointing this out. was (Author: deepak.nigam): Thank you, [~jacques.le.roux] and [~aditya.sharma]. [bsgdprcookies|https://github.com/Aleksander98/bsgdprcookies] plugin looks good to me also. [~aditya.sharma], you can assign this ticket to yourself and start work on [bsgdprcookies|https://github.com/Aleksander98/bsgdprcookies]. If have some other engagements, let me know, I will pick this. [~jacques.le.roux], I will remove my old Jira account with the help for infra. Thanks for pointing this out. > Cookie Consent In E-Commerce > > > Key: OFBIZ-10639 > URL: https://issues.apache.org/jira/browse/OFBIZ-10639 > Project: OFBiz > Issue Type: New Feature > Components: ecommerce >Affects Versions: Trunk >Reporter: Deepak Nigam >Priority: Minor > Attachments: OFBIZ-10639.patch, OFBIZ-10639.patch, > image-2019-06-18-16-55-24-395.png > > > As per discussion on Dev ML [https://markmail.org/message/rcatehtckz6vlvuv] > The Cookie Law is a piece of privacy legislation that requires websites to > get consent from visitors to store or retrieve any information on their > computer, smartphone or tablet. It was designed to protect online privacy, by > making consumers aware of how information about them is collected and used > online, and give them a choice to allow it or not. > > The EU Cookie Legislation began as a directive from the European Union. Some > variation on the policy has since been adopted by all countries within the EU. > > The EU Cookie Legislation requires 4 actions from website owners who use > cookies: > 1. When someone visits your website, you need to let them know that your > site uses cookies. > 2. You need to provide detailed information regarding how that cookie data > will be utilized. > 3. You need to provide visitors with some means of accepting or refusing the > use of cookies in your site. > 4. If they refuse, you need to ensure that cookies will not be placed on > their machine. > > For more information about EU cookie policy, please visit > [here|http://ec.europa.eu/ipg/basics/legal/cookies/index_en.htm]. > > As this crucial feature is missing in OFBiz E-Commerce application, we > should work towards its implementation. There are numerous open-source jQuery > plugins available which we can use. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10639) Cookie Consent In E-Commerce
[ https://issues.apache.org/jira/browse/OFBIZ-10639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16870147#comment-16870147 ] Deepak Nigam commented on OFBIZ-10639: -- Thank you, [~jacques.le.roux] and [~aditya.sharma]. [bsgdprcookies|https://github.com/Aleksander98/bsgdprcookies] plugin looks good to me also. [~aditya.sharma], you can assign this ticket to yourself and start work on [bsgdprcookies|https://github.com/Aleksander98/bsgdprcookies]. If have some other engagements, let me know, I will pick this. [~jacques.le.roux], I will remove my old Jira account with the help for infra. Thanks for pointing this out. > Cookie Consent In E-Commerce > > > Key: OFBIZ-10639 > URL: https://issues.apache.org/jira/browse/OFBIZ-10639 > Project: OFBiz > Issue Type: New Feature > Components: ecommerce >Affects Versions: Trunk >Reporter: Deepak Nigam >Priority: Minor > Attachments: OFBIZ-10639.patch, OFBIZ-10639.patch, > image-2019-06-18-16-55-24-395.png > > > As per discussion on Dev ML [https://markmail.org/message/rcatehtckz6vlvuv] > The Cookie Law is a piece of privacy legislation that requires websites to > get consent from visitors to store or retrieve any information on their > computer, smartphone or tablet. It was designed to protect online privacy, by > making consumers aware of how information about them is collected and used > online, and give them a choice to allow it or not. > > The EU Cookie Legislation began as a directive from the European Union. Some > variation on the policy has since been adopted by all countries within the EU. > > The EU Cookie Legislation requires 4 actions from website owners who use > cookies: > 1. When someone visits your website, you need to let them know that your > site uses cookies. > 2. You need to provide detailed information regarding how that cookie data > will be utilized. > 3. You need to provide visitors with some means of accepting or refusing the > use of cookies in your site. > 4. If they refuse, you need to ensure that cookies will not be placed on > their machine. > > For more information about EU cookie policy, please visit > [here|http://ec.europa.eu/ipg/basics/legal/cookies/index_en.htm]. > > As this crucial feature is missing in OFBiz E-Commerce application, we > should work towards its implementation. There are numerous open-source jQuery > plugins available which we can use. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10639) Cookie Consent In E-Commerce
[ https://issues.apache.org/jira/browse/OFBIZ-10639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16864175#comment-16864175 ] Deepak Nigam commented on OFBIZ-10639: -- [~jacques.le.roux], >From that plugin, I removed the feature of 'Customized Cookies' because it >seems unrequired to me in our case. The complete example of the plugin can be >seen here: [https://iamketan.com.au/|https://iamketan.com.au/]. > Cookie Consent In E-Commerce > > > Key: OFBIZ-10639 > URL: https://issues.apache.org/jira/browse/OFBIZ-10639 > Project: OFBiz > Issue Type: New Feature > Components: ecommerce >Affects Versions: Trunk >Reporter: Deepak Nigam >Assignee: Swapnil M Mane >Priority: Minor > Attachments: OFBIZ-10639.patch, OFBIZ-10639.patch > > > As per discussion on Dev ML [https://markmail.org/message/rcatehtckz6vlvuv] > The Cookie Law is a piece of privacy legislation that requires websites to > get consent from visitors to store or retrieve any information on their > computer, smartphone or tablet. It was designed to protect online privacy, by > making consumers aware of how information about them is collected and used > online, and give them a choice to allow it or not. > > The EU Cookie Legislation began as a directive from the European Union. Some > variation on the policy has since been adopted by all countries within the EU. > > The EU Cookie Legislation requires 4 actions from website owners who use > cookies: > 1. When someone visits your website, you need to let them know that your > site uses cookies. > 2. You need to provide detailed information regarding how that cookie data > will be utilized. > 3. You need to provide visitors with some means of accepting or refusing the > use of cookies in your site. > 4. If they refuse, you need to ensure that cookies will not be placed on > their machine. > > For more information about EU cookie policy, please visit > [here|http://ec.europa.eu/ipg/basics/legal/cookies/index_en.htm]. > > As this crucial feature is missing in OFBiz E-Commerce application, we > should work towards its implementation. There are numerous open-source jQuery > plugins available which we can use. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (OFBIZ-10639) Cookie Consent In E-Commerce
[ https://issues.apache.org/jira/browse/OFBIZ-10639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16862847#comment-16862847 ] Deepak Nigam edited comment on OFBIZ-10639 at 6/13/19 9:09 AM: --- Thanks [~aditya.sharma] and [~jacques.le.roux]. Please find responses to your queries and suggestions below: _"I think we should avoid renaming the external library and its variable names (ihavecookies). Apart from this we should not modify its headers. As per my understanding license headers are added for custom files specific to OFBiz and external files are kept as it is."_ By keeping in mind about MIT license, I changed the name of variables to make them more relevant to the functionality. However, we can keep the previous name also. I also removed some code from the plugin which is not required in our case. I am not sure if we can add OFBiz license header files for the customized files having MIT license. Please help me with this. _"Also we should provide not only the minified library but also its plain source code version"_ I will add the plain source code file also. _"are the changes in custom.css custom or copied from the ihavecookies project (example.css file)? "_ Changes in custom.css files are copied from Example.css but I made some customizations for a better look and feel. _"And last but not least we prefer to generate our patches from root, easier for reviewers to apply and test"_ This patch was created from the root of the e-commerce plugin. I am able to apply it from there. _"Could you explain why init.js would be better than eg InitCookieConsent.js for new custom code. It's not clear to me and I would prefer the later."_ By custom code in Init.js, I mean initialization blocks of other plugins and libraries. It will be a common file for all initialization blocks. However, InitCookieConsent.js is also fine we want to keep it specific to this cookie consent feature. was (Author: deepak.nigam): Thanks [~aditya.sharma] and [~jacques.le.roux]. Please find responses to your queries and suggestions below: _"I think we should avoid renaming the external library and its variable names (ihavecookies). Apart from this we should not modify its headers. As per my understanding license headers are added for custom files specific to OFBiz and external files are kept as it is."_ By keeping in mind about MIT license, I changed the name of variables to make them more relevant to the functionality. However, we can keep the previous name also. I also removed some code from the plugin which is not required in our case. I am not sure if we can add OFBiz license header files for the customized files having MIT license. Please help me with this. _"Also we should provide not only the minified library but also its plain source code version"_ I will add the plain source code file also. _"are the changes in custom.css custom or copied from the ihavecookies project (example.css file)? "_ Changes in custom.css files are copied from Example.css but I made some customizations for a better look and feel. _"And last but not least we prefer to generate our patches from root, easier for reviewers to apply and test"_ This patch was created from the root of the e-commerce component. I am able to apply it from there. _"Could you explain why init.js would be better than eg InitCookieConsent.js for new custom code. It's not clear to me and I would prefer the later."_ By custom code in Init.js, I mean initialization blocks of other plugins and libraries. It will be a common file for all initialization blocks. However, InitCookieConsent.js is also fine we want to keep it specific to this cookie consent feature. > Cookie Consent In E-Commerce > > > Key: OFBIZ-10639 > URL: https://issues.apache.org/jira/browse/OFBIZ-10639 > Project: OFBiz > Issue Type: New Feature > Components: ecommerce >Affects Versions: Trunk >Reporter: Deepak Nigam >Assignee: Swapnil M Mane >Priority: Minor > Attachments: OFBIZ-10639.patch, OFBIZ-10639.patch > > > As per discussion on Dev ML [https://markmail.org/message/rcatehtckz6vlvuv] > The Cookie Law is a piece of privacy legislation that requires websites to > get consent from visitors to store or retrieve any information on their > computer, smartphone or tablet. It was designed to protect online privacy, by > making consumers aware of how information about them is collected and used > online, and give them a choice to allow it or not. > > The EU Cookie Legislation began as a directive from the European Union. Some > variation on the policy has since been adopted by all countries within the EU. > > The EU Cookie Legislation requires 4 actions from
[jira] [Commented] (OFBIZ-10639) Cookie Consent In E-Commerce
[ https://issues.apache.org/jira/browse/OFBIZ-10639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16862847#comment-16862847 ] Deepak Nigam commented on OFBIZ-10639: -- Thanks [~aditya.sharma] and [~jacques.le.roux]. Please find responses to your queries and suggestions below: _"I think we should avoid renaming the external library and its variable names (ihavecookies). Apart from this we should not modify its headers. As per my understanding license headers are added for custom files specific to OFBiz and external files are kept as it is."_ By keeping in mind about MIT license, I changed the name of variables to make them more relevant to the functionality. However, we can keep the previous name also. I also removed some code from the plugin which is not required in our case. I am not sure if we can add OFBiz license header files for the customized files having MIT license. Please help me with this. _"Also we should provide not only the minified library but also its plain source code version"_ I will add the plain source code file also. _"are the changes in custom.css custom or copied from the ihavecookies project (example.css file)? "_ Changes in custom.css files are copied from Example.css but I made some customizations for a better look and feel. _"And last but not least we prefer to generate our patches from root, easier for reviewers to apply and test"_ This patch was created from the root of the e-commerce component. I am able to apply it from there. _"Could you explain why init.js would be better than eg InitCookieConsent.js for new custom code. It's not clear to me and I would prefer the later."_ By custom code in Init.js, I mean initialization blocks of other plugins and libraries. It will be a common file for all initialization blocks. However, InitCookieConsent.js is also fine we want to keep it specific to this cookie consent feature. > Cookie Consent In E-Commerce > > > Key: OFBIZ-10639 > URL: https://issues.apache.org/jira/browse/OFBIZ-10639 > Project: OFBiz > Issue Type: New Feature > Components: ecommerce >Affects Versions: Trunk >Reporter: Deepak Nigam >Assignee: Swapnil M Mane >Priority: Minor > Attachments: OFBIZ-10639.patch, OFBIZ-10639.patch > > > As per discussion on Dev ML [https://markmail.org/message/rcatehtckz6vlvuv] > The Cookie Law is a piece of privacy legislation that requires websites to > get consent from visitors to store or retrieve any information on their > computer, smartphone or tablet. It was designed to protect online privacy, by > making consumers aware of how information about them is collected and used > online, and give them a choice to allow it or not. > > The EU Cookie Legislation began as a directive from the European Union. Some > variation on the policy has since been adopted by all countries within the EU. > > The EU Cookie Legislation requires 4 actions from website owners who use > cookies: > 1. When someone visits your website, you need to let them know that your > site uses cookies. > 2. You need to provide detailed information regarding how that cookie data > will be utilized. > 3. You need to provide visitors with some means of accepting or refusing the > use of cookies in your site. > 4. If they refuse, you need to ensure that cookies will not be placed on > their machine. > > For more information about EU cookie policy, please visit > [here|http://ec.europa.eu/ipg/basics/legal/cookies/index_en.htm]. > > As this crucial feature is missing in OFBiz E-Commerce application, we > should work towards its implementation. There are numerous open-source jQuery > plugins available which we can use. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10639) Cookie Consent In E-Commerce
[ https://issues.apache.org/jira/browse/OFBIZ-10639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861194#comment-16861194 ] Deepak Nigam commented on OFBIZ-10639: -- Uploaded the updated patch with following changes: 1) Replaced $ by jQuery. 2) Added license header in new files. 3) Modified name of some variables. Apart from this, I am also in favor of keeping the name of the file init.js as it is. That will be helpful further for new custom code. > Cookie Consent In E-Commerce > > > Key: OFBIZ-10639 > URL: https://issues.apache.org/jira/browse/OFBIZ-10639 > Project: OFBiz > Issue Type: New Feature > Components: ecommerce >Affects Versions: Trunk >Reporter: Deepak Nigam >Assignee: Swapnil M Mane >Priority: Minor > Attachments: OFBIZ-10639.patch, OFBIZ-10639.patch > > > As per discussion on Dev ML [https://markmail.org/message/rcatehtckz6vlvuv] > The Cookie Law is a piece of privacy legislation that requires websites to > get consent from visitors to store or retrieve any information on their > computer, smartphone or tablet. It was designed to protect online privacy, by > making consumers aware of how information about them is collected and used > online, and give them a choice to allow it or not. > > The EU Cookie Legislation began as a directive from the European Union. Some > variation on the policy has since been adopted by all countries within the EU. > > The EU Cookie Legislation requires 4 actions from website owners who use > cookies: > 1. When someone visits your website, you need to let them know that your > site uses cookies. > 2. You need to provide detailed information regarding how that cookie data > will be utilized. > 3. You need to provide visitors with some means of accepting or refusing the > use of cookies in your site. > 4. If they refuse, you need to ensure that cookies will not be placed on > their machine. > > For more information about EU cookie policy, please visit > [here|http://ec.europa.eu/ipg/basics/legal/cookies/index_en.htm]. > > As this crucial feature is missing in OFBiz E-Commerce application, we > should work towards its implementation. There are numerous open-source jQuery > plugins available which we can use. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10639) Cookie Consent In E-Commerce
[ https://issues.apache.org/jira/browse/OFBIZ-10639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10639: - Attachment: OFBIZ-10639.patch > Cookie Consent In E-Commerce > > > Key: OFBIZ-10639 > URL: https://issues.apache.org/jira/browse/OFBIZ-10639 > Project: OFBiz > Issue Type: New Feature > Components: ecommerce >Affects Versions: Trunk >Reporter: Deepak Nigam >Assignee: Swapnil M Mane >Priority: Minor > Attachments: OFBIZ-10639.patch, OFBIZ-10639.patch > > > As per discussion on Dev ML [https://markmail.org/message/rcatehtckz6vlvuv] > The Cookie Law is a piece of privacy legislation that requires websites to > get consent from visitors to store or retrieve any information on their > computer, smartphone or tablet. It was designed to protect online privacy, by > making consumers aware of how information about them is collected and used > online, and give them a choice to allow it or not. > > The EU Cookie Legislation began as a directive from the European Union. Some > variation on the policy has since been adopted by all countries within the EU. > > The EU Cookie Legislation requires 4 actions from website owners who use > cookies: > 1. When someone visits your website, you need to let them know that your > site uses cookies. > 2. You need to provide detailed information regarding how that cookie data > will be utilized. > 3. You need to provide visitors with some means of accepting or refusing the > use of cookies in your site. > 4. If they refuse, you need to ensure that cookies will not be placed on > their machine. > > For more information about EU cookie policy, please visit > [here|http://ec.europa.eu/ipg/basics/legal/cookies/index_en.htm]. > > As this crucial feature is missing in OFBiz E-Commerce application, we > should work towards its implementation. There are numerous open-source jQuery > plugins available which we can use. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10639) Cookie Consent In E-Commerce
[ https://issues.apache.org/jira/browse/OFBIZ-10639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16857279#comment-16857279 ] Deepak Nigam commented on OFBIZ-10639: -- Thanks for your inputs [~aditya.sharma] and [~jacques.le.roux]. I will upload the updated patch soon. > Cookie Consent In E-Commerce > > > Key: OFBIZ-10639 > URL: https://issues.apache.org/jira/browse/OFBIZ-10639 > Project: OFBiz > Issue Type: New Feature > Components: ecommerce >Affects Versions: Trunk >Reporter: Deepak Nigam >Assignee: Swapnil M Mane >Priority: Minor > Attachments: OFBIZ-10639.patch > > > As per discussion on Dev ML [https://markmail.org/message/rcatehtckz6vlvuv] > The Cookie Law is a piece of privacy legislation that requires websites to > get consent from visitors to store or retrieve any information on their > computer, smartphone or tablet. It was designed to protect online privacy, by > making consumers aware of how information about them is collected and used > online, and give them a choice to allow it or not. > > The EU Cookie Legislation began as a directive from the European Union. Some > variation on the policy has since been adopted by all countries within the EU. > > The EU Cookie Legislation requires 4 actions from website owners who use > cookies: > 1. When someone visits your website, you need to let them know that your > site uses cookies. > 2. You need to provide detailed information regarding how that cookie data > will be utilized. > 3. You need to provide visitors with some means of accepting or refusing the > use of cookies in your site. > 4. If they refuse, you need to ensure that cookies will not be placed on > their machine. > > For more information about EU cookie policy, please visit > [here|http://ec.europa.eu/ipg/basics/legal/cookies/index_en.htm]. > > As this crucial feature is missing in OFBiz E-Commerce application, we > should work towards its implementation. There are numerous open-source jQuery > plugins available which we can use. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10639) Cookie Consent In E-Commerce
[ https://issues.apache.org/jira/browse/OFBIZ-10639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16848100#comment-16848100 ] Deepak Nigam commented on OFBIZ-10639: -- Provided the patch for cookie consent policy. The labels and styling used in the cookie consent pop-up are customizable through init.js and custom.css. Also created a new page for cookie policy and used lorem ipsum text in it. Users can put their own content for this page through the following data: > Cookie Consent In E-Commerce > > > Key: OFBIZ-10639 > URL: https://issues.apache.org/jira/browse/OFBIZ-10639 > Project: OFBiz > Issue Type: New Feature > Components: ecommerce >Affects Versions: Trunk >Reporter: Deepak Nigam >Assignee: Deepak Nigam >Priority: Minor > Attachments: OFBIZ-10639.patch > > > As per discussion on Dev ML [https://markmail.org/message/rcatehtckz6vlvuv] > The Cookie Law is a piece of privacy legislation that requires websites to > get consent from visitors to store or retrieve any information on their > computer, smartphone or tablet. It was designed to protect online privacy, by > making consumers aware of how information about them is collected and used > online, and give them a choice to allow it or not. > > The EU Cookie Legislation began as a directive from the European Union. Some > variation on the policy has since been adopted by all countries within the EU. > > The EU Cookie Legislation requires 4 actions from website owners who use > cookies: > 1. When someone visits your website, you need to let them know that your > site uses cookies. > 2. You need to provide detailed information regarding how that cookie data > will be utilized. > 3. You need to provide visitors with some means of accepting or refusing the > use of cookies in your site. > 4. If they refuse, you need to ensure that cookies will not be placed on > their machine. > > For more information about EU cookie policy, please visit > [here|http://ec.europa.eu/ipg/basics/legal/cookies/index_en.htm]. > > As this crucial feature is missing in OFBiz E-Commerce application, we > should work towards its implementation. There are numerous open-source jQuery > plugins available which we can use. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10639) Cookie Consent In E-Commerce
[ https://issues.apache.org/jira/browse/OFBIZ-10639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10639: - Attachment: OFBIZ-10639.patch > Cookie Consent In E-Commerce > > > Key: OFBIZ-10639 > URL: https://issues.apache.org/jira/browse/OFBIZ-10639 > Project: OFBiz > Issue Type: New Feature > Components: ecommerce >Affects Versions: Trunk >Reporter: Deepak Nigam >Assignee: Deepak Nigam >Priority: Minor > Attachments: OFBIZ-10639.patch > > > As per discussion on Dev ML [https://markmail.org/message/rcatehtckz6vlvuv] > The Cookie Law is a piece of privacy legislation that requires websites to > get consent from visitors to store or retrieve any information on their > computer, smartphone or tablet. It was designed to protect online privacy, by > making consumers aware of how information about them is collected and used > online, and give them a choice to allow it or not. > > The EU Cookie Legislation began as a directive from the European Union. Some > variation on the policy has since been adopted by all countries within the EU. > > The EU Cookie Legislation requires 4 actions from website owners who use > cookies: > 1. When someone visits your website, you need to let them know that your > site uses cookies. > 2. You need to provide detailed information regarding how that cookie data > will be utilized. > 3. You need to provide visitors with some means of accepting or refusing the > use of cookies in your site. > 4. If they refuse, you need to ensure that cookies will not be placed on > their machine. > > For more information about EU cookie policy, please visit > [here|http://ec.europa.eu/ipg/basics/legal/cookies/index_en.htm]. > > As this crucial feature is missing in OFBiz E-Commerce application, we > should work towards its implementation. There are numerous open-source jQuery > plugins available which we can use. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10993) error while loading seeddata
[ https://issues.apache.org/jira/browse/OFBIZ-10993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16828968#comment-16828968 ] Deepak Nigam commented on OFBIZ-10993: -- Hi [~Arshithakmanaf], it seems the entities and data you are referring, are your customized things. You will have to provide entity definitions and the data you are trying to load. At first glance, it looks like you are not entering the value in the column 'HELLO_PERSON_ID'. > error while loading seeddata > > > Key: OFBIZ-10993 > URL: https://issues.apache.org/jira/browse/OFBIZ-10993 > Project: OFBiz > Issue Type: Bug > Components: framework/webtools >Reporter: Arshitha k m >Priority: Major > > hi, > I am new to OFBiz .completed hello1and hello2 .currentlyfacing an issue to > import the seed data .iam getting an error as shown below, > The Following Errors Occurred: > ERROR: parsing file: ERROR parsing Entity Xml file: org.xml.sax.SAXException: > A transaction error occurred reading > dataorg.ofbiz.entity.GenericEntityException: > org.ofbiz.entity.GenericEntityException: > org.ofbiz.entity.GenericEntityException: Error while inserting: > [GenericEntity:HelloHobby][createdStamp,2019-04-29 > 12:08:55.606(java.sql.Timestamp)][createdTxStamp,2019-04-29 > 12:08:55.154(java.sql.Timestamp)][description,Reading(java.lang.String)][helloHobbyId,READING(java.lang.String)][lastUpdatedStamp,2019-04-29 > 12:08:55.606(java.sql.Timestamp)][lastUpdatedTxStamp,2019-04-29 > 12:08:55.154(java.sql.Timestamp)] (SQL Exception while executing the > following:INSERT INTO OFBIZ.HELLO_HOBBY (HELLO_HOBBY_ID, DESCRIPTION, > LAST_UPDATED_STAMP, LAST_UPDATED_TX_STAMP, CREATED_STAMP, CREATED_TX_STAMP) > VALUES (?, ?, ?, ?, ?, ?) (Column 'HELLO_PERSON_ID' cannot accept a NULL > value.)) > tried to load seed data to the HelloPerson ,and that was successfull, > can you please help me to fix the trouble. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827589#comment-16827589 ] Deepak Nigam commented on OFBIZ-10518: -- For enabling this feature productStore.allocateInventory should be equal to Y. > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Suraj Khurana >Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, CreateAllocationPlanEditMode-Step2.png, > EditAllocationPlan.png, FindAllocationPlan.png, OFBiz-10518-UI.patch, > OFBiz-10518-data.patch, OFBiz-10518-entity-model.patch, > OFBiz-10518-secas.patch, OFBiz-10518-services.patch, > OFBiz-10518-ui-labels.patch, OFBiz-10518.patch, OFBiz-10518.patch, > OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, > ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10518: - Attachment: OFBiz-10518-services.patch > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Suraj Khurana >Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, CreateAllocationPlanEditMode-Step2.png, > EditAllocationPlan.png, FindAllocationPlan.png, OFBiz-10518-UI.patch, > OFBiz-10518-data.patch, OFBiz-10518-entity-model.patch, > OFBiz-10518-secas.patch, OFBiz-10518-services.patch, > OFBiz-10518-ui-labels.patch, OFBiz-10518.patch, OFBiz-10518.patch, > OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, > ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10518: - Attachment: (was: OFBiz-10518-services.patch) > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Suraj Khurana >Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, CreateAllocationPlanEditMode-Step2.png, > EditAllocationPlan.png, FindAllocationPlan.png, OFBiz-10518-UI.patch, > OFBiz-10518-data.patch, OFBiz-10518-entity-model.patch, > OFBiz-10518-secas.patch, OFBiz-10518-ui-labels.patch, OFBiz-10518.patch, > OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, > ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10518: - Attachment: OFBiz-10518.patch > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Suraj Khurana >Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, CreateAllocationPlanEditMode-Step2.png, > EditAllocationPlan.png, FindAllocationPlan.png, OFBiz-10518-UI.patch, > OFBiz-10518-data.patch, OFBiz-10518-entity-model.patch, > OFBiz-10518-secas.patch, OFBiz-10518-ui-labels.patch, OFBiz-10518.patch, > OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, > OFBiz-10518.patch, ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10518: - Attachment: (was: OFBiz-10518.patch) > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Suraj Khurana >Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, CreateAllocationPlanEditMode-Step2.png, > EditAllocationPlan.png, FindAllocationPlan.png, OFBiz-10518-UI.patch, > OFBiz-10518-data.patch, OFBiz-10518-entity-model.patch, > OFBiz-10518-secas.patch, OFBiz-10518-services.patch, > OFBiz-10518-ui-labels.patch, OFBiz-10518.patch, OFBiz-10518.patch, > OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, > ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10518: - Attachment: (was: OFBiz-10518.patch) > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Suraj Khurana >Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, CreateAllocationPlanEditMode-Step2.png, > EditAllocationPlan.png, FindAllocationPlan.png, OFBiz-10518-UI.patch, > OFBiz-10518-data.patch, OFBiz-10518-entity-model.patch, > OFBiz-10518-secas.patch, OFBiz-10518-services.patch, > OFBiz-10518-ui-labels.patch, OFBiz-10518.patch, OFBiz-10518.patch, > OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, > ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10518: - Attachment: (was: OFBiz-10518-UI.patch) > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Suraj Khurana >Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, CreateAllocationPlanEditMode-Step2.png, > EditAllocationPlan.png, FindAllocationPlan.png, OFBiz-10518-UI.patch, > OFBiz-10518-data.patch, OFBiz-10518-entity-model.patch, > OFBiz-10518-secas.patch, OFBiz-10518-services.patch, > OFBiz-10518-ui-labels.patch, OFBiz-10518.patch, OFBiz-10518.patch, > OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, > ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10518: - Attachment: OFBiz-10518-UI.patch > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Suraj Khurana >Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, CreateAllocationPlanEditMode-Step2.png, > EditAllocationPlan.png, FindAllocationPlan.png, OFBiz-10518-UI.patch, > OFBiz-10518-data.patch, OFBiz-10518-entity-model.patch, > OFBiz-10518-secas.patch, OFBiz-10518-services.patch, > OFBiz-10518-ui-labels.patch, OFBiz-10518.patch, OFBiz-10518.patch, > OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, > ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10518: - Attachment: OFBiz-10518.patch > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Suraj Khurana >Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, CreateAllocationPlanEditMode-Step2.png, > EditAllocationPlan.png, FindAllocationPlan.png, OFBiz-10518-UI.patch, > OFBiz-10518-data.patch, OFBiz-10518-entity-model.patch, > OFBiz-10518-secas.patch, OFBiz-10518-services.patch, > OFBiz-10518-ui-labels.patch, OFBiz-10518.patch, OFBiz-10518.patch, > OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, > ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10518: - Attachment: (was: OFBiz-10518.patch) > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Suraj Khurana >Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, CreateAllocationPlanEditMode-Step2.png, > EditAllocationPlan.png, FindAllocationPlan.png, OFBiz-10518-UI.patch, > OFBiz-10518-data.patch, OFBiz-10518-entity-model.patch, > OFBiz-10518-secas.patch, OFBiz-10518-services.patch, > OFBiz-10518-ui-labels.patch, OFBiz-10518.patch, OFBiz-10518.patch, > OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, > ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10518: - Attachment: OFBiz-10518.patch > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Suraj Khurana >Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, CreateAllocationPlanEditMode-Step2.png, > EditAllocationPlan.png, FindAllocationPlan.png, OFBiz-10518-UI.patch, > OFBiz-10518-data.patch, OFBiz-10518-entity-model.patch, > OFBiz-10518-secas.patch, OFBiz-10518-services.patch, > OFBiz-10518-ui-labels.patch, OFBiz-10518.patch, OFBiz-10518.patch, > OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, > ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10518: - Attachment: (was: OFBiz-10518-services.patch) > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Suraj Khurana >Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, CreateAllocationPlanEditMode-Step2.png, > EditAllocationPlan.png, FindAllocationPlan.png, OFBiz-10518-UI.patch, > OFBiz-10518-data.patch, OFBiz-10518-entity-model.patch, > OFBiz-10518-secas.patch, OFBiz-10518-services.patch, > OFBiz-10518-ui-labels.patch, OFBiz-10518.patch, OFBiz-10518.patch, > OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, > ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10518: - Attachment: OFBiz-10518-services.patch > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Suraj Khurana >Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, CreateAllocationPlanEditMode-Step2.png, > EditAllocationPlan.png, FindAllocationPlan.png, OFBiz-10518-UI.patch, > OFBiz-10518-data.patch, OFBiz-10518-entity-model.patch, > OFBiz-10518-secas.patch, OFBiz-10518-services.patch, > OFBiz-10518-ui-labels.patch, OFBiz-10518.patch, OFBiz-10518.patch, > OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, > ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10518: - Attachment: (was: OFBiz-10518-entity-model.patch) > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Suraj Khurana >Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, CreateAllocationPlanEditMode-Step2.png, > EditAllocationPlan.png, FindAllocationPlan.png, OFBiz-10518-UI.patch, > OFBiz-10518-data.patch, OFBiz-10518-entity-model.patch, > OFBiz-10518-secas.patch, OFBiz-10518-services.patch, > OFBiz-10518-ui-labels.patch, OFBiz-10518.patch, OFBiz-10518.patch, > OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, > ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827441#comment-16827441 ] Deepak Nigam commented on OFBIZ-10518: -- Updated the patches wrt latest codebase of trunk. > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Suraj Khurana >Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, CreateAllocationPlanEditMode-Step2.png, > EditAllocationPlan.png, FindAllocationPlan.png, OFBiz-10518-UI.patch, > OFBiz-10518-data.patch, OFBiz-10518-entity-model.patch, > OFBiz-10518-entity-model.patch, OFBiz-10518-secas.patch, > OFBiz-10518-services.patch, OFBiz-10518-ui-labels.patch, OFBiz-10518.patch, > OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, > OFBiz-10518.patch, ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10518: - Attachment: OFBiz-10518-entity-model.patch > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Suraj Khurana >Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, CreateAllocationPlanEditMode-Step2.png, > EditAllocationPlan.png, FindAllocationPlan.png, OFBiz-10518-UI.patch, > OFBiz-10518-data.patch, OFBiz-10518-entity-model.patch, > OFBiz-10518-entity-model.patch, OFBiz-10518-secas.patch, > OFBiz-10518-services.patch, OFBiz-10518-ui-labels.patch, OFBiz-10518.patch, > OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, > OFBiz-10518.patch, ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826903#comment-16826903 ] Deepak Nigam commented on OFBIZ-10518: -- Thanks [~suraj.khurana]. Yes, we can commit patches in chunks. > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Suraj Khurana >Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, CreateAllocationPlanEditMode-Step2.png, > EditAllocationPlan.png, FindAllocationPlan.png, OFBiz-10518-UI.patch, > OFBiz-10518-data.patch, OFBiz-10518-entity-model.patch, > OFBiz-10518-secas.patch, OFBiz-10518-services.patch, > OFBiz-10518-ui-labels.patch, OFBiz-10518.patch, OFBiz-10518.patch, > OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, > ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16805630#comment-16805630 ] Deepak Nigam commented on OFBIZ-10518: -- Added mini-patches in place of one big patch. It will help in reviewing the code easily. > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Deepak Nigam >Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, CreateAllocationPlanEditMode-Step2.png, > EditAllocationPlan.png, FindAllocationPlan.png, OFBiz-10518-UI.patch, > OFBiz-10518-data.patch, OFBiz-10518-entity-model.patch, > OFBiz-10518-secas.patch, OFBiz-10518-services.patch, > OFBiz-10518-ui-labels.patch, OFBiz-10518.patch, OFBiz-10518.patch, > OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, > ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10518: - Attachment: OFBiz-10518-services.patch OFBiz-10518-UI.patch OFBiz-10518-secas.patch OFBiz-10518-ui-labels.patch OFBiz-10518-entity-model.patch OFBiz-10518-data.patch > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Deepak Nigam >Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, CreateAllocationPlanEditMode-Step2.png, > EditAllocationPlan.png, FindAllocationPlan.png, OFBiz-10518-UI.patch, > OFBiz-10518-data.patch, OFBiz-10518-entity-model.patch, > OFBiz-10518-secas.patch, OFBiz-10518-services.patch, > OFBiz-10518-ui-labels.patch, OFBiz-10518.patch, OFBiz-10518.patch, > OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, > ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10766) Impossible secure and autologin cookie names when mountpoint contains a slash inside its name
[ https://issues.apache.org/jira/browse/OFBIZ-10766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10766: - Attachment: OFBIZ-10766.patch > Impossible secure and autologin cookie names when mountpoint contains a slash > inside its name > - > > Key: OFBIZ-10766 > URL: https://issues.apache.org/jira/browse/OFBIZ-10766 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Trunk, Release Branch 16.11, Release Branch 17.12, > Release Branch 18.12 >Reporter: Jacques Le Roux >Assignee: Deepak Nigam >Priority: Major > Fix For: 17.12.01, 16.11.06, 18.12.01 > > Attachments: OFBIZ-10766.patch, OFBIZ-10766.patch > > > When you set a mountpoint which contains a slash inside its name (ie not only > a slash as a trailer, which is possible), as it's needed with OFBIZ-10765, > OFBiz tries to create a cookie with a slash in its name and [that's > impossible|https://stackoverflow.com/questions/1969232/allowed-characters-in-cookies]. > This was reported by [~mz4wheeler] on [ilscipio > forum|https://forum.scipioerp.com/t/control-payment-type-options-in-store/215/53] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10766) Impossible secure and autologin cookie names when mountpoint contains a slash inside its name
[ https://issues.apache.org/jira/browse/OFBIZ-10766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16750737#comment-16750737 ] Deepak Nigam commented on OFBIZ-10766: -- Hi [~jacques.le.roux], I tested the patch for one of my custom projects, having a web app with empty mount-point. It is looking good to me. However, I have slightly improved your patch by setting the auto-login cookie path in LoginWorker::autoLoginRemove, in a similar fashion. Attached the updated patch here. > Impossible secure and autologin cookie names when mountpoint contains a slash > inside its name > - > > Key: OFBIZ-10766 > URL: https://issues.apache.org/jira/browse/OFBIZ-10766 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Trunk, Release Branch 16.11, Release Branch 17.12, > Release Branch 18.12 >Reporter: Jacques Le Roux >Assignee: Deepak Nigam >Priority: Major > Fix For: 17.12.01, 16.11.06, 18.12.01 > > Attachments: OFBIZ-10766.patch > > > When you set a mountpoint which contains a slash inside its name (ie not only > a slash as a trailer, which is possible), as it's needed with OFBIZ-10765, > OFBiz tries to create a cookie with a slash in its name and [that's > impossible|https://stackoverflow.com/questions/1969232/allowed-characters-in-cookies]. > This was reported by [~mz4wheeler] on [ilscipio > forum|https://forum.scipioerp.com/t/control-payment-type-options-in-store/215/53] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10766) Impossible secure and autologin cookie names when mountpoint contains a slash inside its name
[ https://issues.apache.org/jira/browse/OFBIZ-10766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16750699#comment-16750699 ] Deepak Nigam commented on OFBIZ-10766: -- Thanks for the patch [~jacques.le.roux], I will check it soon. > Impossible secure and autologin cookie names when mountpoint contains a slash > inside its name > - > > Key: OFBIZ-10766 > URL: https://issues.apache.org/jira/browse/OFBIZ-10766 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Trunk, Release Branch 16.11, Release Branch 17.12, > Release Branch 18.12 >Reporter: Jacques Le Roux >Assignee: Deepak Nigam >Priority: Major > Fix For: 17.12.01, 16.11.06, 18.12.01 > > Attachments: OFBIZ-10766.patch > > > When you set a mountpoint which contains a slash inside its name (ie not only > a slash as a trailer, which is possible), as it's needed with OFBIZ-10765, > OFBiz tries to create a cookie with a slash in its name and [that's > impossible|https://stackoverflow.com/questions/1969232/allowed-characters-in-cookies]. > This was reported by [~mz4wheeler] on [ilscipio > forum|https://forum.scipioerp.com/t/control-payment-type-options-in-store/215/53] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (OFBIZ-10666) User's name is displayed on ecommerce even after user logs out
[ https://issues.apache.org/jira/browse/OFBIZ-10666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16743633#comment-16743633 ] Deepak Nigam edited comment on OFBIZ-10666 at 1/16/19 5:35 AM: --- Thanks for sharing "[the Onion parody|https://www.theonion.com/after-checking-your-bank-account-remember-to-log-out-1819584860];, [~jacques.le.roux]. It is quite interesting, however difficult to grasp in first few readings. ;) was (Author: deepak.nigam): Thanks for sharing "[the Onion parody|https://www.theonion.com/after-checking-your-bank-account-remember-to-log-out-1819584860];. It is quite interesting, however difficult to grasp in first few readings. ;) > User's name is displayed on ecommerce even after user logs out > -- > > Key: OFBIZ-10666 > URL: https://issues.apache.org/jira/browse/OFBIZ-10666 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Trunk >Reporter: Arpit Mor >Assignee: Jacques Le Roux >Priority: Major > Fix For: 17.12.01, 16.11.06, 18.12.01 > > Attachments: 1-OpenURL.png, 2-LoggedIn.png, 3-LoggedOut.png, > 4-NotYou.png, OFBIZ-10666.patch, OFBiz-10666.patch > > > Steps to regenerate: > # Open URL: [https://demo-trunk.ofbiz.apache.org/ecommerce/control/main]. > Welcome is displayed and user's name is not displayed when URL is opened. > (Please refer attachment: 1-OpenURL) > # Login at ecommerce by clicking on login and entering Username: "admin" and > Password: "ofbiz". Username will be displayed after user logs in. (Please > refer attachment: 2-LoggedIn) > # Logout of ecommerce by clicking on logout. User will be logged out and > login link will be displayed in place of logout link, but the name of user is > still displayed. (Please refer attachment: 3-LoggedOut) > Actual: Username is still displayed after user logs out > > Expected: Username should not be displayed after the user logs out > > Note: Similar issue also exists when the user clicks on (Not You? Click Here) > link. (Please refer attachment: 4-NotYou) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10666) User's name is displayed on ecommerce even after user logs out
[ https://issues.apache.org/jira/browse/OFBIZ-10666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16743633#comment-16743633 ] Deepak Nigam commented on OFBIZ-10666: -- Thanks for sharing "[the Onion parody|https://www.theonion.com/after-checking-your-bank-account-remember-to-log-out-1819584860];. It is quite interesting, however difficult to grasp in first few readings. ;) > User's name is displayed on ecommerce even after user logs out > -- > > Key: OFBIZ-10666 > URL: https://issues.apache.org/jira/browse/OFBIZ-10666 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Trunk >Reporter: Arpit Mor >Assignee: Jacques Le Roux >Priority: Major > Fix For: 17.12.01, 16.11.06, 18.12.01 > > Attachments: 1-OpenURL.png, 2-LoggedIn.png, 3-LoggedOut.png, > 4-NotYou.png, OFBIZ-10666.patch, OFBiz-10666.patch > > > Steps to regenerate: > # Open URL: [https://demo-trunk.ofbiz.apache.org/ecommerce/control/main]. > Welcome is displayed and user's name is not displayed when URL is opened. > (Please refer attachment: 1-OpenURL) > # Login at ecommerce by clicking on login and entering Username: "admin" and > Password: "ofbiz". Username will be displayed after user logs in. (Please > refer attachment: 2-LoggedIn) > # Logout of ecommerce by clicking on logout. User will be logged out and > login link will be displayed in place of logout link, but the name of user is > still displayed. (Please refer attachment: 3-LoggedOut) > Actual: Username is still displayed after user logs out > > Expected: Username should not be displayed after the user logs out > > Note: Similar issue also exists when the user clicks on (Not You? Click Here) > link. (Please refer attachment: 4-NotYou) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10666) User's name is displayed on ecommerce even after user logs out
[ https://issues.apache.org/jira/browse/OFBIZ-10666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10666: - Attachment: OFBiz-10666.patch > User's name is displayed on ecommerce even after user logs out > -- > > Key: OFBIZ-10666 > URL: https://issues.apache.org/jira/browse/OFBIZ-10666 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Trunk >Reporter: Arpit Mor >Assignee: Jacques Le Roux >Priority: Major > Fix For: 17.12.01, 16.11.06 > > Attachments: 1-OpenURL.png, 2-LoggedIn.png, 3-LoggedOut.png, > 4-NotYou.png, OFBIZ-10666.patch, OFBiz-10666.patch > > > Steps to regenerate: > # Open URL: [https://demo-trunk.ofbiz.apache.org/ecommerce/control/main]. > Welcome is displayed and user's name is not displayed when URL is opened. > (Please refer attachment: 1-OpenURL) > # Login at ecommerce by clicking on login and entering Username: "admin" and > Password: "ofbiz". Username will be displayed after user logs in. (Please > refer attachment: 2-LoggedIn) > # Logout of ecommerce by clicking on logout. User will be logged out and > login link will be displayed in place of logout link, but the name of user is > still displayed. (Please refer attachment: 3-LoggedOut) > Actual: Username is still displayed after user logs out > > Expected: Username should not be displayed after the user logs out > > Note: Similar issue also exists when the user clicks on (Not You? Click Here) > link. (Please refer attachment: 4-NotYou) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10666) User's name is displayed on ecommerce even after user logs out
[ https://issues.apache.org/jira/browse/OFBIZ-10666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741879#comment-16741879 ] Deepak Nigam commented on OFBIZ-10666: -- It seems that the actual problem is not 'autoName' (at least for this particular issue). On further investigation, I found that cookie path and domain are different in the methods of creating the auto-login cookie i.e. LoginWorker.autoLoginSet() and removing the auto-login cookie i.e. LoginWorker.autoLoginRemove(). After following changes the issue seems to be fixed: 1. Removed getMaxAge() check from the condition used in LoginWorker.getAutoUserLoginId() method. 2. Corrected the path and domain in the method LoginWorker.autoLoginRemove(). Please find the attached patch for reference and commit. > User's name is displayed on ecommerce even after user logs out > -- > > Key: OFBIZ-10666 > URL: https://issues.apache.org/jira/browse/OFBIZ-10666 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Trunk >Reporter: Arpit Mor >Assignee: Jacques Le Roux >Priority: Major > Fix For: 17.12.01, 16.11.06 > > Attachments: 1-OpenURL.png, 2-LoggedIn.png, 3-LoggedOut.png, > 4-NotYou.png, OFBIZ-10666.patch > > > Steps to regenerate: > # Open URL: [https://demo-trunk.ofbiz.apache.org/ecommerce/control/main]. > Welcome is displayed and user's name is not displayed when URL is opened. > (Please refer attachment: 1-OpenURL) > # Login at ecommerce by clicking on login and entering Username: "admin" and > Password: "ofbiz". Username will be displayed after user logs in. (Please > refer attachment: 2-LoggedIn) > # Logout of ecommerce by clicking on logout. User will be logged out and > login link will be displayed in place of logout link, but the name of user is > still displayed. (Please refer attachment: 3-LoggedOut) > Actual: Username is still displayed after user logs out > > Expected: Username should not be displayed after the user logs out > > Note: Similar issue also exists when the user clicks on (Not You? Click Here) > link. (Please refer attachment: 4-NotYou) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (OFBIZ-10666) User's name is displayed on ecommerce even after user logs out
[ https://issues.apache.org/jira/browse/OFBIZ-10666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741761#comment-16741761 ] Deepak Nigam edited comment on OFBIZ-10666 at 1/14/19 4:56 AM: --- Thanks for the detailed research [~jacques.le.roux]. I have already tried by removing getMaxAge() from LoginWorker.getAutoUserLoginId() and setMaxAge(0) in the method LoginWorker.autoLoginRemove(). Even after setting the max age 0 I was getting the auto-login cookie from the cookies array inside LoginWorker.getAutoUserLoginId() method. It means the above statement "If a cookie has expired, the browser does not send that particular cookie to the server with the page request; instead, the expired cookie is deleted." is not 100% correct. So, if we remove the getMaxAge() check from the condition, then the issue reported in this ticket will come again. was (Author: deepak.nigam): Thanks for the detailed research [~jacques.le.roux]. I have already tried by removing getMaxAge() from LoginWorker.getAutoUserLoginId() and setMaxAge(0). Even after setting the max age 0 I was getting the auto-login cookie from the cookies array inside LoginWorker.getAutoUserLoginId() method. It means the above statement "If a cookie has expired, the browser does not send that particular cookie to the server with the page request; instead, the expired cookie is deleted." is not 100% correct. So, if we remove the getMaxAge() check from the condition, then the issue reported in this ticket will come again. > User's name is displayed on ecommerce even after user logs out > -- > > Key: OFBIZ-10666 > URL: https://issues.apache.org/jira/browse/OFBIZ-10666 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Trunk >Reporter: Arpit Mor >Assignee: Jacques Le Roux >Priority: Major > Fix For: 17.12.01, 16.11.06 > > Attachments: 1-OpenURL.png, 2-LoggedIn.png, 3-LoggedOut.png, > 4-NotYou.png, OFBIZ-10666.patch > > > Steps to regenerate: > # Open URL: [https://demo-trunk.ofbiz.apache.org/ecommerce/control/main]. > Welcome is displayed and user's name is not displayed when URL is opened. > (Please refer attachment: 1-OpenURL) > # Login at ecommerce by clicking on login and entering Username: "admin" and > Password: "ofbiz". Username will be displayed after user logs in. (Please > refer attachment: 2-LoggedIn) > # Logout of ecommerce by clicking on logout. User will be logged out and > login link will be displayed in place of logout link, but the name of user is > still displayed. (Please refer attachment: 3-LoggedOut) > Actual: Username is still displayed after user logs out > > Expected: Username should not be displayed after the user logs out > > Note: Similar issue also exists when the user clicks on (Not You? Click Here) > link. (Please refer attachment: 4-NotYou) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10666) User's name is displayed on ecommerce even after user logs out
[ https://issues.apache.org/jira/browse/OFBIZ-10666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741761#comment-16741761 ] Deepak Nigam commented on OFBIZ-10666: -- Thanks for the detailed research [~jacques.le.roux]. I have already tried by removing getMaxAge() from LoginWorker.getAutoUserLoginId() and setMaxAge(0). Even after setting the max age 0 I was getting the auto-login cookie from the cookies array inside LoginWorker.getAutoUserLoginId() method. It means the above statement "If a cookie has expired, the browser does not send that particular cookie to the server with the page request; instead, the expired cookie is deleted." is not 100% correct. So, if we remove the getMaxAge() check from the condition, then the issue reported in this ticket will come again. > User's name is displayed on ecommerce even after user logs out > -- > > Key: OFBIZ-10666 > URL: https://issues.apache.org/jira/browse/OFBIZ-10666 > Project: OFBiz > Issue Type: Bug > Components: ecommerce >Affects Versions: Trunk >Reporter: Arpit Mor >Assignee: Jacques Le Roux >Priority: Major > Fix For: 17.12.01, 16.11.06 > > Attachments: 1-OpenURL.png, 2-LoggedIn.png, 3-LoggedOut.png, > 4-NotYou.png, OFBIZ-10666.patch > > > Steps to regenerate: > # Open URL: [https://demo-trunk.ofbiz.apache.org/ecommerce/control/main]. > Welcome is displayed and user's name is not displayed when URL is opened. > (Please refer attachment: 1-OpenURL) > # Login at ecommerce by clicking on login and entering Username: "admin" and > Password: "ofbiz". Username will be displayed after user logs in. (Please > refer attachment: 2-LoggedIn) > # Logout of ecommerce by clicking on logout. User will be logged out and > login link will be displayed in place of logout link, but the name of user is > still displayed. (Please refer attachment: 3-LoggedOut) > Actual: Username is still displayed after user logs out > > Expected: Username should not be displayed after the user logs out > > Note: Similar issue also exists when the user clicks on (Not You? Click Here) > link. (Please refer attachment: 4-NotYou) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10639) Cookie Consent In E-Commerce
[ https://issues.apache.org/jira/browse/OFBIZ-10639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741146#comment-16741146 ] Deepak Nigam commented on OFBIZ-10639: -- Hello all, Did anyone get time to look into this ticket? > Cookie Consent In E-Commerce > > > Key: OFBIZ-10639 > URL: https://issues.apache.org/jira/browse/OFBIZ-10639 > Project: OFBiz > Issue Type: New Feature > Components: ecommerce >Affects Versions: Trunk >Reporter: Deepak Nigam >Assignee: Deepak Nigam >Priority: Minor > > As per discussion on Dev ML [https://markmail.org/message/rcatehtckz6vlvuv] > The Cookie Law is a piece of privacy legislation that requires websites to > get consent from visitors to store or retrieve any information on their > computer, smartphone or tablet. It was designed to protect online privacy, by > making consumers aware of how information about them is collected and used > online, and give them a choice to allow it or not. > > The EU Cookie Legislation began as a directive from the European Union. Some > variation on the policy has since been adopted by all countries within the EU. > > The EU Cookie Legislation requires 4 actions from website owners who use > cookies: > 1. When someone visits your website, you need to let them know that your > site uses cookies. > 2. You need to provide detailed information regarding how that cookie data > will be utilized. > 3. You need to provide visitors with some means of accepting or refusing the > use of cookies in your site. > 4. If they refuse, you need to ensure that cookies will not be placed on > their machine. > > For more information about EU cookie policy, please visit > [here|http://ec.europa.eu/ipg/basics/legal/cookies/index_en.htm]. > > As this crucial feature is missing in OFBiz E-Commerce application, we > should work towards its implementation. There are numerous open-source jQuery > plugins available which we can use. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (OFBIZ-10639) Cookie Consent In E-Commerce
[ https://issues.apache.org/jira/browse/OFBIZ-10639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741146#comment-16741146 ] Deepak Nigam edited comment on OFBIZ-10639 at 1/12/19 8:10 AM: --- Hello all, Did anyone get time to review the proposal of this ticket? was (Author: deepak.nigam): Hello all, Did anyone get time to look into this ticket? > Cookie Consent In E-Commerce > > > Key: OFBIZ-10639 > URL: https://issues.apache.org/jira/browse/OFBIZ-10639 > Project: OFBiz > Issue Type: New Feature > Components: ecommerce >Affects Versions: Trunk >Reporter: Deepak Nigam >Assignee: Deepak Nigam >Priority: Minor > > As per discussion on Dev ML [https://markmail.org/message/rcatehtckz6vlvuv] > The Cookie Law is a piece of privacy legislation that requires websites to > get consent from visitors to store or retrieve any information on their > computer, smartphone or tablet. It was designed to protect online privacy, by > making consumers aware of how information about them is collected and used > online, and give them a choice to allow it or not. > > The EU Cookie Legislation began as a directive from the European Union. Some > variation on the policy has since been adopted by all countries within the EU. > > The EU Cookie Legislation requires 4 actions from website owners who use > cookies: > 1. When someone visits your website, you need to let them know that your > site uses cookies. > 2. You need to provide detailed information regarding how that cookie data > will be utilized. > 3. You need to provide visitors with some means of accepting or refusing the > use of cookies in your site. > 4. If they refuse, you need to ensure that cookies will not be placed on > their machine. > > For more information about EU cookie policy, please visit > [here|http://ec.europa.eu/ipg/basics/legal/cookies/index_en.htm]. > > As this crucial feature is missing in OFBiz E-Commerce application, we > should work towards its implementation. There are numerous open-source jQuery > plugins available which we can use. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-6655) Add session tracking mode and make cookie secure
[
https://issues.apache.org/jira/browse/OFBIZ-6655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepak Nigam updated OFBIZ-6655:
Attachment: OFBiz-6655.patch
> Add session tracking mode and make cookie secure
>
>
> Key: OFBIZ-6655
> URL: https://issues.apache.org/jira/browse/OFBIZ-6655
> Project: OFBiz
> Issue Type: Sub-task
> Components: ALL COMPONENTS
>Affects Versions: Trunk, 14.12.01
>Reporter: Deepak Dixit
>Assignee: Jacques Le Roux
>Priority: Major
> Fix For: 14.12.01, 15.12.01, 17.12.01, 18.12.01
>
> Attachments: OFBIA-6655.applications.patch,
> OFBIZ-6655-programmatically-session-cookies-plugins.patch,
> OFBIZ-6655-programmatically-session-cookies-trunk.patch,
> OFBIZ-6655.framework_themes.patch, OFBIZ-6655_specialpurpose_leftover.patch,
> OFBiz-6655.patch, sessionConifg_ecommerce.patch
>
>
> Need to enhance security at web-app level.
> As per current implementation:
> - The cookie containing the session identifier is not secure
> - The session identifier is transmitted in the query string of the URL
> To fix these issue we have to add following session config otpions in web.xml
> {code}
>
>
> true
> true
>
> COOKIE
>
> {code}
> Also we need to update the web-app servlet specification from 2.3 to 3.0
> {code}
> xmlns="http://java.sun.com/xml/ns/javaee;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
>
> http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd;>
> {code}
> https://tomcat.apache.org/whichversion.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-6655) Add session tracking mode and make cookie secure
[
https://issues.apache.org/jira/browse/OFBIZ-6655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741116#comment-16741116
]
Deepak Nigam commented on OFBIZ-6655:
-
Hi [~jacques.le.roux],
On double checking, I found that
/applications/marketing/webapp/marketing/WEB-INF/web.xml and
/applications/party/webapp/partymgr/WEB-INF/web.xml files have been missed.
Attached the patch for the same.
Apart from that, I think we need to work for web.xml of various plugins also.
> Add session tracking mode and make cookie secure
>
>
> Key: OFBIZ-6655
> URL: https://issues.apache.org/jira/browse/OFBIZ-6655
> Project: OFBiz
> Issue Type: Sub-task
> Components: ALL COMPONENTS
>Affects Versions: Trunk, 14.12.01
>Reporter: Deepak Dixit
>Assignee: Jacques Le Roux
>Priority: Major
> Fix For: 14.12.01, 15.12.01, 17.12.01, 18.12.01
>
> Attachments: OFBIA-6655.applications.patch,
> OFBIZ-6655-programmatically-session-cookies-plugins.patch,
> OFBIZ-6655-programmatically-session-cookies-trunk.patch,
> OFBIZ-6655.framework_themes.patch, OFBIZ-6655_specialpurpose_leftover.patch,
> sessionConifg_ecommerce.patch
>
>
> Need to enhance security at web-app level.
> As per current implementation:
> - The cookie containing the session identifier is not secure
> - The session identifier is transmitted in the query string of the URL
> To fix these issue we have to add following session config otpions in web.xml
> {code}
>
>
> true
> true
>
> COOKIE
>
> {code}
> Also we need to update the web-app servlet specification from 2.3 to 3.0
> {code}
> xmlns="http://java.sun.com/xml/ns/javaee;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
>
> http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd;>
> {code}
> https://tomcat.apache.org/whichversion.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10620) Invoice date is not displayed on findInvoice screen
[ https://issues.apache.org/jira/browse/OFBIZ-10620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10620: - Attachment: OFBiz-10620-Format2.patch > Invoice date is not displayed on findInvoice screen > --- > > Key: OFBIZ-10620 > URL: https://issues.apache.org/jira/browse/OFBIZ-10620 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk > Environment: https://demo-trunk.ofbiz.apache.org >Reporter: Arpit Mor >Assignee: Deepak Nigam >Priority: Minor > Attachments: InvoiceDateFormat1.png, InvoiceDateFormat2.png, > InvoiceDateFormat3.png, OFBiz-10620-Format1.patch, OFBiz-10620-Format2.patch, > findInvoices.png, invoiceOverview.png > > > Steps to regenerate: > # Open URL: > [https://demo-trunk.ofbiz.apache.org/accounting/control/findInvoices] > # Click on find button > Actual: Invoice date is not displayed on findInvoices screen. Please refer > attachment: findInvoices > But when an invoice is created then current date is set as invoice date which > can be viewed on invoiceOverview screen. Please refer attachment: > invoiceOverview > Expected: Invoice date should be displayed on findInvoices screen -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10620) Invoice date is not displayed on findInvoice screen
[ https://issues.apache.org/jira/browse/OFBIZ-10620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10620: - Affects Version/s: Release Branch 18.12 Release Branch 17.12 > Invoice date is not displayed on findInvoice screen > --- > > Key: OFBIZ-10620 > URL: https://issues.apache.org/jira/browse/OFBIZ-10620 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk, Release Branch 17.12, Release Branch 18.12 > Environment: https://demo-trunk.ofbiz.apache.org >Reporter: Arpit Mor >Assignee: Suraj Khurana >Priority: Minor > Attachments: InvoiceDateFormat1.png, InvoiceDateFormat2.png, > InvoiceDateFormat3.png, OFBiz-10620-Format1.patch, OFBiz-10620-Format2.patch, > OFBiz-10620-Format3.patch, findInvoices.png, invoiceOverview.png > > > Steps to regenerate: > # Open URL: > [https://demo-trunk.ofbiz.apache.org/accounting/control/findInvoices] > # Click on find button > Actual: Invoice date is not displayed on findInvoices screen. Please refer > attachment: findInvoices > But when an invoice is created then current date is set as invoice date which > can be viewed on invoiceOverview screen. Please refer attachment: > invoiceOverview > Expected: Invoice date should be displayed on findInvoices screen -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10620) Invoice date is not displayed on findInvoice screen
[ https://issues.apache.org/jira/browse/OFBIZ-10620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741006#comment-16741006 ] Deepak Nigam commented on OFBIZ-10620: -- However, on previous stable release 16.11, this was working fine and the pattern was #2. > Invoice date is not displayed on findInvoice screen > --- > > Key: OFBIZ-10620 > URL: https://issues.apache.org/jira/browse/OFBIZ-10620 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk > Environment: https://demo-trunk.ofbiz.apache.org >Reporter: Arpit Mor >Assignee: Suraj Khurana >Priority: Minor > Attachments: InvoiceDateFormat1.png, InvoiceDateFormat2.png, > InvoiceDateFormat3.png, OFBiz-10620-Format1.patch, OFBiz-10620-Format2.patch, > OFBiz-10620-Format3.patch, findInvoices.png, invoiceOverview.png > > > Steps to regenerate: > # Open URL: > [https://demo-trunk.ofbiz.apache.org/accounting/control/findInvoices] > # Click on find button > Actual: Invoice date is not displayed on findInvoices screen. Please refer > attachment: findInvoices > But when an invoice is created then current date is set as invoice date which > can be viewed on invoiceOverview screen. Please refer attachment: > invoiceOverview > Expected: Invoice date should be displayed on findInvoices screen -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (OFBIZ-10620) Invoice date is not displayed on findInvoice screen
[ https://issues.apache.org/jira/browse/OFBIZ-10620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16740996#comment-16740996 ] Deepak Nigam edited comment on OFBIZ-10620 at 1/12/19 4:57 AM: --- Hello [~suraj.khurana], Yes, the code suggested by you will also work fine. However, I took reference from some other forms inside InvoiceForms.xml like InvoiceHeader, ListInvoiceStatus. Apart from this, there will be a difference in the date pattern: By using the date pattern will be -MM-DD. Please find the attached screenshot 'InvoiceDateFormat1.png'. By using the date pattern will be MM/DD/YY. Please find the attached screenshot 'InvoiceDateFormat2.png'. When I checked the list order and other list screens of invoices, I found another pattern for showing the date, something like . By this code, the date pattern will be -MM-dd HH:mm:ss.SSS. Please find the attached screenshot 'InvoiceDateFormat3.png' for the same. Out of the above 3, the last pattern is making sense to me. Please share your thoughts on the same and commit the respective patch. was (Author: deepak.nigam): Hello [~suraj.khurana], Yes, the code suggested by you will also work fine. However, I took reference from some other forms inside InvoiceForms.xml like InvoiceHeader, ListInvoiceStatus. Apart from this, there will be a difference in the date pattern: By using the date pattern will be -MM-DD. Please find the attached screenshot 'InvoiceDateFormat1.png'. By using the date pattern will be MM/DD/YY. Please find the attached screenshot 'InvoiceDateFormat2.png'. When I checked the list order and other list screens of invoices, I found another pattern for showing the date, something like . By this code, the date pattern will be -MM-dd HH:mm:ss.SSS. Please find the attached screenshot 'InvoiceDateFormat2.png' for the same. Out of the above 3, the last pattern is making sense to me. Please share your thoughts on the same and commit the respective patch. > Invoice date is not displayed on findInvoice screen > --- > > Key: OFBIZ-10620 > URL: https://issues.apache.org/jira/browse/OFBIZ-10620 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk > Environment: https://demo-trunk.ofbiz.apache.org >Reporter: Arpit Mor >Assignee: Deepak Nigam >Priority: Minor > Attachments: InvoiceDateFormat1.png, InvoiceDateFormat2.png, > InvoiceDateFormat3.png, OFBiz-10620-Format1.patch, OFBiz-10620-Format2.patch, > OFBiz-10620-Format3.patch, findInvoices.png, invoiceOverview.png > > > Steps to regenerate: > # Open URL: > [https://demo-trunk.ofbiz.apache.org/accounting/control/findInvoices] > # Click on find button > Actual: Invoice date is not displayed on findInvoices screen. Please refer > attachment: findInvoices > But when an invoice is created then current date is set as invoice date which > can be viewed on invoiceOverview screen. Please refer attachment: > invoiceOverview > Expected: Invoice date should be displayed on findInvoices screen -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (OFBIZ-10620) Invoice date is not displayed on findInvoice screen
[ https://issues.apache.org/jira/browse/OFBIZ-10620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16740996#comment-16740996 ] Deepak Nigam edited comment on OFBIZ-10620 at 1/12/19 4:57 AM: --- Hello [~suraj.khurana], Yes, the code suggested by you will also work fine. However, I took reference from some other forms inside InvoiceForms.xml like InvoiceHeader, ListInvoiceStatus. Apart from this, there will be a difference in the date pattern: By using the date pattern will be -MM-DD. Please find the attached screenshot 'InvoiceDateFormat1.png'. By using the date pattern will be MM/DD/YY. Please find the attached screenshot 'InvoiceDateFormat2.png'. When I checked the list order and other list screens of invoices, I found another pattern for showing the date, something like . By this code, the date pattern will be -MM-dd HH:mm:ss.SSS. Please find the attached screenshot 'InvoiceDateFormat2.png' for the same. Out of the above 3, the last pattern is making sense to me. Please share your thoughts on the same and commit the respective patch. was (Author: deepak.nigam): Hello [~suraj.khurana], Yes, the code suggested by you will also work fine. However, I took reference from some other forms inside InvoiceForms.xml like InvoiceHeader, ListInvoiceStatus. Apart from this, there will be a difference in the date pattern: By using the date pattern will be -MM-DD. Please find the attached screenshot 'InvoiceDateFormat1.png'. By using the date pattern will be MM/DD/YY. Please find the attached screenshot 'InvoiceDateFormat2.png'. When I checked the list order and other list screens of invoices, I found another pattern for showing the, something like . By this code, the date pattern will be -MM-dd HH:mm:ss.SSS. Please find the attached screenshot 'InvoiceDateFormat2.png' for the same. Out of the above 3, the last pattern is making sense to me. Please share your thoughts on the same and commit the respective patch. > Invoice date is not displayed on findInvoice screen > --- > > Key: OFBIZ-10620 > URL: https://issues.apache.org/jira/browse/OFBIZ-10620 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk > Environment: https://demo-trunk.ofbiz.apache.org >Reporter: Arpit Mor >Assignee: Deepak Nigam >Priority: Minor > Attachments: InvoiceDateFormat1.png, InvoiceDateFormat2.png, > InvoiceDateFormat3.png, OFBiz-10620-Format1.patch, OFBiz-10620-Format2.patch, > OFBiz-10620-Format3.patch, findInvoices.png, invoiceOverview.png > > > Steps to regenerate: > # Open URL: > [https://demo-trunk.ofbiz.apache.org/accounting/control/findInvoices] > # Click on find button > Actual: Invoice date is not displayed on findInvoices screen. Please refer > attachment: findInvoices > But when an invoice is created then current date is set as invoice date which > can be viewed on invoiceOverview screen. Please refer attachment: > invoiceOverview > Expected: Invoice date should be displayed on findInvoices screen -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10620) Invoice date is not displayed on findInvoice screen
[ https://issues.apache.org/jira/browse/OFBIZ-10620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10620: - Attachment: OFBiz-10620-Format3.patch > Invoice date is not displayed on findInvoice screen > --- > > Key: OFBIZ-10620 > URL: https://issues.apache.org/jira/browse/OFBIZ-10620 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk > Environment: https://demo-trunk.ofbiz.apache.org >Reporter: Arpit Mor >Assignee: Deepak Nigam >Priority: Minor > Attachments: InvoiceDateFormat1.png, InvoiceDateFormat2.png, > InvoiceDateFormat3.png, OFBiz-10620-Format1.patch, OFBiz-10620-Format2.patch, > OFBiz-10620-Format3.patch, findInvoices.png, invoiceOverview.png > > > Steps to regenerate: > # Open URL: > [https://demo-trunk.ofbiz.apache.org/accounting/control/findInvoices] > # Click on find button > Actual: Invoice date is not displayed on findInvoices screen. Please refer > attachment: findInvoices > But when an invoice is created then current date is set as invoice date which > can be viewed on invoiceOverview screen. Please refer attachment: > invoiceOverview > Expected: Invoice date should be displayed on findInvoices screen -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10620) Invoice date is not displayed on findInvoice screen
[ https://issues.apache.org/jira/browse/OFBIZ-10620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10620: - Attachment: OFBiz-10620-Format1.patch > Invoice date is not displayed on findInvoice screen > --- > > Key: OFBIZ-10620 > URL: https://issues.apache.org/jira/browse/OFBIZ-10620 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk > Environment: https://demo-trunk.ofbiz.apache.org >Reporter: Arpit Mor >Assignee: Deepak Nigam >Priority: Minor > Attachments: InvoiceDateFormat1.png, InvoiceDateFormat2.png, > InvoiceDateFormat3.png, OFBiz-10620-Format1.patch, OFBiz-10620-Format2.patch, > findInvoices.png, invoiceOverview.png > > > Steps to regenerate: > # Open URL: > [https://demo-trunk.ofbiz.apache.org/accounting/control/findInvoices] > # Click on find button > Actual: Invoice date is not displayed on findInvoices screen. Please refer > attachment: findInvoices > But when an invoice is created then current date is set as invoice date which > can be viewed on invoiceOverview screen. Please refer attachment: > invoiceOverview > Expected: Invoice date should be displayed on findInvoices screen -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10620) Invoice date is not displayed on findInvoice screen
[ https://issues.apache.org/jira/browse/OFBIZ-10620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10620: - Attachment: InvoiceDateFormat3.png > Invoice date is not displayed on findInvoice screen > --- > > Key: OFBIZ-10620 > URL: https://issues.apache.org/jira/browse/OFBIZ-10620 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk > Environment: https://demo-trunk.ofbiz.apache.org >Reporter: Arpit Mor >Assignee: Deepak Nigam >Priority: Minor > Attachments: InvoiceDateFormat1.png, InvoiceDateFormat2.png, > InvoiceDateFormat3.png, OFBiz-10620.patch, findInvoices.png, > invoiceOverview.png > > > Steps to regenerate: > # Open URL: > [https://demo-trunk.ofbiz.apache.org/accounting/control/findInvoices] > # Click on find button > Actual: Invoice date is not displayed on findInvoices screen. Please refer > attachment: findInvoices > But when an invoice is created then current date is set as invoice date which > can be viewed on invoiceOverview screen. Please refer attachment: > invoiceOverview > Expected: Invoice date should be displayed on findInvoices screen -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10620) Invoice date is not displayed on findInvoice screen
[ https://issues.apache.org/jira/browse/OFBIZ-10620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10620: - Attachment: InvoiceDateFormat1.png > Invoice date is not displayed on findInvoice screen > --- > > Key: OFBIZ-10620 > URL: https://issues.apache.org/jira/browse/OFBIZ-10620 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk > Environment: https://demo-trunk.ofbiz.apache.org >Reporter: Arpit Mor >Assignee: Deepak Nigam >Priority: Minor > Attachments: InvoiceDateFormat1.png, InvoiceDateFormat2.png, > InvoiceDateFormat3.png, OFBiz-10620.patch, findInvoices.png, > invoiceOverview.png > > > Steps to regenerate: > # Open URL: > [https://demo-trunk.ofbiz.apache.org/accounting/control/findInvoices] > # Click on find button > Actual: Invoice date is not displayed on findInvoices screen. Please refer > attachment: findInvoices > But when an invoice is created then current date is set as invoice date which > can be viewed on invoiceOverview screen. Please refer attachment: > invoiceOverview > Expected: Invoice date should be displayed on findInvoices screen -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10620) Invoice date is not displayed on findInvoice screen
[ https://issues.apache.org/jira/browse/OFBIZ-10620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10620: - Attachment: InvoiceDateFormat2.png > Invoice date is not displayed on findInvoice screen > --- > > Key: OFBIZ-10620 > URL: https://issues.apache.org/jira/browse/OFBIZ-10620 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk > Environment: https://demo-trunk.ofbiz.apache.org >Reporter: Arpit Mor >Assignee: Deepak Nigam >Priority: Minor > Attachments: InvoiceDateFormat1.png, InvoiceDateFormat2.png, > InvoiceDateFormat3.png, OFBiz-10620.patch, findInvoices.png, > invoiceOverview.png > > > Steps to regenerate: > # Open URL: > [https://demo-trunk.ofbiz.apache.org/accounting/control/findInvoices] > # Click on find button > Actual: Invoice date is not displayed on findInvoices screen. Please refer > attachment: findInvoices > But when an invoice is created then current date is set as invoice date which > can be viewed on invoiceOverview screen. Please refer attachment: > invoiceOverview > Expected: Invoice date should be displayed on findInvoices screen -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10620) Invoice date is not displayed on findInvoice screen
[ https://issues.apache.org/jira/browse/OFBIZ-10620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16740996#comment-16740996 ] Deepak Nigam commented on OFBIZ-10620: -- Hello [~suraj.khurana], Yes, the code suggested by you will also work fine. However, I took reference from some other forms inside InvoiceForms.xml like InvoiceHeader, ListInvoiceStatus. Apart from this, there will be a difference in the date pattern: By using the date pattern will be -MM-DD. Please find the attached screenshot 'InvoiceDateFormat1.png'. By using the date pattern will be MM/DD/YY. Please find the attached screenshot 'InvoiceDateFormat2.png'. When I checked the list order and other list screens of invoices, I found another pattern for showing the, something like . By this code, the date pattern will be -MM-dd HH:mm:ss.SSS. Please find the attached screenshot 'InvoiceDateFormat2.png' for the same. Out of the above 3, the last pattern is making sense to me. Please share your thoughts on the same and commit the respective patch. > Invoice date is not displayed on findInvoice screen > --- > > Key: OFBIZ-10620 > URL: https://issues.apache.org/jira/browse/OFBIZ-10620 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk > Environment: https://demo-trunk.ofbiz.apache.org >Reporter: Arpit Mor >Assignee: Deepak Nigam >Priority: Minor > Attachments: OFBiz-10620.patch, findInvoices.png, invoiceOverview.png > > > Steps to regenerate: > # Open URL: > [https://demo-trunk.ofbiz.apache.org/accounting/control/findInvoices] > # Click on find button > Actual: Invoice date is not displayed on findInvoices screen. Please refer > attachment: findInvoices > But when an invoice is created then current date is set as invoice date which > can be viewed on invoiceOverview screen. Please refer attachment: > invoiceOverview > Expected: Invoice date should be displayed on findInvoices screen -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OFBIZ-10574) 'ORDERMGR_CRQ_ADMIN' permissionId is not defined anywhere
[ https://issues.apache.org/jira/browse/OFBIZ-10574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam closed OFBIZ-10574. > 'ORDERMGR_CRQ_ADMIN' permissionId is not defined anywhere > - > > Key: OFBIZ-10574 > URL: https://issues.apache.org/jira/browse/OFBIZ-10574 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk >Reporter: Deepak Nigam >Assignee: Suraj Khurana >Priority: Major > Fix For: Upcoming Branch > > Attachments: OFBiz-10574.patch, OFBiz-10574.patch > > > We have following references for the permissionId 'ORDERMGR_CRQ_ADMIN' in the > OrderDemoData.xml and OrderSecurityPermissionSeedData.xml. > permissionId="ORDERMGR_CRQ_ADMIN"/> > permissionId="ORDERMGR_CRQ_ADMIN"/> > But the 'SecurityPermission' data for this particular permission is not > defined anywhere. > As the relation type between the entities 'SecurityGroupPermission' and > 'SecurityPermissoin' is 'one-nofk', we are not getting data load error. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10574) 'ORDERMGR_CRQ_ADMIN' permissionId is not defined anywhere
[ https://issues.apache.org/jira/browse/OFBIZ-10574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16740368#comment-16740368 ] Deepak Nigam commented on OFBIZ-10574: -- Thanks [~jacques.le.roux] and [~suraj.khurana]. I think 'ASSETMAINT_VIEW' permission was added mistakenly in the patch. We are good to close the ticket. > 'ORDERMGR_CRQ_ADMIN' permissionId is not defined anywhere > - > > Key: OFBIZ-10574 > URL: https://issues.apache.org/jira/browse/OFBIZ-10574 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk >Reporter: Deepak Nigam >Assignee: Suraj Khurana >Priority: Major > Fix For: Upcoming Branch > > Attachments: OFBiz-10574.patch, OFBiz-10574.patch > > > We have following references for the permissionId 'ORDERMGR_CRQ_ADMIN' in the > OrderDemoData.xml and OrderSecurityPermissionSeedData.xml. > permissionId="ORDERMGR_CRQ_ADMIN"/> > permissionId="ORDERMGR_CRQ_ADMIN"/> > But the 'SecurityPermission' data for this particular permission is not > defined anywhere. > As the relation type between the entities 'SecurityGroupPermission' and > 'SecurityPermissoin' is 'one-nofk', we are not getting data load error. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (OFBIZ-10666) User's name is displayed on ecommerce even after user logs out
[
https://issues.apache.org/jira/browse/OFBIZ-10666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepak Nigam reopened OFBIZ-10666:
--
As per the discussion above, if the user does logout intentionally, then the
autoLogin cookie should not be used otherwise it should be used. But autoLogin
cookie is not getting used in any of the cases. Consider the below code snippet
from LoginWorker.getAutoUserLoginId() method:
if (cookie.getName().equals(getAutoLoginCookieName(request)) &&
cookie.getMaxAge() > 0) {
autoUserLoginId = cookie.getValue();
break;
}
In the above condition the cookie.getMaxAge(0) function is not working as
expexted because getMaxAge() method is not a reliable one and returns -1 in
most of the cases.
Please refer to the following links for more information:
[In Java servlet, cookie.getMaxAge() always returns
-1|https://stackoverflow.com/questions/14391749/in-java-servlet-cookie-getmaxage-always-returns-1]
[What do browsers do with expired
cookies?|https://superuser.com/questions/356265/what-do-browsers-do-with-expired-cookies]
If a cookie has expired, the browser does not send that particular cookie to
the server with the page request; instead, the expired cookie is deleted.
> User's name is displayed on ecommerce even after user logs out
> --
>
> Key: OFBIZ-10666
> URL: https://issues.apache.org/jira/browse/OFBIZ-10666
> Project: OFBiz
> Issue Type: Bug
> Components: ecommerce
>Affects Versions: Trunk
>Reporter: Arpit Mor
>Assignee: Jacques Le Roux
>Priority: Major
> Fix For: 17.12.01, 16.11.06
>
> Attachments: 1-OpenURL.png, 2-LoggedIn.png, 3-LoggedOut.png,
> 4-NotYou.png, OFBIZ-10666.patch
>
>
> Steps to regenerate:
> # Open URL: [https://demo-trunk.ofbiz.apache.org/ecommerce/control/main].
> Welcome is displayed and user's name is not displayed when URL is opened.
> (Please refer attachment: 1-OpenURL)
> # Login at ecommerce by clicking on login and entering Username: "admin" and
> Password: "ofbiz". Username will be displayed after user logs in. (Please
> refer attachment: 2-LoggedIn)
> # Logout of ecommerce by clicking on logout. User will be logged out and
> login link will be displayed in place of logout link, but the name of user is
> still displayed. (Please refer attachment: 3-LoggedOut)
> Actual: Username is still displayed after user logs out
>
> Expected: Username should not be displayed after the user logs out
>
> Note: Similar issue also exists when the user clicks on (Not You? Click Here)
> link. (Please refer attachment: 4-NotYou)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (OFBIZ-10586) Change the relation type with 'SecurityPermission' in SecurityGroupPermission entity to 'one' from 'one-nofk'
[ https://issues.apache.org/jira/browse/OFBIZ-10586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam closed OFBIZ-10586. Resolution: Not A Problem > Change the relation type with 'SecurityPermission' in SecurityGroupPermission > entity to 'one' from 'one-nofk' > - > > Key: OFBIZ-10586 > URL: https://issues.apache.org/jira/browse/OFBIZ-10586 > Project: OFBiz > Issue Type: Improvement > Components: securityext >Affects Versions: Trunk >Reporter: Deepak Nigam >Assignee: Suraj Khurana >Priority: Major > Attachments: OFBiz-10586.patch > > > In the definition of 'SecurityGroupPermission' entity, the relation type with > 'SecurityPermission' entity is 'one-nofk'. Hence the system is allowing to > use the permissions not defined anywhere. (ex. > ORDERMGR_CRQ_ADMIN/ORDERMGR_CRQ_UPDATE, ASSETMAINT_VIEW). > > Change the relation type to 'one' to maintain the referential integrity. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10586) Change the relation type with 'SecurityPermission' in SecurityGroupPermission entity to 'one' from 'one-nofk'
[ https://issues.apache.org/jira/browse/OFBIZ-10586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16696560#comment-16696560 ] Deepak Nigam commented on OFBIZ-10586: -- As discussed, there is nothing to do further in this ticket so closing it. > Change the relation type with 'SecurityPermission' in SecurityGroupPermission > entity to 'one' from 'one-nofk' > - > > Key: OFBIZ-10586 > URL: https://issues.apache.org/jira/browse/OFBIZ-10586 > Project: OFBiz > Issue Type: Improvement > Components: securityext >Affects Versions: Trunk >Reporter: Deepak Nigam >Assignee: Suraj Khurana >Priority: Major > Attachments: OFBiz-10586.patch > > > In the definition of 'SecurityGroupPermission' entity, the relation type with > 'SecurityPermission' entity is 'one-nofk'. Hence the system is allowing to > use the permissions not defined anywhere. (ex. > ORDERMGR_CRQ_ADMIN/ORDERMGR_CRQ_UPDATE, ASSETMAINT_VIEW). > > Change the relation type to 'one' to maintain the referential integrity. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10643) Google reCAPTCHA in E-Commerce Application
[ https://issues.apache.org/jira/browse/OFBIZ-10643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16682204#comment-16682204 ] Deepak Nigam commented on OFBIZ-10643: -- Yes [~mbrohl] , we will make this feature optional with configuration as suggested by [~rishisolankii] . On a side note, pasting the content from [https://developers.google.com/recaptcha/docs/versions] for more information about user interaction in Google Recaptcha. reCAPTCHA v3 reCAPTCHA v3 allows you to verify if an interaction is legitimate without any user interaction. It is a purely JavaScript API returns a score giving you the ability to take action in the context of your site: for instance requiring additional factors of authentication, sending a post to moderation, or throttling bots that may be scraping content. h2. Invisible reCAPTCHA The second option 'Invisible reCAPTCHA' does not require the user to click on a checkbox, instead, it is invoked directly when the user clicks on an existing button on your site or can be invoked via a JavaScript API call. The integration requires a JavaScript callback when reCAPTCHA verification is complete. By default, only the most suspicious traffic will be prompted to solve a captcha. To alter this behaviour edit your site security preference under advanced settings. > Google reCAPTCHA in E-Commerce Application > -- > > Key: OFBIZ-10643 > URL: https://issues.apache.org/jira/browse/OFBIZ-10643 > Project: OFBiz > Issue Type: New Feature > Components: ecommerce >Reporter: Deepak Nigam >Assignee: Deepak Nigam >Priority: Major > > Google reCAPTCHA is a security feature that protects websites forms from spam > entries while letting real people pass through with ease. It can be used for > login, registration, password recovery, comments, popular contact forms, etc. > Users are required to confirm that they are not a robot before the form can > be submitted. It’s easy for people and hard for bots. > > For more information about Google reCAPTCHA, please visit > [here|https://developers.google.com/recaptcha/]. > > I think this feature will be useful for OFBiz e-commerce also. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10643) Google reCAPTCHA in E-Commerce Application
Deepak Nigam created OFBIZ-10643: Summary: Google reCAPTCHA in E-Commerce Application Key: OFBIZ-10643 URL: https://issues.apache.org/jira/browse/OFBIZ-10643 Project: OFBiz Issue Type: New Feature Components: ecommerce Reporter: Deepak Nigam Assignee: Deepak Nigam Google reCAPTCHA is a security feature that protects websites forms from spam entries while letting real people pass through with ease. It can be used for login, registration, password recovery, comments, popular contact forms, etc. Users are required to confirm that they are not a robot before the form can be submitted. It’s easy for people and hard for bots. For more information about Google reCAPTCHA, please visit [here|https://developers.google.com/recaptcha/]. I think this feature will be useful for OFBiz e-commerce also. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10639) Cookie Consent In E-Commerce
[ https://issues.apache.org/jira/browse/OFBIZ-10639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10639: - Summary: Cookie Consent In E-Commerce (was: Cookie Consent In E-Coomerce) > Cookie Consent In E-Commerce > > > Key: OFBIZ-10639 > URL: https://issues.apache.org/jira/browse/OFBIZ-10639 > Project: OFBiz > Issue Type: New Feature > Components: ecommerce >Affects Versions: Trunk >Reporter: Deepak Nigam >Assignee: Deepak Nigam >Priority: Minor > > The Cookie Law is a piece of privacy legislation that requires websites to > get consent from visitors to store or retrieve any information on their > computer, smartphone or tablet. It was designed to protect online privacy, by > making consumers aware of how information about them is collected and used > online, and give them a choice to allow it or not. > > The EU Cookie Legislation began as a directive from the European Union. Some > variation on the policy has since been adopted by all countries within the EU. > > The EU Cookie Legislation requires 4 actions from website owners who use > cookies: > 1. When someone visits your website, you need to let them know that your site > uses cookies. > 2. You need to provide detailed information regarding how that cookie data > will be utilized. > 3. You need to provide visitors with some means of accepting or refusing the > use of cookies in your site. > 4. If they refuse, you need to ensure that cookies will not be placed on > their machine. > > For more information about EU cookie policy, please visit > [here|http://ec.europa.eu/ipg/basics/legal/cookies/index_en.htm]. > > As this crucial feature is missing in OFBiz E-Commerce application, we should > work towards its implementation. There are numerous open-source jQuery > plugins available which we can use. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10639) Cookie Consent In E-Coomerce
Deepak Nigam created OFBIZ-10639: Summary: Cookie Consent In E-Coomerce Key: OFBIZ-10639 URL: https://issues.apache.org/jira/browse/OFBIZ-10639 Project: OFBiz Issue Type: New Feature Components: ecommerce Affects Versions: Trunk Reporter: Deepak Nigam Assignee: Deepak Nigam The Cookie Law is a piece of privacy legislation that requires websites to get consent from visitors to store or retrieve any information on their computer, smartphone or tablet. It was designed to protect online privacy, by making consumers aware of how information about them is collected and used online, and give them a choice to allow it or not. The EU Cookie Legislation began as a directive from the European Union. Some variation on the policy has since been adopted by all countries within the EU. The EU Cookie Legislation requires 4 actions from website owners who use cookies: 1. When someone visits your website, you need to let them know that your site uses cookies. 2. You need to provide detailed information regarding how that cookie data will be utilized. 3. You need to provide visitors with some means of accepting or refusing the use of cookies in your site. 4. If they refuse, you need to ensure that cookies will not be placed on their machine. For more information about EU cookie policy, please visit [here|http://ec.europa.eu/ipg/basics/legal/cookies/index_en.htm]. As this crucial feature is missing in OFBiz E-Commerce application, we should work towards its implementation. There are numerous open-source jQuery plugins available which we can use. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10620) Invoice date is not displayed on findInvoice screen
[ https://issues.apache.org/jira/browse/OFBIZ-10620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10620: - Attachment: OFBiz-10620.patch > Invoice date is not displayed on findInvoice screen > --- > > Key: OFBIZ-10620 > URL: https://issues.apache.org/jira/browse/OFBIZ-10620 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk > Environment: https://demo-trunk.ofbiz.apache.org >Reporter: Arpit Mor >Assignee: Deepak Nigam >Priority: Minor > Attachments: OFBiz-10620.patch, findInvoices.png, invoiceOverview.png > > > Steps to regenerate: > # Open URL: > [https://demo-trunk.ofbiz.apache.org/accounting/control/findInvoices] > # Click on find button > Actual: Invoice date is not displayed on findInvoices screen. Please refer > attachment: findInvoices > But when an invoice is created then current date is set as invoice date which > can be viewed on invoiceOverview screen. Please refer attachment: > invoiceOverview > Expected: Invoice date should be displayed on findInvoices screen -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10620) Invoice date is not displayed on findInvoice screen
[ https://issues.apache.org/jira/browse/OFBIZ-10620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam reassigned OFBIZ-10620: Assignee: Deepak Nigam > Invoice date is not displayed on findInvoice screen > --- > > Key: OFBIZ-10620 > URL: https://issues.apache.org/jira/browse/OFBIZ-10620 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk > Environment: https://demo-trunk.ofbiz.apache.org >Reporter: Arpit Mor >Assignee: Deepak Nigam >Priority: Minor > Attachments: findInvoices.png, invoiceOverview.png > > > Steps to regenerate: > # Open URL: > [https://demo-trunk.ofbiz.apache.org/accounting/control/findInvoices] > # Click on find button > Actual: Invoice date is not displayed on findInvoices screen. Please refer > attachment: findInvoices > But when an invoice is created then current date is set as invoice date which > can be viewed on invoiceOverview screen. Please refer attachment: > invoiceOverview > Expected: Invoice date should be displayed on findInvoices screen -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10427) Add a mean to handle CSRF
[ https://issues.apache.org/jira/browse/OFBIZ-10427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665982#comment-16665982 ] Deepak Nigam commented on OFBIZ-10427: -- For using nonce with the CSRF prevention filter provided by tomcat, we need to make sure that we use transform in every URL. > Add a mean to handle CSRF > - > > Key: OFBIZ-10427 > URL: https://issues.apache.org/jira/browse/OFBIZ-10427 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > Attachments: webtools_web.xml.patch > > > I already worked on that in OFBiz but without success so far: > https://markmail.org/message/r245yie623cdo3wz) > The tracks I explored are: > * https://www.owasp.org/index.php/Category:OWASP_CSRFGuard_Project (really > not simple in OFBiz) > * > https://tomcat.apache.org/tomcat-8.5-doc/config/filter.html#CSRF_Prevention_Filter/Introduction > (I think preferred) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10574) 'ORDERMGR_CRQ_ADMIN' permissionId is not defined anywhere
[ https://issues.apache.org/jira/browse/OFBIZ-10574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665962#comment-16665962 ] Deepak Nigam commented on OFBIZ-10574: -- Hi all, please have a look into the patch attached. We may proceed for committing. > 'ORDERMGR_CRQ_ADMIN' permissionId is not defined anywhere > - > > Key: OFBIZ-10574 > URL: https://issues.apache.org/jira/browse/OFBIZ-10574 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk >Reporter: Deepak Nigam >Assignee: Deepak Nigam >Priority: Major > Attachments: OFBiz-10574.patch, OFBiz-10574.patch > > > We have following references for the permissionId 'ORDERMGR_CRQ_ADMIN' in the > OrderDemoData.xml and OrderSecurityPermissionSeedData.xml. > permissionId="ORDERMGR_CRQ_ADMIN"/> > permissionId="ORDERMGR_CRQ_ADMIN"/> > But the 'SecurityPermission' data for this particular permission is not > defined anywhere. > As the relation type between the entities 'SecurityGroupPermission' and > 'SecurityPermissoin' is 'one-nofk', we are not getting data load error. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665949#comment-16665949 ] Deepak Nigam commented on OFBIZ-10518: -- Team, please let me know if you got time to review this work further? > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Deepak Nigam >Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, CreateAllocationPlanEditMode-Step2.png, > EditAllocationPlan.png, FindAllocationPlan.png, OFBiz-10518.patch, > OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, > ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10597) Missing Security and Cache Headers in CMS Events
[ https://issues.apache.org/jira/browse/OFBIZ-10597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665946#comment-16665946 ] Deepak Nigam commented on OFBIZ-10597: -- Thanks, [~jacques.le.roux] , patch looks fine to me and I think you may proceed for commit. > Missing Security and Cache Headers in CMS Events > > > Key: OFBIZ-10597 > URL: https://issues.apache.org/jira/browse/OFBIZ-10597 > Project: OFBiz > Issue Type: Improvement > Components: cmssite, securityext >Affects Versions: Trunk >Reporter: Deepak Nigam >Assignee: Deepak Nigam >Priority: Major > Attachments: OFBIZ-10597.diff, OFBiz-10597.patch > > > While rendering the view through the controller request we set the important > security headers like x-frame-options, strict-transport-security, > x-content-type-options, X-XSS-Protection and Referrer-Policy etc. in the > response object. (Please see the 'rendervView' method of RequestHandler > class.) > > In the similar line, we set the cache related headers like Expires, > Last-Modified, Cache-Control, Pragma. > > But these security headers are missing in the pages rendered through CMS. > (Please visit the CmsEvents class). > > These headers are very crucial for the security of the application as they > help to prevent various security threats like cross-site scripting, > cross-site request forgery, clickjacking etc. > > IMO, we should add these security headers in the response object prepared > through the CMS also. WDYT? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10590) Add http to https redirect rule for ofbiz.apache.org
[ https://issues.apache.org/jira/browse/OFBIZ-10590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665938#comment-16665938 ] Deepak Nigam commented on OFBIZ-10590: -- Uploaded the patch, in which changed 'http' to 'https' in noNamespaceSchemaLocation. > Add http to https redirect rule for ofbiz.apache.org > > > Key: OFBIZ-10590 > URL: https://issues.apache.org/jira/browse/OFBIZ-10590 > Project: OFBiz > Issue Type: Improvement > Components: site >Reporter: Deepak Dixit >Assignee: Deepak Dixit >Priority: Major > Attachments: OFBiz-10590.patch > > > Add http to https redirect rule for ofbiz site. > Here is the dev list thread for the same > [https://s.apache.org/hRa1] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10597) Missing Security and Cache Headers in CMS Events
[ https://issues.apache.org/jira/browse/OFBIZ-10597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16642917#comment-16642917 ] Deepak Nigam commented on OFBIZ-10597: -- [~jacques.le.roux] , I will have a look at your suggestion. > Missing Security and Cache Headers in CMS Events > > > Key: OFBIZ-10597 > URL: https://issues.apache.org/jira/browse/OFBIZ-10597 > Project: OFBiz > Issue Type: Improvement > Components: cmssite, securityext >Affects Versions: Trunk >Reporter: Deepak Nigam >Assignee: Deepak Nigam >Priority: Major > Attachments: OFBiz-10597.patch > > > While rendering the view through the controller request we set the important > security headers like x-frame-options, strict-transport-security, > x-content-type-options, X-XSS-Protection and Referrer-Policy etc. in the > response object. (Please see the 'rendervView' method of RequestHandler > class.) > > In the similar line, we set the cache related headers like Expires, > Last-Modified, Cache-Control, Pragma. > > But these security headers are missing in the pages rendered through CMS. > (Please visit the CmsEvents class). > > These headers are very crucial for the security of the application as they > help to prevent various security threats like cross-site scripting, > cross-site request forgery, clickjacking etc. > > IMO, we should add these security headers in the response object prepared > through the CMS also. WDYT? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10597) Missing Security and Cache Headers in CMS Events
[ https://issues.apache.org/jira/browse/OFBIZ-10597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16641745#comment-16641745 ] Deepak Nigam commented on OFBIZ-10597: -- Added a separate method 'setResponseBrowserDefaultSecurityHeaders' in UtiHttp similar to 'setResponseBrowserProxyNoCache' and called it from RequestHandler and CmsEvents class. Exploring other options to properly place the security headers so that if the controller uses any other type rather than 'view', these headers will be available. > Missing Security and Cache Headers in CMS Events > > > Key: OFBIZ-10597 > URL: https://issues.apache.org/jira/browse/OFBIZ-10597 > Project: OFBiz > Issue Type: Improvement > Components: cmssite, securityext >Affects Versions: Trunk >Reporter: Deepak Nigam >Assignee: Deepak Nigam >Priority: Major > Attachments: OFBiz-10597.patch > > > While rendering the view through the controller request we set the important > security headers like x-frame-options, strict-transport-security, > x-content-type-options, X-XSS-Protection and Referrer-Policy etc. in the > response object. (Please see the 'rendervView' method of RequestHandler > class.) > > In the similar line, we set the cache related headers like Expires, > Last-Modified, Cache-Control, Pragma. > > But these security headers are missing in the pages rendered through CMS. > (Please visit the CmsEvents class). > > These headers are very crucial for the security of the application as they > help to prevent various security threats like cross-site scripting, > cross-site request forgery, clickjacking etc. > > IMO, we should add these security headers in the response object prepared > through the CMS also. WDYT? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10597) Missing Security and Cache Headers in CMS Events
[ https://issues.apache.org/jira/browse/OFBIZ-10597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10597: - Attachment: OFBiz-10597.patch > Missing Security and Cache Headers in CMS Events > > > Key: OFBIZ-10597 > URL: https://issues.apache.org/jira/browse/OFBIZ-10597 > Project: OFBiz > Issue Type: Improvement > Components: cmssite, securityext >Affects Versions: Trunk >Reporter: Deepak Nigam >Assignee: Deepak Nigam >Priority: Major > Attachments: OFBiz-10597.patch > > > While rendering the view through the controller request we set the important > security headers like x-frame-options, strict-transport-security, > x-content-type-options, X-XSS-Protection and Referrer-Policy etc. in the > response object. (Please see the 'rendervView' method of RequestHandler > class.) > > In the similar line, we set the cache related headers like Expires, > Last-Modified, Cache-Control, Pragma. > > But these security headers are missing in the pages rendered through CMS. > (Please visit the CmsEvents class). > > These headers are very crucial for the security of the application as they > help to prevent various security threats like cross-site scripting, > cross-site request forgery, clickjacking etc. > > IMO, we should add these security headers in the response object prepared > through the CMS also. WDYT? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10597) Missing Security and Cache Headers in CMS Events
Deepak Nigam created OFBIZ-10597: Summary: Missing Security and Cache Headers in CMS Events Key: OFBIZ-10597 URL: https://issues.apache.org/jira/browse/OFBIZ-10597 Project: OFBiz Issue Type: Improvement Components: securityext Affects Versions: Trunk Reporter: Deepak Nigam Assignee: Deepak Nigam While rendering the view through the controller request we set the important security headers like x-frame-options, strict-transport-security, x-content-type-options, X-XSS-Protection and Referrer-Policy etc. in the response object. (Please see the 'rendervView' method of RequestHandler class.) In the similar line, we set the cache related headers like Expires, Last-Modified, Cache-Control, Pragma. But these security headers are missing in the pages rendered through CMS. (Please visit the CmsEvents class). These headers are very crucial for the security of the application as they help to prevent various security threats like cross-site scripting, cross-site request forgery, clickjacking etc. IMO, we should add these security headers in the response object prepared through the CMS also. WDYT? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10518: - Attachment: OFBiz-10518.patch > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Deepak Nigam >Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, CreateAllocationPlanEditMode-Step2.png, > EditAllocationPlan.png, FindAllocationPlan.png, OFBiz-10518.patch, > OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, > ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16631602#comment-16631602 ] Deepak Nigam commented on OFBIZ-10518: -- Following suggestions have been taken care in the latest patch: 1) "Suppose a case where out of 20 ordered quantity, 10 are approved for allocation, after reservation, can we again edit allocation qty to 5? Will, it also re-reserve and change reservation as well to 5? If it is not working like this, IMO, we need to handle it." 2) "Inventory reservation should run after allocation plan approval." > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Deepak Nigam >Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, CreateAllocationPlanEditMode-Step2.png, > EditAllocationPlan.png, FindAllocationPlan.png, OFBiz-10518.patch, > OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, > ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10518: - Attachment: OFBiz-10518.patch > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Deepak Nigam >Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, CreateAllocationPlanEditMode-Step2.png, > EditAllocationPlan.png, FindAllocationPlan.png, OFBiz-10518.patch, > OFBiz-10518.patch, OFBiz-10518.patch, OFBiz-10518.patch, > ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10518: - Attachment: OFBiz-10518.patch > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Deepak Nigam >Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, CreateAllocationPlanEditMode-Step2.png, > EditAllocationPlan.png, FindAllocationPlan.png, OFBiz-10518.patch, > OFBiz-10518.patch, OFBiz-10518.patch, ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16628403#comment-16628403 ] Deepak Nigam commented on OFBIZ-10518: -- Hi Arun Patidar, I have taken care of both the improvements suggested by you and uploaded the latest patch. Thanks! > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Deepak Nigam >Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, CreateAllocationPlanEditMode-Step2.png, > EditAllocationPlan.png, FindAllocationPlan.png, OFBiz-10518.patch, > OFBiz-10518.patch, ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16627142#comment-16627142 ] Deepak Nigam edited comment on OFBIZ-10518 at 9/26/18 8:17 AM: --- Thanks for the inputs [~arunpati], [~suraj.khurana]. [~arunpati], It is not configurable as of now. We can make it configurable to use the allocation feature or not. Yes, for auto reserved, inventory will be allocated as same as item qty along with auto-approval of the corresponding allocation plan item. [~suraj.khurana] , The answer to all of your queries is no as of now. But yes, we can definitely include these in the design. was (Author: deepak.nigam): Thanks for the inputs [~arunpati], [~suraj.khurana]. [~arunpati], It is not configurable as of now. We can make it configurable to use the allocation feature or not. Yes, for auto reserved, inventory will be allocated as same as item qty along with auto approve of Allocation Plan. [~suraj.khurana], The answer to all of your queries is no as of now. But yes, we can definitely include these in the design. > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Deepak Nigam >Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, CreateAllocationPlanEditMode-Step2.png, > EditAllocationPlan.png, FindAllocationPlan.png, OFBiz-10518.patch, > OFBiz-10518.patch, ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10518: - Attachment: OFBiz-10518.patch > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Deepak Nigam >Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, CreateAllocationPlanEditMode-Step2.png, > EditAllocationPlan.png, FindAllocationPlan.png, OFBiz-10518.patch, > OFBiz-10518.patch, ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10518) Inventory (Supply) Allocation Planning
[ https://issues.apache.org/jira/browse/OFBIZ-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16627142#comment-16627142 ] Deepak Nigam commented on OFBIZ-10518: -- Thanks for the inputs [~arunpati], [~suraj.khurana]. [~arunpati], It is not configurable as of now. We can make it configurable to use the allocation feature or not. Yes, for auto reserved, inventory will be allocated as same as item qty along with auto approve of Allocation Plan. [~suraj.khurana], The answer to all of your queries is no as of now. But yes, we can definitely include these in the design. > Inventory (Supply) Allocation Planning > -- > > Key: OFBIZ-10518 > URL: https://issues.apache.org/jira/browse/OFBIZ-10518 > Project: OFBiz > Issue Type: New Feature > Components: order, product >Reporter: Deepak Nigam >Assignee: Deepak Nigam >Priority: Major > Fix For: Trunk > > Attachments: CreateAllocationPlan-Step1.png, > CreateAllocationPlan-Step2.png, CreateAllocationPlanEditMode-Step2.png, > EditAllocationPlan.png, FindAllocationPlan.png, OFBiz-10518.patch, > ViewAllocationPlan.png > > > In the current implementation of inventory reservation flow, inventory gets > reserved for the order based on the reservation algorithm (FIFO, LIFO etc). > Many times, the fulfilment cycle of the order is too long or due to some > unexpected circumstances, the order holds the inventory for a long time. In > such scenarios, inventory availability becomes one of the major bottlenecks > in fulfilling the other sales order and businesses often remains short > supplied against the demand. > > We can provide a feature (Create, Find and Edit supply allocation screen) to > allocate the available and any future supply judiciously amongst existing > customers orders by considering different factors like estimated delivery > dates, order priority, customer preference etc. > > Following are the details design notes for the same: > > An order in the approved status will be considered as ‘Eligible for > Allocation’. The proposed supply allocation planning will have the following > set of features: > > *Create Allocation Plan:* > The authorized user will be able to initiate the process by setting the > desired product. > > *View/Edit Allocation Plan:* > 1) The system would search and list all the order lines which are eligible > for allocation for that particular product. > 2) The user can filter and sort the orders by various parameters like Sale > Channel, Customer, Order Id, Estimated Ship Date etc. > 3) The user can then prioritize the order by moving up or down the given > order in the priority ranking. Higher is the order in display result list, > higher will be the priority it would get during reservations. > 4) The user can set the ‘Allocated Quantity’ against ordered quantity at > order item line level. > 5) Once the Allocation Plan is submitted, the system would auto-assign the > priority and set the allocated quantity for each of the submitted orders to > be honoured during order reservations at any point in time. > 7) Incoming shipments would be reserved by honouring the same allocation plan > during order promising cycle. > 8) After allocating supply as per the allocation plan, any excess stock > should be reserved based on the standard FIFO method. > 9) If any of the items of an order is not planned via the Allocation Plan, > then also it should be reserved based on default FIFO criteria. > 10) The allocation for all the sales orders should be allowed for revision > unless the Shipment Plan is created against them. > > *Find Allocation Plan:* > The authorized user can search allocation plan(s) with filters like Plan Id, > Order Id, Product Id, Plan Method, Status etc. > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10579) Date filtered queries with caching should be restricted to cache
[ https://issues.apache.org/jira/browse/OFBIZ-10579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16626963#comment-16626963 ] Deepak Nigam commented on OFBIZ-10579: -- +1. Patch looks good to me also. > Date filtered queries with caching should be restricted to cache > > > Key: OFBIZ-10579 > URL: https://issues.apache.org/jira/browse/OFBIZ-10579 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Upcoming Branch >Reporter: Suraj Khurana >Assignee: Suraj Khurana >Priority: Major > Attachments: OFBIZ-10579.patch > > > As per discussion on Dev ML > https://markmail.org/thread/3qnkihmsyhly3lsg -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (OFBIZ-10586) Change the relation type with 'SecurityPermission' in SecurityGroupPermission entity to 'one' from 'one-nofk'
[ https://issues.apache.org/jira/browse/OFBIZ-10586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16625770#comment-16625770 ] Deepak Nigam edited comment on OFBIZ-10586 at 9/24/18 12:52 PM: Uploaded the patch for the fix. Related data correction is available in OFBiz-10574 . was (Author: deepak.nigam): Uploaded the patch for the fix. Related data correction is available in OFBiz-10574.[OFBiz-10574|https://issues.apache.org/jira/browse/OFBIZ-10574] > Change the relation type with 'SecurityPermission' in SecurityGroupPermission > entity to 'one' from 'one-nofk' > - > > Key: OFBIZ-10586 > URL: https://issues.apache.org/jira/browse/OFBIZ-10586 > Project: OFBiz > Issue Type: Improvement > Components: securityext >Affects Versions: Trunk >Reporter: Deepak Nigam >Assignee: Deepak Nigam >Priority: Major > Attachments: OFBiz-10586.patch > > > In the definition of 'SecurityGroupPermission' entity, the relation type with > 'SecurityPermission' entity is 'one-nofk'. Hence the system is allowing to > use the permissions not defined anywhere. (ex. > ORDERMGR_CRQ_ADMIN/ORDERMGR_CRQ_UPDATE, ASSETMAINT_VIEW). > > Change the relation type to 'one' to maintain the referential integrity. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10586) Change the relation type with 'SecurityPermission' in SecurityGroupPermission entity to 'one' from 'one-nofk'
[ https://issues.apache.org/jira/browse/OFBIZ-10586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16625775#comment-16625775 ] Deepak Nigam commented on OFBIZ-10586: -- Here is the [link|https://markmail.org/message/wshrwsr6pdy474yw] of related discussion in the dev mailing list. > Change the relation type with 'SecurityPermission' in SecurityGroupPermission > entity to 'one' from 'one-nofk' > - > > Key: OFBIZ-10586 > URL: https://issues.apache.org/jira/browse/OFBIZ-10586 > Project: OFBiz > Issue Type: Improvement > Components: securityext >Affects Versions: Trunk >Reporter: Deepak Nigam >Assignee: Deepak Nigam >Priority: Major > Attachments: OFBiz-10586.patch > > > In the definition of 'SecurityGroupPermission' entity, the relation type with > 'SecurityPermission' entity is 'one-nofk'. Hence the system is allowing to > use the permissions not defined anywhere. (ex. > ORDERMGR_CRQ_ADMIN/ORDERMGR_CRQ_UPDATE, ASSETMAINT_VIEW). > > Change the relation type to 'one' to maintain the referential integrity. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10586) Change the relation type with 'SecurityPermission' in SecurityGroupPermission entity to 'one' from 'one-nofk'
[ https://issues.apache.org/jira/browse/OFBIZ-10586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16625770#comment-16625770 ] Deepak Nigam commented on OFBIZ-10586: -- Uploaded the patch for the fix. Related data correction is available in OFBiz-10574.[OFBiz-10574|https://issues.apache.org/jira/browse/OFBIZ-10574] > Change the relation type with 'SecurityPermission' in SecurityGroupPermission > entity to 'one' from 'one-nofk' > - > > Key: OFBIZ-10586 > URL: https://issues.apache.org/jira/browse/OFBIZ-10586 > Project: OFBiz > Issue Type: Improvement > Components: securityext >Affects Versions: Trunk >Reporter: Deepak Nigam >Assignee: Deepak Nigam >Priority: Major > Attachments: OFBiz-10586.patch > > > In the definition of 'SecurityGroupPermission' entity, the relation type with > 'SecurityPermission' entity is 'one-nofk'. Hence the system is allowing to > use the permissions not defined anywhere. (ex. > ORDERMGR_CRQ_ADMIN/ORDERMGR_CRQ_UPDATE, ASSETMAINT_VIEW). > > Change the relation type to 'one' to maintain the referential integrity. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10586) Change the relation type with 'SecurityPermission' in SecurityGroupPermission entity to 'one' from 'one-nofk'
[ https://issues.apache.org/jira/browse/OFBIZ-10586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10586: - Attachment: OFBiz-10586.patch > Change the relation type with 'SecurityPermission' in SecurityGroupPermission > entity to 'one' from 'one-nofk' > - > > Key: OFBIZ-10586 > URL: https://issues.apache.org/jira/browse/OFBIZ-10586 > Project: OFBiz > Issue Type: Improvement > Components: securityext >Affects Versions: Trunk >Reporter: Deepak Nigam >Assignee: Deepak Nigam >Priority: Major > Attachments: OFBiz-10586.patch > > > In the definition of 'SecurityGroupPermission' entity, the relation type with > 'SecurityPermission' entity is 'one-nofk'. Hence the system is allowing to > use the permissions not defined anywhere. (ex. > ORDERMGR_CRQ_ADMIN/ORDERMGR_CRQ_UPDATE, ASSETMAINT_VIEW). > > Change the relation type to 'one' to maintain the referential integrity. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10586) Change the relation type with 'SecurityPermission' in SecurityGroupPermission entity to 'one' from 'one-nofk'
Deepak Nigam created OFBIZ-10586: Summary: Change the relation type with 'SecurityPermission' in SecurityGroupPermission entity to 'one' from 'one-nofk' Key: OFBIZ-10586 URL: https://issues.apache.org/jira/browse/OFBIZ-10586 Project: OFBiz Issue Type: Improvement Components: securityext Affects Versions: Trunk Reporter: Deepak Nigam Assignee: Deepak Nigam In the definition of 'SecurityGroupPermission' entity, the relation type with 'SecurityPermission' entity is 'one-nofk'. Hence the system is allowing to use the permissions not defined anywhere. (ex. ORDERMGR_CRQ_ADMIN/ORDERMGR_CRQ_UPDATE, ASSETMAINT_VIEW). Change the relation type to 'one' to maintain the referential integrity. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10574) 'ORDERMGR_CRQ_ADMIN' permissionId is not defined anywhere
[ https://issues.apache.org/jira/browse/OFBIZ-10574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16625764#comment-16625764 ] Deepak Nigam commented on OFBIZ-10574: -- Added the updated patch including permission id 'ASSETMAINT_VIEW'. > 'ORDERMGR_CRQ_ADMIN' permissionId is not defined anywhere > - > > Key: OFBIZ-10574 > URL: https://issues.apache.org/jira/browse/OFBIZ-10574 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk >Reporter: Deepak Nigam >Assignee: Deepak Nigam >Priority: Major > Attachments: OFBiz-10574.patch, OFBiz-10574.patch > > > We have following references for the permissionId 'ORDERMGR_CRQ_ADMIN' in the > OrderDemoData.xml and OrderSecurityPermissionSeedData.xml. > permissionId="ORDERMGR_CRQ_ADMIN"/> > permissionId="ORDERMGR_CRQ_ADMIN"/> > But the 'SecurityPermission' data for this particular permission is not > defined anywhere. > As the relation type between the entities 'SecurityGroupPermission' and > 'SecurityPermissoin' is 'one-nofk', we are not getting data load error. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10574) 'ORDERMGR_CRQ_ADMIN' permissionId is not defined anywhere
[ https://issues.apache.org/jira/browse/OFBIZ-10574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepak Nigam updated OFBIZ-10574: - Attachment: OFBiz-10574.patch > 'ORDERMGR_CRQ_ADMIN' permissionId is not defined anywhere > - > > Key: OFBIZ-10574 > URL: https://issues.apache.org/jira/browse/OFBIZ-10574 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk >Reporter: Deepak Nigam >Assignee: Deepak Nigam >Priority: Major > Attachments: OFBiz-10574.patch, OFBiz-10574.patch > > > We have following references for the permissionId 'ORDERMGR_CRQ_ADMIN' in the > OrderDemoData.xml and OrderSecurityPermissionSeedData.xml. > permissionId="ORDERMGR_CRQ_ADMIN"/> > permissionId="ORDERMGR_CRQ_ADMIN"/> > But the 'SecurityPermission' data for this particular permission is not > defined anywhere. > As the relation type between the entities 'SecurityGroupPermission' and > 'SecurityPermissoin' is 'one-nofk', we are not getting data load error. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
