This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Server Time - Workflow Based Notifications Send Time

Former Member
Former Member
Good day Community,

We have a unique scenario with a clients workflows and thought it might be a good idea to plug into the community to see if anyone has solved this before or has a starter point for the script that we may require.  I'd hope we aren't the first to run into this.

There are two parts to this scenario. Firstly the server has a set time for Daily Digest emails of 9:00 AM.  This also impacts any notification rules, built in the Desktop Client, one that use a Date value within the Define Filter, withholding them until 9:00 AM.  This is perfect, sending these out during the clients business hours.

We have also been building various workflows for this client and have noticed that on one workflow which utilizes the DayFrom() function, with a Date Property. That the workflows built in notifications, the ones on certain Events are triggering between 12:00 AM and 01:15 AM.  This makes sense as the server clocks kicks over to the next day, and the property matches the Define Filter conditions of the trigger, the one set before the workflow State containing the notification settings.  Unlike the Notification Rules, these do not appear to be governed by the Digest message time setting in the Admin Console thus they are sent out immediately once matching.

Could a script in the State Transition trigger resolve this?

Or should we script a Precondition on the State with the notification Action?

One concern we have is that if its a Precondition, would it sit on the server until the specified time frame, or would it be prompting the server constantly to complete that action?  Wouldn't want to bog the server down unnecessarily.

Please let me know if you have any suggestions or thoughts regarding this scenario.

Thanks
Parents
  • Former Member
    Former Member
    Our latest idea for this is along the lines of trying to leverage a Time or Timestamp property, likely one hidden away from the users. Has anyone managed something like that? where at the chosen time 'property', that the server goes ok, time to send the notification, 8:00 AM = 8:00 AM kind of logic.

    For this we thought that Created would be a good starting point, since the clients would be creating these during their business hours, the system would see 2:00 PM as the creation time and then the Time/Timestamp trigger would push the workflow to the notification stage once the server matched.

    One of our troubles is Created is treated as a date property with those operators and kind of disregards the fact that they are merged (Date & Time).

    Unfortunately thought this logic, the server would likely see Time=Time immediately because once created they would immediately be equal as the property would be a flat time.

Reply
  • Former Member
    Former Member
    Our latest idea for this is along the lines of trying to leverage a Time or Timestamp property, likely one hidden away from the users. Has anyone managed something like that? where at the chosen time 'property', that the server goes ok, time to send the notification, 8:00 AM = 8:00 AM kind of logic.

    For this we thought that Created would be a good starting point, since the clients would be creating these during their business hours, the system would see 2:00 PM as the creation time and then the Time/Timestamp trigger would push the workflow to the notification stage once the server matched.

    One of our troubles is Created is treated as a date property with those operators and kind of disregards the fact that they are merged (Date & Time).

    Unfortunately thought this logic, the server would likely see Time=Time immediately because once created they would immediately be equal as the property would be a flat time.

Children
No Data