Parameter

Select the appropriate subsystem.

Displays the parameter type as iKnowBase.

Type a name for this parameter.

Type a description for this parameter.

Type the alias for the parameter.

All parameters are sent with the default naming convention such as p_d_i/p_d_v and p_d_c. To increase the readability of the URLs, you can use aliases. For example, the IKB DocumentID attribute has ID = -121. By adding the p_document_id alias, a portlet that uses this parameter can change the URL from p_d_i=-121&p_d_c=IS&p_d_v=<value> to p_document_id=<value>.

Select the appropriate attribute.

Only available for title and search string attribute. When checked, it will add a wildcard when used as a search criteria.

Select the appropriate condition that is used as default in a search source where the parameter is used.

Note: This is applicable only for search sources that are created in the standard mode. Valid values depend on the type of attribute.

Select this check box to lock the selected condition in the filter dialog box. The condition then becomes mandatory for the user, and the user cannot choose to use other conditions for this parameter.

Note: This is applicable only for search sources that are generated in the standard mode.

Select this check box to be able to use the iKnowBase parameter in the search filter under the Add Attribute function. This functionality makes the attribute searchable, even if it is not a part of the predefined filter.

Type the maximum length of the text that a user can type in a search filter box.

Select the appropriate subsystem.

Displays the parameter type as SQL parameter.

Type a name for this parameter.

Type a description for this parameter.

Type the alias for the parameter.

All parameters are sent with the default naming convention such as p_d_i/p_d_v and p_d_c. To increase the readability of the URLs, you can use aliases. For example, the IKB DocumentID attribute has ID = -121. By adding the p_document_id alias, a portlet that uses this parameter can change the URL from p_d_i=-121&p_d_c=IS&p_d_v=<value> to p_document_id=<value>.

If the condition has a #PARAM# notation (means it will use a dynamic value as input) you can define an attribute which can be used as a filter attribute in a search viewer. The value will also define the value list for the filter attribute.

Type the where-condition that adds itself to the SQL produced by the component in which it is used, typically a viewer or search source. These components extracts data from the DOCUMENT table with prefix oi1. The condition must start with AND.

You can use variables in the where-condition:

• #USERID# which will be substituted with numeric user ID.
• #SITEID# which will be substituted with the active site ID.
• #PARAM# which will be substituted by the value of the dynamic parameter that is submitted through a target, where the dynamic parameter is the same as this parameter.

You can also define functions that are executed within the condition. The function must return a value. Functions are specified within curly brackets: { functionName}.

Note: The execution is done only once, rather than one time per document that are extracted, and might be smart regarding performance.

Example:

AND (oi1.document_id_ref IS NOT NULL  
AND (oi1.owner_id = #USERID# 
OR oi1.owner_id = {dbbruker.get_manager(#USERID#)}))

Displays a globally unique identifier number for this component. This property appears after you save a component. You cannot update the information of this property.

Displays a unique identifier number for this component. This property appears after you save a component. You cannot update the information of this property.

Displays when the component was created and by whom it was created.

Displays when the component was last updated and by whom it was updated.