Service Operations uses a number of back-end components (databases, calculations engine, and so forth) that need to be pre-installed and configured, at cloud level, prior to the instantiation of the application in any Devo domain. Once deployed, users do not need to worry about any additional steps or tasks related to infrastructure provisioning, as those tasks are also undertaken by the Devo internal teams.
Back-end components of Service Operations are deployed for Devo’s major servicing clouds, with rollout plans for private customer environments. Contact your Devo representative to understand the availability of Service Operations in your particular domain
Instantiating service operations in a domain
Service Operations is available by default in all domains in the serviced clouds through the Applications Gallery section.
Follow the next steps to deploy Service Operations in your domain:
In Devo’s main menu, click on Administration > Applications Gallery Note: Access to the administration section can be disabled for certain domains based upon your role. Contact your domain’s owner or administrators if you cannot access the Applications Gallery.
Locate Service Operations in the list of modules available for your domain. You might want to use the upper filtering buttons (All, Applications) or sorting buttons for quicker access.
Click on the Inactive button. Service Operations should appear now as Active.
Ensure Service Operations is associated with the right roles in the Devo platform. To do so, go to Devo’s main menu again and click on Administration > Roles.
On the left-hand side of the screen, select your role (Admin, for example) or the role you want Service Operations to be accessible from. Once selected, in the central part of the screen, click on the Applications tab.
Make sure that Service Operations is listed on the right part of the table, under Selected. If that is not the case, click on Service Operations under Available and click the right-pointing button between the two sections to move Service Operations under the Selected section.
Click on Apply changes to make them effective.
OPTIONAL: Repeat steps 5 to 7 to give other roles access to Service Operations.
At this point, you and/or other users in the platform should have access to Service Operations. To verify this, go back to Devo’s main menu and select Applications and check that Service Operations appears in the list.
Should Service Operations not appear in the list of Applications, log out of the Devo platform and log in again to ensure all changes in the roles and permissions configurations you just set are propagated immediately.