Table of Contents

MediaOps Plan 1.5.4

Note

This version requires:

Tip

Installing MediaOps Live alongside MediaOps Plan allows you to orchestrate jobs and workflows and fully automate the setup and teardown processes.

Changes

Enhancements

Scheduling: Confirmation message adjusted for job with start time in the past [ID 45031]

In case MediaOps Live is not installed, a change has been implemented to the message shown when a job is confirmed that has its start time in the past. While previously this message mentioned that automated actions linked to the job start would be triggered immediately, now it will show The start time of this job is in the past. Confirming it will cause it to start running. If MediaOps Live is installed, the message will continue to mention that confirming the job will immediately trigger the automated actions linked to the job start.

Scheduling: Resource swapping blocked when mandatory parameters are missing for a running or confirmed job [ID 45036]

Up to now, it was always possible to swap a resource for a confirmed or running job. Now this will no longer be possible in case mandatory parameters are missing. Before being able to swap the resource, the user will have to provide the values for these parameters via the red hand icon in the swap panel. Only after all mandatory information has been provided, will the user be able to swap the resource.

Unhandled exceptions in scripts now immediately flushed to log files [ID 45086]

As soon as an unhandled exception is caught in a script, the logging of the script is now flushed to the log files, even while the script is still running. Previously, this only happened when the script was closed.

Fixes

Scheduling: Configuration UI incorrectly showed dropdown for running job [ID 45039]

In the window where you can view the configuration for a job and its nodes, it could occur that a dropdown was shown for the configuration section even when a job was already running, when no changes to the configuration should be possible.

Scheduling: Not possible to remove mandatory configuration added to node [ID 45048]

In the Scheduling app, you can use a filter to already create a configuration when adding or swapping nodes on your job. Up to now, in case the selected resource pool did not contain any configuration, you could add anything that is defined in the system. However, if you added mandatory configuration, you could no longer remove this.

Scheduling: Incorrect filter configuration applied when adding node to job [ID 45080]

When a node was added to a job from the Add Node panel, the settings defined in the Add Node panel were not taken into account for the node configuration. This issue has been resolved.

Scheduling: Empty filter window for Resource View when only configuration parameters were defined [ID 45083]

When you used the filter button on the Resource View page of the Scheduling app, but only configuration parameters were defined as orchestration settings on a resource pool, it could occur that the pop-up window only showed the Apply and Reset buttons without any filtering possibilities and without any further information. Now a pop-up message will be shown instead in such a case: "There are no capabilities or capacities available for filtering".

Missing linked pool validation in Plan API helpers [ID 45141]

The following validation related to resource pool links was missing in the Plan API helpers (Skyline.DataMiner.Dev.Utils.Solutions.MediaOps.Plan) and has now been added:

  • It should not be possible to add a deprecated resource pool as a linked resource pool.
  • Deprecating a resource pool should check if the pool is used as a linked pool.

The following issues related to linked resource pools have been resolved:

  • When a resource pool was edited in Resource Studio, all linked resource pools were removed in memory during initialization. When the user made other changes and click Save, the linked resource pools were removed completely.
  • When a new pool link was added, it was no longer possible to change to which pool it was linked.

Categorizing a resource pool did not update the number of items in the category in the Categories app [ID 45178]

In the Categories app, the number of items in each category is shown. However, when you assigned a category to a resource pool in the Resource Studio app, this number was not updated accordingly. This issue has been resolved.

Improve this page