Name
Start-JS7Order
SYNOPSIS
Starts existing orders the JS7 Controller.
SYNTAX
Start-JS7Order [-OrderId] <String> [[-Arguments] <Hashtable>] [[-At] <String>] [[-AtDate] <DateTime>] [[-Timezone] <String>] [[-State] <String>] [[-EndState] <String>] [[-AuditComment] <String>] [[-AuditTimeSpent] <Int32>] [[-AuditTicketLink] <Uri>] [<CommonParameters>]
DESCRIPTION
Start existing orders for the JS7 Controller and optionally adjust the start time and arguments.
PARAMETERS
OrderId
-OrderId <String>
Specifies the identifier of the order.
Required? | true |
Position? | 1 |
Default value | |
Accept pipeline input? | true (ByPropertyName) |
Accept wildcard characters? | false |
Arguments
-Arguments <Hashtable>
Specifies the arguments for the order. Arguments are created from a hashmap,
i.e. a list of names and values.
Example:
$orderArgs = @{ 'arg1' = 'value1'; 'arg2' = 'value2' }
Required? | false |
Position? | 2 |
Default value | |
Accept pipeline input? | true (ByPropertyName) |
Accept wildcard characters? | false |
At
-At <String>
Specifies the point in time when the order should start. Values are added like this:
* now
** specifies that the order should start immediately
* now+1800
** specifies that the order should start with a delay of 1800 seconds, i.e. 30 minutes later.
* yyyy-mm-dd HH:MM[:SS]
** specifies that the order should start at the specified point in time.
Required? | false |
Position? | 3 |
Default value | now |
Accept pipeline input? | true (ByPropertyName) |
Accept wildcard characters? | false |
AtDate
-AtDate <DateTime>
Specifies the date when the order should start. The time zone is used from the date provided.
Required? | false |
Position? | 4 |
Default value | |
Accept pipeline input? | true (ByPropertyName) |
Accept wildcard characters? | false |
Timezone
-Timezone <String>
Specifies the time zone to be considered for the start time that is indicated with the -At argument.
Without this argument the time zone of the JS7 Controller is assumed.
This argument should be used if the JS7 Controller runs in a time zone different to the environment
that makes use of this cmdlet.
Find the list of time zone names from https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
Required? | false |
Position? | 5 |
Default value | |
Accept pipeline input? | true (ByPropertyName) |
Accept wildcard characters? | false |
State
-State <String>
Specifies that the order should enter the workflow at the workflow node that
is assigend the specified state.
Required? | false |
Position? | 6 |
Default value | |
Accept pipeline input? | true (ByPropertyName) |
Accept wildcard characters? | false |
EndState
-EndState <String>
Specifies that the order should leave the workflow at the workflow node that
is assigend the specified state.
Required? | false |
Position? | 7 |
Default value | |
Accept pipeline input? | true (ByPropertyName) |
Accept wildcard characters? | false |
AuditComment
-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 enforece Audit Log comments for any interventions.
Required? | false |
Position? | 8 |
Default value | |
Accept pipeline input? | true (ByPropertyName) |
Accept wildcard characters? | false |
AuditTimeSpent
-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.
Required? | false |
Position? | 9 |
Default value | 0 |
Accept pipeline input? | true (ByPropertyName) |
Accept wildcard characters? | false |
AuditTicketLink
-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.
Required? | false |
Position? | 10 |
Default value | |
Accept pipeline input? | true (ByPropertyName) |
Accept wildcard characters? | false |
RELATED LINKS
EXAMPLES
-------------------------- EXAMPLE 1 --------------------------
PS > Start-JS7Order -OrderId "#2020-11-23#T158058928-myTest03"
Starts the order with order ID "#2020-11-23#T158058928-myTest03".
-------------------------- EXAMPLE 2 --------------------------
PS > Start-JS7Order -OrderId "#2020-11-23#T158058928-myTest03" -At "now+1800"
Starts the specified order for a start time 30 minutes (1800 seconds) from now.
-------------------------- EXAMPLE 3 --------------------------
PS > Start-JS7Order -OrderId "#2020-11-23#T158058928-myTest03" -At "2038-01-01 00:00:00" -Timezone "Europe/Berlin"
Starts the indicated order for a later date that is specified for the "Europe/Berlin" time zone.
-------------------------- EXAMPLE 4 --------------------------
PS > Start-JS7Order -OrderId "#2020-11-23#T158058928-myTest03" -At "now+3600" -Arguments @{'arg1' = 'value1'; 'arg2' = 'value2'}
Starts the order with the specified order ID. The order will start one hour later and will use the arguments from the specified hashmap.