...
Assigning Run-time to the starter
The Job Stream Starter allows assigning a run-time to the Job Stream. Earlier it was not possible to run a Job Stream more than once without using the Reset Job Stream but now we can run the Job Stream more than once for e.g. every 5 minutes. From release 1.13.4 we don't need to specify the run-time to the first job of the Job Stream and then other jobs in the Job Streams start accordingly.
A Job Stream can even have more than one Starter and can have different run-time assigned to each starter.Assigning Parameters to the starter
The Job Starter can have a set of parameter i.e. we can assign parameters to the Job Streams Starter and that parameters will be available to each job in the Job Stream. The parameter can only be accessed by the job in the Job Stream instance which are is created by this Starter. For example, a parameter [name': 'value1'] will be available for each job of the Job Stream if it is assigned to the Starter. Without the Starter, we need to define the parameters for each job in the Job Stream.Starting more than 1 job at a specific time
The Job Stream Starter is assigned to the first of the Job Stream. If there is more than one job that starts the Job Stream then we need to assign Run-Time on each job differently. But with the Starter, we can assign the starter to jobs and all the jobs will be executed at the specified run-time.Specific Job Stream history for each run
The Job Stream when now executed with the Starter creates an instance of Job Stream called the session. Each created session has its own Session ID. The Job Stream now stores the history of each session, so from the release 1.13.4 Job Stream has a specific history for each run which was earlier not possible.Access to the event for one complete run of Job Stream
The Job Stream starter when creates a session then the events are created for this session. And the events can be accessed until the Job Stream execution is not completed i.e. we can access the event for the lifetime of one job stream run. Earlier the events for the Job Streams where only accessible for today i.e. the event cannot access with the expression <event_name> once the period gets completed.
Please refer to Scope of Events for reference.Accessing the events from another Job Stream
The event eventA, when created in a Job Stream jsstreamA, can be consumed by all the InConditions in all the Job Streams using the expression eventA till the release 1.13.3. To access the events from another Job Stream in release 1.13.4 we need to address the Job Stream i.e. from 1.13.4 when using the eventA created in jsstreamA need to be accessed with the expression jsstreamA.eventA.
...