Class Reference
IRIS for UNIX 2024.1.2
|
|
Private
Storage
|
This dialog window displays a finder-style file selection window.
This is intended for use within server portal pages.
To launch the finder use the zenLaunchPopupWindow function:
zenLaunchPopupWindow('%ZEN.Dialog.finderDialog.cls?MODE=classes', 'DataSource', 'status,scrollbars,resizable=yes,width=800,height=600');
ClientMethod onPopupAction(popupName, action, value) [ Language = javascript ] { switch(popupName) { case 'DataSource': if (value != '') { // value is name plus extension // pull extension off of name var s = value.toString().split('.'); if ('cls' == s[s.length-1]) { s.length = s.length-1; var className = (s.join('.'); } } break; } }
|
|
Subclasses | |
---|---|
%DeepSee.UI.Dialog.finderDialog | %iKnow.UI.Dialog.openDomain |
|
AUTOLOGOUT is disabled for the finder dialog as we expect it to be called as a soft modal, and the timeout behaviour should thus be controlled by the opening page.
If this page has multiple categories, this is its initial value. Note: the "local" value has meaning only for "classes" mode. Other modes should set a different default category. See %OnAfterCreatePage() for where these defaults are set for each mode.
If this page has multiple views, this is its initial display mode.
Localization domain
|
Page calling page might populate e.g dtleditor
Category used by some modes.
Current Category.
Current sort mode for this page.
If this page has "views", this is the current view type.
If defined, then use this as the extension for items returned by the finder (e.g., "bpl").
Include abstract classes. Used by some modes.
Used with mode "classes" for the business process context. Include or do not include classes that are either persistent, serial, or datatype. If true, accept any of these types. If false, accept none of them. As you can see in %ZEN.FinderUtils, the value for includeContext overrides any value for includeDatatype. The value for includeContext will also override mode "persistent" so they should not be used together. Use includeContext only with mode "classes".
Used with mode "classes". Include or do not include classes that are datatypes.
Used with mode "classes". Include or do not include classes that are generated.
Used with mode "classes". Include or do not include classes whose names include the % character.
Used with mode "classes". Include or do not include classes that are mapped to product databases, e.g. IRISSYS, IRISLIB, ENSLIB, HSLIB
Include system items. Used by some modes. Note that passing in the empty string when in "classes" mode and "local" category will include both system and non-system classes.
This value is passed in by the caller of this dialog. It indicates what things to display. The default is "classes".In "classes" mode the finderDialog supports four different sub-modes (stored in the currCategory property) which are chosen by the user clicking on an icon in the left-hand column of the finder.
The "local" sub-mode sets SYSTEM=0 and PERCENT=0 and PRODUCT=0. This is the default sub-mode for "classes".
The "persistent" sub-mode sets PERSISTENT=1 and, if they are undefined, SYSTEM=0, PERCENT=0, and PRODUCT=0.
The "datatype" sub-mode sets DATATYPE=1. The "system" sub-mode sets SYSTEM=1 and PERCENT=1 and PRODUCT=1.Any URL parameter for the finderDialog that is not set by a "classes" sub-mode as described above may be used effectively with "classes" mode.
Other mode options are:
"classes" -- show class finder.
"persistent" -- show persistent class finder. Do not use DATATYPE or CONTEXT modifiers with this mode.
"datatype" -- show datatype class finder. Do not use DATATYPE or CONTEXT modifiers with this mode.
"cubes" -- show DeepSee cube finder.
"bpl" -- show BPL business process finder.
"bplplus" -- show business process finder: BPL and non-BPL.
"dtl" -- show DTL data transformation finder.
"dtlplus" -- show DTL data transformation finder: DTL and non-DTL.
"request" -- show all message request classes.
"response" -- show all message response classes.
"allmessages" -- show all message classes, grouped into categories.
"rules" -- show rules finder.
"nms" -- show production-enabled namespaces.
"vdocclass" -- show VDoc or persistent classes.
"vdocschema" -- show VDoc schema categories for one or all VDoc families.
"vdoctype" -- show DocType structures. CATEGORY indicates the doc class.
"vdoccontents" -- show the contents of an VDoc structure. CATEGORY indicates the VDoc class and the DocType in the following format: CATEGORY=VDocClass|DocType.
"vdocsegtype" -- show segment types. CATEGORY indicates the VDoc class.
"vdocsegcontents" -- show property paths for a given segment. CATEGORY indicates the VDoc class and the DocType in the following format: CATEGORY=VDocClass|DocType.
"configurations" -- show configuration items for all Productions.
"folderitems" -- show DeepSee folder items.
"services" -- show all Business Service classes.
"operations" -- show all Business Operation classes.
"lookups" -- show all defined lookup tables.
"sqlstored" -- show all stored procedures.
"queries" -- show all stored procedures that return resultSets except default extent queries. "allqueries" -- show all stored procedures that return resultSets. "views" -- show all SQL views.
"querycontext" -- alternately show queries, allqueries or view. "prjfiles" -- show all Studio project files.
"production" -- show productions which are allowed in the namespace.
"datasettings" -- show all Deployable Settings Documents.
Value to be returned by this dialog.
Current search (filter) key value.
Current super class filter value which does not include the superclass in the output. If set, this overrides the mode behaviour. Note thatsuperKey takes precedence if both properties are specified.
Current super class filter value. If set, this overrides the mode behavior.
|
Add components to page.
This callback is called at the end of the HTML HEAD section of the page.
(default implementation is a simple expression).
Get the (localized) subtitle string for the dialog. This should be implemented in a subclass.
Get the (localized) title string for the dialog. This should be implemented in a subclass.
Draw the contents of the Categories list on the left side of the dialog. This is displayed if a subclass implements theOnGetCategoryInfo callback.
pSeed indicates what to draw: "classes","zen", etc.
Draw the contents of the tool ribbon. This is displayed if a subclass implements theOnGetRibbonInfo callback.
Provide the source data (as an array) that will drive the finder.
Get information to display in the category box.
Get information to display in the ribbon bar.
Avoid writing out the session cookie if we are in a Studio session.
Adjust size and position of components on this page.
Provide HTML for details on selected item in finder.
Get the value that will be applied when the user presses the OK button. This is implemented by subclasses.
Return the icon for the item in "icons" mode.
Item double-clicked within the Finder.
Item selected within the Finder.
Load the children for the given node in the finder.
This client event, if present, is fired when the page is loaded.
User clicked on super class link.
User has changed search key value.
Change the current category for this page.
Do the actual work of applying the new category selection.
Change the current sort mode for the page.
Do the actual work of applying the new sort option.
Change the current display mode for this page. This is called by the icon buttons on the ribbon. This will call thesetViewModeHandler within a subclass.
Do the actual work of updating the view to match the current view mode.