Processing rejected and accepted assignments

You can use this rule to:
  • Resend rejected task suites for recompletion to other performers.

    If you rejected a task suite, you may want it to be completed by a different performer instead of the one whose response you rejected. To do this, you can increase the overlap for this task suite only. This is especially helpful if you have the overlap value set to 1.

  • Save money on re-completing task suites that you have already accepted.

    If you reviewed and accepted a task suite, it may not make sense for other users to complete it. To avoid this, you can reduce the overlap only for accepted task suites.

Example for a JSON block

Re-assign task suites that didn't pass non-automatic acceptance.

Copy the JSON object and add it to the pool parameters:

{
  "configs": [{
    "collector_config": {
      "type": "ASSIGNMENTS_ASSESSMENT"
    },
    "rules": [{
      "conditions": [{
          "key": "rejected_assignments_count",
          "operator": "GTE",
          "value": "1"
        },
        {
          "key": "assessment_event",
          "operator": "EQ",
          "value": "REJECT" 
        }
      ],
      "action": {
        "type": "CHANGE_OVERLAP",
        "parameters": {
          "delta": 1,
          "open_pool": true,
        }
      }
    }]
  }]
}

Keys

Key

Value

Data type

Required during creation

rules.conditions.key
Parameters that are checked in the condition:
  • pending_assignments_count — The number of task suites that are completed and awaiting review.

  • accepted_assignments_count — The number of task suites accepted after the review.

  • rejected_assignments_count — The number of task suites rejected after the review.

String

Yes

rules.conditions.value

The number of task suites with a specific status.

String

Yes

rules.conditions.key

Changing the task suite acceptance status.

String

No

rules.conditions.value

The value can be ACCEPT, ACCEPT_AFTER_REJECT, or REJECT (task suites get accepted, accepted after rejection, or rejected, respectively).

String

No

rules.action.type

CHANGE_OVERLAP — Change the overlap. For example, to re-assign a task suite to other performers or cancel the recompletion of accepted task suites.

String

Yes

rules.action.parameters.delta

The amount to increase the overlap by in the task suite.

Number

Yes

rules.action.parameters.open_pool
Determines whether to re-open a closed pool:
  • true — Open the pool after making changes, if it is closed.
  • false — Don't open the pool after making changes, if it is closed.

Boolean

No

Key

Value

Data type

Required during creation

rules.conditions.key
Parameters that are checked in the condition:
  • pending_assignments_count — The number of task suites that are completed and awaiting review.

  • accepted_assignments_count — The number of task suites accepted after the review.

  • rejected_assignments_count — The number of task suites rejected after the review.

String

Yes

rules.conditions.value

The number of task suites with a specific status.

String

Yes

rules.conditions.key

Changing the task suite acceptance status.

String

No

rules.conditions.value

The value can be ACCEPT, ACCEPT_AFTER_REJECT, or REJECT (task suites get accepted, accepted after rejection, or rejected, respectively).

String

No

rules.action.type

CHANGE_OVERLAP — Change the overlap. For example, to re-assign a task suite to other performers or cancel the recompletion of accepted task suites.

String

Yes

rules.action.parameters.delta

The amount to increase the overlap by in the task suite.

Number

Yes

rules.action.parameters.open_pool
Determines whether to re-open a closed pool:
  • true — Open the pool after making changes, if it is closed.
  • false — Don't open the pool after making changes, if it is closed.

Boolean

No