Screen reuse and parameter configuration

1. Choose a reuse method

Each template insertion creates an instance. Fill template parameters during authoring, use page variables for current-page state, and pass page parameters when opening another page.

Scroll horizontally to view the full table

• First use: create and publish a screen
• Input: from local draft to device parameters
• Table: from fixed arrays to live filtering
• Bit writes: from one button to reusable controls

2. Distinguish a Tag name from its value

A Tag is a Mingcedar data point. speedTag holds its name; ReadTagDouble reads its value. Replace PLC_LINE01.PUMP01.SPEED with a readable numeric Tag from your project.

Scroll horizontally to view the full table

1. Create a page, open MX Design → Scripts → Page Script, and enter the code below.
2. Insert a text shape. Open MX Design → Behaviors → Browse and drag Text → Script Text onto its component node. Double-click the new behavior, clear the default Setup Script, set Condition to true, and enter speedTag + " = " + String(speedNow) in Display Text. Save.
3. Save the PPT, export through MX Design → Export → Export HTML, and open the page in Mingcedar to inspect the displayed name and value.

var speedTag = "PLC_LINE01.PUMP01.SPEED";
var speedNow = ReadTagDouble(speedTag, 0);

Expected result speedNow is sampled when these lines run. For a live display, put the read in an evaluated behavior expression or table function. Declare the possible dynamic Tag names as shown in the lessons.

3. Variable syntax by field

Each row is independent. Define selectedTag in Page Script with a full Tag name of the required type. buildRows is the Table tutorial’s row-array function. Expression syntax differs by field.

Scroll horizontally to view the full table

Expected result Use = for the Input target field, pass variables directly to functions, and keep template placeholders inside JavaScript strings. Some fields only accept fixed values.

4. Convert numeric and Boolean template parameters

Use a new page for this example; no PLC data is required. LIMIT is a non-negative number and ENABLED is true or false. Template parameters substitute text, which must be converted before use.

Scroll horizontally to view the full table

1. Insert a text shape and add Text → Script Text. Replace the default Setup Script with the complete code below. Set Condition to true and Display Text to String(limit) + " / " + String(enabled), then save.
2. Select the text shape, open MX Design → Templates → Library, and click Save selection. Enter Parameter display in Template name, confirm LIMIT and ENABLED in Captured variables, then click Save.
3. After confirming the save, remove the original placeholder text shape from this page. Save selection saves to the library without removing the original. Hiding it or moving it to another slide in the same PPT does not exclude it from a full export.
4. Double-click the Parameter display card twice. Select each whole instance group, open MX Design → Templates → Edit Instance, enter values A and B below in Template variables, and save. Export and open the page. A should display 1500 / true and B should display 2200 / false.

var limitText = "<LIMIT>".trim();
var limit = Number(limitText);
if (!limitText || !Number.isFinite(limit) || limit < 0) {
  throw new Error("LIMIT must be a non-negative number");
}
var enabledText = "<ENABLED>".trim().toLowerCase();
if (enabledText !== "true" && enabledText !== "false") {
  throw new Error("ENABLED must be true or false");
}
var enabled = enabledText === "true";

5. Diagnose data display problems

1. Start with constants: use [["PUMP01", "1200 rpm"]] for Table Rows, Plain Input for typing, or true / false for the indicator condition. Confirm the control itself works.
2. Inspect the computed target: when adding Script Text, clear its default Setup Script and set Condition to true. Temporarily enter selectedTag or GetPageParameter("pump", "missing") in Display Text. A visible <PUMP> means substitution did not happen; the wrong device means selection or parameters are incorrect.
3. Connect the real Tag last: check its name, type, communication quality and user access. After a write, compare the value read back from the device.

Expected result Check control configuration, computed parameters and data connection in that order.