A service goes through six steps and four portals. Each colour is a different person.
↻ Service Improvement loop: a live service is never edited. The organization starts a Service Improvement (a new version), and it goes through Configure → QA → Sign-off again. Portals already active stay active.
A service version is a change request (CR)
| Change request status | Tab in the SM portal | Who acts next |
|---|---|---|
IN_DEVELOPMENT |
In Development | Service manager configures and submits to QA |
IN_REDEVELOPMENT |
In Development | Service manager fixes the QA feedback and resubmits |
IN_QA |
In QA | QA reviewer approves or sends back (back = In Development again, with feedback) |
LIVE_READY |
Ready To Go Live | Organization admin signs off and chooses portals |
LIVE |
Live | Nobody can edit it. Changes need a Service Improvement |
Once the service is live, every application follows the workflow you configured. The workflow is a list of transitions: in state X, event Y moves the application to state Z and runs these actions.
| Item | Matches |
|---|---|
| Create New Service | Organization admin |
| Configure the form and workflow | Service manager |
| Approve Change Request Configurations | QA reviewer |
| Activate on Citizen Portal | IremboGov admin |
A service has been approved by QA. Where is it waiting?
C. QA approval moves the change request to Ready To Go Live. The organization admin signs it off and chooses the portals. Only then, for a new service on a marketplace, the IremboGov admin activates it.
← Welcome: become a certified Service Manager · Meet the demo service →