Page History

...

Whether a Calendar is to be deployed on the Prod. system for the first time or whether an existing Calendar on the Prod system is to be updated.
Whether a Calendar is to be deployed on its own or whether it is to be deployed with the Orders information from the Int. system about the Orders or stand-alone Jobs which have been configured to use the Calender.

Note that Calendars are always exported with usage and folder information - i.e. with :

With information about the Orders or stand-alone Jobs which the Calender has been assigned to and the Run-time information (Period and Restrictions).
With the Calendar Path parameter ...
Status
colour Yellow
title Add Summary

"New" Deployment of a

...

Consider the situation where a new Calendar has been tested and is now to be deployed to a production environment.

The new Calendar can have a
on the Int. system has the same Path parameter as will be required on the Prod. system.

Calendar Export is carried out from the Resources / Calendars view of the JOC Cockpit:

The Calendar or Calendars to be exported are selected using the select boxes shown either in the Calendar Cards or at the left of the list of Calenders (as shown in the screenshot below).
Image Added
Selecting a first Calendar will cause the default Import Calendar button to be replaced with the Export Calendar button as shown in the next screenshot.
Image Added
Clicking the the Export Calendar button will open a standard browser file-saving menu that is then followed to save the Calendar(s) selected as a single .json file to the Int file system. This file can now be transferred to the Prod. file system.
In the configuration used for the screenshots the impexp_cal_sat Calender is assigned to two Orders on the Int. system and the impexp_cal_sun Calender is not assigned to any Order. Both Calenders are none-the-less exported in the .json file.

The ...

...