- 5 minutes to read

Where Generated Articles Appear

New 7.12

Documentation only helps when people find it where they work. Articles from Generate Articles from BizTalk are linked to the things they describe, so architects find them on the Repository Model, operators in Monitor Views, and everyone on C4 diagrams.

Understanding How Articles Are Linked

flowchart LR IA["fa:fa-file-lines Integration Article"] -->|"Repository entities binding"| Int["fa:fa-sitemap Repository Integration
Services, Message Types, System"] Int -->|"Add Monitoring"| Res["fa:fa-lightbulb Monitoring Resources"] Res --> MV["fa:fa-display Monitor Views"] IA -->|"C4 nodes binding"| Node["fa:fa-diagram-project C4 node
Linked by BizTalk generation"] IA -.->|"computed when shown"| Hub["fa:fa-diagram-project Shared receive port node
Inferred"] style IA fill:#2678BD style Int fill:#3F827B style Res fill:#3F827B style MV fill:#E47528 style Node fill:#93d16d style Hub fill:#FFD525

An Integration Article (blue) reaches readers three ways: through its Repository Integration and the bound entities (teal), through Monitoring Resources in Monitor Views (orange), and on C4 diagram nodes, either stored by the run (green) or inferred when the diagram is shown (yellow, dashed). Which links are made is decided by the Binding options in the wizard; see Generate Articles from BizTalk.

Place Reader Needs
Integrations list and entity pages Architects, integration owners Repository entities binding
Monitor Views Operators Monitoring Resources binding (Add Monitoring)
C4 diagrams Everyone C4 nodes binding, or inference
Articles and Snippets lists Administrators, authors Nothing

What a Generated Document Contains

Wherever it appears, a generated document is more than a summary. This is the Building Block of the orchestration Lab.Orders.i0100_OrderFlow, generated with Orchestration design set to ODX as Mermaid and designer image. Every Integration Article whose routes pass through the orchestration includes it, so a reader of the Integration Article in a Monitor View scrolls straight into this design.

BizTalk designer image of the orchestration i0100_OrderFlow, from Receive_Order through Decide_Region, Loop_Settle, Scope_Process, Parallel_Fanout, and Listen_Confirmation to Decide_Size (7.12)
The designer image in the Article. Click it for full size.

Facts: where the orchestration runs, and its logical ports with what they are bound to:

Property Value
Application Lab.Orders
Assembly Lab.Orders
Host LabArticlesHost
Port Direction Bound to Activates
OrderIn Receive RP_i0100_Orders_File Order message
ConfirmIn Receive RP_i0100_Confirm_File No
ErpOut Send i0100_OrderFlow_ToErp No
ArchiveOut Send i0100_OrderFlow_ToArchive No
CopyOut Send i0100_OrderFlow_Copy No

Calls or starts: the orchestrations it calls or starts, here Call Lab.Orders.i0100_Called.

Orchestration Design: the shapes as a Mermaid flowchart read from the ODX, with shape names and no expression code: Receive and Send shapes, Decide and Listen branches, Loops, Scopes with their Catch and Compensation blocks, and Parallel actions. Below it is the designer image, as the BizTalk Monitoring Agent read it from the deployed assembly (right).

Generation Info: the generator, the BizTalk environment, a model hash, and the options of the run. Run the generation again with the same options to reproduce the document.

Option Value
Follow transport loopbacks No
Pipeline stages and components Yes
Pipeline and adapter configuration (redacted) Yes
Orchestration design ODX as Mermaid and designer image

To leave the designer details out, or to redact more, see Sensitive Data in Generated Articles. The options are set in Generate Articles from BizTalk.

Integrations List and Entity Pages

Each Integration Article is linked to its own Repository Integration, found or created by the Article's title. The Article badge on the Integrations list and the Articles card on the Integration's page show it. The page says which Article documents it, for example Documented by the BizTalk Integration Article …, and the card marks the Article Linked by a generator. The same applies to the Services, Message Types, System, and Endpoints the run binds. The Integration page also has Edit BizTalk routes and Refresh from BizTalk; see Document from the Repository.

Integration page saying which BizTalk Integration Article documents it, the Articles card with the Article Linked by a generator, and the Edit BizTalk routes and Refresh from BizTalk buttons (7.12)
The Articles card on a Repository Integration created by the run, with its generated Integration Article.

Monitor Views

Articles linked to Monitoring Resources, through the Services that Add Monitoring creates, open from those Resources in Monitor Views. Operators read the design next to the live state.

Monitor View row of a BizTalk Resource with the Article button next to Action (7.12)
The Article button on the Resource's row.

Monitor View with the generated Article of a BizTalk Resource open in the preview panel (7.12)
Click the Article button to read the generated Article next to the live state. The panel shows the start of the Integration Article; scroll for the rest, including the Building Blocks it includes. See What a Generated Document Contains.

C4 Diagrams

In the Details panel of a C4 diagram node, each Article in the Articles section shows its origin with a pill; hover over the pill for its full meaning:

Pill Tooltip and origin Stored?
— Linked by a user: a link someone made by hand ✅ Yes
auto Linked by BizTalk generation: a link the run made, with the C4 nodes binding ✅ Yes
inferred Computed when the diagram is shown ❌ No

An inferred Article appears where the facts say it belongs. For example, a shared hub receive port shows every Integration Article whose routes pass through it, on every diagram generated from the same BizTalk group. Pin an inferred Article to store it as a manual link. One Article is shown once, under its strongest origin.

C4 node Details panel with one Article marked auto and one marked inferred, with the pin button (7.12)
The Articles of a C4 node with their origin pills. Pin an inferred Article to keep it as a manual link.

The same Details panel next to the Container diagram the node belongs to (7.12)
The panel opens next to the diagram when you select a node.

Details panel of a node with no Articles, saying No articles linked (7.12)
A node without Articles says so. The panel lists only the node's own Articles; the diagram's Tags are edited in the diagram's edit dialog and shown on the Diagram Sets list.

Articles and Snippets Lists

The Articles list, and the Snippets list for Building Blocks, have two filters for generated documents:

  • Generated by: BizTalk, Shipped by Nodinite, or Not generated for hand-written documents.
  • Generation run: the documents one run wrote. Each run is listed with its date, the generator, and how many documents it created and changed. The run result's Show the Articles of this run and Show the Building Blocks of this run links open the list with this filter set.

The C4 Diagram Sets list has the same Generated by filter, and With Selected with Delete and Permanently Delete.

Articles list filtered on Generated by BizTalk and one Generation run (7.12)
The Articles list with the Generated by and Generation run filters set.

The Generation run filter open, listing runs with their date, BizTalk, and the number created and changed (7.12)
Pick the run whose documents you want to see.

Relationships and the dependency views answer which Articles include this Building Block?; see Reading Articles.

Next Steps