RouteWhenStatus Rules

Did you know that you can have your Spitfire system do things to your route when your document changes to a particular status? One way to do this is through workflow scripts. The other way is through the RouteWhenStatus rule group.

Through RouteWhenStatus | Default and DefaultPending rules you can:

  • Append a predefined route [Append],
  • Change the route status of all remaining routees to CC’d [CCRemaining],
  • Change the route status of all but the last routee to CC’d [CCToLast], and
  • Change the route status of all remaining routees to Responded/Sent On [EndRoute]

If you use the Default rule, these route changes will occur when you change the status on the document to Closed (or any “closed” status). If you use the DefaultPending rule, these route changes will occur when you change the status on the document to Pending (or any “pending” status).

For example, if you wanted to jump to the end of the route list when a Commitment is saved as Committed (which is a Pending status), you would set up the following rule:

201608 DefaultPending

This means that, on the following route, if Andrew changes the document status to Committed then routes the document, it will go directly to Chris at Seq 5:

201608 Andrew Route    201608 Chris Route

As another example, if you wanted to remove the Bid Package document from everyone’s Inbox whenever such a document is closed, you would set up the following rule:

201608 DefaultNote:

For more information about the RouteWhenStatus rules, see KBA-01177.
For more information about the Rules Maintenance tool, see the Focus on System Administration guide.
For more information about routing, see the Focus on Routes guide.