1.4.1 Service statuses

Services in JP1/AO are classified by status. The status of a service at a given time depends on the type of service template from which the service was created, and the result of operations performed on the service.

Figure 1‒5: Service status transitions

The operations you can perform on a service also depend on its status. You can see the status of a service in the Services window.

Table 1‒4: List of service statuses
Status name	Description
Debug	A service created from a development service template. Only a service template developer (a user assigned the Admin or Develop role) can execute a service in this status. You can execute a service in Debug status to make sure that the service template you are debugging works correctly.
Test	A service created from a release service template. Only a user assigned the Admin, Develop, or Modify role can execute a service in this status. You use this status when testing the operation of the service. If the test is successful, you can change the status of the service to Released.
Released	A service created from a release template that has passed through Test status. All users can execute services in this status. Services in this status are used for real-world applications in the active environment.
Disabled	A service that was disabled while in Released status. Services in this status cannot be executed by any user. You might use this status when you want to prevent certain services from being executed.
Maintenance	A status used when performing maintenance of a released service. Only a user assigned the Admin, Develop, or Modify role can execute a service in this status. The purpose of this status is to temporarily prevent users in the Submit role from executing a released service during maintenance tasks such as changing the service settings.