This is an old revision of the document!
With this feature you can configure an existing stored procedure or SQL script or SQL command or web service to become available as callable object. Callable objects are linked to catalog objects on table level or record level.
Unique ID for this callable object configuration entry.
Description for this callable object configuration entry.
Type of the callable object. Depending on the type the location, where the callable object is stored physically is set. Stored procecedures have to be in database where the selected connections point to. Web-Service calls and SQL scripts have to be located on the file system of the server where niota is installed.
Connection where the stored procedure can be found or where the connection is established in case of SQL script / SQL command.
Commandstring in case of a SQL based callable object (stored procedure or SQL command) or filename of the script file in case of file based callable object (web-service call / SQL script file)
Customer defined category for this configuration entry. No further check on this value.
Sort order for the order of display in the callable object pop-up window.
Checkbox to toggle message display on. When messages is on, then the messages whicht are written by the callable object into the message table set in the connection configuration are displayed. If messages is off, then no messages are displayed to the user.
Checkbox to force a refresh of the table after execution of callable object.
Type of pop-up window/prompt window that appears before callable object is executed. Actually only file upload is available.
Name of the iconfile (with file extension) that should displayed in the callable object pop-up window.
ID of callalbe object by which this sequence of executions is initiated.
ID of an existing callable object configuration entry, that is member of the sequence.
Sort order to control the order of executions within a sequence.