> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/random-selection/bulk-random-selection-items/creating-a-bulk-random-selection-item.md).

# Creating a Bulk Random Selection item

### Pre-requisites

If the Bulk Random Selection rule will expire or disable a Competency upon a Cardholder being selected, ensure the Competency has been configured before proceeding with this procedure. Refer to "Configuring Competencies" in the Gallagher Configuration Client Online Help.

### Configuring the Random Selection tab

Perform the following procedure to create a Bulk Random Selection item and configure selection conditions:

1. From Command Centre main window, click **Administration** > **Random Selection**.
2. Click the **New Random Selection** button and select **Bulk Random Selection**.

   The Bulk Random Selection Configuration window displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-2c8308b077d3b4d0d70a89fff2fb7ca01432d4c1%2Fbulkrandomselection-bulkrsconfiguration.png?alt=media)
3. Enter a Name and Description, and select a Division. Then, click Close.
4. Click the **Add Selection Criteria** button to add a criteria that Cardholders must meet in order to be eligible for selection.

   **Note:** You must add at least one selection criteria.

   The Advanced Search Rule Definition pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-b4b309c5640d7fbfe0e5224671dcd889e063fab6%2Fadvancesearchrules_popup.png?alt=media)

   This pop-up allows you to set the rules, (i.e. one or more conditions) to define which Cardholders are eligible for selection. The Bulk Random Selection will find Cardholders to select according to these search conditions.
5. Click on the function you want to perform:

<details>

<summary>Inserting a condition</summary>

1. Click the **Insert Condition** button.

   The Cardholder Search Condition pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-e8ed6ef6427592f87fdfffbd1ab4bc60db85c677%2Feditcondition_popup.png?alt=media)
2. Select a Condition **Type** from the drop-down list.

   The options available depend on the Condition Type you selected.
3. Select the appropriate options for the condition you require.

   **Note:** For a multi-server system, if you select to search on "Cardholder last requested access", aggregation must be turned on in order for the search results to be accurate.
4. Click the **OK** button.

   The condition is added to the Advanced Search Rule Definition pop-up.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-ef1152121d0ea7f319b2a888494cfaf450366c56%2Faddedcondition_advancedsearch.png?alt=media)
5. Repeat Steps 1 - 4 for each additional condition you want applied to this rule.

   Each additional condition is also added to the Advanced Search Rule Definition pop-up. As conditions are added an **'And'** will appear to the left of the added row (as shown below):

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-7d1cdbc3342ec0d83f68ee46320a36db7c0012e4%2Faddedcondition_advancedsearch2.png?alt=media)

   **Notes:**

   * The conditions can be re-ordered by clicking the ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-29736411754d57a3b21865d1406c092a8221406f%2Fstatus_orderbuttons.png?alt=media) buttons.
   * Only Cardholders who match ALL conditions will be returned in the Search results.
   * Each condition can only be added once to the same "And" grouping in a Cardholder search, with the exception of unique Personal Data Fields and Competencies.
   * The **'And'** setting of a condition can be changed to **'Or'** by selecting the condition and clicking the **Change to 'Or'** button. The **'And'** is replaced with **'Or'** above the row of the selected condition (as shown below):

     ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-6b0d4abb13fc9f22db6154c550abc50f2728dd14%2Faddedcondition_advancedsearch3.png?alt=media)

     Should you want to revert it back to **'And'**, either select the row the **'Or'** is on and click the **Change to 'And'** button, or click the **Cancel** button.

</details>

<details>

<summary>Editing an existing condition</summary>

1. Click the **Edit** Condition button.

   The Cardholder Search Condition pop-up displays and is populated with data relevant to the condition type selected.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-59457898acfec6e2d08fe989f410632896c4c5b2%2Feditexistingcondition_popup.png?alt=media)

   **Note:** In this example, all cardholders that have an expired Competency will be included in the Advanced Search.
2. Edit the condition as required, and click the **OK** button.

   The condition is altered accordingly in the Advanced Search Rule Definition pop-up.

   **Note:** The conditions can be re-ordered by clicking the ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-29736411754d57a3b21865d1406c092a8221406f%2Fstatus_orderbuttons.png?alt=media) buttons

</details>

<details>

<summary>Removing a condition</summary>

Click the **Remove** button.

The condition is removed from the Advanced Search Rule Definition pop-up.

</details>

6. Click the **OK** button.

   The criteria is added to the **Bulk Random Selection** tab.

   **Notes:**

   * Clicking the ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-46de7e526830dd1b8bd583073883ebba6321ce51%2Fdisplaycholdbutton.png?alt=media) button opens a Cardholder Selection pop-up that displays the cardholders that fit the selection criteria.

     <img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-8e0625767e947142f7c5cf8e2a9e8f9b69d889cc%2Fbulkchange_choldselectionpopup.png?alt=media" alt="" width="392">
   * Criteria in the **Bulk Random Selection** tab can be edited by clicking the ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-7c2828918c7cb681beaf46588ec4d5b23de9a63b%2Feditfilterbutton.png?alt=media) button, or removed by clicking the ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-7fa22e8d9be426ba5f5787abe105815d42650a55%2Fremovefilterbutton.png?alt=media) button.
