The plan status wizard displays status related details of execution plans on the local server and connected remote servers. Depending on the task, the status, and the configuration settings, plans can be downloaded, displayed, mailed, killed, and/or deleted by means of the wizard.
The wizard can be opened as follows: From the "Tools" menu, click "Plan Status". Alternatively, click the plan status icon in the tool bar.
If there are no active plans available, the wizard is not opened, but a popup message informs you so. This will be the case if no scan has ever been executed in the current environment, if all scans have been deleted, and/or if remote servers are disconnected.
If one or more plans are available, the wizard is opened.
You may select a server by means of the "Select Server" dropdown list if remote servers are connected and plans are available for more than one server. If a remote server is missing, it is possibly disconnected and/or no plan is available for the specific server.
Contents of the form is refreshed on a regular basis, typically every 70 seconds (or when another server is selected).
The wizard has two tabs, "Plans" and "Details". Details for a plan can be viewed by selecting a plan and clicking the "Details" tab. Depending on several factors, when highlighting a plan one or more buttons are activated as well. The parameters on the details tab, and the use of each button is explained more elaborately next.
The Details Tab
The "Details" tab shows parameters with corresponding values. The meaning of each parameter is described in the table below.
| Parameter | Description | ||
| User Profile | The user profile is the user id of the account through which you have logged on. Only tasks of the current user can be seen. | ||
| Service | The service is the type of task that was/is being/is planned to be executed. Values include the names of Diagnostic Scans, of specific question groups, and of custom scans. | ||
| Plan Name | When starting up a task, a task name was specified. The name is displayed here. | ||
| Sequence | An internal number ensuring uniqueness of internal file names. | ||
| Status | Each plan has a status. Status values include "Step waiting", "Step busy", "Execution finished", "Plan is being killed", and "Plan killed". | ||
| Short Description | The short description is related to the question (see next parameter) and especially has relevance when the status is "Step waiting" or "Step busy". If the status is "Step waiting", the description of the question is given that will be executed first when the waiting time is over. If the status is "Step busy", the description of the question is given that is being executed right now. | ||
| Question | This is the question number of the question related to the short description mentioned above. | ||
| Start Date/Time | The significance of this
field depends on the status. Most important cases are: Status "Step Waiting": The value corresponds to the moment in time that the wait state was started. Status "Step Busy": The value corresponds to the moment that the indicated question was started. |
||
| Current Date/Time | The current date and time of the server is displayed. Because the window is not constantly refreshed, the actual time may deviate. Goto the "Plans" tab and select any plan to refresh its execution details. | ||
| End Date/Time | The significance of this
field depends on the status. Most important cases are: Status "Step Waiting": The value corresponds to the moment in time that the wait state should terminate and the involved question starts executing. Status "Step Busy": The value corresponds to the moment the indicated question is guaranteed to complete since it is either ready before that time or the involved question will be forcebly terminated at the listed end date/time. Status "Execution finished": The value corresponds to the moment the plan was ready executing. |
||
The buttons
The meaning of each button is described in the table below.
| Button | Description | ||
| Download (or Save) | If the selected task is
one of the OnePoint Diagnostics Services,
and the status is "Execution finished" or "Plan
killed", the "Download" button becomes active. Upon
clicking "Download", personal details need to be entered or
verified (mandatory step). After submitting the required information,
the scan output file can be downloaded from the server to the client.
Subsequent to using the download option, when you close the "Plan
Status" window, the output is deleted from the server to save
space. Therefore treat the downloaded file as your single copy.
If the selected task is System Viewer, and the status is "Execution finished" or "Plan killed", the "Save" button becomes active. Click "Save" to save the System View output on the server, allowing multiple use of the "Display" button. The output will need to be deleted manually as soon as it is no longer of interest (to save disk space on the server). |
||
| Display | The "Display" button becomes active if the task is a System Viewer, Customized Scan, or Question Group and the status is "Execution finished" or "Plan killed". Subsequent to using the display option, when you close the "Plan Status" window, the output is deleted from the server to save space (unless it was saved previously). | ||
| The "Mail"
button can become active only if the correct mode has been selected (see
Mail Settings), the selected task is one
of the OnePoint Diagnostics Services,
and the status is "Execution finished". Upon clicking
"Mail", personal details need to be entered or verified
(mandatory step). If the mail wizard is opened, check the settings (this
only occurs if a value is missing, or if the mail settings mode was set
to "Prompt before mailing output"). After submitting the
required information, the scan output file is sent. Deletion will occur
in analogy to the behaviour described above for the "Download"
option. Note: If you use the mail option, the mechanism to check if the mail was sent and received is limited. Therefore the preferred method is to download the scan output and e-mail it by means of your e-mail client software. |
|||
| Kill Plan | A task with status "Step waiting" or "Step busy" can be killed (i.e. stopped). Upon killing a task, the status will briefly switch to "Plan is being killed", and then to "Plan killed". A killed task cannot be resumed. | ||
| Delete | To save space on the server, output of completed plans can be deleted manually. A delete is final and irrevocable. | ||