...
Event Consumed in a different master.
The scope of events between different master is also called as Global events. The events are accessible in multiple JobScheduler within the same database. Once the Global Event is created we can use it as an In Condition and Out Condition of the same or different JobScheduler masters. To automatically start one JobScheduler's Workflow(Job Stream) with the conditions of another JobScheduler master then we can use Global Events as an In and Out Conditions.
Refer to the article on Global Events for details.
Status subtle true colour Green title FEATURE AVAILABILITY STARTING FROM RELEASE 1.13.4
The global events can be accessed using the expression <global:event_name> if created today. If you want to use the events which are created before the period can be accessed using the condition e.g. global:event1[yesterday]. This condition evaluates to true if the global event was created yesterday.
Period for Event
.
Events that have a calculation of creation date.
The events created today are accessible with the <event_name> but the events which are not accessible and created before today are used with the calculation of creation date. In the In Condition of any Job Stream, the event can be accessed using the expression <event_name[date_for_creation]>.
What is Today and How to Configure it?
The default value for today is 00:00:00 to 24:00:00 UTC and you can configure The 24 hour period is now configurable according to the requirements and the working hours. Users can select the begin-time for the period. To set the begin-time of the period, edit the scheduler.xml file from the $SCHEDULER_DATA/config folder, and add the parameter sos.jobstream_period_begin for the start time of the period. If you didn't add the value for the parameter sos.jobstream_period_begin by default it takes 00:00:00 to 24:00:00 in UTC.
...
Note: Whenever expression <event[today]> is used in any In Condition and Out Condition it takes the period mention in the scheduler.xml.
The period referred to the time up to which the event is accessible using the expression <event_name> in the In Condition and Out Condition. The default value for the period is 00:00:00 to 24:00:00 UTC
How to access the events which are in a period
The events by default, when used the expression as <eventname><event_name>, search for the event in the period. If the event exists in the period then only it evaluates to true otherwise the conditions become false. So, the expression <eventname> is same as
<event[today]> and it searches The expression <event_name> searches for the event created in the current period.With release 1.13.4 the new object is added called session. When the expression <eventname> is used in a Job Stream and the if starter starts the job it creates a session. Now, this expression evaluates to true only if the event was earlier created by the same sessioncurrently available session of Job Stream.
The expression <event[today]> searches for the event created today in all available session of Job Stream.
How to access events which are not in a period
The events can be accessed using the In Conditions expressions if they are not in period. Some examples of the expressions are:
- event[today]: Search for the events created in the period.
- event1[yesterday]: Search for the events created yesterday.
- event1[month.day_of_month]: Search for the events created on the day of the month e.g event1[4.28]: search for the event created on 28'April.
- event1[yesterday-3]: The expression calculates the value 3 days before yesterday.
Note: If the two events are created with the same name in the Job Stream in different sessions and In Condition is used as event1[today] then it will search for an event in the latest available session of the Job Stream.