Summary

The Summary Page serves as the concluding stage in the integration service creation process. Following the successful configuration of the data target, users are prompted to meticulously provide and review essential details on the Summary Page. This meticulous step ensures a comprehensive overview before finalizing and submitting the integration bridge, marking the culmination of the integration setup process.

The following details are required to be entered in this step:

Integration Bridge Name:

Assign a fitting and descriptive name to the integration bridge within the designated space. This step is crucial as it not only helps in identifying the integration bridge accurately but also contributes to the organization and clarity of the overall integration process. Choose a name that succinctly reflects the purpose or nature of the integration, facilitating easy reference and management in future interactions with the integration service.

Description:
Provide a concise yet comprehensive description of the integration service within the allocated space. Craft a description that encapsulates the key functionalities, objectives, and any pertinent details about the integration, aiding both current and future users in understanding the purpose and scope of the service. A well-crafted description enhances documentation, streamlines communication, and fosters a clear understanding of the integration service's role and significance.

Schedule:
Within

the

The schedulingSchedule section,section userslets haveyou theset flexibilitywhen to tailor theyour integration service toruns. meetChoose theirbetween specificInterval requirements.(run Currently,every twoX distinctseconds) schedulingor typesSchedule are(cron-based available:timing). intervalInputs must be valid and schedule.non-negative Thiswhere versatilityapplicable.

empowers

Interval:

users

• Enter the run frequency in seconds (minimum 0).

Example: Set to 3600 to run the service every hour.

Schedule:

• Use a cron expression (format: minute hour day-of-month month day-of-week) to define timeframesprecise andtiming. recurrenceSelect patternsa thattime alignzone preciselyfor withglobal theiralignment.
operational needs.

Interval:Example: In the interval scheduling type, users are promptedSet to input0 the0 duration* in* seconds for which they intend to schedule their integration service. It's imperative to note that the input must be a non-negative value, ensuring that it cannot be less than 0.

Schedule: Within the scheduling feature, users enjoy a comprehensive array of options to finely tailor the execution of their integration service. They can select the specific year, month, date, and day of the week to precisely define when the service should run. Additionally, users can leverage preset options for hours, minutes, and seconds, offering a granular level of control over the scheduling parameters.
To accommodate global operations, users are empowered to choose from various timezones, ensuring that the integration service aligns seamlessly with diverse geographical locations and organizational requirements. This multifaceted scheduling functionality not only enhances user autonomy but also facilitates the optimization of the integration service to match the intricacies of different timeframes* and time zones.zone America/Los_Angeles to run daily at midnight Pacific Time.

Event Emails:
Within the designated space for event emails, users can configure the notification system. Here, users are required to enter the email address of the designated recipient who should receive triggered emails whenever the integration service is initiated or halted. This personalized notification mechanism ensures that the right individuals stay informed in real-time about crucial events related to the integration service lifecycle.