As an OpenIDM Administrator I would like the scheduled items created from the Admin UI to be preserved as part of the project configuration so that they can be managed similarly to other project details during the deployment lifetime.
Presently, when the Admin UI defines various types of scheduled tasks (livesync for connectors, recon for mappings, etc...) all of these schedules are created directly on the scheduler service, rather than on the configuration service. As a result, these schedules are only defined in the currently-running repository; they do not have corresponding entries in the project configuration.
Administrators which are carefully enforcing change-management will be using the Admin UI to help build project configuration during the development phase. They will need to capture all output from the Admin UI in the form of conf files which can be tracked, imaged, and deployed. Since schedules are an important part of that development effort, the schedule configuration which the Admin UI produces should be included in those project files.