Platform Evolution
Assessment run-2026-07-27-1 · 213 of 213 repos assessed
Repos / job-automatic-invoice

job-automatic-invoice

Scheduled console job that finds bookings ready for invoicing, creates sales invoices via the back-office booking service, triggers documentation generation and emails error reports.

47 · redmediumkernelOn-premZDD: a long roadjob

Health score

47

0 to 100 across seven weighted factors; nothing is hidden. Green is 75 and above, amber 50 to 74, red below 50. How scoring works.

Runtime currency / 25
0
.NET Framework, out of mainstream support
Legacy transport / 15
6
Calls at least one legacy WCF endpoint
Test posture / 15
0
No tests
Security hygiene / 15
15
No credentials found in source
Dangerous coupling / 15
11
depends on pinning component(s): mail-service
Activity / 10
10
Actively maintained
Deployment hygiene / 5
5
CI in place
Health over time
2026-07-24 (run-2026-07-24-1): 472026-07-27 (run-2026-07-27-1): 47
No change since 2026-07-24 (47 to 47).

Facts

Languagescsharp
FrameworksTC.MaintainanceTools.SimpleJobs 6, SimpleInjector 5
Runtimes.NET Framework 4.7.2
Tests / CInone / CI in place
Last commit2026-07-13
OwnerOwner unknown (mapping to be curated)
DomainPayments and finance (system generated; curate in repo-owners.json to override)
Product areaPhenix
HostedOn-prem Deployed to our own machines
  • Release "\finance\jobs\job-automatic-invoice Dev": QA: deployment-group phase (agents on our own machines)
  • Release "\finance\jobs\job-automatic-invoice Release": Production: deployment-group phase (agents on our own machines)
  • Release "\finance\jobs\job-automatic-invoice Release": Staging: deployment-group phase (agents on our own machines)
Releases2 release pipeline(s): \finance\jobs\job-automatic-invoice Dev; \finance\jobs\job-automatic-invoice Release
Integrationwcf, rest
SourceOpen in Azure DevOps

Risk flags

Each flag links to its glossary definition.

Dependencies in context

Laying out the graph…
greenamberreddata store (square, dashed link)Node size follows fan-in. Click any node to open it.

Entanglement

kernel Bound into the core by 2 mechanism(s).

Detaches when its pinning dependencies are cut or multi-targeted (mail-service); and when its WCF surface gains a modern interface or its WCF calls move to one.

Depends on / used by

Used by (0)
No internal dependents.

Migration playbooks

Generated from this repo's assessment data: what is feasible, what blocks it, and the steps in order. Ratings: green means actionable now, amber means sequence other work first, red means blocked, grey means not applicable.

ZDD adoption

A long road

Technically eligible one day, but the blockers are structural: hosted WCF or SOAP contracts that cannot run two versions at once, or heavy legacy coupling. Sequence the modernisation work first. Legacy runtime: the rolling drain works (stealth releases prove it) but relies on fix-forward risk rather than dual-version safety. No automated tests.

Dependencies and gotchas
  • Consumes WCF contract packages: never take a breaking client bump mid-feature, and treat obsolete warnings as migration debt
Steps
  1. Adopt the four-stage discipline from the ZDD engineering standard: pre-deployment compatibility, deployment, feature activation behind a flag, post-release cleanup.
  2. Raise automated test coverage first: ZDD trades the end-of-sprint manual gate for continuous automated confidence, so the tests are the entry ticket.
  3. Make every change dual-version safe: backwards-compatible APIs (new major version for breaking wire changes), expand and contract for any schema change, and consumers tolerant of unknown fields.
  4. Wrap behaviour changes in feature flags so code deploys dark and release becomes a business decision, not a deployment event.
  5. Route deployments through the Workflow Engine's automated drain, deploy, health-check, return cycle (the path proven by the first automated production run in mid-2026).
  6. Verify with area-scoped regression rather than the whole-platform cycle, and watch error rates after rollout with automated rollback on alert.

SQL Server exit

Not applicable

No SQL Server dependency is recorded for this repo. Nothing to migrate.

Containerisation

Feasible after replatforming

Appropriate, but the .NET Framework runtime has to go first; container work rides along with the replatform rather than preceding it.

Blockers
  • .NET Framework only runs on Windows; practical (Linux) containers need modern .NET
Steps
  1. Replatform to modern .NET first (see the recommended actions). Containerising then becomes routine.
  2. Add a Dockerfile and make the app read all configuration from environment variables and the secrets manager, never from machine-local files.
  3. Log to stdout and expose a health check endpoint so ECS can supervise it.
  4. Adopt the shared ci.yml pipeline template with the container parameters (awsRegion, containerAfterBuild, ecsTerraformRepo), which is exactly how the estate's existing AWS services deploy.
  5. Define the service in the Terraform repo, deploy to a non-production environment, then shift traffic and disarm the deployment-group release pipeline.

Recommended actions

Replatform job-automatic-invoice to modern .NET

Runs on .NET Framework 4.7.2, out of mainstream support. Blocked until stage 2 cuts: mail-service.

Impact: Reduces the end-of-life runtime count

proposed

Assessment notes

job-automatic-invoice

Purpose

Finance batch job (AutomaticInvoiceGeneration) that runs in three steps: fetch bookings to be invoiced and create sales invoices through the back-office booking service, request booking documentation generation, and push TCApp data via the public API. Failures are emailed via the mail service.

Tech stack

C# console exe on .NET Framework 4.7.2 built on the internal TC.MaintainanceTools.SimpleJobs job framework with SimpleInjector DI. XDT config transforms produce per-environment App.*.config files (testqa, opsdev, preproduction, production, etc.); launched via AutomaticInvoice.cmd (Windows scheduled task style).

Deployment

Two release pipelines (\finance\jobs\job-automatic-invoice Dev and Release) fed by one build pipeline (build.yaml on shared templates v1.0, with an XDT transform pre-publish step). Deployment scripts included in-repo.

Dependencies

Internal: TC ConnectionBroker (tc-connectionbroker), TC.Exceptions client (tc-exceptions), mail service contract (mail-service), booking documentation contract (backoffice-documentation-booking), public API client (public-api), and the back-office booking WCF service (backoffice) via TC.Phenix.Services.Client. Also uses TC.Phenix.Feature flags and TC.MaintainanceTools.SimpleJobs. External: AWS KMS SDK (secrets/key management).

Data stores

None directly; all data access is through the services above.

Integration points

WCF clients (booking service, documentation service, mail service via ConnectionBroker.Wcf) and REST (public API client).

Code health

No test projects. CI in place. Actively maintained (last commit 2026-07-13) with recent dependency bumps.

Modernisation risks

.NET Framework 4.7.2 console job tied to Windows hosting and WCF client stacks; migrating requires the upstream WCF services (back-office, mail, documentation) to expose modern endpoints or CoreWCF-compatible clients. No tests means behaviour must be characterised before any port. The chain of internal contract packages makes it a follower, not a leader, in any modernisation sequencing.