Okay, can you provide some steps or link to a Work Effort in the demo ( http://demo-trunk-ofbiz.apache.org/workeffort/control/EditWorkEffort?workEffortId=10000) so that I can see what fields need to be filled?
In my testing with a job on trunk code, first job would get finished but no new jobs would get created. -- Vyom On 19 September 2015 at 20:52, Adrian Crum < adrian.c...@sandglass-software.com> wrote: > It is best to test temporal expressions with the Work Effort application - > so you can see the effect of your expression. > > I used the DAILY_GRIND temporal expression in a work effort and it creates > the correct events. > > Adrian Crum > Sandglass Software > www.sandglass-software.com > > On 9/19/2015 3:11 AM, Vyom Jain wrote: > >> I've been testing with the demo data and this is more likely a bug with >> HOUR_RANGE. For example, if I use TemporalExpression DAILY_GRIND >> (ServiceDemoData.xml) on a job, the job runs once but no jobs are >> scheduled >> for the next day. >> >> -- >> Vyom >> >> On 18 September 2015 at 20:51, Vyom Jain <vyom0...@gmail.com> wrote: >> >> I've been trying to prepare similar expression on trunk code but neither >>> INTERSECTION nor DIFFERENCE give desired results (mentioned in first >>> message). >>> I've split "TIME_OF_DAY_RANGE" expression & replaced it with separate >>> "FREQUENCY" & "HOUR_RANGE(8, 18)" expressions. >>> There seems to be an issue with HOUR_RANGE evaluation. >>> >>> Can anyone suggest what is wrong in the expression? Could this be a bug? >>> On Aug 11, 2014 16:37, "Vyom Jain" <vyom0...@gmail.com> wrote: >>> >>> TIME_OF_DAY_RANGE includes a frequency portion in it (integer1="13" >>>> integer2="05"), when I had independently used <TemporalExpression >>>> tempExprId="8AM6PM" integer1="13" integer2="05" >>>> tempExprTypeId="TIME_OF_DAY_RANGE" string1="08:00" string2="18:00"/>, >>>> the >>>> service would start *everyday* at 8:00, get scheduled after every 5 >>>> seconds >>>> and finally stop at 18:00. >>>> >>>> I've been able to formulate an expression that is giving me desired >>>> results - >>>> <TemporalExpression tempExprId="8AM6PM_MON_FRI" >>>> tempExprTypeId="DIFFERENCE"/> >>>> <TemporalExpression tempExprId="8AM6PM" integer1="13" integer2="05" >>>> tempExprTypeId="TIME_OF_DAY_RANGE" string1="08:00" string2="18:00"/> >>>> <TemporalExpressionAssoc fromTempExprId="8AM6PM_MON_FRI" >>>> toTempExprId="8AM6PM" exprAssocType="INCLUDE"/> >>>> <TemporalExpressionAssoc fromTempExprId="8AM6PM_MON_FRI" >>>> toTempExprId="SAT_TO_SUN" exprAssocType="EXCLUDE"/> >>>> >>>> >>>> -- >>>> Vyom >>>> >>>> >>>> On 11 August 2014 16:20, Adrian Crum < >>>> adrian.c...@sandglass-software.com> >>>> wrote: >>>> >>>> You are missing a Frequency expression. It is needed to make the event >>>>> repeat every 5 seconds. >>>>> >>>>> Time Of Day Range was removed because it was a bad implementation and >>>>> it >>>>> didn't function properly. >>>>> >>>>> Adrian Crum >>>>> Sandglass Software >>>>> www.sandglass-software.com >>>>> >>>>> >>>>> On 8/10/2014 8:32 PM, Vyom Jain wrote: >>>>> >>>>> Hello Everyone, >>>>>> >>>>>> I would like to schedule recurring jobs in such a way that the job >>>>>> executes >>>>>> every 5 seconds from Monday to Wednesday starting from 08:00 till >>>>>> 18:00. >>>>>> >>>>>> I've tried following temporal expression - >>>>>> >>>>>> <TemporalExpression tempExprId="8AM6PM_MON_FRI" >>>>>> tempExprTypeId="INTERSECTION"/> >>>>>> <TemporalExpression tempExprId="8AM6PM" integer1="13" integer2="05" >>>>>> tempExprTypeId="TIME_OF_DAY_RANGE" string1="08:00" string2="18:00"/> >>>>>> <TemporalExpressionAssoc fromTempExprId="8AM6PM_MON_FRI" >>>>>> toTempExprId="MON_TO_FRI"/> >>>>>> <TemporalExpressionAssoc fromTempExprId="8AM6PM_MON_FRI" >>>>>> toTempExprId="8AM6PM"/> >>>>>> >>>>>> This expression doesn't work as expected - the job doesn't execute >>>>>> every 5 >>>>>> seconds till 6:00 PM, it starts at 8:00 Monday & next run gets >>>>>> scheduled to >>>>>> 8:00 Tuesday. >>>>>> >>>>>> Can anyone suggest what is wrong in the expression? >>>>>> >>>>>> Note: tempExprTypeId="TIME_OF_DAY_RANGE" is no longer valid in current >>>>>> trunk, though it is valid in the version of OFBiz I'm using (somewhere >>>>>> between v09.04 & 10.04). >>>>>> >>>>>> -- >>>>>> Vyom >>>>>> >>>>>> >>>>>> >>>> >>
