IDS Logic

Logic rules act on transactions based on specific criteria. They share some similarities with routing rules in the customization manager but can be more complex and be ‘chained together’ to have multiple rules act on one transaction. Routing rules, on the other hand, can only have one routing rule act on a transaction before a staff member needs to intervene to move the request to another step. 

Logic Rules can be broken down into ‘search’ and ‘action’. 

Search: Some things Logic Rules can search for in a transaction are:

• NVTGC
• Process Type: Borrowing, Lending, Doc Del
• Request Type: Loan, Article
• Queue that the Request is currently in
• Flags
• Time since request was last updated or since creation
• Time until a request is due or time the request is overdue
• Any field in the Request such as:
  • Location
  • Call Number
  • Due Date
  • ISSN/ISBN
  • Bibliographic Information: Title, Author, etc.
  • Citation Information
  • System ID (OCLC, RAPID, DOCLINE, etc)
  • Lending String
  • Borrower

Action: Some things Logic Rules can do: 

• Route transactions
  • To other queues
  • To Borrowing or DocDel
• Add or remove flags
• Send emails (and define the subject of the email)
• Add notes
• Add content to fields like ItemInfo1 or Location

Additionally, Logic Rules have a setting, called “Prevent Reruns” that can prevent a logic rule from running on a transaction more than once.

What does a Logic Rule Look like?

The following is what settings are available within a Logic Rule.

LogicRule_1:
 Enabled: "0"
 RuleName: ""
 PreventReruns: ""
 NVTGCList:
 - ""
 ProcessTypeList:
 - ""
 RequestTypeList:
 - ""
 TransactionStatusList:
 - ""
 FlagList: ""
 Query: ""
 UpdatedMinutes: ""
 CreatedMinutes: ""
 DueMinutes: ""
 OverDueMinutes: ""
 RouteTo: ""
 RouteToBorrowing: ""
 RouteToDocDel: ""
 AddFlag: ""
 RemoveFlag: ""
 EmailTemplate: ""
 EmailSubject: ""
 AddNote: ""
 SetFields:
 - ItemInfo1: ""
 - ItemInfo2: ""
 - ItemInfo3: ""
 - ItemInfo4: ""
 - ItemInfo5: ""

There are some examples of Logic Rules on the Examples of Logic Rules page.

Breaking Logic Rules Down Further

Rules generally have a query or search component as well as an action. The following list describes each configuration option. The answers to the questions can help the IDS team configure and setup rules for you on the backend to meet workflow needs.

The Search Part:

 Enabled: Is this rule on?
 RuleName: What would you like to name your rule
 PreventReruns: Should this rule re-run on TNs it has already acted upon?
 NVTGCList: What NVTGCs should this run on?
 ProcessTypeList: What ProcessTypes should this run on? (Borrowing, Lending, Doc Del)
 RequestTypeList: What RequestTypes should this run on? (Loan, Article)
 TransactionStatusList: What queues should this run on?
 FlagList: What flag or flags does the TN have?
 Query: What special query would you like to run to identify the TN? 
 UpdatedMinutes: This is anything that was updated within X minutes
 CreatedMinutes: This is anything created within X minutes
 DueMinutes: This is anything that was marked as due within X minutes
 OverDueMinutes: This is anything that is overdue by X minutes

The Action Part:

 RouteTo: Where would you like to route the TN (within the same ProcessType)
 RouteToBorrowing: If you want to change the ProcessType to Borrowing, where do 
you want to route?
 RouteToDocDel: If you want to change the ProcessType to DocDel, where do you want 
to route?
 AddFlag: Do you want to add a flag? What is the name of the flag?
 RemoveFlag: Do you want to remove a flag? What is the name of the flag?
 EmailTemplate: Do you want to send an email? What is the name of the template?
 EmailSubject: What is the subject line of the email that you would like to send?
 AddNote: Do you want to add a note to the TN? What would you like it to say?
 SetFields: You can set fields within the TN. These are just examples.
 - ItemInfo1: ""
 - ItemInfo2: ""
 - ItemInfo3: ""
 - ItemInfo4: ""
 - ItemInfo5: ""