Overview
Scheduling integrations at precise intervals streamlines operational workflows and ensures consistent data processing. eZintegrations provides robust scheduling capabilities that enable users to automate data transfers without manual intervention.
This guide explains how to configure an Integration Bridge to run on a biweekly basis using conditional logic, filtering, and scheduling features within eZintegrations.
Introduction
Automated scheduling plays a critical role in maintaining synchronized systems across platforms. By executing integration workflows at fixed intervals, organizations can ensure timely updates of customer data, sales reports, and inventory records.
eZintegrations enables users to schedule workflows every 15 days or on specific alternating weekdays, allowing seamless and reliable automation.
When to Use
Biweekly scheduling is recommended in scenarios where data updates are required every alternate week.
- When synchronizing data on a fortnightly basis
- When processing reports every alternate week
- When reducing system load by limiting execution frequency
- When managing recurring operational workflows
- When implementing time-based data governance
How It Works
Biweekly execution is achieved using a combination of scheduling, conditional filtering, and custom operations.
- Schedule the Integration Bridge using cron expressions
- Determine the current week number using Python
- Apply conditional filters based on week parity
- Allow data to pass only on selected weeks
- Append status indicators to processed records
This approach ensures that data is transmitted only during designated weeks.
Utilizing eZintegrations for Alternate Wednesday Scheduling
This section demonstrates how to configure an Integration Bridge to run every alternate Wednesday at 6 AM PST.
The configuration uses Python, Filter, Append, and scheduling operations to enable controlled execution.
How to Configure
Python Operation
The Python operation determines whether the current week is even or odd and assigns a value to the variable decider.
If the week is even, the value is set to 1. Otherwise, it is set to 0.
import datetime current_date = datetime.date.today() current_week = current_date.isocalendar()[1] result = "1" if current_week % 2 == 0 else "0" pycode_data["decider"] = result
This logic enables data processing only during even-numbered weeks.
Note: To execute during odd weeks, the logic must be adjusted in the filter operation.
Filter Operation
The Filter operation allows data to pass only when the decider value is set to 1.
data['decider'] == '1'
This condition ensures that records are transmitted only during even weeks.
Note: To enable execution during odd weeks, modify the condition to:
data['decider'] == '0'
Append Operation
The Append operation adds a notification field to indicate successful data transmission.
Example configuration:
"success": "yes"
This field confirms that records were successfully processed and sent to the target.
Filter Ends Operation
The Filter Ends operation is used to close the filter block and complete conditional processing.
It ensures proper execution flow within the integration pipeline.
Schedule and Timezone Configuration
Schedule Settings (Summary Tab)
To schedule execution for alternate Wednesdays at 6 AM PST, configure the following cron expression.
0 6 * * WED
Set the Timer Type to Schedule and apply the above cron job.
Timezone Configuration
In the Timezone dropdown, select:
- America/Los_Angeles
This ensures execution at 6 AM Pacific Standard Time.
Troubleshooting
- Integration Runs Every Week: Verify filter condition and Python logic.
- No Data Sent: Check the value of the decider variable.
- Incorrect Execution Time: Confirm timezone configuration.
- Filter Not Working: Review conditional syntax.
- Append Not Applied: Validate Append operation placement.
Frequently Asked Questions
How does biweekly scheduling work in eZintegrations?
Biweekly scheduling uses cron-based execution combined with conditional logic to process data only during selected weeks.
Can I run integrations on odd weeks instead of even weeks?
Yes. Modify the filter condition to allow data when the decider value is set to 0.
Is cron scheduling mandatory for biweekly execution?
Yes. Cron expressions define the base execution frequency, while filters control biweekly behavior.
Why is the Python operation required?
The Python operation calculates the current week number and determines whether execution should occur.
Can I change the execution time?
Yes. Update the cron expression and timezone settings to match the desired schedule.
Notes
- Always test scheduling configurations before production deployment.
- Verify system time and timezone settings.
- Monitor execution logs regularly.
- Document scheduling rules for operational clarity.
- Update filter logic when business requirements change.
Conclusion
By leveraging eZintegrations’ scheduling, Python, filtering, and append capabilities, users can implement reliable biweekly execution workflows.
This approach enables precise control over integration timing, reduces manual effort, and ensures consistent data synchronization across platforms.
