Validate

SitecoreUML includes a Validate Templates command, to help validate templates before they are deployed to Sitecore (Version beta.0.1+). When executed, the Validate Templates command sends the template data to the SitecoreUML service, hosted by the Sitecore instance, to see if the data can be parsed and adheres to the settings defined in the configuration.

SitecoreUML strongly recommends validating templates before every deployment.

Validating Templates

To validate your templates, click Sitecore > Validate Templates

Any validation errors that are found will display in the resulting modal.

Included Validations

SitecoreUML's Validate Templates command is meant to be a one-click validation tool for your UML diagrams. As time goes on, this feature will become more robust, but it currently is meant to help you validate that the templates that you create can be deployed to Sitecore without error.

Field Type Name Validation

Since Version beta.0.1, SitecoreUML has supported field type name validation via the Validate Templates command. This validation strategy checks the field type names specified for each field against the field type mappings (including their aliases) defined in the <fieldTypes> section of the SitecoreUML.config file. Any types that are not recognized will be listed as errors in the validation results.

Note that when deploying templates to Sitecore, any fields with field-types that SitecoreUML is unable to interpret are skipped and logged. This feature helps avoid these situations by enabling users to identify unrecognized field type names before attempting a deployment.

Item Name Validation

Support for item name validation is included in Version 1.0+, and supports validating the names of each of the following using Sitecore's native item name validation logic:

• Templates
• Template Folders
• Template Fields
• Template Field Sections (1.2.0+)

Note that when deploying templates to Sitecore, any invalid names will result in an error that will halt the deployment. This feature helps avoid these situations by enabling users to identify item name issues before attempting a deployment.