Jump to content

Recommended Posts

Posted

Hi,

We are creating a workflow to aid with Absence Management and need to put a request on hold until 8 weeks before the end date of the absence

The end date is captured in custom 22

The easiest way I have thought to do this is by using the Calculate Working Date/Time node, but am unsure if this can calculate minus values?

 

This is how I have it set up where the start date is the end date variable - is this the best way to do this?

image.png.37e2751b08263ba9a1b2698365c360ac.png

Posted

The way I've done this when needed is to use the Get Timestamp utility (Service Manager > Application > Utility > Get Timestamp).

Calculating that against working time is, assuming 8 hours/day 5 days/week, going to turn into something closer to 6 months instead of 56 days.

You'd use the end date as the starting timestamp, operator would be Subtract, and the timeUnitDays would be 56, that should get you the time-stamp. Given it's an off-hold time, it might come off-hold during downtime, a weekend or something, but the SLA wouldn't continue to tick, at the least.

Posted

I have the same scenario as you (starting timestamp is in the future, release x days before that date) and this is how my node is configured (note this is a Cloud Automation task which has since been migrated in to the Hornbill Automation node so may need some adjustment).  If you're processing lots of timestamps in the same Stage, its best to make your nodes unique by updating the result reference - here you can see I have appended ProcessOn, so that a) its easier for me to identify when using the variable picker and b) so that the Workflow knows which Timestamp to use.

image.png.a185280c21dc8aa3bb5b2df2cf64c503.png

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...