Start Date Calculation Using Created Date, Time, and Working Days

Liberty Create
1

In my General Object for my process, I have the following properties (format = date)…

  • Date Received - allows a user to enter a date if the complaint was received before the form is completed

  • Start Date - the date from which the Due Date timer begins

  • Due Date - the target completion date, calculated based on the Start Date and the type of complaint

So far, this is what I am trying to achieve:

When the form is completed:

  • If the created date/time is after 5pm and Date Received is empty, set Start Date to the next working day

  • If the created date/time is before 5pm and on a working day and Date Received is empty, set Start Date to today

  • If the created date/time is before 5pm and not on a working day and Date Received is empty, set Start Date to the next working day

  • If Date Received is not empty, set Start Date to Date Received

I suspect that the way I am trying to implement this just won#t work. I’m unsure how to handle the time (5pm cutoff) and working day logic within the rules. I attempted to create a rule to set the Start Date when the created date/time is before 5pm on a working day, but I’m unable to specify the required time and working day conditions.

Very new Liberty user here, please let me know if more clarity is needed or if I am barking up the totally wrong tree. I realise this might be quite a complicated question, and happy to even be pointed in the right direction of what to look at.

SLA Rule Screenshots
SLA Rule Screenshots1060×972 114 KB

2

I’ve done similar things in the past and I’ve created composite to calculate the 5pm Date Value…and use this value in the subset.

image

You can add one composite to get just the date for a field – e.g. Date Created

image
image1836×801 42.1 KB

And then another composite to use that to add 17 hours to 1st composite

image
image1846×809 41.5 KB

You can then use this composite in your subset…
There is likely a better way, but this is what I’ve done in the past.

1 Like
3

I think i’ve done something similar by modifying the default SLA working days code to handle working hours too, but that was all in code rather than rules. Jonathan’s method using composites sounds like it’s likely to be the best option when done fully no code. Not sure off the top of my head how you determine if something is a working day outside of code, unless you just check for day of the week, likely using a composite again?

1 Like
4

Thanks for your replies. Still working on this at the moment, trying it out with composites and struggling a little bit but will get there and yeah if not, maybe will need to be done in code. Will share the solution once we have it!

5

HI Ashleigh

In your scenario you want the Start Date field to be populated when the form is submitted (or when the record is created). That is a write back operation, you need a rule, event or workflow that sets the field’s value in the database. A composite can’t do that it can only display a derived value so you will need something to store that value.

You could create a composite that shows what the Start Date would be based on the logic you described, but the actual field would still need to be set by a rule so that the value is persisted and can be used by other parts of the system (e.g., due‑date calculations, reporting, notifications) or if you add both fields to the page, you could hide one and copy the derived value and save on submit to use later.