Nodes in the graph always have a title, and can optionally contain a sub title. Various shapes are available. Flowcharts brings more shape options than Entity Relationship diagrams, but with less freedom to modify their contents.
Nodes in the graph always have a title, and can optionally contain free text or column data. Nodes with content can be opened (for example the Template node) and closed (for example the TemplateDocument node).
The type of the box.
Possible value | Description |
---|---|
Comment | A dashed and expandable box that also allows the column "BodyText" with longer descriptions. This box is not intended to be a step in a flow, but rather a way to include text comments to a flow chart. |
Decision | A diamond shape to indicate a decision. |
End | A rectangle with rounded corners to indicate the end of the flow. |
Input | A skewed box intended for input. |
Output | A skewed box intended for output. |
Process | A rectangle intended for process step. |
Start | A rectangle with rounded corners to indicate the start of the flow. |
Subroutine | A rectangle with double lines intended for a subprocess. |
Extra text to show in nodes of type 'Comment'. No other node types may use this column.
Whether the node starts expanded. Not used by nodes that do not have any content to show by expanding them. Only applicable for node types "comment".
Possible value | Description |
---|---|
Arrow | An arrow head. |
NULL | No decoration. |
Possible value | Description |
---|---|
Arrow | An arrow head. |
NULL | No decoration. |
Possible value | Description |
---|---|
Dash-Dot | |
Dash-Dot-Dot | |
Dashed | |
Dotted | |
Long-Dashed | |
Solid |
Made when the user has moved nodes or connection labels. This call will receive two temporary tables with the new coordinates.
CREATE TABLE #MovedNode
(
NodeId varchar(MAX) NOT NULL,
X int NOT NULL,
Y int NOT NULL,
)
CREATE TABLE #MovedConnectionLabel
(
ConnectionId varchar(MAX) NOT NULL,
X int NOT NULL,
Y int NOT NULL,
)
The component will not validate that the moved elements were locked by CanDrag = 0
. Validate in the SQL code if this is important. Please note that a positioned label will still be moved if both it's 'from' and 'to' node are moved in the same operation, regardless if it is locked or not.
Prompts the user with the specified text and the user may answer OK or cancel. If the user chooses OK the sql call will be rerun with the parameter @force set to 1.
Displays a user friendly message to the user.
This call will receive a temporary table with the nodes that changed their expand state. You can use this call, in combination with the IsExpanded column in the Get Graph call to preserve a user's node expansion state.
CREATE TABLE #ExpandedNode
(
NodeId varchar(MAX) NOT NULL,
IsExpanded bit NOT NULL
)
Any nodes that need to be updated because of the created connection. Usually you will not need to update any nodes.
The type of the box.
Possible value | Description |
---|---|
Comment | A dashed and expandable box that also allows the column "BodyText" with longer descriptions. This box is not intended to be a step in a flow, but rather a way to include text comments to a flow chart. |
Decision | A diamond shape to indicate a decision. |
End | A rectangle with rounded corners to indicate the end of the flow. |
Input | A skewed box intended for input. |
Output | A skewed box intended for output. |
Process | A rectangle intended for process step. |
Start | A rectangle with rounded corners to indicate the start of the flow. |
Subroutine | A rectangle with double lines intended for a subprocess. |
Extra text to show in nodes of type 'Comment'. No other node types may use this column.
Whether the node starts expanded. Not used by nodes that do not have any content to show by expanding them. Only applicable for node types "comment".
Node to attach these columns to. This node must not have used the BodyHtml or BodyText columns when it was declared. Multiple rows may refer to the same NodeId.
Column value to show in the node.
The connection's ID.
Node the connection goes from.
Node the connection goes to.
How the part where the connection touches the from-node is drawn.
Possible value | Description |
---|---|
Arrow | An arrow head. |
Crow | A crow's foot (to-many relationship). |
NULL | No decoration. |
How the part where the connection touches the to-node is drawn.
Possible value | Description |
---|---|
Arrow | An arrow head. |
Crow | A crow's foot (to-many relationship). |
NULL | No decoration. |
The connections color. A lighter shade of the color will be used as background if a Connection Label is used.
How the line is drawn.
Possible value | Description |
---|---|
Dash-Dot | |
Dash-Dot-Dot | |
Dashed | |
Dotted | |
Long-Dashed | |
Solid |
A single line tooltip. Use this feature with care as no visible cue will be shown that the tooltip exists.
A multi-line text label to show on the connection.
If the user is allowed to move the connection label.
The connection labels X coordinate, if set. The top left corner of the component is 0,0.
This setting has no effect on connections without labels.
The connection labels X coordinate, if set. The top left corner of the component is 0,0.
This setting has no effect on connections without labels.
Additional columns can be referenced by links of the "Graph connection link" type.
Displays a user friendly error message to the user. This blocks any forwarding for the user.
Displays a user friendly confirmation message to the user with a delete button as the confirm button. If the user chooses OK the SQL call will be rerun with the parameter @ButtonAction set to 'Delete'.
Displays a user friendly confirmation message to the user with a question style. If the user chooses OK the SQL call will be rerun with the parameter @ButtonAction set to 'Confirm'.
Displays a user friendly confirmation message to the user with a warning style. If the user chooses OK the SQL call will be rerun with the parameter @ButtonAction set to 'Confirm'.
Displays a user friendly info message to the user. When the user clicks OK the user is forwarded.
Displays a user friendly success message to the user. When the user clicks OK the user is forwarded.
The dialog alias of a predefined dialog to show the user. Must be the first column in the result set table. Use multiple result set tables to combine with other forwarding.
Use the menu item "Admin > Dialogs" to register new dialogs or find aliases for existing ones.
Any column without special meaning in the result set with the first column ADMIN_Dialog will be used to make replacements of placeholders in the message and title text.
Additional information to show the developer when using ADMIN_Dialog.
Alias of the menu group to show after execution (instead of former menu item). This value overrides any destination specified by the query string.
Displays a user friendly error message to the user.
If this column is anything but NULL the popup will be closed and the parent will be reloaded. Only select this column if the menu item is opened in a popup. Avoid using this feature if the opener is a newEdit as that may interrupt the user's ongoing input.
Changes the text of the Cancel button when used with ADMIN_Force, ADMIN_ConfirmWarning, ADMIN_ConfirmQuestion, ADMIN_ConfirmDelete.
Changes the text of the OK button when used with ADMIN_ErrorMessage, ADMIN_ConfirmWarning, ADMIN_ConfirmQuestion, ADMIN_ConfirmDelete, ADMIN_InfoMessage, ADMIN_SuccessMessage, ADMIN_Message, ADMIN_Force, or ADMIN_Forward. ADMIN_Force,
Allows you to validate the SQL parameters before any other SQL is run in the component. This call is only made if the SQL is a stored procedure and Validate parameters is checked.
Use this call to restrict which entries a user is allowed to view and edit, and to log which entries a user views.
Access to a menu item is normally controlled through functions and roles alone but some entities need more fine grained control. For example, a user may have access to the View Member menu item for normal members but not for members with a protected identity.
The menu items a user visits are always logged (in ADMINLogMenuItem) but for sensitive data you may need to log exactly what entries are viewed. Do the logging in this call as the common ways of viewing data (grid and InfoSQL) are not allowed to modify the database.
If you bind a scalar function instead of a stored procedure to this call then its name must end with '_GrantAccess'.