skip to main content
Corticon Studio: Quick Reference Guide : Objects on a Ruleflow canvas : Properties of Ruleflow objects on a Ruleflow canvas
 

Try Corticon Now

Properties of Ruleflow objects on a Ruleflow canvas

While the Ruleflow that manages the entire file and the current canvas has specific properties (see Ruleflow properties), the objects on the canvas have properties of their own in the context of the Ruleflow.
Common properties
The following properties and buttons are common to many of these objects.
*Name - The default name from the source file. This name can be changed to whatever will improve comprehension of its context and function on the canvas, with no impact on the source file. To change the name on the canvas, double-click the instance on the canvas and re-name it.
* - Color lets you choose from a color palette to override the default color that fills the object. See Adding colors to Ruleflow objects for more information. You could also use preferred general colors for all aspects of canvas objects, as discussed in Ruleflow preferences
* - For objects that are Corticon assets, lets you navigate to a different file of the object type that uses the same Vocabulary.
*Comments - Provides space for adding text annotations that are reflected in reports and on the canvas when the object is in focus. See Adding colors to Ruleflow objects for more information.
Object specific properties
*Rulesheet Activity - Rulesheet is a valid .ers file in the project. You can select a different file but you cannot change the path or the name of the original file.
*Ruleflow Activity - Ruleflow is valid .erf file in the project. You can select a different file but you cannot change the path or the name of the original file.
*Service Call-out - Service Name pulldown menu listing service call-outs that are loaded into the workspace. The currently loaded one displays the unmodifiable Description specified by its author.
*Branch Activity - Defines the branch structure by choosing an appropriate attribute, listing values on which to branch, and then the node for each branch path. See the section Conditional Branching in Ruleflows