Scenario

This topic shows how the HCL Universal Orchestrator policy-driven plan operates in a practical business scenario.

About this task

Company X offers a gifting service and uses the HCL Universal Orchestrator to schedule their gifts to be sent out to their subscribers on every official holiday every year.

In this scenario, the date is the 19th of December and gifts are scheduled to be sent out on the 25th of December and on the 1st of January.

Following an event of national relevance, a new holiday is officially instituted for the 20th of December. The customers adhering to the services of Company X are expecting a gift to be sent on every official holiday, even if the holiday has just been instituted, which means the HCL Universal Orchestrator plan used by Company X needs to be modified.

The user responsible for the plan at Company X needs to change the calendar that regulates when gifts are sent out, let’s call it “GIFTS_CAL”. Immediately, a new gift for the 20th of December has been scheduled to be sent out.

This is how the plan adapts to the last-minute change:

Procedure

  1. Editing the “GIFT_SENDOUT_JS” definition triggers a plan reconciliation for this specific job stream.
  2. All the planned instances of “GIFT_SENDOUT_JS” which are in certain status and are not edited manually by the user are erased.
  3. "GIFT_SENDOUT_JS” cycle of evaluation is re-triggered to re-create the job stream planned future instances.
  4. The instance of “GIFT_SENDOUT_JS” that must run on the 20th of December falls into the 24 hours activation window defined in the policy and is therefore activated.

Results

Gifts are now ready to be sent out in time and the new plan includes the 20th of December as a gifting date for the future.