Connect an AI assistant
Your AI assistant can read this documentation directly, so it answers from the current content instead of guessing. Add one of the servers below to your client — they use the Model Context Protocol (MCP). Each one covers a different body of content, so add the one you need.
The catalog did not load. Refresh the page to try again.
Loading…
{{server.name}}
{{server.summary}}
{{server.documentCount.toLocaleString()}} pages Not published to this site
- Name
-
{{server.name}} - URL
-
{{mcpServerUrl(server.path)}}
| Tool | What it does |
|---|---|
{{tool.name}} |
{{part.text}}{{part.text}} |
How can we help?
Searching in {{docApp.searchFilterBySpecificBookTitle}}
Searching for:
{{docApp.searchResultFilteredItems.length}} results for:
{{docApp.currentResultsSearchText}}
in {{docApp.searchFilterBySpecificBookTitle}}
Found {{docApp.searchResponse.totalResultsAvailable}} matches. Showing the top {{docApp.searchResponse.results ? docApp.searchResponse.results.length : 0}}. Use a more specific search to further narrow down the results.
No documentation pages match this search, so all content types are shown.
Most matches are in {{docApp.searchDocTypeRescue.best.name}}.
There is no book with the ID "{{docApp.searchBookRescue.bid}}", so the book filter from this link was ignored and results from all books are shown.
You have an odd number of " characters in your search terms - each one needs closing with a matching " character!
-
{{resultItem.title}} {{resultItem.matchedBy === 'semantic' ? 'semantic' : (resultItem.matchedBy === 'both' ? 'keyword + semantic' : 'keyword')}}
{{resultItem.url}}
{{docApp.libraryHomeViewProduct.title || docApp.libraryHomeViewProduct.id}}
{{docApp.libraryHomeViewProduct.description}}
{{group.title || group.id}}
{{group.description}}
Description
Settings to define the devliery of the Report output
Properties
| Name | Type | Occurrence | Description |
|---|---|---|---|
jobId |
xs:int |
Optional | The Id of the Scheduled Job Associated with the Report if not specified a job will be created |
runStatus |
scheduleRunStatusType |
Optional | The job run status. Permissible values are disabled, running and expired |
mode |
scheduleType |
Required | The job mode. Permissible values are runOnce, runDaily, runMonthly, runEveryPeriod. |
timeZone |
xs:string |
Optional | Specify the timezone that you would like this schedule to use. If you do not specify any timezone, or set this empty, then UTC/GMT timezone is assumed. |
dayMask |
scheduleDayMaskType |
Optional | The scheduled job day of the week mask. |
monthMask |
scheduleMonthMaskType |
Optional | The scheduled job month mask. |
period |
xs:unsignedInt |
Optional | The scheduled job period. |
nextEvent |
xs:dateTime |
Optional | The next scheduled event. |
expireCount |
xs:integer |
Optional | The number of times to run the schedule job. |
application |
appNameType |
Optional | The application to associate this scheduled job with. |
reference |
xs:anyURI |
Optional | A reference used to identify scheduled job. For example, for report scheduling it could be (urn:sys:reporting:reportId) |
tag |
xs:anyURI |
Optional | A tag used to identify groups of scheduled jobs. For example, for report scheduling it could be (urn:xmlmc:reporting:reportRun) |
description |
xs:string |
Required | The scheduled job description. |
jobRunType |
scheduledJobRunType |
Required | The type of job to run on the scheduled event. |
jobInfo |
xs:string |
Required | The information needed to run the job. In the case of an xmlmc_api type, this would be the XML used to make the methodcall. The XML string can contain replace macros for {{identifier}}, the identifier can be any one of the following: - - {{nowDateTime}} - The current (UTC) date/time in ISO8601 YYYY-MM-DD HH:MM:SS format. - {{jobId}} - The identifier of the scheduled job |
- Version {{docApp.book.version}}
- Node {{docApp.node}} / {{docApp.build}}