Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0035842Openbravo ERPB. User interfacepublic2017-04-26 09:382017-05-29 17:43
Reporteralostale 
Assigned Toinigosanchez 
PriorityhighSeveritymajorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version3.0PR17Q3 
Merge Request Status
Review Assigned Toalostale
OBNetwork customerNo
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0035842: process scheduling data can be set in an inconsistent state
DescriptionIt is possible to edit scheduling settings for an already scheduled process request, leaving it in an inconsistent state because the configuration seen in the UI is not the one that is actually in use.

In this situation the new settings take effect only when:
* the request is unscheduled and scheduled again
* or tomcat is restarted
Steps To Reproduce1. Open Process Request and select "Costing Background process" that is already scheduled to be run every 5 minutes
2. Without unscheduling it, change configuration to be run every 2 seconds
3. Check in Process Monitor subtab the actual scheduling continues to be every 5 minutes
4. Restart Tomcat
5. Check now the new configuration has taken effect
Proposed SolutionAll fields affecting scheduling settings should be read only when the process request is scheduled. In order to edit them, the process request should be unscheduled first.
Additional Information
TagsNo tags attached.
Relationships
related to defect 0035835 closed inigosanchez The scheduler fails to load some scheduled processes when an incorrect configuration should be done 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2017-04-26 09:38alostaleNew Issue
2017-04-26 09:38alostaleAssigned To => platform
2017-04-26 09:38alostaleOBNetwork customer => No
2017-04-26 09:38alostaleModules => Core
2017-04-26 09:38alostaleTriggers an Emergency Pack => No
2017-04-26 09:39alostaleRelationship addedrelated to 0035835
2017-04-26 09:39alostaleStatusnew => acknowledged
2017-05-10 14:04inigosanchezStatusacknowledged => scheduled
2017-05-10 14:04inigosanchezAssigned Toplatform => inigosanchez
2017-05-13 08:02hgbotCheckin
2017-05-13 08:02hgbotNote Added: 0096574
2017-05-13 08:02hgbotStatusscheduled => resolved
2017-05-13 08:02hgbotResolutionopen => fixed
2017-05-13 08:02hgbotFixed in SCM revision => http://code.openbravo.com/erp/devel/pi/rev/8df7c04de69fba88d1ec3bd1a1bb4854cae8734f [^]
2017-05-13 08:03inigosanchezReview Assigned To => alostale
2017-05-15 12:56alostaleNote Added: 0096590
2017-05-15 12:56alostaleStatusresolved => closed
2017-05-15 12:56alostaleFixed in Version => 3.0PR17Q3
2017-05-29 17:43hudsonbotCheckin
2017-05-29 17:43hudsonbotNote Added: 0096965

Notes
(0096574)
hgbot   
2017-05-13 08:02   
Repository: erp/devel/pi
Changeset: 8df7c04de69fba88d1ec3bd1a1bb4854cae8734f
Author: Inigo Sanchez <inigo.sanchez <at> openbravo.com>
Date: Sat May 13 08:01:32 2017 +0200
URL: http://code.openbravo.com/erp/devel/pi/rev/8df7c04de69fba88d1ec3bd1a1bb4854cae8734f [^]

Fixed issue 35842: Process scheduling data can be set in an inconsistent state

The problem was that it was possible to edit scheduling settings for an already scheduled process
request, leaving it in an inconsistent state because the configuration seen in the UI is not the
one that is actually in use.

In order to resolve this problem all fields affecting scheduling settings are read only when the
process request is in scheduled or processing status.

---
M src-db/database/sourcedata/AD_COLUMN.xml
---
(0096590)
alostale   
2017-05-15 12:56   
code reviewed + tested
(0096965)
hudsonbot   
2017-05-29 17:43   
A changeset related to this issue has been promoted main and to the
Central Repository, after passing a series of tests.

Promotion changeset: https://code.openbravo.com/erp/devel/main/rev/1ee70113bdc4 [^]
Maturity status: Test