[Protected vars] Transformation Rule Card: protected test fields

[fvet]

Why do you need this change?

Partners who need to run extra logic when the user runs a test transform (for example persisting the test text via a table extension) currently cannot hook the built-in Test group on page Transformation Rule Card (1238). The TestText / ResultText are not available to page extensions in a supported way.

The practical workaround is to hide the standard Test group and re-implement it with duplicate fields and page variables, which duplicates UI, captions, tooltips, and behaviorÔÇöand risks drifting from the base app when Microsoft changes the page.

Describe the request

Describe

Current behavior

On page Transformation Rule Card (1238), the Test group contains test input, result output, and an update control (drill-down) that executes the transform flow.
That flow and page state are not extensible enough for partner scenarios:

• TestText / ResultText are not exposed for reuse by page extensions.

Because of this, partners that need to add post-transform behavior (for example logging test text) must hide the standard Test group and duplicate it in a page extension, which is brittle and hard to maintain.

Requested changes

1. Expose test variables as protected
   • In Transformation Rule Card (1238), expose TestText and ResultText as protected (and related members if needed).
   • This allows page extensions to interact with the same page state without recreating duplicate variables/UI.

Internal work item: AB#629745

[AleksandricMarko]

Hi @fvet,

This issue contains multiple distinct request types:

• Protected variable exposure on page 1238 Transformation Rule Card for TestText and ResultText
• Event request to add OnAfterUpdateTransformationTestResult after the transform flow

Please create separate issues for each type to ensure proper processing and tracking.

We'll automatically process each issue once they are created separately.

[fvet]

Split into new issue ( #29882 )

[AleksandricMarko]

✅ Analysis complete - approved for implementation

---

Implementation:

Expose the page test state on page 1238 "Transformation Rule Card" by moving TestText and ResultText from the regular var section into the existing protected var section.

Current code:

var
    TestText, ResultText : Text;
    UpdateResultLbl: Label 'Update';

protected var
    VisibleTransformationRuleGroups: List of [Enum "Transformation Rule Group"];
    IsDataFormatVisible, IsFindValueVisible, IsReplaceValueVisible, IsStartPositionVisible, IsEndPositionVisible, IsFieldLookupVisible, IsExtractFromDateVisible, IsRoundVisible : Boolean;

Proposed change:

var
    UpdateResultLbl: Label 'Update';

protected var
    TestText, ResultText : Text;
    VisibleTransformationRuleGroups: List of [Enum "Transformation Rule Group"];
    IsDataFormatVisible, IsFindValueVisible, IsReplaceValueVisible, IsStartPositionVisible, IsEndPositionVisible, IsFieldLookupVisible, IsExtractFromDateVisible, IsRoundVisible : Boolean;

---

File: TransformationRuleCard.Page.al