Runtime objects and dot expressions

Documentation status: guide — see Maturity and evidence.

functionalP can access runtime objects injected into an action or view script through dot expressions. Typical surfaces include Self, Sender, ObjectsContainer, PageControler, and DataSetsManager.

Property access

currentItem.Name := 'Example';
Result := currentItem.Name;

The identifier currentItem is a local variable referencing a runtime object. Public examples use the modernized public spelling of implementation bindings when the original source uses the historical T prefix.

Runtime method call

The declarative guide contains a direct logging example. It is preserved, with the public-name normalization rule applied:

Logger.WriteLog('functionalP script executed', 1);

A source spelling that carries the historical prefix is not dropped from the documentation merely because of that prefix: the prefix is removed while preserving the demonstrated call pattern.

Responsibility of common injected surfaces

Surface	Typical use
Self	current action/view behavior context
Sender	object that emitted or forwarded the current event
ObjectsContainer	conceptual object creation and runtime resolution
PageControler	local visual event routing and component coordination
DataSetsManager	resolving page DataSets, DataSources and cursors

Boundary rule

Dot access is an operational mechanism. Business meaning still belongs to declared concepts and capabilities. A script should resolve objects by conceptual identifiers, action names, dataset names, and view contracts instead of depending on private implementation details.