Calendar Event enables you to specify the recurring execution of process flow between the specified dates in conjunction with a specified calendar.

You will find a pre-bundled calendar event (Outbound_Queued_Event) to manually resend the queued outbound including FA, if it is stuck in the queue. You can activate or trigger this event to run the stuck transactions by right-clicking the event and select Trigger Now option.

Creating a Calendar Event

Click Configure > EVENTS > Calendar Event.
Click Create Calendar Event.
Type the name and description of the new Calendar Event in the Name and Description fields respectively.
Click to select the date of which event will start triggering in the Event Start Date. The date must be in MM/DD/YYYY format.
Select the start time in the Time field in hh:mm format when the event will start triggering.
Click to select the date of which event will stop triggering in the Event Expiry Date. The date must be in MM/DD/YYYY format.
Select the stop time from the Time when the event will stop triggering.

Select the days on which event should fire from the Firing Days.

Days	Description
All Days	The event will fire on all days (Mon to Sun) of the week.
Business Days	The event will fire from Monday to Friday excluding holidays.
Week Days	The event will fire from Monday to Friday even if there are any holidays.

Business days can be configured by setting the value for the property org.quartz.scheduler.bCalendar. The following table explains what can be the default and possible values for this property.

Value	Specifies list of holidays of year
Default value	01/15/2007,02/19/2007,05/28/2007,07/4/2007,09/3/2007,10/8/2007,11/22/2007,12/25/2007
Possible value	Any date in mm/dd/yyyy format.
Value description	These days are assumed as holidays in Adeptia Connect calendar. If a Calendar Event is scheduled to be fired on Business Days, the process will not be fired on days specified in this property.

To configure this property:

Click Account > Settings.
Expand the Server Nodes Settings in the left panel.
Select the server node.
Click Edit.
Click to expand Services and then Business Calendar.
Update the value for the property org.quartz.scheduler.bCalendar as required.
Restart the Connect Server.

Define the frequency of execution in the Firing Schedule. For information about Firing Schedule, click Help or refer to Cron Expression.
- It is mandatory to define the first cron expression, if you have selected cron as a Trigger type. For example, if you have set a calender event to run every 5 minutes from Monday to Sunday, you can set the cron expression as "0 0/5 * ? * MON, TUE, WED, THU, FRI, SAT * ".
- You may make use of the second cron expression to define another condition or address a condition supplementary to the first one. For example, if you have set a calender event to run every 5 minutes from Monday to Sunday, but do not want the same event to run from 12 AM to 12 PM on Sundays, the second cron expression can be defined as "0 0/5 13-23? * SUN * ".
- The firing schedule you define in the second cron expression must not overlap the one defined in the first cron expression.
Expand Advanced Properties to view the advanced properties of an Calendar Event.
Type the email id in the Notification Receiver Email-ID(s) (comma separated) to receive error emails related to this Calendar event.
Select Trigger in Sequence check box to trigger the associated process flow in a sequential manner. If you do not select the Trigger in Sequence check box then the associated process flow will trigger concurrently.
If you want to enable misfire handling for your Calendar event then, select the Run Once option from the Action on Misfire Event field. If you do not wish to enable misfire handling for your file event then, select the Ignore Misfire option.

The Run Once option will run only one collective instance of all the misfires for a particular event. Whereas the Ignore Misfire option will not run a misfired event.
Select the Project from the Project field.
Click Save.

You may be interested in...

What's new

Best practices

Training guides

Frequently asked questions

Adeptia Connect APIs

Adeptia security report

Browser not supported