Page History

...

Submit-JS7DailyPlanOrder [[-OrderId] <String>] [[-WorkflowPath] <String>] [[-WorkflowFolder] <String>] [[-SchedulePath] <String>] [[-FolderScheduleFolder] <String>] [-Recursive] [[-ControllerId] <String>] [-Late] [[-DateFrom] <DateTime>] [[-DateTo] <DateTime>] [[-RelativeDateFrom] <String>] [[-RelativeDateTo] <String>] [[-AuditComment] <String>] [[-AuditTimeSpent] <Int32>] [[-AuditTicketLink] <Uri>] [<CommonParameters>]

...

-WorkflowPath <String>
Optionally specifies the path and name of a workflow for which daily plan orders should be submitted.

WorkflowFolder

-WorkflowFolder <String>
Optionally specifies the folder with workflows for which daily plan orders should be submitted.

...

-SchedulePath <String>
Optionally specifies the path and name of a schedule for which daily plan orders should be submitted.

...

ScheduleFolder

-Folder ScheduleFolder <String>
Optionally specifies the folder with workflows schedules for which daily plan orders should be submitted.

...

-Recursive <SwitchParameter>
When used with the -Folder parameter -WorkflowFolder or -ScheduleFolder parameters then any sub-folders of the specified folder will be looked up.

...

-ControllerId <String>
Specifies the Controller to which daily plan orders have been submitted and should be submitted.

Without this parameter daily plan orders are submitted to any Controllers that are deployed the
workflows that are indicated with the respective parameters.

Late

-Late <SwitchParameter>
Specifies that daily plan orders are submitted that are late or that started later than expected.

...

-DateFrom <DateTime>
Optionally specifies the date starting from which daily plan orders should be submitted.
Consider that a UTC date has to be provided.

Default: Begin of the current day as a UTC date

...

-DateTo <DateTime>
Optionally specifies the date until which daily plan orders should be submitted.
Consider that a UTC date has to be provided.

Default: End of the current day as a UTC date

...

-RelativeDateFrom <String>
Specifies a relative date starting from which daily plan orders should be submitted, e.g.

* -1d, -2d: one day ago, two days ago
* +1d, +2d: one day later, two days later
* -1w, -2w: one week ago, two weeks ago
* +1w, +2w: one week later, two weeks later
* -1M, -2M: one month ago, two months ago
* +1M, +2M: one month later, two months later
* -1y, -2y: one year ago, two years ago
* +1y, +2y: one year later, two years later

Optionally a time offset can be specified, e.g. -1d+02:00, as otherwise midnight UTC is assumed.

This parameter takes precedence over the -DateFrom parameter.

...

-RelativeDateTo <String>
Specifies a relative date until which daily plan orders should be submitted, e.g.

* -1d, -2d: one day ago, two days ago
* +1d, +2d: one day later, two days later
* -1w, -2w: one week ago, two weeks ago
* +1w, +2w: one week later, two weeks later
* -1M, -2M: one month ago, two months ago
* +1M, +2M: one month later, two months later
* -1y, -2y: one year ago, two years ago
* +1y, +2y: one year later, two years later

Optionally a time offset can be specified, e.g. -1d+02:00, as otherwise midnight UTC is assumed.

This parameter takes precedence over the -DateTo parameter.

...

-AuditComment <String>
Specifies a free text that indicates the reason for the current intervention, e.g. "business requirement", "maintenance window" etc.

The Audit Comment is visible from the Audit Log view of JOC Cockpit.
This parameter is not mandatory, however, JOC Cockpit can be configured to enforce Audit Log comments for any interventions.

...

-AuditTimeSpent <Int32>
Specifies the duration in minutes that the current intervention required.

This information is visible with the Audit Log view. It can be useful when integrated
with a ticket system that logs the time spent on interventions with JobScheduler.

...

-AuditTicketLink <Uri>
Specifies a URL to a ticket system that keeps track of any interventions performed for JobScheduler.

This information is visible with the Audit Log view of JOC Cockpit.
It can be useful when integrated with a ticket system that logs interventions with JobScheduler.

...