Should the deactivation of one or more validation steps be necessary after creation of the validation plan for an agent, the deactivate_steps() function will be helpful for that. This has the same effect as using the active = FALSE option (active is an argument in all validation functions) for the selected validation steps. Please note that this directly edits the validation step, wiping out any function that may have been defined for whether the step should be active or not.

## Usage

deactivate_steps(agent, i = NULL)

## Arguments

agent

An agent object of class ptblank_agent.

i

The validation step number, which is assigned to each validation step in the order of definition.

## Value

A ptblank_agent object.

## Function ID

9-6

For the opposite behavior, use the activate_steps() function.

Other Object Ops: activate_steps(), export_report(), remove_steps(), set_tbl(), x_read_disk(), x_write_disk()

## Examples

# Create an agent that has the
# small_table object as the
# target table, add a few
# validation steps, and then use
# interrogate()
agent_1 <-
create_agent(
tbl = small_table,
tbl_name = "small_table",
label = "An example."
) %>%
col_exists(columns = vars(date)) %>%
col_vals_regex(
columns = vars(b),
regex = "[0-9]-[a-z]{3}-[0-9]"
) %>%
interrogate()

# The second validation step is
# now being reconsidered and may
# be either phased out or improved
# upon; in the interim period it
# was decided that the step should
# be deactivated for now
agent_2 <-
agent_1 %>%
deactivate_steps(i = 2) %>%
interrogate()