Rule schemas contain templates for conditions and results in decision tables. These templates define the attributes, the permitted values, and any limitations for each attribute. Decision tables use these attributes to define inputs and the corresponding outputs, thus making the decision making process straightforward and predictable. 

1. Click Menu > Orchestration > Rule-Based Decisions > Rules Schemas. 
2. Click Add Rule Schema. You can create up to 50 rule schemas per organization. 
3. In the Name box, type a unique name. 
4. In the Description box, provide a description of the use of the schema.
5. In the Attributes section, create the require attributes for the schema. A rule schema must contain a minimum of two attributes and a maximum of 50 attributes. You can create two types of schemas
   • Platform: Currently Genesys offers the queue platform attribute. The queue names are available for you to select and use in the rule-based decision tables. When you add a queue attribute, on the decision table, you can view all queues that belong to the division that your user role has access to. 
   • Standard: Enter a name, key, and description for each attribute you define. For more information, review the best practices listed at the end of this article. 
     
     • Boolean: A Boolean expression can have only one of two values: true or false. 
     • Date: A Date value is a string in the format prescribed by the XML standard for date data, similar to ISO 8601.
     • Date & Time: A DateTime value is a string in the format prescribed by the XML standard for date data, similar to ISO 8601. 
     • Enum: An Enum is a predefined list of selectable options.
     • Integer: An integer is a whole number such as 987 or 5.
     • Number: A number includes any numeric values, including decimals. Decimals can have up to 10 decimal digits.
     • String: This is a standard text string or a custom series of alphabetical, numerical, and symbolic characters.
     • String List: A list containing several string values. For example, you can define a list called Portfolio and enter the names of various departments such as Loans, Insurance, Cards, Banking, etc. 
       When you define the list of strings, you can also specify the number of strings that are allowed within a list and the character limit for each string.
       • Minimum Items and Maximum Items – Define the least and the highest number of strings that the list can contain. 
       • Minimum Characters and Maximum Characters (per item) – Define the lower and higher end of character limit for each string within the list. 
       • Unique Values – To prevent duplicate entries of the same string, enable this option.  
6. Click Add. The new attribute is now added to the selected schema.
   Note: If required, you can delete an attribute before you save the schema. You cannot delete the attribute once you save the schema with the newly added attribute.
7. On the Rules schema page, click Save Schema. 

Best practices and limitations to build rules schema

• Genesys recommends that you do not use PII information such as phone numbers or email addresses and sensitive information such as credit card and social security numbers for rule building. Rules that contain PII information may be deleted as part of GDPR request processing and the subsequent decisions may not be accurate as planned. 
• The following rules apply when you set up attribute keys for rule schema:
  
  • Cannot start with numbers.
  • Can contain only english letters, numbers, and underscore.
• To achieve optimum performance, Genesys recommends you create enum attributes.
• Use shorter string values with low cardinality instead of long ones.
• You can create up to 30 attributes in total, with a maximum of 20 attributes of the String data type.
• You can use a maximum of 10 string list attributes within a decision table. Each list can contain a maximum of 50 strings, with each string length limited to 20 characters.
• The combined length of all string attributes per decision table row can be up to 4000 characters only.