Jump to content
Sean Teehan

How to Suspend a change request to Expire after the change end date

Recommended Posts

Hi,

 

is there a way to suspend / expire a change request a certain time frame after the end date?

 

the aim is for Standard changed to automatically resolve 24 hours after the end date of that request as successful unless the user has entered that request and set a different status.

 

thanks,

Sean

Share this post


Link to post
Share on other sites

@Sean Teehan have a look here: https://wiki.hornbill.com/index.php/Service_Manager_Business_Process_Workflow. Look in "Suspend" section at "Wait for Status Change" node. I think that's what you are after.

There is also a guide on how this can be implemented here: https://wiki.hornbill.com/index.php/Two_Stage_Closure. Maybe what you need is not exactly what the guide describes but it looks similar to me.

Share this post


Link to post
Share on other sites

Hi @Victor,

 

Thank you for this. I have taken a look but i don't think the status of the request will change after the scheduled end date has passed. I can see i can suspend the request to get the user to enter the Scheduled start and end but what i am looking for is the request to stop and wait till after the end date has passed then move to the next step.

 

I hope that makes sense.

 

thanks,
Sean

Share this post


Link to post
Share on other sites
15 minutes ago, Sean Teehan said:

scheduled end date

Oh, sorry, looks like I misread this bit... it's about the scheduled dates for a change request... ermm... I am not sure we can do this then, I'll have a quick look though

Share this post


Link to post
Share on other sites

Hi @Victor,

 

Did you manage to find a way to do it? If not, is it possible to add this as an enhancement? i would be very useful to have a suspend option that will move on once to the end date / time has past, this can then be automatically moved into a Review / Verify status.

 

thanks,

Sean

Share this post


Link to post
Share on other sites

@Sean Teehan I’ll have a look a bit later today. The only way this would work is if we can have that scheduled end date in a workflow variable and use that in the expiry for the suspend node. Not sure on top of my head if possible. If not then it will require an enhancement.

Share this post


Link to post
Share on other sites

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...