m/paliad
1
0
Fork 0
Code Issues 151 Pull Requests 4 Actions Packages Projects Releases Wiki Activity

Incoming Submission workflow + CFI/CoA proceeding lookup #17

New Issue
Open
opened 2026-05-08 13:53:14 +00:00 by mAi · 0 comments
mAi commented 2026-05-08 13:53:14 +00:00
Collaborator
Copy Link

Embed the Fristenrechner as one step inside a broader "Incoming Submission" work sequence.

Workflow

For each incoming submission (CMS / beA / Posteingang):

  1. Filing — record the doc in netDocuments (DMS), capture metadata.
  2. Determine deadline — Fristenrechner runs over the trigger event, produces deadline(s), saves to project.
  3. Communicate — notify the team about content + deadlines.

CFI / CoA proceeding lookup (slice)

When a CMS entry arrives, ask "which proceeding?" — match by case number (CFI / CoA), allow auto-create if not yet in Paliad. New "Add Project" workstep tied to the cascade. Slice can ship independently of the full workflow.

Likely sub-issues (file when slicing)

  • netDocuments DMS integration (auth, upload, metadata sync).
  • CFI / CoA case-number index + lookup.
  • Auto-create proceeding from cascade.
  • Team notification surface (uses existing Paliad notification infra).

Open scope questions

  • Is netDocuments integration a Paliad responsibility, or does this depend on existing HLC infra?
  • Where does the workflow live in navigation — new top-level route, or as a CTA from the Fristenrechner / Inbox?
  • Trust + audit story for auto-created proceedings (RLS, project visibility, who can create).

Context

t-paliad-157 items 9 + 11. Scope explicitly larger than just deadlines; m flagged "we can be more general when we batch this into issues."

Embed the Fristenrechner as one step inside a broader "Incoming Submission" work sequence. ## Workflow For each incoming submission (CMS / beA / Posteingang): 1. **Filing** — record the doc in netDocuments (DMS), capture metadata. 2. **Determine deadline** — Fristenrechner runs over the trigger event, produces deadline(s), saves to project. 3. **Communicate** — notify the team about content + deadlines. ## CFI / CoA proceeding lookup (slice) When a CMS entry arrives, ask "which proceeding?" — match by case number (CFI / CoA), allow auto-create if not yet in Paliad. New "Add Project" workstep tied to the cascade. Slice can ship independently of the full workflow. ## Likely sub-issues (file when slicing) - netDocuments DMS integration (auth, upload, metadata sync). - CFI / CoA case-number index + lookup. - Auto-create proceeding from cascade. - Team notification surface (uses existing Paliad notification infra). ## Open scope questions - Is netDocuments integration a Paliad responsibility, or does this depend on existing HLC infra? - Where does the workflow live in navigation — new top-level route, or as a CTA from the Fristenrechner / Inbox? - Trust + audit story for auto-created proceedings (RLS, project visibility, who can create). ## Context t-paliad-157 items 9 + 11. Scope explicitly larger than just deadlines; m flagged "we can be more general when we batch this into issues."
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
deferred
Parked — not pursuing now, may un-park later
done
Work completed by an agent; awaiting m to close
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
mAi m
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: m/paliad#17
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?