7. Configure the remaining parameters as required.

   **Note:** The following parameters inform the selection decision (i.e. whether to select or not) each time a Cardholder is subjected to Bulk Random Selection. To see which parameters take priority over others, refer to the **Bulk Random Selection Rule Priority** section at the end of the [Bulk Random Selection](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/random-selection/bulk-random-selection-items.md) chapter topic.

   <table><thead><tr><th width="150">Parameter</th><th>Description</th></tr></thead><tbody><tr><td>Cardholder Probability of Selection</td><td>Each eligible Cardholder’s probability of being selected. Meaning, for each Cardholder that could be selected, this is the likeliness of them being selected.<br>This is <em>not</em> a percentage of Cardholders that will be selected.<br><br><strong>Note:</strong> Operators can override this setting when they run the Bulk Random Selection.</td></tr><tr><td>Set Competency Upon Selection</td><td>If set, when a Cardholder is selected by this Bulk Random Selection, the Cardholder's Competency (as nominated in the configuration) is either expired or disabled, and an event is raised.<br>Competencies can be used to deny Cardholder access to specific areas until the Cardholder has been tested (e.g. Drug &#x26; Alcohol).</td></tr><tr><td>Per-Cardholder Selection Limit</td><td>The maximum number of times each individual Cardholder can be selected within a specified period of time.<br>To limit the maximum number of selections for any given Cardholder within a specific period of time, select the <strong>Per-Cardholder Selection Limit</strong> check box, and set the maximum <strong>Number of Selections</strong> (valid range = 1-9999, default = 3) a Cardholder can have within the <strong>Duration for Selections</strong> (valid range = 0-999 Days, 0-23 Hours, default = 30 Days, 0 Hours).<br>When this Bulk Random Selection is run, a Cardholder is only eligible for selection if they have had less than the specified ‘Number of Selections’ in the past ‘Duration for Selections’ period.</td></tr><tr><td>Per-Run Total Cardholder Selection Limit</td><td>The maximum total number of selections that may occur across all Cardholders in one run of the Bulk Random Selection.<br>To limit the maximum number of Cardholder selections in a run, select the <strong>Per-Run Total Cardholder Selection Limit</strong> check box, and set the maximum <strong>Number of Selections</strong> (valid range = 1-9999, default = 10) across all Cardholders.<br>Once a run has selected the maximum number of Cardholders, it stops selecting Cardholders and completes.<br><br><strong>Note:</strong> Operators can override this setting when they run the Bulk Random Selection.</td></tr><tr><td>Periodic Total Cardholder Selection Limit</td><td>The maximum total number of selections that may occur across all Cardholders within a specified period of time.<br>To limit the maximum number of Cardholder selections within a specific period of time, select the <strong>Periodic Total Cardholder Selection Limit</strong> check box, and set the maximum <strong>Number of Selections</strong> (valid range = 1-9999, default = 100) across all Cardholders within the <strong>Duration for Selections</strong> (valid range = 0-999 Days, 0-23 Hours, default = 7 Days, 0 Hours).<br>When this Bulk Random Selection is run, if the number of selections that have ocurred in the past ‘Duration for Selections’ period are equal to or greater than the ‘Number of Selections’, no Cardholders are selected.</td></tr></tbody></table>

### Configuring the Overdue Arrivals tab

1. Click the **Overdue Arrivals** tab.

   On this tab you can configure alarms to be raised if a Cardholder does not enter one of your chosen Access Zone(s) after being selected by this Bulk Random Selection item. You can configure how much time they have before an alarm is raised.

   For example, you may require Cardholders to access a clinic within one hour of being randomly selected for medical testing. Otherwise, a Random Selection Overdue Arrival event will be raised.
2. Select the **Create events if cardholder does not...** check box.
3. Click the ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-91b1837bb0a2aeffc6ccef3863831c12a6418018%2F41090.png?alt=media) button to add the Access Zones that Cardholders must access after being selected. Entering one of these Access Zones will stop further alarms being raised.

   The Select Access Zones window displays, listing the selectable Access Zones.
4. Select the checkbox(es) of the required Access Zone(s), then click the **Add Selection** button.

   **Note:** You can add a maximum of 20 Access Zones for Overdue Arrivals per Bulk Random Selection item.
5. Click the ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-91b1837bb0a2aeffc6ccef3863831c12a6418018%2F41090.png?alt=media) button to add a Time Period.

   The Create Time Period window displays.

   **Notes:**

   * Time Periods define how much time will pass after a Cardholder is selected before an alarm is raised (note that alarms are not raised if the Cardholder accesses one of the selected Access Zone(s) before any Time Period has elapsed).
   * Network and server outages can delay the processing of Cardholder access events, causing Overdue Alarms to be raised even after a Cardholder has accessed one of the selected Access Zone(s).
   * Up to five Time Periods can be added, so alarms can be raised at several times until the Cardholder accesses one of the selected Access Zone(s).
6. Enter an amount of time for this Time Period, then click **OK**.

### Configuring the Action Plans/Alarm Instructions tab

1. Click the **Action Plans/Alarm Instructions** tab.
2. To configure the Action Plan or Alarm Instructions, refer to the topic [Event Action Plans and Alarm Instructions for a Macro](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/macros/event-action-plans-and-alarm-instructions-for-a-macro.md) for the procedure.

### Configuring the History / Notes tab

1. Click the **History / Notes** tab, and configure as required.
2. Click the **Save** button to apply your changes.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/random-selection/bulk-random-selection-items/creating-a-bulk-random-selection-item.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
