Standard iPart configuration
- Name - Enter a name for the content item.
This text appears during design mode (configuration).
- Title - Enter the text to display above this iPart on the rendered page.
If blank, no title displays.
- Do not render in design mode - Select this option to prevent content
record data from being loaded in the content editor. This improves performance during design time
(configuration).
- iPart CSS class - (optional) Enter the name of a CSS class to associate with
this iPart, which will add a DIV so named around the iPart. Add this CSS class to an appropriate
style sheet. Using such classes lets you apply special formatting to targeted iParts in a reusable way.
- Display a border around this content - Select this option to display a border
around this iPart on the rendered page.
- Display content within a collapsible panel - Enable to allow users to minimize
the panel within the page, to work with dense pages more efficiently.
- Show the content as collapsed - Enable to display the panel minimized by default.
Tip: Be sure that the Title makes clear what data is hidden from view.
TextAlert configuration
-
SQL stored procedure - A SQL stored procedure name, or a stored procedure with desired parameters. By convention, TextAlert procedures start with
pta_
(Procedure for TextAlert)
If you provide only a procedure name, TextAlert will execute your procedure with parameters of @id, @user, @url
in that order.
If you prefix the procedure name with exec (like exec pta_MyProcedure
) or if you specify one or more parameters, TextAlert will not add to your command.
You can use any or all of the available parameters in any order, and also pass constant/literal values. For example, exec pta_MyProcedure @id, 'MainPage', @appRoot, @url, 'debug'
Available parameters:
@id (varchar(10))
- ID of the selected contact. If no selected contact, ID of user who is logged in.
@user (varchar(60))
- username of the user who is logged in
@url (varchar(1000))
- the complete current browser URL
@appRoot (varchar(1000))
- the URL of the current application root
- Format as table - If checked, TextAlert will generate an HTML table with all the rows and columns returned by the stored procedure. If unchecked, the contents of the FIXEDTEXT column of the first row from the procedure will be displayed.
In table mode, certain special column names will not be added to the table, but will trigger different behavior for the row of results where they are found.
HEADER_COLUMNS
- integer - If greater than zero, the first {HEADER_COLUMNS} of output on this row will be TH (table header) cells instead of TD (table data) cells.
CSS_CLASS
- string - This class will be applied to the TR (table row) tag of the generated table.
- Show table header - If checked, the HTML table will include a header row with the column names. Has no effect when not using a table.
- Allow or block HTML markup in output - If the text used in the alert can contain data from the user, your website can be exposed to Cross-Site Scripting (XSS) attacks. You should only Allow HTML if alerts do not contain user-entered data, or you can protect against XSS in other ways. If you choose "Use global default", this iPart will follow the setting found in RSM Configuration.
This help file:
$Rev: 21431 $
$Date: 2023-01-18 18:53:27 -0600 (Wed, 18 Jan 2023) $