CAPCON Database Help

Connectivity to the EXTERNAL client databases (ยง7) โ€” the paying agency's own systems, reached over VPN.
โ† All apps

CAPCON Database

Connectivity to the EXTERNAL client databases (ยง7) โ€” the paying agency's own systems, reached over VPN.

Connectivity to the EXTERNAL client databases (ยง7) โ€” the paying agency's own systems, reached over VPN. It is the only component that reads from or writes to anything outside CAPCON.

What it does

Panels

Use the menu on the left; each panel has its own help topic.

Client Connections

Status: not written yet. This topic is a stub created with the project template. The panel's owner (see .github/CODEOWNERS) fills it in as the panel is built. Delete this quote block when you do.

What this panel is for

TODO โ€” one or two sentences: what question does this panel answer, and at what point in the CAP-control workflow does an operator open it?

The manifest describes it as: Configure and test connections to external client databases over VPN.

Before you start

TODO โ€” what must already be true. Most panels here need a project selected in the top bar, and the step before them to have completed.

How to use it

  1. TODO โ€” the first thing the operator does.
  2. TODO โ€” the second.
  3. TODO โ€” how they know it worked.

What it writes

TODO โ€” name the outputs exactly: which table, which CSV, which folder under the project tree. An operator reading this later needs to find the artefact without reading the code.

When it goes wrong

TODO โ€” the failure you actually hit while building this, and the check that distinguishes it from the next-most-likely cause. This section is the reason the help system exists; a list of buttons is not.

Retrieve Layers

Status: not written yet. This topic is a stub created with the project template. The panel's owner (see .github/CODEOWNERS) fills it in as the panel is built. Delete this quote block when you do.

What this panel is for

TODO โ€” one or two sentences: what question does this panel answer, and at what point in the CAP-control workflow does an operator open it?

The manifest describes it as: Retrieve updated vector and attribute layers from the client database.

Before you start

TODO โ€” what must already be true. Most panels here need a project selected in the top bar, and the step before them to have completed.

How to use it

  1. TODO โ€” the first thing the operator does.
  2. TODO โ€” the second.
  3. TODO โ€” how they know it worked.

What it writes

TODO โ€” name the outputs exactly: which table, which CSV, which folder under the project tree. An operator reading this later needs to find the artefact without reading the code.

When it goes wrong

TODO โ€” the failure you actually hit while building this, and the check that distinguishes it from the next-most-likely cause. This section is the reason the help system exists; a list of buttons is not.

Result Packages

Status: not written yet. This topic is a stub created with the project template. The panel's owner (see .github/CODEOWNERS) fills it in as the panel is built. Delete this quote block when you do.

What this panel is for

TODO โ€” one or two sentences: what question does this panel answer, and at what point in the CAP-control workflow does an operator open it?

The manifest describes it as: Assemble current results into delivery packages.

Before you start

TODO โ€” what must already be true. Most panels here need a project selected in the top bar, and the step before them to have completed.

How to use it

  1. TODO โ€” the first thing the operator does.
  2. TODO โ€” the second.
  3. TODO โ€” how they know it worked.

What it writes

TODO โ€” name the outputs exactly: which table, which CSV, which folder under the project tree. An operator reading this later needs to find the artefact without reading the code.

When it goes wrong

TODO โ€” the failure you actually hit while building this, and the check that distinguishes it from the next-most-likely cause. This section is the reason the help system exists; a list of buttons is not.

Deliver to Client

Status: not written yet. This topic is a stub created with the project template. The panel's owner (see .github/CODEOWNERS) fills it in as the panel is built. Delete this quote block when you do.

What this panel is for

TODO โ€” one or two sentences: what question does this panel answer, and at what point in the CAP-control workflow does an operator open it?

The manifest describes it as: Deliver result packages back to the client database.

Before you start

TODO โ€” what must already be true. Most panels here need a project selected in the top bar, and the step before them to have completed.

How to use it

  1. TODO โ€” the first thing the operator does.
  2. TODO โ€” the second.
  3. TODO โ€” how they know it worked.

What it writes

TODO โ€” name the outputs exactly: which table, which CSV, which folder under the project tree. An operator reading this later needs to find the artefact without reading the code.

When it goes wrong

TODO โ€” the failure you actually hit while building this, and the check that distinguishes it from the next-most-likely cause. This section is the reason the help system exists; a list of buttons is not.