If certain validation steps need to be activated after the creation of the
validation plan for an agent, use the activate_steps()
function. This is
equivalent to using the active = TRUE
for the selected validation steps
(active
is an argument in all validation functions). This will replace any
function that may have been defined for the active
argument during creation
of the targeted validation steps.
Arguments
- agent
The pointblank agent object
obj:<ptblank_agent>
// requiredA pointblank agent object that is commonly created through the use of the
create_agent()
function.- i
A validation step number
scalar<integer>
// default:NULL
(optional
)The validation step number, which is assigned to each validation step in the order of definition. If
NULL
(the default) then step activation won't occur by index.
See also
For the opposite behavior, use the deactivate_steps()
function.
Other Object Ops:
deactivate_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 inactive
# validation steps, and then use
# `interrogate()`
agent_1 <-
create_agent(
tbl = small_table,
tbl_name = "small_table",
label = "An example."
) %>%
col_exists(
columns = date,
active = FALSE
) %>%
col_vals_regex(
columns = b,
regex = "[0-9]-[a-z]{3}-[0-9]{3}",
active = FALSE
) %>%
interrogate()
# In the above, the data is
# not actually interrogated
# because the `active` setting
# was `FALSE` in all steps; we
# can selectively change this
# with `activate_steps()`
agent_2 <-
agent_1 %>%
activate_steps(i = 1) %>%
interrogate()