K Khan
Aug 18, 2016
visibility 3514
star star star star star star
(4 votes)

page validations

There are instances when Editors should to be informed in form of warning and information rather to stop them and display error messages. For self note IValidate interface can be used for this purpose. e.g

public class StandardPageValidator : IValidate<StandardPage>
    {
        public IEnumerable<ValidationError> Validate(StandardPage instance)
        {
            if (instance.Name.Length < 10)
            {
                return new List<ValidationError>() {
                    new ValidationError() {
                        ErrorMessage ="Name is very short",
                        PropertyName = "Name",
                        Severity =ValidationErrorSeverity.Info,
                        ValidationType =ValidationErrorType.AttributeMatched
                    }
                };
            }

            return Enumerable.Empty< ValidationError>();
        }
    }

Image information.jpg

References:

http://world.episerver.com/documentation/Class-library/?documentId=episerverframework/7.5/e53f458f-f4a1-2904-620d-cad9167f3387

http://world.episerver.com/documentation/Class-library/?documentId=episerverframework/7.5/2a269a53-76ff-8c86-5984-5512fbe9f9b9

Aug 18, 2016

Comments

Aug 19, 2016 05:35 PM

Good post.  One additional thing I would mention here is that you can compare multiple fields as part of your validation logic, which gives the interface a bit more flexibility than other methods.

K Khan
K Khan Aug 19, 2016 07:07 PM

Good point Janaka, Thanks for sharing!

David Strøm
David Strøm Aug 24, 2016 11:15 AM

I have begun using this kind of validation for required properties instead of the builltin functionality which shows the editor a very anonymous form with the required fields. In my opinion the editor can easily loose track of context when they see this form.

Instead I use the IValidate to handle required fields and other validations. Exactly as you describe it. Then the editor has the context of the whole content type.

Good of you to put some spotlight on the IValidate functionality.

K Khan
K Khan Aug 24, 2016 11:24 AM

Thanks for sharing your approach, That makes sense!

Per Nergård (MVP)
Per Nergård (MVP) Aug 24, 2016 09:59 PM

We use this all the time and as David said it's perfect for validate several fields if you whish.  You can actually manipulate the data in the properties. Unfortunately the changes made in a validation isn'r reflected in the UI so the editor can see. I played around with it and you can read a blog post about it here.

K Khan
K Khan Aug 25, 2016 09:52 AM

Here we go! Thanks Per :), I remeber this now, You post is really a good reference point on this topic.

error Please login to comment.
Latest blogs
Composition Over Inheritance: Why Your Content Contract Is Not a Base Class

Inside the structural conformance pattern in SaaS CMS — from server-side inheritance to pipeline governance. A contract in Optimizely SaaS CMS is...

Vipin Banka | Sep 19, 2026

Optimizely Opti ID Integration: Why the API Key Was Missing from the DXP Management Portal

While working on an Optimizely CMS 12 Opti ID integration recently, we ran into an issue that initially appeared to be related to SSO authenticatio...

Madhu | Sep 18, 2026 |

Extending a Contract: What You Can Override

Contracts share fields across content types — but not every field setting can be overridden. Push the same contract onto several components, and CM...

Chirag Khanna | Sep 18, 2026 |

Building a Blazor Server UI Inside the Optimizely CMS 13 Admin Shell

What I learned shipping a Blazor Server UI inside Optimizely CMS 13 — Razor components in a NuGet package, the Blazor hub next to MapContent(),...

Stanisław Szołkowski | Sep 17, 2026 |