Use the Costpoint Web Jobs table window screen to view the details of each Costpoint web job, including the application, submitting user ID, status, execution method, start and end date/time, detailed status, progress, company, cancelled by user ID, report name and status, action name, and whether the job is restartable.
Within this table window, two additional subtask links, Restartable Job Details and Scheduled Job History, are available to view additional job information:
Use the Restartable Job Details subtask to view the job sequence, step type, description, and start and end date/time details for each restartable job that failed or was cancelled by the user. This subtask will not display any information if the job is not restartable or if the job was completed successfully without any errors.
Use the Scheduled Job History subtask to view the status of all operations that are scheduled within the current job. The execution method must be "Process Server." If the current job is not submitted through the job server, this subtask will not display any information.
All users can monitor these screens whenever there is a need to view the details of the job server workload.
System administrators can purge status information stored in the W_APP_STATUS_INFO table whenever desired.
Since a new row is added to this table for each action and report executed on the server, this table can quickly become very large. |
These screens can be used to view the execution status of any job submitted to the server. These are the only screens in the current release of Costpoint web in which there is functionality for users to check on the status of jobs submitted asynchronously.
What is the difference between "synchronous" and "asynchronous" processing?
In Costpoint client/server, most functions are implemented synchronously, in which steps are performed in a specific order and only after the previous step has successfully completed. This means that you cannot execute another process or report on a real-time basis if another long-running process or report is currently in process (except in Report Preview mode). The solution for this limitation in Costpoint client/server is to schedule the execution of longer-running processes and reports on a Process server.
In Costpoint web, for most functions you can choose either a synchronous mode of execution (the default) or an asynchronous (batch mode). In a batch (asynchronous)mode, applications are unlocked almost immediately after submission of a report or process. This means that you can submit a request for another report or process (including closing the application and shutting down the PC) before the current job is complete.
Note: Some reports can only be executed synchronously in Costpoint web, as in a posting report, which must be successfully generated before the application will allow you to post. Executing such a report asynchronously adds little value, since you must still keep the application open and wait for the report to finish before posting. Action/report locking rules still apply. For example, if you begin a single user process or report asynchronously, you cannot initiate another process until the first one completes, even though the application is unlocked. |
Please refer to the following technical topics for more specific information:
Actions
Application Locking
Asynchronous Processing
Job Server vs. Process Server
Use the fields in this screen to view the details of each Costpoint web job, including the application, submitting user ID, status, execution method, start and end date/time, detailed status, progress, company, cancelled by user ID, report name and status, action name, and whether the job is restartable.
The application ID displays in this non-editable field.
The application name displays in this non-editable field.
You can click on the Notes icon at the end of the field, if necessary, to easily view extensive application name data without the need to use the Up arrow and Down arrow function keys within the field.
The submitting user ID displays in this non-editable field.
The job status ("All," "Active," "Completed, " "Failed," "Cancel Requested," or "User Cancelled") displays in this non-editable field.
The execution method ("All," "Asynchronous," "Process Server," and "Synchronous"" displays in this non-editable field.
Note: Although "API" and "Asynchronous API" also display in the drop-down box when you make your filter selections, these choices are not available in the current Costpoint web release. |
The date and time that the application started on the server displays in this non-editable field.
The date and time that the application ended on the server displays in this non-editable field.
The detailed status of the application displays in this non-editable field.
Examples of detailed status messages include the following:
"Processing complete."
"The process/report failed to start because another user was already running it."
"Processing completed with errors."
You can click on the Notes icon at the end of the field, if necessary, to easily view extensive detailed status data without the need to use the Up arrow and Down arrow function keys within the field.
The progress percentage towards completion (from the "Progress Meter" that monitors the real-time job completion on the screen) displays in this non-editable field.
The company ID displays in this non-editable field.
If the job was cancelled, the ID of the user who cancelled the job displays in this non-editable field.
The report name, as applicable, displays in this non-editable field.
You can click on the Notes icon at the end of the field, if necessary, to easily view extensive detailed report name data without the need to use the Up arrow and Down arrow function keys within the field.
The report status displays in this non-editable field.
Examples of status messages include the following:
"Processing complete."
"The process/report failed to start because another user was already running it."
"Processing completed with errors."
You can click on the Notes icon at the end of the field, if necessary, to easily view extensive detailed status data without the need to use the Up Arrow and Down Arrow function keys within the field.
The action name, as applicable, displays in this non-editable field.
You can click on the Notes icon at the end of the field, if necessary, to easily view extensive detailed report name data without the need to use the Up Arrow and Down Arrow function keys within the field.
If this job is restartable, "Y" displays in this non-editable field.
If this job is not restartable, "N" displays in this non-editable field.
Click on this pushbutton to purge the data displayed in the table window.
The purge process will delete ALL rows that have been loaded into the table window, whether visible in the first 6 rows or not. [In other words, all data for which the filter conditions are valid will be deleted from the database.] The purged data is not written to any system table.
System administrators can purge status information whenever desired.
Since a new row is added to this table for each action and report executed on the server, the W_APP_STATUS_INFO table can quickly become very large. |
* A red asterisk denotes a required field.
Click on this subtask link to open the Restartable Job Details subtask screen.
Click on this subtask link to open the Scheduled Job History subtask screen.
This screen accesses and displays data from the W_APP_STATUS_INFO (Web Application Status Information) table.