You can configure an application-quota rule to limit the number of events or jobs that can run in an application's scope within a specified time.

1. Navigate to System Definition > Application Quota Rules.
2. Click New.
   The Application Quota Rule form is shown.
3. Fill in the fields.

   Table 1. Configuring application quota rules

   Field	Description
   Name	A unique name to identify the rule.
   Application	The scoped application's name. To change this field, use the application picker to change the application. This field cannot be Global.
   Order	A number that represents the priority of the quota transaction in relation to other quotas.
   Active	A check box that determines if this rule is active (selected).
   Log only	When checked, transactions are not canceled by a quota violation, but entries are added to the local host log that indicate the transactions are violating the quota rule. An entry is added to the Transaction Cancellation Log where the log only field is set.
   Maximum Events	The maximum number of events allowed during the update period.
   Maximum Jobs	The maximum number of jobs allowed during the update period.
   Condition	The conditions that determine when the transaction quota applies. The condition builder displays conditions that are only applicable to transactions. For example, Foreground is true.
   Description	A description of the transaction quota.

4. Set a condition to specify when the application quota rule should take effect.
   The application quota rule condition builder displays conditions that are only applicable to transactions as listed in the following table.

   Field	Description
   Attributes	Miscellaneous attributes that are related to the transaction.
   Created	When the transaction was created.
   Created by	Who created the transaction.
   Foreground	Whether the transaction was completed in the foreground or background: True: a foreground transaction. False: a background transaction.
   Homepage	The homepage that is running. This value is populated only if the URL is home.do.
   Homepage Widget	The homepage widget that is rendered in the transaction. When a homepage is rendered initially, each homepage widget is rendered in parallel.
   Initial Scope Name	Scope where the method that created the transaction is defined. Setting this name to anything other than the selected application means that the rule is never used. The rule only looks at transactions of the selected application, and this value has the rule look for a different application, so the condition is never satisfied.
   Scope Name	Scope of the application that called the method that created the transaction.
   Sys ID	A sys_id of the transaction.
   Thread Name	The name of the execution thread that is running the transaction. Foreground threads have names like http-bio-8080-exec-1. Background threads may have various names, and may be useful where the URL is not sufficiently descriptive.
   Type	The type of transaction: List: Any list transaction, such as incident_list.do. Form: All forms, UI pages, CMS pages, and so on. XMLHttp: Transactions that run through GlideAjax, where the URL is xmlhttp.do. Report: The page sys_report_template.do. SOAP: SOAP transactions. Export: When a list is exported in a format such as XML, Excel. Scheduler: When a scheduled job is performed. Text Search: The text search transaction or any of its related operations. Other: Any type that does not meet the qualities of another type. Note: Match the transaction quota Type to the transaction type listed in the Quota Manager log entry for the transaction.
   URL	The URL of the page.
   Updated	When the transaction was updated.
   Updated by	Who updated the transaction.
   Updates	What was updated.
   User	The user performing the transaction.

5. Click Submit.