The user interface submits tasks to the Impact Management Services. On reception tasks are queued in a central location and then dispatched according to the priority of the running instances of the service. Undoing tasks has a higher priority than all others and they are guaranteed to be executed first. See Using the Undo Feature.
On task submission, the Impact Management Services acknowledge reception in a confirmation dialog displaying an allocated task number.
Dispatch and execution takes place in background and can be monitored using Show Task Status.
A task with many actions (many documents to be transformed) is always executed in parallel with the individual actions dispatched to all available instances of the service.
Impact Management Services stores logging data for each document that is transformed. The logs are available in the server log files and in the User Interface (Show Task Status). The number of messages in the logs is controlled by the Log4J configuration file (server logs) and during task submission (user logs). See Script Logging Levels.
Note: | For the server logs for Harvester and Transformer services, (files server_messages_HarvesterService.log and server_messages_TransformerService.log), the Log4J configuration file controls the number and formatting of messages. Whereas, for the user logs (accessed by double-clicking in EPM Workspace), the formatting is fixed. However, the user can change the number of messages. |