Setting Variable Values from Scheduled Pipeline Execution
- This functionality allows users to assign specific values to pipeline variables at the schedule level.
- When a pipeline runs through a schedule, the variable values defined in that schedule override the global variable values.
- This enables dynamic, schedule-specific executions without modifying the pipeline itself.
Functionality Details:
1. Accessing Variable Settings in Schedule
- Create a pipeline
- Navigate to add variables and add variables as below:
- On the Schedule Create/Update page, a new option is available to select workflow variables and set their values.
- You can configure values for multiple variables.
- By default when Add Variable checkbox is enabled, it shows all existing variables with their current values.
- All pipeline-level variables are displayed in the dropdown along with their current values.
- Each schedule maintains its own set of variable values.
2. Variable Values During Execution
- When a schedule triggers workflow execution, the variable values defined in that schedule are applied.
- Different schedules may define different values for the same variable; each schedule uses its own assigned values.
- If a variable value is not modified at the schedule level, the "current value" from the pipeline variable modal is used.
- Even if a pipeline fails during execution, variable values in the variable modal still get updated based on the triggered schedule.
3. Behavior on Schedule Update/Delete
- Updating a schedule does not reset previously saved variable values unless they are intentionally modified.
- If variable values are changed during schedule update, the new values are considered during the next execution.
- Schedule delete/update correctly removes or updates only the associated variable values.
4. Behavior When Variables Are Added, Updated, or Deleted
- Deleted variables are not shown in the Schedule Create/Update dropdown.
- Updated variable names are reflected properly in the schedule interface for both new and existing schedules.
- When variables are renamed/deleted/added at workflow level, a warning message appears:
“Some variables are added/updated/removed. May need to update the schedule.”
- If a variable is renamed and the schedule is not updated afterward, the execution will NOT use the old schedule value.
Instead, it will take the value from the current variable modal.
- When you update the displayed values in the Add Variable section on schedule modal, then it will be static and won't be affected by any changes in the variable value at variables modal.
5. Updating Variable Values After Execution
- After schedule execution, the “current value” of the variable in the variable modal is updated with the value used by that schedule.
6. Variable Behavior Across Multiple Schedules
- Example:
User sets var1 = 5 (pipeline-level variable modal).
Schedule1 sets var1 = 50.
Schedule2 sets var1 = 500.
Schedule3 sets var1 = 5000.
- If the user updates var1 at the variable modal (e.g., var1 = 10), the values inside other schedules (50, 500, 5000) remain unchanged.
- Schedules always retain their own values until they are edited manually.
7. Execution Behavior with Run Controls
- When Pipeline is executed manually using Run Control options, the system uses the latest current value from the variable modal.
- Schedule-specific values apply ONLY when the Pipeline is triggered by that schedule.
- Variables update in the variable modal even if variables are not used in any task.
8. Supported Variable Value Types
- This is applicable for all variable types including:
- Email
- URL
- Number
- Name
- Strings with special characters
9. Logging and Trace
- Run logs show variables in the format:
variables set: var1=value1, var2=value2, var3=value3
- Names and values are comma-separated.
10. Where Variables Are Usable
Variables set or updated through schedules and variable modal work correctly in:
- Reader filtering
- RubiPython
- RubiSQL
- RubiR
- If-Else task
- While task
- Expression task
- Filtering task
Summary:
- Schedule-level variable values override pipeline-level values during scheduled execution, with reference to values of values defined for variables in the executed schedule.
- Pipeline-level variable modal values are used when workflows are executed manually.
- Variable updates in schedules and modal remain independent unless explicitly changed.
- The system correctly handles add/update/delete of variables and ensures scheduled executions always work with the right values.
Related Articles
External Pipeline Execution
1.1 Overview This document outlines the steps required to execute the Pipeline using the Rubiscape API. The process involves obtaining a login token, preparing the necessary parameters, defining the API endpoint and request body, making the API call ...Multiple Execution
Rubiscape provides a feature that enables the multiple execution of a complete pipeline. This allows the entire pipeline to be executed multiple times, creating a new instance for each run. Each instance can be configured independently. For multiple ...Persistent Variable
Persistent variables are those variables that hold their last run value. It uses the Current Value as the true value for the next run. Hence, the Current Value changes in each run and gets updated each time. Persistent variables can be defined for ...Persistent Variable
Persistent variables are those variables that hold their last run value. It uses the Current Value as the true value for the next run. Hence, the Current Value changes in each run and gets updated each time. Persistent variables can be defined for ...Values
Values formatting option is available in the Cross Table widget. The table given below describes different fields present on Values formatting. Field Description Remark Header Font It allows you to change the appearance of the Header row. You can ...