Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Once you've learned how to create a registry extension file and a content, see the list of the Governance Artifacts main element descriptions below:

...

Table of Contents
maxLevel4
minLevel4
locationtop
styleborder:1
locationtop
typeflat
separatorpipe

...

The table Element

...

Code Block
<table name="Overview">
  <field type="text" required="true"> <name>Name</name> </field>
  <field type="text" required="true"> <name>Namespace</name> </field>
  <field type="text"> <name>Version</name> </field>
  <field type="text-area"> <name>Description</name> </field>field>only lower case characters are allowed in short name
</table>

The generated HTML UI of the table element appears as below.

...

The field element can have a couple of attributes, including a mandatory attribute type. The type attribute specifies the field type, which can be text, option, text-area, option-text, or date or checkbox.

Some types of fields can have optional attributes. A The text-area field accepts height and width url as optional attributes. The height and width attributes should be numerical and their values should be in pixels. The text field accepts url as an optional attributean optional attribute. Setting url="true" will display the text as a URL instead of as a plain text box.

...

Code Block
<field type="options"> <name>States<<name>states</name> <values> <value>Created</value> <value>Tested</value> <value>Deployed</value> <value>Deprecated</value> </values> </field>

...

Code Block
<field type="options">
     <name label="Lifecycle Name">Lifecycle Name<>lifecycle_name</name>
     </field>
Info
titleTip

The label is the text that appears on the browser UI, whereas the name is the actual name of what is being stored on the repository, in XML format.
The label is optional. If it is not defined, the name will be used instead.

Info
titleNote

The label can have characters such as spaces, paranthesis parenthesis uppercase letters etc, . whereas the name cannot have those.

...

This is the root element of the new artifact which is being defined. It has several attributes:

  • type - Defines the

    mediatype

    media type of the artifact. The type format should be application/vnd.[SOMENAME]+xml. SOMENAME can contain any alphanumeric character, "-" (hyphen), or "." (period).

  • shortName - Short name for the artifact
  • singularLabel - Singular label of the artifact
  • pluralLabel -
    Info

     Use the following pattern when defining the media type of custom RXTs:  application/[a-zA-Z0-9.+-]+

  • shortName - Short name for the artifact. Only lower case characters are allowed in the short name.
  • singularLabel - Singular label of the artifact
  • pluralLabel - Plural label of the artifact
  • hasNamespace - Defines whether the artifact has a namespace (boolean)
  • iconSet - Icon set number used for the artifact icons

...

This is the path where the instance data of the artifact is stored. When you evaluate this expression, it automatically replaces @{name} with the name of the artifact and @{namespace} with the namespace of the artifact. In addition to the name and namespace, you can also specify any other attribute in the format @{ATTRIBUTE_NAME}, e.g., /trunk/processes/@{business_domain}/@{overview_version}format @{ATTRIBUTE_NAME}, e.g., /trunk/processes/@{business_domain}/@{overview_version}.

Info

You cannot have the (~!@#;%^*()+={}|\<>"',) characters in the value of the unique fields that are defined in the storagePath element in the RXT. Hence, you need to add a validation for the field definitions of those fields. For example, consider the following storage path.

Code Block
languagexml
<storagePath>/gadgets/@
{overview_provider}
/@
{overview_name}
/@
{overview_version}
</storagePath>

The validations required for the following storage path are as follows:

Code Block
languagexml
...............
<content>
<table name="Overview">
<field type="text" required="true">
<name>Provider</name>
</field>
<field type="text" required="true" validate="^([a-zA-Z0-9_\s\-]*)$">
<name>Name</name>
</field>
........................

...

The nameAttribute Element

Code Block
<nameAttribute>details_name</nameAttribute>

...

Code Block
    <field type="text" validate="^\d+$">
     <name>Age</name>
    </field>

Note: If you want to have characters like '<' in regular expression you have to put corresponding XML codes like &lt; as RXT configuration is an XML document. 

tooltip Attribute

The tooltip attribute can be used to give a tooltip to be shown with any type of field.

...