[jira] [Commented] (OFBIZ-9557) Add the ability to schedule a job to run as a system/service user
[ https://issues.apache.org/jira/browse/OFBIZ-9557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16628736#comment-16628736 ] Jacques Le Roux commented on OFBIZ-9557: Hi Rohit, Yes good idea, a permissions seems to fit more indeed. Of course the admin (super and system also) should have it. > Add the ability to schedule a job to run as a system/service user > - > > Key: OFBIZ-9557 > URL: https://issues.apache.org/jira/browse/OFBIZ-9557 > Project: OFBiz > Issue Type: Improvement > Components: tools >Reporter: Matthew Mulligan >Assignee: Rohit Koushal >Priority: Major > > When scheduling a job it automatically schedules it to run as the user that > created the schedule. The issue comes up when that users password changes. > We use LDAP authentication and our passwords change every 90 days. Right now > every 90 days when my password changes I have to delete all previously > scheduled jobs and recreate them. > What would be nice is an option when scheduling the job to Run as System > account or Run as User and be able to put the users name in. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-9557) Add the ability to schedule a job to run as a system/service user
[ https://issues.apache.org/jira/browse/OFBIZ-9557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16628677#comment-16628677 ] Rohit Koushal commented on OFBIZ-9557: -- Thanks [~jacques.le.roux] for the suggestion and sorry for the late reply but instead of properties can we use permissions here? > Add the ability to schedule a job to run as a system/service user > - > > Key: OFBIZ-9557 > URL: https://issues.apache.org/jira/browse/OFBIZ-9557 > Project: OFBiz > Issue Type: Improvement > Components: tools >Reporter: Matthew Mulligan >Assignee: Rohit Koushal >Priority: Major > > When scheduling a job it automatically schedules it to run as the user that > created the schedule. The issue comes up when that users password changes. > We use LDAP authentication and our passwords change every 90 days. Right now > every 90 days when my password changes I have to delete all previously > scheduled jobs and recreate them. > What would be nice is an option when scheduling the job to Run as System > account or Run as User and be able to put the users name in. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-9379) No definition found for view with name [setLocaleFromBrowser]
[
https://issues.apache.org/jira/browse/OFBIZ-9379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16628590#comment-16628590
]
Benjamin Jugl commented on OFBIZ-9379:
--
It seems as if some patch in the past solved this issue. It can not be
replicated on the actual trunk. I did not go to all extends to locate the fix,
but I think I can roughly pinpoint it to r1835616 to r1834628, when last
modifications on this classes took place.
None the less an error is thrown when calling webtools/control/checkLogin/main:
{{|E| Error in request handler:}}
{{org.apache.ofbiz.webapp.control.RequestHandlerException: Unknown request
[checkLogin]; this request does not exist or cannot be called directly.}}
{{ at
org.apache.ofbiz.webapp.control.RequestHandler.doRequest(RequestHandler.java:280)
~[ofbiz.jar:?]}}
{{ at
org.apache.ofbiz.webapp.control.ControlServlet.doGet(ControlServlet.java:213)
[ofbiz.jar:?]}}
{{ at
org.apache.ofbiz.webapp.control.ControlServlet.doPost(ControlServlet.java:87)
[ofbiz.jar:?][...]}}
It is not shown in the frontend like the original error was.
It is due to the nested request that can not be resolved properly.
I think the useage of nested requests in this context should be considered as
well, as requests that require authentication automatically (and without
errors) redirect to the login page to execute authentication before calling the
initial request. I can neither find the button Jacques mentioned nor is this
link (checklogin/main) used in the actual trunk.
Apart from calling it directly, how can (or could) I get the error? Where has
this nested request been used?
> No definition found for view with name [setLocaleFromBrowser]
> -
>
> Key: OFBIZ-9379
> URL: https://issues.apache.org/jira/browse/OFBIZ-9379
> Project: OFBiz
> Issue Type: Bug
> Components: framework/webtools
>Affects Versions: Trunk
>Reporter: Michael Brohl
>Assignee: Michael Brohl
>Priority: Blocker
>
> After a fresh install, go to localhost:8443/webtools and login with the
> default admin user. Next you get the :ERROR MESSAGE: view with the message
> "org.apache.ofbiz.webapp.control.RequestHandlerException: No definition found
> for view with name [setLocaleFromBrowser]".
--
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=16628419#comment-16628419 ] Arun Patidar edited comment on OFBIZ-10518 at 9/26/18 8:45 AM: --- Thanks [~deepak.nigam] for considering my suggestions. IMO, Inventory reservation should run after allocation plan approval. WDYT? was (Author: arunpati): Thanks [~deepak.nigam] for considering my suggestions. I am thinking that there should run reservation whenever an allocation plan get approved to assign inventory from available. > 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=16628419#comment-16628419 ] Arun Patidar commented on OFBIZ-10518: -- Thanks [~deepak.nigam] for considering my suggestions. I am thinking that there should run reservation whenever an allocation plan get approved to assign inventory from available. > 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=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] [Created] (OFBIZ-10587) _WARNING_MESSAGE_
Niklas Fallik created OFBIZ-10587: - Summary: _WARNING_MESSAGE_ Key: OFBIZ-10587 URL: https://issues.apache.org/jira/browse/OFBIZ-10587 Project: OFBiz Issue Type: Wish Components: ALL COMPONENTS Affects Versions: 16.11.04 Reporter: Niklas Fallik Hi there, I am looking for a way to display warning messages. We are using EVENT_MESSAGE and ERROR_MESSAGE which we can pass to the frontend to display to the user, but it turned out that it would be nice to have a type for warnings like WARNING_MESSAGE. I figured out that the java classes ServiceEventHandler and ScriptEventHandler deal with those message types. I really would appreciate if anyone already had a solution for this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
