Berto2002 Posted September 3, 2021 Share Posted September 3, 2021 I have a change window expiry action in the workflow that escalates to me if the window passes and the change is not declared as done. My technician went to the task at 15:10 to action it but it had gone. The Scheduled End Time was 15:10... He thought he was in time. We humans we see an expiry at 15:10 as meaning that we have got until the whole of that minute goes by - i.e. until its END at 15:11. However, the system sees the START of that minute as it's criteria for expiry. Never thought of that before. My Expiry uses this Variable: &[global["flowcoderefs"]["resultRef"]["scheduledEndDate"]]. What node/logic do I need to use to add one minute to that time to give me a variable that is 1 minute later? Link to comment Share on other sites More sharing options...
Steven Boardman Posted September 3, 2021 Share Posted September 3, 2021 @Berto2002 you could take a look at the Get Timestamp option which is available in the iBridge > utilities in the business process designer This will allow you to set the scheduled end date as the Starting Timestamp, you can use the Add Operator, and then increment the value using the Minute option by one, and then use the output timestamp as the expiry. You would of course need to use this option ahead of the window expiry action in your workflow. Something to look at i hope 1 Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now