Framework Initialization

Framework Initialisation 

When your Job starts, the Framework will be initialised. The following sections describe the initialisation that will take place, for each type of Template Job.

Job: Template

The Framework is initialised when the top-level Job starts. This is you executable Job that is derived from Job: Template.

Initialisation consists of: –

  • Instantiating a Framework object
  • Parsing default File System directory paths, for File System Token Replacement
  • Testing if the Job was built using the current Framework version

Jobs: TemplateProcess, TemplateChild

The Framework is initialised when the top-level Job starts. This is you executable Job that is derived from Job: Template. Child Jobs make reference to the Framework object that was created.

Initialisation consists of: –

  • Ensuring that the Job has a Parent Job
  • Referencing the Parent’s Framework object
  • Testing if the Job was built with the current Framework version

Initialisation with Older Versions of the Framework

If a Job was built using an older version of the Framework, this fact will be reported. This is not an error. New releases of the Framework will be compatible with Jobs that were built using older versions. You may choose to upgrade your Jobs to later Framework versions, should you wish to take advantage of new features.