data_entry_properties.xml file file parameters

The data_entry_properties.xml file defines the HTML properties and script that provide content for an additional catalog and hierarchy elements that are displayed in the Single Edit pane.

Values

For each set of <script></script> tags, you can specify:

type

There are two types of scripts you can specify in the <type></type> tags:

url: Note: The getURL(entry) function is deprecated.
content: Specifies a script whose getContent(entry) function returns HTML content. This HTML content is then used for displaying a div on the Single Edit pane directly after the Common Attributes section.

title

In the <title></title> tags, specify the title of the div element.

path

In the <path></path> tags, specify the script and directory file path: scripts/triggers/script_Name

where, script_Name is the script.

extra

Optionally, through the <extra></extra> tags, you can pass extra HTML markup to format your div elements.

File location

The data_entry_properties.xml file is located in $TOP/etc/default directory.

Single edit and multi-edit with rich search simplified user interface support

For the Single edit and multi-edit with rich search simplified screen, the data_entry_properties.xml file provides additional options to configure the behavior and display of the frames. In addition to the required parameters mentioned earlier, you can also specify the following optional parameters for each script:

<position></position> tags

Specify the position of the div element for a script. The position can be tab or top. If this tag is not present for a script, the default position for the div element is top.

<display-state></display-state> tags

Specify the initial display state of a div element for a script, which is configured to be displayed at the top position. The display state can be expanded or collapsed. If this tag is not present for a script, the initial display state for the div element is expanded.

<refresh-on></refresh-on> tags

Specify zero or more <action></action> tags. Each action tag represents a single action on the single edit screen on which the script should be run again and the content of the div element refreshed. If the refresh-on tag for a script does not contain any action tags, the script will not be run after the initial load on any action. If the refresh-on tag is not present for a script, the script is executed again and the content of the div element is refreshed on all valid actions for the container.

<action></action> tag

Specify a valid action on the Single Edit screen. The valid values of action tags for different container types are:

Catalog: save, refresh, revert, categorize
Catalog Collaboration Area: save, refresh, revert, categorize
Hierarchy: save, refresh, revert, modify_spec_mapping
Hierarchy Collaboration Area: save, refresh, revert, modify_spec_mapping

In addition to the <catalog></catalog> and <hierarchy></hierarchy> tags, the use of <collaboration-area></collaboration-area> tags are also supported in the single edit and multi-edit with rich search simplified user interface.

Example


<company code="trigo">
	<catalog name="catalog1">
		<script>
			<type>content</type>
			<title>Sample Script 2</title>
			<path>/scripts/triggers/sampleScript2</path>
			<position>tab</position>
			<refresh-on></refresh-on>
		</script>
	</catalog>
	<hierarchy name="hierarchy1">
		<script>
			<type>content</type>
			<title>Sample Script 6</title>
			<path>/scripts/triggers/sampleScript6</path>
			<position>tab</position>
			<refresh-on></refresh-on>
		</script>
	</hierarchy>
	<collaboration-area name="catalogCA1">
		<script>
			<type>content</type>
			<title>Sample Script 7</title>
			<path>/scripts/triggers/sampleScript7</path>
			<position>tab</position>
		</script>
	</collaboration-area>
</company>