Check Syntax
Once all executable Components are completed and connected,  check the accuracy of your work (the syntax check validates not only the connectivity of the Components but also the accuracy of all instructions):

• press the Check syntax/Edit Again toggle button

(the image on the button will change and the appropriate syntax validation message will appear in the Workspace window e.g. Missing operand over the object that contains the error, or No errors, if none are found)

• if an error is found, press the Check syntax/Edit Again toggle button to restore the Procedure into an editable state and reset the button image;
• repeat the Check syntax routine until No errors are indicated;
• shortly after flashing the No errors message, the Procedure Workspace will be restored into an editable state and reset the button's icon to Check syntax.

The Procedure can be saved (select Save menu item) at anytime even when the Procedure is incomplete (i.e. error messages are generated). This Save anyway option was introduced in order to allow developers to build Procedures in stages, if necessary.

Testing the Procedure
Once a Procedure is completed and syntactically correct, it can be tested before putting it into production.

• press the Test menu item or button .
• this causes the Test/trace window to be displayed. This window has a number of options:
  • Cancel button (terminates test mode),
  • Run button (runs through the entire Procedure without stopping),
  • Break button (will interrupt the Test in Run mode - select the desired "stop" Component, then press on the Break button, repeat if necessary, then press on the Run button),
  • Step button (steps through each phase of the Procedure, one executable Component at a time)
    • as the steps are executed, the Component currently under execution in the Procedure Workspace is framed with a green border,
    • halts at the end of each step and awaits the next press on the Step button before executing the next Component);
  • Trace switch (when set, displays the intermediate results as the test progresses through the Procedure)

Save the Procedure
Simply select the Save menu item - may be done before or after testing of the Procedure (upon receiving the Save command, Scribe transparently performs the syntax check. If errors exist, they will be identified and an Alert Panel will offer the option to Save anyway.

A syntactically correct saved Procedure is automatically placed "into production mode" i.e. ready to be run as a Report or Process. However, just because the syntax is correct does not guarantee that the Procedure performs as intended. Therefore, always test your Procedures.

Invalidated Procedures
Procedures can be invalidated as a result of making critical modifications to Print Templates or other Procedures (Functions, Reports or Processes) that this Procedure depends on.

Having invalidated Procedures does not necessarily mean that they are incapacitated as to their original purpose. Rather, the purpose of this feature is to force the Developer making changes to a Template to review all existing Procedures.

Invalidated Procedures are indicated in the Open Procedure window by a "broken checkmark" next to the Procedure name in addition to having the name text shown in bold. See the example in the Selector panel.

When an invalidated Procedure is loaded for editing:

• review Procedure as to the viability of its original intent;
• make modifications, if required; and,
• Save.

Functions in other Functions and Procedures
A completed Function can be imbedded in another Function or Procedure. In order to do so,

• drag the Function object from the Palette into the Workspace;
• select the appropriate Function from the Functions view of the Palette:
  • A single click will display the Description, if any in the Palette - a double-click will load the Function name into the Function box.
  • You can also drag-and-drop the Function's name from the Palette into the Function box in the Workspace.

This causes the Function component to expand and display all required Parameters and the Return value, if used. Each of the Parameter fields comes equipped with a Run-time button allowing the required values to be hard-coded or loaded at run-time (soft-coded). You may want to review the usage of the Run-time button.