Zero-touch autopilot

Zero-touch autopilot collapses the multi-step Publish flow into one step. Instead of importing a WSDL, then generating a service, then generating operations, then generating mappings, you point the platform at a WSDL and it produces a draft service + operations + full-field mappings in a single pass — and reports a readiness score per operation so you know exactly what (if anything) needs your attention before you publish.

It is the fast path for the common case; the step-by-step flow remains available when you want to drive each stage by hand.

---

What it does in one step

From a single WSDL input, zero-touch:

1. Imports and parses the WSDL — materializes the canonical per-operation request/response contract (see Import a WSDL), including the inferred backend endpoint, SOAP version, and auth hint.
2. Creates the draft service — with a suggested service key, name, and environment, and the inferred backend pre-filled.
3. Generates all operations — one per portType/operation, with inferred REST method/path.
4. Generates the deterministic full-field mappings — for every operation's full request and response tree (see How mapping works).

The result is a draft you review and publish — nothing goes live until you publish it.

---

The readiness score

Every operation comes back with a per-operation readiness grade, the same one the publish gate uses:

| Grade | What it means for you | |---|---| | AUTO_READY | Mapping is complete; publish as-is. | | AUTO_READY_WITH_WARNINGS | Publishable, but review the flagged edge case (e.g. an unusual XSD construct, MTOM/XOP or WS-Addressing capability note). | | MANUAL_REQUIRED | Needs attention before publish — resolve via a field override or deselect the operation. |

The score turns "did the autopilot get it right?" into a concrete, per-operation answer, so you only spend review time where the platform flagged genuine ambiguity — not re-checking the whole estate by hand.

---

After autopilot

1. Review the generated mappings, concentrating on operations graded AUTO_READY_WITH_WARNINGS or MANUAL_REQUIRED.
2. Adjust with field-level overrides and conversion options where needed.
3. Confirm the backend — endpoint, SOAP version, auth, timeout/retry — see Configure the backend.
4. Test with the SOAP application test, then publish. Activating a version makes an immutable mapping snapshot live, with rollback always available.

---

Next reads

• Onboarding overview
• Import a WSDL
• Publish & version a service
• How mapping works

---

All Specaria SOAP to REST docs