Skip to main content

# UpdateCheckSelectorInput

No description

    input UpdateCheckSelectorInput {
      id: ID!
      name: String
      description: String
      customerId: ID
      criteria: [SelectorCriterionInput!]
      raw: RawSelectorDataInput
      systemSelector: SystemSelectorAssignment
    }

### Fields​

#### `UpdateCheckSelectorInput.id` ● `ID!` non-null scalar​

To update a check selector an ID of an existing check selector is needed.

#### `UpdateCheckSelectorInput.name` ● `String` scalar​

A new name - if omitted the name property won't be touched. If null is set an error will be returned.

#### `UpdateCheckSelectorInput.description` ● `String` scalar​

A new description - if omitted the current description won't be changed.

#### `UpdateCheckSelectorInput.customerId` ● `ID` scalar​

To change the customer the following field can be used. Keep in mind that setting the customer to null is only possible if the current user is a super user. To set a different customer the current user needs to have SYSTEM_EDIT permission on both customers - the current one and the potential new one.

#### `UpdateCheckSelectorInput.criteria` ● `[SelectorCriterionInput!]` list input​

The typed criteria list to use to update the check selector. NOTE[mis/2022-06-23]: We could think about fields in the payload object to add/remove criteria from the list.

#### `UpdateCheckSelectorInput.raw` ● `RawSelectorDataInput` input​

If raw is used the typeCriteria field will be ignored and the selector will be create from the XML data.

#### `UpdateCheckSelectorInput.systemSelector` ● `SystemSelectorAssignment` input​

If you want to narrow the checks to a specific system selector you can use this field. If not set no selector will be assigned to the check selector and all systems will be considered.

### Member Of​

`updateCheckSelector` mutation