codeunitPlatform, DevOps & Performanceofficial - Microsoftderived - from the source, no model text

Codeunit 1470 "Headlines Impl."

System Application · System.Visualization

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Codeunit 1439 "Headlines" (calls, 7 links)HeadlinesCodeunit 9026 "User Login Time Tracker" (calls)User Login Time Tracker

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

System Application · System.Visualization · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Access Internal
Permissions tabledata User = r

Procedures

  • Truncate(TextToTruncate: Text; MaxLength: Integer): Text
  • Emphasize(TextToEmphasize: Text): Text
  • GetHeadlineText(Qualifier: Text; Payload: Text; var ResultText: Text): Boolean
  • GetUserGreetingText(): Text
  • GetUserGreetingTextInternal(UserName: Text[80]; CurrentTimeOfDay: Time): Text
  • ShouldUserGreetingBeVisible(): Boolean
  • GetMaxQualifierLength(): Integer
  • GetMaxPayloadLength(): Integer

Plus 2 local procedures.

Calls

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

Called by

  • Codeunit 1439 “Headlines” (7 calls: Emphasize → Emphasize, GetHeadlineText → GetHeadlineText, GetMaxPayloadLength → GetMaxPayloadLength, …)

Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "codeunit", object_name: "Headlines Impl."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources