...
Table of Contents | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
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 |
...
This is the root element of the new artifact which is being defined. It has several attributes:
type - Defines the 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 of the artifact. Only lower case characters are allowed in the short name. This value cannot be modified once the RXT is added into the WSO2 Governance Registry.
- 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
...
Info | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
You cannot have the (~!@#;%^*()+={}|\<>"',) characters in the value of the unique fields that are defined in the
The validations required for the following storage path are as follows:
|
Note | |||||||
---|---|---|---|---|---|---|---|
When choosing attributes for the
|
...
The nameAttribute
Element
Code Block |
---|
<nameAttribute>details_name</nameAttribute> |
...