Page History

...

Audit log information is returned from a JOC Cockpit instance.
Audit log entries can be selected by workflow path, order Order ID, folder etc.

The audit log information returned includes point in time, request, object etc. of a change.

The following REST Web Service API resources are used:

* /audit_log
* /audit_log/details

...

-Type <String[]>
Specifies the object types for which audit log entries should be returned. Multiyple Multiple values can be specifed specified by
use of commacommas, for example -Type WORKFLOW,SCHEDULE

* WORKFLOW
* JOBRESOURCE
* LOCK
* FILEORDERSOURCE
* NOTICEBOARD
* WORKINGDAYSCALENDAR
* NONWORKINGDAYSCALENDAR
* SCHEDULE
* INCLUDESCRIPT
* JOBTEMPLATE
* REPORT
* DOCUMENTATION
* ORDER

...

Category

-Category <String[]>
Specfies Specifies a category that further limits results of audit log entries.

* INVENTORY
* CONTROLLER
* DAILYPLAN
* DEPLOYMENT
* DOCUMENTATIONS
* CERTIFICATES
* IDENTITY

...

-DateFrom <DateTime>
Specifies the date starting from which audit log entries should be returned.
Consider that a UTC date has to be provided.

Default: Begin Beginning of the current day as a UTC date

...

-RelativeDateFrom <String>
Specifies a relative date starting from which audit log entries should be returned, e.g.

* -1s, -2s: one second ago, two seconds ago
* -1m, -2m: one minute ago, two minutes ago
* -1h, -2h: one hour ago, two hours ago
* -1d, -2d: one day ago, two days ago
* -1w, -2w: one week ago, two weeks ago
* -1M, -2M: one month ago, two months ago
* -1y, -2y: one year ago, two years ago

Optionally a time offset can be specified, e.g. -1d+02:00, as otherwise midnight UTC is assumed.
Alternatively a timezone offset can be added, e.g. by using -1d+TZ, that . This is calculated by the cmdlet
for the timezone that is specified with the -Timezone parameter.

This parameter takes precedence over the -DateFrom parameter.

...

-RelativeDateTo <String>
Specifies a relative date until which audit log entries should be returned, e.g.

* -1s, -2s: one second ago, two seconds ago
* -1m, -2m: one minute ago, two minutes ago
* -1h, -2h: one hour ago, two hours ago
* -1d, -2d: one day ago, two days ago
* -1w, -2w: one week ago, two weeks ago
* -1M, -2M: one month ago, two months ago
* -1y, -2y: one year ago, two years ago

Optionally a time offset can be specified, e.g. -1d+02:00, as otherwise midnight UTC is assumed.
Alternatively a timezone offset can be added, e.g. by using -1d+TZ, that is . This will be calculated by the cmdlet
for the timezone that is specified with the -Timezone parameter.

This parameter takes precedence over the -DateFrom parameter.

...

-Timezone <TimeZoneInfo>
Specifies the timezone to for which dates should be converted to from the history information.
A timezone can e.g. be specified like this:

Get-JS7OrderHistory JS7AuditLog -Timezone (Get-Timezone -Id 'GMT Standard Time')

All dates in JobScheduler JS7 are UTC and can be converted e.g. to the local time zone like this:

Get-JS7OrderHistory JS7AuditLog -Timezone (Get-Timezone)

Default: Dates are returned in UTC.

...

-TicketLink <String>
Limits results to entries that inlcude include the specified ticket link.

...

-Detailed <SwitchParameter>
Specifies that the original request should be returned that caused the change related to the respective audit log entry.
Consider Note that the -Detailed parameter can return large amounts of data and will slow down processing.

...