Self Service: what changed from OpCon Classic
This page maps OpCon Classic concepts to their OpCon Continuum equivalents. It is a conceptual mapping under review, and it deliberately does not compare the two products' platform or job-type breadth. Use it to translate what you already know — not as the basis for a migration plan. Confirm specifics with your Continuous contact.
What this solves
Both products let a business user trigger automation from a form. In OpCon Classic that was Self Service; in OpCon Continuum you build a Service Request (a form of typed inputs and the events that fire on submit) and deploy it to an environment, where it shows up in the Self Service portal. The idea is familiar, but the authoring is more structured, so it's worth seeing how it maps.
What you get. How Classic Self Service maps to OpCon Continuum Service Requests, and the path from building a request to a business user submitting it.
Related topics
- Create a service request (Builder)
- Submit a service request (Business User)
- Publish a self-service request for business users (Build Outcome)