Whenever an object is manually modified and stored, the system checks whether this object is currently being executed.
If so, a warning is displayed:
"ATTENTION: Modifications in object 'JOBP01_TEST' can affect running processes. Save anyway?"
In most cases, object modification actually influences ongoing executions. Nevertheless, this only applies to tasks that are not yet active but in the status "registered" or "waiting for precondition".
The listing below shows all modifications that show only little or no effects at all:
Object type |
Modified setting |
Effects |
---|---|---|
All executable objects |
Start type (Group) |
None Note: The script function GET_ATT supplies the name of the new group. |
Notification |
Responsible recipient, calendar and calendar keyword |
None |
Cockpit |
Content of the Cockpit tab |
None |
|
Properties of the display elements |
None |
Event |
Calendar tab |
None |
FileTransfer |
Use of wildcards |
None |
Job |
Host |
No effects when the job is in the status "Waiting for Host" |
Workflow |
Content of the Workflow tab |
None |
|
Properties of tasks |
Modifications only take effect when they were made via the Workflow Monitor |
RemoteTaskManager |
Filter specifications |
None |
Schedule |
Period and result evaluation |
None |
|
Content of the Schedule tab and properties of tasks |
Modifications take effect when they were made in the monitor. If they were made in the object, it is queried if the modifications should be reloaded at the next period turnaround. |
See also: