Rule to schedule a task offset from a date in DUAS V7

[Angus Reid]

This is an old query but wondering if this has been achiever in V7.

Need to schedule a task in DUAS but the task needs to run a certain number of workdays prior to a specific date. the schedule needs to allow for month end bounderies and leap years and do not want to make a custom calendar.

This can be done easily with a script, wondering if v7 has this useful feature?

i.e. Need to run a uproc 3 work days before the 5th calendar day of April.  Sounds like this should be **** but there does not seem to be an option to fix the 5th of April as a date period and cannot use day of the year due to leap years.

Any thoughts?  

[Eric Delawoevre]

Hi 

Hope you 're well

Never seen your request in the past.

I think all of this is possible on v5 v6 and v7

First: You define the 5th calendar day of April... easy. To compute it fastly. you can define like this:

• Every 1 Month On 5 Calendar Day Forward
• Only April Chekcked

Then.... into the task definition, you define the rule AND a specific item called "Offset Rule"

• - 3 Worked day
• Processing date checked

Kindly

Eric

------------------------------
[JobTitle]
[CompanyName]
#dollaruniverse
------------------------------

[Angus Reid]

The original query was from 2010 so quite a while back. 

Think the is issue is that I was getting bogged down in attempting to create rule to do this as opposed to applying an 'offset rule' when applying the 5th of April rule to the task. 

Still think is some merit in being able to do this within a rule, but yes applying an offset rule to the task will resolve the issue. Thank-you

[Gilles deBuzonniere]

Hello,

You can create this rule :
[cid:image001.png@01DA325F.C2B71030]
And apply it to your task with 5th day of the current month as application date :
[cid:image002.png@01DA3260.508147F0]

The workload forecast gives :
[cid:image003.png@01DA3260.7D233700]

Hope this can help you !

[Gilles deBuzonniere]

Hello,

You can create this rule :
Name : Y-3WD
Every 1 year, on 3 Working day Backward

And apply it to your task with 05/04/2024 as application date :
Rule : Y-3WD (start date : 05/04/2023) (launch time : 20:00) (duration : 0 hour(s) 10 min.)

Hope this can help you !

[Eric Delawoevre]

Gilles,

This is not working because the 05/04/2024 is a remanent date that is applicable for every years. The goal (I think) is to never touch any thing any time

I sent my proposition that is variabized/setable everywhere

------------------------------
[JobTitle]
[CompanyName]
#dollaruniverse
------------------------------

[Gilles deBuzonniere]

Hi Eric,

I've seen your solution, and both do the work ! You should try mine !
The application date of rule is the start date for calculation. Rule Y-3WD gives the third working day from end of each year starting on 5th april. So you'll never have to update the task...

[Eric Delawoevre]

Ok ok. perhapps I missed something. Where is the information for "April 5th YYYY" ? into the rule ? If yes, I'm suspicious, do you have the screenshoot of the rule please?

------------------------------
[JobTitle]
[CompanyName]
#dollaruniverse
------------------------------

[Eric Delawoevre]

Ok I take the point. Yes it's works but....

The computation here is based on a date (05/04/2023).

For that, you inform the CAL to compute this from a calendar With a remanent year. When you go forward, the calculation is done still on this verbatim date. If the calendar is reduced or tranform, th e resoltion can be else, not garranted

Hope that it's clear (sorry for my somewhat explanation)

------------------------------
[JobTitle]
[CompanyName]
#dollaruniverse
------------------------------

[Gilles deBuzonniere]

Yes, the calculation is still done with this verbatim date. As all rule put in any sheduled task !

[Eric Delawoevre]

Yes you're right. Not easy to explain sorry.

On $U The Start Date is useful for Cyclicals (schedules). Here the the information is yearly with a particular date (5). So a cyclical computation on 1/365.

Not only is the sample too extended, but it conforms to the instability in relation to the Calendar/Ruler/Task set

------------------------------
[JobTitle]
[CompanyName]
#dollaruniverse
------------------------------

[Angus Reid]

One more word on this.

Yes the offset_rule works, however unlike rules where many can be added to a specific task it seems it is only possible to add 1 offset rule to a task. So if  2 seperate days are required for a particular offset it would appear that 2 seperate tasks with different offset_rules are required.

Would be nice if the offet_rule could be applied to a specific rule on a task then multiple offsets could be calculated in a single task which had several rules applied

[Gilles deBuzonniere]

I think you should see this idea, which should solve your problem!
Idea Details - Broadcom Community - Discussion Forums, Technical Docs, Ideas and Blogs

------------------------------
Gilles de Buzonnière
------------------------------

[Angus Reid]

Yes that is kinda what is described in this thread have an offset rule. That idea thread was from Jun 27, 2023 take it nothing has happened with it

Maybe later versions of V7 will have this feature? 

Really this in only for a very specific case which has been used once and there is a workaround for this using existing rules. Perhaps once fix up work on current v7 has moved on then support will look at adding more features from the ideas suggestion box?