Introduction
Scheduling integrations at precise intervals significantly streamlines operations and ensures timely data processing. Among the various integration platforms, eZintegrations stands out for its robust capabilities in orchestrating seamless data workflows.
Imagine having a perfectly synchronized system where essential data moves effortlessly every 15 days, syncing vital information across platforms without any manual intervention. Achieving this level of automation is not just a possibility; it’s a reality with eZintegrations.
This article delves into the comprehensive process of setting up and executing integration bridges at a biweekly interval using eZintegrations. Whether you’re managing customer data, sales reports, or inventory updates, this guide will equip you with the knowledge to schedule and automate these tasks effortlessly.
Utilizing eZintegrations for Alternate Wednesday Scheduling:
To illustrate the practical application of eZintegrations’ scheduling feature, let’s consider a use case: scheduling an integration bridge to run every alternate Wednesday at 6 AM PST. This specific scenario highlights the platform’s versatility in catering to distinct scheduling needs.
To enable the scheduling of the bridge for alternate Wednesdays at 6 AM PST, we will incorporate the following set of operations alongside the user’s existing operations.
PYTHON Operation :
In the Python operation we use a Python code which retrieves the current week number and assigns “1” to the variable “decider” if the week is even; otherwise, it assigns “0”.
Below is the example of code that can be used.
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
Note : This Python code operates solely on even weeks, sending data to the target every alternate week (even weeks), excluding odd weeks. If your current week is odd, adjustments should be made within the filter operation.
FILTER Operation :
In the Filter operation, the condition is set to allow data passage only when the ‘decider’ is set to 1 (indicating an even week of the year). The condition setup is demonstrated below:
data['decider']=='1'
Note : If users wish to send data during odd weeks to the target, the condition can be modified to ‘data[‘decider’]==’0′.
APPEND Operation :
The Append operation enables the addition of a new key-value pair within your dataset, serving as a notification indicating successful data transmission to the target.
Here’s an example demonstrating the addition of a new key ‘success’ with the assigned value of ‘yes’
"success": "yes"
FILTER ENDS Operation :
The Filter Ends operation is utilized to conclude the filter block.
Schedule & Timezone (In Summary Tab)
Choose the Timer Type as ‘Schedule’ and enter the following Cron Job :
0 6 * * WED
In the Timezone Dropdown, opt for the timezone ‘America/Los_Angeles,’ indicating the execution of the integration in the PST timezone.
Conclusion
In harnessing the power of eZintegrations’ scheduling capabilities, we’ve navigated through the process of orchestrating biweekly integration executions. From configuring operations to modifying conditions based on weeks within the year, this guide empowers users to seamlessly schedule and manage data flows.
By understanding the nuances of conditional filtering, leveraging append operations for notifications, and efficiently closing filter blocks, users can optimize their integration workflows. Whether for even or odd week execution, eZintegrations offers a versatile platform for tailored scheduling needs.
