We have moved!

You are currently looking at documentation for Umbraco 8 and older versions.
Go to docs.umbraco.com for documentation for Umbraco 9 and newer versions.

    Adding a type to the provider model

    To add a new type, no matter if it's a workflow, field, data source, etc, there is a number of tasks to perform to connect to the Forms provider model. This chapter walks through each step and describes how each part works. This chapter will reference the creation of a workflow type. It is, however, the same process for all types.


    Create a new ASP.NET or class project in Visual Studio add references to the Umbraco.Forms.Core.dll.

    Adding the type to Forms

    The Forms API contains a collection of classes that the provider model automatically registers. So to add a new type to Forms you inherit from the right class. In the sample below we use the class for the workflow type.

    public class LogWorkflow : Umbraco.Forms.Core.WorkflowType
        public override WorkflowExecutionStatus Execute(Umbraco.Forms.Core.Persistence.Dtos.Record record, RecordEventArgs e)
            throw new NotImplementedException();
        public override List<Exception> ValidateSettings() {
            throw new NotImplementedException();

    When you implement this class you get two methods added. One of them is Execute which performs the execution of the workflow and the other is a method which validates the workflow settings, we will get back to these settings later on.

    Even though we have the class inheritance in place, we still need to add a bit of default information.

    Setting up basic type information

    Even though we have the class inheritance in place, we still need to add a bit of default information. This information is added in the class's empty constructor like this:

    public LogWorkflow() {
        this.Name = "The logging workflow";
        this.Id = new Guid("D6A2C406-CF89-11DE-B075-55B055D89593");
        this.Description = "This will save an entry to the log";

    All three are mandatory and the ID must be unique, otherwise the type might conflict with an existing one.

    Adding settings to a type

    Now that we have a basic class setup, we would like to pass setting items to the type. So we can reuse the type on multiple items but with different settings. To add a setting to a type, we add a property to the class, and give it a specific attribute like this:

    [Umbraco.Forms.Core.Attributes.Setting("Log Header",
            Description = "Log item header",
            View = "TextField")]
    public string LogHeader { get; set; }

    The Umbraco.Forms.Core.Attributes.Setting registers the property in Umbraco Forms and there will automatically be UI and storage generated for it. In the attribute, a name, description and the view to be rendered is defined.

    With the attribute in place, the property value is set every time the class is instantiated by Umbraco Forms. This means you can use the property in your code like this:

    [Umbraco.Forms.Core.Attributes.Setting("Document ID",
            Description = "Node the log entry belongs to",
            View = "Pickers.Content")]
    public string Document { get; set; }
    public override WorkflowExecutionStatus Execute(Umbraco.Forms.Core.Persistence.Dtos.Record record, RecordEventArgs e) {
         Umbraco.Core.Composing.Current.Logger.Info<WorkflowType>("{Document} record submitted from: {IP}", int.Parse(Document), record.IP);
                return WorkflowExecutionStatus.Completed;

    For all types that use the provider model, settings work this way. By adding the Setting attribute Forms automatically registers the property in the UI and sets the value when the class is instantiated.

    Validate type settings with ValidateSettings()

    The ValidateSettings() method which can be found on all types supporting dynamic settings, is used for making sure the data entered by the user is valid and works with the type.

    public override List<Exception> ValidateSettings() {
        List<Exception> exceptions = new List<Exception>();
        int docId = 0;
        if (!int.TryParse(Document, out docId))
            exceptions.Add(new Exception("Document is not a valid integer"));
        return exceptions;

    Registering the class with Umbraco and Forms

    Finally compile the project and copy the .dll to your website /bin folder or copy the .cs file to the app_code directory. The website will now restart and your type will be registered automatically, no configuration needed. Also look in the reference chapter for complete class implementations of workflows, fields and export types

    Overriding default providers in Umbraco Forms

    This is a new feature in Forms 6.0.3+ that makes it possible to override & inherit the original provider, be it a Field Type or Workflow etc. The only requirement when inheriting a fieldtype that you wish to override is to ensure you do not override/change the Id set for the provider, and make sure your class is public.

    Here is an example of overriding the Textarea field aka Long Answer that is taken from Per's CodeGarden 17 talk, which has been updated for Forms 8.

    public class TextareaWithCount : Umbraco.Forms.Core.Providers.FieldTypes.Textarea
        // Added a new setting when we add our field to the form
        [Umbraco.Forms.Core.Attributes.Setting("Max length",
        Description = "Max length",
        View = "TextField")]
        public string MaxNumberOfChars { get; set; }
        public TextareaWithCount()
            // Set a different view for this fieldtype
            this.FieldTypeViewName = "FieldType.TextareaWithCount.cshtml";
            // We can change the default name of 'Long answer' to something that suits us
            this.Name = "Long Answer with Limit";
        public override IEnumerable<string> ValidateField(Form form, Field field, IEnumerable<object> postedValues, HttpContextBase context, IFormStorage formStorage)
            var baseValidation = base.ValidateField(form, field, postedValues, context, formStorage);
            var value = postedValues.FirstOrDefault();
            if (value != null && value.ToString().Length < int.Parse(MaxNumberOfChars))
                return baseValidation;
            var custom = new List<string>();
            custom.Add("String is way way way too long!");
            return custom;