4.15 Notes on intervening actions performed when editing services

While you are editing a service in the Service Definition (editing) window, another user might perform an action in relation to a service you are editing (such as editing, deleting, or submitting the service). This section describes the effect the action performed by the other user will have on the actions you perform.

The following table shows the results of intervening actions performed by other users:

Table 4‒8: Results of intervening actions when using the *Service Definition* (editing) window
No.	Intervening action	Result of intervening action
1	Submit service	Intervening user This user is able to submit the service. Any changes made by the original user do not apply to the service submitted by the intervening user. Original user This user is able to edit the service.
2	Edit service	Intervening user This user can edit and save the service. Original user When this user edits and saves the service, the settings entered by this user are applied to the service.
3	Delete service	Intervening user This user can delete the service. Original user This use cannot save the edited service.

The following figure shows how JP1/AO behaves when an intervening action is performed while you are using the Service Definition (editing) window:

Figure 4‒10: Behavior when an intervening action is performed while using the *Service Definition* (editing) window

If another user edits or submits a service that has been submitted for execution, any tasks that have already been generated from that service are unaffected. If another user attempts to delete the service, he or she will be unable to do so as long as tasks generated from that service remain in the tasks list.