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
