0010245: Process Scheduling: Start Time in Process Request is not taken into account if daily option is not null

Openbravo Issue Tracking System - Openbravo ERP

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0010245

Openbravo ERP

A. Platform

public

2009-08-12 10:24

2010-04-17 00:00

Reporter

AinhoaPagola

Assigned To

iperdomo

Priority

urgent

Severity

minor

Reproducibility

have not tried

Status

closed

Resolution

fixed

Platform

OS Version

Ubuntu 8.4

Product Version

Target Version

2.50MP14

Fixed in Version

Merge Request Status

Review Assigned To

OBNetwork customer

Web browser

Modules

Core

Support ticket

Regression level

Regression date

Regression introduced in release

Regression introduced by commit

Triggers an Emergency Pack

Summary

0010245: Process Scheduling: Start Time in Process Request is not taken into account if daily option is not null

Description

If a process request is filled out with frequency field set to daily, the fields daily option and start time are incompatible.

If frequency is set to daily and:

- start time is set and daily option field is null -> process scheduled to start time.
- daily option is NOT null -> start time is ignored and the process is scheduled to 'now' time.

Steps To Reproduce

Go to General Setup || Process Scheduling || Process Request
Create a new record:
* Timing: Schedule
* Frequency: Daily
* Start time: 00:00
* daily option: Every N days.
* daily interval: 1
Click on schedule process

Check that in ad_process_request table the field next_fire is created for 'now' hour and no for '00:00' hour. If daily_option field was null, the hour would be 00:00.

Proposed Solution

I have several proposals:

1.- Take into account the start time although daily option is selected.
2.- Show a message to advise the user that the start time will not be considered if daily option has a value.
3.- If daily option is not null hide the start time. Be careful because it will be hidden by default and it's not intuitive how to make it visible.

If possible, I would go for 1.

If case of 2 or 3 I would suggest to remove the 'on default = N' set in the application dictionary for daily_option column. Notice that in the database there is no default set. If for some reason this default value is kept, I would set a default value (1) for daily_interval.

Additional Information