Submission channels

A submission channel is the outbound destination a signed certificate is transmitted to. Each material has one or more submission channels, and each certificate picks the submission channel it will use. When you submit a certificate, DASH generates the output and sends it through this channel.

Before you start

• You need the Materials (Projects) permission to add or edit channels, and an active (non-trial) subscription. See Roles & permissions.
• Submission channels are configured inside a material — see Data channels overview.

The submission channel kinds

A submission channel is one of the four channel kinds:

• Email (CHANNEL-001) — the output is emailed to the recipient.
• API (CHANNEL-002) — the output is transmitted to a partner API, such as the GSK vendor API, Veeva Vault or SharePoint.
• DASH Manual (CHANNEL-004) — the internal, built-in channel. It is a no-op destination used as the fallback when no external submission channel is configured, so a submission never fails for the want of a channel.

1. Add a submission channel

1. Open the material and go to its Data Channels section.
2. In the submission group, add a channel.
3. Give it a name, choose its kind (Email or API), and enter its configuration and any credentials. See Enter credentials & test connectivity.
4. Save the channel.

Adding an outbound submission channel to a material

2. Choose the channel on a certificate

When you create or edit a certificate, the Certificate Data Channel field lists the material’s submission channels. DASH pre-selects the built-in DASH (Manual) channel if you have not chosen an external one. See Create a certificate.

How transmission works on submit

When you submit a signed certificate, DASH runs a background chain:

1. Generate XML — the output is rendered.
2. Transmit — the output is sent to the certificate’s submission channel (Email, API, or Manual).
3. Storage push — a copy is pushed to any storage channels (best-effort). See Storage channels.

You can follow this on the certificate record and the Channel Log. See Submit & track status.

Tip

Channels stay editable even after certificates have used them, and connection testing never blocks a submission — a test only records an advisory result. If transmission fails you can retry from the certificate. See Retry a failed certificate.

Related

• Data channels overview
• Storage channels
• Enter credentials & test connectivity
• Submit & track status
• Data channel troubleshooting