Solution Studio
The screen where you bring published capability versions together to create a solution on behalf of the platform. You also see listed solutions here.
For: Builder
What's on this screen
- Composed solutions, on the left: every solution version the platform has created. Choose one to open it on the right with its status (
draft,published), its latest certification record and whether it is listed; the address keeps the choice (?open=). - With no solution chosen, the right side shows Listed solutions: every solution placed on a surface, in the form
slug — status. If there are none yet, the screen says so. - New solution: the form where you enter the key, name and description and select components.
Creating a solution
- Fill in Key, Name and Description; all three are required.
- In the Components list, tick the capability versions to include in the package. Only published versions are listed, in the form
name vN. - Press Create solution. If it succeeds, the reference of the new solution version is shown and the version appears under Created solutions as
draft.
If you select no components you get a NO_COMPONENTS error, and if the key is already in use you get DUPLICATE_SOLUTION_KEY. If there is no published capability, a "Publish a capability first" warning appears instead of the form.
Who can do what
| Task | Permission key needed (in the platform scope) |
|---|---|
| See the screen | solution.read |
| Create a solution | solution.write |
| Run the certification check | solution.write |
| List the solution | listing.publish |
Under a version whose certification passed (passed or conditional) and that isn't listed yet, a Marketplace address (slug) field and a List button appear. The suggested slug is the solution's key; change it if it's already used on the surface.
Under a version with no certification, or one that didn't pass, there is a Certify button. The button runs a check: is every component published, and has every component declared its dependencies. If everything is in order, the certification becomes passed and the solution version is published; if not, it becomes failed and the gaps are listed component by component.
Keep in mind The certification is given by the check, not by a person: whoever presses the button only starts the check and is recorded as the one who ran it. If the check fails, close the gaps first (publish in Capability Studio or Declare no dependencies), then run it again.