Versions Compared

Old Version 19

changes.mady.by.user Former user

Saved on

compared with

New Version Current

changes.mady.by.user Former user

Saved on

Key

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

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

Note

Following configurations are only valid for generic RXTs and not for the content RXTs such as WSDL, WADL, XSD, Policy etc.

...

Table of Contents
location
maxLevel4
minLevel4
locationtop
styleborder:1
toptypeflat
separatorpipe

...

The table Element

...

Some types of fields can have optional attributes. A The text-area field accepts height and width 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 attribute. Setting url="true" displays 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

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 is used instead.

Info

The label can have characters such as spaces, parentheses, 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).

    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}.

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>

...