Skip to content

docs(pipelines): notifications page + wizard updates (move-to-Sent, signer name, ZIP) - #162

Draft
nicolasiscoding wants to merge 3 commits into
developfrom
docs/pipelines-notification-delivery
Draft

docs(pipelines): notifications page + wizard updates (move-to-Sent, signer name, ZIP)#162
nicolasiscoding wants to merge 3 commits into
developfrom
docs/pipelines-notification-delivery

Conversation

@nicolasiscoding

Copy link
Copy Markdown
Member

What this does

Documents the new Pipelines capabilities and fixes one stale reference.

New page — Pipeline Notifications:

  • Default notification recipients: Signed & delivered and Failed lists.
  • Per-store notification overrides (the Notify chip and the Store notifications panel).
  • Customizing the completion email: subject, message, and attach-as-ZIP.

Updates to Creating an E-Signature Pipeline:

  • Step 2: the "Move files to a Sent folder" option.
  • Step 4: the signer-facing "Document name shown to signers" and "Message to signers" fields.
  • Step 5: the "Deliver as a single ZIP file" toggle, and a corrected notifications bullet that replaces the removed single "Error-alert email" field.
  • Cross-links to the new page; downstream sidebar positions bumped by one.

All screenshots were captured against the live product with the guidewright workflow (red boxes on the exact control) using neutral demo data.

Closes #161

🤖 Generated with Claude Code

https://claude.ai/code/session_01WGTz3v7aRSGCBi45DizjDv

…batch

Add a new Pipeline Notifications page covering default recipient lists
(Signed & delivered / Failed), per-store notification overrides, and
customizing the completion email (subject, message, attach-as-ZIP).

Update the Creating an E-Signature Pipeline walkthrough for the new
move-to-Sent toggle (Step 2), signer document name and message fields
(Step 4), and the deliver-as-ZIP toggle (Step 5). Replace the stale
single error-alert email bullet with the current notifications model and
cross-link the new page. Bump downstream sidebar positions to make room.

Closes #161
@nicolasiscoding nicolasiscoding self-assigned this Sep 14, 2026
… placement, step-label alignment

Address guidewright-review findings on the pipeline how-to:
- State the SharePoint connection prerequisite (Azure AD app) in Before You
  Begin and point back to it from Step 2 (was an unstated wall at Step 2).
- Add the required signature-placement sub-step to Step 3 with a link to
  Field Placement (the wizard blocks Next until a field is placed; the
  walkthrough previously omitted it entirely).
- Align step headings with the wizard rail (Sample/Source/Extract & Route/
  Sign/Deliver) and name the Create Pipeline button; clarify the default vs
  per-rule destination folder.
- Correct the Notifications page: per-store overrides live on Extract & Route,
  not Destination.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs(pipelines): notifications page + wizard updates (move-to-Sent, signer name, ZIP)

1 participant