how-to Automatically remove from a board after a given time period?

[lee mcdermott]

Hi,

is it possible to remove a call from a board using the BPM after x amount of time(i.e. 4 weeks)?

thanks

 

lee

[Steven Boardman]

Hi @lee mcdermott there isn't an action to delay the removal of a request from a board for after a specific period of time, however you could achieve the same result by using the Expire options which are on other BPM nodes - such as 

* Task

* Suspend await status change

* Suspend await request update

So at the appropriate point in the process, use one of the above (maybe a task) set the task Expire to 28 days and then follow it with decision and and outcome of expire - then you can use the remove from board node following the expire path.

Just a thought 

Steve

 

 

[lee mcdermott]

@Steven Boardman

 

thanks for that. Do you think this would still work following a closure task?

Basically at the end of a bpm I have move call to completed list on a board. But that list now has over 300 on it which becomes a bit meaningless. So I thought i would add a timer to remove it after 28 days once the call is closed.

[Steve Giller]

I've updated this similar thread to include your suggestion, @lee mcdermott

[lee mcdermott]

@DeadMeatGF

 

ah thanks

 

yes exactly the same issue. Lets see if anything comes of it. Hopefully so. 

having a timer or setting for the board to remove things is a good idea.

[Steven Boardman]

@lee mcdermott i have done a quick test and the expiry option on a task after a request is closed works fine

In my example below i Auto Close then do a check if it was a major incident, close linked requests, send notifications then have a task set to expire after 2 mins, with an outcome of expire and then remove from board

Hope that helps

We will explore the options of even having a generic Suspend for a defined period of time option

We also have a story for the remove from any boards which will remove a request from any board it is on, again as this progresses we will post back

Steve

[lee mcdermott]

@Steven Boardman

 

thanks steve. I will give this a try.

 

On a slightly separate note I was going to start looking at how we deal with and process major incidents. i noticed your example is checking if it is a major incident.

How or what is this actually checking is it just a certain priority level or is there something in Hornbill where you can actually specify the call as being a major incident?

[Steven Boardman]

HI @lee mcdermott in my example i am simply checking the priority of the request to see if it is Major in my example i check this on logging, to see if a Major Incident Comms plan needs invoking, and at the end of the workflow to see what i need to do to close it down.  You could of course look at any other value to determine if it is a major incident, such as a request custom field as a tick box.

On the demo instance, if you want to take a look their is an example major incident process which takes care of:

* Adding operational management

* Adding in senior management

* Invoking the relevant Service Level Targets

* Notifying all interested parties (email and workspaces) as the major incident proceeds and is updated

* Use of hot topics Boards

* Closure of all linked requests 

* removal from boards

Access the sandbox at admin.hornbill.com/demo

user: grahamc

password: H0rnbill 

In the process designer take a look at the Desktop Support example

Hope it helps

Steve

[lee mcdermott]

@Steven Boardman

 

thanks steve - will certainly have a look.