EventFlow Editor Annotations Tab

The EventFlow Editor's Annotations tab provides two features for the current EventFlow module:

Typecheck Warnings

Use this section to enable or disable categories of typecheck warnings from appearing as decoration markers on the EventFlow Editor canvas for this module, or as warning text in the Properties view. You can set any typecheck warning category as Warning or Ignore; by default, all categories are set as Warning. See Typecheck Warnings for an overview of where the warnings appear.

This tab affects only the current module. You can also enable and disable warnings for an entire project or for the Studio workspace as a whole:

Click the Project settings link in the upper right corner to open the StreamBase → Project Builder preference page for the current module's containing project.
Click the Workspace settings link to open the StreamBase Studio → Typechecking page in the Window → Preferences dialog.

The typecheck warning settings in all three locations have the following meanings:

Typecheck warning category	Description
Container connection endpoint missing	Warns when you have specified a container connection, but the container or a stream in the container at one end of the connection is not visible in the current module search path.
Constant expression is not static	Warns when you define a constant with an expression that produces different results when the module that contains the constant definition is loaded.
A field or variable name is hidden by another	Warns when you have named a function alias, dynamic variable, or named schema with the same name as built-in expression language function or as another alias, variable, or named schema elsewhere in the module search path.
An explicitly specified action is hidden by a field mapping	In a Query operator Properties view, Operation tab, Additional Expressions grid, warnings are issued when you specify an action (set or ignore) that contradicts the fields read from the associated Query Table. For example, if you add a Set row for the non-existing field `foo` with any expression, you receive the warning "`Field foo set but does not exist in table schema, so it will be dropped`". This warning can also appear when you attempt to set a value for the table's primary key field.
An error port or stream is left unconnected	An Input Stream, Error Input Stream, or an error port on any component was defined, but left without a downstream connection.
A Query Table will be accessed using a potentially slow plan	A proposed Query operation on its associated Query Table will require a full table scan or other time-consuming operation.
The application contains an unused import	A module imports schemas and/or constants from another module or interface, but then does not use any of them.
A conditional expression always evaluates to null	This operator contains an expression that does not return a result, which is not likely to be what you intended. Check all expressions defined for this operator.
Access to a deprecated feature	This warning appears under certain conditions, including: An expression in an Aggregate operator uses the deprecated stream qualifier `last.fieldname.` Use `input.fieldname` instead.

Module Annotations

Mark this module as hygienic by clearing the check box for the References to this module control:

Select the check box to mark this module as flexible:

See Hygienic Modules for more on hygienic versus flexible modules.