diff --git a/14/umbraco-forms/.gitbook.yaml b/14/umbraco-forms/.gitbook.yaml deleted file mode 100644 index 8865254d413..00000000000 --- a/14/umbraco-forms/.gitbook.yaml +++ /dev/null @@ -1,10 +0,0 @@ -root: ./ - -​structure: - readme: README.md - summary: SUMMARY.md - -redirects: - the-licensing-model: installation/the-licensing-model.md - installation/manualupgrade: upgrading/manualupgrade.md - installation/version-specific: upgrading/version-specific.md diff --git a/14/umbraco-forms/.gitbook/assets/Blog_post_for_com_900x400px_1_8_7_ (1).png b/14/umbraco-forms/.gitbook/assets/Blog_post_for_com_900x400px_1_8_7_ (1).png deleted file mode 100644 index 2a8c064f60e..00000000000 Binary files a/14/umbraco-forms/.gitbook/assets/Blog_post_for_com_900x400px_1_8_7_ (1).png and /dev/null differ diff --git a/14/umbraco-forms/.gitbook/assets/Blog_post_for_com_900x400px_1_8_7_.png b/14/umbraco-forms/.gitbook/assets/Blog_post_for_com_900x400px_1_8_7_.png deleted file mode 100644 index 2a8c064f60e..00000000000 Binary files a/14/umbraco-forms/.gitbook/assets/Blog_post_for_com_900x400px_1_8_7_.png and /dev/null differ diff --git a/14/umbraco-forms/.gitbook/assets/FormSettingsAutocomplete (1).png b/14/umbraco-forms/.gitbook/assets/FormSettingsAutocomplete (1).png deleted file mode 100644 index 148c59918e3..00000000000 Binary files a/14/umbraco-forms/.gitbook/assets/FormSettingsAutocomplete (1).png and /dev/null differ diff --git a/14/umbraco-forms/.gitbook/assets/FormSettingsAutocomplete.png b/14/umbraco-forms/.gitbook/assets/FormSettingsAutocomplete.png deleted file mode 100644 index 148c59918e3..00000000000 Binary files a/14/umbraco-forms/.gitbook/assets/FormSettingsAutocomplete.png and /dev/null differ diff --git a/14/umbraco-forms/.gitbook/assets/FormSettingsFieldsDisplayed.png b/14/umbraco-forms/.gitbook/assets/FormSettingsFieldsDisplayed.png deleted file mode 100644 index 18cc4170619..00000000000 Binary files a/14/umbraco-forms/.gitbook/assets/FormSettingsFieldsDisplayed.png and /dev/null differ diff --git a/14/umbraco-forms/.gitbook/assets/Umbraco 9.3RC- Blog_post_for_com_900x400px_1@2x-80 (1).jpg b/14/umbraco-forms/.gitbook/assets/Umbraco 9.3RC- Blog_post_for_com_900x400px_1@2x-80 (1).jpg deleted file mode 100644 index d12b2963fc0..00000000000 Binary files a/14/umbraco-forms/.gitbook/assets/Umbraco 9.3RC- Blog_post_for_com_900x400px_1@2x-80 (1).jpg and /dev/null differ diff --git a/14/umbraco-forms/.gitbook/assets/Umbraco 9.3RC- Blog_post_for_com_900x400px_1@2x-80.jpg b/14/umbraco-forms/.gitbook/assets/Umbraco 9.3RC- Blog_post_for_com_900x400px_1@2x-80.jpg deleted file mode 100644 index d12b2963fc0..00000000000 Binary files a/14/umbraco-forms/.gitbook/assets/Umbraco 9.3RC- Blog_post_for_com_900x400px_1@2x-80.jpg and /dev/null differ diff --git a/14/umbraco-forms/.gitbook/assets/_packageBlog_post_for_com_900x400px (1).png b/14/umbraco-forms/.gitbook/assets/_packageBlog_post_for_com_900x400px (1).png deleted file mode 100644 index 824e289115a..00000000000 Binary files a/14/umbraco-forms/.gitbook/assets/_packageBlog_post_for_com_900x400px (1).png and /dev/null differ diff --git a/14/umbraco-forms/.gitbook/assets/_packageBlog_post_for_com_900x400px.png b/14/umbraco-forms/.gitbook/assets/_packageBlog_post_for_com_900x400px.png deleted file mode 100644 index 824e289115a..00000000000 Binary files a/14/umbraco-forms/.gitbook/assets/_packageBlog_post_for_com_900x400px.png and /dev/null differ diff --git a/14/umbraco-forms/.gitbook/assets/image.png b/14/umbraco-forms/.gitbook/assets/image.png deleted file mode 100644 index 002dbcbe5c8..00000000000 Binary files a/14/umbraco-forms/.gitbook/assets/image.png and /dev/null differ diff --git a/14/umbraco-forms/.gitbook/assets/umbraco_forms_swagger.json b/14/umbraco-forms/.gitbook/assets/umbraco_forms_swagger.json deleted file mode 100644 index 360a0c02bf4..00000000000 --- a/14/umbraco-forms/.gitbook/assets/umbraco_forms_swagger.json +++ /dev/null @@ -1,555 +0,0 @@ -{ - "openapi": "3.0.1", - "info": { - "title": "Umbraco Forms API", - "description": "Describes the Umbraco Forms API available for rendering and submitting forms. You can find out more about the API in [the documentation](https://docs.umbraco.com/umbraco-forms/v/12.forms.latest/developer/ajaxforms)", - "version": "Latest" - }, - "paths": { - "/umbraco/forms/delivery/api/v1/definitions/{id}": { - "get": { - "tags": [ - "Forms" - ], - "parameters": [ - { - "name": "id", - "in": "path", - "description": "The form's Id.", - "required": true, - "schema": { - "type": "string", - "format": "uuid" - } - }, - { - "name": "contentId", - "in": "query", - "description": "The Id of the content page on which the form is hosted.", - "schema": { - "type": "string" - } - }, - { - "name": "culture", - "in": "query", - "description": "The culture code for the form's localization context.", - "schema": { - "type": "string" - } - }, - { - "name": "additionalData", - "in": "query", - "description": "Additional data provided when rendering the form.", - "schema": { - "type": "object", - "additionalProperties": { - "type": "string" - } - } - } - ], - "responses": { - "200": { - "description": "Success", - "content": { - "application/json": { - "schema": { - "$ref": "#/components/schemas/FormDto" - } - } - } - }, - "400": { - "description": "Bad Request", - "content": { - "application/json": { - "schema": { - "$ref": "#/components/schemas/ProblemDetails" - } - } - } - }, - "404": { - "description": "Not Found", - "content": { - "application/json": { - "schema": { - "$ref": "#/components/schemas/ProblemDetails" - } - } - } - } - } - } - }, - "/umbraco/forms/delivery/api/v1/entries/{id}": { - "post": { - "tags": [ - "Forms" - ], - "parameters": [ - { - "name": "id", - "in": "path", - "description": "The form's Id.", - "required": true, - "schema": { - "type": "string", - "format": "uuid" - } - } - ], - "requestBody": { - "content": { - "application/json": { - "schema": { - "$ref": "#/components/schemas/FormEntryDto" - } - } - } - }, - "responses": { - "202": { - "description": "Accepted" - }, - "400": { - "description": "Bad Request", - "content": { - "application/json": { - "schema": { - "$ref": "#/components/schemas/ProblemDetails" - } - } - } - }, - "404": { - "description": "Not Found", - "content": { - "application/json": { - "schema": { - "$ref": "#/components/schemas/ProblemDetails" - } - } - } - }, - "422": { - "description": "Client Error", - "content": { - "application/json": { - "schema": { - "$ref": "#/components/schemas/ProblemDetails" - } - } - } - } - } - } - } - }, - "components": { - "schemas": { - "FieldConditionActionType": { - "enum": [ - "Show", - "Hide" - ], - "type": "integer", - "format": "int32" - }, - "FieldConditionLogicType": { - "enum": [ - "All", - "Any" - ], - "type": "integer", - "format": "int32" - }, - "FieldConditionRuleOperator": { - "enum": [ - "Is", - "IsNot", - "GreaterThen", - "LessThen", - "Contains", - "StartsWith", - "EndsWith" - ], - "type": "integer", - "format": "int32" - }, - "FormConditionDto": { - "type": "object", - "properties": { - "actionType": { - "$ref": "#/components/schemas/FieldConditionActionType" - }, - "logicType": { - "$ref": "#/components/schemas/FieldConditionLogicType" - }, - "rules": { - "type": "array", - "items": { - "$ref": "#/components/schemas/FormConditionRuleDto" - } - } - }, - "additionalProperties": false - }, - "FormConditionRuleDto": { - "type": "object", - "properties": { - "field": { - "type": "string" - }, - "operator": { - "$ref": "#/components/schemas/FieldConditionRuleOperator" - }, - "value": { - "type": "string" - } - }, - "additionalProperties": false - }, - "FormDto": { - "type": "object", - "properties": { - "id": { - "type": "string", - "format": "uuid" - }, - "name": { - "type": "string" - }, - "indicator": { - "type": "string" - }, - "cssClass": { - "type": "string", - "nullable": true - }, - "nextLabel": { - "type": "string", - "nullable": true - }, - "previousLabel": { - "type": "string", - "nullable": true - }, - "submitLabel": { - "type": "string", - "nullable": true - }, - "disableDefaultStylesheet": { - "type": "boolean" - }, - "fieldIndicationType": { - "$ref": "#/components/schemas/FormFieldIndication" - }, - "hideFieldValidation": { - "type": "boolean" - }, - "messageOnSubmit": { - "type": "string", - "nullable": true - }, - "messageOnSubmitIsHtml": { - "type": "boolean" - }, - "showValidationSummary": { - "type": "boolean" - }, - "gotoPageOnSubmit": { - "type": "string", - "format": "uuid", - "nullable": true - }, - "gotoPageOnSubmitRoute": { - "$ref": "#/components/schemas/IApiContentRouteModel" - }, - "pages": { - "type": "array", - "items": { - "$ref": "#/components/schemas/FormPageDto" - } - } - }, - "additionalProperties": false - }, - "FormEntryDto": { - "type": "object", - "properties": { - "values": { - "type": "object", - "additionalProperties": { - "type": "array", - "items": { - "type": "string" - } - } - }, - "contentId": { - "type": "string", - "nullable": true - }, - "culture": { - "type": "string", - "nullable": true - }, - "additionalData": { - "type": "object", - "additionalProperties": { - "type": "string" - }, - "nullable": true - } - }, - "additionalProperties": false - }, - "FormFieldDto": { - "type": "object", - "properties": { - "id": { - "type": "string", - "format": "uuid" - }, - "caption": { - "type": "string" - }, - "helpText": { - "type": "string", - "nullable": true - }, - "placeholder": { - "type": "string", - "nullable": true - }, - "cssClass": { - "type": "string", - "nullable": true - }, - "alias": { - "type": "string" - }, - "required": { - "type": "boolean" - }, - "requiredErrorMessage": { - "type": "string", - "nullable": true - }, - "pattern": { - "type": "string", - "nullable": true - }, - "patternInvalidErrorMessage": { - "type": "string", - "nullable": true - }, - "condition": { - "$ref": "#/components/schemas/FormConditionDto" - }, - "fileUploadOptions": { - "$ref": "#/components/schemas/FormFileUploadOptionsDto" - }, - "preValues": { - "type": "array", - "items": { - "$ref": "#/components/schemas/FormFieldPrevalueDto" - } - }, - "settings": { - "type": "object", - "additionalProperties": { - "type": "string" - } - }, - "type": { - "$ref": "#/components/schemas/FormFieldTypeDto" - } - }, - "additionalProperties": false - }, - "FormFieldIndication": { - "enum": [ - "NoIndicator", - "MarkMandatoryFields", - "MarkOptionalFields" - ], - "type": "integer", - "format": "int32" - }, - "FormFieldPrevalueDto": { - "type": "object", - "properties": { - "value": { - "type": "string" - }, - "caption": { - "type": "string", - "nullable": true - } - }, - "additionalProperties": false - }, - "FormFieldTypeDto": { - "type": "object", - "properties": { - "id": { - "type": "string", - "format": "uuid" - }, - "name": { - "type": "string" - }, - "supportsPreValues": { - "type": "boolean" - }, - "supportsUploadTypes": { - "type": "boolean" - }, - "renderInputType": { - "type": "string" - } - }, - "additionalProperties": false - }, - "FormFieldsetColumnDto": { - "type": "object", - "properties": { - "caption": { - "type": "string", - "nullable": true - }, - "width": { - "type": "integer", - "format": "int32" - }, - "fields": { - "type": "array", - "items": { - "$ref": "#/components/schemas/FormFieldDto" - } - } - }, - "additionalProperties": false - }, - "FormFieldsetDto": { - "type": "object", - "properties": { - "id": { - "type": "string", - "format": "uuid" - }, - "caption": { - "type": "string", - "nullable": true - }, - "condition": { - "$ref": "#/components/schemas/FormConditionDto" - }, - "columns": { - "type": "array", - "items": { - "$ref": "#/components/schemas/FormFieldsetColumnDto" - } - } - }, - "additionalProperties": false - }, - "FormFileUploadOptionsDto": { - "type": "object", - "properties": { - "allowAllUploadExtensions": { - "type": "boolean" - }, - "allowedUploadExtensions": { - "type": "array", - "items": { - "type": "string" - } - }, - "allowMultipleFileUploads": { - "type": "boolean" - } - }, - "additionalProperties": false - }, - "FormPageDto": { - "type": "object", - "properties": { - "caption": { - "type": "string", - "nullable": true - }, - "condition": { - "$ref": "#/components/schemas/FormConditionDto" - }, - "fieldsets": { - "type": "array", - "items": { - "$ref": "#/components/schemas/FormFieldsetDto" - } - } - }, - "additionalProperties": false - }, - "IApiContentRouteModel": { - "type": "object", - "properties": { - "path": { - "type": "string", - "readOnly": true - }, - "startItem": { - "$ref": "#/components/schemas/IApiContentStartItemModel" - } - }, - "additionalProperties": false - }, - "IApiContentStartItemModel": { - "type": "object", - "properties": { - "id": { - "type": "string", - "format": "uuid", - "readOnly": true - }, - "path": { - "type": "string", - "readOnly": true - } - }, - "additionalProperties": false - }, - "ProblemDetails": { - "type": "object", - "properties": { - "type": { - "type": "string", - "nullable": true - }, - "title": { - "type": "string", - "nullable": true - }, - "status": { - "type": "integer", - "format": "int32", - "nullable": true - }, - "detail": { - "type": "string", - "nullable": true - }, - "instance": { - "type": "string", - "nullable": true - } - }, - "additionalProperties": { } - } - } - } -} \ No newline at end of file diff --git a/14/umbraco-forms/README.md b/14/umbraco-forms/README.md deleted file mode 100644 index 5709fcb33dc..00000000000 --- a/14/umbraco-forms/README.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -description: >- - Documentation on how to work with Umbraco Forms for both editors and - developers. ---- - -# Umbraco Forms Documentation - -Umbraco Forms is a tool that lets you build forms of all shapes and sizes and put them on your Umbraco websites. Build forms using a long list of elements like multiple choice, dropdowns, text areas and checkboxes. Choose between a series of different workflow and control what happens once a form has been submitted. - -[Purchase Umbraco Forms](https://umbraco.com/products/umbraco-forms/) or sign up for an [Umbraco Cloud](https://try.umbraco.com/) project where Umbraco Forms is part of the package. - -
Installing Umbraco FormsInstall Umbraco Forms in a few steps.install.md_packageBlog_post_for_com_900x400px.png
Creating a FormCreate new Forms and add them to your Umbraco site in minutes.creating-a-formBlog_post_for_com_900x400px_1_8_7_.png
Preparing your FrontendEnsure you have the necessary client dependencies before adding a Form to your site.prepping-frontend.mdUmbraco 9.3RC- Blog_post_for_com_900x400px_1@2x-80.jpg
- -{% embed url="" %} - -## Quick Links - -{% content-ref url="upgrading/manualupgrade.md" %} -[upgrading/manualupgrade.md](upgrading/manualupgrade.md) -{% endcontent-ref %} - -{% content-ref url="editor/attaching-workflows/" %} -[attaching-workflows](editor/attaching-workflows/) -{% endcontent-ref %} - -{% content-ref url="developer/forms-in-the-database.md" %} -[forms-in-the-database.md](developer/forms-in-the-database.md) -{% endcontent-ref %} diff --git a/14/umbraco-forms/SUMMARY.md b/14/umbraco-forms/SUMMARY.md deleted file mode 100644 index 711c3dfbb64..00000000000 --- a/14/umbraco-forms/SUMMARY.md +++ /dev/null @@ -1,76 +0,0 @@ -# Table of contents - -* [Umbraco Forms Documentation](README.md) -* [Legacy Documentation](legacy-documentation.md) -* [Release Notes](release-notes.md) - -## Installation - -* [Installing Umbraco Forms](installation/install.md) -* [Licensing](installation/the-licensing-model.md) - -## Upgrading - -* [Upgrading Umbraco Forms](upgrading/manualupgrade.md) -* [Version Specific Upgrade Notes](upgrading/version-specific.md) -* [Migration IDs](upgrading/migration-ids.md) - -## Editor - -* [Creating a Form - The basics](editor/creating-a-form/README.md) - * [Form Settings](editor/creating-a-form/form-settings.md) - * [Form Information](editor/creating-a-form/form-info.md) - * [Overview Of The Field Types](editor/creating-a-form/fieldtypes/README.md) - * [Date](editor/creating-a-form/fieldtypes/date.md) - * [File Upload](editor/creating-a-form/fieldtypes/fileupload.md) - * [reCAPTCHA V2](editor/creating-a-form/fieldtypes/recaptcha2.md) - * [reCAPTCHA V3](editor/creating-a-form/fieldtypes/recaptcha3.md) - * [Setting-up Conditional Logic on Fields](editor/creating-a-form/conditional-logic.md) -* [Attaching Workflows](editor/attaching-workflows/README.md) - * [Workflow Types](editor/attaching-workflows/workflow-types.md) -* [Viewing And Exporting Entries](editor/viewing-and-exporting-entries.md) -* [Defining And Attaching Prevalue Sources](editor/defining-and-attaching-prevaluesources/README.md) - * [Prevalue Source Types Overview](editor/defining-and-attaching-prevaluesources/prevalue-source-types.md) - -## Developer - -* [Property Editors](developer/property-editors.md) -* [Preparing Your Frontend](developer/prepping-frontend.md) -* [Rendering Forms](developer/rendering-forms.md) -* [Rendering Forms Scripts](developer/rendering-scripts.md) -* [Themes](developer/themes.md) -* [Custom Markup](developer/custom-markup.md) -* [Email Templates](developer/email-templates.md) -* [Working With Record Data](developer/working-with-data.md) -* [Umbraco Forms in the Database](developer/forms-in-the-database.md) -* [Extending](developer/extending/README.md) - * [Adding A Type To The Provider Model](developer/extending/adding-a-type.md) - * [Setting Types](developer/extending/setting-types.md) - * [Adding A Field Type To Umbraco Forms](developer/extending/adding-a-fieldtype.md) - * [Excluding a built-in field](developer/extending/excluding-a-built-in-field.md) - * [Adding A Prevalue Source Type To Umbraco Forms](developer/extending/adding-a-prevaluesourcetype.md) - * [Adding A Workflow Type To Umbraco Forms](developer/extending/adding-a-workflowtype.md) - * [Adding An Export Type To Umbraco Forms](developer/extending/adding-a-exporttype.md) - * [Adding a Magic String Format Function](developer/extending/adding-a-magic-string-format-function.md) - * [Adding A Server-Side Notification Handler To Umbraco Forms](developer/extending/adding-an-event-handler.md) - * [Adding a Validation Pattern](developer/extending/adding-a-validation-pattern.md) - * [Customize Default Fields and Workflows For a Form](developer/extending/customize-default-workflows.md) -* [Configuration](developer/configuration/README.md) - * [Forms Provider Type Details](developer/configuration/type-details.md) -* [Webhooks](developer/webhooks.md) -* [Security](developer/security.md) -* [Magic Strings](developer/magic-strings.md) -* [Health Checks](developer/healthchecks/README.md) - * [Apply keys and indexes](developer/healthchecks/apply-keys.md) - * [Apply keys and indexes for forms in the database](developer/healthchecks/forms-in-the-database-apply-keys.md) -* [Localization](developer/localization.md) -* [Headless/AJAX Forms](developer/ajaxforms.md) -* [Block List Labels](developer/blocklistfilters.md) -* [Field Types](developer/field-types.md) -* [Storing Prevalue Text Files With IPreValueTextFileStorage](developer/iprevaluetextfilestorage.md) - -## Tutorials - -* [Overview](tutorials/overview.md) -* [Creating a Contact Form](tutorials/creating-a-contact-form.md) -* [Creating a Multi-Page Form](tutorials/creating-a-multipage-form.md) diff --git a/14/umbraco-forms/developer/ajaxforms.md b/14/umbraco-forms/developer/ajaxforms.md deleted file mode 100644 index ba1e678dab6..00000000000 --- a/14/umbraco-forms/developer/ajaxforms.md +++ /dev/null @@ -1,600 +0,0 @@ -# Headless/AJAX Forms - -Umbraco Forms provides an API for client-side rendering and submission of forms. This will be useful when you want to handle forms in a headless style scenario. - -## Enabling the API - -The Forms API is disabled by default. To enable it, set the `Umbraco:Forms:Options:EnableFormsApi` configuration key to `true`. - -For example: - -```json - "Umbraco": { - "Forms": { - "Options": { - "EnableFormsApi": true - } - } - } -``` - -## API Definition - -The API supports two endpoints, one for rendering a form and one for submitting it. - -{% swagger src="../.gitbook/assets/umbraco_forms_swagger.json" path="/umbraco/forms/delivery/api/v1/definitions/{id}" method="get" %} -[umbraco_forms_swagger.json](../.gitbook/assets/umbraco_forms_swagger.json) -{% endswagger %} - -{% swagger src="../.gitbook/assets/umbraco_forms_swagger.json" path="/umbraco/forms/delivery/api/v1/entries/{id}" method="post" %} -[umbraco_forms_swagger.json](../.gitbook/assets/umbraco_forms_swagger.json) -{% endswagger %} - -As well as this documentation, the definition of the API can also be reviewed via the Swagger UI. - -This is available alongside the Umbraco 12 Content Delivery Api at: `/umbraco/swagger/index.html`. Select "Umbraco Forms API" from the "Select a definition" list to view the methods available. - -![Swagger UI](images/swagger-ui.png) - -The Open API specification is available from: `/umbraco/swagger/forms/swagger.json` - -### Requesting a Form Definition - -To request the definition of a form, the following request can be made: - -```none -GET /umbraco/forms/delivery/api/v1/definitions/{id}?contentId={contentId}&culture={culture}&additionalData[{key}]={value}&additionalData[key2]={value2} -``` - -The GET request requires the Guid identifying the form. - -An optional `contentId` parameter can be provided, which can either be the integer or GUID identifier for the current page. If provided, the content item identified will be used for Forms features requiring information from the page the form is hosted on. This includes the parsing of ["magic string" placeholders](magic-strings.md). - -A `culture` parameter can also be provided, expected as an ISO code identifying a language used in the Umbraco installation (for example, `en-US`). This will be used to ensure the correct translation for dictionary keys is used. It will also retrieve page content from the appropriate language variant. If the parameter is not provided in the request, the default Umbraco language will be used. - -Finally, an `additionalData` parameter can be provided as a dictionary. This information will be made available when rendering the form allowing it to be used as a source for ["magic string" replacements](./magic-strings.md). - -If the requested form is not found, a 404 status code will be returned. - -A successful request will return a 200 status code. An example response is as follows. It will differ depending on the pages, fields and other settings available for the form. - -```json -{ - "disableDefaultStylesheet": false, - "fieldIndicationType": "MarkMandatoryFields", - "hideFieldValidation": false, - "id": "34ef4a19-efa7-40c1-b8b6-2fd7257f2ed3", - "indicator": "*", - "messageOnSubmit": "Thanks for submitting the form", - "name": "Simple Comment Form", - "nextLabel": "Next", - "pages": [ - { - "caption": "Your comment", - "fieldsets": [ - { - "caption": "", - "columns": [ - { - "caption": "", - "width": 12, - "fields": [ - { - "alias": "name", - "caption": "Name", - "condition": { - "actionType": "Show", - "logicType": "All", - "rules": [] - }, - "helpText": "[#message] from [#pageName]", - "id": "25185934-9a61-491c-9610-83dfe774662c", - "pattern": "", - "patternInvalidErrorMessage": "Please provide a valid value for Name", - "placeholder": "", - "preValues": [], - "required": true, - "requiredErrorMessage": "Please provide a value for Name", - "settings": { - "defaultValue": "", - "placeholder": "Please enter your name.", - "showLabel": "", - "maximumLength": "", - "fieldType": "", - "autocompleteAttribute": "" - }, - "type": { - "id": "3f92e01b-29e2-4a30-bf33-9df5580ed52c", - "name": "Short answer" - } - }, - { - "alias": "email", - "caption": "Email", - "condition": { - "actionType": "Show", - "logicType": "All", - "rules": [] - }, - "helpText": "", - "id": "816fdf3b-a796-4677-a317-943a54bf9d55", - "pattern": "^[_a-z0-9-]+(\\.[_a-z0-9-]+)*@[a-z0-9-]+(\\.[a-z0-9-]+)*(\\.[a-z]{2,4})$", - "patternInvalidErrorMessage": "Please provide a valid value for Email", - "placeholder": "", - "preValues": [], - "required": true, - "requiredErrorMessage": "Please provide a value for Email", - "settings": { - "defaultValue": "", - "placeholder": "", - "showLabel": "", - "maximumLength": "", - "fieldType": "email", - "autocompleteAttribute": "" - }, - "type": { - "id": "3f92e01b-29e2-4a30-bf33-9df5580ed52c", - "name": "Short answer" - } - }, - { - "alias": "comment", - "caption": "Comment", - "condition": { - "actionType": "Show", - "logicType": "All", - "rules": [] - }, - "helpText": "", - "id": "9d723100-ec34-412f-aaa5-516634d7c833", - "pattern": "", - "patternInvalidErrorMessage": "Please provide a valid value for Comment", - "placeholder": "", - "preValues": [], - "required": false, - "requiredErrorMessage": "Please provide a value for Comment", - "settings": { - "defaultValue": "", - "placeholder": "", - "showLabel": "", - "autocompleteAttribute": "", - "numberOfRows": "2", - "maximumLength": "" - }, - "type": { - "id": "023f09ac-1445-4bcb-b8fa-ab49f33bd046", - "name": "Long answer" - } - }, - { - "alias": "country", - "caption": "Country", - "condition": { - "actionType": "Show", - "logicType": "All", - "rules": [] - }, - "helpText": "", - "id": "30ff8f37-28d4-47df-f281-422b36c62e73", - "pattern": "", - "patternInvalidErrorMessage": "Please provide a valid value for Country", - "placeholder": "", - "preValues": [ - { - "caption": "France", - "value": "fr" - }, - { - "caption": "Italy", - "value": "it" - }, - { - "caption": "Span", - "value": "es" - }, - { - "caption": "United Kingdom", - "value": "gb" - } - ], - "required": false, - "requiredErrorMessage": "Please provide a value for Country", - "settings": { - "defaultValue": "", - "allowMultipleSelections": "", - "showLabel": "", - "autocompleteAttribute": "", - "selectPrompt": "Please select" - }, - "type": { - "id": "0dd29d42-a6a5-11de-a2f2-222256d89593", - "name": "Dropdown" - } - }, - { - "alias": "favouriteColour", - "caption": "Favourite Colour", - "condition": { - "actionType": "Show", - "logicType": "All", - "rules": [] - }, - "helpText": "", - "id": "a6e2e27f-097d-476a-edb9-4aa79449ab5c", - "pattern": "", - "patternInvalidErrorMessage": "Please provide a valid value for Favourite Colour", - "placeholder": "", - "preValues": [ - { - "caption": "Red", - "value": "red" - }, - { - "caption": "Green", - "value": "green" - }, - { - "caption": "Yellow", - "value": "yello" - } - ], - "required": false, - "requiredErrorMessage": "Please provide a value for Favourite Colour", - "settings": { - "defaultValue": "", - "showLabel": "" - }, - "type": { - "id": "fab43f20-a6bf-11de-a28f-9b5755d89593", - "name": "Multiple choice" - } - }, - { - "alias": "dataConsent", - "caption": "Data consent", - "condition": { - "actionType": "Show", - "logicType": "All", - "rules": [] - }, - "helpText": "Please indicate if it's OK to store your data.", - "id": "9f25acaf-4ac4-4105-9afe-eb0bb0c03b31", - "pattern": "", - "patternInvalidErrorMessage": "Please provide a valid value for Data consent", - "placeholder": "", - "preValues": [], - "required": true, - "requiredErrorMessage": "Please confirm your data consent", - "settings": { - "acceptCopy": "Yes, I give permission to store and process my data.", - "showLabel": "" - }, - "type": { - "id": "a72c9df9-3847-47cf-afb8-b86773fd12cd", - "name": "Data Consent" - } - }, - { - "alias": "tickToAddMoreInfo", - "caption": "Tick to add more info", - "condition": { - "actionType": "Show", - "logicType": "All", - "rules": [] - }, - "helpText": "", - "id": "6ce0cf78-5102-47c1-85c6-9530d9e9c6a6", - "pattern": "", - "patternInvalidErrorMessage": "Please provide a valid value for Tick to add more info", - "placeholder": "", - "preValues": [], - "required": false, - "requiredErrorMessage": "Please provide a value for Tick to add more info", - "settings": { - "defaultValue": "" - }, - "type": { - "id": "d5c0c390-ae9a-11de-a69e-666455d89593", - "name": "Checkbox" - } - }, - { - "alias": "moreInfo", - "caption": "More info", - "condition": { - "actionType": "Show", - "logicType": "All", - "rules": [ - { - "field": "6ce0cf78-5102-47c1-85c6-9530d9e9c6a6", - "operator": "Is", - "value": "on" - } - ] - }, - "helpText": "", - "id": "5b4100ed-cc5e-4113-943c-ee5a8f4e448d", - "pattern": "", - "patternInvalidErrorMessage": "Please provide a valid value for More info", - "placeholder": "", - "preValues": [], - "required": false, - "requiredErrorMessage": "Please provide a value for More info", - "settings": { - "defaultValue": "", - "placeholder": "", - "showLabel": "", - "maximumLength": "", - "fieldType": "", - "autocompleteAttribute": "" - }, - "type": { - "id": "3f92e01b-29e2-4a30-bf33-9df5580ed52c", - "name": "Short answer" - } - } - ], - "width": 0 - } - ], - "id": "d677b96f-488d-4052-b00d-fb852b35e9c5" - } - ] - } - ], - "previousLabel": "Previous", - "showValidationSummary": false, - "submitLabel": "Submit" -} -``` - -It's possible to define either a message displayed when a form is submitted, or a redirect to another website page. - -With the former, the output will be as above, and as shown in this extract: - -```json -{ - ... - "messageOnSubmit": "Thanks for submitting the form", - ... -} -``` - -When a redirect is configured, details of the content ID and a route will be included, as follows: - -```json -{ - ... - "gotoPageOnSubmit": "eab72f13-b22e-46d5-b270-9c196e49a53b", - "gotoPageOnSubmitRoute": { - "path": "/contact-us/thanks/", - "startItem": { - "id": "ca4249ed-2b23-4337-b522-63cabe5587d1", - "path": "home" - } - }, - ... -} -``` - -### Submitting a Form Entry - -To submit a form entry, the following request can be made: - -```none -POST /umbraco/forms/delivery/api/v1/entries/{id} -``` - -The POST request requires the Guid identifying the form. - -It also requires a `Content-Type` header of `application/json` and accepts a body as per this example: - -```json -{ - "values": { - "name": "Fred", - "email": "fred@test.com", - "comment": "Test", - "country": "it", - "favouriteColours": ["red", "green"], - "dataConsent": "on" - }, - "contentId": "ca4249ed-2b23-4337-b522-63cabe5587d1", - "culture": "en-US", - "additionalData": { - "foo": "bar", - "baz": "buzz", - } -} -``` - -The `values` collection consists of a set of name/value pairs, where the name is the alias of a form field. The value is the value of the submitted field, which can either be a string, or an array of strings. In this way we support fields that accept multiple values, such as checkbox lists. - -The `contentId` and `culture` parameters are optional. If provided they will be used to customize the response for the current page and language respectively. - -Similarly the `additionalData` dictionary is optional. This data is associated with the created record and made available within workflows. - -In the case of a validation error, a 422 "Unprocessable Entity" status code will be returned, along with a response similar to the following: - -```json -{ - "errors": { - "name": [ - "Please provide a value for Name" - ] - }, - "extensions": {}, - "status": 422, - "title": "One or more validation errors occurred." -} -``` - -A successful response will return a 202 "Accepted" status code. - -It will contain an object detailing the post-submission configured the form, for example: - -```json -{ - "gotoPageOnSubmit": "3cce2545-e3ac-44ec-bf55-a52cc5965db3", - "gotoPageOnSubmitRoute": { - "path": "/about-us/", - "startItem": { - "id": "ca4249ed-2b23-4337-b522-63cabe5587d1", - "path": "home" - } - }, - "messageOnSubmit": "Thanks for your entry", - "messageOnSubmitIsHtml": false -} -``` - -#### File Uploads - -The file upload field type is supported via the API for the rendering and submission of forms. - -When retrieving a form definition, some additional detail is provided for fields of this type to allow for the appropriate rendering of the form interface: - -```json - ... - "fields": [ - { - "alias": "uploadAPicture", - ... - "fileUploadOptions": { - "allowAllUploadExtensions": false, - "allowedUploadExtensions": [ - "png", - "jpg", - "gif" - ], - "allowMultipleFileUploads": false - }, - } - ] - ... -``` - -When submitting a form, the value should be a JSON structure that provides a collection. Each item in the collection should contain the file name and the file contents as a base64 encoded data URL. - -```json -{ - "values": { - "uploadAPicture": [ - { - "fileName": "mypic.jpg", - "fileContents": "data:image/png;base64,iVBORw..." - } - ] - }, -} -``` - -## Securing the API - -### Antiforgery Protection - -When posting forms in the traditional way, via a full page post back, an anti-forgery token is generated and validated. This provides protection against Cross-Site Request Forgery (CSRF) attacks. - -The same protection is available for forms submitted via AJAX techniques. - -In order to generate the token and provide it in the form post, the following code can be applied to the .cshtml template: - -```csharp -@using Microsoft.AspNetCore.Antiforgery - -@inject IAntiforgery antiforgery - -@{ - var tokenSet = antiforgery.GetAndStoreTokens(Context); -} -``` - -When posting the form, the header value generated can be provided, where it will be validated server-side before accepting the request. - -```javascript - let response = await fetch("/umbraco/forms/delivery/api/v1/entries/" + formId, { - method: "POST", - headers: { - "Content-Type": "application/json", - "@tokenSet.HeaderName" : "@tokenSet.RequestToken" - }, - body: JSON.stringify(data), - }); -``` - -### API Key - -The antiforgery token security approach is valid when building a client-side integration with API calls made from the browser. - -Providing the token isn't possible though in other headless situations such as server-to-server requests. In these situations, an alternative approach to securing the API is available. - -Firstly, with server-to-server integrations you will want to disable the antiforgery token protection. - -This is done by setting the `Umbraco:Forms:Security:EnableAntiForgeryTokenForFormsApi` configuration key to a value of `false`. - -You should then configure an API key `Umbraco:Forms:Security:FormsApiKey`. This can be any string value, but it should be complex enough to resist being guessed by a brute force attack. - -With this in place any request to the Forms API will be rejected unless the configured value is provided in an HTTP header named `Api-Key`. - -## Rendering and Submitting forms with JavaScript - -For an illustrative example showing how a form can be rendered, validated and submitted using the API and vanilla JavaScript, please [see this gist](https://gist.github.com/AndyButland/9371175d6acf24a5307b053398f08448). - -Examples demonstrating how to handle a file upload and use reCAPTCHA fields are included. - -## Working with the CMS Content Delivery API - -The [Content Delivery API](https://docs.umbraco.com/umbraco-cms/v/12.latest/reference/content-delivery-api) provides headless capabilities within Umbraco by allowing you to retrieve content in JSON format. - -When retrieving content that contains an Umbraco Forms form picker, the output by default will consist of the ID of the selected form: - -```json -{ - "name": "Contact Us", - "route": { - "path": "/contact-us/", - "startItem": { - "id": "ca4249ed-2b23-4337-b522-63cabe5587d1", - "path": "home" - } - }, - "id": "4a1f4198-e143-48ba-a0f5-1a7ef2df23aa", - "contentType": "contactPage", - "properties": { - "title": "Contact Us", - "contactForm": { - "id": "3623b232-9296-4bf0-b16c-57801dc4f296", - "form": null - } - } -} -``` - -With [expanded output](https://docs.umbraco.com/umbraco-cms/v/12.latest/reference/content-delivery-api#output-expansion) for the property, the full details of the form will be available. The structure and content of the form representation will be exactly the same as that provided by the Forms API itself. - -```json -{ - "name": "Contact Us", - "route": { - "path": "/contact-us/", - "startItem": { - "id": "ca4249ed-2b23-4337-b522-63cabe5587d1", - "path": "home" - } - }, - "id": "4a1f4198-e143-48ba-a0f5-1a7ef2df23aa", - "contentType": "contactPage", - "properties": { - "title": "Contact Us", - "contactForm": { - "id": "3623b232-9296-4bf0-b16c-57801dc4f296", - "form": { - "id": "3623b232-9296-4bf0-b16c-57801dc4f296", - "name": "Contact Form", - ... - "pages": [ ... ] - } - } - } -} -``` diff --git a/14/umbraco-forms/developer/blocklistfilters.md b/14/umbraco-forms/developer/blocklistfilters.md deleted file mode 100644 index c522271a943..00000000000 --- a/14/umbraco-forms/developer/blocklistfilters.md +++ /dev/null @@ -1,27 +0,0 @@ -# Block List Labels - -When working with the Block List editor, [the editor experience is enhanced](https://docs.umbraco.com/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/block-editor/block-list-editor#editor-appearance) by defining a label for the appearance of the Block. - -These labels can use [Umbraco Flavored Markdown (UFM)](https://docs.umbraco.com/umbraco-cms/reference/umbraco-flavored-markdown). - -An option is available to display a form's name - `umbFormName`. - -It should be rendered as follows, with a reference to the property alias on the block element that uses a form picker. - -``` -{umbFormName: } -``` - -If you add a reference to a property containing a form to the block's label, it will render with the form's Id. - -For example, assuming a property containing a picked form with an alias of `contactForm`: - -``` -{=contactForm} -``` - -By using the markdown as follows, the form's name will be displayed instead. - -``` -{umbFormName: contactForm} -``` diff --git a/14/umbraco-forms/developer/configuration/README.md b/14/umbraco-forms/developer/configuration/README.md deleted file mode 100644 index c6dde0aedbe..00000000000 --- a/14/umbraco-forms/developer/configuration/README.md +++ /dev/null @@ -1,571 +0,0 @@ ---- -description: >- - In Umbraco Forms it's possible to customize the functionality with various - configuration values. ---- - -# Configuration - -With Umbraco Forms it's possible to customize the functionality with various configuration values. - -## Editing configuration values - -All configuration for Umbraco Forms is held in the `appSettings.json` file found at the root of your Umbraco website. If the configuration has been customized to use another source, then the same keys and values discussed in this article can be applied there. - -The convention for Umbraco configuration is to have package based options stored as a child structure below the `Umbraco` element, and as a sibling of `CMS`. Forms configuration follows this pattern, i.e.: - -```json -{ - ... - "Umbraco": { - "CMS": { - ... - }, - "Forms": { - ... - } - } -} -``` - -All configuration for Forms is optional. In other words, all values have defaults that will be applied if no configuration is available for a particular key. - -For illustration purposes, the following structure represents the full set of options for configuration of Forms, along with the default values. This will help when you need to provide a different setting to understand where it should be applied. - -```json - "Forms": { - "FormDesign": { - "DisableAutomaticAdditionOfDataConsentField": false, - "DisableDefaultWorkflow": false, - "MaxNumberOfColumnsInFormGroup": 12, - "DefaultTheme": "default", - "DefaultEmailTemplate": "Forms/Emails/Example-Template.cshtml", - "Defaults": { - "ManualApproval": false, - "DisableStylesheet": false, - "MarkFieldsIndicator": "NoIndicator", - "Indicator": "*", - "RequiredErrorMessage": "Please provide a value for {0}", - "InvalidErrorMessage": "Please provide a valid value for {0}", - "ShowValidationSummary": false, - "HideFieldValidationLabels": false, - "NextPageButtonLabel": "Next", - "PreviousPageButtonLabel": "Previous", - "SubmitButtonLabel": "Submit", - "MessageOnSubmit": "Thank you", - "StoreRecordsLocally": true, - "AutocompleteAttribute": "", - "DaysToRetainSubmittedRecordsFor": 0, - "DaysToRetainApprovedRecordsFor": 0, - "DaysToRetainRejectedRecordsFor": 0, - "ShowPagingOnMultiPageForms": "None", - "PagingDetailsFormat": "Page {0} of {1}", - "PageCaptionFormat": "Page {0}", - "ShowSummaryPageOnMultiPageForms": false, - "SummaryLabel": "Summary of Entry" - }, - "RemoveProvidedEmailTemplate": false, - "RemoveProvidedFormTemplates": false, - "FormElementHtmlIdPrefix": "", - "SettingsCustomization": { - "DataSourceTypes": {}, - "FieldTypes": {}, - "PrevalueSourceTypes": {}, - "WorkflowTypes": {}, - }, - "MandatoryFieldsetLegends": false - }, - "Options": { - "IgnoreWorkFlowsOnEdit": "True", - "AllowEditableFormSubmissions": false, - "AppendQueryStringOnRedirectAfterFormSubmission": false, - "CultureToUseWhenParsingDatesForBackOffice": "", - "TriggerConditionsCheckOn": "change", - "ScheduledRecordDeletion": { - "Enabled": false, - "FirstRunTime": "", - "Period": "1.00:00:00" - }, - "DisableRecordIndexing": false, - "EnableFormsApi": false, - "EnableRecordingOfIpWithFormSubmission": false, - "UseSemanticFieldsetRendering": false, - "DisableClientSideValidationDependencyCheck": false, - "DisableRelationTracking": false, - "TrackRenderedFormsStorageMethod": "HttpContextItems", - "EnableMultiPageFormSettings": false - }, - "Security": { - "DisallowedFileUploadExtensions": "config,exe,dll,asp,aspx", - "AllowedFileUploadExtensions": "", - "EnableAntiForgeryToken": true, - "SavePlainTextPasswords": false, - "DisableFileUploadAccessProtection": false, - "DefaultUserAccessToNewForms": "Grant", - "ManageSecurityWithUserGroups": false, - "GrantAccessToNewFormsForUserGroups": "admin,editor", - "FormsApiKey": "", - "EnableAntiForgeryTokenForFormsApi": true, - }, - "FieldTypes": { - "DatePicker": { - "DatePickerYearRange": 10, - "DatePickerFormat": "LL", - "DatePickerFormatForValidation": "" - }, - "Recaptcha2": { - "PublicKey": "", - "PrivateKey": "" - }, - "Recaptcha3": { - "SiteKey": "", - "PrivateKey": "", - "Domain": "Google", - "VerificationUrl": "https://www.google.com/recaptcha/api/siteverify", - "ShowFieldValidation": false - }, - "RichText": { - "DataTypeId": "ca90c950-0aff-4e72-b976-a30b1ac57dad" - }, - "TitleAndDescription": { - "AllowUnsafeHtmlRendering": false - } - } - } -``` - -## Form design configuration - -### DisableAutomaticAdditionOfDataConsentField - -This configuration value expects a `true` or `false` value and can be used to disable the feature where all new forms are provided with a default "Consent for storing submitted data" field on creation. Defaults to `false`. - -### DisableDefaultWorkflow - -This configuration value expects a `true` or `false` value and can be used to toggle if new forms that are created adds an email workflow to send the result of the form to the current user who created the form. Defaults to `false`. - -### MaxNumberOfColumnsInFormGroup - -This setting controls the maximum number of columns that can be created by editors when they configure groups within a form. The default value used if the setting value is not provided is 12. - -### DefaultTheme - -This setting allows you to configure the name of the theme to use when an editor has not specifically selected one for a form. If empty or missing, the default value of "default" is used. If a custom default theme is configured, it will be used for rendering forms where the requested file exists, and where not, will fall back to the out of the box default theme. - -### DefaultEmailTemplate - -When creating an empty form, a single workflow is added that will send an email to the current user's address. By default, the template shipped with Umbraco Forms is available at `Forms/Emails/Example-Template.cshtml` is used. - -If you have created a custom template and would like to use that as the default instead, you can set the path here using this configuration setting. - -### RemoveProvidedEmailTemplate - -The provided template can be removed from the selection if you have created email templates for the "send Razor email" workflow. To do this, set this value to `true`. - -### RemoveProvidedFormTemplates - -Similarly, the provided form templates available from the form creation dialog can be removed from selection. To do this, set this configuration value to `true`. - -### FormElementHtmlIdPrefix - -By default the value of HTML `id` attribute rendered for fieldsets and fields using the default theme is the GUID associated with the form element. Although [this is valid](https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/id), some browsers, particularly Safari, may report issues with this if the identifier begins with a number. To avoid such issues, the attribute values can be prefixed with the value provided in this configuration element. - -For example, providing a value of `"f_"` will apply a prefix of "f\_" to each fieldset and field `id` attribute. - -### SettingsCustomization - -Forms introduced the ability to configure settings for the field, workflow, data source, and prevalue sources. The default behavior, when a new field or workflow is added to a form, is for each setting to be empty. The values are then completed by the editor. All settings defined on the type are displayed for entry. - -In some situations, you may want to hide certain settings from entry, so they always take an empty value. In others, you may want to provide a default value that the editor can accept or amend. And lastly, you may have a requirement for a fixed, non-empty value, that's enforced by the organization and not editable. Each of these scenarios can be supported by this configuration setting. - -It consists of four dictionaries, one for each type: - -* `DataSourceTypes` -* `FieldTypes` -* `PrevalueSourceTypes` -* `WorkflowTypes` - -Each dictionary can be identified using the GUID or alias of the type as the key. The value is set to the following structure that contains three settings: - -```json -{ - "IsHidden": true|false, - "DefaultValue": "", - "IsReadOnly": true|false -} -``` - -* `IsHidden` - if provided and set to true the setting will be hidden and will always have an empty value. -* `DefaultValue` - if provided the value will be pre-filled when a type using it is created. -* `IsReadOnly` - used in conjunction with the above, if set the field won't be editable and hence whatever is set as the `DefaultValue` won't be able to be changed. If set to false (or omitted) the editor can change the value from the default. - -In this example, the sender address field on a workflow for sending emails can be hidden, such that the system configured value is always used: - -```json - "SettingsCustomization": { - "WorkflowTypes": { - "sendEmailWithRazorTemplate": { - "SenderEmail": { - "IsHidden": true - } - } - }, - } -``` - -Here an organization-approved reCAPTCHA score threshold is defined, that can't be changed by editors: - -```json - "SettingsCustomization": { - "FieldTypes": { - "recaptcha3": { - "ScoreThreshold": { - "DefaultValue": "0.8", - "IsReadOnly": true - } - } - }, - } -``` - -In order to configure this setting, you will need to know the GUID or alias for the type and the property name for each setting. You can find [these values for the built-in Forms types here](type-details.md). - -Take care to not hide any settings that are required for the particular field or workflow type (for example, the `Subject` field for email workflows). If you do that, the item will fail validation when an editor tries to create it. - -The default value and read-only settings apply to most setting types. There is an exception for complex ones where a default string value isn't appropriate. An example of one of these is the field mapper used in the "Send to URL" workflow. - -### MandatoryFieldsetLegends - -When creating a form with Umbraco Forms, adding captions to the groups for fields is optional. To follow accessibility best practices, these fields should be completed. When they are, the group of fields are presented within a `
` element that has a populated ``. - -If you want to ensure form creators always have to provide a caption, you can set the value of this setting to `true`. - -### Form default settings configuration - -The following configured values are applied to all forms as they are created. They can then be amended on a per-form basis via the Umbraco backoffice. - -Once the form has been created, the values are set explicitly on the form, so subsequent changes to the defaults in configuration won't change the settings used on existing forms. - -#### ManualApproval - -This setting needs to be a `true` or `false` value and will allow you to toggle if a form allows submissions to be post moderated. Most use cases are for publicly shown entries such as blog post comments or submissions for a social campaign. Defaults to `false`. - -#### DisableStylesheet - -This setting needs to be a `true` or `false` value and will allow you to toggle if the form will include some default styling with the Umbraco Forms CSS stylesheet. Defaults to `false`. - -#### MarkFieldsIndicator - -This setting can have the following values to allow you to toggle the mode of marking mandatory or optional fields: - -* `NoIndicator` (default) -* `MarkMandatoryFields` -* `MarkOptionalFields` - -#### Indicator - -This setting is used to mark the mandatory or optional fields based on the setting above. By default this is an asterisk `*`. - -#### RequiredErrorMessage - -This allows you to configure the required error validation message. By default this is `Please provide a value for {0}` where the `{0}` is used to replace the name of the field that is required. - -#### InvalidErrorMessage - -This allows you to configure the invalid error validation message. By default this is `Please provide a valid value for {0}` where the `{0}` is used to replace the name of the field that is invalid. - -#### ShowValidationSummary - -This setting needs to be a `true` or `false` value and will allow you to toggle if the form will display all form validation error messages in a validation summary together. Defaults to `false`. - -#### HideFieldValidationLabels - -This setting needs to be a `true` or `false` value and will allow you to toggle if the form will show inline validation error messages next to the form field that is invalid. Defaults to `false`. - -#### NextPageButtonLabel, PreviousPageButtonLabel, SubmitButtonLabel - -These settings configure the default next, previous, and submit button labels. By default, these are `Next`, `Previous`, and `Submit` respectively. These labels can be amended on a form-by-form basis via the form's **Settings** section. - -#### MessageOnSubmit - -This allows you to configure what text is displayed when a form is submitted and is not being redirected to a different content node. Defaults to `Thank you`. - -#### StoreRecordsLocally - -This setting needs to be a `True` or `False` value and will allow you to toggle if form submission data should be stored in the Umbraco Forms database tables. By default this is set to `True`. - -#### AutocompleteAttribute - -This setting provides a value to be used for the `autocomplete` attribute for newly created forms. By default the value is empty, but can be set to `on` or `off` to have that value applied as the attribute value used when rendering the form. - -#### DaysToRetainSubmittedRecordsFor - -Introduced in 10.2, this setting controls the initial value of the number of days to retain form submission records for newly created forms. By default the value is 0, which means records will not be deleted at any time and are retained forever. - -If set to a positive number, a date value calculated by taking away the number of days configured from the current date is found. Records in the 'submitted' state, that are older than this date, will be flagged for removal. - -#### DaysToRetainApprovedRecordsFor - -Applies as per `DaysToRetainSubmittedRecordsFor` but for records in the 'approved' state. - -#### DaysToRetainRejectedRecordsFor - -Applies as per `DaysToRetainSubmittedRecordsFor` but for records in the 'rejected' state. - -### ShowPagingOnMultiPageForms - -Defines whether and where paging details are displayed for multi-page forms. - -### PagingDetailsFormat - -Defines the paging details format for multi-page forms. - -### PageCaptionFormat - -Defines the page caption format for multi-page forms. - -### ShowSummaryPageOnMultiPageForms - -Defines whether summary pages are on by default for multi-page forms. - -### SummaryLabel - -Defines the default summary label for multi-page forms. - -## Package options configuration - -### IgnoreWorkFlowsOnEdit - -This configuration expects a `True` or `False` string value, or a comma-separated list of form names, and allows you to toggle if a form submission is edited again, that the workflows on the form will re-fire after an update to the form submission. This is used in conjunction with the `AllowEditableFormSubmissions` configuration value. Defaults to `True`. - -### AllowEditableFormSubmissions - -This configuration value expects a `true` or `false` value and can be used to toggle the functionality to allow a form submission to be editable and re-submitted. When the value is set to `true` it allows Form Submissions to be edited using the following querystring for the page containing the form on the site. `?recordId=GUID` Replace `GUID` with the GUID of the form submission. Defaults to `false`. - -{% hint style="info" %} -There was a typo in this setting where it had been named as `AllowEditableFormSubmissions`. This is the name that needs to be used in configuration for Forms 9. In Forms 10 this was be corrected to the now documented value of `AllowEditableFormSubmissions`. -{% endhint %} - -{% hint style="warning" %} -Enable this feature ONLY if you understand the security implications. -{% endhint %} - -### AppendQueryStringOnRedirectAfterFormSubmission - -When redirecting following a form submission, a `TempData` value is set that is used to ensure the submission message is displayed rather than the form itself. In certain situations, such as hosting pages with forms in IFRAMEs from other websites, this value is not persisted between requests. - -By setting the following value to True, a querystring value of `formSubmitted=`, will be used to indicate a form submitted on the previous request. - -### CultureToUseWhenParsingDatesForBackOffice - -This setting has been added to help resolve an issue with multi-lingual setups. - -When Umbraco Forms stores data for a record, it saves the values submitted for each field into a dedicated table for each type (string, date etc.). It also saves a second copy of the record in a JSON structure which is more suitable for fast look-up and display in the backoffice. Date values are serialized using the culture used by the front-end website when the form entry is stored. - -When displaying the data in the backoffice, the date value needs to be parsed back into an actual date object for formatting. And this can cause a problem if the backoffice user is using a different language, and hence culture setting, than that used when the value was stored. - -The culture used when storing the form entry is recorded, thus we can ensure the correct value is used when parsing the date. However, this doesn't help for historically stored records. To at least partially mitigate the problem, when you have editors using different languages to a single language presented on the website front-end, you can set this value to match the culture code used on the website. This ensures the date fields in the backoffice are correctly presented. - -Taking an example of a website globalization culture code setting of "en-US" (and a date format of `m/d/y`), but an editor uses "en-GB" (which formats dates as of `d/m/y`). By setting the value of this configuration key to "en-US", you can ensure that the culture when parsing dates for presentation in the backoffice will match that used when the value was stored. - -If no value is set, and no culture value was stored alongside the form entry, the culture based on the language associated with the current backoffice user will be used. - -### TriggerConditionsCheckOn - -This configuration setting provides control over the client-side event used to trigger conditions. The `change` event is the default used if this setting is empty. It can also be set to a value of `input`. The main difference seen here relates to text fields, with the "input" event firing on each key press, and the "change" only when the field loses focus. - -### ScheduledRecordDeletion - -Scheduled deletion of records older than a specified number of days. It uses a background task to run the cleanup operation, which can be customized with the following settings. - -#### Enabled - -By default this value is `false` and no data will be removed. Even if forms are configured to have submitted data cleaned up, no records will be deleted. A note will be displayed in the backoffice indicating this status. - -Set to `true` to enabled the background task. - -#### FirstRunTime - -This will configure when the record deletion process will run for the first time. If the value is not configured the health checks will run after a short delay following the website start. The value is specified as a string in crontab format. For example, a value of `"* 4 * * *"` will first run the operation at 4 a.m. - -#### Period - -Defines how often the record deletion process will run. The default value is `1.00:00:00` which is equivalent to once every 24 hours. Shorter or longer periods can be set using different datetime strings. - -### DisableRecordIndexing - -Set this value to `true` to disable the default behavior of indexing the form submissions into the Examine index. - -If indexing has already occurred, you will still need to manually remove the files (found in `App_Data\TEMP\ExamineIndexes\UmbracoFormsRecords`). They will be recreated if indexing is subsequently re-enabled. - -### EnableFormsApi - -Set this value to `true` to enable the Forms API supporting headless and AJAX forms. - -### EnableRecordingOfIpWithFormSubmission - -By default, the user's IP address is not recorded when a form is submitted and stored in the `UFRecords` database table. - -To include this information in the saved data, set this value to `true`. - -If recording IPs and your site is behind a proxy, load balancer or CDN, we recommend using [ASP.NET's forwarded headers middleware](https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/proxy-load-balancer?view=aspnetcore-7.0) to ensure the correct value for the client IP is resolved. - -### UseSemanticFieldsetRendering - -In Forms 12.1 amends were made to the default theme for Forms that improved accessibility. Specifically we provide the option to use alternative markup for rendering checkbox and radio button lists. These use the more semantically correct `fieldset` and `legend` elements, instead of the previously used `div` and `label`. - -Although this semantic markup is preferred, it could be a presentational breaking change for those styling the default theme. As such we have made this markup improvement optional. You can opt into using it by setting this configuration value to `true`. - -In Umbraco 13 this configuration option will be removed and the semantic rendering made the only option. - -### DisableClientSideValidationDependencyCheck - -When a form is rendered on the front-end website, a check is run to ensure that client-side validation framework is available and registered. - -You can disable this check by setting the value of this configuration key to `true`. - -If you are rendering your forms dependency scripts using the `async` attribute, you will need to disable this check. - -### DisableRelationTracking - -Forms will by default track relations between forms and the content pages they are used on. This allows editors to see where forms are being used in their Umbraco website. - -If you would like to disable this feature, you can set the value of this setting to `true`. - -## TrackRenderedFormsStorageMethod - -Forms tracks the forms rendered on a page in order that the associated scripts can be placed in a different location within the HTML. Usually this is used to [render the scripts](../rendering-scripts.md)) at the bottom of the page. - -By default, `HttpContext.Items` is used as the storage mechanism for this tracking. - -You can optionally revert to the legacy behavior of using `TempData` by changing this setting from the default of `HttpContextItems` to `TempData`. - -## EnableMultiPageFormSettings - -This setting determines whether [multi-page form settings](../../editor/creating-a-form/form-settings.md#multi-page-forms) are available to editors. - -By default the value is `false`. This ensures that, in an upgrade scenario, before the feature is used the necessary styling and/or theme updates can be prepared. - -To make the feature available to editors set the value to `true`. - -## Security configuration - -### DisallowedFileUploadExtensions - -When using the File Upload field in a form, editors can choose which file extensions they want to accept. When an image is expected, they can for example specify that only `.jpg` or `.png` files are uploaded. - -There are certain file extensions that in almost all cases should never be allowed, which are held in this configuration value. This means that even if an editor has selected to allow all files, any files that match the extensions listed here will be blocked. - -By default, .NET related code files like `.config` and `.aspx` are included in this deny list. You can add or - if you are sure - remove values from this list to meet your needs. - -### AllowedFileUploadExtensions - -For further control, an "allow list" of extension can be provided via this setting. If provided, only the extensions entered as a comma separated list here will be accepted in file uploads through forms. - -### EnableAntiForgeryToken - -This setting needs to be a `true` or `false` value and will enable the ASP.NET Anti Forgery Token and we recommend that you enable this option. Defaults to `true`. - -In certain circumstances, including hosting pages with forms in IFRAMEs from other websites, this may need to be set to `false`. - -### SavePlainTextPasswords - -This setting needs to be a `true` or `false` value and controls whether password fields provided in forms will be saved to the database. Defaults to `false`. - -### DisableFileUploadAccessProtection - -Protection was added to uploaded files to prevent users from accessing them if they aren't logged into the backoffice and have permission to manage the form for which the file was submitted. As a policy of being "secure by default", the out of the box behavior is that this access protection is in place. - -If for any reason you need to revert to the previous behavior, or have other reasons where you want to permit unauthenticated users from accessing the files, you can turn off this protection by setting this configuration value to `true`. - -### DefaultUserAccessToNewForms - -This setting was added to add control over access to new forms. The default behavior is for all users to be granted access to newly created forms. To amend that to deny access, the setting can be updated to a value of `Deny`. A value of `Grant` or configuration with the setting absent preserves the default behavior. - -### ManageSecurityWithUserGroups - -Ability to administer access to Umbraco Forms using Umbraco's user groups. This can be used instead or in addition to the legacy administration which is at the level of the individual user. Set this option to `true` to enable the user group permission management functionality. - -### GrantAccessToNewFormsForUserGroups - -This setting takes a comma-separated list of user group aliases which will be granted access automatically to newly created forms. This setting only takes effect when `ManageSecurityWithUserGroups` is set to `true`. - -There are two "special" values that can be applied within or instead of the comma-separated list. - -A value of `all` will give access to the form to all user groups. - -A value of `form-creator` will give access to all the user groups that the user who created the form is part of. - -### FormsApiKey and EnableAntiForgeryTokenForFormsApi - -Available from Forms 10.2.1, the `FormsApiKey` configuration setting can be used to secure the Forms Headless API in server-to-server integrations. When set, API calls will be rejected unless the value of this setting is provided in an HTTP header. - -Setting the value of `EnableAntiForgeryTokenForFormsApi` to `false` will disable the anti-forgery protection for the Forms Headless/AJAX API. You need to do this for server-to-server integrations where it's not possible to provide a valid anti-forgery token in the request. - -For more information, see the [Headless/AJAX Forms](../ajaxforms.md) article. - -## Field type specific configuration - -### Date picker field type configuration - -#### DatePickerYearRange - -This setting is used to configure the Date Picker form field range of years that is available in the date picker. By default this is a small range of 10 years. - -#### DatePickerFormat - -A custom date format can be provided in [momentjs format](https://momentjscom.readthedocs.io/en/latest/moment/01-parsing/03-string-format/) if you want to override the default. - -#### DatePickerFormatForValidation - -If a custom date format is provided it will be used on the client-side. A matching string in [C# date format](https://learn.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings) should be provided, so that server-side validation will match the expected format of the entry. - -### reCAPTCHA v2 field type configuration - -#### PublicKey & PrivateKey - -Both of these configuration values are needed in order to use the "_Recaptcha2_" field type implementing legacy ReCaptcha V2 from Google. You can obtain both of these values after signing up to create a ReCaptcha key here - [https://www.google.com/recaptcha/admin](https://www.google.com/recaptcha/admin) - -Google has renamed these recently and the `Site Key` refers to `RecaptchaPublicKey` and `Secret Key` is to be used for `RecaptchaPrivateKey` - -### reCAPTCHA v3 field type configuration - -#### SiteKey & PrivateKey - -Both of these configuration values are needed in order to use the "_reCAPTCHA V3 with Score_" field type implementing ReCaptcha V3 from Google. - -You can obtain both of these values after signing up to create a ReCaptcha key here: [https://www.google.com/recaptcha/admin](https://www.google.com/recaptcha/admin). - -#### Domain - -This setting defines the domain from which the client-side assets for using the reCAPTCHA service are requested. - -Valid options are `Google` (the default) or `Recaptcha`. You may want to use the latter for control of which domains are setting cookies on your site. [Read more at the reCAPTCHA documentation](https://developers.google.com/recaptcha/docs/faq#does-recaptcha-use-cookies). - -#### VerificationUrl - -By default, the server-side validation of the reCAPTCHA response is sent to Google's servers at `https://www.google.com/recaptcha/api/siteverify`. - -Some customers with a locked-down production environment cannot configure the firewall to allow these requests and instead use a proxy server. They can use this setting to configure the URL to their proxy server, which will relay the request to and response from Google. - -#### ShowFieldValidation - -By default the validation message returned from a failed reCAPTCHA 3 request will be displayed only in the form level validation summary. - -To render also at a field level, set this value to `true`. - -We expect to make the default value for this option `true` in Umbraco Forms 15. - -### Rich text field type configuration - -#### DataTypeId - -Sets the Data Type Guid to use to obtain the configuration for the rich text field type. If the setting is absent, the value of the default rich text Data Type created by Umbraco on a new install is used. - -### Title and description field type configuration - -#### AllowUnsafeHtmlRendering - -When using the "title and description" field type, if editors provide HTML in the "description" field it will be encoded when rendering on the website. - -If you understand the risks and want to allow HTML to be displayed, you can set this value to `false`. diff --git a/14/umbraco-forms/developer/configuration/type-details.md b/14/umbraco-forms/developer/configuration/type-details.md deleted file mode 100644 index 3ea7f40e003..00000000000 --- a/14/umbraco-forms/developer/configuration/type-details.md +++ /dev/null @@ -1,528 +0,0 @@ ---- -description: "Provides details of the built-in provider types available with Umbraco Forms" ---- - -# Forms Provider Type Details - -This page provides some details of the provider types available in Umbraco Forms. - -The intention is to be able to make available details such as IDs, aliases and property names, that may be necessary when configuring the product. - -## Field Types - -
- -Checkbox - -**ID:** `D5C0C390-AE9A-11DE-A69E-666455D89593` - -**Alias:** `checkbox` - -**Settings:** - -* `Caption` -* `DefaultValue` -* `ShowLabel` - -
- -
- -Data Consent - -**ID:** `A72C9DF9-3847-47CF-AFB8-B86773FD12CD` - -**Alias:** `dataConsent` - -**Settings:** - -* `AcceptCopy` -* `ShowLabel` - -
- -
- -Date - -**ID:** `F8B4C3B8-AF28-11DE-9DD8-EF5956D89593` - -**Alias:** `date` - -**Settings:** - -* `Placeholder` -* `ShowLabel` -* `AriaLabel` - -
- -
- -Dropdown List - -**ID:** `0DD29D42-A6A5-11DE-A2F2-222256D89593` - -**Alias:** `dropdown` - -**Settings:** - -* `DefaultValue` -* `AllowMultipleSelections` -* `ShowLabel` -* `AutocompleteAttribute` -* `SelectPrompt` - -
- -
- -File Upload - -**ID:** `84A17CF8-B711-46a6-9840-0E4A072AD000` - -**Alias:** `fileUpload` - -**Settings:** - -* `SelectedFilesListHeading` - -
- -
- -Long Answer - -**ID:** `023F09AC-1445-4bcb-B8FA-AB49F33BD046` - -**Alias:** `longAnswer` - -**Settings:** - -* `DefaultValue` -* `Placeholder` -* `ShowLabel` -* `AutocompleteAttribute` -* `NumberOfRows` -* `MaximumLength` - -
- -
- -Hidden Field - -**ID:** `DA206CAE-1C52-434E-B21A-4A7C198AF877` - -**Alias:** `hidden` - -**Settings:** - -* `DefaultValue` - -
- -
- -Multiple Choice - -**ID:** `FAB43F20-A6BF-11DE-A28F-9B5755D89593` - -**Alias:** `multipleChoice` - -**Settings:** - -* `DisplayLayout` -* `DefaultValue` -* `ShowLabel` - -
- -
- -Password - -**ID:** `FB37BC60-D41E-11DE-AEAE-37C155D89593` - -**Alias:** `password` - -**Settings:** - -* `Placeholder` - -
- -
- -reCAPTCHA 2 - -**ID:** `B69DEAEB-ED75-4DC9-BFB8-D036BF9D3730` - -**Alias:** `recaptcha2` - -**Settings:** - -* `Theme` -* `Size` -* `ErrorMessage` - -
- -
- -reCAPTCHA 3 - -**ID:** `663AA19B-423D-4F38-A1D6-C840C926EF86` - -**Alias:** `recaptcha3` - -**Settings:** - -* `ScoreThreshold` -* `ErrorMessage` -* `SaveScore` - -
- -
- -Rich Text - -**ID:** `1F8D45F8-76E6-4550-A0F5-9637B8454619` - -**Alias:** `richText` - -**Settings:** - -* `Html` -* `ShowLabel` - -
- -
- -Single Choice - -**ID:** `903DF9B0-A78C-11DE-9FC1-DB7A56D89593` - -**Alias:** `singleChoice` - -**Settings:** - -* `DisplayLayout` -* `DefaultValue` -* `ShowLabel` - -
- -
- -Short Answer - -**ID:** `3F92E01B-29E2-4a30-BF33-9DF5580ED52C` - -**Alias:** `shortAnswer` - -**Settings:** - -* `DefaultValue` -* `Placeholder` -* `ShowLabel` -* `MaximumLength` -* `FieldType` -* `AutocompleteAttribute` - -
- -
- -Title and Description - -**ID:** `e3fbf6c4-f46c-495e-aff8-4b3c227b4a98` - -**Alias:** `titleAndDescription` - -**Settings:** - -* `CaptionTag` -* `Caption` -* `BodyText` -* `ShowLabel` - -
- -## Workflow Types - -
- -Change Record State - -**ID:** `4C40A092-0CB5-481d-96A7-A02D8E7CDB2F` - -**Alias:** `changeRecordState` - -**Settings:** - -* `Words` -* `Action` - -
- -
- -Post as XML - -**ID:** `470EEB3A-CB15-4b08-9FC0-A2F091583332` - -**Alias:** `postAsXml` - -**Settings:** - -* `Url` -* `Method` -* `XsltFile` -* `Fields` -* `Username` -* `Password` - -
- -
- -Save As Umbraco Content Node - -**ID:** `89FB1E31-9F36-4e08-9D1B-AF1180D340DB` - -**Alias:** `saveAsUmbracoContentNode` - -**Settings:** - -* `Fields` -* `Publish` -* `RootNode` - -
- -
- -Save As XML File - -**ID:** `9CC5854D-61A2-48f6-9F4A-8F3BDFAFB521` - -**Alias:** `saveAsAnXmlFile` - -**Settings:** - -* `Path` -* `Extension` -* `XsltFile` - -
- -
- -Send Email - -**ID:** `E96BADD7-05BE-4978-B8D9-B3D733DE70A5` - -**Alias:** `sendEmail` - -**Settings:** - -* `Email` -* `CcEmail` -* `BccEmail` -* `SenderEmail` -* `ReplyToEmail` -* `Subject` -* `Message` -* `Attachment` - -
- -
- -Send Email With Razor Template - -**ID:** `17c61629-d984-4e86-b43b-a8407b3efea9` - -**Alias:** `sendEmailWithRazorTemplate` - -**Settings:** - -* `Email` -* `CcEmail` -* `BccEmail` -* `SenderEmail` -* `ReplyToEmail` -* `Subject` -* `RazorViewFilePath` -* `Attachment` - -
- -
- -Send Email With Extensible Stylesheet Language Transformations (XSLT) Template - -**ID:** `616edfeb-badf-414b-89dc-d8655eb85998` - -**Alias:** `sendEmailWithXsltTemplate` - -**Settings:** - -* `Email` -* `CcEmail` -* `BccEmail` -* `SenderEmail` -* `ReplyToEmail` -* `Subject` -* `XsltFile` - -
- -
- -Send Form To URL - -**ID:** `FD02C929-4E7D-4f90-B9FA-13D074A76688` - -**Alias:** `sendFormToUrl` - -**Settings:** - -* `Url` -* `Method` -* `StandardFields` -* `Fields` -* `Username` -* `Password` - -
- -
- -Slack - -**ID:** `bc52ab28-d3ff-42ee-af75-a5d49be83040` - -**Alias:** `slack` - -**Settings:** - -* `WebhookUrl` - -
- -
- -Slack (Legacy) - -**ID:** `ccbfb0d5-adaa-4729-8b4c-4bb439dc0202` - -**Alias:** `slackLegacy` - -**Settings:** - -* `Token` -* `Channel` -* `Username` -* `AvatarUrl` - -
- -## Prevalue Source Types - -
- -Datasource - -**ID:** `cc9f9b2a-a746-11de-9e17-681b56d89593` - -**Alias:** `dataSource` - -
- -
- -Get Values From Text File - -**ID:** `35C2053E-CBF7-4793-B27C-6E97B7671A2D` - -**Alias:** `getValuesFromTextFile` - -**Settings:** - -* `TextFile` - -
- -
- -SQL Database - -**ID:** `F1F5BD4D-E6AE-44ed-86CB-97661E4660B2` - -**Alias:** `sqlDatabase` - -**Settings:** - -* `Connection` -* `ConnectionString` -* `Table` -* `KeyColumn` -* `ValueColumn` -* `CaptionColumn` - -
- -
- -Umbraco Datatype Prevalues - -**ID:** `EA773CAF-FEF2-491B-B5B7-6A3552B1A0E2` - -**Alias:** `umbracoDataTypePreValues` - -**Settings:** - -* `DataTypeId` - -
- -
- -Umbraco Documents - -**ID:** `de996870-c45a-11de-8a39-0800200c9a66` - -**Alias:** `umbracoDocuments` - -**Settings:** - -* `RootNode` -* `UseCurrentPage` -* `DocType` -* `ValueField` -* `CaptionField` -* `ListGrandChildren` -* `OrderBy` - -
- -## Data Source Types - -
- -SQL Database - -**ID:** `F19506F3-EFEA-4b13-A308-89348F69DF91` - -**Alias:** `sqlDatabase` - -**Settings:** - -* `Connection` -* `Table` - -
diff --git a/14/umbraco-forms/developer/custom-markup.md b/14/umbraco-forms/developer/custom-markup.md deleted file mode 100644 index 65d29f0059a..00000000000 --- a/14/umbraco-forms/developer/custom-markup.md +++ /dev/null @@ -1,86 +0,0 @@ ---- -description: >- - This article teaches you how to customize how your Umbraco Forms are - outputted. ---- - -# Custom Markup - -With Umbraco Forms, it is possible to customize the output markup of a Form, which means you have complete control over what Forms will display. - -{% hint style="warning" %} -We recommend using [Themes](themes.md) to customize your Forms. This will ensure that nothing is overwritten when you upgrade Forms to a newer version. -{% endhint %} - -## Customizing the Default Views - -The razor macro uses some razor views to output the Form: - -* 1 view for each fieldtype -* 1 view for the scripts -* 1 view for the rest of the Form - -You can find the default views in the `~\Views\Partials\Forms\Themes\default` folder. - -To avoid your custom changes to the default views from being overwritten, you need to copy the view you want to customize into your theme folder, e.g. `~\Views\Partials\Forms\Themes\YourTheme`, and edit the file in `YourTheme` folder. - -### Form.cshtml - -This is the main view responsible for rendering the Form markup. - -The view is separated into two parts, one is the actual Form and the other will be shown if the Form is submitted. - -This view can be customized, if you do so it will be customized for all your Forms. - -### Script.cshtml - -This view renders the JavaScript that will take care of the conditional logic, customization won't be needed here. - -### FieldType.\*.cshtml - -The rest of the views start with FieldType, like `FieldType.Textfield.cshtml` and those will output the fields. There is a view for each default fieldtype like _textfield_, _textarea_, _checkbox_, etc) - -Contents of the `FieldType.Textfield.cshtml` view (from the default theme): - -```csharp -@model Umbraco.Forms.Mvc.Models.FieldViewModel -@using Umbraco.Forms.Mvc - -placeholder="@Model.PlaceholderText"}} - @{if(Model.Mandatory || Model.Validate){data-val="true"}} - @{if (Model.Mandatory) { data-val-required="@Model.RequiredErrorMessage"}} - @{if (Model.Validate) { data-val-regex="@Model.InvalidErrorMessage" data-val-regex-pattern="@Html.Raw(Model.Regex)"}} -/> -``` - -Umbraco Forms uses ASP.NET Unobtrusive Validation which is why you see attributes like `data-val` and `data-val-required`. - -This can be customized but it's important to keep the ID of the control to `@Model.Id` since that is used to match the value to the Form field. For fields that are conditionally hidden, without an ID of `@Model.Id` the control won't be shown when the conditions to show the field are met. An ID needs to be added to text controls such as headings and paragraphs. - -The view model for the partial view for a field is `FieldViewModel`. This defines properties that may be useful when creating new themes or custom fields, some of which are shown in the code samples above. Others include: - -* `AdditionalSettings` - a dictionary of the settings keys and values populated for the form field. These can be retrieved in typed form by key using e.g. `Model.GetSettingValue("MaximumLength", 255);`. - -The following are available on the model but only populated for fields that support file upload: - -* `AllowAllUploadExtensions`- a boolean indicating whether all file extensions are permitted for upload. -* `AllowedUploadExtensions`- a collection of strings indicating the file extensions that are permitted for upload. -* `AllowMultipleFileUploads`- a boolean indicating whether selecting multiple files for upload is allowed. - -### Customizing for a Specific Form - -It is also possible to customize the markup for a specific Form. - -You will need to create folder using the ID of the Form: `~\Views\Partials\Forms\{FormId}` (find the id of the Form in the URL when you are viewing the Form in the backoffice.) - -![Form GUID](../../../10/umbraco-forms/developer/images/form-guid.png) - -As an example if your Form ID is 0d3e6b2d-db8a-43e5-8f28-36241d712487 then you can overwrite the Form view by adding the `Form.cshtml` file to the directory. Start by copying the default one and then making your custom changes: `~\Views\Partials\Forms\0d3e6b2d-db8a-43e5-8f28-36241d712487\Form.cshtml`. - -You can also overwrite views for one or more fieldtypes by adding the views to the `Fieldtypes` folder: `~\Views\Partials\Forms\0d3e6b2d-db8a-43e5-8f28-36241d712487\Fieldtypes\Fieldtype.Textfield.cshtml`. diff --git a/14/umbraco-forms/developer/email-templates.md b/14/umbraco-forms/developer/email-templates.md deleted file mode 100644 index 6e175528457..00000000000 --- a/14/umbraco-forms/developer/email-templates.md +++ /dev/null @@ -1,245 +0,0 @@ ---- -description: "Creating an email template for Umbraco Forms." ---- - -# Email Templates - -We include a Workflow **Send email with template (Razor)** that allows you to pick a Razor view file that can be used to send out a _pretty HTML email_ for Form submissions. - -## Creating an Email Template - -If you wish to have one or more templates to choose from the **Send email with template (Razor)**, you will need to place all email templates into the `~/Views/Partials/Forms/Emails/` folder. - -The Razor view must inherit from FormsHtmlModel: - -```csharp -@inherits Umbraco.Cms.Web.Common.Views.UmbracoViewPage -``` - -You now have a model that contains your Form fields which can be used in your email HTML markup, along with the UmbracoHelper methods such as `Umbraco.TypedContent` and `Umbraco.TypedMedia` etc. - -Below is an example of an email template from the `~/Views/Partials/Forms/Emails/` folder: - -```csharp -@inherits Umbraco.Cms.Web.Common.Views.UmbracoViewPage - -@{ - //This is an example email template where you can use Razor Views to send HTML emails - - //You can use Umbraco.TypedContent & Umbraco.TypedMedia etc to use Images & content from your site - //directly in your email templates too - - //Strongly Typed - //@Model.GetValue("aliasFormField") - //@foreach (var color in Model.GetValues("checkboxField")){} - - //Dynamics - //@Model.DynamicFields.aliasFormField - //@foreach(var color in Model.DynamicFields.checkboxField - - //Images need to be absolute - so fetching domain to prefix with images - var siteDomain = Context.Request.Scheme + "://" + Context.Request.Host; - var assetUrl = siteDomain + "/App_plugins/UmbracoForms/Assets/Email-Example"; - -} - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - -
- - Logo - -
- -
- - - - - -
-

Umbraco Forms

-
- -
- - - - - - - - - - - - - - - - - - - - - - -
- This is an example email template from Umbraco Forms Razor based email templates. You can build forms using any HTML markup you wish. -
- - CodeGarden16 Attendees - -
-

Form Results

-
- - @foreach (var field in Model.Fields) - { -

@field.Name

- - switch (field.FieldType) - { - case "FieldType.FileUpload.cshtml": -

@field.GetValue()

- break; - - case "FieldType.DatePicker.cshtml": - DateTime dt; - var fieldValue = field.GetValue(); - var dateValid = DateTime.TryParse(fieldValue != null ? fieldValue.ToString() : string.Empty, out dt); - var dateStr = dateValid ? dt.ToString("f") : ""; -

@dateStr

- break; - - case "FieldType.CheckBoxList.cshtml": -

- @foreach (var color in field.GetValues()) - { - @color
- } -

- break; - default: -

@field.GetValue()

- break; - } - } - -
- -
- - - - - - -
-

Need more help?

-

Find our documentation here

-
- -
- - -``` diff --git a/14/umbraco-forms/developer/extending/README.md b/14/umbraco-forms/developer/extending/README.md deleted file mode 100644 index 635b9fd8f8e..00000000000 --- a/14/umbraco-forms/developer/extending/README.md +++ /dev/null @@ -1,83 +0,0 @@ -# Extending - -Umbraco Forms functionality can be extended in different ways. In this section we focus on techniques available to a back-end/C# developer. - -For front-end extensions, specifically via theming, see the [Themes](../themes.md) section. - -## Developing Custom Providers - -Although the Forms package comes with many fields, workflows and other built-in types, you can still create and develop your own if needed. - -### [Provider model](adding-a-type.md) - -Many features of Forms use a provider model, which makes it quicker to add new parts to the application. - -The model uses the notion that everything must have a type to exist. The type defines the capabilities of the item. For instance a Textfield on a form has a FieldType, this particular field type enables it to render an input field and save text strings. The same goes for workflows, which have a workflow type, datasources which have a datasource type and so on. Using the model you can seamlessly add new types and thereby extend the application. - -It is possible to add new Field types, Data Source Types, Prevalue Source Types, Export Types, and Workflow Types. - -### [Field types](adding-a-fieldtype.md) - -A field type handles rendering of the UI for a field in a form. It renders a standard ASP.NET Razor partial view and is able to return a list of values when the form is saved. - -The concept of provider settings, common to the field and other types, is also discussed in this section. - -### Data Source Types - -A data source type enables Umbraco Forms to connect to a custom source of data. A data source consists of any kind of storage if it is possible to return a list of fields Umbraco Forms can map values to. For example: a Database data source can return a list of columns Forms can send data to. This enables Umbraco Forms to map a form to a data source. A data source type is responsible for connecting Forms to external storage. - -### [Prevalue Source Types](adding-a-prevaluesourcetype.md) - -A prevalue source type connects to 3rd party storage to retrieve values. These values are used on fields supporting prevalues. The source fetches the collection of values. - -### [Workflow Types](adding-a-workflowtype.md) - -A workflow can be executed each time a form changes state (when it is submitted for instance). A workflow is responsible for executing logic which can modify the record or notify 3rd party systems. - -### [Export Types](adding-a-exporttype.md) - -Export types are responsible for turning form records into any other data format, which is then returned as a file. - -### [Magic String Format Functions](adding-a-magic-string-format-function.md) - -Custom magic string format functions to add to the [ones shipped with Umbraco Forms](../magic-strings.md#formatting-magic-strings) can be created in code. - -### [Validation Patterns](adding-a-validation-pattern.md) - -When creating a text field in Umbraco Forms, a validation pattern in the form of a regular expression can be applied. Default patterns can be removed or re-ordered, and custom ones created and added. - -## Handling Forms Events - -Another option for extension via custom code is to hook into one of the many events available. - -### [Validation](adding-an-event-handler.md) - -Form events are raised during the submission life cycle and can be handled for executing custom logic. - -### [Default Fields and Workflows](customize-default-workflows.md) - -When a new form is created, the default behavior is to add a single workflow. This workflow will send a copy of the form to the current backoffice user's email address. - -A single "data consent" field will also be added unless it has been disabled via configuration. - -It's possible to amend this behavior and change it to fit your needs. - -## Responding to State Values - -In the course of submitting a form, Umbraco Forms will set values in `TempData` and/or `HttpContext.Items`, that you can use to customize the website functionality. - -### Customizing Post-Submission Behavior - -Whether displaying a message or redirecting, a developer can customize the page viewed after the form is submitted based on the presence of `TempData` variables. - -One variable with a key of `UmbracoFormSubmitted` has a value containing the Guid identifier for the submitted form. - -A second variable contains the Guid identifier of the record created from the form submission. You can find this using the `Forms_Current_Record_id` key. - -In order to redirect to an external URL rather than a selected page on the Umbraco website, you will need to use a [custom workflow](adding-a-workflowtype.md). Within this workflow you can set the required redirect URL on the `HttpContext.Items` dictionary using the key `FormsRedirectAfterFormSubmitUrl` (defined in the constant `Umbraco.Forms.Core.Constants.ItemKeys.RedirectAfterFormSubmitUrl`). - -For example, using an injected instance of `IHttpContextAccessor`: - -``` -_httpContextAccessor.HttpContext.Items[Constants.ItemKeys.RedirectAfterFormSubmitUrl] = "https://www.umbraco.com"; -``` diff --git a/14/umbraco-forms/developer/extending/adding-a-exporttype.md b/14/umbraco-forms/developer/extending/adding-a-exporttype.md deleted file mode 100644 index 22495e7db8b..00000000000 --- a/14/umbraco-forms/developer/extending/adding-a-exporttype.md +++ /dev/null @@ -1,243 +0,0 @@ -# Adding An Export Type To Umbraco Forms - -_This builds on the "_[_adding a type to the provider model_](adding-a-type.md)_" chapter._ - -Add a new class to your project and have it inherit from `Umbraco.Forms.Core.ExportType`. You have two options when implementing the class, as shown in the following examples. - -## Basic Example - -You can implement the method `public override string ExportRecords(RecordExportFilter filter)` in your export provider class. You need to return a string you wish to write to a file. For example, you can generate a `.csv` (comma-separated values) file. You would perform your logic to build up a comma-separated string in the `ExportRecords` method. - -{% hint style="info" %} -In the constructor of your provider, you will need a further two properties, `FileExtension` and `Icon`. -{% endhint %} - -`FileExtension` is the extension such as `zip`, `txt` or `csv` of the file you will be generating and serving from the file system. - -In this example below we will create a single HTML file which takes all the submissions/entries to be displayed as a HTML report. We will do this in conjunction with a Razor partial view to help build up our HTML and thus merge it with the form submission data to generate a string of HTML. - -### Provider Class - -```csharp -using System; -using Umbraco.Cms.Core.Hosting; -using Umbraco.Forms.Core; -using Umbraco.Forms.Core.Models; -using Umbraco.Forms.Core.Searchers; -using Umbraco.Forms.Web.Helpers; - -namespace MyFormsExtensions -{ - public class ExportToHtml : ExportType - { - private readonly IHttpContextAccessor _httpContextAccessor; - private readonly IFormRecordSearcher _formRecordSearcher; - - public ExportToHtml( - IHostEnvironment hostEnvironment, - IHttpContextAccessor httpContextAccessor, - IFormRecordSearcher formRecordSearcher) - : base(hostEnvironment) - { - _httpContextAccessor = httpContextAccessor; - _formRecordSearcher = formRecordSearcher; - - Name = "Export as HTML"; - Description = "Export entries as a single HTML report"; - Id = new Guid("4117D352-FB41-4A4C-96F5-F6EF35B384D2"); - FileExtension = "html"; - Icon = "icon-article"; - } - - public override string ExportRecords(RecordExportFilter filter) - { - var view = "~/Views/Partials/Forms/Export/html-report.cshtml"; - EntrySearchResultCollection model = _formRecordSearcher.QueryDataBase(filter); - return ViewHelper.RenderPartialViewToString(_httpContextAccessor.GetRequiredHttpContext(), view, model); - } - } -} -``` - -### Razor Partial View - -```csharp -@model Umbraco.Forms.Core.Searchers.EntrySearchResultCollection - -@{ - var submissions = Model.Results.ToList(); - var schemaItems = Model.Schema.ToList(); -} - -

Form Submissions

- -@foreach (var submission in submissions) -{ - var values = submission.Fields.ToList(); - - for (int i = 0; i < schemaItems.Count; i++) - { - @schemaItems[i].Name @values[i].Value -
- } - -
-} -``` - -### Registration - -```csharp -using Umbraco.Cms.Core.Composing; -using Umbraco.Forms.Core.Providers.Extensions; -using Umbraco.Forms.TestSite.Business.ExportTypes; - -namespace MyFormsExtensions -{ - public class TestComposer : IComposer - { - public void Compose(IUmbracoBuilder builder) - { - builder.FormsExporters().Add(); - } - } -} -``` - -## Advanced Example - -This approach gives us more flexibility in creating the file we wish to serve as the exported file. We do this for the export to Excel file export provider we ship in Umbraco Forms. With this we can use a library to create the Excel file and store it in a temporary location before we send back the filepath for the browser to stream down the export file. - -In this example we will create a collection of text files, one for each submission which is then zipped up into a single file and served as the export file. - -```csharp -using System; -using System.IO; -using System.IO.Compression; -using System.Linq; -using Umbraco.Cms.Core.Hosting; -using Umbraco.Forms.Core; -using Umbraco.Forms.Core.Models; -using Umbraco.Forms.Core.Searchers; - -namespace MyFormsExtensions -{ - public class ExportToTextFiles : ExportType - { - private readonly IFormRecordSearcher _formRecordSearcher; - - public ExportToTextFiles( - IHostingEnvironment hostingEnvironment, - IFormRecordSearcher formRecordSearcher) - : base(hostingEnvironment) - { - _formRecordSearcher = formRecordSearcher; - - this.Name = "Export as text files"; - this.Description = "Export entries as text files inside a zip file"; - this.Id = new Guid("171CABC9-2207-4575-83D5-2A77E824D5DB"); - this.FileExtension = "zip"; - this.Icon = "icon-zip"; - } - - /// - /// We do not implement this method from the interface - /// As this method is called from ExportToFile that we also override here & is expecting the file contents as a string to be written as a stream to a file - /// Which would be OK if we were creating a CSV or a single based file that can have a simple string written as a string such as one large HTML report or XML file perhaps - /// - public override string ExportRecords(RecordExportFilter filter) => throw new NotImplementedException(); - - /// - /// This gives us greater control of the export process - /// - /// - /// This filter contains the date range & other search parameters to limit the entries we are exporting - /// - /// - /// The filepath that the export file is expecting to be served from - /// So ensure that the zip of text files is saved at this location - /// - /// The final file path to serve up as the export - this is unlikely to change through the export logic - public override string ExportToFile(RecordExportFilter filter, string filepath) - { - // Before Save - Check Path, Directory & Previous File export does not exist - string pathToSaveZipFile = filepath; - - // Check our path does not contain \\ - // If not, use the filePath - if (filepath.Contains('\\') == false) - { - pathToSaveZipFile = HostingEnvironment.MapPathContentRoot(filepath); - } - - // Get the directory (strip out \\ if it exists) - var dir = filepath.Substring(0, filepath.LastIndexOf('\\')); - var tempFileDir = Path.Combine(dir, "text-files"); - - - // If the path does not end with our file extension, ensure it's added - if (pathToSaveZipFile.EndsWith("." + FileExtension) == false) - { - pathToSaveZipFile += "." + FileExtension; - } - - // Check that the directory where we will save the ZIP file temporarily exists - // If not just create it - if (Directory.Exists(tempFileDir) == false) - { - Directory.CreateDirectory(tempFileDir); - } - - // Check if the zip file exists already - if so delete it, as we have a new update - if (File.Exists(pathToSaveZipFile)) - { - File.Delete(pathToSaveZipFile); - } - - // Query the DB for submissions to export based on the filter - EntrySearchResultCollection submissions = _formRecordSearcher.QueryDataBase(filter); - - // Get the schema objects to a list so we can get items using position index - var schemaItems = submissions.schema.ToList(); - - // We will use this to store our contents of our file to save as a text file - var fileContents = string.Empty; - - // For each submission we have build up a string to save to a text file - foreach (EntrySearchResult submission in submissions.Results) - { - // The submitted data for the form submission - var submissionData = submission.Fields.ToList(); - - // For loop to match the schema position to the submission data - for (int i = 0; i < schemaItems.Count; i++) - { - // Concat a string of the name of the field & its stored data - fileContents += schemaItems[i].Name + ": " + submissionData[i] + Environment.NewLine; - } - - // Now save the contents to a text file - // Base it on the format of the record submission unique id - var textFileName = Path.Combine(tempFileDir, submission.UniqueId + ".txt"); - File.WriteAllText(textFileName, fileContents); - - // Reset fileContents to be empty again - fileContents = string.Empty; - } - - // Now we have a temp folder full of text files - // Generate a zip file containing them & save that - ZipFile.CreateFromDirectory(tempFileDir, pathToSaveZipFile); - - // Tidy up after ourselves & delete the temp folder of text files - if (Directory.Exists(tempFileDir)) - { - Directory.Delete(tempFileDir, true); - } - - // Return the path where we saved the zip file containing the text files - return pathToSaveZipFile; - } - } -} -``` diff --git a/14/umbraco-forms/developer/extending/adding-a-fieldtype.md b/14/umbraco-forms/developer/extending/adding-a-fieldtype.md deleted file mode 100644 index 9999fdd7275..00000000000 --- a/14/umbraco-forms/developer/extending/adding-a-fieldtype.md +++ /dev/null @@ -1,513 +0,0 @@ -# Adding A Field Type To Umbraco Forms - -_This builds on the "_[_adding a type to the provider model_](adding-a-type.md)_" chapter_ - -In this article, we will illustrate how to add a custom form field type using server-side and client-side components. We will use the example of rendering a "slider" field type that allows the user to select a number within a specific range of values. - -## Server-side Field Type Definition - -Add a new class to the Visual Studio solution. Inherit from `Umbraco.Forms.Core.FieldType` and complete as follows: - -```csharp -using Umbraco.Cms.Core.Composing; -using Umbraco.Forms.Core.Attributes; -using Umbraco.Forms.Core.Enums; -using Umbraco.Forms.Core.Providers; - -namespace MyProject; - -public class SliderFieldType : Core.FieldType -{ - public SliderFieldType() - { - Id = new Guid("6dff0075-598c-4345-89d7-e0db8684c819"); - Name = "Slider"; - Alias = "slider"; - Description = "Render a UUI Slider field."; - Icon = "icon-autofill"; - DataType = FieldDataType.String; - SortOrder = 10; - - FieldTypeViewName = "FieldType.Slider.cshtml"; - EditView = "My.PropertyEditorUi.InputNumber"; - PreviewView = "My.FieldPreview.Slider"; - } - - [Setting("Minimum", Description = "Minimum value", View = "Umb.PropertyEditorUi.Integer", DisplayOrder = 10)] - public virtual string? Min { get; set; } = "1"; - - [Setting("Maximum", Description = "Maximum value", View = "Umb.PropertyEditorUi.Integer", DisplayOrder = 20)] - public virtual string? Max { get; set; } = "1"; - - [Setting("Step", Description = "Step size", View = "Umb.PropertyEditorUi.Integer", DisplayOrder = 30)] - public virtual string? Step { get; set; } = "1"; - - [Setting("Default Value", Description = "Default value", View = "Umb.PropertyEditorUi.Integer", DisplayOrder = 40)] - public virtual string? DefaultValue { get; set; } = "1"; - - [Setting("Hide step values", Description = "Hides the numbers representing the value of each steps. Dots will still be visible", View = "Umb.PropertyEditorUi.Toggle", DisplayOrder = 50)] - public virtual string? HideStepValues { get; set; } - - [Setting("Background color", Description = "Background color for the input field", View = "My.PropertyEditorUi.InputColor", DisplayOrder = 60)] - public virtual string? BgColor { get; set; } = "1"; -} -``` - -In the constructor or via overridden properties, we can specify details of the field type: - -* `Id` - should be set to a unique GUID. -* `Alias` - an internal alias for the field, used for localized translation keys. -* `Name` - the name of the field presented in the backoffice. -* `Description` - the description of the field presented in the backoffice. -* `Icon` - the icon of the field presented in the backoffice form builder user interface. -* `DataType` - specifies the type of data stored by the field. Options are `String`, `LongString`, `Integer`, `DataTime` or `Bit` (boolean). -* `SupportsMandatory` - indicates whether mandatory validation can be used with the field (defaults to `true`). -* `MandatoryByDefault` - indicates whether the field will be mandatory by default when added to a form (defaults to `false`). -* `SupportsRegex` - indicates whether pattern-based validation using regular expressions can be used with the field (defaults to `false`). -* `SupportsPreValues` - indicates whether prevalues are supported by the field (defaults to `false`). -* `RenderInputType`- indicates how the field should be rendered within the theme as defined with the `RenderInputType` enum. - * The default is `Single` for a single input field. - * `Multiple` should be used for multiple input fields such as checkbox lists. - * `Custom` is used for fields without visible input fields. -* `FieldTypeViewName` - indicates the name of the partial view used to render the field on the website. -* `EditView` - indicates the name of a property editor UI that is used for editing the field in the backoffice. If nothing is provided, the built-in label will be used and the field won't be editable. -* `PreviewView` - indicates the name of a manifest registered client-side resource that is used for previewing the field in the backoffice. If nothing is provided, the name of the field type will be used as the preview. - -You now need to register this new field as a dependency: - -```csharp -using Umbraco.Cms.Core.Composing; -using Umbraco.Cms.Core.DependencyInjection; -using Umbraco.Forms.Core.Providers; - -namespace MyProject; - -public class Startup : IComposer -{ - public void Compose(IUmbracoBuilder builder) - { - builder.WithCollectionBuilder() - .Add(); - } -} -``` - -## Partial View - -We will start building the view for the default theme of the Form at `Views\Partials\Forms\Themes\default\FieldTypes\FieldType.Slider.cshtml`. - -The file name for the partial view should match the value set on the `FieldTypeViewName` property. - -```csharp -@using Umbraco.Forms.Web -@model Umbraco.Forms.Web.Models.FieldViewModel -@{ - var min = Model.GetSettingValue("Min", 1); - var max = Model.GetSettingValue("Max", 10); - var step = Model.GetSettingValue("Step", 1); - var bgColor = Model.GetSettingValue("BgColor", "#fff"); -} -
This is a custom "slider" field type. We'll just use an input to mock this up.
- -``` - -This will be rendered when the default theme is used. - -If working with Umbraco 9 or earlier versions, you'll find the `Views\Partials\Forms\Themes\default\` folder on disk and can create the files there. - -For Umbraco 10 and above, we've moved to [distributing the theme as part of a Razor Class Library](../../upgrading/version-specific.md#views-and-client-side-files) so the folder won't exist. However, you can create it for your custom field type. If you would like to reference the partial views of the default theme, you can download them as mentioned in the [Themes](../themes.md) article. - -### Read-only partial view - -When rendering a multi-page form, editors have the option to display a summary page where the entries can be viewed before submitting. - -To support this, a read-only view of the field is necessary. - -For most fields, nothing is required here, as the default read-only display defined in the built-in `ReadOnly.cshtml` file suffices. - -However, if you want to provide a custom read-only display for your field, you can do so by creating a second partial view. This should be named with a `.ReadOnly` suffix. For this example, you would create `FieldType.Slider.ReadOnly.cshtml`. - -## Field Settings - -Field settings will be managed in the backoffice by editors who will create forms using the custom field type. These settings can be added to the C# class as properties with a `Setting` attribute: - -```csharp -[Setting("Minimum", Description = "Minimum value", View = "Umb.PropertyEditorUi.Integer", DisplayOrder = 10)] -public virtual string? Min { get; set; } = "1"; -``` - -The property `Name` names the setting in the backoffice with the `Description` providing the help text. Both of these can be translated, as discussed in the backoffice components section below. - -The `View` property indicates a property editor UI used for editing the setting value. You can use a built-in property editor UI, one from a package, or a custom one registered with your solution. The default value if not provided is `Umb.PropertyEditorUi.TextBox`, which will use the standard Umbraco text box property editor UI. - -`SupportsPlaceholders` is a flag indicating whether the setting can contain ["magic string" placeholders](../magic-strings.md) and controls whether they are parsed on rendering. - -`HtmlEncodeReplacedPlaceholderValues` takes effect only if `SupportsPlaceholders` is `true`. It controls whether the replaced placeholder values should be HTML encoded (as is necessary for rendering within content from a rich text editor). - -`SupportsHtml` is a flag indicating whether the setting can contain HTML content. When set to `true` it will be treated as HTML content when the value is read from the Forms delivery API. - -`IsMandatory` if set to `true` will provide client-side validation in the backoffice to ensure the value is completed. - -When creating a field or other provider type, you might choose to inherit from an existing class. This could be if one of the types provided with Umbraco Forms almost meets your needs but you want to make some changes. - -All setting properties for the Forms provider types are marked as `virtual`, so you can override them and change the setting values: - -## Umbraco Backoffice Components - -With Forms 14, aspects of the presentation and functionality of the custom field are handled by client-side components, registered via manifests: - -* The preview, displayed on the form definition editor. -* The property editor UI used for editing the the submitted values via the backoffice. -* The property editor UI used for editing settings. -* A settings converter, that handles configuring the property editor and translating between the editor and persisted values. -* Translations for setting labels and descriptions. - -To create custom backoffice components for Umbraco 14, it's recommended to use a front-end build setup using Vite, TypeScript, and Lit. For more information, see the [Extension with Vite, TypeScript, and Lit](https://app.gitbook.com/s/G1Byxw7XfiZAj8zDMCTD/tutorials/creating-your-first-extension#extension-with-vite-typescript-and-lit) article. - -To display a name and description on a custom field, you need to register a JavaScript file as shown in the [Localization](https://app.gitbook.com/s/7MBVdnTbFiAgWuRsHpNS/customizing/extending-overview/extension-types/localization) article. - -### Field Preview - -The alias of the preview to use is defined on the field type via the `PreviewView` property. - -A preview for our slider, representing the selected setting values could look as follows: - -```javascript -import { UmbElementMixin } from "@umbraco-cms/backoffice/element-api"; -import { - LitElement, - css, - customElement, - html, - property, -} from "@umbraco-cms/backoffice/external/lit"; - -const elementName = "my-field-preview-slider"; - -@customElement(elementName) -export class MyFieldPreviewSliderElement extends UmbElementMixin(LitElement) { - @property() - settings = {}; - - @property({ type: Array }) - prevalues = []; - - getSettingValue(key: string) { - return this.settings[key]; - } - - render() { - return html`
- -
`; - } - - static styles = css` - div { - padding: var(--uui-size-4); - } - `; -} - -export default MyFieldPreviewSliderElement; - -declare global { - interface HTMLElementTagNameMap { - [elementName]: MyFieldPreviewSliderElement; - } -} -``` - -And it is registered via a manifest: - -```javascript -import MyFieldPreviewSliderElement from './slider-preview.element.js'; - -const sliderPreviewManifest = { - type: "formsFieldPreview", - alias: "My.FieldPreview.Slider", - name: "Forms UUI Slider Field Preview", - api: MyFieldPreviewSliderElement, - element: () => import('./slider-preview.element.js') - }; - - export const manifests = [sliderPreviewManifest]; -``` - -### Field Editor - -Umbraco Forms supports editing of the entries submitted by website visitors via the backoffice. The property editor interface to use for this is defined in the field type's `EditView` property. - -If not using a built-in property editor, you can create your own. The following example shows how the numerical entries could be edited using an input control. - -```javascript -import { - html, - customElement, -} from "@umbraco-cms/backoffice/external/lit"; -import type { UmbPropertyEditorUiElement } from "@umbraco-cms/backoffice/extension-registry"; -import { UmbLitElement } from "@umbraco-cms/backoffice/lit-element"; -import { - UmbPropertyValueChangeEvent, -} from "@umbraco-cms/backoffice/property-editor"; -import { UmbFormControlMixin } from "@umbraco-cms/backoffice/validation"; - -const elementName = "my-property-editor-ui-number"; - -@customElement(elementName) -export class MyPropertyEditorUINumberElement - extends UmbFormControlMixin(UmbLitElement, undefined) - implements UmbPropertyEditorUiElement -{ - private onChange(e: Event) { - const newValue = (e.target as HTMLInputElement).value; - if (newValue === this.value) return; - this.value = newValue; - this.dispatchEvent(new UmbPropertyValueChangeEvent()); - } - - render() { - return html``; - } -} - -export default MyPropertyEditorUINumberElement; - -declare global { - interface HTMLElementTagNameMap { - [elementName]: MyPropertyEditorUINumberElement; - } -} -``` - -Again, it's registered via a manifest. - -```javascript -const numberPropertyEditorManifest = { - type: 'propertyEditorUi', - alias: 'My.PropertyEditorUi.InputNumber', - name: 'Number Input Property Editor UI', - element: () => import('./property-editor-ui-number.element.js'), - meta: { - label: 'Number Input', - icon: 'icon-autofill', - }, -}; -export const manifests = [numberPropertyEditorManifest]; -``` - -### Setting Value Editor - -Field type settings also use a property editor UI for editing the values in the backoffice. The one to use is defined via the `View` property on the `Setting` attribute. - -In our example we use a custom one, allowing the value for the background color to the field to be selected via an input control. - -```javascript -import { - html, - customElement, - type PropertyValueMap, -} from "@umbraco-cms/backoffice/external/lit"; -import type { UmbPropertyEditorUiElement } from "@umbraco-cms/backoffice/extension-registry"; -import { UmbLitElement } from "@umbraco-cms/backoffice/lit-element"; -import { - UmbPropertyValueChangeEvent, -} from "@umbraco-cms/backoffice/property-editor"; -import { UmbFormControlMixin } from "@umbraco-cms/backoffice/validation"; - -const elementName = "my-property-editor-ui-color"; - -@customElement(elementName) -export class MyPropertyEditorUIColorElement - extends UmbFormControlMixin(UmbLitElement, undefined) - implements UmbPropertyEditorUiElement -{ - protected firstUpdated( - _changedProperties: PropertyValueMap | Map - ): void { - super.firstUpdated(_changedProperties); - this.addFormControlElement(this.shadowRoot!.querySelector("input")!); - } - - private onChange(e: Event) { - const newValue = (e.target as HTMLInputElement).value; - if (newValue === this.value) return; - this.value = newValue; - this.dispatchEvent(new UmbPropertyValueChangeEvent()); - } - - render() { - return html``; - } -} - -export default MyPropertyEditorUIColorElement; - -declare global { - interface HTMLElementTagNameMap { - [elementName]: MyPropertyEditorUIColorElement; - } -} -``` - -And register it via a manifest: - -```javascript -const colorPropertyEditorManifest = { - type: 'propertyEditorUi', - alias: 'My.PropertyEditorUi.InputColor', - name: 'Color Input Property Editor UI', - element: () => import('./property-editor-ui-color.element.js'), - meta: { - label: 'Color Input', - icon: 'icon-autofill', - }, -}; - -export const manifests = [colorPropertyEditorManifest]; -``` - -### Setting Value Converter - -You may want to consider registering a settings value converter. This is another client-side component that is registered in a manifest. It converts between the setting value required for the editor and the value persisted with the form definition. A converter defines three methods: - -* `getSettingValueForEditor` - converts the persisted string value into one suitable for the editor -* `getSettingValueForPersistence` - converts the editor value into the string needed for persistence -* `getSettingPropertyConfig` - creates the configuration needed for the property editor - -The following code shows the structure for these converter elements. - -```javascript -import type { UmbPropertyValueData } from "@umbraco-cms/backoffice/property"; - -export class SliderSettingValueConverter { - - async getSettingValueForEditor(setting, alias: string, value: string) { - return Promise.resolve(value); - } - - async getSettingValueForPersistence(setting, valueData: UmbPropertyValueData) { - return Promise.resolve(valueData.value); - } - - async getSettingPropertyConfig(setting, alias: string, values: UmbPropertyValueData[]) { - return Promise.resolve([]); - } -} -``` - -It's registered as follows. The `propertyEditorUiAlias` matches with the property editor UI that requires the conversions. - -```javascript -import { SliderSettingValueConverter } from "./slider-setting-value-converter.api"; - -const sliderValueConverterManifest = { - type: "formsSettingValueConverter", - alias: "My.SettingValueConverter.Slider", - name: "Slider Value Converter", - propertyEditorUiAlias: "My.PropertyEditorUi.Slider", - api: SliderSettingValueConverter, -}; - -export const manifests = [sliderValueConverterManifest]; -``` - -### Language Files - -Setting labels and descriptions are translated via language files. The following example shows how this is created for the settings on our example field type: - -```javascript -import type { UmbLocalizationDictionary } from "@umbraco-cms/backoffice/localization-api"; - -export default { - formProviderFieldTypes: { - sliderMinLabel: `Minimum`, - sliderMinDescription: `Minimum value`, - sliderMaxLabel: `Maximum`, - sliderMaxDescription: `Maximum value`, - sliderStepLabel: `Step`, - sliderStepDescription: `Step size`, - sliderDefaultValueLabel: `Default Value`, - sliderDefaultValueDescription: `Default value shown when the slider is displayed`, - sliderHideStepValuesLabel: `Hide step values`, - sliderHideStepValuesDescription: `Indicate whether the the field's label should be shown when rendering the form`, - sliderBgColorLabel: `Background color`, - sliderBgColorDescription: `Background color for the field`, - }, -} -``` - -Each different type of extension for Forms uses a different root value: - -* Data sources - `formProviderDataSources` -* Export types - `formProviderExportTypes` -* Field types - `formProviderFieldTypes` -* Prevalue sources - `formProviderPrevalueSources` -* Recordset actions - `formRecordSetActions` -* Workflows - `formProviderWorkflows` - -The language files are registered with: - -```javascript -import type { ManifestLocalization } from "@umbraco-cms/backoffice/extension-registry"; - -const localizationManifests: Array = [ - { - type: "localization", - alias: "My.Localization.En_US", - weight: -100, - name: "English (US)", - meta: { - culture: "en-us", - }, - js: () => import("./en-us.js"), - }, -]; -export const manifests = [...localizationManifests]; -``` - -### Registering the Components - -Finally, you will need an entry point to your client-side components that will register the manifests with Umbraco's extension registry. For example: - -```javascript -import { manifests as propertyEditorManifests } from "./property-editor/manifests.js"; -import { manifests as fieldPreviewManifests } from "./field-preview/manifests.js"; -import { manifests as settingValueConverterManifests } from "./setting-value-converter/manifests.js"; -import { manifests as localizationManifests } from "./lang/manifests.js"; - -const manifests = [ - ...propertyEditorManifests, - ...fieldPreviewManifests, - ...settingValueConverterManifests, - ...localizationManifests -]; - -export const onInit = async (host, extensionRegistry) => { - extensionRegistry.registerMany(manifests); -}; -``` diff --git a/14/umbraco-forms/developer/extending/adding-a-magic-string-format-function.md b/14/umbraco-forms/developer/extending/adding-a-magic-string-format-function.md deleted file mode 100644 index e7fcd23d89a..00000000000 --- a/14/umbraco-forms/developer/extending/adding-a-magic-string-format-function.md +++ /dev/null @@ -1,86 +0,0 @@ -# Adding a Magic String Format Function - -_This builds on the "_[_adding a type to the provider model_](adding-a-type.md)_" chapter_ - -Umbraco Forms [Magic Strings](../magic-strings.md) can be used to replace placeholders within form elements with values from different sources. Sources include the HTTP request or the Umbraco page where the form is hosted. - -These values can be formatted using [filter functions](../magic-strings.md#formatting-magic-strings). - -Filter functions for common operations such as truncating a string or formatting a date or number are provided. It's also possible to create custom ones in code. - -## Creating a custom format function - -To create a custom format function, create a class that implements `IParsedPlaceholderFormatter`. - -The `FunctionName` property provides the name of the function that will be used within the form's magic string. - -The `FormatValue` property parses the provided value and arguments and returns the formatted value as a string. - -The following example shows the implementation of a function that bounds an integer value. It takes two arguments, a minimum and maximum value. If the value read from the magic string source is numeric, and fits within the two bounds, it is returned. Otherwise, either the minimum or maximum value is returned depending on whether the value is lower or higher than the bounds respectively. - -```csharp -using System.Globalization; -using Umbraco.Forms.Core.Interfaces; - -namespace Umbraco.Forms.Core.Providers.ParsedPlacholderFormatters -{ - public class BoundNumber : IParsedPlaceholderFormatter - { - public string FunctionName => "bound"; - - public string FormatValue(string value, string[] args) - { - if (args.Length != 2) - { - return value; - } - - if (!int.TryParse(args[0], out var min) || !int.TryParse(args[1], out var max)) - { - return value; - } - - if (int.TryParse(value, out int valueAsInteger) || - int.TryParse(value, NumberStyles.None, CultureInfo.InvariantCulture, out valueAsInteger)) - { - if (valueAsInteger < min) - { - return min.ToString(); - } - - if (valueAsInteger > max) - { - return max.ToString(); - } - - return valueAsInteger.ToString(); - } - - return value; - } - } -} -``` - -## Registering the custom format function - -As with other provider types, the custom function needs to be registered. An example registration using the `IUmbracoBuilder` is shown below: - -```csharp -public static IUmbracoBuilder AddCustomProviders(this IUmbracoBuilder builder) -{ - builder.FormsParsedPlaceholderFormatters() - .Add(); - return builder; -} -``` - -## Using the custom format function - -The format function can be used within a form's magic string in the same way as the ones provided with Umbraco Forms. - -For the example provided, it would be used like this: - -``` -[#field | bound: 1: 10] -``` diff --git a/14/umbraco-forms/developer/extending/adding-a-prevaluesourcetype.md b/14/umbraco-forms/developer/extending/adding-a-prevaluesourcetype.md deleted file mode 100644 index e7535c9526d..00000000000 --- a/14/umbraco-forms/developer/extending/adding-a-prevaluesourcetype.md +++ /dev/null @@ -1,219 +0,0 @@ -# Adding A Prevalue Source Type To Umbraco Forms - -_This builds on the "_[_Adding a type to the provider model_](adding-a-type.md)_" article_ - -Add a new class to your project - inherit it from `Umbraco.Forms.Core.FieldPreValueSourceType` and implement the class. - -The following example shows an illustrative custom prevalue source type that returns a hard-coded list of values. It can be extended for your needs via injection of services via the constructor. (See additional example at the bottom.) - -Dynamic settings can be applied and validated as shown in the [Validate type settings with ValidateSettings()](adding-a-type.md#validate-type-settings-with-validatesettings) article. - -```csharp -using System; -using System.Collections.Generic; -using Umbraco.Forms.Core; -using Umbraco.Forms.Core.Models; - -namespace MyFormsExtensions -{ - public class FixedListPrevalueSource : FieldPreValueSourceType - { - public FixedListPrevalueSource() - { - Id = new Guid("42C8158D-2AA8-4621-B653-6A63C7545768"); - Name = "Fixed List"; - Description = "Example prevalue source providing a fixed list of values."; - } - - public override List GetPreValues(Field field, Form form) => - new List - { - new PreValue - { - Id = 1, - Value = "item-one", - Caption = "Item One" - }, - new PreValue - { - Id = 2, - Value = "item-two", - Caption = "Item Two" - } - }; - - /// - public override List ValidateSettings() - { - // this is used to validate any dynamic settings you might apply to the PreValueSource - // if there are no dynamic settings, return an empty list of Exceptions: - var exceptions = new List(); - return exceptions; - } - } -} -``` - -You will then need to register this new prevalue source type as a dependency. - -```csharp -using Umbraco.Cms.Core.Composing; -using Umbraco.Cms.Core.DependencyInjection; -using Umbraco.Forms.Core.Providers; - -namespace MyFormsExtensions -{ - public class Startup : IComposer - { - public void Compose(IUmbracoBuilder builder) - { - builder.WithCollectionBuilder() - .Add(); - } - } -} -``` - -{% hint style="info" %} -The `PreValue` model in Umbraco Forms Versions 8.13.0, 9.5.0, 10.1.0, and above includes a `.Caption` property. This property is set separately from the `.Value` property. In the previous versions, the `Value` is generally used as the caption when rendered on the form. -{% endhint %} - -## Another Example Using Dependency Injection to Access Additional Services - -This example will take a user-provided Content Node and create a custom Prevalue list from the property data on that node. Your own `FieldPreValueSourceType` can get its data from wherever you like - an API call, custom functions, etc. - -```csharp -using System; -using System.Collections.Generic; -using Microsoft.Extensions.Logging; -using Umbraco.Cms.Core; -using Umbraco.Cms.Core.Models.PublishedContent; -using Umbraco.Cms.Core.Web; -using Umbraco.Forms.Core; -using Umbraco.Forms.Core.Models; -namespace MyFormsExtensions - public class FormPrevaluesSourceNode : FieldPreValueSourceType - { - private readonly ILogger _logger; - private readonly IUmbracoContextFactory _UmbracoContextFactory; - //DEFINE ANY CONFIGURATION SETTING HERE - [Umbraco.Forms.Core.Attributes.Setting(name: "Source Node", - Alias = "SourceNodeId", - Description = "Node holding the Options desired.", - View = "pickers.content")] - public string SourceNodeId { get; set; } - public FormPrevaluesSourceNode( - ILogger logger - , IUmbracoContextFactory umbracoContextFactory - ) - { - _logger = logger; - _UmbracoContextFactory = umbracoContextFactory; - this.Id = new Guid("0E4D4E2B-56E1-4E86-84E4-9A0A6051B57C"); //MAKE THIS UNIQUE! - this.Name = "Content-defined Form Prevalues Source Node"; - this.Description = "Select a node of type 'FormPrevaluesSourceNode'"; - this.Group = "Custom"; - this.Icon = "icon-science"; - } - /// - /// The main method where the PreValues are defined and returned. - /// - /// - /// - /// List of 'Umbraco.Forms.Core.Models.PreValue' - public override List GetPreValues(Field field, Form form) - { - List result = new List(); - try - { - // Access the Configuration Setting and check that is is valid - if (!string.IsNullOrEmpty(SourceNodeId)) - { - var nodeId = 0; - var isValidId = Int32.TryParse(SourceNodeId, out nodeId); - if (isValidId) - { - IPublishedContent iPub; - using (var umbracoContextReference = _UmbracoContextFactory.EnsureUmbracoContext()) - { - iPub = umbracoContextReference.UmbracoContext.Content.GetById(nodeId); - } - if (iPub != null) - { - int sort = 0; - //This is using a ModelsBuilder Model to strongly-type the selected node - var preValSourceNode = new Models.FormPrevaluesSourceNode(iPub, null); - foreach (var prevalue in preValSourceNode.PreValues) - { - PreValue pv = new PreValue(); - pv.Id = $"{iPub.Id}-{sort}"; - pv.Value = prevalue.StoredValue; - pv.Caption = prevalue.DisplayText; //.Caption only available in Forms Versions 8.13.0+, 9.5.0+, & 10.1.0+ - pv.SortOrder = sort; - result.Add(pv); - sort++; - } - } - } - } - } - catch (Exception ex) - { - _logger.LogError($"Unable to get options from FormPrevaluesSourceNode #{SourceNodeId}", ex); - } - return result; - } - /// - /// This is where any checks for Configuration validity are done. - /// The exceptions will be displayed in the back-office UI to the user. - /// - /// List of 'System.Exception' - public override List ValidateSettings() - { - List exceptions = new List(); - if (string.IsNullOrEmpty(SourceNodeId)) - { - exceptions.Add(new Exception("'Source Node' setting not filled out")); - } - else - { - var nodeId = 0; - var isValidId = Int32.TryParse(SourceNodeId, out nodeId); - if (isValidId) - { - IPublishedContent iPub; - using (var umbracoContextReference = _UmbracoContextFactory.EnsureUmbracoContext()) - { - iPub = umbracoContextReference.UmbracoContext.Content.GetById(nodeId); - } - if (iPub != null && iPub.ContentType.Alias != Models.FormPrevaluesSourceNode.ModelTypeAlias) - { - exceptions.Add(new Exception("'Source Node' needs to be of type 'FormPrevaluesSourceNode'")); - } - } - } - return exceptions; - } - } -} -``` - -You will then need to register this new type as a dependency (either in `Program.cs` or in your own IComposer, as shown here). - -```csharp -using Umbraco.Cms.Core.Composing; -using Umbraco.Cms.Core.DependencyInjection; -using Umbraco.Forms.Core.Providers; -namespace MyFormsExtensions -{ - public class FormsComposer : IComposer - { - public void Compose(IUmbracoBuilder builder) - { - //Adding Custom Form PreValueSource - builder.WithCollectionBuilder() - .Add(); - } - } -} -``` diff --git a/14/umbraco-forms/developer/extending/adding-a-type.md b/14/umbraco-forms/developer/extending/adding-a-type.md deleted file mode 100644 index c1b1784e3dc..00000000000 --- a/14/umbraco-forms/developer/extending/adding-a-type.md +++ /dev/null @@ -1,222 +0,0 @@ -# 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. - -## Preparations - -Create a new class library project in Visual Studio add references to the `Umbraco.Forms.Core.dll` (available via referencing the [NuGet package](https://www.nuget.org/packages/Umbraco.Forms.Core/)). You might also need to reference [Umbraco.Forms.Core.Providers](https://www.nuget.org/packages/Umbraco.Forms.Core.Providers/). - -## Adding the type to Forms - -The Forms API contains a collection of classes that can be registered at startup or in an Umbraco component. 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. - -```csharp -public class LogWorkflow : Umbraco.Forms.Core.WorkflowType -{ - private readonly ILogger _logger; - - public LogWorkflow(ILogger logger) - { - _logger = logger; - } - - public override WorkflowExecutionStatus Execute(WorkflowExecutionContext context) - { - throw new NotImplementedException(); - } - - public override List 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. - -Any dependencies required that are registered with the dependency injection container can be provided via the constructor. - -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 constructor like this: - -```csharp -public LogWorkflow(ILogger logger) { - - _logger = logger; - - 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: - -```csharp -[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: - -```csharp -[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(WorkflowExecutionContext context) { - _logger.LogInformation("Record submitted from: {IP}", context.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. - -Each setting value is stored as a string with the user interface for generating the value defined via the `View` property. - -Umbraco Forms ships with [setting types and you can also create your own](./setting-types.md). - -## 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. - -```csharp -public override List ValidateSettings() { - List exceptions = new List(); - 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 - -To register the type, ensure your web application project has a reference to the class library, either via a project or NuGet reference. -Then add the following code into the startup pipeline. In this example, the registration is implemented as an extension method to `IUmbracoBuilder` and should be called from `Program.cs`: - -```csharp -public static IUmbracoBuilder AddUmbracoFormsCustomProviders(this IUmbracoBuilder builder) -{ - builder.WithCollectionBuilder() - .Add(); -} -``` - -An alternative approach is to use a composer, as per this example: - -```csharp -public class UmbracoFormsCustomProvidersComposer : IComposer -{ - public void Compose(IUmbracoBuilder builder) - { - builder.WithCollectionBuilder() - .Add(); - } -} -``` - -There are further convenience methods you can use for registering custom types. These are found in the namespace `Umbraco.Forms.Core.Providers.Extensions`. - -For example, instead of the following: - -```csharp - builder.WithCollectionBuilder() - .Add(); -``` - -Your workflow can be registered using: - -```csharp - builder.AddFormsWorkflow(): -``` - -Or: - -```csharp - builder.FormsWorkflows().Add(); -``` - -Existing items that are not required in a particular installation can be removed with: - -```csharp - builder.FormsWorkflows().Exclude(); -``` - -Also look in the reference chapter for complete class implementations of workflows, fields and export types. - -## Overriding default providers in Umbraco Forms - -It is possible to override and 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. - -```csharp -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 ValidateField(Form form, Field field, IEnumerable postedValues, HttpContext context, IPlaceholderParsingService placeholderParsingService, List errors) - { - var baseValidation = base.ValidateField(form, field, postedValues, context, placeholderParsingService, errors); - var value = postedValues.FirstOrDefault(); - - if (value != null && value.ToString().Length < int.Parse(MaxNumberOfChars)) - { - return baseValidation; - } - - var custom = new List(); - custom.AddRange(baseValidation); - custom.Add("String is way way way too long!"); - - return custom; - } -} -``` - -As discussed in the previous section, you must also register the extended field type within a composer. You also need to create the the backoffice field type view. - -**Composer:** - -```csharp -public class UmbracoFormsCustomProvidersComposer : IComposer -{ - public void Compose(IUmbracoBuilder builder) - { - builder.FormsFields().Add(); - } -} -``` - -**Backoffice View:** - -Add a new HTML file as per the name of the field class (e.g. `textareawithcount.html`) to `\wwwroot\App_Plugins\umbracoforms\Backoffice\Common\FieldTypes\` within your project. For this example, we can copy the original `textarea.html` file used by the standard 'Long Answer' field. - -The AngularJS client-side files are shipped with Umbraco Forms as part of a Razor Class Library. So you won't find these files on disk when you install the package. - -However if you do want to reference them you can view and extract them from the [`Umbraco.Forms.StaticAssets` NuGet package](https://nuget.info/packages/Umbraco.Forms.StaticAssets). diff --git a/14/umbraco-forms/developer/extending/adding-a-validation-pattern.md b/14/umbraco-forms/developer/extending/adding-a-validation-pattern.md deleted file mode 100644 index dc7ace93bb3..00000000000 --- a/14/umbraco-forms/developer/extending/adding-a-validation-pattern.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -description: >- - Customize the regular expression based validation patterns available for text fields. ---- - -# Adding a Validation Pattern - -When creating a text field in Umbraco Forms, a validation pattern in the form of a regular expression can be applied. Default patterns can be removed or re-ordered, and custom ones created and added. - -## Provided patterns - -Umbraco Forms ships with three patterns: number, email, and URL. The class names are `Number`, `Email`, and `Url` respectively, and all are found in the -`Umbraco.Forms.Core.Providers.ValidationPatterns` namespace. - -## Creating a custom validation pattern - -To create a custom format function, create a class that implements `IValidationPattern`. You will need to initialize five properties: - -- `Alias` - an alias that should be unique across the patterns and is typically camel-cased with no spaces. -- `Name` - the name of the pattern that will be visible in the backoffice. -- `LabelKey` - as an alternative to providing a name, a translation key can be provided. This will be used to look-up the name in the correct language for the backoffice user. -- `Pattern` - the regular expression pattern. -- `ReadOnly` - a flag indicating whether the pattern can be edited in the backoffice. - -The following example shows the implementation of a pattern for a United Kingdom postcode (credit for the [pattern](https://stackoverflow.com/a/69806181/489433) to [Mecanik](https://stackoverflow.com/users/6583298/mecanik) at StackOverflow). - -```csharp -using Umbraco.Forms.Core.Interfaces; -namespace Umbraco.Forms.TestSite.Business.ValidationPatterns -{ - public class UkPostCode : IValidationPattern - { - public string Alias => "ukPostCode"; - public string Name => "UK Post Code"; - public string LabelKey => string.Empty; - public string Pattern => @"^([a-zA-Z]{1,2}[a-zA-Z\d]{1,2})\s(\d[a-zA-Z]{2})$"; - public bool ReadOnly => true; - } -} -``` - -## Registering the validation pattern - -As with other provider types, the validation pattern needs to be registered. There are options to add, remove, and re-order patterns. - -An example registration using the `IUmbracoBuilder` is shown below: - -```csharp -public static IUmbracoBuilder AddCustomProviders(this IUmbracoBuilder builder) -{ - builder.FormsValidationPatterns() - .Append(); - return builder; -} -``` - -## Using the pattern - -With the pattern registered it will be available for selection by editors in the backoffice when they create validation for fields supporting this feature. - -![Validation pattern](../images/validation-pattern.png) \ No newline at end of file diff --git a/14/umbraco-forms/developer/extending/adding-a-workflowtype.md b/14/umbraco-forms/developer/extending/adding-a-workflowtype.md deleted file mode 100644 index 019f24f030d..00000000000 --- a/14/umbraco-forms/developer/extending/adding-a-workflowtype.md +++ /dev/null @@ -1,119 +0,0 @@ -# Adding a workflow type to Umbraco Forms - -*This builds on the "[adding a type to the provider model](adding-a-type.md)" chapter* - -Add a new class to your project and have it inherit from `Umbraco.Forms.Core.WorkflowType`, and implement the class. For this sample, we will focus on the execute method. This method processes the current record (the data submitted by the form) and have the ability to change data and state. - -```csharp -using Serilog; -using System; -using System.Collections.Generic; -using Umbraco.Forms.Core; -using Umbraco.Forms.Core.Data.Storage; -using Umbraco.Forms.Core.Enums; -using Umbraco.Forms.Core.Persistence.Dtos; -using Microsoft.Extensions.Logging; -using Umbraco.Core.Composing; - -namespace MyFormsExtensions -{ - public class TestWorkflow : WorkflowType - { - private readonly ILogger _logger; - - public TestWorkflow(ILogger logger) - { - _logger = logger; - - this.Id = new Guid("ccbeb0d5-adaa-4729-8b4c-4bb439dc0202"); - this.Name = "TestWorkflow"; - this.Description = "This workflow is just for testing"; - this.Icon = "icon-chat-active"; - this.Group = "Services"; - } - - public override Task ExecuteAsync(WorkflowExecutionContext context) - { - // first we log it - _logger.LogDebug("the IP " + context.Record.IP + " has submitted a record"); - - // we can then iterate through the fields - foreach (RecordField rf in context.Record.RecordFields.Values) - { - // and we can then do something with the collection of values on each field - List vals = rf.Values; - - // or get it as a string - rf.ValuesAsString(false); - } - - //Change the state - context.Record.State = FormState.Approved; - - _logger.LogDebug("The record with unique id {RecordId} that was submitted via the Form {FormName} with id {FormId} has been changed to {RecordState} state", - context.Record.UniqueId, context.Form.Name, context.Form.Id, "approved"); - - return Task.FromResult(WorkflowExecutionStatus.Completed); - } - - public override List ValidateSettings() - { - return new List(); - } - } -} -``` - -## Information available to the workflow - -### Record information - -The `ExecuteAsync()` method gets a `WorkflowExecutionContext` which has properties for the related `Form`, `Record`, and `FormState`. This parameter contains all information related to the workflow. - -The `Record` contains all data and metadata submitted by the form. As shown in the example above, you can iterate over all `RecordField` values in the form. You can also retrieve a specific record field by alias using the following method: - -```csharp -RecordField? recordField = context.Record.GetRecordFieldByAlias("myalias"); -``` - -Having obtained a reference to a record field, the submitted value can be retrieved via: - -```csharp -var fieldValue = recordField.ValuesAsString(false); -``` - -The `ValuesAsString` will JSON escape the result by default. If you do not want this escaping to occur, pass `false` as the parameter. - -If the field stores multiple values, they are delimited with a comma. In many cases, you can safely split on that delimiter to obtain the individual values. However, this can lead to issues if the prevalues being selected also contain commas. If that's a concern, the following extension method is available in `Umbraco.Forms.Core.Extensions` to correctly parse the selected prevalues: - -```csharp -IEnumerable selectedPrevalues = recordField.GetSelectedPrevalues(); -``` - -### Form and state information - -The `Form` references the form the record is from and `FormState` provides its state (submitted or approved). - -Other context, such as the current `HttpContext`, if needed can be passed as constructor parameters (for example: the `HttpContext` can be accessed by injecting `IHttpContextAccessor`). - -## Registering the workflow type - -To use the new workflow type, you will need to register it as part of application startup. - -```csharp -using Umbraco.Cms.Core.Composing; -using Umbraco.Cms.Core.DependencyInjection; -using Umbraco.Forms.Core.Providers; - -namespace MyFormsExtensions -{ - public class Startup : IComposer - { - public void Compose(IUmbracoBuilder builder) - { - builder.WithCollectionBuilder() - .Add(); - } - } -} -``` diff --git a/14/umbraco-forms/developer/extending/adding-an-event-handler.md b/14/umbraco-forms/developer/extending/adding-an-event-handler.md deleted file mode 100644 index 0a6736dcdd9..00000000000 --- a/14/umbraco-forms/developer/extending/adding-an-event-handler.md +++ /dev/null @@ -1,181 +0,0 @@ ---- -description: "See an example of validating a form server-side" ---- - -# Adding A Server-Side Notification Handler To Umbraco Forms - -## Form validation notification - -Add a new class to your project as a handler for the `FormValidateNotification` notification: - -```csharp -using System.Linq; -using Microsoft.AspNetCore.Http; -using Umbraco.Cms.Core.Events; -using Umbraco.Forms.Core.Models; -using Umbraco.Forms.Core.Services.Notifications; - -namespace MyFormsExtensions -{ - /// - /// Catch form submissions before being saved and perform custom validation. - /// - public class FormValidateNotificationHandler : INotificationHandler - { - public void Handle(FormValidateNotification notification) - { - // If needed, be selective about which form submissions you affect. - if (notification.Form.Name == "Form Name") - { - // Check the ModelState - if (notification.ModelState.IsValid == false) - { - return; - } - - // A sample validation - var email = GetPostFieldValue(notification.Form, notification.Context, "email"); - var emailConfirm = GetPostFieldValue(notification.Form, notification.Context, "verifyEmail"); - - // If the validation fails, return a ModelError - if (email.ToLower() != emailConfirm.ToLower()) - { - notification.ModelState.AddModelError(GetPostField(notification.Form, "verifyEmail").Id.ToString(), "Email does not match"); - } - } - } - - private static string GetPostFieldValue(Form form, HttpContext context, string key) - { - Field field = GetPostField(form, key); - if (field == null) - { - return string.Empty; - } - - - return context.Request.HasFormContentType && context.Request.Form.Keys.Contains(field.Id.ToString()) - ? context.Request.Form[field.Id.ToString()].ToString().Trim() - : string.Empty; - } - - private static Field GetPostField(Form form, string key) => form.AllFields.SingleOrDefault(f => f.Alias == key); - } -} -``` - -The handler will check the `ModelState` and `Form` field values provided in the notification. If validation fails, we add a `ModelError`. - -To register the handler, add the following code into the startup pipeline. In this example, the registration is implemented as an extension method to `IUmbracoBuilder` and should be called from `Program.cs`: - -```csharp -public static IUmbracoBuilder AddUmbracoFormsCoreProviders(this IUmbracoBuilder builder) -{ - builder.AddNotificationHandler(); -} -``` - -## Service notifications - -The services available via interfaces `IFormService`, `IFolderService`, `IDataSourceService` and `IPrevalueSourceService` trigger following notifications before or after an entity handled by the service is modified. - -The "-ing" events allow for the entity being changed to be modified before the operation takes place, or to cancel the operation. The "-ed" events fire after the update is complete. - -Both can be wired up using a composer and component: - -```csharp - public class TestSiteComposer : IComposer - { - public void Compose(IUmbracoBuilder builder) - { - builder.AddNotificationHandler(); - } - } - - public class FormSavingNotificationHandler : INotificationHandler - { - public void Handle(FormSavingNotification notification) - { - foreach (Form form in notification.SavedEntities) - { - foreach (Page page in form.Pages) - { - foreach (FieldSet fieldset in page.FieldSets) - { - foreach (FieldsetContainer fieldsetContainer in fieldset.Containers) - { - foreach (Field field in fieldsetContainer.Fields) - { - field.Caption += " (updated)"; - } - } - } - } - } - } - } -``` - -When a form or folder is _moved_ there is no specific service event. However, information available in the `State` dictionary on the notification object can be used to determine whether the item was moved. If so, it can show where it was moved from: - -```csharp - public class TestSiteComposer : IComposer - { - public void Compose(IUmbracoBuilder builder) - { - builder.AddNotificationHandler(); - } - } - - public class FormSavingNotificationHandler : INotificationHandler - { - private readonly ILogger _logger; - - public FormSavingNotificationHandler(ILogger logger) => _logger = logger; - - public void Handle(FormSavingNotification notification) - { - foreach (Form savedEntity in notification.SavedEntities) - { - _logger.LogInformation($"Form updated. New parent: {savedEntity.FolderId}. Old parent: {notification.State["MovedFromFolderId"]}"); - } - } - } -``` - -If a folder is being moved, the key within the `State` dictionary is `"MovedFromParentId"`. - -## Backoffice entry rendering events - -When an entry for a form is rendered in the backoffice, an event is available to allow modification of the record detail. This event is available before the record details are presented to the user. This is shown in the following example: - -```csharp - public class TestSiteComposer : IComposer - { - public void Compose(IUmbracoBuilder builder) - { - builder.AddNotificationHandler(); - } - } - - public class EntrySearchResultFetchingNotificationHandler : INotificationHandler - { - public void Handle(EntrySearchResultFetchingNotification notification) - { - var transformedFields = new List(); - foreach (var field in notification.EntrySearchResult.Fields) - { - if (field?.ToString() == "Test") - { - transformedFields.Add("Test (updated)"); - } - else - { - transformedFields.Add(field); - } - } - - notification.EntrySearchResult.Fields = transformedFields; - } - } -``` diff --git a/14/umbraco-forms/developer/extending/customize-default-workflows.md b/14/umbraco-forms/developer/extending/customize-default-workflows.md deleted file mode 100644 index cd420da3ca3..00000000000 --- a/14/umbraco-forms/developer/extending/customize-default-workflows.md +++ /dev/null @@ -1,257 +0,0 @@ ---- -description: "How to amend the built-in behavior of adding fields and associating workflows with new forms" ---- - -# Customize Default Fields and Workflows For a Form - -By default, a single workflow is added when a new form is created. This workflow will send a copy of the form to the email address of the current backoffice user. - -A single "data consent" field will also be added unless it has been disabled via configuration. - -It's possible to amend this behavior and change it to fit your needs. - -## Implementing a Custom Behavior - -Two interfaces are used to abstract the logic for setting default fields and workflows for a form. They are `IApplyDefaultFieldsBehavior` and `IApplyDefaultWorkflowsBehavior` respectively. - -The default behaviors are defined using built-in, internal classes that implement this interface. - -You can create your own implementation of these interfaces. - -### Example - Providing a Custom Apply Workflows Behavior - -An illustrative example, adding a custom workflow that writes to the log, is shown below. - -Firstly, the custom workflow: - -```csharp -using System; -using System.Collections.Generic; -using Umbraco.Core.Composing; -using Umbraco.Core.Logging; -using Umbraco.Forms.Core.Attributes; -using Umbraco.Forms.Core.Enums; -using Umbraco.Forms.Core.Persistence.Dtos; - -namespace MyNamespace -{ - public class LogMessageWorkflow : WorkflowType - { - public const string LogMessageWorkflowId = "7ca500a7-cb34-4a82-8ae9-2acac777382d"; - private readonly ILogger _logger; - - public LogMessageWorkflow(ILogger logger) - { - Id = new Guid(LogMessageWorkflowId); - Name = "Test Workflow"; - Description = "A test workflow that writes a log line"; - Icon = "icon-edit"; - - _logger = logger; - } - - [Setting("Message", Description = "The log message to write", View = "TextField")] - public string Message { get; set; } - - public override List ValidateSettings() - { - var exs = new List(); - if (string.IsNullOrEmpty(Message)) - { - exs.Add(new Exception("'Message' setting has not been set")); - } - - return exs; - } - - public override WorkflowExecutionStatus Execute(WorkflowExecutionContext context) - { - _logger.LogInformation($"'{Message}' written at {DateTime.Now}"); - return WorkflowExecutionStatus.Completed; - } - } -} -``` - -Secondly, the custom implementation of `IApplyDefaultWorkflowsBehavior`: - -```csharp -using System; -using System.Collections.Generic; -using System.Linq; -using Umbraco.Cms.Core.Hosting; -using Umbraco.Forms.Core; -using Umbraco.Forms.Core.Enums; -using Umbraco.Forms.Core.Providers; -using Umbraco.Forms.Web.Behaviors; -using Umbraco.Forms.Web.Models.Backoffice; - -namespace MyNamespace -{ - public class CustomApplyDefaultWorkflowsBehavior : IApplyDefaultWorkflowsBehavior - { - private readonly WorkflowCollection _workflowCollection; - private readonly IHostingEnvironment _hostingEnvironment; - - public CustomApplyDefaultWorkflowsBehavior( - WorkflowCollection workflowCollection, IHostingEnvironment hostingEnvironment) - { - _workflowCollection = workflowCollection; - _hostingEnvironment = hostingEnvironment; - } - - public void ApplyDefaultWorkflows(FormDesign form) - { - // Retrieve the type of the default workflow to add. - WorkflowType testWorkflowType = _workflowCollection[new Guid(LogMessageWorkflow.LogMessageWorkflowId)]; - - // Create a workflow object based on the workflow type. - var defaultWorkflow = new FormWorkflowWithTypeSettings - { - Id = Guid.Empty, - Name = "Log a message", - Active = true, - IncludeSensitiveData = IncludeSensitiveData.False, - SortOrder = 1, - WorkflowTypeId = testWorkflowType.Id, - WorkflowTypeName = testWorkflowType.Name, - WorkflowTypeDescription = testWorkflowType.Description, - WorkflowTypeGroup = testWorkflowType.Group, - WorkflowTypeIcon = testWorkflowType.Icon, - - // Optionally set the default workflow to be mandatory (which means editors won't be able to remove it - // via the back-office user interface). - IsMandatory = true - }; - - // Retrieve the settings from the type. - Dictionary workflowTypeSettings = testWorkflowType.Settings(); - - // Create a collection for the specific settings to be applied to the workflow. - // Populate with the setting details from the type. - var workflowSettings = new List(); - foreach (KeyValuePair setting in workflowTypeSettings) - { - Core.Attributes.Setting settingItem = setting.Value; - - var settingItemToAdd = new SettingWithValue - { - Name = settingItem.Name, - Alias = settingItem.Alias, - Description = settingItem.Description, - Prevalues = settingItem.GetPreValues(), - View = _hostingEnvironment.ToAbsolute(settingItem.GetSettingView()), - Value = string.Empty - }; - - workflowSettings.Add(settingItemToAdd); - } - - // For each setting, provide a value for the workflow instance (in this example, we only have one). - SettingWithValue messageSetting = workflowSettings.SingleOrDefault(x => x.Alias == "Message"); - if (messageSetting != null) - { - messageSetting.Value = "A test log message"; - } - - // Apply the settings to the workflow. - defaultWorkflow.Settings = workflowSettings; - - // Associate the workflow with the appropriate form submission event. - form.FormWorkflows.OnSubmit.Add(defaultWorkflow); - } - } -} -``` - -Finally, to register the custom implementation in place of the default one: - -```csharp -using Umbraco.Cms.Core.Composing; -using Umbraco.Cms.Core.DependencyInjection; -using Umbraco.Extensions; -using Umbraco.Forms.Core.Providers; -using Umbraco.Forms.Testsite.Business.Workflows; -using Umbraco.Forms.Web.Behaviors; - -namespace MyNamespace -{ - public class TestSiteComposer : IComposer - { - public void Compose(IUmbracoBuilder builder) - { - builder.WithCollectionBuilder() - .Add(); - - builder.Services.AddUnique(); - } - } -} -``` - -#### Setting a Mandatory Default Workflow - -When adding a default workflow in code, it's possible to make it mandatory, which will prevent editors from removing it from a form. - -You can see this in the example above, where the `IsMandatory` property of the created `FormWorkflowWithTypeSettings` instance is set to `true`. - -### Example - Providing a Custom Apply Fields Behavior - -The following class shows the default implementation provided with Forms. You can copy this and customize it to your needs. - -```csharp -using Microsoft.Extensions.Options; -using Umbraco.Forms.Core.Configuration; -using Umbraco.Forms.Core.Models; -using Umbraco.Forms.Web.Extensions; -using Umbraco.Forms.Web.Models.Backoffice; - -namespace Umbraco.Forms.Web.Behaviors -{ - internal class CustomApplyDefaultFieldsBehavior : IApplyDefaultFieldsBehavior - { - private readonly FormDesignSettings _formDesignSettings; - - public CustomApplyDefaultFieldsBehavior(IOptions formDesignSettings) => - _formDesignSettings = formDesignSettings.Value; - - public virtual void ApplyDefaultFields(FormDesign form) - { - // Add one page as a starting point. - var page = new Page(); - form.Pages.Add(page); - - // Add one empty fieldset to the page to start with. - var fieldset = new FieldSet - { - Id = Guid.NewGuid() - }; - page.FieldSets.Add(fieldset); - - // Add one full-width (12cols) container/row to the fieldset. - var container = new FieldsetContainer - { - Width = 12 - }; - fieldset.Containers.Add(container); - - // As all forms default to having StoreRecordsLocally we need to add the data consent field to the the form - // (unless this feature has been explicitly disabled). - if (_formDesignSettings.DisableAutomaticAdditionOfDataConsentField) - { - return; - } - - container.AddDataConsentField(_formDesignSettings, _fieldCollection); - - // Add any further fields you require. - } - } -} -``` - -Again, you will need to register your custom class, for example, in a composer with: - -```csharp -builder.Services.AddUnique(); -``` diff --git a/14/umbraco-forms/developer/extending/excluding-a-built-in-field.md b/14/umbraco-forms/developer/extending/excluding-a-built-in-field.md deleted file mode 100644 index 9714474a3e0..00000000000 --- a/14/umbraco-forms/developer/extending/excluding-a-built-in-field.md +++ /dev/null @@ -1,28 +0,0 @@ -# Excluding a Built-in Field - -Umbraco Forms comes with some built-in fields however it is possible to exclude/remove them if necessary. -There might some use cases where you have no use for file upload and don't want editors using them. Or perhaps you want to remove a field to replace it with one with enhanced functionality that you build yourself. - -## Example - -The following class shows how to exclude built-in field types using a custom composer. The `Password`, `Recaptcha2` and `RichText` field types (or "answers") will no longer be available for selection when creating a form in the backoffice. - -```csharp -using Umbraco.Cms.Core.Composing; -using Umbraco.Forms.Core.Providers.Extensions; -using Umbraco.Forms.Core.Providers.FieldTypes; - -namespace MyNamespace -{ - public class MyFormFieldsComposer : IComposer - { - public void Compose(IUmbracoBuilder builder) - { - builder.FormsFields() - .Exclude() - .Exclude() - .Exclude(); - } - } -} -``` diff --git a/14/umbraco-forms/developer/extending/images/text-with-field-picker.png b/14/umbraco-forms/developer/extending/images/text-with-field-picker.png deleted file mode 100644 index bc822cbc599..00000000000 Binary files a/14/umbraco-forms/developer/extending/images/text-with-field-picker.png and /dev/null differ diff --git a/14/umbraco-forms/developer/extending/setting-types.md b/14/umbraco-forms/developer/extending/setting-types.md deleted file mode 100644 index 3918acdcc0b..00000000000 --- a/14/umbraco-forms/developer/extending/setting-types.md +++ /dev/null @@ -1,63 +0,0 @@ -# Setting Types - -Umbraco Forms field, prevalue source and workflow types are defined in C# and include one or more setting values. - -These settings are completed by the editor when using the type on their form. - -Each setting type can have it's own user interface. So a string can use a text box but a more complicated JSON structure can use a more appropriate user interface. - -From Forms 14, each interface is defined as an Umbraco [property editor UI](https://docs.umbraco.com/umbraco-cms/extending/property-editors/composition/property-editor-ui). - -The user interface used for a particular setting is defined by the `View` property: - -```csharp -[Umbraco.Forms.Core.Attributes.Setting("Message", View = "Umb.PropertyEditorUi.TextBox")] -public string Message { get; set; } -``` - -If not specified, the default `Umb.PropertyEditorUi.TextBox` is used. - -## Built-in setting types - -The following setting types are available and are used for the field, prevalue source and workflow types that ship with the package. - -Some are defined with the Umbraco CMS and some ship with the Forms package. - -| Name | Source | Description | Used in | -|--------------------------------------------------|--------------|-------------------------------------------------------------------|-------------------------------------------------| -| Umb.PropertyEditorUi.ContentPicker.Source | CMS | Uses a content picker with the option for XPath entry | The "Save as Umbraco node" workflow | -| Umb.PropertyEditorUi.Dropdown | CMS | Used for selection from a list of options | | -| Umb.PropertyEditorUi.Integer | CMS | Uses numerical text box for entry | | -| Umb.PropertyEditorUi.MediaEntityPicker | CMS | Uses a media item picker for entry | The "Send email with XSLT template" workflow | -| Umb.PropertyEditorUi.MultipleTextString | CMS | Uses multiple text boxes for entry | Not used in core types | -| Umb.PropertyEditorUi.Slider | CMS | Uses a slider for range input | The "reCAPTCHAv3" field type | -| Umb.PropertyEditorUi.TextArea | CMS | Uses a multiline textbox for entry | | -| Umb.PropertyEditorUi.TextBox | CMS | Uses a single-line textbox for entry | | -| Umb.PropertyEditorUi.TinyMCE | CMS | Uses a rich text editor for input | The "Send email" workflows | -| Umb.PropertyEditorUi.Toggle | CMS | Uses a single checkbox for entry | | -| Umb.PropertyEditorUi.UploadField | CMS | Used for selection of a file | The "Text file" prevalue source | -| Forms.PropertyEditorUi.DataTypePicker | Forms | Uses a datatype picker | The "Umbraco prevalues" prevalue source | -| Forms.PropertyEditorUi.DocumentTypePicker | Forms | Uses a Document Type picker | The "Umbraco nodes" prevalue source | -| Forms.PropertyEditorUi.DocumentTypeFieldPicker | Forms | Uses to select fields from a Document Type | The "Umbraco nodes" prevalue source | -| Forms.PropertyEditorUi.DocumentMapper | Forms | Used for mapping of fields from a Document Type | The "Save as Umbraco node" workflow | -| Forms.PropertyEditorUi.EmailTemplatePicker | Forms | Used for selection of an email template | The "Send email with Razor template" workflow | -| Forms.PropertyEditorUi.FieldMapper | Forms | Used to map fields from a form to required aliases | The "Send to URL" workflow | -| Forms.PropertyEditorUi.Password | Forms | Uses password text box for entry | | -| Forms.PropertyEditorUi.StandardFieldMapper | Forms | Used to map system fields from a form to required aliases | The "Send to URL" workflow | -| Forms.PropertyEditorUi.TextWithFieldPicker | Forms | Uses a single-line textbox/form field list for entry | Not used in core types | - -Most of the above setting types are used in one or more field, prevalue source and workflow types available with Umbraco Forms. For the less common ones, a usage has been indicated in the table. - -## Additional setting types - -Some types we don't use within the package, but we make available for developers to use when creating their own types. - -For example `Forms.PropertyEditorUi.TextWithFieldPicker`. This offers the option of text field entry or the selection of a field from the form. This can be useful in workflows where you need to reference the value of a specific field. - -![Text with field picker](./images/text-with-field-picker.png) - -## Creating a setting type - -It's also possible to define your own setting type using a combination of server and client-side code. - -Read how do this in the article on [adding a custom field type](./adding-a-fieldtype.md#field-settings). diff --git a/14/umbraco-forms/developer/field-types.md b/14/umbraco-forms/developer/field-types.md deleted file mode 100644 index e6f058dd377..00000000000 --- a/14/umbraco-forms/developer/field-types.md +++ /dev/null @@ -1,31 +0,0 @@ -# Field Types - -Umbraco Forms comes with a number of Field Types to allow you to request certain data in the forms that you design & build. This documentation is to guide specific details about field types that we ship that require some detail in how they work. - -## Date Picker - -The date picker uses a front-end library called [PikaDay.js](https://github.com/dbushell/Pikaday) to display a UI to pick dates from. We have added the support for the Pikaday date picker to be localized based on the page the form is rendered on. This displays the picked date in the correct locale. In JavaScript, we update a hidden field with a standard date format. This is done to send the date to the server, ensuring the record submission is stored in a standard format. This is to avoid locale mixing up dates. - -To achieve this a new Razor partial view is included `/Views/Partials/Forms/DatePicker.cshtml`. Once on a page with a form that includes a Date Picker, it also includes the MomentJS library to assist with date locale formatting. Additionally, there are appropriate changes to Pikaday.js to support the locales. If you wish to use a different DatePicker component this is the file that you would customize to your needs. - -### Date Picker configuration of the year range - -The `DatePicker` has one configuration setting to control the number of year shown. The default is 10 years which makes the picker unusable for picking birth dates. - -Go to your `appsettings.json` and add: -```json - "Umbraco": { - "CMS": { - ... - }, - "Forms": { - "FieldTypes": { - "DatePicker": { - "DatePickerYearRange": 12 - } - } - } - } -``` - -You can then change the `DatePickerYearRange` to a higher number (for example 100). diff --git a/14/umbraco-forms/developer/files/umbraco-forms-default-theme-14.0.0.zip b/14/umbraco-forms/developer/files/umbraco-forms-default-theme-14.0.0.zip deleted file mode 100644 index 259a3800311..00000000000 Binary files a/14/umbraco-forms/developer/files/umbraco-forms-default-theme-14.0.0.zip and /dev/null differ diff --git a/14/umbraco-forms/developer/files/umbraco-forms-default-theme-14.0.1.zip b/14/umbraco-forms/developer/files/umbraco-forms-default-theme-14.0.1.zip deleted file mode 100644 index 9e8eef543d9..00000000000 Binary files a/14/umbraco-forms/developer/files/umbraco-forms-default-theme-14.0.1.zip and /dev/null differ diff --git a/14/umbraco-forms/developer/files/umbraco-forms-default-theme-14.1.0.zip b/14/umbraco-forms/developer/files/umbraco-forms-default-theme-14.1.0.zip deleted file mode 100644 index 0c7a79230c4..00000000000 Binary files a/14/umbraco-forms/developer/files/umbraco-forms-default-theme-14.1.0.zip and /dev/null differ diff --git a/14/umbraco-forms/developer/files/umbraco-forms-default-theme-14.1.4.zip b/14/umbraco-forms/developer/files/umbraco-forms-default-theme-14.1.4.zip deleted file mode 100644 index 495887875c7..00000000000 Binary files a/14/umbraco-forms/developer/files/umbraco-forms-default-theme-14.1.4.zip and /dev/null differ diff --git a/14/umbraco-forms/developer/files/umbraco-forms-default-theme-14.2.0.zip b/14/umbraco-forms/developer/files/umbraco-forms-default-theme-14.2.0.zip deleted file mode 100644 index 65651543110..00000000000 Binary files a/14/umbraco-forms/developer/files/umbraco-forms-default-theme-14.2.0.zip and /dev/null differ diff --git a/14/umbraco-forms/developer/files/umbraco-forms-default-theme-14.2.4.zip b/14/umbraco-forms/developer/files/umbraco-forms-default-theme-14.2.4.zip deleted file mode 100644 index 03e372d63c2..00000000000 Binary files a/14/umbraco-forms/developer/files/umbraco-forms-default-theme-14.2.4.zip and /dev/null differ diff --git a/14/umbraco-forms/developer/forms-in-the-database.md b/14/umbraco-forms/developer/forms-in-the-database.md deleted file mode 100644 index e49ef383ec9..00000000000 --- a/14/umbraco-forms/developer/forms-in-the-database.md +++ /dev/null @@ -1,53 +0,0 @@ -# Umbraco Forms in the Database - -In Umbraco Forms, it is _only_ possible to store Form data in the database. - -If you are upgrading to Umbraco 9 or later and using Forms, you should first migrate the Forms to the database using Forms 8. As of Umbraco Forms version 8.5.0 it is possible to persist all Forms data in the Umbraco database. This includes definitions for each Form and their fields, as well as workflow definitions and prevalues. - -{% hint style="info" %} -**Custom file system providers** - -If [custom file system providers are used on your project for storing Umbraco Forms data](https://docs.umbraco.com/umbraco-cms/extending/filesystemproviders#custom-providers), the migration will not be able to run. - -To persist your Umbraco Forms data in the database, you will need to revert to a **standard Umbraco Forms configuration**. Use the default provider to store the Forms definition files in the default location. - -You need to ensure that your Forms definition files are moved from their previous location. This is a non-default file path, blob storage, or similar to the default location, `App_Data/UmbracoForms`, that Forms will now be using. - -Your configuration is now considered a standard configuration and you can perform the steps required for a normal migration. -{% endhint %} - -## Enable storing Forms definitions in the database - -To persist Umbraco Forms definitions in the database, follow these steps: - -1. Upgrade to at least Umbraco Forms version 8.5.2. -2. Open the configuration file `App_Plugins\UmbracoForms\UmbracoForms.config`. -3. Locate the `StoreUmbracoFormsInDb` key in the `` section, and make sure it has the following value: - - ```xml - - ``` - -4. Save the file. - -If you are working with a Umbraco Cloud project, make sure you follow the migration steps outlined in the [Umbraco Forms on Cloud](https://docs.umbraco.com/umbraco-cloud/deployments/umbraco-forms-on-cloud) article. - -{% hint style="warning" %} -Enabling the persisting of Umbraco Forms in the database is irreversible. Once you've made the change, reverting to the file approach will not be an option. -{% endhint %} - -When you save the file, the site will restart and run a migration step, migrating the files to the Umbraco database. - -## Migrating Forms in files into a site - -You can force Forms to rerun the migration of the file-format Forms if you have a Umbraco 8 site storing Forms in the database. - -First of all, you should ensure that you have enabled the setting that persists Forms in the database, as the migration requires this (`StoreUmbracoFormsInDb`) key. We highly recommend testing this on a local setup before applying it to your live site. - -1. Copy over the Forms, workflows, prevaluesources, and datasource files to the site into `~\App_Data\UmbracoForms\Data`. -2. Go to the database and find the `[umbracoKeyValue]` table. -3. Find the Form's row and check that the value is `1d084819-84ba-4ac7-b152-2c3d167d22bc` (if not you are not currently working with Forms in the database, changing the setting should be enough). -4. Change that value to `{forms-init-complete}`. -5. Restart the site. - -The site will now try to migrate the Forms files into the database. In the umbracoTraceLog, you can follow the progress. It will throw errors if anything goes wrong. Additionally, it will log out "The Umbraco Forms DB table {TableName} already exists" for the 4 Forms tables before starting the migration. diff --git a/14/umbraco-forms/developer/healthchecks/README.md b/14/umbraco-forms/developer/healthchecks/README.md deleted file mode 100644 index d9b34c2e10b..00000000000 --- a/14/umbraco-forms/developer/healthchecks/README.md +++ /dev/null @@ -1,115 +0,0 @@ -# Health Checks - -In this article, you will find information about Umbraco Forms-related health checks that can be run from the Umbraco backoffice to ensure that your installation is running seamlessly. - -Read the [Health Check](https://docs.umbraco.com/umbraco-cms/extending/health-check) article to learn more about the feature in general. - -## Database Integrity Health Check - -Running this health check will verify whether the database tables for the Umbraco Forms installation are all set up correctly with the proper data integrity checks. - -In this section, you can learn more about the background for adding this check, as well as how to use and understand the results. - -### Background - -A health check was introduced to confirm the Umbraco Forms database tables are all set up with the expected data integrity checks - i.e. primary keys, foreign keys and unique constraints. - -In most cases, you can expect them all to be in place without any developer intervention. For new installs, the database schema is initialized with all the necessary integrity constraints. And for upgrades, any new schema changes are automatically applied. - -There remains the possibility though that not all will be in place for a particular installation. For example, this could happen if a constraint is added in a new version. It can't be added via an automated migration due to existing data integrity issues. - -In particular, prior to version 8.7, there were a number of tables that weren't defined as strictly as they should be in this area. So we've added some primary key, foreign key and unique constraints with this version. If you've been running a version prior to this and are upgrading, these schema updates will be applied automatically _unless_ there is existing data in the tables that prevent them from being added. - -There shouldn't be - but without these constraints in place it's always possible for an application bug to exist that allows for example the creation of duplicate records, or the orphaning of records, that aren't correct. This is the reason for the constraints to exist, and why we want to ensure they are in place. - -### Running The Health Check - -To run the health check: - -1. Navigate to the **Health Check** dashboard in the **Settings** section in the Umbraco backoffice. - -
-2. Click on the **Forms** button and select **Perform checks**. You'll see a result that looks something like this: - -
- -If you have a full set of green ticks, then you're all good - and no need to read on! - -If you have one or more red crosses though, that means a particular constraint wasn't able to be applied via the automatic schema migrations when you installed a new version of Umbraco Forms, due to existing data issues. - -It isn't essential that they are resolved - the package can and does function correctly without them - but for reasons of ensuring data integrity and performance, it is recommended that they are. - -### Resolving Reported Problems - -When Umbraco Forms installs an upgrade, it will attempt to apply any schema changes. If though, the update isn't essential, and it can't proceed due to existing data integrity issues, the failed update will be logged and then the rest of the migration will continue. - -As well as in the log files, such issues will be visible via the health check and will need to be resolved by applying scripts directly to the database. - -To support this, we provide the following SQL scripts: - -* Apply database integrity schema changes for 8.7.0+ - [8.7.0-apply-keys-and-indexes](apply-keys.md) -* Apply database integrity schema changes for 8.7.0+ (Forms in database tables) - [8.7.0-apply-keys-and-indexes-forms-in-db](forms-in-the-database-apply-keys.md) - -The first of these provides the SQL statements required to apply the schema updates for 8.7.0+ to the common Umbraco Forms tables. The second applies to those tables used for when Forms are stored in the database, and hence only need to be applied if that option is configured. - -{% hint style="info" %} -Before running any scripts or queries, please be sure to have a database backup in place. -{% endhint %} - -To take an example, let's say that via the health check results you can see that the _"Unique constraint on table 'UFForms', column 'Key' is missing."_ - -If you look in the SQL script you'll see that in order to apply this directly to the database, you would need to run the following SQL statement: - -```sql --- Adds unique constraint to UFForms. -ALTER TABLE dbo.UFForms -ADD CONSTRAINT UK_UFForms_Key UNIQUE NONCLUSTERED -( - [Key] ASC -) WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] -GO -``` - -If you run it though, you'll see the reason why the migration that ran when Umbraco Forms was upgraded couldn't apply the change: - -```sql -The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.UFForms' and the index name 'UK_UFForms_Key'. The duplicate key value is (...). -``` - -The constraint can't be applied if there are existing duplicate values, so first they need to be found and removed. - -To find duplicate values in the 'Key' field in this table you can run the following SQL statement: - -```sql -SELECT [Key] -FROM UFForms -GROUP BY [Key] -HAVING COUNT(*) > 1 -``` - -Running the statement above will list out the 'Key' fields that are duplicated in the table. - -To see the full details of the duplicate records, you can use this query: - -```sql -SELECT * -FROM UFForms -WHERE [Key] IN (SELECT [Key] - FROM UFForms - GROUP BY [Key] - HAVING COUNT(*) > 1 -) -``` - -From the `Id` field you can identify the Form records that are duplicated and should be removed, and delete the records. To check you have found them all, run one of the above queries again, and confirm you find no records returned. - -Finally you can run the `ALTER TABLE...` statement shown above to apply the constraint, and confirm via the health check that it's now in place. - -By repeating similar steps as required, you'll be able to ensure that all recommended keys, constraints and indexes are in place. - -If for any reason you wish to revert the changes - perhaps when testing these updates in a non-production environment - reversion scripts for all the 8.7 updates are also provided: - -To support this, we provide the following SQL scripts: - -* Revert database integrity schema changes for 8.7.0+ - [8.7.0-apply-keys-and-indexes\_revert](apply-keys.md#revert-application-of-keys-and-indexes) -* Revert database integrity schema changes for 8.7.0+ (Forms in database tables) - [8.7.0-apply-keys-and-indexes-forms-in-db\_revert](forms-in-the-database-apply-keys.md#reverting-the-application-of-keys-and-indexes) diff --git a/14/umbraco-forms/developer/healthchecks/apply-keys.md b/14/umbraco-forms/developer/healthchecks/apply-keys.md deleted file mode 100644 index 2a1213bd225..00000000000 --- a/14/umbraco-forms/developer/healthchecks/apply-keys.md +++ /dev/null @@ -1,231 +0,0 @@ -# Apply keys and indexes - -```sql -/* - Applies recommended primary keys, foreign keys and indexes to core Umbraco Forms tables. - This replicates for SQL Server the migration AddRecordKeysAndIndexes. - */ - --- Adds relationship between UFRecords and UFRecordFields. -ALTER TABLE dbo.UFRecordFields -ADD CONSTRAINT - FK_UFRecordFields_UFRecords_Record FOREIGN KEY - ( - Record - ) REFERENCES dbo.UFRecords - ( - Id - ) ON UPDATE NO ACTION - ON DELETE NO ACTION -GO - --- Adds primary keys to UFRecordData* tables. -ALTER TABLE dbo.UFRecordDataBit -ADD CONSTRAINT - PK_UFRecordDataBit PRIMARY KEY CLUSTERED - ( - Id - ) WITH( STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] -GO - -ALTER TABLE dbo.UFRecordDataDateTime -ADD CONSTRAINT - PK_UFRecordDataDateTime PRIMARY KEY CLUSTERED - ( - Id - ) WITH( STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] -GO - -ALTER TABLE dbo.UFRecordDataInteger -ADD CONSTRAINT - PK_UFRecordDataInteger PRIMARY KEY CLUSTERED - ( - Id - ) WITH( STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] -GO - -ALTER TABLE dbo.UFRecordDataLongString -ADD CONSTRAINT - PK_UFRecordDataLongString PRIMARY KEY CLUSTERED - ( - Id - ) WITH( STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] -GO - --- Adds relationship between UFRecordFields and UFREcordData* tables. -ALTER TABLE dbo.UFRecordDataBit -ADD CONSTRAINT - FK_UFRecordDataBit_UFRecordFields_Key FOREIGN KEY - ( - [Key] - ) REFERENCES dbo.UFRecordFields - ( - [Key] - ) ON UPDATE NO ACTION - ON DELETE NO ACTION -GO - -ALTER TABLE dbo.UFRecordDataDateTime -ADD CONSTRAINT - FK_UFRecordDataDateTime_UFRecordFields_Key FOREIGN KEY - ( - [Key] - ) REFERENCES dbo.UFRecordFields - ( - [Key] - ) ON UPDATE NO ACTION - ON DELETE NO ACTION -GO - -ALTER TABLE dbo.UFRecordDataInteger -ADD CONSTRAINT - FK_UFRecordDataInteger_UFRecordFields_Key FOREIGN KEY - ( - [Key] - ) REFERENCES dbo.UFRecordFields - ( - [Key] - ) ON UPDATE NO ACTION - ON DELETE NO ACTION -GO - -ALTER TABLE dbo.UFRecordDataLongString -ADD CONSTRAINT - FK_UFRecordDataLongString_UFRecordFields_Key FOREIGN KEY - ( - [Key] - ) REFERENCES dbo.UFRecordFields - ( - [Key] - ) ON UPDATE NO ACTION - ON DELETE NO ACTION -GO - --- Adds index on foreign key fields in UFREcordData* tables. -CREATE NONCLUSTERED INDEX IX_UFRecordDataBit_Key ON dbo.UFRecordDataBit -( - [Key] ASC -) WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] -GO - -CREATE NONCLUSTERED INDEX IX_UFRecordDataDateTime_Key ON dbo.UFRecordDataDateTime -( - [Key] ASC -) WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] -GO - -CREATE NONCLUSTERED INDEX IX_UFRecordDataInteger_Key ON dbo.UFRecordDataInteger -( - [Key] ASC -) WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] -GO - -CREATE NONCLUSTERED INDEX IX_UFRecordDataLongString_Key ON dbo.UFRecordDataLongString -( - [Key] ASC -) WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] -GO - --- Adds primary key to UFUserSecurity. -ALTER TABLE dbo.UFUserSecurity -ADD CONSTRAINT - PK_UFUserSecurity PRIMARY KEY CLUSTERED - ( - [User] - ) WITH( STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] -GO - --- Adds primary key to UFUserFormSecurity. -ALTER TABLE dbo.UFUserFormSecurity -ADD CONSTRAINT - PK_UFUserFormSecurity PRIMARY KEY CLUSTERED - ( - Id - ) WITH( STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] -GO - --- Adds unique constraint to UFUserFormSecurity across user/form fields. -ALTER TABLE dbo.UFUserFormSecurity -ADD CONSTRAINT UK_UFUserFormSecurity_User_Form UNIQUE NONCLUSTERED -( - [User] ASC, - [Form] ASC -) WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] -GO -``` - -## Revert application of keys and indexes - -```sql -/* - Reverts application of recommended primary keys, foreign keys and indexes to core Umbraco Forms tables. - This reverts for SQL Server the migration AddRecordKeysAndIndexes and can be used for rolling that back in testing. - */ - --- Reverts addition of relationship between UFRecords and UFRecordFields. -ALTER TABLE dbo.UFRecordFields -DROP CONSTRAINT IF EXISTS FK_UFRecordFields_UFRecords_Record -GO - --- Reverts addition of primary keys to UFRecordData* tables. -ALTER TABLE dbo.UFRecordDataBit -DROP CONSTRAINT IF EXISTS PK_UFRecordDataBit -GO - -ALTER TABLE dbo.UFRecordDataDateTime -DROP CONSTRAINT IF EXISTS PK_UFRecordDataDateTime -GO - -ALTER TABLE dbo.UFRecordDataInteger -DROP CONSTRAINT IF EXISTS PK_UFRecordDataInteger -GO - -ALTER TABLE dbo.UFRecordDataLongString -DROP CONSTRAINT IF EXISTS PK_UFRecordDataLongString -GO - --- Reverts addition of relationship between UFRecordFields and UFREcordData* tables. -ALTER TABLE dbo.UFRecordDataBit -DROP CONSTRAINT IF EXISTS FK_UFRecordDataBit_UFRecordFields_Key -GO - -ALTER TABLE dbo.UFRecordDataDateTime -DROP CONSTRAINT IF EXISTS FK_UFRecordDataDateTime_UFRecordFields_Key -GO - -ALTER TABLE dbo.UFRecordDataInteger -DROP CONSTRAINT IF EXISTS FK_UFRecordDataInteger_UFRecordFields_Key -GO - -ALTER TABLE dbo.UFRecordDataLongString -DROP CONSTRAINT IF EXISTS FK_UFRecordDataLongString_UFRecordFields_Key -GO - --- Reverts addition of index on foreign key fields in UFREcordData* tables. -DROP INDEX IF EXISTS IX_UFRecordDataBit_Key ON dbo.UFRecordDataBit -GO - -DROP INDEX IF EXISTS IX_UFRecordDataDateTime_Key ON dbo.UFRecordDataDateTime -GO - -DROP INDEX IF EXISTS IX_UFRecordDataInteger_Key ON dbo.UFRecordDataInteger -GO - -DROP INDEX IF EXISTS IX_UFRecordDataLongString_Key ON dbo.UFRecordDataLongString -GO - --- Reverts addition of primary key to UFUserSecurity -ALTER TABLE dbo.UFUserSecurity -DROP CONSTRAINT IF EXISTS PK_UFUserSecurity -GO - --- Reverts addition of primary key to UFUserFormSecurity -ALTER TABLE dbo.UFUserFormSecurity -DROP CONSTRAINT IF EXISTS PK_UFUserFormSecurity -GO - --- Reverts addition of unique constraint to UFUserFormSecurity across user/form fields. -ALTER TABLE dbo.UFUserFormSecurity -DROP CONSTRAINT IF EXISTS UK_UFUserFormSecurity_User_Form -GO -``` diff --git a/14/umbraco-forms/developer/healthchecks/forms-in-the-database-apply-keys.md b/14/umbraco-forms/developer/healthchecks/forms-in-the-database-apply-keys.md deleted file mode 100644 index 814bf15930d..00000000000 --- a/14/umbraco-forms/developer/healthchecks/forms-in-the-database-apply-keys.md +++ /dev/null @@ -1,86 +0,0 @@ -# Apply keys and indexes for forms in the database - -```sql -/* - Applies recommended primary keys, foreign keys and indexes to Umbraco Forms tables relating to "forms in the database" (i.e. - when configuration key StoreUmbracoFormsInDb = true). - This replicates for SQL Server the migration AddFormKeysAndIndexes. - */ - --- Adds unique constraint to UFForms. -ALTER TABLE dbo.UFForms -ADD CONSTRAINT UK_UFForms_Key UNIQUE NONCLUSTERED -( - [Key] ASC -) WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] -GO - --- Adds unique constraint to UFDataSource. -ALTER TABLE dbo.UFDataSource -ADD CONSTRAINT UK_UFDataSource_Key UNIQUE NONCLUSTERED -( - [Key] ASC -) WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] -GO - --- Adds unique constraint to UFPrevalueSource. -ALTER TABLE dbo.UFPrevalueSource -ADD CONSTRAINT UK_UFPrevalueSource_Key UNIQUE NONCLUSTERED -( - [Key] ASC -) WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] -GO - --- Adds unique constraint to UFWorkflows. -ALTER TABLE dbo.UFWorkflows -ADD CONSTRAINT UK_UFWorkflows_Key UNIQUE NONCLUSTERED -( - [Key] ASC -) WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] -GO - --- Adds index on join field in UFWorkflows. -CREATE NONCLUSTERED INDEX IX_UFWorkflows_FormId ON dbo.UFWorkflows -( - FormId ASC -) WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] -GO -``` - -## Reverting the application of keys and indexes - -```sql -/* - Reverts application of recommended primary keys, foreign keys and indexes to Umbraco Forms tables relating to "forms in the database" (i.e. - when configuration key StoreUmbracoFormsInDb = true). - This reverts for SQL Server the migration AddFormKeysAndIndexes and can be used for rolling that back in testing. - */ - --- Reverts addition of unique constraint to UFForms. -ALTER TABLE dbo.UFForms -DROP CONSTRAINT IF EXISTS UK_UFForms_Key -GO - --- Reverts addition of unique constraint to UFPrevalueSource. -ALTER TABLE dbo.UFDataSource -DROP CONSTRAINT IF EXISTS UK_UFDataSource_Key -GO - --- Reverts addition of unique constraint to UFPrevalueSource. -ALTER TABLE dbo.UFPrevalueSource -DROP CONSTRAINT IF EXISTS UK_UFPrevalueSource_Key -GO - --- Reverts addition of unique constraint to UFWorkflows. -ALTER TABLE dbo.UFWorkflows -DROP CONSTRAINT IF EXISTS UK_UFWorkflows_Key -GO - --- Reverts addition of index on foreign key fields in UFWorkflows. -DROP INDEX IF EXISTS IX_UFWorkflows_FormId ON dbo.UFWorkflows -GO - --- Reverts addition of index on foreign key fields in UFWorkflows. -DROP INDEX IF EXISTS IX_UFWorkflows_FormId ON dbo.UFWorkflows -GO -``` diff --git a/14/umbraco-forms/developer/healthchecks/images/Umb-backoffice.png b/14/umbraco-forms/developer/healthchecks/images/Umb-backoffice.png deleted file mode 100644 index 7c006f92ca1..00000000000 Binary files a/14/umbraco-forms/developer/healthchecks/images/Umb-backoffice.png and /dev/null differ diff --git a/14/umbraco-forms/developer/healthchecks/images/healthcheck-v14.png b/14/umbraco-forms/developer/healthchecks/images/healthcheck-v14.png deleted file mode 100644 index eb16cd812d5..00000000000 Binary files a/14/umbraco-forms/developer/healthchecks/images/healthcheck-v14.png and /dev/null differ diff --git a/14/umbraco-forms/developer/healthchecks/images/healthcheck.png b/14/umbraco-forms/developer/healthchecks/images/healthcheck.png deleted file mode 100644 index c701f83f778..00000000000 Binary files a/14/umbraco-forms/developer/healthchecks/images/healthcheck.png and /dev/null differ diff --git a/14/umbraco-forms/developer/images/assign-sensitive-data-to-user.png b/14/umbraco-forms/developer/images/assign-sensitive-data-to-user.png deleted file mode 100644 index a1cafe90d27..00000000000 Binary files a/14/umbraco-forms/developer/images/assign-sensitive-data-to-user.png and /dev/null differ diff --git a/14/umbraco-forms/developer/images/content-app.png b/14/umbraco-forms/developer/images/content-app.png deleted file mode 100644 index 2ebbfbbf08a..00000000000 Binary files a/14/umbraco-forms/developer/images/content-app.png and /dev/null differ diff --git a/14/umbraco-forms/developer/images/exclude-scripts-v9.png b/14/umbraco-forms/developer/images/exclude-scripts-v9.png deleted file mode 100644 index d592b5e73d6..00000000000 Binary files a/14/umbraco-forms/developer/images/exclude-scripts-v9.png and /dev/null differ diff --git a/14/umbraco-forms/developer/images/exclude-scripts.png b/14/umbraco-forms/developer/images/exclude-scripts.png deleted file mode 100644 index 571bd847008..00000000000 Binary files a/14/umbraco-forms/developer/images/exclude-scripts.png and /dev/null differ diff --git a/14/umbraco-forms/developer/images/form-guid.png b/14/umbraco-forms/developer/images/form-guid.png deleted file mode 100644 index 71a21c7618c..00000000000 Binary files a/14/umbraco-forms/developer/images/form-guid.png and /dev/null differ diff --git a/14/umbraco-forms/developer/images/form-picker-config.png b/14/umbraco-forms/developer/images/form-picker-config.png deleted file mode 100644 index d7c600b894e..00000000000 Binary files a/14/umbraco-forms/developer/images/form-picker-config.png and /dev/null differ diff --git a/14/umbraco-forms/developer/images/form-pickers.png b/14/umbraco-forms/developer/images/form-pickers.png deleted file mode 100644 index 037e25fabe0..00000000000 Binary files a/14/umbraco-forms/developer/images/form-pickers.png and /dev/null differ diff --git a/14/umbraco-forms/developer/images/mark-field-as-sensitive.png b/14/umbraco-forms/developer/images/mark-field-as-sensitive.png deleted file mode 100644 index 06f2496feab..00000000000 Binary files a/14/umbraco-forms/developer/images/mark-field-as-sensitive.png and /dev/null differ diff --git a/14/umbraco-forms/developer/images/select-a-theme.png b/14/umbraco-forms/developer/images/select-a-theme.png deleted file mode 100644 index 985dd572041..00000000000 Binary files a/14/umbraco-forms/developer/images/select-a-theme.png and /dev/null differ diff --git a/14/umbraco-forms/developer/images/sensitive-data-field.png b/14/umbraco-forms/developer/images/sensitive-data-field.png deleted file mode 100644 index 82243d3840d..00000000000 Binary files a/14/umbraco-forms/developer/images/sensitive-data-field.png and /dev/null differ diff --git a/14/umbraco-forms/developer/images/swagger-ui.png b/14/umbraco-forms/developer/images/swagger-ui.png deleted file mode 100644 index 51358f36b64..00000000000 Binary files a/14/umbraco-forms/developer/images/swagger-ui.png and /dev/null differ diff --git a/14/umbraco-forms/developer/images/user-group-permissions.png b/14/umbraco-forms/developer/images/user-group-permissions.png deleted file mode 100644 index 43e7df5cb94..00000000000 Binary files a/14/umbraco-forms/developer/images/user-group-permissions.png and /dev/null differ diff --git a/14/umbraco-forms/developer/images/user-start-folders-v14.png b/14/umbraco-forms/developer/images/user-start-folders-v14.png deleted file mode 100644 index d0df3ca2c23..00000000000 Binary files a/14/umbraco-forms/developer/images/user-start-folders-v14.png and /dev/null differ diff --git a/14/umbraco-forms/developer/images/user-start-folders.png b/14/umbraco-forms/developer/images/user-start-folders.png deleted file mode 100644 index ff01a21c28c..00000000000 Binary files a/14/umbraco-forms/developer/images/user-start-folders.png and /dev/null differ diff --git a/14/umbraco-forms/developer/images/validation-pattern.png b/14/umbraco-forms/developer/images/validation-pattern.png deleted file mode 100644 index e90ec8642dc..00000000000 Binary files a/14/umbraco-forms/developer/images/validation-pattern.png and /dev/null differ diff --git a/14/umbraco-forms/developer/images/wehbook-events-v14.png b/14/umbraco-forms/developer/images/wehbook-events-v14.png deleted file mode 100644 index 5d737e3c0c9..00000000000 Binary files a/14/umbraco-forms/developer/images/wehbook-events-v14.png and /dev/null differ diff --git a/14/umbraco-forms/developer/images/wehbook-events.png b/14/umbraco-forms/developer/images/wehbook-events.png deleted file mode 100644 index c8ad67f92a3..00000000000 Binary files a/14/umbraco-forms/developer/images/wehbook-events.png and /dev/null differ diff --git a/14/umbraco-forms/developer/iprevaluetextfilestorage.md b/14/umbraco-forms/developer/iprevaluetextfilestorage.md deleted file mode 100644 index d25103de140..00000000000 --- a/14/umbraco-forms/developer/iprevaluetextfilestorage.md +++ /dev/null @@ -1,69 +0,0 @@ -# Storing Prevalue Text Files With IPreValueTextFileStorage - -Umbraco Forms contains a built-in `Get value from textfile` [Prevalue Source Type](extending/adding-a-prevaluesourcetype.md) that stores the uploaded text file into the physical file system (by default in `umbraco\Data\UmbracoForms\PreValueTextFiles`). - -You can replace the default implementation by writing your own `IPreValueTextFileStorage` and registering that using e.g. `builder.Services.AddUnique()` (in `Program.cs` or a composer). - -You can also use/inherit from `PreValueTextFileSystemStorage` to change the underlying `IFileSystem` that's used to store the prevalue text files. - -## Move files to Media file system - -You can use the following composer to move the prevalue text files into the media file system. If the media file system is using Azure Blob Storage, this will remove the files from the local physical file system. - -```csharp -using Umbraco.Cms.Core.Composing; -using Umbraco.Cms.Core.IO; -using Umbraco.Cms.Core.Scoping; -using Umbraco.Forms.Core.Data; - -public class PreValueTextFileSystemStorageComposer : IComposer -{ - public void Compose(IUmbracoBuilder builder) - => builder.Services.AddUnique(factory => new PreValueTextFileSystemStorage( - factory.GetRequiredService().FileSystem, - factory.GetRequiredService(), - "PreValueTextFiles")); -} -``` - -You need to manually move the existing files from `umbraco\Data\UmbracoForms\PreValueTextFiles` to your media storage. The final file path/URL will look like `~/media/PreValueTextFiles/{GUID}/{filename.txt}` and be accessible from the browser. - -## Move files to Azure Blob Storage - -First, install [Umbraco.StorageProviders.AzureBlob](https://github.com/umbraco/Umbraco.StorageProviders) and configure the Forms storage container, for example by adding the following to your `appsettings.json`: - -```json -{ - "Umbraco": { - "Storage": { - "AzureBlob": { - "Forms": { - "ConnectionString": "UseDevelopmentStorage=true", - "ContainerName": "sample-container" - } - } - } - } -} -``` - -Next, add the following composer that adds the Forms storage container and stores the prevalue text files into Azure Blob Storage (in `forms/PreValueTextFiles/{GUID}/{filename.txt}`): - -```csharp -using Umbraco.Cms.Core.Composing; -using Umbraco.Cms.Infrastructure.Scoping; -using Umbraco.Forms.Core.Data; -using Umbraco.StorageProviders.AzureBlob.IO; - -public class PreValueTextFileSystemStorageComposer : IComposer -{ - public void Compose(IUmbracoBuilder builder) - => builder.AddAzureBlobFileSystem("Forms", options => options.VirtualPath = "~/forms") - .Services.AddUnique(factory => new PreValueTextFileSystemStorage( - factory.GetRequiredService().GetFileSystem("Forms"), - factory.GetRequiredService(), - "PreValueTextFiles")); -} -``` - -You need to manually move the existing files from `umbraco\Data\UmbracoForms\PreValueTextFiles` to your storage container. If you've disabled public access, the stored files are not accessible from the browser. diff --git a/14/umbraco-forms/developer/localization.md b/14/umbraco-forms/developer/localization.md deleted file mode 100644 index c2cefbd7512..00000000000 --- a/14/umbraco-forms/developer/localization.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -meta.Title: Localization ---- - -# Localization - -The labels, descriptions, and buttons that make up the backoffice screens for Umbraco Forms can be translated into different languages. - -When an editor chooses a language for their account, Umbraco CMS will render appropriate translations. The translations will contain a file for that language and a key for the label in question. If either of these can't be found, the label will be displayed in English (US). - -## Language Files - -Umbraco Forms ships with translations for the following languages: - - - Czech (`cs-cz.js`) - - Danish (`da-dk.js`) - - Spanish (`es-es.js`) - - French (`fr-fr.js`) - - Italian (`it-it.js`) - - Polish (`pl-pl.js`) - - UK English (`en-gb.js`) - - US English (`en-us.js`) - - Dutch (`nl-nl.js`) - -If the language you require does not exist, it's possible to create your own by duplicating the default `en-us.js` file. You can then save it with the appropriate culture code for the language you need and replace the English text with the translated version. - -As of Forms 10, the file no longer exists on disk and is shipped as part of the `Umbraco.Forms.StaticAssets` NuGet package. You can open this package, either locally using [Nuget Package Explorer](https://apps.microsoft.com/store/detail/nuget-package-explorer/9WZDNCRDMDM3?hl=en-gb&gl=gb&rtc=1), or [online](https://www.nuget.org/packages/Umbraco.Forms.StaticAssets/) by clicking the "Open in NuGet Package Explorer" link. You'll find the file at `staticwebassets/en-us.js`. - -Once translated, the new file should be saved somewhere in the `App_Plugins` folder for example `App_Plugins/UmbracoFormsLocalization/`. The final step is to register the localization file. This can be done by creating a `umbraco-package.json` like so: - -```json -{ - "$schema": "../../umbraco-package-schema.json", - "name": "Umbraco.Forms.Extensions", - "extensions": [ - { - "type": "localization", - "alias": "UmbracoForms.Localize.DeDE", - "name": " German (Germany)", - "meta": { - "culture": "de-de" - }, - "js": "/App_Plugins/UmbracoFormsLocalization/de-de.js" - } - ] -} -``` diff --git a/14/umbraco-forms/developer/magic-strings.md b/14/umbraco-forms/developer/magic-strings.md deleted file mode 100644 index 5e8d9da683f..00000000000 --- a/14/umbraco-forms/developer/magic-strings.md +++ /dev/null @@ -1,123 +0,0 @@ -# Magic Strings - -Umbraco Forms has some magic strings that enable you to render values from various sources, such as session, cookies and Umbraco page fields. - -## Where can I use magic strings? - -Magic strings can be used in form fields as a label, description or default value. As an example they can be used in default values in hidden fields - normally in the form of referral codes from a session, cookie or request item. - -These values can also be used for properties and settings in workflows. This means you can use name and email fields from a form to create a personal 'Thank you' email. - -## Sources of magic string values - -### Request - -`[@SomeRequestItem]` this allows you to display an item from the current `HttpContext.Request` with the key of 'SomeRequestItem'. - -Some examples of variables that are normally available in `HttpContext.Request`: - -* `[@Url]`: Insert the current URL -* `[@Http_Referer]`: The previous visited URL (if available) -* `[@Remote_Addr]`: The IP address of the visitor (stored by default by Umbraco) -* `[@Http_User_Agent]`: The browser of the visitor - -The variables are not case-sensitive. - -You can use it for any available query string variable in the URL as well. If your URL has the query string `?email=foobar@umbraco.com`, you can get the value of the query string into your field by using `[@email]`. - -### Dictionary Items - -For multi-lingual websites, rather than hard-coding labels like form field captions, a dictionary key can be entered as, for example, `#MyKey`. When the form is rendered, the placeholder will be replaced by the value of the dictionary item identified by the key, according to the current language. - -In most cases, the field must contain only the magic string for the replacement to be carried out. This makes sense for translated values, as you will want the whole phrase replaced when, for example, using one for a field's placeholder. - -We also translate dictionary keys found within the rich text field, which will be contained within HTML tags. Here we look for dictionary keys making up the full inner text of a tag. So for example, `

#myKey

` would be translated, but `

Lorem ipsum #myKey dolor sit amet.

` would not. - -### Session & Cookies - -`[%SomeSessionOrCookieItem]` this allows you to display an item from the current `HttpContext.Session` with the key of 'SomeSessionOrCookieItem'. The session key can only contain alphanumeric chars and you cannot use dots for example. `[%Member.Firstname]` cannot be used, but `[%MemberFirstname]` can be used. You would have to fill these session keys yourself. - -If the item cannot be found in the collection of session keys, it will then try to find the item from the `HttpContext.Cookies` collection with the same key. - -### Umbraco Page field - -`[#myUmbracoField]` this allows you to insert a property of that page and is based on the alias of the field. If your page has a property with the alias 'title', you can use `[#title]` in your form. - -Some extra variables are: - -* `[#pageName]`: The nodename of the current page -* `[#pageID]`: The node ID of the current page - -### Recursive Umbraco Page field - -`[$myRecursiveItem]` this allows you to parse the Umbraco Document Type property myRecursiveItem. So if the current page does not contain a value for this then it will request it from the parent up until the root or until it finds a value. - -### Additional data - -When rendering a form, additional data can be provided in the form of a dictionary. As well as being associated with the created record and available within workflows, they can be used for "magic string" replacements. - -They are accessed using this syntax: `[+additionalDataKey]`. - -### Umbraco Form field - -`{myAliasForFormField}` this allows you to display the entered value for that specific field from the form submission. Used in workflows to send an automated email back to the customer based on the email address submitted in the form. The value here needs to be the alias of the field, and not the name of the field. - -Some extra variables are: - -* `{record.id}`: The ID of the current record - this is only accessible on workflows triggered "on approve" or "on reject" rather than "on submit" -* `{record.updated}`: The updated date/time of the current record -* `{record.created}`: The created date/time of the current record -* `{record.umbracopageid}`: The Umbraco Page ID the form was submitted on -* `{record.uniqueid}`: The unique ID of the current record -* `{record.ip}`: The IP address that was used when the form was submitted -* `{record.memberkey}`: The member key that was used when the form was submitted - -### Member properties from a form submission - -`{member.FOO}` with the prefix of member, the same syntax will allow you to retrieve information about the submission if it was submitted by a logged-in member. - -## Formatting magic strings - -Using a magic string such as in the examples above will output the values exactly as read from the source. It's possible to apply a format string to customize the output. - -The syntax follows that of AngularJS filters, i.e. `[ | : : ]`. - -For example, to truncate a string value read from an Umbraco page field with alias `title`, you would use: - -``` -[#title | truncate: 10] -``` - -Umbraco Forms ships with the following filters: - -| Filter | Function | Arguments | Example | -| ------------------------------------------------ | ----------------------- | -------------------- | ---------------------------------------------------- | -| Bound a number | `bound` | min and max bound | `[#field \| bound: 1: 10]` | -| Convert string to lower case | `lower` | | `[#field \| lower]` | -| Convert string to upper case | `upper` | | `[#field \| upper]` | -| Format a number | `number` | format string | `[#field \| number: #0.##%]` | -| Format a number as a currency | `currency` | | `[#field \| currency]` | -| Format a date | `date` | format string | `[#field \| date: dd-MM-yyyy HH:mm]` | -| HTML encode a string | `html` | | `[#field \| html]` | -| Truncate a string | `truncate` | number of characters | `[#field \| truncate: 10]` | - -The format strings used for formatting dates and numbers are the standard or custom .NET [date](https://docs.microsoft.com/en-us/dotnet/standard/base-types/standard-date-and-time-format-strings) and [numeric](https://docs.microsoft.com/en-us/dotnet/standard/base-types/standard-numeric-format-strings) format strings respectively. - -Further magic string format functions can be [created in code](extending/adding-a-magic-string-format-function.md) for use in forms. - -## How can I parse these values elsewhere in my C# code or Razor Views? - -A service implemented by the `IPlaceholderParsingService` interface is available for use in custom code or views. It's found in the `Umbraco.Forms.Core.Services` namespace. - -In a controller you can inject it via the constructor and it can also be injected into views via: - -```csharp -@using Umbraco.Forms.Core.Services; -@inject IPlaceholderParsingService PlaceholderParsingService -``` - -The interface implements a single method, `ParsePlaceHolders`, that can be used for parsing magic strings. There are a few overloads available for use depending on the context. - -If parameters for the `Record` or `Form` are omitted, magic strings relating to these objects will be removed. - -There is also a public extension method `ParsePlaceHolders()` extending the `string` object in the `Umbraco.Forms.Core.Extensions` namespace, again available with some overloads allowing the provision of a `Form` or `Record` object if available. diff --git a/14/umbraco-forms/developer/prepping-frontend.md b/14/umbraco-forms/developer/prepping-frontend.md deleted file mode 100644 index f0b644751f5..00000000000 --- a/14/umbraco-forms/developer/prepping-frontend.md +++ /dev/null @@ -1,82 +0,0 @@ -# Preparing your Frontend - -For Umbraco Forms to work correctly, you need to include some client dependencies. - -## Client-Side Validation - -Umbraco Forms ships with client-side form validation features provided by the [ASP.NET Client Validation library](https://github.com/haacked/aspnet-client-validation). - -You can use the following Razor helper to output script tags containing the dependencies. To access this method you will need a reference to `Umbraco.Forms.Web`: - -```csharp -@using Umbraco.Forms.Web - - @Html.RenderUmbracoFormDependencies(Url) - -``` - -`Url` is a parameter passed into the method. It’s defined as a property on the base view model for an Umbraco template, so it will be automatically available in your Razor views. - -Alternatively, you can add the dependencies to the body tag: - -```csharp -@using Umbraco.Forms.Web -... - - - @Html.RenderUmbracoFormDependencies(Url) - -``` - -All dependencies originate from your Umbraco Forms installation, which means that no external references are needed. - -If you want to modify the rendering of the scripts, you can provide a object parameter named `htmlAttributes`. The contents of the object will be written out as HTML attributes on the script tags. - -You can use this to apply `async` or `defer` attributes. For example: - -```csharp -@Html.RenderUmbracoFormDependencies(Url, new { @async = "async" }) -``` - -If using `async`, please make sure to [disable the Forms client-side validation framework check](../developer/configuration/README.md#disableclientsidevalidationdependencycheck). This is necessary as it's not possible to guarantee that the asynchronous script will load in time to be recognized by the check. This can then cause a false positive warning. - -## Validation Using jQuery - -If you want to use jQuery as your validation framework for Umbraco Forms, you can manually add the following client dependencies: - -- `jQuery` (JavaScript library) -- `jQuery validate` (jQuery plugin that provides client-side Form validation) -- `jQuery validate unobtrusive` (Add-on to jQuery Validation that provides unobtrusive validation via data-* attributes) - -You should remove any calls to `@Html.RenderUmbracoFormDependencies(Url)`. - -The easiest way to add the dependencies is to fetch them from a [CDN](https://en.wikipedia.org/wiki/Content_delivery_network). There are various CDN services you can use: - -- For example: [Microsoft CDN](https://docs.microsoft.com/en-us/aspnet/ajax/cdn/overview). -- Other CDN services you might want to look at are https://www.jsdelivr.com/ and https://cdnjs.com/about, which may offer better performance and more reliable service. - -To add the three client dependencies, see the examples below: - -**Example within `head` tags.** - -```html - - - - - -``` - -**Example within `body` tags.** - -When adding the script to the bottom of the page, you will also need to render the scripts. For more information, see [Rendering Forms Scripts](rendering-scripts.md) article. - -```html - - - - - - - -``` diff --git a/14/umbraco-forms/developer/property-editors.md b/14/umbraco-forms/developer/property-editors.md deleted file mode 100644 index 5789e0b4a17..00000000000 --- a/14/umbraco-forms/developer/property-editors.md +++ /dev/null @@ -1,39 +0,0 @@ -# Property Editors - -When forms are created, editors will want to add them to pages in Umbraco. To do this they need a Document Type with a property that uses a Data Type based on a Form Picker property editor. - -Umbraco Forms provides three variations of a form picker. - -

Form Pickers

- -Most commonly used is **Form Picker (single)**. This will allow the editor to select a single form for display on page. - -Rarely but feasibly, you will have a requirement to present multiple forms on a page. Should this be appropriate, you can use **Form Picker (multiple)**. - -{% hint style="info" %} -Internally this is used for presenting the list of "Allowed forms" you can select when setting up a form picker datatype. -{% endhint %} - -Finally you can provide further flexibility for the editor to select not only a form, but also the theme and redirect as well. For this you will use the **Form Details Picker**. - -## Configuring the Data Type - -Each property editor allows you to restrict the forms that can be chosen with the Data Type. You do this by setting either or both of the list of "Allowed folders" or "Allowed forms". - -

Form Picker DataType Configuration

- -The "Form Details Picker" also allows you to select whether a theme or redirect selection is available. - -## Property Value Conversion - -The type of a property based on the Form Picker presented in a Razor class library is as follows: - -| Option | Description | -| -------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | -| **Form Picker (single)** | Single GUID representing the form's identifier. | -| **Form Picker (multiple)** | Collection of GUIDs representing the form identifiers. | -| **Form Details Picker** | Instance of the `Umbraco.Forms.Core.PropertyEditors.Models.FormDetails` object, which has properties for the form, theme and redirect. | - -## Content Delivery API Expansion - -Each reference to a form supports expansion via the Umbraco Content Delivery API, as described in the [Working with the CMS Content Delivery API](./ajaxforms.md#working-with-the-cms-content-delivery-api) article. diff --git a/14/umbraco-forms/developer/rendering-forms.md b/14/umbraco-forms/developer/rendering-forms.md deleted file mode 100644 index 9e5b31ff10f..00000000000 --- a/14/umbraco-forms/developer/rendering-forms.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -description: Learn the different ways of rendering a form on your website when using Umbraco Forms. ---- - -# Rendering Forms - -There are two options available for rendering a form. - -## Rendering Using a View Component - -To display a form in your view, you can make a call to a view component. You can use a forms GUID directly or add a form dynamically by referencing a form selected via a Forms Picker. - -When selecting a theme, it can be added directly as a string or dynamically by referencing a theme picked via a Theme Picker. - -{% tabs %} - -{% tab title="Dynamic" %} - -```csharp -@await Component.InvokeAsync("RenderForm", new { formId = @Model.Form, - theme = @Model.Theme, - includeScripts = false }) -``` - -This example uses a Forms Picker with `form` as alias, and a Theme Picker with `theme` as alias. - -{% endtab %} - -{% tab title="Static" %} - -```csharp -@await Component.InvokeAsync("RenderForm", new { formId = Guid.Parse("
"), - theme = "default", - includeScripts = false }) -``` - -This example hard-codes the GUID of a form and the name of the theme. - -{% endtab %} - -{% endtabs %} - -Six parameters can be provided: - -- `formId` is the GUID of a form. -- `theme` is the name of a theme. If not provided, the default theme is used (see [Themes](./themes.md)). -- `includeScripts` indicates whether scripts should be rendered with the form (see [Rendering Scripts](./rendering-scripts.md). -- `recordId` is an optional existing record GUID, used if editing records via the website is [enabled in configuration](../developer/configuration/README.md#alloweditableformsubmissions) -- `redirectToPageId` is an optional GUID for a content page that, if provided, is redirected to once the form has been submitted. It will be used in preference to post-submission behavior defined on the form itself. -- `additionalData` is an optional dictionary of string values. When provided it will be used as a source for ["magic string" replacements](./magic-strings.md). The data will be associated with the created record and made available for custom logic or update within workflows. - -The following example shows how the `additionalData` parameter is used: - -{% code wrap="true" %} - -```csharp -var additionalData = new Dictionary { { "foo", "bar" }, { "buzz", "baz" } }; -@await Component.InvokeAsync("RenderForm", new { formId = @Model.Form, theme = @Model.Theme, includeScripts = false, additionalData }) -``` - -{% endcode %} - -## Rendering Using a Tag Helper - -If you prefer a tag helper syntax, you can use one that ships with Umbraco Forms. - -Firstly, in your `_ViewImports.cshtml` file, add a reference to the Umbraco Forms tag helpers with: - -```cshtml -@addTagHelper *, Umbraco.Forms.Web -``` - -Then in your view you can use: - -```csharp -@if (Model.Form.HasValue) -{ - var additionalData = new Dictionary { { "foo", "bar" }, { "buzz", "baz" } }; - -} -``` diff --git a/14/umbraco-forms/developer/rendering-scripts.md b/14/umbraco-forms/developer/rendering-scripts.md deleted file mode 100644 index fc99f1dcfdb..00000000000 --- a/14/umbraco-forms/developer/rendering-scripts.md +++ /dev/null @@ -1,74 +0,0 @@ -# Rendering Forms Scripts - -Forms output some JavaScript which is by default rendered right below the markup. - -In many cases, you might prefer rendering your scripts at the bottom of the page. For example, before the closing `` tag. This generally improves site performance. - -In order to render your scripts where you want, you need to add a snippet to your template. Make sure you add it below your scripts, right before the closing `` tag. - -By default, Forms uses `TempData` for tracking the forms rendered on a page. The stored values are used when rendering the form scripts and associated data. - -The following snippet should be used. - -```csharp -@using Umbraco.Forms.Web.Extensions; - -@if (TempData.Get("UmbracoForms") is Guid[] formIds) -{ - foreach (var formId in formIds) - { - @await Component.InvokeAsync("RenderFormScripts", new { formId, theme = "default" }) - } - - TempData.Remove("UmbracoForms"); -} -``` - -If you have changed the configuration value `TrackRenderedFormsStorageMethod` to use `HttpContext.Items`, the snippet is: - -```csharp -@if (Context.Items.TryGetValue("UmbracoForms", out object? formIdsObject) && formIdsObject is IEnumerable formIds) -{ - foreach (var formId in formIds) - { - @await Component.InvokeAsync("RenderFormScripts", new { formId, theme = "default" }) - } -} -``` - -Read more about this configuration option in the [configuration ](./configuration/README.md#TrackRenderedFormsStorageMethod) article. - -If you prefer to use a tag helper, that's an option too. - -Firstly, in your `_ViewImports.cshtml` file, ensure you have a reference to the Umbraco Forms tag helpers with: - -```cshtml -@addTagHelper *, Umbraco.Forms.Web -``` - -Then instead of reading from `TempData` and invoking the view component directly, you can use: - -```cshtml - -``` - -This will use the appropriate storage method that you have configured. - -## Enabling `ExcludeScripts` - -If you do not want to render the associated scripts with a Form, you need to explicitly say so. You need to make sure `ExcludeScripts` is checked/enabled, whether you are inserting your Form using a macro or adding it directly in your template. - -To enable `ExcludeScripts`: - -* Using the **Insert Form with Theme** macro: - - ![Exclude scripts](../../../10/umbraco-forms/developer/images/exclude-scripts-v9.png) -* While inserting Forms **directly** in your template: - - ```csharp - @await Umbraco.RenderMacroAsync("renderUmbracoForm", new {FormGuid="6c3f053c-1774-43fa-ad95-710a01d9cd12", FormTheme="bootstrap3-horizontal", ExcludeScripts="1"}) - ``` - -{% hint style="info" %} -`ExcludeScripts = "1"` prevents the associated scripts from being rendered. Any other value, an empty value, or if the parameter is excluded, will render the scripts on the Form. -{% endhint %} diff --git a/14/umbraco-forms/developer/security.md b/14/umbraco-forms/developer/security.md deleted file mode 100644 index df6ea219a39..00000000000 --- a/14/umbraco-forms/developer/security.md +++ /dev/null @@ -1,116 +0,0 @@ ---- -description: How to secure access to Umbraco Forms data and functionality. ---- - -# Security - -Umbraco Forms has a backoffice security model integrated with Umbraco users. Details are managed in the _Forms_ section of the backoffice, within a tree named _Security_. - -## User-based permissions - -Within the _Forms_ > _Security_ tree, each user with a backoffice account is listed. Clicking on a user allows each functional permission to be set: - -* Manage Forms - user can create and edit form definitions -* View Entries - user can view the submitted entries -* Edit Entries - user can edit the submitted entries -* Delete entries - user can delete the submitted entries -* Manage Workflows - user can create and edit workflow items -* Manage Datasources - user can create and edit datasource definitions -* Manage Prevalue Sources - user can create and edit prevalue source definitions - -For further control, each form is listed and the user can be granted or denied access to each as appropriate. - -As new forms are created, users will automatically be granted access to them, unless the configuration setting `DefaultUserAccessToNewForms` has been set to a value of `Deny`. - -## Start Folders - -When form definitions are configured for storage in the database, it allows for the creation of folders to group forms within. It's also possible to define one or more start folders for a user. This is done in order to limit their access to a subset of the forms available. - -If no start folders are selected, the user will be able to access all forms in the backoffice according to their permissions. - -If a single start folder is selected, that will act as the root of the tree view of forms. The user will have access to all folders and forms below that selected folder. - -If more than one start folder is selected, they will appear underneath the root of the tree view of forms. The user will have access to only those folders and their descendant folders and forms. - -![Start folders](images/user-start-folders-v14.png) - -## User group based permissions - -A new model was introduced allowing for the management of permissions at the level of user groups. Particularly for installations with a large number of users, we expect this to be a more useful setup and require less ongoing administration. - -When user groups are involved in permissions, access to a particular resource or feature is determined by the following: - -* If the user has a specific user permission set, it is used in preference to anything set on the user groups they are a part of. -* If the user doesn't have a specific user permission set, they are granted access if at least one of the user groups they are part of has access. - -To enable the feature, it's necessary to update the `ManageSecurityWithUserGroups` configuration setting to `true`. - -With that in place the _Form Security_ tree divides into three sub-trees: - -* Under _Group Permissions_, each user group is listed and the same settings as described above for individual users can be set here. -* Under _User Permissions_, each user that has a specific user permission record is listed and can be managed. Records for users can be created or deleted via the tree's action menu. - -As new forms are created, user groups with aliases listed in the `GrantAccessToNewFormsForUserGroups` configuration setting will be automatically given access. For example, with a value of `admin, editor`, the built-in Administrators and Editors groups would have access. - -### Start folders for user groups - -Start folders are enabled for User Groups. They work in a similar way as the group based permissions described above: - -* If the user has a specific user permission set, it is used in preference to anything set on the user groups they are a part of. - * This means if the user has no start folders defined and the groups they are part of do, they will have access to the root of the Forms tree and be able to access all folders and Forms. -* If the user doesn't have a specific user permission set, they are granted access to all the unique folders the groups they are part of have access to. - * If they are part of any group that has access to the forms section, permission to manage forms and no start folders defined, they will have access to the root of the Forms tree and be able to access all folders and Forms. - -### Migrating to user group-based permissions - -In introducing the user group based permissions, we've taken care to ensure a migration path. This is available for those existing installations running on older versions of Umbraco Forms. In that situation, we'd recommend the following approach. - -* Upgrade to Umbraco 9.3. -* At this stage nothing will have changed in terms of the permissions model in use. -* Set the `ManageSecurityWithUserGroups` configuration value to `true` and the `GrantAccessToNewFormsForUserGroups` as appropriate for your setup. -* Via the _Users > Form Security_ section, set the required permissions on each user group. -* Again at this point nothing will have changed with regard the effective permissions for each user, as they will currently all have an existing user permission record. -* Via _Users > Form Security > User permissions_, delete the permission records for each user. -* The effective permissions for each user will now be derived from their user groups. -* If you have any exceptions - where a particular user needs a particular combination of permissions that you can't or don't want to provide via the user groups - it's always possible to re-create a user permission record that will take precedence over the group based permissions. - -![User group permissions](../../../10/umbraco-forms/developer/images/user-group-permissions.png) - -## Handling Sensitive Data in Umbraco Forms - -Marking fields and properties as sensitive will hide the data in those fields for backoffice users that are not privy to the data. Built-in features are available to help you secure sensitive information. For more information, see the [Sensitive data](https://docs.umbraco.com/umbraco-cms/reference/security/sensitive-data-on-members) article. - -The following sections covers how to grant or deny access to sensitive data for specific users and how to mark form questions as sensitive. - -### Assigning Users to the Sensitive Data Group - -To allow users to view and handle sensitive data in Umbraco Forms, you must assign them to the _Sensitive Data_ user group: - -1. Navigate to the **Users** section in the Umbraco Backoffice. -2. Select the user you want to grant access to. -3. Click **Choose** in the Groups field under the **Assign access** section. -4. Select **Sensitive Data** from the list of User Groups. -5. Click **Submit**. -6. Click **Save**. - -![Assigning Users to the Sensitive Data Group](images/assign-sensitive-data-to-user.png) - -### Marking Questions in Forms as Sensitive - -Once the users are set up with the appropriate permissions, the next step is to identify which form fields should be marked as sensitive. - -Marking a field as sensitive ensures that only authorized users in the Sensitive Data user group can access data from these fields. - -To mark questions as sensitive, follow these steps: - -1. Navigate to the **Forms** section in the Umbraco Backoffice. -2. Open the form you wish to configure (for example: Contact Form). -3. Click on the cogwheel icon next to the form field you want to secure. -4. Enable the **Sensitive data** setting for the field. - -![Mark Question as Sensitive](images/mark-field-as-sensitive.png) - -5. Click **Submit**. -6. Click **Save**. - -![Sensitive Data on Field](images/sensitive-data-field.png) diff --git a/14/umbraco-forms/developer/themes.md b/14/umbraco-forms/developer/themes.md deleted file mode 100644 index 5255d03f87e..00000000000 --- a/14/umbraco-forms/developer/themes.md +++ /dev/null @@ -1,198 +0,0 @@ ---- -description: Documentation on how to apply custom themes to Umbraco Forms ---- - -# Themes - -Umbraco Forms supports Themes, allowing forms to be customized in a much simpler manner. - -## Creating a Theme - -To create a theme, you need to create a folder at `/Views/Partials/Forms/Themes/`. The name of the folder is the name of theme that will be visible in the backoffice when choosing it. - -Copy the explicit files you wish to override in your theme, it may be a single file or all files from the `default` theme folder. Make the necessary changes you desire to CSS class names, markup etc. - -### Obtaining the Default Theme Files - -For Umbraco 9 and previous, it's straightforward to copy the files you need from the default theme folder. We highly recommend that you never customize any files found in the `default` themes folder. There is a risk that any customizations to these files will be lost with any future upgrades you do to Umbraco Forms. Umbraco 10+ distributes these files as part of a Razor Class Library, so you won't find them on disk. Instead you should download the appropriate zip file for your Forms version and extract the ones you need. - -You can obtain the latest version of the Forms default theme from the following links: - -* [14.0.0](./files/umbraco-forms-default-theme-14.0.0.zip) -* [14.0.1](./files/umbraco-forms-default-theme-14.0.1.zip) -* [14.1.0](./files/umbraco-forms-default-theme-14.1.0.zip) -* [14.1.4](./files/umbraco-forms-default-theme-14.1.4.zip) -* [14.2.0](./files/umbraco-forms-default-theme-14.2.0.zip) -* [14.2.4](./files/umbraco-forms-default-theme-14.2.4.zip) - -You should use the theme available for the highest version that's less or equal to the version of Forms you have installed. For example, when using Umbraco Forms 14.1.2, and no file for that version is available use version 14.1.0 instead. - -### Amending Theme Files - -{% hint style="info" %} -Umbraco Forms conditional JavaScript logic depends on some CSS classes currently and it is advised that you add any additional classes you require but **do not remove those already being set**. -{% endhint %} - -If adding or amending client-side scripts, you need to copy the `Script.cshtml` file from the `default` themes folder. In your copy, amend the `.js` references to reference your own script files. - -### Shipping Themes in a Razor Class Library - -Umbraco Forms provides it's built-in themes as part of a Razor Class Library for ease of distribution. This can be useful for custom themes, particularly those used in multiple solutions or released as an Umbraco package. - -From Forms 14.2 it is possible to do this for custom themes. - -1. Create a new Razor Class Library project to hold the theme. -2. Create the necessary Partial Views for your theme within `Views\Partials\Forms\Themes\`. -3. Provide the names of the files in your theme via an implementation of `ITheme`. - * For example, if only overriding a single file, your class would look like the code snippet below: - -```csharp -using Umbraco.Forms.Core.Interfaces; - -public class MyCustomTheme : ITheme -{ - private const string FilePathFormat = "{0}/{1}/{2}.cshtml"; - - public virtual string Name => "my-custom-theme"; - - public virtual IEnumerable Files => - [ - string.Format(FilePathFormat, Core.Constants.System.ThemesPath, Name, "FieldTypes/FieldType.Textfield"), - ]; -} -``` - -4. Register the themes you want to use via a composer: - -```csharp -public class MyComposer : IComposer -{ - public void Compose(IUmbracoBuilder builder) - { - builder.Themes() - .Add(); - } -} -``` - -Your theme will now be available in the Theme Picker and the partial view files will be used when rendering forms. - -#### Email Templates - -Email templates provided for the send email workflow can be provided in a Razor Class Library similar to the Themes files. - -The partial view will be created in `Views\Partials\Forms\Emails`. - -It's made available via an implementation of `IEmailTemplate`: - -```csharp -using Umbraco.Forms.Core.Interfaces; - -public class MyCustomEmailTemplate : IEmailTemplate -{ - public virtual string FileName => "My-Custom-Email-Template.cshtml"; -} -``` - -And registered with: - -```csharp -public class MyComposer : IComposer -{ - public void Compose(IUmbracoBuilder builder) - { - builder.EmailTemplates() - .Add(); - } -} -``` - -##### Removing the Default Email Template - -If providing custom email templates, you may want to remove the one provided with Forms. You can do that via the same `EmailTemplates` collection. - -```csharp -public class MyComposer : IComposer -{ - public void Compose(IUmbracoBuilder builder) - { - builder.EmailTemplates() - .Exclude(); - } -} -``` - -## Using a Theme - -When rendering a form in a view file, you can specify which theme to use with the form. - -Learn more about how to render a form with a theme in the [Rendering Forms](./rendering-forms.md) article. - -## Theme Fallbacks - -When using a theme, Umbraco Forms will try to use a view from the theme folder, but then fallback to the same view in the default theme folder if it can't be found. This allows you to create a theme by only modifying the files necessary to make your customizations. - -Files which can be overridden: - -* Render.cshtml (overrides the entire form - usually not needed) -* Form.cshtml (overrides the generation of the fields on the current page) -* Script.cshtml (overrides the way files are included with the form) -* /Fieldtypes/FieldType.\*.cshtml (overrides a specific view for a field) - -## Helper Methods - -### SetFormThemeCssFile - -Sets the primary form theme stylesheet path. This overrides an already assigned stylesheet and will be rendered out when inserting the form into the page - -```csharp -Html.SetFormThemeCssFile(Model, "~/App_Plugins/UmbracoForms/Assets/Themes/Default/style.css") -``` - -### AddFormThemeScriptFile - -Add a JavaScript file path to include on form render - -```csharp -Html.AddFormThemeScriptFile("~/App_Plugins/UmbracoForms/Assets/themes/default/umbracoforms.js"); -``` - -### SetFormFieldClass - -Adds a class to the form field HTML element of a given type. If no type is given, it will add the class to all fields - -```csharp -// Applies the CSS class 'form-control' to all fields that GetFormFieldClass uses in FieldType views -@Html.SetFormFieldClass("form-control") - -// Applies the CSS class 'some-other-class' for the FieldType of the name 'Password' -@Html.SetFormFieldClass("some-other-class", "Password") -``` - -### GetFormFieldClass - -Retrieves all classes for a given field type, used when rendering form fieldtype partial views - -```csharp -class="@Html.GetFormFieldClass(Model.FieldTypeName)" -``` - -### SetFormFieldWrapperClass - -Adds a class to the div element wrapping around form fields of a given type. If no type is given, it will add the class to all fields - -```csharp -// Applies the CSS class 'form-group' around all fields, labels & help texts -@Html.SetFormFieldWrapperClass("form-group") - -// Applies the CSS class 'some-other-class' for the FieldType of the name 'Password' -@Html.SetFormFieldWrapperClass("some-other-class", "Password") -``` - -### GetFormFieldWrapperClass - -Retrieves all wrapper classes for a given field type, used when rendering form fields. This class wraps both label, help-text and the field itself in the default view - -```csharp -class="@Html.GetFormFieldWrapperClass(f.FieldTypeName)" -``` diff --git a/14/umbraco-forms/developer/webhooks.md b/14/umbraco-forms/developer/webhooks.md deleted file mode 100644 index 790d2d77a8d..00000000000 --- a/14/umbraco-forms/developer/webhooks.md +++ /dev/null @@ -1,24 +0,0 @@ -# Webhooks - -Umbraco Forms will register events for workflow operations that you can use with [Umbraco webhooks](https://docs.umbraco.com/umbraco-cms/reference/webhooks). - -Workflows are operations that you can associate with form submission, approval, or rejection actions. You can use these where you need to notify external systems of the success or failure of a workflow. - -On the Umbraco **Settings** > **Advanced** > **Webhooks** dashboard, you can configure webhooks to respond to workflows. - -![Webhook events](images/wehbook-events-v14.png) - -You can amend the registration of workflow events in code. - -To remove the webhooks that are added by default you can use a composer as follows: - -```csharp -using Umbraco.Cms.Core.Composing; -using Umbraco.Forms.Core.Extensions; - -internal sealed class TestComposer : IComposer -{ - public void Compose(IUmbracoBuilder builder) - => builder.WebhookEvents().AddForms(formsBuilder => formsBuilder.RemoveDefault()); -} -``` \ No newline at end of file diff --git a/14/umbraco-forms/developer/working-with-data.md b/14/umbraco-forms/developer/working-with-data.md deleted file mode 100644 index eb4ef07555a..00000000000 --- a/14/umbraco-forms/developer/working-with-data.md +++ /dev/null @@ -1,112 +0,0 @@ ---- -description: "Developer documentation on working with Forms record data." ---- - -# Working With Record Data - -Umbraco Forms includes some helper methods that return records of a given Form, which can be used to output records in your templates using razor. - -## Available Methods - -The methods can be found by injecting the `Umbraco.Forms.Core.Services.IRecordReaderService` interface. For performance reasons, all these methods are paged. - -### GetApprovedRecordsFromPage - -```csharp -PagedResult GetApprovedRecordsFromPage(int pageId, int pageNumber, int pageSize) -``` - -Returns all records with the state set to approved from all Forms on the Umbraco page with the id = `pageId` . - -### GetApprovedRecordsFromFormOnPage - -```csharp -PagedResult GetApprovedRecordsFromFormOnPage(int pageId, Guid formId, int pageNumber, int pageSize) -``` - -Returns all records with the state set to approved from the Form with the id = `formId` on the Umbraco page with the id = `pageId` as a `PagedResult`. - -### GetApprovedRecordsFromForm - -```csharp -PagedResult GetApprovedRecordsFromForm(Guid formId, int pageNumber, int pageSize) -``` - -Returns all records with the state set to approved from the Form with the ID = `formId` as a `PagedResult`. - -### GetRecordsFromPage - -```csharp -PagedResult GetRecordsFromPage(int pageId, int pageNumber, int pageSize) -``` - -Returns all records from all Forms on the Umbraco page with the id = `pageId` as a `PagedResult`. - -### GetRecordsFromFormOnPage - -```csharp -PagedResult GetRecordsFromFormOnPage(int pageId, Guid formId, int pageNumber, int pageSize) -``` - -Returns all records from the Form with the id = `formId` on the Umbraco page with the id = `pageId` as a `PagedResult`. - -### GetRecordsFromForm - -```csharp -PagedResult GetRecordsFromForm(Guid formId, int pageNumber, int pageSize) -``` - -Returns all records from the Form with the ID = formId as a `PagedResult`. - -## The returned objects - -All of these methods will return an object of type `PagedResult` so you can iterate through the `Record` objects. - -The properties available on a `Record` are: - -```csharp -int Id -FormState State -DateTime Created -DateTime Updated -Guid Form -string IP -int UmbracoPageId -string MemberKey -Guid UniqueId -Dictionary RecordFields -``` - -In order to access custom Form fields, these are available in the `RecordFields` property. Furthermore there exists an extension method named `ValueAsString` on `Record` in `Umbraco.Forms.Core.Extensions`, such that you can get the value as string given the alias of the field. - -This extension method handle multi value fields by comma separating the values. E.g. "A, B, C" - -## Sample razor script - -Sample script that is outputting comments using a Form created with the default comment Form template. - -```csharp -@using Umbraco.Core; -@using Umbraco.Cms.Core.Composing; -@using Umbraco.Forms.Core.Extensions; -@inject IRecordReaderService _recordReaderService; - -
    - @foreach (var record in _recordReaderService.GetApprovedRecordsFromPage(Model.Id, 1, 10).Items) - { -
  • - @record.Created.ToString("dd MMMM yyy") - @if(string.IsNullOrEmpty(record.ValueAsString("email"))){ - @record.ValueAsString("name") - } - else{ - - @record.ValueAsString("name") - - } - said -

    @record.ValueAsString("comment")

    -
    • - } -
-``` diff --git a/14/umbraco-forms/editor/attaching-workflows/README.md b/14/umbraco-forms/editor/attaching-workflows/README.md deleted file mode 100644 index 2885acb1e55..00000000000 --- a/14/umbraco-forms/editor/attaching-workflows/README.md +++ /dev/null @@ -1,83 +0,0 @@ -# Attaching Workflows - -In this article, you can learn how to add extra functionality to your Form by attaching **workflows**. - -Workflows are a way of defining actions after your Form is submitted like sending an email or creating a content node. - -## Default Workflow - -By default, when a Form is submitted the record data is stored in the database. This can be configured in the [Store records](../creating-a-form/form-settings.md#settings-options) of the Forms settings. - -The behavior to display a message to the user who submitted the form can be configured by clicking on the built-in first workflow step. This step is labelled **Submit message/Go to page**, and it can also configure the redirection to another page. - -![Submit message/Go to page](images/MessageOnSubmit-v14.png) - -If a value is selected for **Go to page**, it will be used to redirect to that page once the form has been submitted. - -If no value is selected, the message in **Message on submit** is displayed to the user on the same page, instead of the form fields. This is implemented via a redirect to the current page, ensuring that the form can't be accidentally resubmitted. - -By default, the message is created and rendered in plain text. If you need to add formatting to the message, toggle the **Format message in rich text** button. - -![Submit message/Go to page](images/MessageOnSubmitRichText-v14.png) - -## Video Tutorial - -{% embed url="https://www.youtube.com/watch?ab_channel=UmbracoLearningBase&v=qJrf1drw1Bg" %} -Attaching Workflows to Umbraco Forms -{% endembed %} - -## Adding a Workflow - -At the bottom of your Form, a default workflow is already attached to the Form, as well as an option to configure the workflows. - -![Button](images/configure-workflows-v14.png) - -Clicking **Configure workflow** will give you the option to configure existing workflows, as well as setup new ones. - -![Workflow add](images/WorkflowsPage-v14.png) - -### Choose a Workflow - -A new workflow can be of different types and Umbraco Forms ships with a few default ones. You can find an overview of the types in the [Workflow types](workflow-types.md) article. - -![Workflow add modal](images/WorkflowsAddModel-v14.png) - -### Update Type-specific Settings - -Once the Workflow Type has been selected, you will need to configure the workflow. There are different settings depending on the type that has been selected. - -To use data from the submitted Form in your workflow, head over to the [Magic Strings](../../developer/magic-strings.md) article and learn more about how that's done. - -### Configuring Condition on a Workflow - -You can apply conditions to a workflow that trigger it only under specific circumstances. After adding the desired workflow type (for example, sending an email), you can add a condition to the workflow. - -Select **Enable conditions** to open the condition editor. In the condition editor, you will see options to create logic that determines when the workflow should run. The condition is generally based on the values of the form fields. - -For example: You have a form with a dropdown field labeled **Preferred Contact Method** with options such as **Email** and **Phone**. You can set up a workflow that sends an email notification only when the user selects **Email**. - -![Workflow Conditions](images/workflow-conditions.png) - -Now, this email notification will only be sent when the user selects **Email** as their preferred contact method. - -Fill in the rest of the settings and click **Submit**. The workflow is added to your Form and displayed at the bottom of the page. - -## Workflow Processing - -When a form is submitted, any workflows associated with the "submit" stage of the form will run sequentially in the configured order. The record is stored after these workflows are completed, and as such they can make changes to the information recorded. - -Similarly, approval of a form entry, whether automatic or manual, will trigger the execution of the workflows associated with the "approve" stage. - -Rejection of an entry will trigger the execution of the workflows associated with the "reject" stage. - -If a workflow encounters an unexpected error, it will silently fail from the perspective of the user submitting the form. The exception along with the other details of the failed operation is recorded to the log. - -From Umbraco Forms versions 8.13.0 and 10.1, an audit trail has been made available. In the list of entries for a form, a summary is presented that shows how many workflows were executed, and how many were successful: - -![Workflow execution summary](images/workflow-summary.png) - -For each entry, in the backoffice a table can be viewed that shows each of the workflows and the success, or otherwise, of the operation. - -![Workflow execution summary](images/workflow-audit.png) - -For any workflows that did not complete successfully, a "Retry" link is available to trigger the workflow again. This is useful for example if there was a temporary infrastructure issue that perhaps prevented an email going out. You would be able to retrigger the workflow once the issue is resolved. diff --git a/14/umbraco-forms/editor/attaching-workflows/images/MessageOnSubmit-v14.png b/14/umbraco-forms/editor/attaching-workflows/images/MessageOnSubmit-v14.png deleted file mode 100644 index 85a648b5bc1..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/MessageOnSubmit-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/MessageOnSubmit.png b/14/umbraco-forms/editor/attaching-workflows/images/MessageOnSubmit.png deleted file mode 100644 index 60cd7c57306..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/MessageOnSubmit.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/MessageOnSubmitRichText-v14.png b/14/umbraco-forms/editor/attaching-workflows/images/MessageOnSubmitRichText-v14.png deleted file mode 100644 index 1d89cf21e13..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/MessageOnSubmitRichText-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/MessageOnSubmitRichText.png b/14/umbraco-forms/editor/attaching-workflows/images/MessageOnSubmitRichText.png deleted file mode 100644 index 49b67e2cff7..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/MessageOnSubmitRichText.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/WorkflowOverview.png b/14/umbraco-forms/editor/attaching-workflows/images/WorkflowOverview.png deleted file mode 100644 index f156cca1d26..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/WorkflowOverview.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/Workflownode.png b/14/umbraco-forms/editor/attaching-workflows/images/Workflownode.png deleted file mode 100644 index c236ee78763..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/Workflownode.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/WorkflowsAddModal.png b/14/umbraco-forms/editor/attaching-workflows/images/WorkflowsAddModal.png deleted file mode 100644 index 3039c8ddd0f..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/WorkflowsAddModal.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/WorkflowsAddModel-v14.png b/14/umbraco-forms/editor/attaching-workflows/images/WorkflowsAddModel-v14.png deleted file mode 100644 index 5eaa074a6e8..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/WorkflowsAddModel-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/WorkflowsAddModel.png b/14/umbraco-forms/editor/attaching-workflows/images/WorkflowsAddModel.png deleted file mode 100644 index 66598e8f552..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/WorkflowsAddModel.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/WorkflowsPage-v14.png b/14/umbraco-forms/editor/attaching-workflows/images/WorkflowsPage-v14.png deleted file mode 100644 index e6c0a82009c..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/WorkflowsPage-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/WorkflowsPage.png b/14/umbraco-forms/editor/attaching-workflows/images/WorkflowsPage.png deleted file mode 100644 index 01815fa21e2..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/WorkflowsPage.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/WorkflowsPageAdd.png b/14/umbraco-forms/editor/attaching-workflows/images/WorkflowsPageAdd.png deleted file mode 100644 index d924d7e420a..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/WorkflowsPageAdd.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/WorkflowsPageAddAdd.png b/14/umbraco-forms/editor/attaching-workflows/images/WorkflowsPageAddAdd.png deleted file mode 100644 index 49468a6b78f..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/WorkflowsPageAddAdd.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/WorkflowsPageAddSelectType.png b/14/umbraco-forms/editor/attaching-workflows/images/WorkflowsPageAddSelectType.png deleted file mode 100644 index 1de9c4fc42f..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/WorkflowsPageAddSelectType.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/WorkflowsPageAddSubmit.PNG b/14/umbraco-forms/editor/attaching-workflows/images/WorkflowsPageAddSubmit.PNG deleted file mode 100644 index 544ea10c7c5..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/WorkflowsPageAddSubmit.PNG and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/WorkflowsPageAddTypeSettings.png b/14/umbraco-forms/editor/attaching-workflows/images/WorkflowsPageAddTypeSettings.png deleted file mode 100644 index c34d27e5e45..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/WorkflowsPageAddTypeSettings.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/change-record-state-v14.png b/14/umbraco-forms/editor/attaching-workflows/images/change-record-state-v14.png deleted file mode 100644 index 8153682ffde..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/change-record-state-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/change-record-state.png b/14/umbraco-forms/editor/attaching-workflows/images/change-record-state.png deleted file mode 100644 index 85a3e5f177f..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/change-record-state.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/configure-workflows-v14.png b/14/umbraco-forms/editor/attaching-workflows/images/configure-workflows-v14.png deleted file mode 100644 index 7951c5b6f24..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/configure-workflows-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/configure-workflows.png b/14/umbraco-forms/editor/attaching-workflows/images/configure-workflows.png deleted file mode 100644 index a1419f8c13c..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/configure-workflows.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/create-new-node.png b/14/umbraco-forms/editor/attaching-workflows/images/create-new-node.png deleted file mode 100644 index fbf73980957..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/create-new-node.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/email-slack-v14.png b/14/umbraco-forms/editor/attaching-workflows/images/email-slack-v14.png deleted file mode 100644 index 202af5757e0..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/email-slack-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/email-slack.png b/14/umbraco-forms/editor/attaching-workflows/images/email-slack.png deleted file mode 100644 index 03c8585713d..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/email-slack.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/post-as-xml-v14.png b/14/umbraco-forms/editor/attaching-workflows/images/post-as-xml-v14.png deleted file mode 100644 index 5d04edbb4ff..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/post-as-xml-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/post-as-xml.png b/14/umbraco-forms/editor/attaching-workflows/images/post-as-xml.png deleted file mode 100644 index ed22ad754a5..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/post-as-xml.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/save-as-an-xml-file-v14.png b/14/umbraco-forms/editor/attaching-workflows/images/save-as-an-xml-file-v14.png deleted file mode 100644 index ff5775ab668..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/save-as-an-xml-file-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/save-as-an-xml-file.png b/14/umbraco-forms/editor/attaching-workflows/images/save-as-an-xml-file.png deleted file mode 100644 index f6f8b1f1b50..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/save-as-an-xml-file.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/save-as-content-node-v14.png b/14/umbraco-forms/editor/attaching-workflows/images/save-as-content-node-v14.png deleted file mode 100644 index f50bdd2487e..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/save-as-content-node-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/save-as-content-node.png b/14/umbraco-forms/editor/attaching-workflows/images/save-as-content-node.png deleted file mode 100644 index 394b3f0c5d0..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/save-as-content-node.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/send-email-razor-v14.png b/14/umbraco-forms/editor/attaching-workflows/images/send-email-razor-v14.png deleted file mode 100644 index 5710b6b84f8..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/send-email-razor-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/send-email-razor.png b/14/umbraco-forms/editor/attaching-workflows/images/send-email-razor.png deleted file mode 100644 index 59cbe74aa75..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/send-email-razor.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/send-email-v14.png b/14/umbraco-forms/editor/attaching-workflows/images/send-email-v14.png deleted file mode 100644 index b0efad6e23a..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/send-email-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/send-email.png b/14/umbraco-forms/editor/attaching-workflows/images/send-email.png deleted file mode 100644 index 96b67e0ceb5..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/send-email.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/send-to-URL-v14.png b/14/umbraco-forms/editor/attaching-workflows/images/send-to-URL-v14.png deleted file mode 100644 index 3fad02e3ed2..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/send-to-URL-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/send-to-URL.png b/14/umbraco-forms/editor/attaching-workflows/images/send-to-URL.png deleted file mode 100644 index 40b1ff4dfad..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/send-to-URL.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/workflow-audit.png b/14/umbraco-forms/editor/attaching-workflows/images/workflow-audit.png deleted file mode 100644 index 2f4b33b5502..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/workflow-audit.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/workflow-conditions.png b/14/umbraco-forms/editor/attaching-workflows/images/workflow-conditions.png deleted file mode 100644 index c40623927ca..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/workflow-conditions.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/workflow-summary.png b/14/umbraco-forms/editor/attaching-workflows/images/workflow-summary.png deleted file mode 100644 index cb1553920b8..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/workflow-summary.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/workflowbutton.png b/14/umbraco-forms/editor/attaching-workflows/images/workflowbutton.png deleted file mode 100644 index 734758ffc9e..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/workflowbutton.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/xslt-email-v14.png b/14/umbraco-forms/editor/attaching-workflows/images/xslt-email-v14.png deleted file mode 100644 index 098799744ba..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/xslt-email-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/images/xslt-email.png b/14/umbraco-forms/editor/attaching-workflows/images/xslt-email.png deleted file mode 100644 index faa1e070fd8..00000000000 Binary files a/14/umbraco-forms/editor/attaching-workflows/images/xslt-email.png and /dev/null differ diff --git a/14/umbraco-forms/editor/attaching-workflows/workflow-types.md b/14/umbraco-forms/editor/attaching-workflows/workflow-types.md deleted file mode 100644 index 4142596f260..00000000000 --- a/14/umbraco-forms/editor/attaching-workflows/workflow-types.md +++ /dev/null @@ -1,229 +0,0 @@ ---- -description: >- - This article will give you an overview of the Workflow Types available in - Umbraco Forms. ---- - -# Workflow Types - -There are multiple built-in Workflow Types that can be used to extend the functionality of your form. Do you want to post the submitted form as XML, send the data as an email, or send a notification through another messaging system? These are a few of the options you can choose when working with Umbraco Forms. - -## Video Tutorial - -{% embed url="https://www.youtube.com/watch?ab_channel=UmbracoLearningBase&v=L9k0yDbV6qo" %} -Workflow Types in Umbraco Forms -{% endembed %} - -## **Change Record State** - -![Change Record state](images/change-record-state-v14.png) - -Used to automatically **Approve Record**, **Reject Record** or **Delete Record** once it is submitted. Configure words that you want to match and select whether these words should trigger an approval or deletion of the record. - -## **Post as XML** - -![Post as XML](images/post-as-xml-v14.png) - -Used to post the Form as an XML to a specified URL. The following configuration can be set: - -* Workflow Name -* URL (required) -* Method -* XsltFile - used to transform the XML -* Headers - map the needed files -* User -* Password - -## **Save as an XML file** - -![Save as XML](images/save-as-an-xml-file-v14.png) - -Saves the result of the Form as an XML file by using XSLT. The following configuration can be set: - -* Workflow Name -* Path (required) - where to save the XML file -* File extension (required) -* XsltFile - used to transform the XML - -The path needs to point to a folder, not a file name. The files are then stored locally, and relative paths are resolved to the content root. - -{% hint style="info" %} -When storing the files within the `wwwroot` or `App_Plugins` folders, the files will be publicly available by default. -{% endhint %} - -## **Save as Umbraco Content Node** - -![Save as content node](images/save-as-content-node-v14.png) - -Saves a submitted Form as a new content node. You need to choose a Document type and match the fields in the Form with the properties on the selected Document Type. - -You can also choose to set a static value to fill in the properties: - -![Save as content node](images/create-new-node.png) - -In the example above, a Document Type called **Blogpost** is selected for creating the new Content node. - -The value from the **Name** field will be added as the **Node Name** property in the new Content node. The value from the **Email** field will be used as the **Content** property. - -The following configuration can be set: - -* Workflow Name -* Publish - choose whether to publish the node on submission -* Where to save - choose a section in the content tree where this new node should be added - -## **Send Email** - -![Send email](images/send-email-v14.png) - -Sends the result of the Form to the specified email address. The following configuration can be set: - -* Workflow Name -* Message (required) -* Attachment - specify whether file uploads should be attached to the email -* Recipient Email (required) -* CC Email -* BCC Email -* SenderEmail -* Reply To Email -* Subject of the email (required) - -For fields that accept multiple email addresses (Recipient Email, CC Email, BCC Email), you can separate addresses using semicolons (';') or commas (','). For example: - -```none -person@umbraco.dk; person@umbraco.com, person@umbraco.de -``` - -If the _Sender Email_ field is not populated, the address used will be read from CMS configuration. - -The [Content Settings](https://docs.umbraco.com/umbraco-cms/reference/configuration/contentsettings) value configured at `Umbraco:CMS:Content:Notifications:Email` will be used if provided. - -```json - "Umbraco": { - "CMS": { - "Content": { - "Notifications": { - "Email": "person@umbraco.dk" - } - } - } - } -``` - -If that is not set, the [Global Settings](https://docs.umbraco.com/umbraco-cms/reference/configuration/globalsettings) value configured at `Umbraco:CMS:Global:Smtp` will be used. - -```json - "Umbraco": { - "CMS": { - "Global": { - "Smtp": { - "From": "person@umbraco.dk" - } - } - } - } -``` - -The fallback behavior also applies to the other email workflows. - -## **Send Email with Template (Razor)** - -![Send email with template](images/send-email-razor-v14.png) - -Uses a template to send the results of the Form to a specified email address. - -You can create your own custom Razor templates to be used to send out emails upon Forms submission. Read more about how to create these templates in the [Email Templates](../../developer/email-templates.md) article. - -The following configuration can be set: - -* Workflow Name -* Email Template (required) - specify which template you want to use -* Header text - formatted text that will be rendered above the form entry details -* Footer text - formatted text that will be rendered below the form entry details -* Attachments - specify whether file uploads should be attached to the email -* Recipient Email (required) -* CC Email -* BCC Email -* SenderEmail -* Reply To Email -* Subject of the email (required) - -## **Send Form to URL** - -![Send to URL](images/send-to-URL-v14.png) - -Sends the Form to a URL either as a HTTP POST or GET. The following configuration can be set: - -* Workflow Name -* URL (required) -* Method (required) - POST, GET, PUT or DELETE -* Standard Fields - optionally include and map standard form information such as name and page URL -* Fields - map the needed fields -* User -* Password - -When mapping fields, if any are selected, only those chosen will be sent in the request to the configured URL. If no fields are mapped, all will be sent. - -The receiving endpoint extracts form fields and values using GET for querystrings and POST for form collections. - -As an illustrative example, the following code can be used to write the posted form information to a text file: - -```csharp -using Microsoft.AspNetCore.Mvc; -using Microsoft.Extensions.Logging; -using System.IO; - -namespace RequestSaver.Controllers -{ - [ApiController] - [Route("[controller]")] - public class SaveRequestController : ControllerBase - { - private const string _filePath = "c:\\temp\\request-save.txt"; - - private readonly ILogger _logger; - - public SaveRequestController(ILogger logger) - { - _logger = logger; - } - - [HttpPost] - public string Save() - { - using (StreamWriter outputFile = new StreamWriter(_filePath)) - { - foreach (var key in Request.Form.Keys) - { - outputFile.WriteLine($"{key}: {(Request.Form[key])}"); - } - } - - return "Done"; - } - } -} -``` - -## **Send XSLT Transformed Email** - -![Send XSLT Email](images/xslt-email-v14.png) - -Sends the result of the Form to an email address with full control over the email contents by providing an xslt file. The following configuration can be set: - -* Workflow Name -* XSLT File - specify which file should be used to transform the content -* Recipient Email (required) -* CC Email -* BCC Email -* SenderEmail -* Reply To Email -* Subject of the email (required) - -## **Slack** - -![Send to Slack](images/email-slack-v14.png) - -Allows to post the Form data to a specific channel on Slack. The following configuration can be set: - -* Workflow Name -* Webhook URL (required) diff --git a/14/umbraco-forms/editor/creating-a-form/README.md b/14/umbraco-forms/editor/creating-a-form/README.md deleted file mode 100644 index 70a2086f24a..00000000000 --- a/14/umbraco-forms/editor/creating-a-form/README.md +++ /dev/null @@ -1,161 +0,0 @@ -# Creating a Form - The Basics - -In this article, we'll take a look at the basic steps of creating a Form and adding the Form to your Umbraco site. - -## Accessing the Forms Section - -You can manage the Forms in the **Forms** section of the Umbraco backoffice. You need to have access to the section in order to see it. - -If you do not see the **Forms** section, you might need to request access from the site Administrator. An Administrator can give permission to view the **Forms** section. This is done from the **Users** section of the backoffice. - -![Forms Section](images/FormsSectionV14.png) - -## Creating a Form - -To create a Form, follow these steps: - -1. Navigate to the **Forms** section. -2. Click **...** next to the Forms folder. - - ![Forms tree](images/FormsTree-v14.png) -3. Select **Create** > **New Form**. - - ![Forms create dialog](images/FormsCreateDialogV14.png) -4. The Form Designer opens in the editor. - - ![Forms designer](images/FormDesignerStartV14.png) -5. By default, there is a page, a fieldset, and a container available. The rest of the Form has to be added using the interface. -6. Enter a **Name** for the Form. Let's call it _Our first form_. - - ![Forms Name](images/FormDesignerFormNamev14.png) -7. *[Optional]* Enter the **Page Name**. We'll call it _The first page_. Click **Add new page** at the bottom of the Forms designer to add more pages. - - ![Forms Page Name](images/FormDesignerPageCaptionV14.png) -8. *[Optional]* Enter the **Group Name**. Click **Add new group** to add another group. - - ![Forms Group Name](images/FormDesignerPageGroupV14.png) -9. Click the **Add Question** button to add a new field. - - ![Forms Add Field](images/FormDesignerAddFieldV14.png) -10. The **Choose field type** dialog opens. - - ![Forms add field dialog](images/FormDesignerAddFieldDialogV14.png) -11. Select **Short Answer**. Enter the following details in the **Edit field** window: - - | Field Name | Value | - | ------------------ | -------------------- | - | Enter question | Name | - | Enter help text | Enter your name here | -12. In the **Sensitive data** field, choose if the field stores sensitive data. Once selected, the data from this field will be prevented from being downloaded and viewed by users who do not have permission to do so. Only members of the sensitive data user group will see this option of downloading. -13. Enter a **Default Value** for the field. -14. Add a **Placeholder** to make it easier for the user to fill in the Form. -15. Select if the field is **Mandatory** and customize the message. -16. Add a **Validation** to the field. There are some predefined validations available but it is possible to add your own custom validation as well. -17. Some form fields allow you to show or hide the label that's associated with the field when it is rendered within the form on the website. The default is always to show the field, but if you prefer to hide it, untick the **Show label** option. -18. Set **Conditions** for the field. For more information on Conditions, see the [Setting-up conditional logic on fields](conditional-logic.md) article. - - Some of the additional settings are dependent on which answer type was chosen. For example, since we selected _Short Answer_ as our answer type we got two additional settings (Default Value and Placeholder). -19. Once the configuration is completed, click **Submit**. You will see that the field has been added to the Form designer. - - ![Forms name field added](images/FormDesignerFieldAddedV14.png) - -To edit a field, click the **cog** icon next to the field to open the dialog. To copy the field and its properties, click the **copy** icon. To delete a field or a group, click the **Recycle Bin** icon. - -### Structuring the Form - -#### Ordering Fields - -Once you've added a few fields to your Form, you might want to change the order of questions. To do so, click **Reorder** in the top-right corner of the Form designer. - -![Reorder Form field](images/Reorder-Form-v14.png) - -When reordering your Form, you can drag and drop the fields to make it look the way you want. Click **I am done reordering** to get back to the Form designer. - -![Form Fields Reordered](images/Reorder-form-fields-done-v14.png) - -#### Form Pages - -Forms can be grouped into pages. When rendered, each page will be presented one at a time to the user. They will need to complete the first page before moving onto the second and can navigate back and forth between pages. - -To add a new page at the start or end of the form, use the buttons in the top right corner of the editing view. - -![Add new page button at the top of Form](images/add-new-page-v14.png) - -You can also add a new page directly to the bottom of the form via the **Add new page** button. This will appear below other pages when at least one exists. - -![Add new page button](images/add-new-page-button-v14.png) - -### Form Groups - -With a page, form fields can be arranged into groups. These will display all together on a single page but can be styled so the fields are appropriately grouped in fieldsets. - -New groups are added via the **Add new group** button. - -![Add new Group button](images/add-new-group-button-v14.png) - -## Form Columns - -The last level of structure are columns that can be created within a group. To set the number of columns, click the **cog** icon next to the Group Name. You can now add or move fields to the new columns created. - -![Form Columns](images/edit-group-columns.png) - -## Saving the Form - -Once have created the Form, save the design by clicking the **Save** button. - -![Form save Form](images/FormDesignerSaveV14.png) - -## Importing a Form - -**Import Form Definition** allows you to import a form into your Umbraco site using a predefined JSON file. This file contains the form’s structure, fields, validations, workflows, and settings. - -When you import a form definition, Umbraco uses the JSON structure to recreate the form as it was defined, enabling you to: - -- Reuse existing forms across multiple projects or environments. -- Migrate forms between development, testing, and production environments. -- Restore forms from backups or previously exported definitions. - -Using the **Import Form Definition** option, you can manage your forms without having to recreate them. - -![Import a Form](images/import-form.png) - -## Organizing Forms in Folders - -If the product installation is set up to store form definitions in the database, you will be able to store forms within folders. This can help with organization and makes it easier to locate the forms for modification, especially if you plan to create many Forms. - -To create a folder: - -1. Go to the **Forms** section. -2. Click ... next to Forms folder. -3. Select **Create**. -4. Select **New Folder**. - - ![Create Folder](images/create-forms-folder-v14.png) -5. Enter a **Folder Name**. -6. Click **Create Folder**. - - ![Folder Name](images/forms-folder-name-v14.png) - -You can create folders within folders, rename, move, import folders, or delete them. - -![Folder Options](images/Forms-folder-options-v14.png) - -To move or copy forms into folders, click the **...** next to the Form and select **Move**. - -![Move Form in Folder](images/move-form-in-folder-v14.png) - -## Adding the Form to the Umbraco Site - -To add the Form, follow these steps: - -1. Navigate to the **Content** section of the Umbraco Backoffice. -2. Select the content page where you want to insert the Form. The page you choose should have a form picker which you can add in the **Settings** section under **Document Types**. - - ![Content page](images/ContentExamples-v14.png) -3. Click **Choose** and select the Form you want to insert. You will be able to select from the full list of forms. If available on your installation, you will also be able to select using a folder based view, which can be quicker to navigate when many forms have been prepared. - - ![Content page add macro](images/ContentPageAddForm-v14.png) -4. Click **Choose**. -5. The Form is inserted on your page. Click **Save and publish**. - - ![Content page with form](images/ContentExamplesWithFormV14.png) diff --git a/14/umbraco-forms/editor/creating-a-form/conditional-logic.md b/14/umbraco-forms/editor/creating-a-form/conditional-logic.md deleted file mode 100644 index 4ee8c8c0511..00000000000 --- a/14/umbraco-forms/editor/creating-a-form/conditional-logic.md +++ /dev/null @@ -1,64 +0,0 @@ -# Setting-up Conditional Logic on Fields - -Sometimes you might have a field in your Form, that you want to show _only_ if the user has entered a specific value in another field. - -You can achieve this setting by using **conditional logic** on Fields. - -## Example - -Take a look at the following: - -![Example Form](images/ExampleForm-v14.png) - -In this case, it makes sense to *only* show the email or phone field when the corresponding option is selected in the **How should we contact you?** field. - -To enable conditions for the **Email** and **Phone** fields, do the following: - -1. Click the `cog` wheel next to the **Email** and **Phone** field. The **Edit question** dialog opens. -2. Enable **Conditions**. The condition field displays more options: - - ![Enable Conditions](images/conditions-v14.png) - -3. Set the appropriate conditions and click **Submit**. - -### Action and Logic Types - -There are two **Action Types**: - -* Show: the field will be displayed if the rules match -* Hide: the field will be hidden if the rules match - -Next up, you'll need to specify the **Logic Type**. This setting is only important if you have multiple rules. - -* All: All of the rules must match -* Any: Any of the rules may match - -## Adding a new condition - -When adding a new condition, you'll need to select the field where you want to evaluate the value and can select an operator. - -In this example, we only want to show the **Phone** field if the value of the **How should we contact you** field is `Phone`. - -![Setup rule](images/phone-conditions-v14.png) - -Similarly, you can display the **Email** field, if the value of the **How should we contact you** field is `Email`. You can see the conditions added to each field in the Forms designer: - -![See conditions in the Forms designer](images/exampleBackoffice-v14.png) - -## Result - -When both the conditions have been set as shown above, this is how it will look on the frontend: - -![Frontend Example](images/exampleFrontend-v14.png) - -In this example, we have only selected **Phone** but it is possible to choose both _Phone_\* and **Email** and display both the fields. - -## Conditions for Pages and Fieldsets - -As well as showing or hiding a field based on conditions, you can also apply conditions to groups of fields (known as fieldsets) or to pages. The process is the same as described above. - -When applying a condition to a page, effectively you are controlling the display of the submit button (for a single-page form) or the next/previous buttons (available on multi-page forms). In this way you can ensure that the entry so far is complete before accepting it or allowing the user to move onto the next page. - -## Conditions for Dates - -You can apply conditions to dates as well as strings. When you use the date picker field, you can set a condition if a submitted date is greater/less than a specific date. diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/README.md b/14/umbraco-forms/editor/creating-a-form/fieldtypes/README.md deleted file mode 100644 index f36c166aeb5..00000000000 --- a/14/umbraco-forms/editor/creating-a-form/fieldtypes/README.md +++ /dev/null @@ -1,51 +0,0 @@ -# Overview Of The Field Types - -Umbraco Forms comes with a bunch of default Field Types also known as **Answer Types**. You can choose from different field types when adding new fields to your Forms. - -By default, the following Field Types are available: - -* **Short Answer**: A textbox allows up to 250 characters. - - ![Textfield](images/shortanswer-V14.png) -* **Long Answer**: A bigger text field that allows multiline text and more than 250 characters. - - ![Textarea](images/longanswer-v14.png) -* [Date](date.md): Displays a picker that allows the user to select a date. - - ![Datepicker](images/date-v14.png) -* **Checkbox**: Displays a single checkbox that can be checked or not. - - ![Checkbox](images/CheckBox-v14.png) -* [File Upload](fileupload.md): Allows user to select and upload a local file. - - ![File upload](images/fileupload-v14.png) -* **Password**: Allows to type a password. The input is not visible when typing. - - ![Password field](images/password-v14.png) -* **Multiple Choice**: Displays a list of items with a checkbox for each item where the user can select multiple options. - - ![Checkboxlist](images/multiplechoice-v14.png) -* **Data Consent**: A field for the purpose of asking for data consent. By default, this field is added to all new Forms. - - ![Data Consent](images/dataconsent-v14.png) -* **Dropdown**: Displays a list of items in a drop down box where the user can select a single option. - - ![Dropdownlist](images/dropdown-v14.png) -* **Single Choice**: Displays a list of items with a radio button for each item where the user can select a single option. - - ![Single choice](images/singlechoice-v14.png) -* **Title and Description**: Displays a read-only title and description for a set of form fields. - - ![Title and description](images/titleanddescription-v14.png) -* **Rich Text**: Displays read-only formatted text that can be used to provide additional information and links within a form. - - ![Rich text](images/richtext-v14.png) -* **Hidden**: A hidden field allows developers to include data that cannot be seen or modified by users when a Form is submitted. - - ![Hidden](images/hidden-v14.png) -* [Recaptcha V2](recaptcha2.md): The field displays a single checkbox for the user to select in order to validate the Form. - - ![reCAPTCHA v2](images/recaptcha2-v14.png) -* [Recaptcha V3 with Score](recaptcha3.md): This field returns a score for each request without user interaction. The score is based on user interactions with the site and enables you to take an appropriate action for your site based on the score. - - ![reCAPTCHA v3](images/recaptcha3-v14.png) diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/date.md b/14/umbraco-forms/editor/creating-a-form/fieldtypes/date.md deleted file mode 100644 index 73f841dc893..00000000000 --- a/14/umbraco-forms/editor/creating-a-form/fieldtypes/date.md +++ /dev/null @@ -1,18 +0,0 @@ -# Date - -The date picker uses a front-end library called [Pikaday](https://github.com/dbushell/Pikaday) to display a UI to pick dates. - -![Date picker on frontend](images/date-v14.png) - -Pikaday date picker can be localized based on the page the Form is rendered on. - -The date picker displays the picked date in the required locale. Using JavaScript, a hidden field is updated with a standard date format to send to the server for storing record submissions. This avoids the locale mixing up the dates. - -To achieve localized date, a Razor partial view is included at `/Views/Partials/Forms/Themes/default/DatePicker.cshtml`. - -The **DatePicker.cshtml** includes the `moment-with-locales.min.js` library to help with the date locale formatting and the appropriate changes to Pikaday to support the locales. If you wish to use a different DatePicker component, edit the **DatePicker.cshtml** file as per your needs. - -## Configure the date picker - -The Date picker has [configuration settings](../../../developer/configuration/README.md#date-picker-field-type-configuration) to control the number of years shown in the picker and the date format. - diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/fileupload.md b/14/umbraco-forms/editor/creating-a-form/fieldtypes/fileupload.md deleted file mode 100644 index 4a201ca618b..00000000000 --- a/14/umbraco-forms/editor/creating-a-form/fieldtypes/fileupload.md +++ /dev/null @@ -1,36 +0,0 @@ -# File upload - -The File Upload field allows the users to upload a file along with the Form on your website. - -In this article, you will find details about the configuration options you have for the File Upload field. - -![fileupload](images/fileupload-types-v14.png) - -## Predefined allowed File Types - -You can choose to specify which files you want to allow the user to upload, when accessing the Form. - -To allow only specific files: - -1. Select the specific File Types the user should be able to upload. -2. Click **Submit**. - -{% hint style="info" %} -We recommend selecting only specified files, to limit malicious code to be uploaded, whenever the user is submitting the Form. -{% endhint %} - -## User Defined Allowed File Types - -If the list of predefined file types does not include a specific file type, you can add additional ones. - -To add new file type: - -1. Type a file extension name in the **User defined allowed file types** field. -2. Click **+**. -3. Click **Submit**. - -## Server-side file validation - -The file upload field type will verify the file contents using the registered set of `IFileStreamSecurityValidator` instances. - -To read more about this feature, see [Server-side file validation](https://docs.umbraco.com/umbraco-cms/v/10.latest-lts/reference/security/serverside-file-validation) in the CMS documentation. diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/CheckBox-v14.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/CheckBox-v14.png deleted file mode 100644 index 0236d22b7bd..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/CheckBox-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/CheckBox-v9.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/CheckBox-v9.png deleted file mode 100644 index b25bb9e7981..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/CheckBox-v9.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/CheckBox.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/CheckBox.png deleted file mode 100644 index 83e772f6d8f..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/CheckBox.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/dataconsent-v14.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/dataconsent-v14.png deleted file mode 100644 index c79ab2a79b7..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/dataconsent-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/dataconsent-v9.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/dataconsent-v9.png deleted file mode 100644 index 5593e50daed..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/dataconsent-v9.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/dataconsent.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/dataconsent.png deleted file mode 100644 index 6212b9aaa08..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/dataconsent.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/date-picker.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/date-picker.png deleted file mode 100644 index 88438cf1128..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/date-picker.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/date-v14.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/date-v14.png deleted file mode 100644 index 97e766caeb8..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/date-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/date-v9.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/date-v9.png deleted file mode 100644 index a7120c5bd61..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/date-v9.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/date.PNG b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/date.PNG deleted file mode 100644 index 29b4381bcbb..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/date.PNG and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/dropdown-v14.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/dropdown-v14.png deleted file mode 100644 index 675c49aef4c..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/dropdown-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/dropdown-v9.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/dropdown-v9.png deleted file mode 100644 index 449893930f3..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/dropdown-v9.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/dropdown.PNG b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/dropdown.PNG deleted file mode 100644 index 6e91b9d23f6..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/dropdown.PNG and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/fileupload-types-v14.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/fileupload-types-v14.png deleted file mode 100644 index fe6d83959e6..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/fileupload-types-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/fileupload-types.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/fileupload-types.png deleted file mode 100644 index f00c05c4fc2..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/fileupload-types.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/fileupload-v14.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/fileupload-v14.png deleted file mode 100644 index a0dbb52c581..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/fileupload-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/fileupload-v9.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/fileupload-v9.png deleted file mode 100644 index 4e60329f2fc..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/fileupload-v9.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/fileupload.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/fileupload.png deleted file mode 100644 index f80a306f364..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/fileupload.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/hidden-v14.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/hidden-v14.png deleted file mode 100644 index bfdfe08a630..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/hidden-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/hidden-v9.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/hidden-v9.png deleted file mode 100644 index 5ab1c600a3e..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/hidden-v9.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/hidden.PNG b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/hidden.PNG deleted file mode 100644 index bc9f9ce9fa1..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/hidden.PNG and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/longanswer-v14.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/longanswer-v14.png deleted file mode 100644 index 009387ada19..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/longanswer-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/longanswer-v9.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/longanswer-v9.png deleted file mode 100644 index 9980b404ede..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/longanswer-v9.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/longanswer.PNG b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/longanswer.PNG deleted file mode 100644 index 077b1b2c7dc..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/longanswer.PNG and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/multiplechoice-v14.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/multiplechoice-v14.png deleted file mode 100644 index 1e09a543229..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/multiplechoice-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/multiplechoice-v9.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/multiplechoice-v9.png deleted file mode 100644 index d1a37cedf1c..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/multiplechoice-v9.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/multiplechoice.PNG b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/multiplechoice.PNG deleted file mode 100644 index 8d3344212e7..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/multiplechoice.PNG and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/password-v14.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/password-v14.png deleted file mode 100644 index 94909e503df..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/password-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/password-v9.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/password-v9.png deleted file mode 100644 index c771733f6f7..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/password-v9.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/password.PNG b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/password.PNG deleted file mode 100644 index 6ed6590fd8d..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/password.PNG and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/recaptcha2-v14.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/recaptcha2-v14.png deleted file mode 100644 index 87d6f6e63c6..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/recaptcha2-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/recaptcha2-v9.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/recaptcha2-v9.png deleted file mode 100644 index c5de9019855..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/recaptcha2-v9.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/recaptcha2.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/recaptcha2.png deleted file mode 100644 index 2ae28bcf014..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/recaptcha2.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/recaptcha3-v14.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/recaptcha3-v14.png deleted file mode 100644 index c68b59b5eb3..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/recaptcha3-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/recaptcha3-v9.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/recaptcha3-v9.png deleted file mode 100644 index 41d9316ede4..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/recaptcha3-v9.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/richtext-v14.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/richtext-v14.png deleted file mode 100644 index 0ec23abba93..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/richtext-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/richtext.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/richtext.png deleted file mode 100644 index da89d3394cc..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/richtext.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/shortanswer-V14.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/shortanswer-V14.png deleted file mode 100644 index 95dfabe1fca..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/shortanswer-V14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/shortanswer-v9.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/shortanswer-v9.png deleted file mode 100644 index 6e504b4aa61..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/shortanswer-v9.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/shortanswer.PNG b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/shortanswer.PNG deleted file mode 100644 index bf130226f3b..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/shortanswer.PNG and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/singlechoice-v14.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/singlechoice-v14.png deleted file mode 100644 index 1c36d09f476..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/singlechoice-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/singlechoice-v9.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/singlechoice-v9.png deleted file mode 100644 index f175439fd32..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/singlechoice-v9.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/singlechoice.PNG b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/singlechoice.PNG deleted file mode 100644 index 589dbd4d563..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/singlechoice.PNG and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/titleanddescription-v14.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/titleanddescription-v14.png deleted file mode 100644 index 00b2877899d..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/titleanddescription-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/titleanddescription-v9.png b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/titleanddescription-v9.png deleted file mode 100644 index 1260f8cb9d2..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/titleanddescription-v9.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/titleanddescription.PNG b/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/titleanddescription.PNG deleted file mode 100644 index 02c2187853d..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/fieldtypes/images/titleanddescription.PNG and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/recaptcha2.md b/14/umbraco-forms/editor/creating-a-form/fieldtypes/recaptcha2.md deleted file mode 100644 index 6ee355bd82d..00000000000 --- a/14/umbraco-forms/editor/creating-a-form/fieldtypes/recaptcha2.md +++ /dev/null @@ -1,28 +0,0 @@ -# reCAPTCHA V2 - -In Umbraco Forms, reCAPTCHA V2 comes out of the box to help you to protect your site from spam, malicious people, and so on. - -## Enabling reCAPTCHA V2 - -Follow these steps to enable reCAPTCHA V2 in Umbraco Forms: - -1. Go to the **Forms** section in the backoffice. -2. Find the form that should have **ReCAPTCHA v2** enabled. -3. Add a new question and select **ReCAPTCHA v2** as its answer type. -4. Make sure the field is set as **Mandatory**. -5. Configure ReCAPTCHA settings in the `appSettings.json` file to include public and private keys: - -```json -"Umbraco"{ - "Forms": { - "FieldTypes": { - "Recaptcha2": { - "PublicKey": "", - "PrivateKey": "" - } - } - } - } -``` - -You can create your keys by logging into your [reCAPTCHA account](https://www.google.com/recaptcha/). diff --git a/14/umbraco-forms/editor/creating-a-form/fieldtypes/recaptcha3.md b/14/umbraco-forms/editor/creating-a-form/fieldtypes/recaptcha3.md deleted file mode 100644 index e8d23ca9bc4..00000000000 --- a/14/umbraco-forms/editor/creating-a-form/fieldtypes/recaptcha3.md +++ /dev/null @@ -1,30 +0,0 @@ -# reCAPTCHA V3 - -In Umbraco Forms, reCAPTCHA V3 comes out of the box. - -reCAPTCHA v3 allows you to verify if an interaction is legitimate without any user interaction. - -## Enabling reCAPTCHA V3 - -Follow these steps to enable reCAPTCHA V3 in Umbraco Forms: - -1. Go to the **Forms** section in the backoffice. -2. Find the form that should have **ReCAPTCHA v3** enabled. -3. Add a new question and select **ReCAPTCHA v3 with Score** as its answer type. -4. Make sure the field is set as **Mandatory**. -5. Configure ReCAPTCHA settings in the `appSettings.json` file to include public and private keys: - -```json -"Umbraco"{ - "Forms": { - "FieldTypes": { - "Recaptcha3": { - "SiteKey": "", - "PrivateKey": "" - } - } - } - } -``` - -You can create your keys by logging into your [reCAPTCHA account](https://www.google.com/recaptcha/). diff --git a/14/umbraco-forms/editor/creating-a-form/form-info.md b/14/umbraco-forms/editor/creating-a-form/form-info.md deleted file mode 100644 index ce615b50b51..00000000000 --- a/14/umbraco-forms/editor/creating-a-form/form-info.md +++ /dev/null @@ -1,25 +0,0 @@ -# Form Information - -You can view the System information of the form in the **Info** tab. - -To access the Form Information: - -1. Go to the **Forms** section. -2. Open a Form you wish to customize. -3. Click **Info** in the top-right corner of the screen. - -![Form information dialog](images/form-info-V14.png) - -## General - -The "General" panel displays system information about the form. The date the form was created and last updated are shown. Also available are the integer and GUID identifiers that are useful when referring to the form in code. - -![Form general information panel](images/form-info-general-v14.png) - -## References - -Information about which pages a form is hosted on is tracked by Umbraco every time a content item is saved. - -The list of pages where the form is hosted is shown in this section. - -![Form relations panel](images/form-info-references-V14.png) diff --git a/14/umbraco-forms/editor/creating-a-form/form-settings.md b/14/umbraco-forms/editor/creating-a-form/form-settings.md deleted file mode 100644 index 2139b30efed..00000000000 --- a/14/umbraco-forms/editor/creating-a-form/form-settings.md +++ /dev/null @@ -1,98 +0,0 @@ -# Form Settings - -In this article, you will find information about accessing the Form Settings and the validations available to customize your Form. - -To access the Form Settings: - -1. Go to the **Forms** section. -2. Open a Form you wish to customize. -3. Click **Settings** in the top-right corner of the screen. - - ![Form settings dialog](images/FormSettings-V14.png) - -## Settings Options - -The following options are available in Forms Settings: - -### Store Records - -By default, all submitted records are saved in the database. This option allows you to view and export the saved records from the queries overview. If you do not want to store data (due to policies in your organization), you can uncheck the box. - -Disabling this option will prevent database records from being stored, but any file uploads made as part of the form submission will still be retained. If you do not want the files to be stored, ensure that any process or method used to process, move, or copy them to a different location also removes the file. - -![Form settings Store Records](images/Store-Records-V14.png) - -### Captions - -Customize the labels of the **Submit**, **Next**, and **Previous** buttons used in your Form. - -![Form settings stylesheet](images/FormSettingsCaptions-V14.png) - -### Styling - -Set a stylesheet to give your Form custom styling. You have an option to disable the default styling. Enabling the **Disable default stylesheet** option will prevent a default stylesheet to be added to the pages where the Form is placed. - -![Form settings stylesheet](images/FormSettingsStyling-V14.png) - -### Validation - -Define a message that is displayed when a field is mandatory, when a value is not supplied, or when the value is invalid. - -![Form settings validation](images/FormSettingsValidation-V14.png) - -The following Validations are available: - -| Validation Type | Description | -| -------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| **Mandatory error message** | The error message is displayed for a field that is marked as mandatory but a value has not been provided upon submission. This setting can be overwritten on a field level - `{0}` will be replaced with the field caption. | -| **Invalid error message** | The error message is displayed for a field if the value provided is not valid (a regular expression has been setup but the input does not match). This setting can be overwritten on a field level - `{0}` will be replaced with the field caption. | -| **Show validation summary** | Enable this option if you wish to display a summary of all the error messages on top of the Form. | -| **Hide field validation labels** | Enable this option if you wish to hide individual field error messages from being displayed. | -| **Mark fields** | You can choose to not mark any fields or only mark mandatory or optional fields. | -| **Indicator** | Choose which indicator to use when a field has been marked as mandatory. The default indicator is `*` | - -### Autocomplete - -The autocomplete setting for the overall form can be changed from the default of "None" to "On" or "Off". Setting this explicitly will control how the browser offers automatic prompts to the user when completing the form. - -![Form Settings Autocomplete](images/FormSettingsAutocomplete-V14.png) - -### Multi-page forms - -The settings available in this section allow you to customize how multi-page forms are presented to site visitors. - -

Multi-Page Form Settings

- -| Option | Description | -| -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| **Paging display** | Select whether paging information is displayed at the top and/or bottom of the form. | -| **Paging display format** | Provide a format string for the paging details. By default `Page {0} of {1}` is used which will be replaced as, for example, `Page 1 of 4`. | -| **Page caption format** | Provide a format string for rendering the page captions. By default `Page {0}` is used which will be replaced as, for example, `Page 1`. If a caption for the page has been provided, it will be used instead. | -| **Show summary page** | Select whether a summary page is displayed at the end of multi-page forms, where a user can review their entry before submitting. | -| **Summary heading** | Provide the heading for the summary page. | - -{% hint style="info" %} -These options will only be available if [the feature is configured for display](../../developer/configuration/README.md#enablemultipageformsettings). -{% endhint %} - -### Moderation - -Enabling this feature allows the moderator to manage the approval status of a form. This can be used in a number of scenarios. For example, if the form submission will be publicly shown, you can control which are published. - -![Form settings Moderation](images/FormSettingsModeration-V14.png) - -### Fields Displayed - -By default, a constant set of fields are displayed when form entries are shown in a list. You will see the first three fields in the form, plus some system information like the record state and the date it was created. - -To customize this, turn off the "Display default fields" option and select the ones you wish to display. - -![Form settings Fields Displayed](images/FormSettingsFieldsDisplayed-V14.png) - -### Data Retentions - -To help protect site visitor privacy, rules can be configured in this section for the automatic deletion of submissions. You can set how long to retain records for each state (submitted, approved or rejected). - -A background service that carries out the actual removal of records needs to be [enabled in configuration](../../developer/configuration/#scheduledrecorddeletion). If that is not running, a notification will be displayed. - -![Form settings Date Retentions](images/FormSettingsDataRetention-V14.png) diff --git a/14/umbraco-forms/editor/creating-a-form/images/ContentExampleMacroButton.png b/14/umbraco-forms/editor/creating-a-form/images/ContentExampleMacroButton.png deleted file mode 100644 index 6eb9af9ba2a..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/ContentExampleMacroButton.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/ContentExamples-v14.png b/14/umbraco-forms/editor/creating-a-form/images/ContentExamples-v14.png deleted file mode 100644 index 1631e9aa17f..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/ContentExamples-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/ContentExamples.png b/14/umbraco-forms/editor/creating-a-form/images/ContentExamples.png deleted file mode 100644 index 4788a8051cb..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/ContentExamples.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/ContentExamplesWithForm.png b/14/umbraco-forms/editor/creating-a-form/images/ContentExamplesWithForm.png deleted file mode 100644 index fbfac9ec1e2..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/ContentExamplesWithForm.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/ContentExamplesWithFormV14.png b/14/umbraco-forms/editor/creating-a-form/images/ContentExamplesWithFormV14.png deleted file mode 100644 index aad96c12297..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/ContentExamplesWithFormV14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/ContentPage.png b/14/umbraco-forms/editor/creating-a-form/images/ContentPage.png deleted file mode 100644 index 4f69f96fbb9..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/ContentPage.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/ContentPageAddForm-v14.png b/14/umbraco-forms/editor/creating-a-form/images/ContentPageAddForm-v14.png deleted file mode 100644 index 8193eb6a31d..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/ContentPageAddForm-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/ContentPageAddMacroDialog.png b/14/umbraco-forms/editor/creating-a-form/images/ContentPageAddMacroDialog.png deleted file mode 100644 index 768d74786e2..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/ContentPageAddMacroDialog.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/ContentPageAddMacroDialogChooseForm.png b/14/umbraco-forms/editor/creating-a-form/images/ContentPageAddMacroDialogChooseForm.png deleted file mode 100644 index 0e7d474a735..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/ContentPageAddMacroDialogChooseForm.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/ContentPageMacroButton.png b/14/umbraco-forms/editor/creating-a-form/images/ContentPageMacroButton.png deleted file mode 100644 index 4b246d8300e..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/ContentPageMacroButton.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/ContentPageWithForm.png b/14/umbraco-forms/editor/creating-a-form/images/ContentPageWithForm.png deleted file mode 100644 index 20367d97c3a..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/ContentPageWithForm.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/EnableConditions-v9.png b/14/umbraco-forms/editor/creating-a-form/images/EnableConditions-v9.png deleted file mode 100644 index c966c9dd1b5..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/EnableConditions-v9.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/EnableConditions.png b/14/umbraco-forms/editor/creating-a-form/images/EnableConditions.png deleted file mode 100644 index 6b340b94d29..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/EnableConditions.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/ExampleForm-v14.png b/14/umbraco-forms/editor/creating-a-form/images/ExampleForm-v14.png deleted file mode 100644 index 9c511f6dfe5..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/ExampleForm-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/ExampleForm.png b/14/umbraco-forms/editor/creating-a-form/images/ExampleForm.png deleted file mode 100644 index ff0f3e4d85f..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/ExampleForm.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerAddField.png b/14/umbraco-forms/editor/creating-a-form/images/FormDesignerAddField.png deleted file mode 100644 index 8b0e1300dcd..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerAddField.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerAddFieldDialog.png b/14/umbraco-forms/editor/creating-a-form/images/FormDesignerAddFieldDialog.png deleted file mode 100644 index 98dccacddfb..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerAddFieldDialog.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerAddFieldDialogV14.png b/14/umbraco-forms/editor/creating-a-form/images/FormDesignerAddFieldDialogV14.png deleted file mode 100644 index acca60a6587..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerAddFieldDialogV14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerAddFieldDialogV8.png b/14/umbraco-forms/editor/creating-a-form/images/FormDesignerAddFieldDialogV8.png deleted file mode 100644 index a3496f28f83..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerAddFieldDialogV8.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerAddFieldV14.png b/14/umbraco-forms/editor/creating-a-form/images/FormDesignerAddFieldV14.png deleted file mode 100644 index 532d3ce4218..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerAddFieldV14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerAddFieldV8.png b/14/umbraco-forms/editor/creating-a-form/images/FormDesignerAddFieldV8.png deleted file mode 100644 index e299ae2e4c7..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerAddFieldV8.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerFieldAdded.png b/14/umbraco-forms/editor/creating-a-form/images/FormDesignerFieldAdded.png deleted file mode 100644 index 295eea6fb2e..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerFieldAdded.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerFieldAddedV14.png b/14/umbraco-forms/editor/creating-a-form/images/FormDesignerFieldAddedV14.png deleted file mode 100644 index df5c3351312..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerFieldAddedV14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerFieldAddedV8.png b/14/umbraco-forms/editor/creating-a-form/images/FormDesignerFieldAddedV8.png deleted file mode 100644 index dec6a524c71..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerFieldAddedV8.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerFormName.png b/14/umbraco-forms/editor/creating-a-form/images/FormDesignerFormName.png deleted file mode 100644 index 44b3416ea87..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerFormName.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerFormNameV8.png b/14/umbraco-forms/editor/creating-a-form/images/FormDesignerFormNameV8.png deleted file mode 100644 index d6309410183..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerFormNameV8.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerFormNamev14.png b/14/umbraco-forms/editor/creating-a-form/images/FormDesignerFormNamev14.png deleted file mode 100644 index 633800eb6db..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerFormNamev14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerPageCaption.png b/14/umbraco-forms/editor/creating-a-form/images/FormDesignerPageCaption.png deleted file mode 100644 index 86f6b8c0da9..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerPageCaption.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerPageCaptionV14.png b/14/umbraco-forms/editor/creating-a-form/images/FormDesignerPageCaptionV14.png deleted file mode 100644 index abc1667bf8f..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerPageCaptionV14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerPageCaptionV8.png b/14/umbraco-forms/editor/creating-a-form/images/FormDesignerPageCaptionV8.png deleted file mode 100644 index d3949955585..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerPageCaptionV8.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerPageGroup.png b/14/umbraco-forms/editor/creating-a-form/images/FormDesignerPageGroup.png deleted file mode 100644 index 21e7a5cfedb..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerPageGroup.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerPageGroupV14.png b/14/umbraco-forms/editor/creating-a-form/images/FormDesignerPageGroupV14.png deleted file mode 100644 index 2eec93fa39f..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerPageGroupV14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerPageGroupV8.png b/14/umbraco-forms/editor/creating-a-form/images/FormDesignerPageGroupV8.png deleted file mode 100644 index 60b9ba0ec4c..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerPageGroupV8.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerSave.png b/14/umbraco-forms/editor/creating-a-form/images/FormDesignerSave.png deleted file mode 100644 index 9f7d175686c..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerSave.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerSaveV14.png b/14/umbraco-forms/editor/creating-a-form/images/FormDesignerSaveV14.png deleted file mode 100644 index 14277e102f0..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerSaveV14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerSaveV8.png b/14/umbraco-forms/editor/creating-a-form/images/FormDesignerSaveV8.png deleted file mode 100644 index 65ba8981085..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerSaveV8.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerSetFieldCaption.png b/14/umbraco-forms/editor/creating-a-form/images/FormDesignerSetFieldCaption.png deleted file mode 100644 index cccb58ed6fc..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerSetFieldCaption.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerStart.png b/14/umbraco-forms/editor/creating-a-form/images/FormDesignerStart.png deleted file mode 100644 index 1c8c630ba2b..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerStart.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerStartV14.png b/14/umbraco-forms/editor/creating-a-form/images/FormDesignerStartV14.png deleted file mode 100644 index 71d3d2f3908..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerStartV14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerStartV8.png b/14/umbraco-forms/editor/creating-a-form/images/FormDesignerStartV8.png deleted file mode 100644 index c2d410cc4b8..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormDesignerStartV8.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormSettings-V14.png b/14/umbraco-forms/editor/creating-a-form/images/FormSettings-V14.png deleted file mode 100644 index 45713c06409..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormSettings-V14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormSettings.png b/14/umbraco-forms/editor/creating-a-form/images/FormSettings.png deleted file mode 100644 index 75869b154b9..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormSettings.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormSettingsAutocomplete (1).png b/14/umbraco-forms/editor/creating-a-form/images/FormSettingsAutocomplete (1).png deleted file mode 100644 index 148c59918e3..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormSettingsAutocomplete (1).png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormSettingsAutocomplete-V14.png b/14/umbraco-forms/editor/creating-a-form/images/FormSettingsAutocomplete-V14.png deleted file mode 100644 index 7580de5f9d8..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormSettingsAutocomplete-V14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormSettingsAutocomplete.png b/14/umbraco-forms/editor/creating-a-form/images/FormSettingsAutocomplete.png deleted file mode 100644 index 148c59918e3..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormSettingsAutocomplete.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormSettingsCaptions-V14.png b/14/umbraco-forms/editor/creating-a-form/images/FormSettingsCaptions-V14.png deleted file mode 100644 index 6cfe5eba5cb..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormSettingsCaptions-V14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormSettingsCaptions-v9.png b/14/umbraco-forms/editor/creating-a-form/images/FormSettingsCaptions-v9.png deleted file mode 100644 index 47d983ac098..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormSettingsCaptions-v9.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormSettingsCaptions.png b/14/umbraco-forms/editor/creating-a-form/images/FormSettingsCaptions.png deleted file mode 100644 index 78aa8931291..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormSettingsCaptions.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormSettingsDataRetention-V14.png b/14/umbraco-forms/editor/creating-a-form/images/FormSettingsDataRetention-V14.png deleted file mode 100644 index 1285c139069..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormSettingsDataRetention-V14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormSettingsDataRetention.png b/14/umbraco-forms/editor/creating-a-form/images/FormSettingsDataRetention.png deleted file mode 100644 index 9021062ac0a..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormSettingsDataRetention.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormSettingsFieldsDisplayed-V14.png b/14/umbraco-forms/editor/creating-a-form/images/FormSettingsFieldsDisplayed-V14.png deleted file mode 100644 index 9193b25fbe4..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormSettingsFieldsDisplayed-V14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormSettingsFieldsDisplayed.png b/14/umbraco-forms/editor/creating-a-form/images/FormSettingsFieldsDisplayed.png deleted file mode 100644 index 18cc4170619..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormSettingsFieldsDisplayed.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormSettingsModeration-V14.png b/14/umbraco-forms/editor/creating-a-form/images/FormSettingsModeration-V14.png deleted file mode 100644 index 6ae72c1f72b..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormSettingsModeration-V14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormSettingsModeration.png b/14/umbraco-forms/editor/creating-a-form/images/FormSettingsModeration.png deleted file mode 100644 index 02deafec93d..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormSettingsModeration.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormSettingsStyling-V14.png b/14/umbraco-forms/editor/creating-a-form/images/FormSettingsStyling-V14.png deleted file mode 100644 index bfd37303560..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormSettingsStyling-V14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormSettingsStyling.png b/14/umbraco-forms/editor/creating-a-form/images/FormSettingsStyling.png deleted file mode 100644 index 450a2a8ace6..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormSettingsStyling.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormSettingsValidation-V14.png b/14/umbraco-forms/editor/creating-a-form/images/FormSettingsValidation-V14.png deleted file mode 100644 index d4ec44a8472..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormSettingsValidation-V14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormSettingsValidation.png b/14/umbraco-forms/editor/creating-a-form/images/FormSettingsValidation.png deleted file mode 100644 index ed70a24c4af..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormSettingsValidation.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/Forms-folder-options-v14.png b/14/umbraco-forms/editor/creating-a-form/images/Forms-folder-options-v14.png deleted file mode 100644 index f3ed72c626f..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/Forms-folder-options-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormsCreateDialog.png b/14/umbraco-forms/editor/creating-a-form/images/FormsCreateDialog.png deleted file mode 100644 index 147cb920f8d..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormsCreateDialog.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormsCreateDialogV14.png b/14/umbraco-forms/editor/creating-a-form/images/FormsCreateDialogV14.png deleted file mode 100644 index 7a0f7d6c053..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormsCreateDialogV14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormsCreateDialogV8.png b/14/umbraco-forms/editor/creating-a-form/images/FormsCreateDialogV8.png deleted file mode 100644 index ed694743220..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormsCreateDialogV8.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormsCreateDialogV9.png b/14/umbraco-forms/editor/creating-a-form/images/FormsCreateDialogV9.png deleted file mode 100644 index b607cfdfedc..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormsCreateDialogV9.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormsFieldSettings.gif b/14/umbraco-forms/editor/creating-a-form/images/FormsFieldSettings.gif deleted file mode 100644 index eee91a2c3f2..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormsFieldSettings.gif and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormsSection.png b/14/umbraco-forms/editor/creating-a-form/images/FormsSection.png deleted file mode 100644 index 388839d192e..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormsSection.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormsSectionV14.png b/14/umbraco-forms/editor/creating-a-form/images/FormsSectionV14.png deleted file mode 100644 index c8cbd01f797..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormsSectionV14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormsSectionV8.png b/14/umbraco-forms/editor/creating-a-form/images/FormsSectionV8.png deleted file mode 100644 index d10b6854700..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormsSectionV8.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormsSectionV9.png b/14/umbraco-forms/editor/creating-a-form/images/FormsSectionV9.png deleted file mode 100644 index ff9731388e2..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormsSectionV9.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormsTree-v14.png b/14/umbraco-forms/editor/creating-a-form/images/FormsTree-v14.png deleted file mode 100644 index 8d1af3e3ea6..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormsTree-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/FormsTree.png b/14/umbraco-forms/editor/creating-a-form/images/FormsTree.png deleted file mode 100644 index 83c8153e016..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/FormsTree.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/Reorder-Form-v14.png b/14/umbraco-forms/editor/creating-a-form/images/Reorder-Form-v14.png deleted file mode 100644 index e0424f8deb8..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/Reorder-Form-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/Reorder-form-fields-done-v14.png b/14/umbraco-forms/editor/creating-a-form/images/Reorder-form-fields-done-v14.png deleted file mode 100644 index d4f50e63259..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/Reorder-form-fields-done-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/Reorder_Form.png b/14/umbraco-forms/editor/creating-a-form/images/Reorder_Form.png deleted file mode 100644 index 46d08a18cce..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/Reorder_Form.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/Reorder_Form_1.png b/14/umbraco-forms/editor/creating-a-form/images/Reorder_Form_1.png deleted file mode 100644 index ca5c608127b..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/Reorder_Form_1.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/Store-Records-V14.png b/14/umbraco-forms/editor/creating-a-form/images/Store-Records-V14.png deleted file mode 100644 index 2f1cc088557..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/Store-Records-V14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/Store-Records.png b/14/umbraco-forms/editor/creating-a-form/images/Store-Records.png deleted file mode 100644 index 4c6b7287dd5..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/Store-Records.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/add-new-group-button-v14.png b/14/umbraco-forms/editor/creating-a-form/images/add-new-group-button-v14.png deleted file mode 100644 index 47bed8874f0..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/add-new-group-button-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/add-new-page-button-v14.png b/14/umbraco-forms/editor/creating-a-form/images/add-new-page-button-v14.png deleted file mode 100644 index 4c8502b0f23..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/add-new-page-button-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/add-new-page-v14.png b/14/umbraco-forms/editor/creating-a-form/images/add-new-page-v14.png deleted file mode 100644 index 57809496a8e..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/add-new-page-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/add-new-page.png b/14/umbraco-forms/editor/creating-a-form/images/add-new-page.png deleted file mode 100644 index c7eccc7a639..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/add-new-page.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/conditions-v14.png b/14/umbraco-forms/editor/creating-a-form/images/conditions-v14.png deleted file mode 100644 index 71ff4f34777..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/conditions-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/conditions-v9.png b/14/umbraco-forms/editor/creating-a-form/images/conditions-v9.png deleted file mode 100644 index 894fa43a1c5..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/conditions-v9.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/conditions.png b/14/umbraco-forms/editor/creating-a-form/images/conditions.png deleted file mode 100644 index 6fa49f4e76d..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/conditions.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/create-forms-folder-v14.png b/14/umbraco-forms/editor/creating-a-form/images/create-forms-folder-v14.png deleted file mode 100644 index b5fef0962e7..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/create-forms-folder-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/edit-group-columns.png b/14/umbraco-forms/editor/creating-a-form/images/edit-group-columns.png deleted file mode 100644 index a57099f3d6d..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/edit-group-columns.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/email.png b/14/umbraco-forms/editor/creating-a-form/images/email.png deleted file mode 100644 index bf8baf3211b..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/email.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/exampleBackoffice-v14.png b/14/umbraco-forms/editor/creating-a-form/images/exampleBackoffice-v14.png deleted file mode 100644 index c950da37724..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/exampleBackoffice-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/exampleBackoffice-v9.png b/14/umbraco-forms/editor/creating-a-form/images/exampleBackoffice-v9.png deleted file mode 100644 index 2a1c0a8d0d5..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/exampleBackoffice-v9.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/exampleBackoffice.png b/14/umbraco-forms/editor/creating-a-form/images/exampleBackoffice.png deleted file mode 100644 index 9e2798b2350..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/exampleBackoffice.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/exampleConditions.png b/14/umbraco-forms/editor/creating-a-form/images/exampleConditions.png deleted file mode 100644 index 47720a8a894..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/exampleConditions.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/exampleFrontend-v14.png b/14/umbraco-forms/editor/creating-a-form/images/exampleFrontend-v14.png deleted file mode 100644 index 3a2c1de6c25..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/exampleFrontend-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/exampleFrontend-v9.png b/14/umbraco-forms/editor/creating-a-form/images/exampleFrontend-v9.png deleted file mode 100644 index 1d31ab79570..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/exampleFrontend-v9.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/exampleFrontend.png b/14/umbraco-forms/editor/creating-a-form/images/exampleFrontend.png deleted file mode 100644 index e400cd61780..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/exampleFrontend.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/form-info-V14.png b/14/umbraco-forms/editor/creating-a-form/images/form-info-V14.png deleted file mode 100644 index 89076d66f75..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/form-info-V14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/form-info-general-v14.png b/14/umbraco-forms/editor/creating-a-form/images/form-info-general-v14.png deleted file mode 100644 index 16766b38d54..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/form-info-general-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/form-info-general.png b/14/umbraco-forms/editor/creating-a-form/images/form-info-general.png deleted file mode 100644 index 00f228f6e6a..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/form-info-general.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/form-info-references-V14.png b/14/umbraco-forms/editor/creating-a-form/images/form-info-references-V14.png deleted file mode 100644 index 23e111fc50e..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/form-info-references-V14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/form-info-relations.png b/14/umbraco-forms/editor/creating-a-form/images/form-info-relations.png deleted file mode 100644 index 03eac1b8ec5..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/form-info-relations.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/form-info.png b/14/umbraco-forms/editor/creating-a-form/images/form-info.png deleted file mode 100644 index f0f8e36d94b..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/form-info.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/forms-folder-name-v14.png b/14/umbraco-forms/editor/creating-a-form/images/forms-folder-name-v14.png deleted file mode 100644 index 8b166a4fefc..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/forms-folder-name-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/frontend-email.png b/14/umbraco-forms/editor/creating-a-form/images/frontend-email.png deleted file mode 100644 index 1a30fbcdc0c..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/frontend-email.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/frontend-phone.png b/14/umbraco-forms/editor/creating-a-form/images/frontend-phone.png deleted file mode 100644 index 662b35cec7a..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/frontend-phone.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/import-form.png b/14/umbraco-forms/editor/creating-a-form/images/import-form.png deleted file mode 100644 index ad5b8c6c180..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/import-form.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/move-form-in-folder-v14.png b/14/umbraco-forms/editor/creating-a-form/images/move-form-in-folder-v14.png deleted file mode 100644 index dff1e769bfa..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/move-form-in-folder-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/phone-conditions-v14.png b/14/umbraco-forms/editor/creating-a-form/images/phone-conditions-v14.png deleted file mode 100644 index 1e2425cd03e..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/phone-conditions-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/creating-a-form/images/phone.png b/14/umbraco-forms/editor/creating-a-form/images/phone.png deleted file mode 100644 index 77cc3f9a414..00000000000 Binary files a/14/umbraco-forms/editor/creating-a-form/images/phone.png and /dev/null differ diff --git a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/README.md b/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/README.md deleted file mode 100644 index 5592c0ea01d..00000000000 --- a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/README.md +++ /dev/null @@ -1,86 +0,0 @@ -# Defining And Attaching Prevalue Sources - -Prevalue sources are a way to pre-define and/or retrieve a list of items from a certain source. They can be added in any field types that include some kind of list like Dropdown and Multiple/Single Choice lists. - -## Setting up a Prevalue Source - -Prevalue sources can be managed in the **Prevalue sources** folder available in the **Forms** section. - -![Prevalue source tree](images/prevaluesourcetree-v14.png) - -To set a prevalue source: - -1. Go to the **Forms** section. -2. Click **...** next to the **Prevalue Sources** folder. -3. Click **Create**. -4. The **Choose prevalue source type** pane opens in the right-side of the editor. -5. Select the type of prevalue source. For more information on the different default types, see the [Overview of the Prevalue Source Types](prevalue-source-types.md) article. - - ![Choose type](images/choosetype-v14.png.png) - -### Configuring the Prevalue Source - -Depending on the **prevalue source type** you choose, you'll need to provide some additional settings. For this article, we will select **Get values from textfile**. - -1. Select **Get values from textfile** from the **Choose prevalue source type** pane. - ![Type settings](images/typesettings-v14.png) - -2. Enter a Name for the prevalue source type. Let's call it *My Prevalue Source*. -3. Now, create a file containing the list to use as prevalues. For example: a `.txt` file containing the following values: - - ```cs - example value 1 - example value 2 - example value 3 - example value 4 - example value 5 - ``` - -4. Select **Click to upload** in the **Text File**. -5. Choose the text file you created. Click **Open**. -6. Select your preferred **Cache option** for caching the list of prevalues when rendering in a form. -7. Click **Save**. - - ![Prevalue source settings](images/preview-v14.png) - -If you would like to have different values presented to your users from the value stored, you can provide two values per line, separated with a vertical bar (|), e.g.: - -``` -1|example value 1 -2|example value 2 -3|example value 3 -4|example value 4 -5|example value 5 -``` - -In this case the user would pick from a list showing the captions, but the single integer values would be stored with the record. - -This can be useful if the recorded entries are used in any subsequent workflows or business processes, where particular values, that aren't appropriate for the user to select from, are required. - -### Defining Cache Options for the Prevalue Source - -Sometimes retrieving the list of options for a prevalue source can be an expensive operation. If the source depends on data from external systems, it could be that the list changes regularly or rarely. - -Given the variation here, we allow you to select an appropriate level of caching for the list of options. - -You can choose between: - -- `No Caching` - no caching will be applied and the list of options will be retrieved from source on every request. You will likely only want to choose this option if the information changes frequently and it's important that the latest is presented to website visitors. -- `Cache For Specified Time` - the list will be cached for the period of time provided. -- `Cache With No Expiry` - the list will be cached on first request and not retrieved again until either the prevalue source is edited or the website is restarted. This ismost appropriate to use for information held within the prevalue source data itself (such as when uploading a text file). - -![Prevalue cache options](images/prevalue-cache-options-v14.png) - -## Attaching a Prevalue Source to a Field - -Once a prevalue source has been created, it can be used while building Forms in the Forms designer. - -**Example:** Let's add a Multiple Choice field type in our Form. - -If there is at least one prevalue source defined in the project, the Prevalues source will contain a dropdown from where you can choose the predefined value. - -![Prevalue source](images/FieldPrevalueSource-v16.png) - -Once you have selected the prevalue source, the values are rendered in the Forms designer from the attached source. - -![Preview](images/fieldpreview.png) diff --git a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/FieldPrevalueSource-v14.png b/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/FieldPrevalueSource-v14.png deleted file mode 100644 index fa445776bcf..00000000000 Binary files a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/FieldPrevalueSource-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/FieldPrevalueSource-v16.png b/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/FieldPrevalueSource-v16.png deleted file mode 100644 index 99840e59d7a..00000000000 Binary files a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/FieldPrevalueSource-v16.png and /dev/null differ diff --git a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/FieldPrevalueSource.png b/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/FieldPrevalueSource.png deleted file mode 100644 index c1293a4a9ae..00000000000 Binary files a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/FieldPrevalueSource.png and /dev/null differ diff --git a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/Prevalues-with-caption.png b/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/Prevalues-with-caption.png deleted file mode 100644 index 7e0a79b21b1..00000000000 Binary files a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/Prevalues-with-caption.png and /dev/null differ diff --git a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/SQLdatabase-v14.png b/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/SQLdatabase-v14.png deleted file mode 100644 index e5793f6bfe6..00000000000 Binary files a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/SQLdatabase-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/SQLdatabase-v16.png b/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/SQLdatabase-v16.png deleted file mode 100644 index 7cfdf02ae49..00000000000 Binary files a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/SQLdatabase-v16.png and /dev/null differ diff --git a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/choosetype-v14.png b/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/choosetype-v14.png deleted file mode 100644 index 5fe77bae083..00000000000 Binary files a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/choosetype-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/choosetype.png b/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/choosetype.png deleted file mode 100644 index 3ed6b97bb94..00000000000 Binary files a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/choosetype.png and /dev/null differ diff --git a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/datatype-prevalues-v14.png b/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/datatype-prevalues-v14.png deleted file mode 100644 index 9f350a72448..00000000000 Binary files a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/datatype-prevalues-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/datatype-prevalues.png b/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/datatype-prevalues.png deleted file mode 100644 index 4e0dd7513ce..00000000000 Binary files a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/datatype-prevalues.png and /dev/null differ diff --git a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/docs-from-xpath.png b/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/docs-from-xpath.png deleted file mode 100644 index 05a0b020f3f..00000000000 Binary files a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/docs-from-xpath.png and /dev/null differ diff --git a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/fieldpreview.png b/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/fieldpreview.png deleted file mode 100644 index ba1e9aeac2f..00000000000 Binary files a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/fieldpreview.png and /dev/null differ diff --git a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/prevalue-cache-options-v14.png b/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/prevalue-cache-options-v14.png deleted file mode 100644 index 52222907264..00000000000 Binary files a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/prevalue-cache-options-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/prevalue-cache-options.png b/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/prevalue-cache-options.png deleted file mode 100644 index d030dd94fd4..00000000000 Binary files a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/prevalue-cache-options.png and /dev/null differ diff --git a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/prevaluesourcetree-v14.png b/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/prevaluesourcetree-v14.png deleted file mode 100644 index 23ae81e8c86..00000000000 Binary files a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/prevaluesourcetree-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/prevaluesourcetree.png b/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/prevaluesourcetree.png deleted file mode 100644 index bb90fa4e7d3..00000000000 Binary files a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/prevaluesourcetree.png and /dev/null differ diff --git a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/preview-v14.png b/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/preview-v14.png deleted file mode 100644 index 94d165ae93b..00000000000 Binary files a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/preview-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/preview.png b/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/preview.png deleted file mode 100644 index 3fca5d00d48..00000000000 Binary files a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/preview.png and /dev/null differ diff --git a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/typesettings-v14.png b/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/typesettings-v14.png deleted file mode 100644 index aa1c171d39c..00000000000 Binary files a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/typesettings-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/typesettings.png b/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/typesettings.png deleted file mode 100644 index 8281c10fab2..00000000000 Binary files a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/typesettings.png and /dev/null differ diff --git a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/umbraco-documents-v14.png b/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/umbraco-documents-v14.png deleted file mode 100644 index 940c3a9ecaf..00000000000 Binary files a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/umbraco-documents-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/umbraco-documents-v16.png b/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/umbraco-documents-v16.png deleted file mode 100644 index 98135a6a5a9..00000000000 Binary files a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/umbraco-documents-v16.png and /dev/null differ diff --git a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/umbraco-documents-v9.png b/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/umbraco-documents-v9.png deleted file mode 100644 index 2f769c15c47..00000000000 Binary files a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/umbraco-documents-v9.png and /dev/null differ diff --git a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/umbraco-documents.png b/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/umbraco-documents.png deleted file mode 100644 index ec43727e01e..00000000000 Binary files a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/images/umbraco-documents.png and /dev/null differ diff --git a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/prevalue-source-types.md b/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/prevalue-source-types.md deleted file mode 100644 index 1573b5361c7..00000000000 --- a/14/umbraco-forms/editor/defining-and-attaching-prevaluesources/prevalue-source-types.md +++ /dev/null @@ -1,50 +0,0 @@ -# Prevalue Source Types Overview - -There are some default prevalue source types that can be used. In this article, we will give a quick overview of them: - -## Get values from textfile - -Upload a textfile that contains the prevalues. Each prevalue should have its own line in the file. Once the file has been uploaded, you can find it in `~/wwwroot/App_Data/UmbracoForms/Data/PreValueTextFiles/{GUID}` where the `{GUID}`is replaced with the pre-value ID. - -![Get values from textfile](images/preview-v14.png) - -## Umbraco Documents - -Allows you to use content nodes from a specific source as prevalues. Configure the following options in the **Details** section: - -* Define the root node by either: - * Selecting the type of item the picker should target such as **Content**, **Media**, or **Members**, or - * Specifying a dynamic root. -* Enable **Use current page as root** instead of choosing a specific root node. _Preview is not available when this setting is enabled._ -* Choose a specific **Document type**, if the selected root node contains a different Document Type. -* Select the **Value field** to define the value stored for the prevalue. -* Select the **Caption field** to define the label shown in the list. -* Enable **List all Descendants** of the selected root node to include all child nodes beneath the root. -* Select **Order by** from the drop-down list to display how the prevalue list is sorted. -* Select your preferred **Cache option** for caching the list of prevalues when rendering in a form. - -![Umbraco Documents](images/umbraco-documents-v16.png) - -## SQL Database - -Connect to a OleDB compatible database table and construct a prevalue source from it. Once selected, it will be editable from the Forms interface. - -Configure the following options in the **Details** section: - -* Connection string (either choose one from your web.config or add another from a textfield). -* Connection String from configuration -* Table Name -* Key Column -* Value Column -* Caption Column -* Select your preferred **Cache option** for caching the list of prevalues when rendering in a form. - -![SQL Database](images/SQLdatabase-v16.png) - -## Umbraco Data Type Prevalues - -Choose an Umbraco Data Type to use its configured prevalue collection. - -In the example below, the prevalue collection from a Data Type called `Home - Font - Radio button` is used: - -![Data Type prevalues](images/datatype-prevalues-v14.png) diff --git a/14/umbraco-forms/editor/images/BulkActions.png b/14/umbraco-forms/editor/images/BulkActions.png deleted file mode 100644 index dfb879546e9..00000000000 Binary files a/14/umbraco-forms/editor/images/BulkActions.png and /dev/null differ diff --git a/14/umbraco-forms/editor/images/EntriesViewer.png b/14/umbraco-forms/editor/images/EntriesViewer.png deleted file mode 100644 index fe077a4161f..00000000000 Binary files a/14/umbraco-forms/editor/images/EntriesViewer.png and /dev/null differ diff --git a/14/umbraco-forms/editor/images/Export-v14.png b/14/umbraco-forms/editor/images/Export-v14.png deleted file mode 100644 index efc9bb7686b..00000000000 Binary files a/14/umbraco-forms/editor/images/Export-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/images/Export.png b/14/umbraco-forms/editor/images/Export.png deleted file mode 100644 index 9ba199defea..00000000000 Binary files a/14/umbraco-forms/editor/images/Export.png and /dev/null differ diff --git a/14/umbraco-forms/editor/images/ExportAllDialog-v14.png b/14/umbraco-forms/editor/images/ExportAllDialog-v14.png deleted file mode 100644 index 2d7dd5a549f..00000000000 Binary files a/14/umbraco-forms/editor/images/ExportAllDialog-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/images/ExportAllDialog.png b/14/umbraco-forms/editor/images/ExportAllDialog.png deleted file mode 100644 index 09bf4519314..00000000000 Binary files a/14/umbraco-forms/editor/images/ExportAllDialog.png and /dev/null differ diff --git a/14/umbraco-forms/editor/images/Filter.png b/14/umbraco-forms/editor/images/Filter.png deleted file mode 100644 index 36dbbd65dd6..00000000000 Binary files a/14/umbraco-forms/editor/images/Filter.png and /dev/null differ diff --git a/14/umbraco-forms/editor/images/entry-details-v14.png b/14/umbraco-forms/editor/images/entry-details-v14.png deleted file mode 100644 index 77e47c96500..00000000000 Binary files a/14/umbraco-forms/editor/images/entry-details-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/images/tree-v14.png b/14/umbraco-forms/editor/images/tree-v14.png deleted file mode 100644 index c472e109511..00000000000 Binary files a/14/umbraco-forms/editor/images/tree-v14.png and /dev/null differ diff --git a/14/umbraco-forms/editor/images/tree.png b/14/umbraco-forms/editor/images/tree.png deleted file mode 100644 index 37918780188..00000000000 Binary files a/14/umbraco-forms/editor/images/tree.png and /dev/null differ diff --git a/14/umbraco-forms/editor/viewing-and-exporting-entries.md b/14/umbraco-forms/editor/viewing-and-exporting-entries.md deleted file mode 100644 index 8d873f1548e..00000000000 --- a/14/umbraco-forms/editor/viewing-and-exporting-entries.md +++ /dev/null @@ -1,60 +0,0 @@ -# Viewing And Exporting Entries - -To view the Entries for each Form, go to the Form and click on the **Entries** tab. - -![Tree](images/tree-v14.png) - -## Video overview - -{% embed url="https://youtu.be/vUQpX3wqDrs" %} -Watch this video to learn how to manage entries submitted via Umbraco Forms. -{% endembed %} - -## Entries Overview - -When accessing the Entries viewer, you will be able to see all the entries submitted via the Form. - -![Entries viewer](images/tree-v14.png) - -### Viewing the Entries - -By default, the list is filtered to show entries only from the past month. If you want to change the date range, pick the appropriate time period from the date picker. You can also filter the entries by specific words using the Search field on the left. - -Click **Entry details** on each record in the list to open the full set of information recorded for the form entry. Clicking on the entry record displays the **Clear** and **Delete** buttons. - -![Filter](images/entry-details-v14.png) - -### Editing the Entries - -If configured via the permissions model and supported by the version of Umbraco Forms you are running, entries may be editable via the backoffice. If available, click the _Edit_ button to switch the read-only view of an entry to an editable one and _Save_ to record the changes. An audit trail will show who and when updates on the entry were made. - -Validation will operate as is configured for the form in terms of mandatory fields and those that must match a particular pattern. Conditional display of fields is not supported. - -## Exporting Entries - -To export all the entries from your Form: - -1. Go to the **Forms** section. -2. Navigate to the Form **Entries** you wish to export. -3. Click **Export**. - - ![Export Entries](images/Export-v14.png) - -4. The Export dialog opens. Choose a format such as **Excel File** to export the Form records to. - - ![Export dialog](images/ExportAllDialog-v14.png) -5. Click **Export**. -6. Click **Save**. - -If you have fields that allow the user to upload files within your form, you will also have the option to download a zip file containing these files. You can either download the files in the structure that they are stored on the web server's disk. Or you can download them organised by entry, so it's easier to match up the entry listed in the spreadsheet download with the uploaded file(s). - -## Record Actions - -When selecting entries, it is possible to execute different actions. To select an entry, click anywhere on the entry. - -![Record bulk actions](images/entry-details-v14.png) - -Select at least 1 record to see the available actions. By default, there are 2 possible actions: - -* Clear -* Delete diff --git a/14/umbraco-forms/installation/images/Forms_Section_Backoffice.png b/14/umbraco-forms/installation/images/Forms_Section_Backoffice.png deleted file mode 100644 index 9ed7bf7f936..00000000000 Binary files a/14/umbraco-forms/installation/images/Forms_Section_Backoffice.png and /dev/null differ diff --git a/14/umbraco-forms/installation/images/InstallingForms.gif b/14/umbraco-forms/installation/images/InstallingForms.gif deleted file mode 100644 index 59643bd9c02..00000000000 Binary files a/14/umbraco-forms/installation/images/InstallingForms.gif and /dev/null differ diff --git a/14/umbraco-forms/installation/images/Manage_packages.png b/14/umbraco-forms/installation/images/Manage_packages.png deleted file mode 100644 index 53774af554b..00000000000 Binary files a/14/umbraco-forms/installation/images/Manage_packages.png and /dev/null differ diff --git a/14/umbraco-forms/installation/images/Manage_packages_v10.png b/14/umbraco-forms/installation/images/Manage_packages_v10.png deleted file mode 100644 index c47a0ecf652..00000000000 Binary files a/14/umbraco-forms/installation/images/Manage_packages_v10.png and /dev/null differ diff --git a/14/umbraco-forms/installation/images/Manage_packages_v14.png b/14/umbraco-forms/installation/images/Manage_packages_v14.png deleted file mode 100644 index dd8f92cf16a..00000000000 Binary files a/14/umbraco-forms/installation/images/Manage_packages_v14.png and /dev/null differ diff --git a/14/umbraco-forms/installation/images/UpgradeAvailable.png b/14/umbraco-forms/installation/images/UpgradeAvailable.png deleted file mode 100644 index 6a24cc30737..00000000000 Binary files a/14/umbraco-forms/installation/images/UpgradeAvailable.png and /dev/null differ diff --git a/14/umbraco-forms/installation/images/UpgradeNow.png b/14/umbraco-forms/installation/images/UpgradeNow.png deleted file mode 100644 index 92a5d752e00..00000000000 Binary files a/14/umbraco-forms/installation/images/UpgradeNow.png and /dev/null differ diff --git a/14/umbraco-forms/installation/images/UpgradeProgress.png b/14/umbraco-forms/installation/images/UpgradeProgress.png deleted file mode 100644 index 3d092da8972..00000000000 Binary files a/14/umbraco-forms/installation/images/UpgradeProgress.png and /dev/null differ diff --git a/14/umbraco-forms/installation/images/buy-license.png b/14/umbraco-forms/installation/images/buy-license.png deleted file mode 100644 index 29655a7bf20..00000000000 Binary files a/14/umbraco-forms/installation/images/buy-license.png and /dev/null differ diff --git a/14/umbraco-forms/installation/images/image.png b/14/umbraco-forms/installation/images/image.png deleted file mode 100644 index 002dbcbe5c8..00000000000 Binary files a/14/umbraco-forms/installation/images/image.png and /dev/null differ diff --git a/14/umbraco-forms/installation/images/start-with-forms-v14.png b/14/umbraco-forms/installation/images/start-with-forms-v14.png deleted file mode 100644 index a17420f6d3d..00000000000 Binary files a/14/umbraco-forms/installation/images/start-with-forms-v14.png and /dev/null differ diff --git a/14/umbraco-forms/installation/images/start-with-forms-v9.png b/14/umbraco-forms/installation/images/start-with-forms-v9.png deleted file mode 100644 index e8ff764e518..00000000000 Binary files a/14/umbraco-forms/installation/images/start-with-forms-v9.png and /dev/null differ diff --git a/14/umbraco-forms/installation/images/start-with-forms.png b/14/umbraco-forms/installation/images/start-with-forms.png deleted file mode 100644 index eafcd021e58..00000000000 Binary files a/14/umbraco-forms/installation/images/start-with-forms.png and /dev/null differ diff --git a/14/umbraco-forms/installation/install.md b/14/umbraco-forms/installation/install.md deleted file mode 100644 index 3b65659a255..00000000000 --- a/14/umbraco-forms/installation/install.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -description: Installing Umbraco Forms ---- - -# Installing Umbraco Forms - -Umbraco contains the **Forms** section, by default. You will see a similar interface, when you click on the **Forms** section in the **Umbraco Backoffice**. - -![Form section in backoffice](images/Forms\_Section\_Backoffice.png) - -## Video Tutorial - -{% embed url="https://www.youtube.com/watch?v=3Aojbp_1MPc" %} - -To install the Umbraco Forms package (**Umbraco.Forms**), follow these steps: - -1. Identify the Umbraco CMS version your project is running. -2. Find a compatible version of Umbraco Forms that matches your Umbraco CMS version. A list of Umbraco Forms versions can be found on [nuget.org](https://www.nuget.org/packages/Umbraco.Forms#versions-body-tab). -3. Run the following command on a command prompt of your choice, replacing `` with the appropriate version identified above: - - ```cs - dotnet add package Umbraco.Forms --version - ``` -4. Restart the web application using the following command: - - ```cs - dotnet run - ``` - -## Start Building Forms - -Once the installation is successful, you will see a similar screen in the **Forms** section: - -![Create form](images/start-with-forms-v14.png) - -## Using Forms - -For details on using Forms, see the [Editor Documentation](../editor/creating-a-form/README.md). diff --git a/14/umbraco-forms/installation/the-licensing-model.md b/14/umbraco-forms/installation/the-licensing-model.md deleted file mode 100644 index a96377b2963..00000000000 --- a/14/umbraco-forms/installation/the-licensing-model.md +++ /dev/null @@ -1,132 +0,0 @@ -# Licensing - -Umbraco Forms is a commercial product. You have a 14-day free trial to try out the product. After your trial expires, you'll need to have a **valid license** to keep using the product on your site. - -## How does it work? - -Licenses are sold per domain and will also work on all subdomains. With every license, you will be able to configure two development/testing domains. - -{% hint style="info" %} -The licenses are not bound to a specific product version. They will work for all versions of the related product, but version 17+ will only be available through a subscription based license (see [announcement](https://github.com/umbraco/Announcements/issues/25)). -{% endhint %} - -Let's say that you have a license configured for your domain, `mysite.com`, and you've configured two development domains, `devdomain.com` and `devdomain2.com`. - -The license will cover the following domains: - -* `localhost` -* `*.mysite.com` -* `www.mysite.com` -* `mysite.com.local` -* `devdomain.com` -* `www.devdomain.com` -* `devdomain2.com` -* `www.devdomain2.com` - -{% hint style="info" %} -You can have only 1 license per Umbraco installation. -{% endhint %} - -## What does a license cover? - -There are a few differences as to what the licenses cover: - -* A single license covers the installation of Umbraco Forms in 1 production domain, as well as in 2 development domains. -* The production domain includes **all subdomains** (e.g. `*.mysite.com`), as well as the `.local` extension (e.g. `mysite.com.local`). -* The development domains work with or without the `www` subdomain. -* The license allows for an unlimited number of forms. -* The license also includes `localhost` as a valid domain. - -{% hint style="info" %} -If you have multiple domains pointing at the same installation, you have the option to purchase and [add **additional domains**](the-licensing-model.md#add-additional-domains) to your license. - -Each additional domain includes 1 live domain and 2 development/testing domains. - -This is an add-on domain for existing licenses. Refunds will not be given for this product. -{% endhint %} - -## Configuring your license - -You can look at the pricing, features, and purchase the license on the [Umbraco Forms](https://umbraco.com/products/add-ons/forms/) page. - -When you've bought a license you need to configure it with your domains. You can either configure your license right away or you can do it later by visiting your account on Umbraco.com. - -1. Login to your account at [shop.umbraco.com](https://shop.umbraco.com). -2. Navigate to the **Manage Licenses** section. -3. Locate your unconfigured Forms license and choose **Configure / Add domain**. -4. Define the primary as well as up to two development domains for which the license will be used. - -### Add additional domains - -Once you have a configured Umbraco Forms license, you can add additional domains. This is relevant if you need your forms to be available on multiple public domains. - -1. Login to your account at [shop.umbraco.com](https://shop.umbraco.com). -2. Navigate to the **Manage Licenses** section. -3. Locate your configured Forms license. -4. Choose **Configure / Add domain**. - -
- -5. Select **Click here to buy** at the bottom of the configuration page. -6. Configure the additional domain after completing the purchase, or do it later via your account. - -### Reconfiguration of domains - -Once a license has been configured with the domains, it is not possible to reconfigure them. An exception is when there is a mistake in the domain URL. -As reconfiguration is not possible, you will either need to purchase an additional domain or a [new license](https://umbraco.com/products/umbraco-forms/). - -## Installing your license - -Once you've configured your license with the correct domains, you are ready to install the license on your Umbraco installation. - -1. Download your license from your Umbraco.com account - this will give you a `.lic` file -2. Place the file in the `/umbraco/Licenses` directory in your Umbraco installation - -The `.lic` file must be placed in the `/umbraco/Licenses` directory to be registered by Umbraco Forms. If the file isn't placed correctly, the application will automatically switch to trial mode. - -### Multiple license files - -You can install multiple Umbraco Forms license files without merging them. Place each license file in the `/umbraco/Licenses` directory (or an alternative location). Each file should begin with `umbracoForms`, for example, `umbracoForms.example1.lic` and `umbracoForms.example2.lic`. This setup allows your installation to recognize multiple licensed domains. - -### Alternative license location - -If you can't include the license file in the `/umbraco/Licenses` directory for any reason, it is possible to configure an alternative location for the file. - -It can be configured in the Umbraco installation's `appSettings.json` file by adding the following configuration: - -```json -{ - "Umbraco": { - "Licensing": { - "Directory": "~/custom-licenses-folder/" - } - } -} -``` - -The value contains the path of your custom license directory relative to the root of your Umbraco installation. - -{% hint style="warning" %} -This will also change the location for other Umbraco-related licenses in this project. -{% endhint %} - -## Federal Information Processing Standards (FIPS) Compliant Environments - -The algorithm used to decrypt Forms licenses is not supported on locked down FIPS compliant environments, such as those used in the defense industry. - -If you are in this situation and unable to resolve it via configuration of the environment, please reach out to Umbraco support. - -We have the possibility of generating and providing Forms licenses using alternate algorithms. - -{% hint style="info" %} -You can use this configuration if you reference `Umbraco.Licensing` version `13.0.1` or higher. -{% endhint %} - -Apply the following configuration with the appropriate algorithm - `DES` (the default), `TripleDES`, or `AES`: - -```json - "Umbraco": { - "Licensing": { - "LicenseEncodeAndDecodeAlgorithm": "DES|TripleDES|AES" - }, -`````` \ No newline at end of file diff --git a/14/umbraco-forms/legacy-documentation.md b/14/umbraco-forms/legacy-documentation.md deleted file mode 100644 index 50cadab40d4..00000000000 --- a/14/umbraco-forms/legacy-documentation.md +++ /dev/null @@ -1,7 +0,0 @@ -# Legacy Documentation - -This documentation platform covers only major versions of the Umbraco Forms since Umbraco 9+. If you are using an older version of Umbraco Forms, you will need to go elsewhere. - -The documentation for Umbraco 7 and 8 lives on [our.umbraco.com](https://our.umbraco.com/documentation/Add-ons/). - -
Umbraco 11 Documentationhttps://github.com/umbraco/UmbracoDocs/tree/umbraco-eol-versions/11/umbraco-forms
Umbraco 8 Documentationhttps://our.umbraco.com/documentation/Add-ons/UmbracoForms/
diff --git a/14/umbraco-forms/release-notes.md b/14/umbraco-forms/release-notes.md deleted file mode 100644 index 82994e1ad3e..00000000000 --- a/14/umbraco-forms/release-notes.md +++ /dev/null @@ -1,202 +0,0 @@ ---- -description: Get an overview of the things changed and fixed in each version of Umbraco Forms. ---- - -# Release notes - -In this section, we have summarized the changes to Umbraco Forms released in each version. Each version is presented with a link to the [Forms issue tracker](https://github.com/umbraco/Umbraco.Forms.Issues/issues) showing a list of issues resolved in the release. We also link to the individual issues themselves from the detail. - -If there are any breaking changes or other issues to be aware of when upgrading they are also noted here. - -{% hint style="info" %} -If you are upgrading to a new major version, you can find information about the breaking changes in the [Version Specific Upgrade Notes](upgrading/version-specific.md) article. -{% endhint %} - -## Release history - -This section contains the release notes for Umbraco Forms 14 including all changes for this version. - -### [14.2.3](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.2.3) (December 5th 2024) - -* Fixed regression introduced in 14.2.1 that caused issues for custom field types overriding the `ProcessSubmittedValue` method [#1328](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1328). - -### [14.2.2](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.2.2) (November 28th 2024) - -* Fixed issue with case sensitive checkbox conditions across multi-page forms [#1325](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1325). -* Fixed Forms dashboard form title and icon alignment. - -### [14.2.1](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.2.1) (November 21st 2024) - -* Fixed issues with multi-page forms used in conjunction with a `FormPrePopulateNotification` handler. File uploads and multi-value fields like checkbox lists now function correctly [#1317](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1317) [#1320](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1320). -* Added a couple of missing translation keys [#1316](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1316) [#1319](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1319). -* Rendered file upload previews in the backoffice. -* Fixed issue with saving the "Hide field validation labels" value when editing form settings. -* Fixed issue with selection of Document Type on the "Save as Umbraco node" workflow type. -* Used correct labels for conditions when used on fields, fieldsets, pages or workflows [#1323](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1323). - -### [14.2.0](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.2.0) (November 7th 2024) - -* All items detailed under release candidates for 14.2.0. -* Fixed issue with validation for invalid file extension on form submissions via the API [#1310](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1310). - -### [14.2.0-rc2](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.2.0) **November 3rd 2024** - -* Updated dependency on Umbraco CMS to 14.3.0. -* Added a replacement for the AngularJS [block list label filter we provide for Forms 13](../../13/umbraco-forms/developer/blocklistfilters.md). The new implementations use [Umbraco Flavored Markdown (UFM)](https://docs.umbraco.com/umbraco-cms/reference/umbraco-flavored-markdown) and are [documented here](./developer/blocklistfilters.md). - -### [14.2.0-rc1](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.2.0) **October 25th 2024** - -#### Multi-step forms - -The 14.2 release of Forms contains features that can improve the user experience of completing multi-page forms. - -We have added the option for [editors to choose to display paging details on the forms](./editor/creating-a-form/form-settings.md#multi-page-forms). This will allow those completing forms to get a better understanding of progress as well as see details of the pages still to be completed. [#281](https://github.com/umbraco/Umbraco.Forms.Issues/issues/281) [#648](https://github.com/umbraco/Umbraco.Forms.Issues/issues/648). - -These options are enabled and configured by editors in the Forms settings section on a per-form basis. We also provide a [configuration-based toggle for the feature as a whole](./developer/configuration/README.md#enablemultipageformsettings). In this way, editors can be given access to use the feature only once the styling or theme is prepared. - -#### Form picker enhancements - -Another improvement is found in the [form picker property editors](./developer/property-editors.md). We now support restriction of which forms can be selected by folder rather than only by individual forms. - -A second "form details picker" is also available, allowing editors the option of selecting the form, theme and redirect via a single property editor. - -#### Ship themes in Razor Class Libraries - -Forms ships it's themes and email templates as part of a razor class library for ease of distribution. With this release we make that feature [available to your own custom themes and templates](./developer/themes.md#shipping-themes-in-a-razor-class-library) (or those created by package developers) [#795](https://github.com/umbraco/Umbraco.Forms.Issues/issues/795). - -#### Date picker field type - -We have made a couple of updates to the Date Picker field type. The format for the field can now be provided in configuration [#1276](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1276). And you can now override and localize the aria label provided for assistive technologies such as screen readers [#1082](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1082). - -#### Umbraco documents prevalue source type - -When creating a prevalue source based on Umbraco documents, you can now select custom properties for the value or caption. Previously you had a choice of the content item's `Id`, `Key` or `Name`. We've extended this to allow the selection of any properties defined on the selected Document Type [#1195](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1195). - -#### Finer grained entries permissions - -To allow finer control over editor permissions, we have introduced a "delete entries" setting for users and user groups. Thus you can now give editors explicit permissions to view, edit, or delete entries [#1303](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1303). - -#### Backoffice localization - -Finally thanks to a kind contribution from [Erik-Jan Westendorp](https://github.com/erikjanwestendorp) the backoffice is now translated into Dutch [#1264](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1264). - -#### Other - -Other bug fixes included in the release: - -* Reverted entry list to display most recent first. -* Fixed issue with display of prevalue captions in the entry list. -* Fixed issue on restoring values of checkbox and radio lists when navigating backward on multi-page forms. -* Fixed issue with single checkbox triggering a condition on a field on a subsequent page [#1304](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1304). -* Improved cross-platform check when exporting to Excel. - -### [14.1.5](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.1.5) (October 3rd 2024) - -* Handled "chunked" authentication cookie in protection of file uploads saved in the media file system [#11](https://github.com/umbraco/Umbraco.Forms.Issues/issues/11#issuecomment-2376788751). -* Ensured field list for condition rules updates as new fields are added to the form [#1301](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1301). -* Resolved issues with requesting management API endpoints for forms from content without access to the Forms section [#1244](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1244). -* Fixed button labels on form copy dialog. -* Fixed localization of SQL prevalue source labels. - -### [14.1.4](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F13.2.4) (September 26th 2024) - -* Fixed regression in 14.1.2 that caused validation to fire on the wrong form when multiple forms are hosted on a single page [#1297](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1297). -* Fixed issue with line breaks in form submissions breaking the entries view [#1296](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1296). - -### [14.1.3](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.1.3) (September 19th 2024) - -* Fixed regression in 13.2.0 that prevented a form submission from saving if a workflow approved the entry [#1293](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1293). -* Added file name validation to file uploads, rejecting files with invalid colon characters [#1295](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1295). - -### [14.1.2](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.1.2) (September 12th 2024) - -* Added configurable field level rendering of reCAPTCHA 3 validation result [#1277](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1277). -* Fixed validate and submit script to handle additional markup around submit buttons [#1280](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1280). -* Fixed incorrect concatenation of field CSS classes [#1284](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1284). -* Added server-side validation of configured maximum length for short and long answer fields. -* Restored provision of field values in HTTP headers in Post as XML workflow. -* Fixed issue with recording of form submissions in custom Examine indexes [#1282](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1282). -* Added ability to retrieve "slim" workflow entities from services [#1283](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1283). -* Fixed the following backoffice user interface issues [#1291](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1291), [#1290](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1290), [#1288](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1288), [#1287](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1287), [#1286](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1286), [#1278](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1278) and [#1275](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1275). - -### [14.1.1](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.1.1) (August 6th 2024) - -* Fixed issues with entries export for Windows installations without access to a component necessary for auto-fit of Excel columns [#1259](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1259). -* Resolved intermittent issues with display of entries list [#1256](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1256). -* Restored access to setting option for sensitive data handling in workflows [#1262](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1262). -* Fixed validation on saving a form without a name [#1263](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1263). -* Fixed fallback of the localized user interface for English (GB) to English (US) [#1267](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1267). -* Fixed issue with form block rendering from rich text content [#1268](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1268). -* Restored the `ValueAsString` extension method on `Record`. - -### [14.1.0](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.1.0) (July 23rd 2024) - -{% hint style="warning" %} -The 14.1.0 release contains minor changes to the mark-up in the following Razor files shipped with the product: `Form.cshtml`, `FieldType.RadioButtonList.cshtml`, and `FieldType.CheckBoxList.cshtml`. These changes were made to resolve issues [#1220](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1220) and [#1218](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1218). - -Please ensure to check the rendering of these features on website forms after the upgrade. If you need to view the files to compare changes, you can download and view the [latest](https://our.umbraco.com/FileDownload?id=24343) and [previous](https://our.umbraco.com/FileDownload?id=24339) versions. -{% endhint %} - -* All issues from earlier 14.1 release candidates. -* Ensured prevalues can be retrieved outside of an HTTP request context when they depend on a static root node [#1258](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1258). - -### [14.1.0-rc2](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.1.0) (July 18th 2024) - -* Added configuration option `AllowedFileUploadExtensions` to provide an "allow list" of extensions that will be accepted in file uploads via forms [#1252](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1252). - * Read more about this and related settings [here](developer/configuration/#allowedfileuploadextensions). -* Allowed users without sensitive data permissions to set, but not remove, the sensitive flag on a form field [#1233](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1233). -* Ordered select list of prevalue sources when defining prevalues for a form field. -* Limited the field preview for a field containing prevalues. -* Improved support for editing large, multi-page forms by retaining scroll position between views and adding a "jump to page" option [#1243](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1243). - -### [14.1.0-rc1](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.1.0) (July 9th 2024) - -* Added setting option for single and multiple choice fields to allow for vertical or horizontal display [#1218](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1218) -* Updated themes such that accessibility is improved by having hidden labels remain in markup but be visually hidden [#1220](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1220). -* Added new setting type for multiple text strings [#1217](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1217) -* Added validation to prevent users defining an email workflow that allows the form's sender email to be defined as that entered by the user [#1210](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1210) -* Allowed for the provision of additional data when rendering and submitting forms. When provided it will be used as a source for ["magic string" replacements](magic-strings.md). The data will be associated with the created record and made available for custom logic and update within workflows. [#578](https://github.com/umbraco/Umbraco.Forms.Issues/issues/578) -* Added details of workflow type to edit workflow dialog [#1183](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1183) -* Allowed for use of prevalue sources that customize based on the current form or field in backoffice editing and preview [#1221](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1221) -* Ensured links to Umbraco pages within rich text fields used for emails are correctly parsed [#1208](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1208). -* Added body rich text field for send email with Razor template workflow [#1198](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1198). -* Fixed console error with blank values in the date picker field [#1241](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1241). -* Ensured placeholders are parsed for accepted entry response from the delivery API [#1238](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1238). -* Resolved issues with intermittent failures of the form entries table display [#1239](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1239). - -### [14.0.2](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.0.2) (June 11th 2024) - -* Fixed issue with upload of text file for the prevalue source based on file contents. - -### [14.0.1](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.0.1) (June 6th 2024) - -* Ensured local links are parsed when HTML fields are returned in the delivery API results for form definitions [#1227](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1227). -* Restored target used to generate local configuration schema information [#1226](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1226). -* Resolved duplicate approval occurring when the record is approved via a workflow [#1223](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1223). -* Added some missing localization keys and translations. -* Fixed description of management API on Swagger UI. -* Fixed display of specific form access list for user and group security. - -### [14.0.0](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.0.0) (May 30th 2024) - -* Compatibility with Umbraco 14 - * See full details of breaking changes under the [Version-specific Upgrade Guide](upgrading/version-specific.md). - -## Umbraco.Forms.Deploy - -### 14.1.1 (October 3rd 2024) - -* Add migrator to add missing Forms editor UI aliases - -### 14.1.0 (August 16th 2024) - -* Add check for keyed services before examining the registered services implementation type (workaround for https://github.com/dotnet/runtime/issues/95789) -* Request tree items for forms-folder entity - -### 14.0.0 (May 30th 2024) - -* Compatibility with Umbraco 14, Forms 14 and Deploy 14. - -## Legacy release notes - -You can find the release notes for versions out of support in the [Legacy documentation on GitHub](https://github.com/umbraco/UmbracoDocs/blob/umbraco-eol-versions/11/umbraco-forms/release-notes.md) and [Umbraco Forms Package page](https://our.umbraco.com/packages/developer-tools/umbraco-forms/). diff --git a/14/umbraco-forms/tutorials/creating-a-contact-form.md b/14/umbraco-forms/tutorials/creating-a-contact-form.md deleted file mode 100644 index d3a5a386a59..00000000000 --- a/14/umbraco-forms/tutorials/creating-a-contact-form.md +++ /dev/null @@ -1,300 +0,0 @@ -# Creating a Contact Form - -In this tutorial, we'll look at creating a Contact Form using Umbraco Forms. It will take you through the process of creating a Contact Form and cover all the different components involved in building the form. - -You can use a Contact Form on your website to allow a visitors to send you a message. Having a Contact Form on your website allows you to keep track of potential customer queries and possibly generate leads via email communication. - -## Video Tutorial - -{% embed url="https://www.youtube-nocookie.com/embed/l0X9DOwd6zk" %} -Creating a Contact Us Form using Umbraco Forms -{% endembed %} - -## Step 1: Configure the Document Types - -The first step in this tutorial is to configure the Document Types that will be used to show the Contact Form on your website. - -### Creating a Composition - -We'll start off by creating a Composition. A Composition is a stand-alone Document Type, that you can reuse on other Document Types. By creating a Composition, we are not duplicating the same properties on multiple Document Types. This is helpful when we want to use the same set of properties on multiple Document Types. - -To create a Composition, follow these steps: - -1. Go to **Settings** in the Umbraco Backoffice. -2. Expand the **Document Types** folder in the **Settings** tree. -3. Select **...** next to the **Compositions** folder. -4. Click **Create**. -5. Select **Document Type**. -6. Enter a **Name** for the **Composition**- let's call it _Title Box_. -7. Add the following fields with the respective specifications: - - | Group | Field Name | Alias | Data Type | - |-----------|------------|----------|------------| - | Title Box | Title | title | Textstring | - | Title Box | Subtitle | subtitle | Textarea | - -8. Click **Save** to save the Composition. - - ![Add Composition Properties](images/composition-properties-v14.png) - -### Creating a Contact Us Document Type with Template - -Next, we will create a Document type with template. A Document Type contains different properties for holding different types of content. The Document Type we create here will be the one used for creating the content page that will hold our Contact Form. - -To create a **Contact Us** Document Type, follow these steps: - -1. Go to **Settings** in the Umbraco Backoffice. -2. Select **...** next to the **Document Types** folder. -3. Click **Create**. -4. Select **Document Type with Template**. -5. Enter a **Name** for the **Document Type**- let's call it _Contact Us_. -6. Select **Compositions** in the top-right corner. -7. Select **Title Box**. -8. Click **Submit**. -9. Add the following fields with the respective specifications: - - | Group | Field Name | Alias | Data Type | - |---------|--------------|-------------|-----------------| - | Form | Contact Form | contactForm | Form Picker | - | Content | Body Text | bodyText | Richtext Editor | - -10. Click **Save**. - - ![Contact Us Document Type Properties](images/contact-us-doc-type-properties-v14.png) - -### Updating the Document Type Permission - -In the following we will update the Document Type permissions to specifically add child nodes under the root content node. - -To update the **Contact Us** Document Type permissions, follow these steps: - -1. Navigate to the Document Type used for the root content node on your website, in this case **Home** page. -2. Go to the **Structure** tab. -3. Select **Choose** in the **Allowed child node types** section. -4. Select the **Contact Us** page. - - ![Update Home Page Document Type Properties](images/update-doc-type-permissions-v14.png) - -5. Click **Choose**. -6. Click **Save**. - -## Step 2: Prepare the Content Node - -This step takes you through creating the content node for your Contact Form. The content node uses the Document Type and Template to serve up an HTML page to web visitors. - -To add the content node, follow these steps: - -1. Go to **Content** in the Umbraco Backoffice. -2. Select **...** next to the **Home Page**. -3. Click **Create**. -4. Select **Contact Us**. -5. Enter the name for the content node. let's call it _Contact Us_. -6. Enter a **Title**, **Subtitle**, and **Body Text** value. These can always be updated at a later point. - - ![Enter values in Contact Us Content node](images/fill-contact-us-node-v14.png) - -7. Click **Save** or **Save and Publish**. - -## Step 3: Creating the Contact Form - -In this step, we will create the Contact Form using Umbraco Forms. - -To create a form, follow these steps: - -1. Go to the **Forms** section in the Umbraco Backoffice. -2. Click **...** next to the Forms folder. -3. Click Create. -4. Select **New Form...**. -5. Enter a **Name** for the Form. Let's call it _Contact Us_. -6. _[Optional]_ Enter a **Page Name** and **Group Name** for the Data Consent statement. Let's call it _Data Consent_. -7. Click **Add new group**. Let's call it _Information_. -8. Select **Add Question** to add a new field. -9. Enter the following details: - - | Field Name | Value | - | ------------------ | -------------------- | - | Enter question | **Name** | - | Alias | fullName | - | Choose answer type | Short answer | - | Field Type | text | - | Mandatory | On | - -10. Click **Submit**. -11. Repeat **steps 8-10** to add the following fields: - - | Field Name | Value | - | ------------------ | -------------------- | - | Enter question | **Company Name** | - | Choose answer type | Short answer | - - | Field Name | Value | - |--------------------|----------------------------| - | Enter question | **How should we contact you?** | - | Choose answer type | Single choice | - | Prevalues Items | phone, email | - | Mandatory | On | - - | Field Name | Value | - |--------------------|----------------------------| - | Enter question | **Enter your phone number**| - | Choose answer type | Short answer | - | Field Type | tel | - | Validation | Validate as a number | - -12. Enable **Conditions** in the _Enter your phone number_ field. -13. Click **Add Condition**. -14. Select **How should we contact you?** from the dropwdown. -15. Select **phone** in the value field. -16. Click **Submit**. -17. Repeat **steps 8-10** to add the following field: - - | Field Name | Value | - |--------------------|------------------------------| - | Enter question | **Enter your email address** | - | Choose answer type | Short answer | - | Field Type | email | - | Validation | Validate as an email address | - -18. Enable **Conditions** in the _Enter your email address_ field. -19. Click **Add Condition**. -20. Select **How should we contact you?** from the dropwdown. -21. Select **email** in the value field. -22. Click **Submit**. -23. Repeat **steps 8-10** to add the following field: - - | Field Name | Value | - |--------------------|----------------------------------------------------------| - | Enter question | **What is your role?** | - | Choose answer type | Dropdown | - | Prevalues Items | manager, developer, tester, writer, marketing specialist | - - | Field Name | Value | - |--------------------------------|--------------------------| - | Enter question | **Attachments (if any)** | - | Choose answer type | File upload | - | Predefined allowed file types | pdf, png, jpg, gif, txt | - - | Field Name | Value | - |--------------------|---------------------| - | Enter question | **Are you a Robot?**| - | Choose answer type | reCAPTCHAv2 | - | Theme | light | - | Size | normal | - | Mandatory | On | - - ![Add questions](images/contact-us-form-add-questions-v14.png) - -24. Select the **Reorder** option. -25. Drag the **Data consent** group below the **Information** group. -26. Click **I am done reordering**. -27. Click **Save**. - -### Configuring the Form Workflow - -Workflows is how you determine what you happen after your form is submitted. It could be actions like sending an email or displaying a "Thank You" message. - -To configure the Form workflow, follow these steps: - -1. Select the **Submit message/ Go to page** options in the bottom of the Forms editor. -2. Enter a customised message in the **Message on Submit** field. -3. Click **Submit**. -4. Click on **Send template email to xxx@xx.dk**. -5. Enter an email address in the **Sender Email** field. -6. By default, the **Example-Template.cshtml** template will be selected in the **Email template** field. -7. Enable **Attach Uploaded Files**. -8. Click **Submit**. -9. Click **Save**. - -### Configuring the Form Settings - -In this step, you will find the information about accessing the Forms Settings and the validations available to customise your form. - -To configure the form settings, follow these steps: - -1. Navigate to the **Settings** tab in the Forms editor. -2. Scroll to find the **Validation** section. -3. Ensure that the **Mark Mandatory fields** option is checked under **Mark fields**. -4. Click **Save**. - -{% hint style="info" %} -There are multiple settings that be configured. These are all optional in relation to this tutorial. -{% endhint %} - -## Step 4: Adding the Contact Form to the Content Node - -Now that you have created your Contact Form, you can add it in the Contact Us Content Node using the _Form Picke_ Data Type. - -To add the Contact Form to the Content Node, follow these steps: - -1. Go to the **Content** section in the Umbraco Backoffice. -2. Open the **Contact Us** Page. -3. Select **Choose** in the **Contact Form** field. -4. Select the **Insert Form with Theme** option. -5. Select the **Contact Us** Form. -6. Click **Choose**. - - ![Adding the Contact Us Form](images/select-form-v14.png) - -7. Click **Save** or **Save and Publish**. - -## Step 5: Additional configuration - -In the next couple of steps, we will add some additional configuration required in order for our form to work properly. - -### Configuring the reCAPTCHA value - -You need to update the configuration to include a value in the `appsettings.json` file. - -To configure the reCAPTCHA value, see the [reCAPTCHA configuration](../developer/configuration/README.md#recaptcha-v2-field-type-configuration) article. - -### Configuring Simple Mail Transfer Protocol (SMTP) - -By adding the SMTP settings in the `appsettings.json` file, you can send out emails from your Umbraco installation. It is required in order for your form to be able to send emails on submission. - -To configure the SMTP settings, see the [Global Settings](https://docs.umbraco.com/umbraco-cms/reference/configuration/globalsettings#smtp-settings) article. - -## Step 6: Rendering the Contact Form - -In this step, we will render the values of the Contact Us Document Type in the template. - -To render the Contact Form, follow these steps: - -1. Go to the **Settings** section in the Umbraco Backoffice. -2. Open the **Contact Us** template in the **Templates** folder. -3. Enter the following code to render the form: - - ```cs - @using Umbraco.Forms.Web.Helpers; - @await Component.InvokeAsync("RenderForm", new { formId = Guid.Parse(""), FormTheme = "bootstrap3-horizontal", ExcludeScripts = "1" }) - ``` - - {% hint style="info" %} - Replace **** with the ID of your form. You can find the ID in the Form's **Info** tab. - {% endhint %} - -4. Select **Insert**. -5. Click **Value**. -6. Select **Document Type** from the **Choose field** dropdown. -7. Select **Contact Us**. -8. Click **Choose**. -9. Select **bodyText** from the **Contact Us** dropdown. -10. Click **Submit**. -11. Click **Save**. - -{% hint style="info" %} -For Umbraco Forms to work correctly, you need to include some client dependencies. For more information, see the [Preparing Your Frontend](https://docs.umbraco.com/umbraco-forms/developer/prepping-frontend) article. -{% endhint %} - -## The final result - -Finally, it is time to view the Contact Form on the frontend. - -To view the Contact Form on the Frontend, follow these steps: - -1. Go to the **Content** section in the Umbraco Backoffice. -2. Open the **Contact Us** Page. -3. Ensure that the page is published. -4. Go to the **Info** tab. -5. Click on the Published link in the **Links** section. - -You now have a full-fledged Contact Form ready to be used on your website. diff --git a/14/umbraco-forms/tutorials/creating-a-multipage-form.md b/14/umbraco-forms/tutorials/creating-a-multipage-form.md deleted file mode 100644 index 4bd749367e8..00000000000 --- a/14/umbraco-forms/tutorials/creating-a-multipage-form.md +++ /dev/null @@ -1,187 +0,0 @@ -# Creating a Multi-Page Form - -In this tutorial, you will learn how to create a multi-page form using Umbraco Forms. Multi-page forms are particularly useful when you need to collect detailed information from users in a structured and user-friendly way. - -Multi-page forms are ideal for use cases such as event registration, job applications, booking a meeting, and so on. - -## Prerequisites - -- [Umbraco CMS Installation](https://docs.umbraco.com/umbraco-cms/fundamentals/setup/install) -- [Umbraco Forms Package](../installation/install.md) -- Pre-built Website including a **Document Type** with the **Form Picker** Data Type. - -## Log in to the Umbraco Backoffice - -1. Log in to the Umbraco backoffice. -2. Go to the **Forms** section. - -## Create a New Form - -1. Click **+** next to the Forms folder. -2. Select **New Form**. - -![New Form Creation](images/create-form.png) - -3. Enter a **Name** for the form. For example: *Book a Meeting*. -4. Click **Save**. - -## Set up the First Page of the Form - -Let us begin by adding some fields to the first page of the form. By default, the **Data Consent** field is already available, and we will call this group **Data Consent**. - -To create a new group: - -1. Click **Add new group**. -2. **Enter the Name** of the group. For example: *Personal Information*. -3. Click **Add question**. -4. Select **Short answer** as the field type. -5. **Enter a Name** for the field type. For example, *First Name*. -6. Select **Text** as the **Field Type** from the drop-down list. -7. Mark the field as **Mandatory**. -8. Click **Submit**. -9. Click **Save**. - -Similarly, you can also add other relevant fields such as last name or email based on your requirements. - -For this tutorial, the following fields are added with the respective specifications: - -| Field Name | Data Type | Field Type | -|---------------|--------------|------------| -| Surname | Short answer | text | -| Age | Short answer | number | -| Country | Short answer | text | -| Phone number | Short answer | tel | -| Email address | Short answer | email | - -If you wish to reorder your fields, click **Reorder**. - -![Personal Information Questions on the First Page](images/first-page-of-form.png) - -## Create the Second Page - -To create a multi-page form, you need to add more pages: - -1. Click **Add new page** to create the second page of your form. -2. **Enter a Name** for this page. For example: *Company Information*. -3. Click **Add question**. -4. Select **Short answer** as the field type. -5. **Enter a Name** for the field type. For example, *Company Name*. -6. Provide a **Default Value**. For example, *Enter the name of your company*. -7. Click **Submit**. -8. Click **Save**. - -![Default Value displayed](images/company-information.png) - -Similarly, you can also add other relevant fields based on your requirements. - -### Add Conditional Logic - -Umbraco Forms allows you to customize the flow of your multi-page form. You can add conditional logic to control which questions appear based on user inputs. - -To add conditions, follow these steps: - -1. Click **Add question**. -2. Select **Single choice** as the field type. -3. **Enter a Name** for the field type. For example, *Do you work with Umbraco*. -4. Enter the **Value** and **Caption** in the **Options** field. - - For this tutorial, the following values are added: - - Yes - - No - -![Values in the Options Field](images/prevalue-fields.png) - -5. Mark the field as **Mandatory**. -6. Click **Submit**. -7. Click **Save**. -8. Repeat steps 1-4 to create a conditional question titled: *If yes, how many years?* -9. Enter the **Value** and **Caption** in the **Options** field. - - For this tutorial, the following values are added: - - 1-5 years - - 5-10 years - - 10+ years - -![Conditional Question Values in the Options Field](images/conditional-question-part-1.png) - -10. Enable **Conditions**. -11. Set the parameters for the condition as follows: - - - **Show** this field if **all** of the following match: - - Question: **Do you work with Umbraco?** - - Condition: **is** - - Value: **Yes** - -![Values for adding a Condition](images/conditional-question-part-2.png) - -12. Click **Submit**. -13. Click **Save**. - -![Company information Questions on the Second Page](images/page-2-details.png) - -## Create the Final Page - -1. Click **Add new page** to create the final page of your form. -2. **Enter a Name** for this page. For example: *Products*. -3. Click **Add question**. -4. Select **Multiple choice** as the field type. -5. **Enter a Name** for the field type. For example, *Select the products you are interested in*. -6. Enter the **Value** and **Caption** in the **Options** field. - - For this tutorial, the following values are added: - - Umbraco CMS - - Umbraco Cloud - - Umbraco Deploy - - Umbraco Heartcore - - Umbraco Forms - - Umbraco Commerce - - Umbraco Workflow - -![Multiple Values in the Option Field](images/multiple-choice.png) - -7. Click **Submit**. -8. Click **Save**. - -![Products Selection Question on the Final Page](images/Final-page.png) - -## Embed the Form on a Web Page - -Once you are satisfied with your multi-page form, it is time to embed it on your website. - -To display the form on the website, follow these steps: - -1. Go to the **Content** section. -2. Click **+** next to the parent page of the website. -3. Select the Document Type. - -![Pick a Document Type](images/pick-document-type.png) - -4. **Enter a Name** for the page. For example, *Book a Meeting!* -5. Select the **Book a Meeting** form using the *Form Picker*. -6. Click **Save and Publish**. - -![New Page created in the Content Section](images/Form-Content-section.png) - -## Customize Form Settings - -If you wish to customize the Form Settings, see the [Form Settings](../editor/creating-a-form/form-settings.md) article. - -## Rendering the Form on the Frontend - -For Umbraco Forms to work correctly, you need to include some client dependencies. For more information, see the [Preparing Your Frontend](https://docs.umbraco.com/umbraco-forms/developer/prepping-frontend) article. - -To render the Form on the frontend, see the [Rendering Forms](../developer/rendering-forms.md) article. - -## Testing the Form - -1. Go to the **Info** workspace view of the *Book a Meeting!* page. -2. Click on the Published link in the **Links** section. -3. Fill out the form to see how it functions. -4. Submit the form to ensure it redirects to a Thank You page. -5. Go to the **Forms** section in the Backoffice. -6. Navigate to the **Book a Meeting** Form. -7. Click on the **Entries** tab and verify that the data is captured. - -![Form Data in the Entries tab](images/form-data-entry.png) - -You have successfully created a multi-page form with conditional logic in Umbraco Forms. By using multi-page forms, you have made complex data entry much simpler and more user-friendly. This not only improves the experience for your users but also makes your forms more efficient and manageable. diff --git a/14/umbraco-forms/tutorials/images/Final-page.png b/14/umbraco-forms/tutorials/images/Final-page.png deleted file mode 100644 index d418c911578..00000000000 Binary files a/14/umbraco-forms/tutorials/images/Final-page.png and /dev/null differ diff --git a/14/umbraco-forms/tutorials/images/Form-Content-section.png b/14/umbraco-forms/tutorials/images/Form-Content-section.png deleted file mode 100644 index 5b60689923d..00000000000 Binary files a/14/umbraco-forms/tutorials/images/Form-Content-section.png and /dev/null differ diff --git a/14/umbraco-forms/tutorials/images/company-information.png b/14/umbraco-forms/tutorials/images/company-information.png deleted file mode 100644 index 8208c9af31e..00000000000 Binary files a/14/umbraco-forms/tutorials/images/company-information.png and /dev/null differ diff --git a/14/umbraco-forms/tutorials/images/composition-properties-v14.png b/14/umbraco-forms/tutorials/images/composition-properties-v14.png deleted file mode 100644 index 19ee86be699..00000000000 Binary files a/14/umbraco-forms/tutorials/images/composition-properties-v14.png and /dev/null differ diff --git a/14/umbraco-forms/tutorials/images/composition-properties.png b/14/umbraco-forms/tutorials/images/composition-properties.png deleted file mode 100644 index 3bf730fba7e..00000000000 Binary files a/14/umbraco-forms/tutorials/images/composition-properties.png and /dev/null differ diff --git a/14/umbraco-forms/tutorials/images/conditional-question-part-1.png b/14/umbraco-forms/tutorials/images/conditional-question-part-1.png deleted file mode 100644 index ca2b9b83d18..00000000000 Binary files a/14/umbraco-forms/tutorials/images/conditional-question-part-1.png and /dev/null differ diff --git a/14/umbraco-forms/tutorials/images/conditional-question-part-2.png b/14/umbraco-forms/tutorials/images/conditional-question-part-2.png deleted file mode 100644 index eabde810d2d..00000000000 Binary files a/14/umbraco-forms/tutorials/images/conditional-question-part-2.png and /dev/null differ diff --git a/14/umbraco-forms/tutorials/images/contact-us-doc-type-properties-v14.png b/14/umbraco-forms/tutorials/images/contact-us-doc-type-properties-v14.png deleted file mode 100644 index 307f0aca971..00000000000 Binary files a/14/umbraco-forms/tutorials/images/contact-us-doc-type-properties-v14.png and /dev/null differ diff --git a/14/umbraco-forms/tutorials/images/contact-us-doc-type-properties.png b/14/umbraco-forms/tutorials/images/contact-us-doc-type-properties.png deleted file mode 100644 index efe005b1c57..00000000000 Binary files a/14/umbraco-forms/tutorials/images/contact-us-doc-type-properties.png and /dev/null differ diff --git a/14/umbraco-forms/tutorials/images/contact-us-form-add-questions-v14.png b/14/umbraco-forms/tutorials/images/contact-us-form-add-questions-v14.png deleted file mode 100644 index e0d4cf1bd10..00000000000 Binary files a/14/umbraco-forms/tutorials/images/contact-us-form-add-questions-v14.png and /dev/null differ diff --git a/14/umbraco-forms/tutorials/images/contact-us-form-add-questions.png b/14/umbraco-forms/tutorials/images/contact-us-form-add-questions.png deleted file mode 100644 index a100b2d4426..00000000000 Binary files a/14/umbraco-forms/tutorials/images/contact-us-form-add-questions.png and /dev/null differ diff --git a/14/umbraco-forms/tutorials/images/create-form.png b/14/umbraco-forms/tutorials/images/create-form.png deleted file mode 100644 index b735f9d1e9f..00000000000 Binary files a/14/umbraco-forms/tutorials/images/create-form.png and /dev/null differ diff --git a/14/umbraco-forms/tutorials/images/creating-a-composition.png b/14/umbraco-forms/tutorials/images/creating-a-composition.png deleted file mode 100644 index c616f49f0b9..00000000000 Binary files a/14/umbraco-forms/tutorials/images/creating-a-composition.png and /dev/null differ diff --git a/14/umbraco-forms/tutorials/images/fill-contact-us-node-v14.png b/14/umbraco-forms/tutorials/images/fill-contact-us-node-v14.png deleted file mode 100644 index fc5a30263f1..00000000000 Binary files a/14/umbraco-forms/tutorials/images/fill-contact-us-node-v14.png and /dev/null differ diff --git a/14/umbraco-forms/tutorials/images/fill-contact-us-node.png b/14/umbraco-forms/tutorials/images/fill-contact-us-node.png deleted file mode 100644 index 5473a8c2589..00000000000 Binary files a/14/umbraco-forms/tutorials/images/fill-contact-us-node.png and /dev/null differ diff --git a/14/umbraco-forms/tutorials/images/first-page-of-form.png b/14/umbraco-forms/tutorials/images/first-page-of-form.png deleted file mode 100644 index 5e0c6c742bd..00000000000 Binary files a/14/umbraco-forms/tutorials/images/first-page-of-form.png and /dev/null differ diff --git a/14/umbraco-forms/tutorials/images/form-data-entry.png b/14/umbraco-forms/tutorials/images/form-data-entry.png deleted file mode 100644 index 0d66f6f1847..00000000000 Binary files a/14/umbraco-forms/tutorials/images/form-data-entry.png and /dev/null differ diff --git a/14/umbraco-forms/tutorials/images/multiple-choice.png b/14/umbraco-forms/tutorials/images/multiple-choice.png deleted file mode 100644 index d4abe0b3ed1..00000000000 Binary files a/14/umbraco-forms/tutorials/images/multiple-choice.png and /dev/null differ diff --git a/14/umbraco-forms/tutorials/images/page-2-details.png b/14/umbraco-forms/tutorials/images/page-2-details.png deleted file mode 100644 index 4285fc810be..00000000000 Binary files a/14/umbraco-forms/tutorials/images/page-2-details.png and /dev/null differ diff --git a/14/umbraco-forms/tutorials/images/pick-document-type.png b/14/umbraco-forms/tutorials/images/pick-document-type.png deleted file mode 100644 index 6d3f1b2f9be..00000000000 Binary files a/14/umbraco-forms/tutorials/images/pick-document-type.png and /dev/null differ diff --git a/14/umbraco-forms/tutorials/images/prevalue-fields.png b/14/umbraco-forms/tutorials/images/prevalue-fields.png deleted file mode 100644 index f713a9f6212..00000000000 Binary files a/14/umbraco-forms/tutorials/images/prevalue-fields.png and /dev/null differ diff --git a/14/umbraco-forms/tutorials/images/select-form-v14.png b/14/umbraco-forms/tutorials/images/select-form-v14.png deleted file mode 100644 index 078eb3b06a9..00000000000 Binary files a/14/umbraco-forms/tutorials/images/select-form-v14.png and /dev/null differ diff --git a/14/umbraco-forms/tutorials/images/select-form.png b/14/umbraco-forms/tutorials/images/select-form.png deleted file mode 100644 index 888e8f1e48e..00000000000 Binary files a/14/umbraco-forms/tutorials/images/select-form.png and /dev/null differ diff --git a/14/umbraco-forms/tutorials/images/update-doc-type-permissions-v14.png b/14/umbraco-forms/tutorials/images/update-doc-type-permissions-v14.png deleted file mode 100644 index 548a86d93fe..00000000000 Binary files a/14/umbraco-forms/tutorials/images/update-doc-type-permissions-v14.png and /dev/null differ diff --git a/14/umbraco-forms/tutorials/images/update-doc-type-permissions.png b/14/umbraco-forms/tutorials/images/update-doc-type-permissions.png deleted file mode 100644 index a26f091fc53..00000000000 Binary files a/14/umbraco-forms/tutorials/images/update-doc-type-permissions.png and /dev/null differ diff --git a/14/umbraco-forms/tutorials/overview.md b/14/umbraco-forms/tutorials/overview.md deleted file mode 100644 index 22071b01561..00000000000 --- a/14/umbraco-forms/tutorials/overview.md +++ /dev/null @@ -1,16 +0,0 @@ -# Overview - -In this section, you can find a set of different tutorials to use when creating and working with Umbraco Forms. - -{% hint style="info" %} -This section is a work in progress. - -Do you have suggestions for or wishes for tutorials on Umbraco Forms? -Let us know using the [UmbracoDocs GitHub Issue Tracker](https://github.com/umbraco/UmbracoDocs/issues). -{% endhint %} - -## Tutorials - -### [Creating a Contact Form](creating-a-contact-form.md) - -Learn how to create a Contact Form and add it to your website. \ No newline at end of file diff --git a/14/umbraco-forms/upgrading/manualupgrade.md b/14/umbraco-forms/upgrading/manualupgrade.md deleted file mode 100644 index dfd3d5c1362..00000000000 --- a/14/umbraco-forms/upgrading/manualupgrade.md +++ /dev/null @@ -1,33 +0,0 @@ -# Upgrading Umbraco Forms - -This article shows how to manually upgrade Umbraco Forms to run the latest version. - -When upgrading Umbraco Forms, be sure to also consult the [version specific upgrade notes](version-specific.md) to learn about potential breaking changes and common pitfalls. - -## Get the latest version of Umbraco Forms - -To get the latest version of Umbraco Forms, you can upgrade using: - -* [NuGet](manualupgrade.md#nuget) -* [Visual Studio](manualupgrade.md#visual-studio) - -### NuGet - -* NuGet installs the latest version of the package when you use the `dotnet add package Umbraco.Forms` command unless you specify a package version: `dotnet add package Umbraco.Forms --version ` -* After you have added a package reference to your project by executing the `dotnet add package Umbraco.Forms` command in the directory that contains your project file, run `dotnet restore` to install the package. - -### Visual Studio - -1. Go to `Tools` -> `NuGet Package Manager` -> `Manage NuGet Packages for Solution...` in Visual Studio, to upgrade your Forms: -2. Select **Umbraco.Forms**. -3. Select the latest version from the **Version** drop-down and click **Install**. - -
NuGet Package Manager
- -4. When the command completes, open the **.csproj** file to make sure the package reference is updated: - -```xml - - - -``` diff --git a/14/umbraco-forms/upgrading/migration-ids.md b/14/umbraco-forms/upgrading/migration-ids.md deleted file mode 100644 index 49ac005fa33..00000000000 --- a/14/umbraco-forms/upgrading/migration-ids.md +++ /dev/null @@ -1,25 +0,0 @@ -# Migration IDs - -A unique **migration ID** is generated for each Umbraco Forms upgrade that requires a migration. The migration IDs are all listed in this article. - -| Migration ID | Introduced In Version | Description | -| ------------------------------------ | --------------------- | ----------------------------------------------------------------------------------- | -| 7c7bc5ee-4c5b-42dc-9576-5ce6dfbddb8e | 10.0.0 | Installs Umbraco Forms. | -| 9f7e6fe6-bbd5-4b2b-8820-e9e0e36cc74c | 10.1.0 | Adds Culture column to Records table. | -| 1a8f0d04-9396-40a2-9423-39fc9ae3828f | 10.1.0 | Adds a Record Workflow Audit table. | -| 6e692c5d-c670-4c34-af17-28d8dbf0dcd2 | 10.1.0 | Adds an ExecutionStage column to the Record Workflow Audit table. | -| 5d84fee1-388c-4e5f-b98c-1e66947278f1 | 10.1.0 | No operation migration. | -| 22df962a-ae26-4bdd-b8fd-0513a9c636bf | 10.5.2/12.1.2 | Ensures the presence of an index on the FolderKey column in the Forms table. | -| c3e657f6-3ae7-4ee9-b442-01702a41de9a | 12.2.0/13.0.0 | Adds a relation between content and forms. | -| e0290a40-91c9-4acb-a7ca-d312037078f2 | 12.2.0/13.0.0 | Adds a NodeId column to Forms table | -| 6f0eb771-6690-4b53-870a-f7dbb2785cac | 12.2.0/13.0.0 | Populates the NodeId column in the Forms table. | -| 44949e12-e4ef-42c0-949b-67286b946fe0 | 12.2.0/13.0.0 | No operation migration. | -| 773ae769-00b7-4429-b7d5-de0fda0b4217 | 12.2.1/13.0.1 | Ensures the consistent key is used for the relation type between content and forms. | -| 55d53d2e-f795-42fb-9e77-8edfc6eed4aa | 13.2.0 | Adds an AdditionalData column to the Records table. | -| 1fff8b7b-48e7-450a-80b1-7df628508b27 | 13.3.0 | Adds delete entries permissions field to the security tables. | -| 7e170195-cab7-48ca-98c7-bbcbd5cfda95 | 13.4.0 | Adds created and updated by columns to the entity tables. | -| c74223ed-a554-4a14-a1f0-0477dce01ad6 | 14.0.0 | Updates the form picker property editor UI alias. | -| a5ffa9a7-ca77-4a7c-a1e4-f32e25cde758 | 14.1.0 | Same as 13.2.0 to allow upgrading 13.2 to 14.1. | -| db5ef50d-51d0-4f93-aae9-bd3df53a3bb1 | 14.2.0 | Same as 13.3.0 to allow upgrading 13.3 to 14.2. | - -You can't upgrade to version 14 from 13.4.0 or later, because active development moved to version 15 at that time. Please upgrade directly to version 15 or later instead. diff --git a/14/umbraco-forms/upgrading/version-specific.md b/14/umbraco-forms/upgrading/version-specific.md deleted file mode 100644 index a8397b5394a..00000000000 --- a/14/umbraco-forms/upgrading/version-specific.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -description: >- - Version specific documentation for upgrading to new major versions of Umbraco - Forms. ---- - -# Version Specific Upgrade Notes - -This article provides specific upgrade documentation for migrating to Umbraco Forms version 14. - -{% hint style="info" %} -If you are upgrading to a minor or patch version, you can find the details about the changes in the [Release Notes](../release-notes.md) article. -{% endhint %} - -## Version Specific Upgrade Notes History - -Version 14 of Umbraco Forms has a minimum dependency on Umbraco CMS core of `14.0.0`. It runs on .NET 8. - -#### **Breaking changes** - -Version 14 contains a number of breaking changes, primarily due to the new backoffice introduced in Umbraco 14. The details are listed here: - -#### **Behavior** - -* A new management API has been introduced at `umbraco/forms/management/api`. -* The root of the existing delivery API used for headless/AJAX solutions has moved to `umbraco/forms/delivery/api`. -* The HTML helper `RenderUmbracoFormDependencies` no longer renders the promises polyfill, which is not needed in modern browsers. -* Server-side registration of content apps has been removed as this is now a client-side concern. -* Creation of custom fields, workflow, and other provider types remains primarily a server-side task. However, they no longer require the provision of AngularJS views and controllers. Instead, these reference registered client-side manifests. For more information, see the [extending Umbraco Forms](../developer/extending/) article. -* With the removal of node selection by XPath support in Umbraco 14, the "Save as Umbraco node" workflow now uses [dynamic root](https://docs.umbraco.com/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/multinode-treepicker). - -#### **Configuration** - -* The setting `FieldSettings:TitleAndDescription:AllowUnsafeHtmlRendering` has a new default of `false`. -* The setting `PageOptions:TrackRenderedFormsStorageMethod` has a new default of `HttpContextItems`. - -#### **Dependencies** - -* Umbraco CMS dependency was updated to `14.0.0`. - -#### **Code** - -The following updates describe the more significant changes to the codebase and public API: - -* All controllers relating to backoffice trees and editors have been removed and their functionality replaced by the management API. -* The serialization library has been changed from `Newtonsoft.Json` to `System.Text.Json`. Among other updates this involved removing the public class `FormsJsonSerializerSettings` and replacing it with `FormsJsonSerializerOptions`. -* The obsolete methods `GetFieldsNotDisplayed` and `Build` on `FormViewModel` have been removed. -* The unused `RetryWorkflow` class has been removed. - -## Legacy version specific upgrade notes - -You can find the version specific upgrade notes for versions out of support in the [Legacy documentation on GitHub](https://github.com/umbraco/UmbracoDocs/blob/umbraco-eol-versions/11/umbraco-forms/installation/version-specific.md). diff --git a/14/umbraco-ui-builder/.gitbook.yaml b/14/umbraco-ui-builder/.gitbook.yaml deleted file mode 100644 index 5422b068ba5..00000000000 --- a/14/umbraco-ui-builder/.gitbook.yaml +++ /dev/null @@ -1,5 +0,0 @@ -root: ./ - -​structure: - readme: README.md - summary: SUMMARY.md diff --git a/14/umbraco-ui-builder/README.md b/14/umbraco-ui-builder/README.md deleted file mode 100644 index 68acb7c47a0..00000000000 --- a/14/umbraco-ui-builder/README.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -description: Documentation for Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Umbraco UI Builder Documentation - -Umbraco UI Builder is the Umbraco v14+ backoffice UI builder for custom data structures configured via a fluent API. - -{% hint style="warning" %} -This page is a work in progress and may undergo further revisions, updates, or amendments. The information contained herein is subject to change without notice. -{% endhint %} - -![Example Umbraco UI Builder UI](images/listview.png) - -If you have a custom data store that you want to content manage from within Umbraco, then you can use Umbraco UI Builder. With some lines of code, you can configure a custom administration UI, and reuse many core components with a consistent look and feel. - -With Umbraco UI Builder, custom backoffice integrations can now take a matter of minutes, rather than days. - -## Using the Documentation - -**This documentation is aimed at developers** who have at least a basic understanding of Umbraco, as well as C#/MVC principles. - -If you are new to Umbraco UI Builder, it is recommended that you start by taking a look at the [Getting Started](./getting-started/overview.md) section. This provides details on the system requirements and how to install Umbraco UI Builder. - -Once you have Umbraco UI Builder installed and are wondering "What next?" then you'll want to take a look at the [Guides](./guides/creating-your-first-integration.md) section. This provides a quick-start example of how to configure Umbraco UI Builder. - -Use the main menu to dive deeper into Umbraco UI Builder and get to know all of its features in detail. You can then jump to the specific topic you are interested in to find out more. - -Finally, for all other resources/useful information you can head over to the [Miscellaneous](./miscellaneous/conventions.md) section. - -## Getting Help - -If you require assistance you can use our support channels to seek assistance. diff --git a/14/umbraco-ui-builder/SUMMARY.md b/14/umbraco-ui-builder/SUMMARY.md deleted file mode 100644 index 3423f807237..00000000000 --- a/14/umbraco-ui-builder/SUMMARY.md +++ /dev/null @@ -1,92 +0,0 @@ -# Table of contents - -* [Umbraco UI Builder Documentation](README.md) -* [Known Issues](known-issues.md) -* [Release Notes](release-notes.md) - -## Installation - -* [Installing Umbraco UI Builder](installation/installation.md) -* [Licensing](installation/licensing-model.md) - -## Upgrading - -* [Upgrading Umbraco UI Builder](upgrading/upgrade.md) -* [Version Specific Upgrade Notes](upgrading/version-specific.md) -* [Migrate from Konstrukt to Umbraco UI Builder](upgrading/migrating-from-konstrukt-to-umbraco-ui-builder.md) - -## Getting Started - -* [Overview](getting-started/overview.md) -* [Configuration](getting-started/configuration.md) -* [User Interface](getting-started/user-interface.md) - -## How-to Guides - -* [Creating your first integration](guides/creating-your-first-integration.md) - -## Areas - -* [Overview](areas/overview.md) -* [Sections](areas/sections.md) - * [Summary Dashboards](areas/summary-dashboards.md) -* [Trees](areas/trees.md) - * [Folders](areas/folders.md) -* [Dashboards](areas/dashboards.md) -* [Context Apps](areas/context-apps.md) - -## Collections - -* [Overview](collections/overview.md) -* [The Basics](collections/the-basics.md) -* [List Views](collections/list-views.md) - * [Field Views](collections/field-views.md) -* [Editors](collections/editors.md) -* [Child Collections](collections/child-collections.md) - * [Child Collection Groups](collections/child-collection-groups.md) - * [Retrieve Child Collections](collections/retrieve-child-collections.md) -* [Related Collections](collections/related-collections.md) - -## Searching - -* [Overview](searching/overview.md) -* [Searchable Properties](searching/searchable-properties.md) - -## Filtering - -* [Overview](filtering/overview.md) -* [Global Filters](filtering/global-filters.md) -* [Data Views](filtering/data-views.md) - * [Data Views Builders](filtering/data-views-builders.md) -* [Filterable Properties](filtering/filterable-properties.md) - -## Actions - -* [Overview](actions/overview.md) -* [The Basics](actions/the-basics.md) -* [Action Visibility](actions/action-visibility.md) -* [Inbuilt Actions](actions/inbuilt-actions.md) - -## Cards - -* [Overview](cards/overview.md) -* [Count Cards](cards/count-cards.md) -* [Custom Cards](cards/custom-cards.md) - -## Property Editors - -* [Overview](property-editors/overview.md) -* [Entity Picker](property-editors/entity-picker.md) - -## Advanced - -* [Virtual Sub Trees](advanced/virtual-sub-trees.md) -* [Encrypted Properties](advanced/encrypted-properties.md) -* [Value Mappers](advanced/value-mappers.md) -* [Repositories](advanced/repositories.md) -* [Events](advanced/events.md) - -## Miscellaneous - -* [Conventions](miscellaneous/conventions.md) -* [Umbraco Aliases](miscellaneous/umbraco-aliases.md) diff --git a/14/umbraco-ui-builder/actions/action-visibility.md b/14/umbraco-ui-builder/actions/action-visibility.md deleted file mode 100644 index 99086bb89b4..00000000000 --- a/14/umbraco-ui-builder/actions/action-visibility.md +++ /dev/null @@ -1,109 +0,0 @@ ---- -description: Controlling the visibility of actions in Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Action Visibility - -By default actions are not visible in the UI and you must expressly define when and where an action should display. This can be achieved in two ways, either on the action definition itself or at the point of registration on the collections config. - -## Controlling the default action visibility - -To define the default visibility of an action at the action level you can do this by overriding the `IsVisible` method of the `Action<>` base class. - -````csharp -// Example -public class MyAction : Action -{ - ... - public override bool IsVisible(ActionVisibilityContext ctx) - { - return ctx.ActionType == ActionType.Bulk - || ctx.ActionType == ActionType.Row; - } - ... -} -```` - -The `IsVisible` method is passed a `ActionVisibilityContext` which you should use to decide whether the action should display, returning `true` if it should, or `false` if it should not. For more information check the [Action visibility context](#action-visibility-context). - -## Overriding an actions visibility - -Overriding an actions visibility is controlled via the [collections](../collections/overview.md) configuration. - -### **AddAction<TMenuActionType>(Lambda actionConfig = null) : CollectionConfigBuilder<TEntityType>** - -Adds an action of the given type to the collection with the given visibility. - -````csharp -// Example -collectionConfig.AddAction(actionConfig => actionConfig - .SetVisibility(x => x.ActionType == ActionType.Bulk - || x.ActionType == ActionType.Row) -); -```` - -### **AddAction(Type actionType, Lambda actionConfig = null) : CollectionConfigBuilder<TEntityType>** - -Adds an action of the given type to the collection with the given visibility. - -````csharp -// Example -collectionConfig.AddAction(typeof(ExportMenuAction), actionConfig => actionConfig - .SetVisibility(x => x.ActionType == ActionType.Bulk - || x.ActionType == ActionType.Row) -); -```` - -### **AddAction(IAction action, Lambda actionConfig = null) : CollectionConfigBuilder<TEntityType>** - -Adds the given action to the collection with the given visibility. - -````csharp -// Example -collectionConfig.AddAction(action, actionConfig => actionConfig - .SetVisibility(x => x.ActionType == ActionType.Bulk - || x.ActionType == ActionType.Row) -); -```` - -## Action visibility context - -When controlling the visibility of an action you will be given a `ActionVisibilityContext` object from which you can decide whether to show the action or not. The visibility context contains two key pieces of information on which you can base this decision. - -### ActionType - -The action type property is an enum property that define which area of the UI it is that wishes to access this action. Enabling an action to display for a given action type will determine where an action is displayed. - -#### ContainerMenu - -The `ContainerMenu` action type determines that the action will be displayed in both the tree of the collection and its list view actions menu. - -![Container Menu](../images/container_actions_menu.png) - -#### EntityMenu - -The `EntityMenu` action type determines that the action will be displayed in the actions menu of a collection editor UI. - -![Entity Menu](../images/entity_actions_menu.png) - -#### Bulk - -The `Bulk` action type determines that the action will be displayed in the collection list view bulk actions menu. - -![Bulk Actions](../images/bulk_actions_menu.png) - -#### Row - -The `Row` action type determines that the action will be displayed in the collection list view action row menu. - -![Row Actions](../images/row_actions_menu.png) - -#### Save - -The `Save` action type determines that the action will be displayed as a sub button in an entity editors save button. All `Save` action types trigger a save before the action is executed and so to convey this, all `Save` action type button labels are prefixed `Save & [Action Name]` - -![Save Actions](../images/save_actions_menu.png) - -### UserGroups - -The user groups collection contains a list of Umbraco `IReadOnlyUserGroup` objects for the current logged-in backoffice user. This allows you to control the visibility of actions for given user group members. diff --git a/14/umbraco-ui-builder/actions/inbuilt-actions.md b/14/umbraco-ui-builder/actions/inbuilt-actions.md deleted file mode 100644 index 6a88bc85bb2..00000000000 --- a/14/umbraco-ui-builder/actions/inbuilt-actions.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -description: A list of inbuilt actions that come with Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Inbuilt Actions - -Umbraco UI Builder comes with some inbuilt actions that are available for you to use straight away. - -## ExportEntityAction - -**Namespace** Umbraco.UIBuilder.Infrastructure.Configuration.Actions - -Provides a Comma-Separated Values (CSV) export functionality converting all properties to column headings and rendering each entity property values on each row. - -## ImportEntityAction - -**Namespace** Umbraco.UIBuilder.Infrastructure.Configuration.Actions - -Provides a Comma-Separated Values (CSV) import functionality matching column headings with entity properties and mapping row values to an entity. diff --git a/14/umbraco-ui-builder/actions/overview.md b/14/umbraco-ui-builder/actions/overview.md deleted file mode 100644 index cf0369c2b15..00000000000 --- a/14/umbraco-ui-builder/actions/overview.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -description: Configuring actions in Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Actions - -Actions provide an API to perform custom tasks against a collection and its entities from multiple locations in the UI. Examples: menu actions, bulk actions, or individual table row actions. - -![Bulk Actions UI](../images/bulk_actions.png) - -Get started with actions by learning about the basics. - -{% content-ref url="the-basics.md" %} -[the-basics.md](the-basics.md) -{% endcontent-ref %} diff --git a/14/umbraco-ui-builder/actions/the-basics.md b/14/umbraco-ui-builder/actions/the-basics.md deleted file mode 100644 index 430a66c1a40..00000000000 --- a/14/umbraco-ui-builder/actions/the-basics.md +++ /dev/null @@ -1,119 +0,0 @@ ---- -description: Configuring actions in Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# The Basics - -Actions are a powerful way of adding custom functionality to Umbraco UI Builder without needing to create custom UI elements. By providing an action to run, Umbraco UI Builder can automatically trigger actions from a number of UI locations. - -## Defining an action - -To define an action create a class that inherits from the base class `Action<>` and configure it like below: - -````csharp -// Example -public class MyAction : Action -{ - public override string Icon => "icon-settings"; - public override string Alias => "myaction"; - public override string Name => "My Action"; - public override bool ConfirmAction => true; - - public override ActionResult Execute(string collectionAlias, object[] entityIds) - { - // Perform operation here... - } -} -```` - -The required configuration options are: - -* **Name:** The name of the action. -* **Alias:** A unique alias for the action. -* **Icon:** An icon to display next to the name in the action button. -* **Execute:** The method to run against a given list of entities. - -Additional optional configuration options are: - -* **ConfirmAction:** Set whether a confirm dialog should display before performing this action. - -The generic argument is a return type for the action. See [Controlling the action result](#controlling-the-action-result) below. - -{% hint style="info" %} -You can use dependency injection to inject any services you require to perform your specific task. When injecting dependencies, it's always recommended that you inject `Lazy` implementations of the required services to ensure they are only resolved when needed. -{% endhint %} - -## Controlling the action result - -Actions by default will return a `ActionResult` but you can return other types of result by swapping the `Action<>` generic argument. - -* **`ActionResult`** - Standard result with a boolean `Success` value. -* **`FileActionResult`** - Returns a file stream / bytes and triggers a download dialog. - -## Capturing settings for an action - -Sometimes you may need to collect further user input before you can perform an action. To achieve this you can use the `Action<>` base class that accepts an additional `TSetting` generic argument. - -````csharp -// Example -public class MyAction : Action -{ - public override string Icon => "icon-settings"; - public override string Alias => "myaction"; - public override string Name => "My Action"; - public override bool ConfirmAction => true; - - public override void Configure(SettingsConfigBuilder settingsConfig) - { - settingsConfig.AddFielset("General", fieldsetConfig => fieldsetConfig - .AddField(s => s.RecipientName).SetLabel("Recipient Name") - .AddField(s => s.RecipientEmail).SetLabel("Recipient Email")) - } - - public override ActionResult Execute(string collectionAlias, object[] entityIds, MyActionSettings settings) - { - // Perform operation here... - } -} - -public class MyActionSettings -{ - public string RecipientName { get; set; } - public string RecipientEmail { get; set; } -} -```` - -By implementing this base class you are required to implement an additional `Configure` method which accepts a `SettingsConfigBuilder<>` parameter. You should use this parameter calling the builders fluent API to define the settings dialog UI and how it maps to the settings type. With the settings config builder you are able to create fieldsets and fields with the same fluent API as defined in the [Collection Editors section](../collections/editors.md#adding-a-fieldset-to-a-tab). - -In addition to this `Configure` method, the `Execute` method will now accept an additional `settings` parameter of the settings type. This will be pre-populated by Umbraco UI Builder with the value entered by the user, allowing you to alter your actions behavior accordingly. - -## Adding an action to a collection - -Actions are added via the [Collections](../collections/overview.md) configuration. - -### **AddAction<TMenuActionType>() : CollectionConfigBuilder<TEntityType>** - -Adds an action of the given type to the collection. - -````csharp -// Example -collectionConfig.AddAction(); -```` - -#### **AddAction(Type actionType) : CollectionConfigBuilder<TEntityType>** - -Adds an action of the given type to the collection. - -````csharp -// Example -collectionConfig.AddAction(actionType); -```` - -#### **AddAction(IAction action) : CollectionConfigBuilder<TEntityType>** - -Adds the given action to the collection. - -````csharp -// Example -collectionConfig.AddAction(action); -```` diff --git a/14/umbraco-ui-builder/advanced/encrypted-properties.md b/14/umbraco-ui-builder/advanced/encrypted-properties.md deleted file mode 100644 index 7962111773b..00000000000 --- a/14/umbraco-ui-builder/advanced/encrypted-properties.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -description: Configuring encrypted properties in Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Encrypted Properties - -If needed to collect sensitive information in a collection but don't want to persist in a plain text format to the data storage mechanism. Umbraco UI Builder can help with this by allowing you to define properties as encrypted. After which any time the value is persisted or retrieved from persistence, Umbraco UI Builder will automatically encrypt and decrypt the value. - -{% hint style="info" %} -Umbraco UI Builder uses the `IDataProtectionProvider` instance registered in the DI container to perform its encryption/decryption. If you need to change the encryption algorithm, you should replace the `IDataProtectionProvider` instance in the DI container. -{% endhint %} - -## Defining encrypted properties - -### **AddEncryptedProperty(Lambda encryptedPropertyExpression) : CollectionConfigBuilder<TEntityType>** - -Adds the given property to the encrypted properties collection. Property must be of type `String`. When set, the property will be encrypted/decrypted on write/read respectively. - -````csharp -// Example -collectionConfig.AddEncryptedProperty(p => p.Secret); -```` diff --git a/14/umbraco-ui-builder/advanced/events.md b/14/umbraco-ui-builder/advanced/events.md deleted file mode 100644 index 78b7363d5ba..00000000000 --- a/14/umbraco-ui-builder/advanced/events.md +++ /dev/null @@ -1,145 +0,0 @@ ---- -description: Configuring event handlers in Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Events - -Umbraco UI Builder fires a number of notification events during regular operation to allow for extending of the default behaviour. - -## Registering event handlers - -Umbraco UI Builder uses the same [Notification Mechanism built into Umbraco v9+](../../umbraco-cms/fundamentals/code/subscribing-to-notifications.md) and so uses the same registration process. First you will need to define a notification event handler for the event you wish to handle like below: - -```csharp -public class MyEntitySavingEventHandler : INotificationHandler { - - public void Handle(EntitySavingNotification notification) - { - // Handle the event here - } - -} -``` - -Then register your event handler in the `Program.cs` file like below: - -```csharp -builder.CreateUmbracoBuilder() - .AddBackOffice() - .AddWebsite() - .AddDeliveryApi() - .AddComposers() - .AddNotificationHandler() - .Build(); -``` - -## Repository events - -### **EntitySavingNotification** - -Raised when the repository `Save` method is called and before the entity has been persisted. The notification contains an `Entity` property with `Before` and `After` inner properties. These properties provide access to a copy of the currently persisted entity (or null if a new entity) and the updated entity that´s saved. -Changes can be made to the `After` entity and they will be persisted as part of the save operation. If the `Cancel` property of the notification is set to `true` then the save operation will be canceled and no changes will be saved. - -````csharp -// Example -public class MyEntitySavingEventHandler : INotificationHandler { - - public void Handle(EntitySavingNotification notification) - { - var person = notification.Entity.After as Person; - if (person != null){ - ... - } - } - -} -```` - -### **EntitySavedNotification** - -Raised when the repository `Save` method is called and after the entity has been persisted. The notification contains an `Entity` property with `Before` and `After` inner properties. These properties provide access to a copy of the previously persisted entity (or null if a new entity) and the updated entity that´s saved. - -````csharp -// Example -public class MyEntitySavedEventHandler : INotificationHandler { - - public void Handle(EntitySavedNotification notification) - { - var person = notification.Entity.After as Person; - if (person != null){ - ... - } - } - -} -```` - -### **EntityDeletingNotification** - -Raised when the repository `Delete` method is called and **before** the entity is deleted. The notification contains an `Entity` property providing access to a copy of the entity about to be deleted. If the `Cancel` property of notification is set to `true` then the delete operation will be cancelled and entity won't be deleted. - -````csharp -// Example -public class MyEntityDeletingEventHandler : INotificationHandler { - - public void Handle(EntityDeletingNotification notification) - { - var person = notification.Entity.After as Person; - if (person != null){ - ... - } - } - -} -```` - -### **EntityDeletedNotification** - -Raised when the repository `Delete` method is called and **after** the entity has been deleted. The notification contains an `Entity` property providing access to a copy of the entity that´s deleted. - -````csharp -// Example -public class MyEntityDeletedEventHandler : INotificationHandler { - - public void Handle(EntityDeletedNotification notification) - { - var person = notification.Entity.After as Person; - if (person != null){ - ... - } - } - -} -```` - -### **SqlQueryBuildingNotification** - -Raised when the repository is **preparing** a SQL query. The notification contains the collection alias + type, the NPoco `Sql` object, and the where clause/order by clauses. These will be used to generate the SQL query. - -````csharp -// Example -public class MySqlQueryBuildingEventHandler : INotificationHandler { - - public void Handle(SqlQueryBuildingNotification notification) - { - notification.Sql = notification.Sql.Append("WHERE MyId = @0", 1); - } - -} -```` - -### **SqlQueryBuiltNotification** - -Raised when the repository has **repaired** a SQL query. The notification contains the collection alias + type, the NPoco `Sql` object and the where clause/order by clauses that was used to generate the SQL query. - -````csharp -// Example -public class MySqlQueryBuiltEventHandler : INotificationHandler { - - public void Handle(SqlQueryBuiltNotification notification) - { - notification.Sql = notification.Sql.Append("WHERE MyId = @0", 1); - } - -} -```` diff --git a/14/umbraco-ui-builder/advanced/repositories.md b/14/umbraco-ui-builder/advanced/repositories.md deleted file mode 100644 index f49db720184..00000000000 --- a/14/umbraco-ui-builder/advanced/repositories.md +++ /dev/null @@ -1,120 +0,0 @@ ---- -description: Configuring repositories in Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Repositories - -Repositories are used by Umbraco UI Builder to access the entity data stores. By default, collections will use a generic built-in NPoco repository. However, you can define your own repository implementation should you wish to store your entities via an alternative strategy. - -## Defining a repository - -To define a repository create a class that inherits from the base class `Repository` and implements all of its abstract methods. - -````csharp -// Example -public class PersonRepository : Repository { - - public PersonRepository(RepositoryContext context) - : base(context) - { } - - protected override int GetIdImpl(Person entity) { - return entity.Id; - } - - protected override Person GetImpl(int id) { - ... - } - - protected override Person SaveImpl(Person entity) { - ... - } - - protected override void DeleteImpl(int id) { - ... - } - - protected override IEnumerable GetAllImpl(Expression> whereClause, Expression> orderBy, SortDirection orderByDirection) { - ... - } - - protected override PagedResult GetPagedImpl(int pageNumber, int pageSize, Expression> whereClause, Expression> orderBy, SortDirection orderByDirection) { - ... - } - - protected override long GetCountImpl(Expression> whereClause) { - ... - } - - protected override IEnumerable GetRelationsByParentIdImpl(int parentId, string relationAlias) - { - ... - } - - protected override TJunctionEntity SaveRelationImpl(TJunctionEntity entity) - { - ... - } -} -```` - -**Note:** For all `Impl` methods there are public alternatives without the `Impl` suffix. However, there are separate implementation methods in order to ensure all repositories fire the relevant Umbraco UI Builder events. This is whether triggered via the Umbraco UI Builder's UI or not. - -## Changing the repository implementation of a collection - -### **SetRepositoryType<TRepositoryType>() : CollectionConfigBuilder<TEntityType>** - -Sets the repository type to the given type for the current collection. - -````csharp -// Example -collectionConfig.SetRepositoryType(); -```` - -### **SetRepositoryType(Type repositoryType) : CollectionConfigBuilder<TEntityType>** - -Sets the repository type to the given type for the current collection. - -````csharp -// Example -collectionConfig.SetRepositoryType(typeof(PersonRepositoryType)); -```` - -## Accessing a repository in code - -To help with accessing a repository (default or custom) Umbraco UI Builder has an `IRepositoryFactory` you can inject into your code base. This includes a couple of factory methods to create the repository instances for you. -Repositories should only be created via the repository factory as there are some injected dependencies that can only be resolved by Umbraco UI Builder. - -### **IRepositoryFactory.GetRepository<TEntity, TId>() : Repository<TEntity, TId>** - -Creates a repository for the given entity type. Umbraco UI Builder will search the configuration for the first section/collection with a configuration for the given entity type. Then it will use that as a repository configuration. - -````csharp -// Example -public class MyController : Controller -{ - private readonly Repository _repo; - - public MyController(IRepositoryFactory repoFactory) - { - _repo = repoFactory.GetRepository(); - } -} -```` - -### **IRepositoryFactory.GetRepository<TEntity, TId>(string collectionAlias) : Repository<TEntity, TId>** - -Creates a repository for the given entity type from the collection with the given alias. - -````csharp -// Example -public class MyController : Controller -{ - private readonly Repository _repo; - - public MyController(IRepositoryFactory repoFactory) - { - _repo = repoFactory.GetRepository("person"); - } -} -```` diff --git a/14/umbraco-ui-builder/advanced/value-mappers.md b/14/umbraco-ui-builder/advanced/value-mappers.md deleted file mode 100644 index e49f44aadd7..00000000000 --- a/14/umbraco-ui-builder/advanced/value-mappers.md +++ /dev/null @@ -1,62 +0,0 @@ ---- -description: Configuring value mappers in Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Value Mappers - -A value mapper is an Umbraco UI Builder helper class that sits between the editor UI and the database. It also lets you tweak the stored value of a field. By default Umbraco UI Builder will save a datatype value as it would be stored in Umbraco. Value mappers let you change this. - -When Umbraco UI Builder resolves a value mapper it will attempt to do so from the global DI container. This means you can inject any dependencies that you require for your mapper. If there is no type defined in the DI container, Umbraco UI Builder will fall-back to manually instantiating a new instance of value mapper. - -## Defining a value mapper - -To define a mapper create a class that inherits from the base class `ValueMapper` and implements the methods `EditorToModel` and `ModelToEditor`. - -````csharp -// Example -public class MyValueMapper : ValueMapper -{ - public override object EditorToModel(object input) - { - // Tweak the input and return mapped object - ... - } - - public override object ModelToEditor(object input) - { - // Tweak the input and return mapped object - ... - } -} -```` - -## Setting a field value mapper - -Value mappers are defined as part of a collection editor field configuration. - -### **SetValueMapper<TMapperType>() : EditorFieldConfigBuilder<TEntityType, TValueType>** - -Set the value mapper for the current field. - -````csharp -// Example -fieldConfig.SetValueMapper(); -```` - -### **SetValueMapper(Type mapperType) : EditorFieldConfigBuilder<TEntityType, TValueType>** - -Set the value mapper for the current field. - -````csharp -// Example -fieldConfig.SetValueMapper(typeof(MyValueMapper)); -```` - -### **SetValueMapper(Mapper mapper) : EditorFieldConfigBuilder<TEntityType, TValueType>** - -Set the value mapper for the current field. - -````csharp -// Example -fieldConfig.SetValueMapper(new MyValueMapper()); -```` diff --git a/14/umbraco-ui-builder/advanced/virtual-sub-trees.md b/14/umbraco-ui-builder/advanced/virtual-sub-trees.md deleted file mode 100644 index 3394a2f20e1..00000000000 --- a/14/umbraco-ui-builder/advanced/virtual-sub-trees.md +++ /dev/null @@ -1,141 +0,0 @@ ---- -description: Configuring virtual sub trees in Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Virtual SubTrees - -{% hint style="warning" %} -This page is a work in progress and may undergo further revisions, updates, or amendments. The information contained herein is subject to change without notice. -{% endhint %} - -Virtual subtrees are a powerful feature that allows you to inject an Umbraco UI Builder tree structure into another Umbraco tree at a desired location. Thus acting as child nodes to the node chosen as the injection point. With virtual subtrees it allows you to extend built in or even 3rd party package trees with additional features. An example could be developing a "loyalty point" program for your e-commerce site and injecting the related database tables into a Vendr store tree. This allows the management of the program in its most logical location. - -![Example virtual sub tree injected into a Vendr store tree](../images/virtual-sub-tree.png) - -## Defining virtual SubTrees - -You define a virtual subtree by calling one of the `AddVirtualSubTree` methods of a [`WithTreeConfigBuilder`](../areas/trees.md#extending-an-existing-tree) instance. - -### **AddVirtualSubTree(string sectionAlias, string treeAlias, Lambda visibilityExpression, Lambda virtualSubTreeConfig = null) : VirtualSubTreeConfigBuilder** - -Adds a virtual subtree to the current tree with its visibility controlled via the visibility expression. - -````csharp -// Example -withTreeConfig.AddVirtualSubTree(ctx => ctx.Source.Id == 1056, contextAppConfig => { - ... -}); -```` - -### **AddVirtualSubTreeBefore(string sectionAlias, string treeAlias, Lambda visibilityExpression, Lambda matchExpression, Lambda virtualSubTreeConfig = null) : VirtualSubTreeConfigBuilder** - -Adds a virtual subtree to the current tree, **before** the tree node matches the match expression, with its visibility controlled via the visibility expression. - -````csharp -// Example -withTreeConfig.AddVirtualSubTreeBefore(ctx => ctx.Source.Id == 1056, treeNode => treeNode.Name == "Settings", contextAppConfig => { - ... -}); -```` - -### **AddVirtualSubTreeAfter(string sectionAlias, string treeAlias, Lambda visibilityExpression, Lambda matchExpression, Lambda virtualSubTreeConfig = null) : VirtualSubTreeConfigBuilder** - -Adds a virtual subtree to the current tree, **after** the tree node matches the match expression, with its visibility controlled via the visibility expression. - -````csharp -// Example -withTreeConfig.AddVirtualSubTreeAfter(ctx => ctx.Source.Id == 1056, treeNode => treeNode.Name == "Settings", contextAppConfig => { - ... -}); -```` - -## Controlling where to inject the Virtual SubTrees - -Controlling where a virtual subtree is injected is done via the visibility expression passed to one of the `AddVirtualSubTree` methods on the root `UIBuilderConfigBuilder` instance. Without a visibility expression, Umbraco UI Builder would inject the virtual subtree under every node in the given tree. This expression can be used to identify the exact location where our tree should go. - -To help with this, the visibility expression is passed a single `VirtualSubTreeFilterContext` argument with relevant contextual information. This information is about the current node being rendered, alongside a list of the current user's user groups for permission-based visibility control. It also includes access to an `IServiceProvider` in case you need to resolve a service to determine the correct node to inject below. - -````csharp -public class VirtualSubTreeFilterContext -{ - public NodeContext Source { get; } - public IEnumerable UserGroups { get; } - public IServiceProvider ServiceProvider { get; } -} - -public class NodeContext -{ - public string Id { get; } - public string TreeAlias { get; } - public string SectionAlias { get; } - public FormCollection QueryString { get; } -} -```` - -Below you can find an example of a more complex filter expression where injection is based on the Document Type of a content node: - -````csharp -withTreeConfig.AddVirtualSubTree(ctx => - { - using var umbracoContextRef = ctx.ServiceProvider.GetRequiredService().EnsureUmbracoContext(); - - if (!int.TryParse(ctx.Source.Id, out int id)) - return false; - - return (umbracoContextRef.UmbracoContext.Content.GetById(id)?.ContentType.Alias ?? "") == "textPage"; - }, - virtualNodeConfig => virtualNodeConfig - ... -); -```` - -## Controlling the position of the injected Virtual SubTrees - -The position of a virtual subtree within the child nodes of the injection node is controlled by using one of the `AddVirtualSubTreeBefore` or `AddVirtualSubTreeAfter` methods. These methods need to be on the root level `UIBuilderConfigBuilder` instance and pass a match expression used to identify the tree node to insert before/after. This expression is passed a single `TreeNode` argument to determine the position. It also requires a `boolean` return value to indicate the relevant location has been found. - -````csharp -public class TreeNode -{ - public object Id { get; } - public object ParentId { get; } - public string Alias { get; } - public string Name { get; } - public string NodeType { get; } - public string Path { get; } - public string RoutePath { get; } - public IDictionary AdditionalData { get; } - ... -} -```` - -Below you can find an example of positioning a subtree after a node with the alias "settings": - -````csharp -treeNode => treeNode.alias == "settings" -```` - -## Configuring a Virtual SubTrees - -Virtual subtrees share the same API as the `Tree` config builder API including support for folders and collections. There is an exception when adding collections to a subtree where you will have an additional foreign key expression parameter to define. The foreign key expression links the entities of the collection to the parent node of the subtree. For more information check the [Core Trees Documentation](../areas/trees.md). - -## Injecting Virtual SubTrees into 3rd party trees - -Out of the box, Umbraco UI Builder supports injecting subtrees into the core content, media, members, and member group trees. It also includes 3rd party support for [Umbraco Commerce](../../umbraco-commerce/README.md) settings and commerce trees. In order to support additional trees to inject into, you must implement an `ITreeHelper` which is used to extract the required information. The tree helper consists of a tree alias for which the tree helper is. It includes methods to correctly identify the full parent path, a unique ID for a given node ID, and to resolve the actual entity ID. The entity ID should be used for the foreign key collection values. - -````csharp -public interface ITreeHelper -{ - string TreeAlias { get; } - string GetUniqueId(string nodeId, FormCollection queryString); - object GetEntityId(string uniqueId); - string GetPath(string uniqueId); -} -```` - -Once you have defined a tree helper, you can register the DI container in your startup class. - -````csharp -builder.Services.AddSingleton(); -```` - -Once registered any virtual subtrees registered against the given helpers tree alias will then use your tree helper to locate the required information. diff --git a/14/umbraco-ui-builder/areas/context-apps.md b/14/umbraco-ui-builder/areas/context-apps.md deleted file mode 100644 index ad04cf5d62d..00000000000 --- a/14/umbraco-ui-builder/areas/context-apps.md +++ /dev/null @@ -1,144 +0,0 @@ ---- -description: Configuring context apps in Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Context Apps - -Context Apps in Umbraco UI Builder are analogous to Content Apps in Umbraco. They allow you to provide contextual apps that appear in the editor UI of content. From Umbraco UI Builder's perspective, defining context apps allows you to expose collections as content apps. This is where a collection has a relation to the content in question. An example could be something like blog post comments which are linked to individual blog posts. Exposing these as a content app allows them to be managed in context next to the blog post they are linked to. - -![Context App](../images/context_app.png) - -## Defining a context app - -You can define a context app by calling one of the `AddContextApp` methods on a [`WithTreeConfigBuilder`](trees.md#extending-an-existing-tree) instance. - -### **AddContextApp(string name, Lambda contextAppConfig = null) : ContextAppConfigBuilder** - -Adds a context app with the given name and default icon. - -```csharp -// Example -withTreeConfig.AddContextApp("Comments", contextAppConfig => { - ... -}); -``` - -### **AddContextApp(string name, string icon, Lambda contextAppConfig = null) : ContextAppConfigBuilder** - -Adds a context app to the Umbraco menu with the given name and icon. - -```csharp -// Example -withTreeConfig.AddContextApp("Comments", "icon-chat", contextAppConfig => { - ... -}); -``` - -### **AddContextAppBefore(string beforeAlias, string name, Lambda contextAppConfig = null) : ContextAppConfigBuilder** - -Adds a context app with the given name and default icon **before** the context app with the given alias. - -```csharp -// Example -withTreeConfig.AddContextAppBefore("umbContent", "Comments", contextAppConfig => { - ... -}); -``` - -### **AddContextAppBefore(string beforeAlias, string name, string icon, Lambda contextAppConfig = null) : ContextAppConfigBuilder** - -Adds a context app to the Umbraco menu with the given name and icon **before** the context app with the given alias. - -```csharp -// Example -withTreeConfig.AddContextAppBefore("umbContent", "Comments", "icon-chat", contextAppConfig => { - ... -}); -``` - -### **AddContextAppAfter(string afterAlias, string name, Lambda contextAppConfig = null) : ContextAppConfigBuilder** - -Adds a context app with the given name and default icon **after** the context app with the given alias. - -```csharp -// Example -withTreeConfig.AddContextAppAfter("umbContent", "Comments", contextAppConfig => { - ... -}); -``` - -### **AddContextAppAfter(string afterAlias, string name, string icon, Lambda contextAppConfig = null) : ContextAppConfigBuilder** - -Adds a context app to the Umbraco menu with the given name and icon **after** the context app with the given alias. - -```csharp -// Example -withTreeConfig.AddContextAppAfter("umbContent", "Comments", "icon-chat", contextAppConfig => { - ... -}); -``` - -## Changing a context app alias - -### **SetAlias(string alias) : ContextAppConfigBuilder** - -Sets the alias of the context app. - -**Optional:** When adding a new context app, an alias is automatically generated from the supplied name for you. However, you can use the `SetAlias` method to override this if you need a specific alias. - -```csharp -// Example -contextAppConfig.SetAlias("comments"); -``` - -## Changing a context app icon color - -### **SetIconColor(string color) : ContextAppConfigBuilder** - -Sets the context app icon color to the given color. Possible options are `black`, `green`, `yellow`, `orange`, `blue` or `red`. - -````csharp -// Example -contextAppConfig.SetIconColor("blue"); -```` - -## Changing when a context app should display - -Changing when a context app is displayed, is controlled by a delegate method which is passed a `ContextAppVisibilityContext` instance. This method contains a `Source` property which holds a reference to the source object that the content app is being displayed on (i.e., an `IContent` instance). It also holds a reference to a `UserGroups` collection of the currently logged-in user's user groups. You can use any value from those to return a boolean result which sets whether to display the context app or not. - -By default, Umbraco UI Builder will pre-filter context apps to only display on the tree it is defined in. This will be combined with the `SetVisibility` config to decide when to display the context app. - -### **SetVisibility(Func<ContextAppVisibilityContext, bool> visibilityExpression) : ContextAppConfigBuilder** - -Sets the context app visibility delegate. - -````csharp -// Example -contextAppConfig.SetVisibility(appCtx => appCtx.Source is IContent content && content.ContentType.Alias == "blogPost"); -```` - -## Adding a collection to a context app - -Context apps can consist of one or more collections. If a context app contains multiple collections, the collection list views will be displayed in tabs within the context app. - -### **AddCollection<TEntityType>(Lambda idFieldExpression, Lambda fkFieldExpression, string nameSingular, string namePlural, string description, Lambda collectionConfig = null) : ContextAppConfigBuilder** - -Adds a collection to the current content app with the given names, descriptions and default icons. An ID property accessor expression is required so that Umbraco UI Builder knows which property is the ID property. A foreign key property accessor is also required so that the Umbraco UI Builder knows which property holds the Umbraco nodes UDI value. You can read more about this in the [Collections documentation](../collections/overview.md). - -```csharp -// Example -contextAppConfig.AddCollection(p => p.Id, p=> "Comment", "Comments", "A collection of comments", collectionConfig => { - ... -}); -``` - -### **AddCollection<TEntityType>(Lambda idFieldExpression, Lambda fkFieldExpression, string nameSingular, string namePlural, string description, string iconSingular, string iconPlural, Lambda collectionConfig = null) : ContextAppConfigBuilder** - -Adds a collection to the current context app with the given names, description and icons. An ID property accessor expression is required so that Umbraco UI Builder knows which property is the ID property. A foreign key property accessor is also required so that Umbraco UI Builder knows which property holds the Umbraco nodes UDI value. You can read more about this in the [Collections documentation](../collections/overview.md). - -```csharp -// Example -contextAppConfig.AddCollection(p => p.Id, "Comment", "Comments", "A collection of comments", "icon-chat", "icon-chat", collectionConfig => { - ... -}); -``` diff --git a/14/umbraco-ui-builder/areas/dashboards.md b/14/umbraco-ui-builder/areas/dashboards.md deleted file mode 100644 index 3a84ba959ff..00000000000 --- a/14/umbraco-ui-builder/areas/dashboards.md +++ /dev/null @@ -1,103 +0,0 @@ ---- -description: Configuring dashboards in Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Dashboards - -A dashboard is a view that is displayed at the root of a section and contains welcome information. It also includes useful tools relevant to the given section. When there are multiple dashboards to display in a section these are presented in a tabbed layout to allow you to switch between the dashboards. - -![Dashboards](../images/dashboards.png) - -## Defining a dashboard - -You can define a dashboard by calling one of the `AddDashboard` methods on either a [`SectionConfigBuilder`](sections.md) or a [`WithSectionConfigBuilder`](sections.md#extending-an-existing-section) instance. - -### **AddDashboard(string name, Lambda dashboardConfig = null) : DashboardConfigBuilder** - -Adds a dashboard with the given name. - -```csharp -// Example -sectionConfig.AddDashboard("Team", dashboardConfig => { - ... -}); -``` - -### **AddDashboardBefore(string beforeAlias, string name, Lambda dashboardConfig = null) : DashboardConfigBuilder** - -Adds a dashboard with the given name **before** the dashboard with the given alias. - -```csharp -// Example -sectionConfig.AddDashboardBefore("contentIntro", "Team", dashboardConfig => { - ... -}); -``` - -### **AddDashboardAfter(string afterAlias, string name, Lambda dashboardConfig = null) : DashboardConfigBuilder** - -Adds a dashboard with the given name **after** the dashboard with the given alias. - -```csharp -// Example -sectionConfig.AddDashboardAfter("contentIntro", "Team", dashboardConfig => { - ... -}); -``` - -## Changing a dashboard alias - -### **SetAlias(string alias) : DashboardConfigBuilder** - -Sets the alias of the dashboard. - -**Optional:** When adding a new dashboard, an alias is automatically generated from the supplied name for you. However, if you need a specific alias you can use the `SetAlias` method to override this. - -```csharp -// Example -dashboardConfig.SetAlias("team"); -``` - -## Changing when a dashboard should display - -Changing when a dashboard is displayed is controlled via an inner config. Options on the inner config are `ShowForUserGroup` and `HideForUserGroup` to control the visibility of the dashboard for given user groups. You can call these config methods multiple times to add multiple role configurations. - -By default, will pre-filter dashboards to display only on the section it is defined in. This will be combined with the `SetVisibility` config to decide when to display the dashboard. - -### **SetVisibility(Lambda visibilityConfig) : DashboardConfigBuilder** - -Sets the dashboard visibility config. - -````csharp -// Example -dashboardConfig.SetVisibility(visibilityConfig => visibilityConfig - .ShowForUserGroup("admin") - .HideForUserGroup("translator") -); -```` - -## Setting the collection of a dashboard - -Dashboards are only able to display a single collection. If you need to display multiple collections, then you need to configure multiple dashboards. - -### **SetCollection<TEntityType>(Lambda idFieldExpression, string nameSingular, string namePlural, string description, Lambda collectionConfig = null) : ContextAppConfigBuilder** - -Sets the collection of the current dashboard with the given names, descriptions, and default icons. An ID property accessor expression is required so that Umbraco UI Builder knows which property is the ID property. For more information check the [Collections documentation](../collections/overview.md). - -```csharp -// Example -dashboardConfig.SetCollection(p => p.Id, p=> "Team Member", "Team Members", "A collection of team members", collectionConfig => { - ... -}); -``` - -### **SetCollection<TEntityType>(Lambda idFieldExpression, Lambda fkFieldExpression, string nameSingular, string namePlural, string description, string iconSingular, string iconPlural, Lambda collectionConfig = null) : ContextAppConfigBuilder** - -Sets the collection of the current dashboard with the given names, description and icons. An ID property accessor expression is required so that Umbraco UI Builder knows which property is the ID property. For more information check the [Collections documentation](../collections/overview.md). - -```csharp -// Example -dashboardConfig.SetCollection(p => p.Id, "Team Member", "Team Members", "A collection of team members", "icon-umm-user", "icon-umb-user", collectionConfig => { - ... -}); -``` diff --git a/14/umbraco-ui-builder/areas/folders.md b/14/umbraco-ui-builder/areas/folders.md deleted file mode 100644 index 4f9017346fd..00000000000 --- a/14/umbraco-ui-builder/areas/folders.md +++ /dev/null @@ -1,107 +0,0 @@ ---- -description: Configuring folders to organise trees in Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Folders - -A folder can appear in either a tree or as a sub folder to other folders. Folders can contain either other (sub)folders or [collections](../collections/overview.md). - -![Tree with Settings folder](../images/tree.png) - -## Defining a folder - -You can define a folder by calling one of the `AddFolder` methods on a given [`Tree`](trees.md) or parent `Folder` config builder instance. - -### **AddFolder(string name, Lambda folderConfig = null) : FolderConfigBuilder** - -Adds a folder to the current tree with the given name and a default folder icon. - -````csharp -// Example -treeConfig.AddFolder("Settings", folderConfig => { - ... -}); -```` - -### **AddFolder(string name, string icon, Lambda folderConfig = null) : FolderConfigBuilder** - -Adds a folder to the current tree with the given name + icon. - -````csharp -// Example -treeConfig.AddFolder("Settings", "icon-settings", folderConfig => { - ... -}); -```` - -## Changing a folder alias - -### **SetAlias(string alias) : FolderConfigBuilder** - -Sets the alias of the folder. - -**Optional:** When creating a new folder, an alias is automatically generated from the supplied name for you. However, if you need a specific alias you can use the `SetAlias` method to override this. - -````csharp -// Example -folderConfig.SetAlias("settings"); -```` - -## Changing a folder icon color - -### **SetIconColor(string color) : FolderConfigBuilder** - -Sets the folder icon color to the given color. The options that are possible are `black`, `green`, `yellow`, `orange`, `blue` or `red`. - -````csharp -// Example -folderConfig.SetIconColor("blue"); -```` - -## Adding a sub folder to a folder - -### **AddFolder (string name, Lambda folderConfig = null) : FolderConfigBuilder** - -Adds a sub folder to the current folder with the given name and a default folder icon. - -````csharp -// Example -folderConfig.AddFolder("Categories", subFolderConfig => { - ... -}); -```` - -### **AddFolder (string name, string icon, Lambda folderConfig = null) : FolderConfigBuilder** - -Adds a sub folder to the current folder with the given name + icon. - -````csharp -// Example -folderConfig.AddFolder("Categories", "icon-tags", subFolderConfig => { - ... -}); -```` - -## Adding a collection to a folder - -### **AddCollection<TEntityType>(Lambda idFieldExpression, string nameSingular, string namePlural, string description, Lambda collectionConfig = null) : CollectionConfigBuilder<TEntityType>** - -Adds a collection to the current folder with the given names, descriptions, and default icons. An ID property accessor expression is required so that Umbraco UI Builder knows which property is the ID property. For more information check the [Collections documentation](../collections/overview.md). - -````csharp -// Example -folderConfig.AddCollection(p => p.Id, "Person", "People", "A collection of people", collectionConfig => { - ... -}); -```` - -### **AddCollection<TEntityType>(Lambda idFieldExpression, string nameSingular, string namePlural, string description, string iconSingular, string iconPlural, Lambda collectionConfig = null) : CollectionConfigBuilder<TEntityType>** - -Adds a collection to the current folder with the given names, description and icons. An ID property accessor expression is required so that Umbraco UI Builder knows which property is the ID property. For more information check the [Collections documentation](../collections/overview.md). - -````csharp -// Example -folderConfig.AddCollection(p => p.Id, "Person", "People", "A collection of people", "icon-umb-users", "icon-umb-users", collectionConfig => { - ... -}); -```` diff --git a/14/umbraco-ui-builder/areas/overview.md b/14/umbraco-ui-builder/areas/overview.md deleted file mode 100644 index 49e31b9031c..00000000000 --- a/14/umbraco-ui-builder/areas/overview.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -description: Choosing an area to connect Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Areas - -There are different areas of the Umbraco UI that Umbraco UI Builder can be injected into. Before you get to managing your actual content you need to choose which area makes the most sense to present that data in. Then you can review how to go about configuring that particular type of area. - -Choose an area type from the list below to find out more. - -{% content-ref url="sections.md" %} -[sections.md](sections.md) -{% endcontent-ref %} -{% content-ref url="dashboards.md" %} -[dashboards.md](dashboards.md) -{% endcontent-ref %} -{% content-ref url="context-apps.md" %} -[context-apps.md](context-apps.md) -{% endcontent-ref %} diff --git a/14/umbraco-ui-builder/areas/sections.md b/14/umbraco-ui-builder/areas/sections.md deleted file mode 100644 index 3ac357ad3d9..00000000000 --- a/14/umbraco-ui-builder/areas/sections.md +++ /dev/null @@ -1,203 +0,0 @@ ---- -description: Configuring sections in Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Sections - -A section is a distinct area of the Umbraco backoffice, such as content, media, etc. The section is accessed via a link in the main menu at the top of the Umbraco interface. Umbraco UI Builder allows you to define multiple sections in order to organise the management of your models into logical sections. - -![Sections](../images/sections.png) - -## Defining a section - -You can define a section by calling one of the `AddSection` methods on the root level `UIBuilderConfigBuilder` instance. - -### **AddSection(string name, Lambda sectionConfig = null) : SectionConfigBuilder** - -Adds a section to the Umbraco menu with the given name. - -```csharp -// Example -config.AddSection("Repositories", sectionConfig => { - ... -}); -``` - -### **AddSectionBefore(string beforeAlias, string name, Lambda sectionConfig = null) : SectionConfigBuilder** - -Adds a section to the Umbraco menu with the given name **before** the section with the given alias. - -```csharp -// Example -config.AddSectionBefore("settings", "Repositories", sectionConfig => { - ... -}); -``` - -### **AddSectionAfter(string afterAlias, string name, Lambda sectionConfig = null) : SectionConfigBuilder** - -Adds a section to the Umbraco menu with the given name **after** the section with the given alias. - -```csharp -// Example -config.AddSectionAfter("media", "Repositories", sectionConfig => { - ... -}); -``` - -## Changing a section alias - -### **SetAlias(string alias) : SectionConfigBuilder** - -Sets the alias of the section. - -**Optional:** When adding a new section, an alias is automatically generated from the supplied name for you. However, if you need a specific alias you can use the `SetAlias` method to override this. - -```csharp -// Example -sectionConfig.SetAlias("repositories"); -``` - -## Configuring the section tree - -### **Tree(Lambda treeConfig = null) : TreeConfigBuilder** - -Accesses the tree config of the current section. For more information check the [Trees documentation](trees.md). - -````csharp -// Example -sectionConfig.Tree(treeConfig => { - ... -}); -```` - -## Adding a dashboard to the section - -### **AddDashboard(string name, Lambda dashboardConfig = null) : DashboardConfigBuilder** - -Adds a dashboard with the given name. For more information check the [Dashboards documentation](dashboards.md). - -```csharp -// Example -sectionConfig.AddDashboard("Team", dashboardConfig => { - ... -}); -``` - -#### **AddDashboardBefore(string beforeAlias, string name, Lambda dashboardConfig = null) : DashboardConfigBuilder** - -Adds a dashboard with the given name **before** the dashboard with the given alias. For more information check the [Dashboards documentation](dashboards.md). - -```csharp -// Example -sectionConfig.AddDashboardBefore("contentIntro", "Team", dashboardConfig => { - ... -}); -``` - -#### **AddDashboardAfter(string afterAlias, string name, Lambda dashboardConfig = null) : DashboardConfigBuilder** - -Adds a dashboard with the given name **after** the dashboard with the given alias. For more information check the [Dashboards documentation](dashboards.md). - -```csharp -// Example -sectionConfig.AddDashboardAfter("contentIntro", "Team", dashboardConfig => { - ... -}); -``` - -## Extending an existing section - -You can extend existing sections by adding Umbraco UI Builder trees and dashboards, context apps, and virtual subtrees. This can be done by calling the `WithSection` method on the root level `UIBuilderConfigBuilder` instance. - -### **WithSection(string alias, Lambda sectionConfig = null) : WithSectionConfigBuilder** - -Starts a sub-configuration for the existing Umbraco section with the given alias. - -```csharp -// Example -config.WithSection("member", withSectionConfig => { - ... -}); -``` - -## Adding a tree to an existing section - -### **AddTree(string name, string icon, Lambda treeConfig = null) : TreeConfigBuilder** - -Adds a tree to the current section. For more information check the [Trees documentation](trees.md). - -````csharp -// Example -withSectionConfig.AddTree("My Tree", "icon-folder", treeConfig => { - ... -}); -```` - -#### **AddTree(string groupName, string name, string icon, Lambda treeConfig = null) : TreeConfigBuilder** - -Adds a tree to the current section in a group with the given name. For more information check the [Trees documentation](trees.md). - -````csharp -// Example -withSectionConfig.AddTree("My Group", "My Tree", "icon-folder", treeConfig => { - ... -}); -```` - -#### **AddTreeBefore(string treeAlias, string name, string icon, Lambda treeConfig = null) : TreeConfigBuilder** - -Adds a tree to the current section **before** the tree with the given alias. For more information check the [Trees documentation](trees.md). - -````csharp -// Example -withSectionConfig.AddTreeBefore("member", "My Tree", "icon-folder", treeConfig => { - ... -}); -```` - -#### **AddTreeAfter(string treeAlias, string name, string icon, Lambda treeConfig = null) : TreeConfigBuilder** - -Adds a tree to the current section **after** the tree with the given alias. For more information check the [Trees documentation](trees.md). - -````csharp -// Example -withSectionConfig.AddTreeAfter("member", "My Tree", "icon-folder", treeConfig => { - ... -}); -```` - -## Adding a dashboard to an existing section - -### **AddDashboard (string name, Lambda dashboardConfig = null) : DashboardConfigBuilder** - -Adds a dashboard with the given name. For more information check the [Dashboards documentation](dashboards.md). - -```csharp -// Example -withSectionConfig.AddDashboard("Team", dashboardConfig => { - ... -}); -``` - -### **AddDashboardBefore (string beforeAlias, string name, Lambda dashboardConfig = null) : DashboardConfigBuilder** - -Adds a dashboard with the given name **before** the dashboard with the given alias. For more information check the [Dashboards documentation](dashboards.md). - -```csharp -// Example -withSectionConfig.AddDashboardBefore("contentIntro", "Team", dashboardConfig => { - ... -}); -``` - -### **AddDashboardAfter (string afterAlias, string name, Lambda dashboardConfig = null) : DashboardConfigBuilder** - -Adds a dashboard with the given name **after** the dashboard with the given alias. For more information check the [Dashboards documentation](dashboards.md). - -```csharp -// Example -withSectionConfig.AddDashboardAfter("contentIntro", "Team", dashboardConfig => { - ... -}); -``` diff --git a/14/umbraco-ui-builder/areas/summary-dashboards.md b/14/umbraco-ui-builder/areas/summary-dashboards.md deleted file mode 100644 index c17dbb5bdb9..00000000000 --- a/14/umbraco-ui-builder/areas/summary-dashboards.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -description: Configuring a summary dashboard in Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Summary Dashboards - -A summary dashboard is automatically displayed at the root of a defined Umbraco UI Builder section. It displays summaries of collections found within it that are told to display on the dashboard. It also provides quick links to jump to that collections list view. It can also add quickly a new entry to that collection (if the collection isn't read-only). - -![Summary Dashboard](../images/dashboard.png) - -## Showing a collection on a summary dashboard - -Showing a collection in the summary dashboard is controlled via the collection configuration. - -### **ShowOnSummaryDashboard() : CollectionConfigBuilder<TEntityType>** - -Sets the collection to display on the summary dashboard. - -````csharp -// Example -collectionConfig.ShowOnSummaryDashboard(); -```` - -{% hint style="warning" %} -Only section root level collections can be shown on the summary dashboard. -{% endhint %} diff --git a/14/umbraco-ui-builder/areas/trees.md b/14/umbraco-ui-builder/areas/trees.md deleted file mode 100644 index 551f95bbc4d..00000000000 --- a/14/umbraco-ui-builder/areas/trees.md +++ /dev/null @@ -1,235 +0,0 @@ ---- -description: Configuring trees in Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Trees - -A tree is a hierarchical structure that helps organize a section into logical sub-sections. A tree is accessed in the main side panel of the Umbraco interface. In Umbraco UI Builder, a section may only have a single tree definition. However, you can use folder nodes to help organize the tree structure as you need it. - -![Tree](../images/tree.png) - -## Configuring a Umbraco UI Builder section tree - -The tree configuration for Umbraco UI Builder sections is a sub-configuration of a [`Section`](sections.md) config builder instance and is accessed via its `Tree` method. - -### **Tree(Lambda treeConfig = null) : TreeConfigBuilder** - -Accesses the tree config of the given section. - -````csharp -// Example -sectionConfig.Tree(treeConfig => { - ... -}); -```` - -## Adding a tree to an existing section - -The tree configuration for existing sections is a sub-configuration of a [`WithSection`](sections.md#extending-an-existing-section) config builder instance and is accessed via one of its `AddTree` methods. - -### **AddTree(string name, string icon, Lambda treeConfig = null) : TreeConfigBuilder** - -Adds a tree to the current section. - -````csharp -// Example -withSectionConfig.AddTree("My Tree", "icon-folder", treeConfig => { - ... -}); -```` - -### **AddTree(string groupName, string name, string icon, Lambda treeConfig = null) : TreeConfigBuilder** - -Adds a tree to the current section in a group with the given name. - -````csharp -// Example -withSectionConfig.AddTree("My Group", "My Tree", "icon-folder", treeConfig => { - ... -}); -```` - -### **AddTreeBefore(string treeAlias, string name, string icon, Lambda treeConfig = null) : TreeConfigBuilder** - -Adds a tree to the current section **before** the tree with the given alias. - -````csharp -// Example -withSectionConfig.AddTreeBefore("member", "My Tree", "icon-folder", treeConfig => { - ... -}); -```` - -### **AddTreeAfter(string treeAlias, string name, string icon, Lambda treeConfig = null) : TreeConfigBuilder** - -Adds a tree to the current section **after** the tree with the given alias. - -````csharp -// Example -withSectionConfig.AddTreeAfter("member", "My Tree", "icon-folder", treeConfig => { - ... -}); -```` - -## Changing the tree icon color - -### **SetIconColor(string color) : TreeConfigBuilder** - -Sets the trees icon color to the given color. The options that are possible are `black`, `green`, `yellow`, `orange`, `blue` or `red`. - -{% hint style="warning" %} -Only trees added to existing sections have an icon. Trees added to Umbraco UI Builder sections don't show a tree icon instead they go straight into displaying the tree contents. -{% endhint %} - -````csharp -// Example -collectionConfig.SetIconColor("blue"); -```` - -## Adding a group to a tree - -### **AddGroup(string name, Lambda groupConfig = null) : GroupConfigBuilder** - -Adds a group to the current tree with the given name. - -{% hint style="warning" %} -Only Umbraco UI Builder section trees can configure groups, where trees added to existing sections cannot. -{% endhint %} - -```csharp -// Example -treeConfig.AddGroup("Settings", groupConfig => { - ... -}); -``` - -## Adding a folder to a tree/group - -### **AddFolder(string name, Lambda folderConfig = null) : FolderConfigBuilder** - -Adds a folder to the current tree/group with the given name and a default folder icon. For more information check the [Folders documentation](folders.md). - -```csharp -// Example -treeConfig.AddFolder("Settings", folderConfig => { - ... -}); -``` - -### **AddFolder(string name, string icon, Lambda folderConfig = null) : FolderConfigBuilder** - -Adds a folder to the current tree/group with the given name + icon. For more information check the [Folders documentation](folders.md). - -```csharp -// Example -treeConfig.AddFolder("Settings", "icon-settings", folderConfig => { - ... -}); -``` - -## Adding a collection to a tree/group - -### **AddCollection<TEntityType>(Lambda idFieldExpression, string nameSingular, string namePlural, string description, Lambda collectionConfig = null) : CollectionConfigBuilder<TEntityType>** - -Adds a collection to the current tree/group with the given names, descriptions, and default icons. An ID property accessor expression is required so that Umbraco UI Builder knows which property is the ID property. For more information check the [Collections documentation](../collections/overview.md). - -```csharp -// Example -treeConfig.AddCollection(p => p.Id, "Person", "People", "A collection of people", collectionConfig => { - ... -}); -``` - -#### **AddCollection<TEntityType>(Lambda idFieldExpression, string nameSingular, string namePlural, string description, string iconSingular, string iconPlural, Lambda collectionConfig = null) : CollectionConfigBuilder<TEntityType>** - -Adds a collection to the current tree/group with the given names, description and icons. An ID property accessor expression is required so that Umbraco UI Builder knows which property is the ID property. For more information check the [Collections documentation](../collections/overview.md). - -```csharp -// Example -treeConfig.AddCollection(p => p.Id, "Person", "People", "A collection of people", "icon-umb-users", "icon-umb-users", collectionConfig => { - ... -}); -``` - -## Extending an existing tree - -You can extend existing trees adding Umbraco UI Builder context apps and virtual sub trees by calling the `WithTree` method of a [`WithSectionConfigBuilder`](sections.md#extending-an-existing-section) instance. - -### **WithTree(string alias, Lambda treeConfig = null) : WithTreeConfigBuilder** - -Starts a sub-configuration for the existing Umbraco tree with the given alias. - -```csharp -// Example -sectionConfig.WithTree("content", withTreeConfig => { - ... -}); -``` - -## Adding a context app to an existing tree - -### **AddContextApp(string name, Lambda contextAppConfig = null) : ContextAppConfigBuilder** - -Adds a context app with the given name and default icon. For more information check the [Context App documentation](context-apps.md). - -```csharp -// Example -withTreeConfig.AddContextApp("Comments", contextAppConfig => { - ... -}); -``` - -### **AddContextApp(string name, string icon, Lambda contextAppConfig = null) : ContextAppConfigBuilder** - -Adds a context app to the Umbraco menu with the given name and icon. For more information check the [Context App documentation](context-apps.md). - -```csharp -// Example -withTreeConfig.AddContextApp("Comments", "icon-chat", contextAppConfig => { - ... -}); -``` - -### **AddContextAppBefore(string beforeAlias, string name, Lambda contextAppConfig = null) : ContextAppConfigBuilder** - -Adds a context app with the given name and default icon **before** the context app with the given alias. For more information check the [Context App documentation](context-apps.md). - -```csharp -// Example -withTreeConfig.AddContextAppBefore("umbContent", "Comments", contextAppConfig => { - ... -}); -``` - -### **AddContextAppBefore(string beforeAlias, string name, string icon, Lambda contextAppConfig = null) : ContextAppConfigBuilder** - -Adds a context app to the Umbraco menu with the given name and icon **before** the context app with the given alias. For more information check the [Context App documentation](context-apps.md). - -```csharp -// Example -withTreeConfig.AddContextAppBefore("umbContent", "Comments", "icon-chat", contextAppConfig => { - ... -}); -``` - -### **AddContextAppAfter(string afterAlias, string name, Lambda contextAppConfig = null) : ContextAppConfigBuilder** - -Adds a context app with the given name and default icon **after** the context app with the given alias. For more information check the [Context App documentation](context-apps.md). - -```csharp -// Example -withTreeConfig.AddContextAppAfter("umbContent", "Comments", contextAppConfig => { - ... -}); -``` - -### **AddContextAppAfter(string afterAlias, string name, string icon, Lambda contextAppConfig = null) : ContextAppConfigBuilder** - -Adds a context app to the Umbraco menu with the given name and icon **after** the context app with the given alias. For more information check the [Context App documentation](context-apps.md). - -```csharp -// Example -withTreeConfig.AddContextAppAfter("umbContent", "Comments", "icon-chat", contextAppConfig => { - ... -}); -``` diff --git a/14/umbraco-ui-builder/cards/count-cards.md b/14/umbraco-ui-builder/cards/count-cards.md deleted file mode 100644 index 57830b0be1c..00000000000 --- a/14/umbraco-ui-builder/cards/count-cards.md +++ /dev/null @@ -1,68 +0,0 @@ ---- -description: Configuring count cards in Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Count Cards - -Count cards allow you to define cards directly against the [collection](../collections/overview.md) configuration, providing a basic **where clause** to use in a count SQL statement. These work perfectly for basic data visualizations based on counts of entities in a collection. - -If you need to do more than a basic count, you'll want to take a look at the [custom cards](custom-cards.md) documentation. - -## Adding a count card to a collection - -Cards allow you to display basic summaries of key information that may be useful to the editor. - -### **AddCard(string name, Lambda whereClauseExpression, Lambda cardConfig = null) : CardConfigBuilder** - -Adds a card with the given name and **where clause** filter expression. Expression must be a `boolean` expression. - -````csharp -// Example -collectionConfig.AddCard("Older than 30", p => p.Age > 30, cardConfig => { - ... -}); -```` - -### **AddCard(string name, string icon, Lambda whereClauseExpression, Lambda cardConfig = null) : CardConfigBuilder** - -Adds a card with the given name + icon and **where clause** filter expression. Expression must be a `boolean` expression. - -````csharp -// Example -collectionConfig.AddCard("Older than 30", "icon-umb-users", p => p.Age > 30, cardConfig => { - ... -}); -```` - -### Change the color of a count card - -#### **SetColor(string color) : CardConfigBuilder** - -Sets the color of the card. - -````csharp -// Example -cardConfig.SetColor("blue"); -```` - -### Add a suffix to a count value - -#### **SetSuffix(string suffix) : CardConfigBuilder** - -Sets the suffix of the card value. - -````csharp -// Example -cardConfig.SetSuffix("years"); -```` - -### Formatting the value of a count - -#### **SetFormat(Lambda formatExpression) : CardConfigBuilder** - -Sets the format expression for the card. - -````csharp -// Example -cardConfig.SetFormat((v) => $"{v}%"); -```` diff --git a/14/umbraco-ui-builder/cards/custom-cards.md b/14/umbraco-ui-builder/cards/custom-cards.md deleted file mode 100644 index 0cbec414a86..00000000000 --- a/14/umbraco-ui-builder/cards/custom-cards.md +++ /dev/null @@ -1,62 +0,0 @@ ---- -description: Configuring custom cards in Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Custom Cards - -Custom cards allow you to perform more complex metric calculations and are defined via a class implementing the `Card` base class. - -When Umbraco UI Builder resolves a card it will attempt to do so from the global DI container. This means you can inject any dependencies that you require for your card to calculate its value. If there is no type defined in the DI container, Umbraco UI Builder will fall-back to manually instantiating a new instance of value mapper. - -## Defining a custom card - -To define a card you create a class that inherits from the base class `Card` and configure it within the constructor like so. - -````csharp -// Example -public class AvgPersonAgeCard : Card -{ - public override string Alias => "avgPersonAge"; - public override string Name => "Average Age"; - public override string Icon => "icon-calendar"; - public override string Color => "green"; - public override string Suffix => "yrs"; - - public override object GetValue(object parentId = null) - { - // Perform value calculation logic - } -} -```` - -The required configuration options are: - -* **Name:** The name of the card. -* **Alias:** A unique alias for the card. -* **GetValue(object parentId = null):** A method to get the cards value. - -Additional optional configuration options are: - -* **Icon:** An icon to display in the card. -* **Color:** The color of the card. -* **Suffix:** A suffix to display after the card value. - -## Adding a custom card to a collection - -### **AddCard() : CollectionConfigBuilder<TEntityType>** - -Adds a card of the given type to the collection. - -````csharp -// Example -collectionConfig.AddCard(); -```` - -### **AddCard(Type cardType) : CollectionConfigBuilder<TEntityType>** - -Adds a card of the given type to the collection. - -````csharp -// Example -collectionConfig.AddCard(typeof(AvgPersonAgeCard)); -```` diff --git a/14/umbraco-ui-builder/cards/overview.md b/14/umbraco-ui-builder/cards/overview.md deleted file mode 100644 index 35b687e3e60..00000000000 --- a/14/umbraco-ui-builder/cards/overview.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -description: Configuring cards in Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Cards - -Cards provide an API to display basic summary information in a card-based format and are useful for displaying key metrics about a collection. - -![Cards](../images/cards.png) - -Cards can be defined in one of two ways: - -{% content-ref url="count-cards.md" %} -[Count Cards](count-cards.md) -{% endcontent-ref %} - -{% content-ref url="custom-cards.md" %} -[Custom Cards](custom-cards.md) -{% endcontent-ref %} diff --git a/14/umbraco-ui-builder/changelog-archive/changelog.md b/14/umbraco-ui-builder/changelog-archive/changelog.md deleted file mode 100644 index 82b8c320984..00000000000 --- a/14/umbraco-ui-builder/changelog-archive/changelog.md +++ /dev/null @@ -1,180 +0,0 @@ ---- -description: Changelog for Konstrukt, the backoffice UI builder for Umbraco. ---- - -# Changelog - -## v1.6.4 - -**Date:** 2023-02-22 -**Description:** Patch release with bug fixes - -- Fixed issue where upload file property editor throws "the specified file type has been disallowed by the administrator" error ([#49](https://github.com/outfielddigital/konstrukt/issues/49)). -- Added ngrok URLs to allow domains that don't need a license. - -## v1.6.3 - -**Date:** 2023-01-16 -**Description:** Patch release with bug fixes - -- Moved encrypted properties implementation to the base repository class so encryption is honored when performing save/load operation directly against the repository API ([#44](https://github.com/outfielddigital/konstrukt/issues/44)). -- Made `SecurityHelper` swappable so you can use something other than the default `DataProtectionProvider` implementation that comes out of the box (OOTB). -- Fixed issue with advanced filters that use the lambda `ParameterReplacer` due to the parameter being replaced in the function, but not in the Lambda parameters list ([#45](https://github.com/outfielddigital/konstrukt/issues/45)). -- Fixed date filters not working on mobile resolution devices ([#46](https://github.com/outfielddigital/konstrukt/issues/46)). - -## v1.6.2 - -**Date:** 2022-12-01 -**Description:** Patch release with bug fixes - -- Added marketplace updates. -- Update the Konstrukt type finder to use a non-obsolete constructor. -- Updated to use `IComposer` instead of `IUserComposer` as the latter has been removed in v11. -- Fixed parent ID not being passed to create dialog for associated entities. -- Removed settings section restriction on the licensing info endpoint as it would cause errors when the licensing banner is shown in other sections. - -## v1.6.1 - -**Date:** 2022-10-11 -**Description:** Patch release with bug fixes - -- Fixed issue when running on Azure where the DB provider name reverts to `System.Data.SqlClient` when it should be `Microsoft.Data.SqlClient` - -## v1.6.0 - -**Date:** 2022-09-30 -**Description:** Minor release with additional features - -- Added a Save action type to display actions as a sub-button in an entities Save button (similar to the "Save and Publish" button in the content section). - -## v1.5.2 - -**Date:** 2022-09-09 -**Description:** Patch release with bug fixes - -- Fixed bug in entity picker not correctly showing the `Add` button when it should ([#39](https://github.com/outfielddigital/konstrukt/issues/39)). -- Added some basic validation to config at startup to ensure a valid config model. - -## v1.5.1 - -**Date:** 2022-08-22 -**Description:** Patch release with bug fixes - -- Fixed searchable properties not being searched in a case-insensitive way for repositories that don't use Umbraco's NPoco extension methods ([#36](https://github.com/outfielddigital/konstrukt/issues/36)). -- Fixed regression in Konstrukt repository not correctly combining filters. -- Fixed exception due to `ServiceProvider` not getting passed to Data transfer object (DTO) mapper. - -## v1.5.0 - -**Date:** 2022-08-18 -**Description:** Minor release with additional features and bug fixes - -- Added ability to control collection visibility in the section tree at runtime. -- Added ability to control collection create, update, and delete permissions at runtime. -- Added ability to control list view field visibility at runtime. -- Added ability to control editor tab visibility at runtime. -- Added ability to control editor fieldset visibility at runtime. -- Added ability to control editor field visibility at runtime. -- Added ability to control whether an editor field is read-only or not at runtime. -- Added the ability to add custom dashboards to Konstrukt sections. -- Added child collections support to dashboard collections. -- Updated Konstrukt API to null check sections/collections first and throw exceptions if not found. -- Updated based repositories to automatically implement filtering for configurable options. -- Updated the summary dashboard to not display if there are no collections configured to show on it. -- Fixed bug where entity service would silently fail if it couldn't retrieve an entity. Now throws an exception. -- Fixed bug where content app factory would throw an exception when run in sections where the section entity was not `IUmbracoEntity`. - -## v1.4.0 - -**Date:** 2022-07-12 -**Description:** Minor release with additional features and bug fixes - -- Added [`WithSection`](../areas/sections.md#extending-an-existing-section) / [`WithTree`](../areas/trees.md#extending-an-existing-tree) API to create more logical API groupings and to set context for some APIs. -- Added [`AddTree`](../areas/trees.md#adding-a-tree-to-an-existing-section) support to allow adding a tree to an existing section (currently only able to add 1 Konstrukt tree per section). -- Added [Tree Group](../areas/trees.md#adding-a-group-to-a-tree) support to allow grouping root-level tree folders/collections. -- Added [Tab Sidebar](../collections/editors.md#configuring-a-sidebar-to-a-tab) support to allow showing metadata on the right-hand side of the editor. -- Added file upload support to the actions dialog -- Added a basic [Comma-separated values (CSV) Import](../actions/inbuilt-actions.md#konstruktimportentityaction) action -- Added [`HideLabel`](../collections/editors.md#hiding-the-label-of-a-field) support to editor fields to explicitly hide the label. -- Added explicit Insert / Update methods to IKonstruktRepository. Internally we use these now instead of the Save method as the Save method isn't reliably able to determine if an entity is new. -- Added better support for transient / scoped repository dependencies (example: better support for EF Core DB contexts which are by default registered as scoped) -- Obsoleted root-level APIs for `AddSection`, `AddDashboard` and `AddVirtualSubTree` which have now moved to sub-configurations of the [`WithSection`](../areas/sections.md#extending-an-existing-section) or [`WithTree`](../areas/trees.md#extending-an-existing-tree) APIs. -- Fixed bug with DataViews resolving the wrong filter when using groups and the data view has the same name as a view in a different group. We now prefix the data view alias with the group name to ensure uniqueness across groups. -- Fixed bug in child collections creating dialog thinking it was always editing an existing entity and so wrongfully trying to load an entity from the DB due to the fact the entity ID passed through to the dialog "0" when it should be "-1". - -## v1.3.0 - -**Date:** 2022-07-06 -**Description:** Minor release with additional features and bug fixes - -- Added [Virtual Sub Trees](../advanced/virtual-sub-trees.md) support -- Fixed save/delete notification events being passed the wrong model -- Fixed bug where connection strings with no provider cause an error - -## v1.2.0 - -**Date:** 2022-06-20 -**Description:** Minor release with some breaking changes / additional features - -- Added `DeletedProperty` support where the column type is an `int`, and the value is a unix timestamp -- Fixed bug with encrypted properties not handling `null` values -- **[Breaking]** - Updated minimum Umbraco dependency to v10 -- **[Breaking]** - Updated UI assets to be a (RCL) Razor Compiled Library. **Be sure to clean your solution to remove old files**. - -## v1.1.1 - -**Date:** 2022-06-08 -**Description:** Minor patch release with non-breaking changes - -- Added client-side required / regex validation support -- Added support for nullable types when mapping property filters -- Added support for passing notification messages back from action results -- Fixed SQL escaping issue when using table names with schema prefix -- Fixed a bug in range property filters when a value is `null` -- Fixed a bug where save operations would show a success notification even if the save operation failed -- Fixed a bug in Data Attribute validation where `IServiceProvider` wasn't being passed through -- Fixed `null` error when searching returns no items -- Fixed deleted property filter condition not working -- Fixed bug where encrypted properties would throw an exception if the value was `null` - -## v1.1.0 - -**Date:** 2022-05-03 -**Description:** Minor release with some breaking changes / additional features - -- Added field views support for custom field markup in list views -- Added new consistent actions API -- Added row actions support -- Added filterable properties support -- Fixed entity picker value converter not working -- Fixed JS error when editing content due to bad null checking in the Konstrukt `redirectId` interceptor -- Deprecated List View Layout support -- **[Breaking]** - Obsoleted bulk actions and menu items in favour of new actions API -- **[Breaking]** - Moved actions, data views and cards configuration out of list views onto collections API - -## v1.0.2 - -**Date:** 2022-04-11 -**Description:** Minor patch release with non-breaking changes - -- Fixed OrderBy not handling name field correctly -- Updated license warning to only display if the number of "editable" collections is exceeded -- Fixed custom connection strings not working by implementing a DB factory pattern -- Introduced `IKonstruktNodeUdiResolver` to allow content apps to resolve a different node UDI than the current page -- Fixed error being thrown by menu actions because the current section wasn't being passed through to the menu - -## v1.0.1 - -**Date:** 2022-01-27 -**Description:** Minor patch release with non-breaking changes - -- Fixed bug where section/tree registration can sometimes occur twice resulting in an error. -- Removed licensing header when using a single collection. -- Fixed bug with `ORDER BY 1` causing SQL exceptions - -## v1.0.0 - -**Date:** 2022-01-20 -**Description:** Major new release - -- Initial release diff --git a/14/umbraco-ui-builder/collections/child-collection-groups.md b/14/umbraco-ui-builder/collections/child-collection-groups.md deleted file mode 100644 index 6d5b79cebcd..00000000000 --- a/14/umbraco-ui-builder/collections/child-collection-groups.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -description: Configuring child collection groups in Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Child Collection Groups - -{% hint style="warning" %} -This page is a work in progress and may undergo further revisions, updates, or amendments. The information contained herein is subject to change without notice. -{% endhint %} - -A child collection group is a container for other child collections. Its purpose is mainly to provide a logical grouping of multiple child collections to help with organization and an improved user experience. - -![Child Collection Groups](../images/child_collection_groups.png) - -## Defining a child collection group - -You can define a child collection group by calling one of the `AddChildCollectionGroup` methods on a given collection config builder instance. - -### **AddChildCollectionGroup(string name, Lambda childCollectionGroupConfig = null) : ChildCollectionGroupConfigBuilder** - -Adds a child collection group to the current collection with the given name and default icon. - -```csharp -// Example -collectionConfig.AddChildCollectionGroup("Family", childCollectionGroupConfig => { - ... -}); -``` - -### **AddChildCollectionGroup(string name, string icon, Lambda childCollectionGroupConfig = null) : ChildCollectionGroupConfigBuilder** - -Adds a child collection group to the current collection with the given name and icon. - -```csharp -// Example -collectionConfig.AddChildCollectionGroup("Family", "icon-users", childCollectionGroupConfig => { - ... -}); -``` diff --git a/14/umbraco-ui-builder/collections/child-collections.md b/14/umbraco-ui-builder/collections/child-collections.md deleted file mode 100644 index 2672706c01f..00000000000 --- a/14/umbraco-ui-builder/collections/child-collections.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -description: Configuring child collections in Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Child Collections - -{% hint style="warning" %} -This page is a work in progress and may undergo further revisions, updates, or amendments. The information contained herein is subject to change without notice. -{% endhint %} - -A child collection is a container for a given data model that is tied to a parent collection data model. It shares all of the [Collections](the-basics.md) config builder API except child collections cannot contain further child collections. - -![Child Collections](../images/child_collections.png) - -{% hint style="info" %} -**Child Collections UI:** By default, child collections will be presented in the UI as context apps in the parent models editor view. If you have multiple child collections that make the context apps area overpopulated, you can use the [Child Collection Groups API](child-collection-groups.md). By using this you can group child collections under a single context app with the inner child collections then being presented in tabs. -{% endhint %} - -## Defining a child collection - -You define a child collection by calling one of the `AddChildCollection` methods on a given collection config builder instance. - -### **AddChildCollection<TChildEntityType>(Lambda idFieldExpression, Lambda fkFieldExpression, string nameSingular, string namePlural, string description, Lambda childCollectionConfig = null) : ChildCollectionConfigBuilder<TEntityType>** - -Adds a child collection to the current collection with the given names and description and default icons. A property accessor expression is required for both the entity ID field and FK (Foreign Key) field of the entity. - -```csharp -// Example -collectionConfig.AddChildCollection(c => c.Id, c => c.ParentId, "Child", "Children", "A collection of children", childCollectionConfig => { - ... -}); -``` - -### **AddChildCollection<TChildEntityType>(Lambda idFieldExpression, Lambda fkFieldExpression, string nameSingular, string namePlural, string description, string iconSingular, string iconPlural, Lambda childCollectionConfig = null) : ChildCollectionConfigBuilder<TEntityType>** - -Adds a child collection to the current collection with the given names, description and icons. A property accessor expression is required for both the entity ID field and FK (Foreign Key) field of the entity. - -```csharp -// Example -collectionConfig.AddChildCollection(c => c.Id, c => c.ParentId, "Child", "Children", "A collection of children", "icon-umb-users", "icon-umb-users", childCollectionConfig => { - ... -}); -``` - -## Configuring a child collection - -Child collections share the same API as the `Collection` config builder API, except child collections cannot contain further child collections. For more information check the [core collections documentation](the-basics.md). diff --git a/14/umbraco-ui-builder/collections/editors.md b/14/umbraco-ui-builder/collections/editors.md deleted file mode 100644 index 204ded86981..00000000000 --- a/14/umbraco-ui-builder/collections/editors.md +++ /dev/null @@ -1,268 +0,0 @@ ---- -description: Configuring the editor of a collection in Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Editors - -An editor is the user interface used to edit an entity and is made up of tabs and property editors. - -![A collection editor](../images/editor.png) - -## Configuring an editor - -The editor configuration is a sub-configuration of a [`Collection`](the-basics.md) config builder instance and is accessed via its `Editor` method. - -### **Editor(Lambda editorConfig = null) : EditorConfig<TEntityType>** - -Accesses the editor config of the given collection. - -````csharp -// Example -collectionConfig.Editor(editorConfig => { - ... -}); -```` - -## Adding a tab to an editor - -### **AddTab(string name, Lambda tabConfig = null) : EditorTabConfigBuilder<TEntityType>** - -Adds a tab to the editor. - -````csharp -// Example -editorConfig.AddTab("General", tabConfig => { - ... -}); -```` - -## Configuring a sidebar to a tab - -A slidebar is a smaller area that is displayed to the right of the main editor. The sidebar can also contain fieldsets and fields in the same way tabs can. However, it is a much more limited display area so you'll need to choose your field types carefully. The sidebar is a great location to display entity metadata. - -### **Sidebar(Lambda sidebarConfig = null) : EditorTabSidebarConfigBuilder<TEntityType>** - -Configures the sidebar for the tab. - -````csharp -// Example -tabConfig.Sidebar(sidebarConfig => { - ... -}); -```` - -## Setting the visibility of a tab - -### **SetVisibility(Predicate<EditorTabVisibilityContext> visibilityExpression) : EditorTabConfigBuilder<TEntityType>** - -Sets the runtime visibility of the tab. - -````csharp -// Example -tabConfig.SetVisibility(ctx => ctx.EditorMode == EditorMode.Create); -```` - -## Adding a fieldset to a tab - -### **AddFieldset(string name, Lambda fieldsetConfig = null) : EditorFieldsetConfigBuilder<TEntityType>** - -Adds the given fieldset to the tab. - -````csharp -// Example -tabConfig.AddFieldset("Contact", fieldsetConfig => { - ... -}); -```` - -## Setting the visibility of a fieldset - -### **SetVisibility(Predicate<EditorFieldsetVisibilityContext> visibilityExpression) : EditorFieldsetConfigBuilder<TEntityType>** - -Sets the runtime visibility of the fieldset. - -````csharp -// Example -fieldsetConfig.SetVisibility(ctx => ctx.EditorMode == EditorMode.Create); -```` - -## Adding a field to a fieldset - -### **AddField(Lambda propertyExpression, Lambda propertyConfig = null) : EditorFieldConfigBuilder<TEntityType, TValueType>** - -Adds the given property to the editor. - -````csharp -// Example -fieldsetConfig.AddField(p => p.FirstName, fieldConfig => { - ... -}); -```` - -## Changing the label of a field - -By default, Umbraco UI Builder will build the label from the property name, including splitting camel case names into sentence cases. However, you can set an explicit label if preferred. - -### **SetLabel(string label) : EditorFieldConfigBuilder<TEntityType, TValueType>** - -Sets the label for the editor field. - -````csharp -// Example -fieldConfig.SetLabel("First Name"); -```` - -## Hiding the label of a field - -Sometimes you may have a field editor that would work better in full width. You can achieve this by explicitly hiding the field label. - -### **HideLabel() : EditorFieldConfigBuilder<TEntityType, TValueType>** - -Hides the label for the editor field. - -````csharp -// Example -fieldConfig.HideLabel(); -```` - -## Adding a description to a field - -### **SetDescription(string description) : EditorFieldConfigBuilder<TEntityType, TValueType>** - -Sets the description for the editor field. - -````csharp -// Example -fieldConfig.SetDescription("Enter your age in years"); -```` - -## Changing the Data Type of a field - -By default, Umbraco UI Builder will automatically choose a relevant Data Type for basic field types. However, if you wish to use an alternative Data Type then you can override this. - -### **SetDataType(string dataTypeName) : EditorFieldConfigBuilder<TEntityType, TValueType>** - -Set the Data Type of the current field to the Umbraco Data Type with the given name. - -````csharp -// Example -fieldConfig.SetDataType("Richtext Editor"); -```` - -### **SetDataType(int dataTypeId) : EditorFieldConfigBuilder<TEntityType, TValueType>** - -Set the Data Type of the current field to the Umbraco Data Type with the given id. - -````csharp -// Example -fieldConfig.SetDataType(-88); -```` - -## Setting the default value of a field - -### **SetDefaultValue(TValueType defaultValue) : EditorFieldConfigBuilder<TEntityType, TValueType>** - -Sets the default value to a known constant. - -````csharp -// Example -fieldConfig.SetDefaultValue(10); -```` - -### **SetDefaultValue(Func defaultValueFunc) : EditorFieldConfigBuilder<TEntityType, TValueType>** - -Sets the default value via a function that gets evaluated at time of entity creation. - -````csharp -// Example -fieldConfig.SetDefaultValue(() => DateTime.Now); -```` - -## Making a field required - -### **MakeRequired() : EditorFieldConfigBuilder<TEntityType, TValueType>** - -Makes the given field required. - -````csharp -// Example -fieldConfig.MakeRequired(); -```` - -## Validating a field - -### **SetValidationRegex(string regex) : EditorFieldConfigBuilder<TEntityType, TValueType>** - -Defines the regular expression to use when validating the field. - -````csharp -// Example -fieldConfig.SetValidationRegex("[A-Z0-9._%+-]+@[A-Z0-9.-]+\\.[A-Z]{2,4}"); -```` - -## Making a field read-only - -### **MakeReadOnly() : EditorFieldConfigBuilder<TEntityType, TValueType>** - -Makes the current field read-only disabling editing in the UI. - -````csharp -// Example -fieldConfig.MakeReadOnly(); -```` - -### **MakeReadOnly(Func<TValueType, string> format) : EditorFieldConfigBuilder<TEntityType, TValueType>** - -Makes the current field read-only disabling editing in the UI. Provides a custom formatting expression to use when rendering the value as a string. - -````csharp -// Example -fieldConfig.MakeReadOnly(distanceProp => $"{distanceProp:## 'km'}"); -```` - -### **MakeReadOnly(object dataTypeNameOrId) : EditorFieldConfigBuilder<TEntityType, TValueType>** - -Makes the current field read-only disabling editing in the UI. Provides the name or id of a datatype to use when in read-only mode. - -````csharp -// Example -fieldConfig.MakeReadOnly("myReadOnlyEditor"); -```` - -### **MakeReadOnly(Predicate<EditorFieldReadOnlyContext> readOnlyExp) : EditorFieldConfigBuilder<TEntityType, TValueType>** - -Makes the current field read-only disabling editing in the UI if the given runtime predicate is true. - -````csharp -// Example -fieldConfig.MakeReadOnly(ctx => ctx.EditorMode == EditorMode.Create); -```` - -### **MakeReadOnly(Predicate<EditorFieldReadOnlyContext> readOnlyExp, Func<TValueType, string> format) : EditorFieldConfigBuilder<TEntityType, TValueType>** - -Makes the current field read-only disabling editing in the UI if the given runtime predicate is true. Provides a custom formatting expression to use when rendering the value as a string. - -````csharp -// Example -fieldConfig.MakeReadOnly(ctx => ctx.EditorMode == EditorMode.Create, distanceProp => $"{distanceProp:## 'km'}"); -```` - -### **MakeReadOnly(Predicate<EditorFieldReadOnlyContext> readOnlyExp, object dataTypeNameOrId) : EditorFieldConfigBuilder<TEntityType, TValueType>** - -Makes the current field read-only disabling editing in the UI if the given runtime predicate is true. Provides the name or id of a datatype to use when in read-only mode. - -````csharp -// Example -fieldConfig.MakeReadOnly(ctx => ctx.EditorMode == EditorMode.Create, "myReadOnlyEditor"); -```` - -## Setting the visibility of a field - -### **SetVisibility(Predicate<EditorFieldVisibilityContext> visibilityExpression) : EditorFieldConfigBuilder<TEntityType, TValueType>** - -Sets the runtime visibility of the field. - -````csharp -// Example -fieldConfig.SetVisibility(ctx => ctx.EditorMode == EditorMode.Create); -```` diff --git a/14/umbraco-ui-builder/collections/field-views.md b/14/umbraco-ui-builder/collections/field-views.md deleted file mode 100644 index 59a4cd4687a..00000000000 --- a/14/umbraco-ui-builder/collections/field-views.md +++ /dev/null @@ -1,68 +0,0 @@ ---- -description: Configuring field views in Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Field Views - -Field Views allow you to customize the markup used by a field when displayed in a list view. Field Views are implemented as .NET Core View Components that are passed a single `FieldViewsContext` argument with information about the entity/field being rendered. - -## Defining a field view - -You can define a field view in one of two ways. - -### **1. A basic view file for the built in `FieldView` view component** - -The simplest way to define a field view for non-complex fields is to place a view file in the `/Views/Shared/Components/FieldView` folder with the following markup. - -````csharp -@model Umbraco.UIBuilder.Web.Models.FieldViewContext - -```` - -When registering a basic file view you can pass the name of the view file (excluding the `.cshtml` file extension) to the relevant API method. - -### **2. A complete custom view component** - -To define a more complex field view you can create your own view component class (which can use dependency injection for any required dependencies). This can be done by using the following signature: - -````csharp -// Example -public class MyComplexFieldViewViewComponent : ViewComponent -{ - public async Task InvokeAsync(FieldViewContext context) - { - // Do your custom logic here - - return View("Default", model); - } -} -```` - -{% hint style="info" %} -It's important to know that the `FieldViewContext` parameter to the `InvokeAsync` method **MUST** be named `context`. -{% endhint %} - -For the view element of your component, based on the example above, you would place a file `Default.cshtml` into the `/Views/Shared/Components/MyComplexFieldView` folder with the following markup: - -````csharp -@model Namespace.Of.Model.Returned.By.Custom.ViewComponent - -```` - -## The field view context - -Field view components are passed a `FieldViewContext` object with the following information: - -````csharp -public class FieldViewContext -{ - public string ViewName { get; set; } - public object Entity { get; set; } - public string PropertyName { get; set; } - public object PropertyValue { get; set; } -} -```` - -## Setting the field view of a list view field - -A field view is assigned to a list view field as part of the list view configuration. For more information you can check the [List View Documentation](list-views.md#setting-the-view-of-a-field). diff --git a/14/umbraco-ui-builder/collections/list-view-layouts.md b/14/umbraco-ui-builder/collections/list-view-layouts.md deleted file mode 100644 index f37338992f0..00000000000 --- a/14/umbraco-ui-builder/collections/list-view-layouts.md +++ /dev/null @@ -1,50 +0,0 @@ ---- -description: Configuring list view layouts in Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# List View Layouts - -{% hint style="danger" %} -**List View Layouts** in Umbraco UI Builder are now considered deprecated. Moving forward, only the table list view will be supported. Whilst you can continue to use this feature for the time being, it will be removed in a future release. -{% endhint %} - -List view layouts allow you to provide custom angular views to be used by the list view UI. By default, there are two built-in layouts, `TableListViewLayout` which displays results in a tabular layout, and `GridListViewLayout` which displays results in a tiled grid layout. - -## Defining a list view layout - -To define a list view layout you create a class that inherits from the base class `ListViewLayout` and implements the abstract configuration properties. - -````csharp -// Example -public class MyCustomListViewLayout : ListViewLayout -{ - public GridListViewLayout() - { - Name = "My Custom List"; - Alias = "my-custom-list"; - Icon = "icon-list"; - View = "/app_plugins/myplugin/views/mycustomlist.htm"; - } -} -```` - -The required configuration options are: - -* **Name:** The name of the layout. -* **Alias:** A unique alias for the layout. -* **Icon:** An icon to display in the list view layouts dropdown. -* **View:** The path of the angular view to load by the list view. - -As well as defining the list view layout class you will also need to implement the relevant angular view and controller. This is a little out of scope for the Umbraco UI Builder documentation, however in summary you will need to: - -* Create a plugin folder in the root `App_Plugin` folder. -* Create a `package.manifest` file in your plugin folder. -* Create a HTML view to be loaded. -* Create an angular controller to control the view. -* Hook up the controller with the view using the `ng-controller` attribute. -* Add the controller JS file path to the `package.manifest`. -* Build your custom logic. - -## Changing the list view layout of a list view - -A list view layout is assigned to a list view as part of the list view configuration. For more information you can check the [List View API Documentation](list-views.md#changing-the-list-view-layout). diff --git a/14/umbraco-ui-builder/collections/list-views.md b/14/umbraco-ui-builder/collections/list-views.md deleted file mode 100644 index 2f237a41e54..00000000000 --- a/14/umbraco-ui-builder/collections/list-views.md +++ /dev/null @@ -1,103 +0,0 @@ ---- -description: Configuring the list view of a collection in Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# List Views - -A list view is a list-based view of a collection entity providing features: pagination for large collections, custom data views, searching, and bulk actions. - -![A collection list view](../images/listview.png) - -## Configuring a list view - -The list view configuration is a sub-configuration of a [`Collection`](the-basics.md) config builder instance and is accessed via its `ListView` method. - -### **ListView(Lambda listViewConfig = null) : ListViewConfigBuilder<TEntityType>** - -Accesses the list view config of the given collection. - -````csharp -// Example -collectionConfig.ListView(listViewConfig => { - ... -}); -```` - -## Adding a field to the list view - -### **AddField(Lambda propertyExpression, Lambda fieldConfig = null) : ListViewFieldConfigBuilder<TEntityType, TValueType>** - -Adds the given property to the list view. - -````csharp -// Example -listViewConfig.AddField(p => p.FirstName, fieldConfig => { - ... -}); -```` - -## Changing the heading of a field - -### **SetHeading(string heading) : ListViewFieldConfigBuilder<TEntityType, TValueType>** - -Sets the heading for the list view field. - -````csharp -// Example -fieldConfig.SetHeading("First Name"); -```` - -## Formatting the value of a field - -### **SetFormat(Lambda formatExpression) : ListViewFieldConfigBuilder<TEntityType, TValueType>** - -Sets the format expression for the list view field. - -````csharp -// Example -fieldConfig.SetFormat((v, p) => $"{v} years old"); -```` - -## Setting the view of a field - -With field views, you can customize the markup the list view's field so you can show richer visualizations of the field's content. For more information you can check the [Field Views Documentation](field-views.md). - -### **SetView(string viewComponentName) : ListViewFieldConfigBuilder<TEntityType, TValueType>** - -Sets the view component for the list view field. - -````csharp -// Example -fieldConfig.SetView("ImageFieldView"); -```` - -### **SetView<TView>() : ListViewFieldConfigBuilder<TEntityType, TValueType>** - -Sets the view component for the list view field. - -````csharp -// Example -fieldConfig.SetView(); -```` - -## Setting the visibility of a field - -### **SetVisibility(Predicate<ListViewFieldVisibilityContext> visibilityExpression) : ListViewFieldConfigBuilder<TEntityType, TValueType>** - -Sets the runtime visibility of the list view field. - -````csharp -// Example -fieldConfig.SetVisibility(ctx => ctx.UserGroups.Any(x => x.Alias == "editor")); -```` - -## Changing the page size - -### **SetPageSize(int pageSize) : ListViewConfigBuilder<TEntityType>** - -Sets the number of items to display per page for the given list view. - -````csharp -// Example -listViewConfig.SetPageSize(20); -```` diff --git a/14/umbraco-ui-builder/collections/overview.md b/14/umbraco-ui-builder/collections/overview.md deleted file mode 100644 index cf27e7db0ee..00000000000 --- a/14/umbraco-ui-builder/collections/overview.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -description: Configuring collection in Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Collections - -A collection is the cornerstone Umbraco UI Builder config and it represents a collection of entities for a given data model. From this config object, you can configure everything about how this collection integrates into the UI. You can also configure how it should display in a list view as well as how it should be edited. - -![A collection list view](../images/listview.png) - -Get started by reviewing the basics of collection configuration. - -{% content-ref url="the-basics.md" %} -[the-basics.md](the-basics.md) -{% endcontent-ref %} diff --git a/14/umbraco-ui-builder/collections/related-collections.md b/14/umbraco-ui-builder/collections/related-collections.md deleted file mode 100644 index cb8ef2345ba..00000000000 --- a/14/umbraco-ui-builder/collections/related-collections.md +++ /dev/null @@ -1,166 +0,0 @@ ---- -description: Configuring **many-to-many** relationships in Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Related Collections - -{% hint style="warning" %} -This page is a work in progress and may undergo further revisions, updates, or amendments. The information contained herein is subject to change without notice. -{% endhint %} - -Related collections add support for editing **many-to-many** relationships with UI Builder. These are found when multiple entities from one collection are associated with multiple entities from another. They are modeled in a database via two tables related to a junction table. - -A classic example is with `Students` and `Courses`. Each course has many students, and each student takes many courses. - -![Child Collection](../images/related_collections_child.png) - -![Parent Collection](../images/related_collections_parent.png) - -![Entity Picker](../images/entity_picker_config.png) - -## Collections Representation - -A representation of your collections would look like this: - -![Related Collections Diagram](../images/related_collections_diagram.png) - -And the entities would be represented using the following Models: - -```csharp -[TableName("Students")] -[PrimaryKey("Id")] -public class Student -{ - [PrimaryKeyColumn] - public int Id { get; set; } - - public string FirstName { get; set; } - - public string LastName { get; set; } - - public string Email { get; set; } -} -``` - -```csharp -[TableName("Courses")] -[PrimaryKey("Id")] -public class Course -{ - [PrimaryKeyColumn] - public int Id { get; set; } - - public string Title { get; set; } - - public string Description { get; set; } -} -``` - -```csharp -[TableName("StudentsCourses")] -[PrimaryKey(new[] { "StudentId", "CourseId" })] -public class StudentCourse -{ - [PrimaryKeyColumn] - public int StudentId { get; set; } - - [PrimaryKeyColumn] - public int CourseId { get; set; } -} -``` - -## Defining a related collection - -You can get started with related collection through a two step process: - -1. Add collection definition -2. Add related collection entity picker and definition - -### Collection definition - -Define a related collection by calling the `AddRelatedCollection` method on a given collection config builder instance. - -### **AddRelatedCollection<TEntityType, TRelatedEntityType, TJunctionEntityType>(Expression<Func<TRelatedEntityType, object>> idPropertyExpression, string nameSingular, string namePlural, Action<RelationConfigBuilder<TBuilder, TEntity, TRelatedEntityType, TJunctionEntityType>> relationConfig)** - -Adds a related collection to the current collection with the given names, descriptions, and default icons. A property accessor expression is required for the entity ID field of the entity. The relation configuration will define the junction entity by specifying the references to parent and child entities. - -```csharp -collectionConfig.AddRelatedCollection(x => x.Id, "Student Course", "Students Courses", relationConfig => -{ - relationConfig - .SetAlias("studentsCourses") - .SetJunction(x => x.StudentId, y => y.CourseId); -}); -``` - -### Configuring a related collection entity picker - -Define the child collection entity picker by calling the `AddRelatedCollectionPickerField` method on the parent collection fieldset config. - -### **AddRelatedCollectionPickerField<TValueType>(string alias, string dataTypeName, string label)** - -Adds an entity picker with the specified Data Type name to the editor of the parent collection. - -```csharp -collectionConfig.Editor(editorConfig => -{ - editorConfig.AddTab("General", tabConfig => - tabConfig.AddFieldset("General", fieldsetConfig => - { - fieldsetConfig.AddField(x => x.FirstName).MakeRequired(); - fieldsetConfig.AddField(x => x.LastName).MakeRequired(); - fieldsetConfig.AddField(x => x.Email).MakeRequired(); - - fieldsetConfig.AddRelatedCollectionPickerField("studentsCourses", "Courses Related Picker", "Courses"); - })); -}); -``` - -{% hint style="info" %} -**Relation Config Alias:** The relation config alias must correspond to the related collection picker field alias! (e.g. `studentsCourses`) -{% endhint %} - -## Defining repository methods - -### **IEnumerable GetRelationsByParentIdImpl(int parentId, string relationAlias)** - -Retrieves the related collections based on the ID of the parent entity. - -```csharp -{ - var db = _scopeProvider.CreateScope().Database; - var sql = db.SqlContext.Sql() - .Select(new[] { "StudentId", "CourseId" } ) - .From("StudentsCourses") - .Where($"studentId = @0", parentId); - - var result = db.Fetch(sql); - - return result; -} -``` - -### **StudentCourse SaveRelationImpl(StudentCourse entity)** - -Adds a new related collection to the current parent entity. - -```csharp -{ - var db = _scopeProvider.CreateScope().Database; - - var type = entity.GetType(); - var studentId = type.GetProperty("StudentId").GetValue(entity); - var courseId = type.GetProperty("CourseId").GetValue(entity); - - // delete relation if exists - db.Execute("DELETE FROM StudentsCourses WHERE StudentId = @0 AND CourseId = @1", - studentId, - courseId); - - db.Execute("INSERT INTO StudentsCourses (StudentId, CourseId) VALUES (@0, @1)", - studentId, - courseId); - - return entity; -} -``` diff --git a/14/umbraco-ui-builder/collections/retrieve-child-collections.md b/14/umbraco-ui-builder/collections/retrieve-child-collections.md deleted file mode 100644 index 0f85f135917..00000000000 --- a/14/umbraco-ui-builder/collections/retrieve-child-collections.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -description: Configuring **one-to-many** relationships in Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Retrieve Child Collections - -{% hint style="warning" %} -This page is a work in progress and may undergo further revisions, updates, or amendments. The information contained herein is subject to change without notice. -{% endhint %} - -Retrieving child collections in **one-to-many** relationships with UI Builder, can be achieved with the support of child repositories. One-to-many relations are where one parent entity of a collection is associated with multiple entities from another. - -## Models Representation - -The models would look like this: - -```csharp -[TableName("Students")] -[PrimaryKey("Id")] -public class Student -{ - [PrimaryKeyColumn] - public int Id { get; set; } - - public string FirstName { get; set; } - - public string LastName { get; set; } - - public string Email { get; set; } -} -``` - -```csharp -[TableName("StudentProjects")] -[PrimaryKey("Id")] -public class StudentProject -{ - [PrimaryKeyColumn] - public int Id { get; set; } - - public string Name { get; set; } - - public int StudentId { get; set; } -} -``` - -## Child Repositories - -You can create child repository instances via the `IRepositoryFactory` and use them to retrieve information from the child collection. - -```csharp -public class StudentProjectController : Controller -{ - private readonly IRepositoryFactory _repositoryFactory; - - public StudentProjectController(IRepositoryFactory repositoryFactory) - { - _repositoryFactory = repositoryFactory; - } - - public IActionResult Index(int projectId) - { - var childRepository = _repositoryFactory.GetChildRepository(projectId); - - var list = childRepository.GetAll(); - - var count = childRepository.GetCount(); - - var listPaged = childRepository.GetPaged(); - - return View(list); - } -} -``` diff --git a/14/umbraco-ui-builder/collections/the-basics.md b/14/umbraco-ui-builder/collections/the-basics.md deleted file mode 100644 index 7dc097226b1..00000000000 --- a/14/umbraco-ui-builder/collections/the-basics.md +++ /dev/null @@ -1,239 +0,0 @@ ---- -description: The basics of a collection configuration in Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# The Basics - -There is a lot that can be configured from the collection config, but what follows are the core basics. You can find more configuration options about specific topics from the other configuration sections in the main menu. - -## Defining a collection - -You can define a collection by calling one of the `AddCollection` methods on a given [`Tree`](../areas/trees.md) or parent [`Folder`](../areas/folders.md) config builder instance. - -### **AddCollection<TEntityType>(Lambda idFieldExpression, string nameSingular, string namePlural, string description, Lambda collectionConfig = null) : CollectionConfigBuilder<TEntityType>** - -Adds a collection to the given container with the given names and description and default icons. An ID property accessor expression is required so that Umbraco UI Builder knows which property is the ID property. - -````csharp -// Example -folderConfig.AddCollection(p => p.Id, "Person", "People", "A collection of people", collectionConfig => { - ... -}); -```` - -### **AddCollection<TEntityType>(Lambda idFieldExpression, string nameSingular, string namePlural, string description, string iconSingular, string iconPlural, Lambda collectionConfig = null) : CollectionConfigBuilder<TEntityType>** - -Adds a collection to the given container with the given names, description and icons. An ID property accessor expression is required so that Umbraco UI Builder knows which property is the ID property. - -````csharp -// Example -folderConfig.AddCollection(p => p.Id, "Person", "People", "A collection of people", "icon-umb-users", "icon-umb-users", collectionConfig => { - ... -}); -```` - -## Changing a collection alias - -### **SetAlias(string alias) : CollectionConfigBuilder<TEntityType>** - -Sets the alias of the collection. - -**Optional:** When creating a new collection, an alias is automatically generated from the supplied name for you. However, if you need a specific alias you can use the `SetAlias` method to override this. - -````csharp -// Example -collectionConfig.SetAlias("person"); -```` - -## Changing a collection icon color - -### **SetIconColor(string color) : CollectionConfigBuilder<TEntityType>** - -Sets the collection icon color to the given color. Possible options are `black`, `green`, `yellow`, `orange`, `blue` or `red`. - -````csharp -// Example -collectionConfig.SetIconColor("blue"); -```` - -## Defining an entity name - -Within Umbraco, it is expected that an entity has a name property. So we need to let Umbraco UI Builder know which property to use for the name. If the entity doesn't have a name property, then it needs to know how to construct a name from an entity's other properties. We do this by using either the `SetNameProperty` or `SetNameFormat` methods on a `Collection` config builder instance. - -### **SetNameProperty(Lambda namePropertyExpression) : CollectionConfigBuilder<TEntityType>** - -Sets which property of your entity to use as the name property. Property must be of type `string`. By defining a property as the name property, its value will be used as the label for the entity in trees and list views. It will also be editable in the header region of the editor interface. The property will also automatically be added to the searchable properties collection and be used for the default sort property. - -````csharp -// Example -collectionConfig.SetNameProperty(p => p.Name); -```` - -### **SetNameProperty(Lambda namePropertyExpression, string heading) : CollectionConfigBuilder<TEntityType>** - -Sets which property of your entity to use as the name property and what custom heading should the list view column heading be. Property must be of type `string`. By defining a property as the name property, its value will be used as the label for the entity in trees and list views. It will also be editable in the header region of the editor interface. The property will also automatically be added to the searchable properties collection and be used for the default sort property. - -````csharp -// Example -collectionConfig.SetNameProperty(p => p.Name, "Person Name"); -```` - -### **SetNameFormat(Lambda nameFormatExpression) : CollectionConfigBuilder<TEntityType>** - -Sets a format expression to use to dynamically create a label for the entity in things like trees and list views. By providing a name format it is assumed there is no single name property available on the entity. And as such none of the default behaviors described for the `SetNameProperty` method will apply. - -````csharp -// Example -collectionConfig.SetNameFormat(p => $"{p.FirstName} {p.LastName}"); -```` - -## Defining a default sort order - -### **SetSortProperty(Lambda sortPropertyExpression) : CollectionConfigBuilder<TEntityType>** - -Sets which property of our entity to sort against, defaulting to ascending sort direction. - -````csharp -// Example -collectionConfig.SetSortProperty(p => p.FirstName); -```` - -### **SetSortProperty(Lambda sortPropertyExpression, SortDirection sortDirection) : CollectionConfigBuilder<TEntityType>** - -Sets which property of our entity to sort against in the provided sort direction. - -````csharp -// Example -collectionConfig.SetSortProperty(p => p.FirstName, SortDirection.Descending); -```` - -## Defining time stamp properties - -### **SetDateCreatedProperty(Lambda dateCreatedProperty) : CollectionConfigBuilder<TEntityType>** - -Sets which property of our entity to use as the date created property. Property must be of type `DateTime`. When set and a new entity is saved via the repository, then the given field will be populated with the current date and time. - -````csharp -// Example -collectionConfig.SetDateCreatedProperty(p => p.DateCreated); -```` - -### **SetDateModifiedProperty(Lambda dateCreatedProperty) : CollectionConfigBuilder<TEntityType>** - -Sets which property of our entity to use as the date modified property. Property must be of type `DateTime`. When set and an entity is saved via the repository, then the given field will be populated with the current date and time. - -````csharp -// Example -collectionConfig.SetDateModifiedProperty(p => p.DateModified); -```` - -## Configuring soft deletes - -By default, in Umbraco UI Builder any entity that is deleted via the Umbraco UI Builder repository is definitively removed from the system. The `SetDeletedProperty` method can be used if needed to keep the records in the data repository despite having them marked as deleted. This is so they do not show the the UI. - -### **SetDeletedProperty(Lambda deletedPropertyExpression) : CollectionConfigBuilder<TEntityType>** - -Sets which property of our entity to use as the deleted property flag. Property must be of type `boolean` or `int`. When a deleted property is set, any delete actions will set the deleted flag instead of deleting the entity. For `boolean` based properties, deleted entities will have a value of `True` when deleted. For `int` based properties, deleted entities will have a UTC Unix timestamp value of the date the entity was deleted. In addition, any fetch actions will also pre-filter out any deleted entities. - -````csharp -// Example -collectionConfig.SetDeletedProperty(p => p.Deleted); -```` - -## Disabling create, update or delete features - -### **DisableCreate() : CollectionConfigBuilder<TEntityType>** - -Disables the option to create entities on the current collection. An entity could be created via code and only then editing is allowed in the UI for example. - -````csharp -// Example -collectionConfig.DisableCreate(); -```` - -### **DisableCreate(Predicate<CollectionPermissionContext> disableExpression) : CollectionConfigBuilder<TEntityType>** - -Disables the option to create entities on the current collection if the given runtime predicate is true. An entity could be created via code and only then editing is allowed in the UI. - -````csharp -// Example -collectionConfig.DisableCreate(ctx => ctx.UserGroups.Any(x => x.Alias == "editor")); -```` - -### **DisableUpdate() : CollectionConfigBuilder<TEntityType>** - -Disables the option to update entities on the current collection. An entity can be created, but further editing is not allowed. - -````csharp -// Example -collectionConfig.DisableUpdate(); -```` - -### **DisableUpdate(Predicate<CollectionPermissionContext> disableExpression) : CollectionConfigBuilder<TEntityType>** - -Disables the option to update entities on the current collection if the given runtime predicate is true. An entity can be created, but further editing is not allowed. - -````csharp -// Example -collectionConfig.DisableUpdate(ctx => ctx.UserGroups.Any(x => x.Alias == "editor")); -```` - -### **DisableDelete() : CollectionConfigBuilder<TEntityType>** - -Disables the option to delete entities on the current collection. Useful if the data needs to be retained and visible. See also [configuring soft deletes](#configuring-soft-deletes). - -````csharp -// Example -collectionConfig.DisableDelete(); -```` - -### **DisableDelete(Predicate<CollectionPermissionContext> disableExpression) : CollectionConfigBuilder<TEntityType>** - -Disables the option to delete entities on the current collection if the given runtime predicate is true. Useful if the data needs to be retained and visible. See also [configuring soft deletes](#configuring-soft-deletes). - -````csharp -// Example -collectionConfig.DisableDelete(ctx => ctx.UserGroups.Any(x => x.Alias == "editor")); -```` - -### **MakeReadOnly() : CollectionConfigBuilder<TEntityType>** - -Sets the collection as read-only and disables any Create, Read, Update, and Delete (CRUD) operations from being performed on the collection via the UI. - -````csharp -// Example -collectionConfig.MakeReadOnly(); -```` - -### **MakeReadOnly(Predicate<CollectionPermissionContext> disableExpression) : CollectionConfigBuilder<TEntityType>** - -Sets the collection as read-only if the given runtime predicate is true. It also disables any Create, Read, Update, and Delete (CRUD) operations from being performed on the collection via the UI. - -````csharp -// Example -collectionConfig.MakeReadOnly(ctx => ctx.UserGroups.Any(x => x.Alias == "editor")); -```` - -## Set the visibility of the collection - -### **SetVisibility(Predicate<CollectionVisibilityContext> visibilityExpression) : CollectionConfigBuilder<TEntityType>** - -Sets the runtime visibility of the collection. - -````csharp -// Example -collectionConfig.SetVisibility(ctx => ctx.UserRoles.Any(x => x.Alias == "editor")); -```` - -## Changing a collection connection string - -By default, Umbraco UI Builder will use the Umbraco connection string for its database connection. However, you can change this by calling the `SetConnectionString` method on a `Collection` config builder instance. - -### **SetConnectionString(string connectionStringName) : CollectionConfigBuilder<TEntityType>** - -Sets the connection string name for the given collection repository. - -````csharp -// Example -collectionConfig.SetConnectionString("myConnectionStringName"); -```` diff --git a/14/umbraco-ui-builder/filtering/data-views-builders.md b/14/umbraco-ui-builder/filtering/data-views-builders.md deleted file mode 100644 index 5803cadcd52..00000000000 --- a/14/umbraco-ui-builder/filtering/data-views-builders.md +++ /dev/null @@ -1,65 +0,0 @@ ---- -description: Configuring data views builders in Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Data Views Builders - -Data views builders allow you to create a collection data views list dynamically at run time. By default, Umbraco UI Builder will use the hard-coded data views defined in your Umbraco UI Builder config. However, if you need to build your data views list dynamically, then this is when you'd use a data views builder. - -When Umbraco UI Builder resolves a data views builder it will attempt to do so from the global DI container. This means you can inject any dependencies that you require for your builder. If there is no type defined in the DI container, Umbraco UI Builder will fall-back to manually instantiating a new instance of value mapper. - -## Defining a data views builder - -To define a data views builder you can create a class that inherits from the base class `DataViewsBuilder` and implements the abstract methods. - -````csharp -// Example -public class PersonDataViewsBuilder : DataViewsBuilder -{ - public override IEnumerable GetDataViews() - { - // Generate and return a list of data views - } - - public override Expression> GetDataViewWhereClause(string dataViewAlias) - { - // Return a where clause expression for the supplied data view alias - } -} -```` - -The required methods are: - -* **GetDataViews:** Returns the list of data views to choose from. -* **GetDataViewWhereClause:** Returns the boolean **where clause** expression for the given data views alias. - -## Setting the data views builder of a collection - -Setting a data views builder is controlled via the [collections](../collections/overview.md) configuration. - -### **SetDataViewsBuilder<TDataViewsBuilder>() : CollectionConfigBuilder<TEntityType>** - -Sets the collections data views builder which allows you to define the data views dynamically at run time. - -````csharp -// Example -collectionConfig.SetDataViewsBuilder(); -```` - -### **SetDataViewsBuilder(Type dataViewsBuilderType) : CollectionConfigBuilder<TEntityType>** - -Sets the collections data views builder which allows you to define the data views dynamically at run time. - -````csharp -// Example -collectionConfig.SetDataViewsBuilder(typeof(PersonDataViewsBuilder)); -```` - -### **SetDataViewsBuilder(DataViewsBuilder<TEntityType> dataViewsBuilder) : CollectionConfigBuilder<TEntityType>** - -Sets the collections data views builder which allows you to define the data views dynamically at run time. - -````csharp -// Example -collectionConfig.SetDataViewsBuilder(new PersonDataViewsBuilder()); -```` diff --git a/14/umbraco-ui-builder/filtering/data-views.md b/14/umbraco-ui-builder/filtering/data-views.md deleted file mode 100644 index e35edbcc384..00000000000 --- a/14/umbraco-ui-builder/filtering/data-views.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -description: Configuring data views in Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Data Views - -Data views allow you to define multiple, pre-filtered views of the same data source. This can be useful when entities exist in different states and you want a way to toggle between them. - -![Data Views](../images/data_views.png) - -## Defining data views - -Data views are defined via the [collections](../collections/overview.md) configuration. - -### **AddDataView(string name, Lambda whereClauseExpression) : CollectionConfigBuilder<TEntityType>** - -Adds a data view with the given name and **where clause** filter expression. Expression must be a `boolean` expression. - -````csharp -// Example -collectionConfig.AddDataView("Active", p => p.IsActive); -```` - -### **AddDataView(string group, string name, Lambda whereClauseExpression) : CollectionConfigBuilder<TEntityType>** - -Adds a data view with the given group, name and **where clause** filter expression. Expression must be a `boolean` expression. - -````csharp -// Example -collectionConfig.AddDataView("Status", "Active", p => p.IsActive); -```` diff --git a/14/umbraco-ui-builder/filtering/filterable-properties.md b/14/umbraco-ui-builder/filtering/filterable-properties.md deleted file mode 100644 index 0c61d0b18e4..00000000000 --- a/14/umbraco-ui-builder/filtering/filterable-properties.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -description: Configuring filterable properties in Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Filterable Properties - -Umbraco UI Builder can dynamically build a filter dialog choosing appropriate editor views for you based on a basic property configuration. Properties of a number or date types will become range pickers and enums. Properties with options defined will become select/checkbox lists and all other properties will become text input filters. - -![Filterable Properties](../images/filterable_properties.png) - -## Defining filterable properties - -Defining filterable properties is controlled via the [collections](../collections/overview.md) configuration. - -### **AddFilterableProperty(Lambda filterablePropertyExpression, Lambda filterConfig = null) : CollectionConfigBuilder<TEntityType>** - -Adds the given property to the filterable properties collection. - -````csharp -// Example -collectionConfig.AddFilterableProperty(p => p.FirstName, filterConfig => filterConfig - // ... -); -```` - -## Changing the label of a filterable property - -### **SetLabel(string label) : FilterablePropertyConfigBuilder<TEntityType, TValueType>** - -````csharp -// Example -filterConfig.SetLabel("First Name"); -```` - -## Adding a description to a filterable property - -### **SetDescription(string description) : FilterablePropertyConfigBuilder<TEntityType, TValueType>** - -````csharp -// Example -filterConfig.SetDescription("The first name of the person"); -```` - -## Defining basic options for a filterable property - -### **SetOptions(IDictionary<TValueType, string> options) : FilterablePropertyConfigBuilder<TEntityType, TValueType>** - -````csharp -// Example -filterConfig.SetOptions(new Dictionary { - { "Option1", "Option One" }, - { "Option2", "Option Two" } -}); -```` - -## Defining options with custom compare clauses for a filterable property - -### **AddOption(object key, string label, Lambda compareExpression) : FilterablePropertyConfigBuilder<TEntityType, TValueType>** - -````csharp -// Example -filterConfig.AddOption("Option1", "Option One", (val) => val != "Option Two"); -```` - -## Configuring the mode of a filterable property - -For filterable properties with options you can configure whether the options should be multiple or single choice. - -### **SetMode(FilterMode mode) : FilterablePropertyConfigBuilder<TEntityType, TValueType>** - -````csharp -// Example -filterConfig.SetMode(FilterMode.MultipleChoice); -```` diff --git a/14/umbraco-ui-builder/filtering/global-filters.md b/14/umbraco-ui-builder/filtering/global-filters.md deleted file mode 100644 index 6ead9ff183f..00000000000 --- a/14/umbraco-ui-builder/filtering/global-filters.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -description: Configuring a global filter in Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Global Filters - -If you want to work with a subset of data within a given collection then this is where the global filters come in handy. These allow you to define a filter to apply to all queries for a given collection. - -## Applying a global filter - -Applying a global filter is controlled via the [collections](../collections/overview.md) configuration. - -### **SetFilter(Lambda whereClauseExpression) : CollectionConfigBuilder<TEntityType>** - -Sets the filter **where clause** expression. Expression must be a `boolean` expression. - -````csharp -// Example -collectionConfig.SetFilter(p => p.Current); -```` diff --git a/14/umbraco-ui-builder/filtering/overview.md b/14/umbraco-ui-builder/filtering/overview.md deleted file mode 100644 index 3721654078b..00000000000 --- a/14/umbraco-ui-builder/filtering/overview.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -description: Configuring filtering in Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Filtering - -Beyond [searching](../searching/overview.md) there might be times when you need to be able to create specific views of a collection's data. To help with this Umbraco UI Builder has different filtering mechanisms available. - -![Filterable Properties](../images/filterable_properties.png) - -Choose a filtering method from the list below to find out more. - -{% content-ref url="global-filters.md" %} -[global-filters.md](global-filters.md) -{% endcontent-ref %} -{% content-ref url="data-views.md" %} -[data-views.md](data-views.md) -{% endcontent-ref %} -{% content-ref url="filterable-properties.md" %} -[filterable-properties.md](filterable-properties.md) -{% endcontent-ref %} diff --git a/14/umbraco-ui-builder/getting-started/configuration.md b/14/umbraco-ui-builder/getting-started/configuration.md deleted file mode 100644 index 69e9bf105aa..00000000000 --- a/14/umbraco-ui-builder/getting-started/configuration.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -description: Configuring Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Configuration - -Umbraco UI Builder can be configured directly via the `AddUIBuilder` extension method on `IUmbracoBuilder`. - -## AddUIBuilder - -To configure Umbraco UI Builder via the `AddUIBuilder` extension method, You can look in the `Program.cs` file in the root of your web project. From within this file, before the call to `AddComposers()` we can add our `AddUIBuilder` configuration. - -```csharp -builder.CreateUmbracoBuilder() - .AddBackOffice() - .AddWebsite() - .AddUIBuilder(cfg => { - // Apply your configuration here - }) - .AddDeliveryApi() - .AddComposers() - .Build(); -``` - -The `AddUIBuilder` extension method accepts a single parameter, a delegate function with one of the Umbraco UI Builder configuration builder arguments. With this, you can then call the relevant fluent APIs to define your solution. diff --git a/14/umbraco-ui-builder/getting-started/overview.md b/14/umbraco-ui-builder/getting-started/overview.md deleted file mode 100644 index 0dd186f3b98..00000000000 --- a/14/umbraco-ui-builder/getting-started/overview.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -description: >- - Getting Started with Umbraco UI Builder, the backoffice UI builder for - Umbraco. ---- - -# Overview - -This section will guide you through the key steps necessary to get you started with Umbraco UI Builder. - -It is assumed that you have an Umbraco 10+ website configured, and ready to install Umbraco UI Builder. - -{% hint style="info" %} -Find detailed instructions on how to install the latest version of Umbraco in the [Umbraco CMS documentation](https://docs.umbraco.com/umbraco-cms/fundamentals/setup/install). -{% endhint %} - -## System Requirements - -At this time, the minimum requirements for using Umbraco UI Builder are as follows: - -* **Umbraco CMS version 10.0/12.0+** -* **SQL Server Database** (SQLite is fine for testing, but not recommended for live deployments) - -## Versioning - -This is an add-on product to Umbraco CMS. Umbraco UI Builder follows the [versioning strategy laid out for Umbraco CMS](https://umbraco.com/products/knowledge-center/versioning-and-release-cadence/). diff --git a/14/umbraco-ui-builder/getting-started/user-interface.md b/14/umbraco-ui-builder/getting-started/user-interface.md deleted file mode 100644 index 5f7b92fc6b1..00000000000 --- a/14/umbraco-ui-builder/getting-started/user-interface.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -description: Key User Interface Concepts used by Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# User Interface - -Before you get to know Umbraco UI Builder, you need to become familiar with the Umbraco UI and a few of its concepts. This is because Umbraco UI Builder reuses these same concepts for constructing its UI. - -![Sections, Trees, and Dashboards](../images/ui_01.png) - -**1. Section** A distinct area of the Umbraco backoffice. -**2. Tree** A hierarchical structure to help organize a section. -**3. Dashboard** An intro screen for a section, usually with useful links for that section. - -![List View](../images/ui_02.png) - -**4. List View** A list-based view of items in a tree node. - -![Editor](../images/ui_03.png) - -**5. Editor** The main content editing area is made up of tabs, fieldsets, and fields. - -![Context Apps and Tabs](../images/ui_06.png) - -**6. Context Apps** A contextual section of a given editor UI. -**7. Tabs** A tabbed container of content. - -![Menu Item](../images/ui_04.png) - -**8. Menu Item** A context menu item + action. - -![Bulk Action](../images/ui_05.png) - -**9. Bulk Action** An action to perform on multiple list view items at once. diff --git a/14/umbraco-ui-builder/guides/creating-your-first-integration.md b/14/umbraco-ui-builder/guides/creating-your-first-integration.md deleted file mode 100644 index 49c871ae1b2..00000000000 --- a/14/umbraco-ui-builder/guides/creating-your-first-integration.md +++ /dev/null @@ -1,112 +0,0 @@ ---- -description: Creating your first integration with Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Creating your first integration - -In this guide, you can find the necessary steps needed for a basic implementation using Umbraco UI Builder to manage a single custom database table. - -## Set up the database - -Out of the box, Umbraco UI Builder works using PetaPoco as the persistence layer as this is what ships with Umbraco. If you prefer, it is possible to use a custom [Repository](../advanced/repositories.md). However, for getting started, it is expected that you are using this default strategy. - -Start by setting up a database table for your model (you might want to populate it with some dummy data as well while learning). We’ll use the following as an example: - -```sql -CREATE TABLE [Person] ( - [Id] int IDENTITY (1,1) NOT NULL, - [Name] nvarchar(255) NOT NULL, - [JobTitle] nvarchar(255) NOT NULL, - [Email] nvarchar(255) NOT NULL, - [Telephone] nvarchar(255) NOT NULL, - [Age] int NOT NULL, - [Avatar] nvarchar(255) NOT NULL -); -``` - -## Set up your model - -With the database table setup, we then need to create the associated Poco model in our project. - -```csharp -[TableName("Person")] -[PrimaryKey("Id")] -public class Person -{ - [PrimaryKeyColumn] - public int Id { get; set; } - public string Name { get; set; } - public string JobTitle { get; set; } - public string Email { get; set; } - public string Telephone { get; set; } - public int Age { get; set; } - public string Avatar { get; set; } -} -``` - -## Configure Umbraco UI Builder - -With the database and model setup, we can now start to configure Umbraco UI Builder itself. The entry point for the Umbraco UI Builder configuration is via the `AddUIBuilder` extension method. On this method, we call on the `IUmbracoBuilder` instance within the `Program.cs` class. - -```csharp -builder.CreateUmbracoBuilder() - .AddBackOffice() - .AddWebsite() - .AddDeliveryApi() - .AddComposers() - .AddUIBuilder(cfg => { - // Apply your configuration here - }) - .Build(); -``` - -For our example, we will use the following configuration: - -```csharp -... -.AddUIBuilder(cfg => { - - cfg.AddSectionAfter("media", "Repositories", sectionConfig => sectionConfig - .Tree(treeConfig => treeConfig - .AddCollection(x => x.Id, "Person", "People", "A person entity", "icon-umb-users", "icon-umb-users", collectionConfig => collectionConfig - .SetNameProperty(p => p.Name) - .ListView(listViewConfig => listViewConfig - .AddField(p => p.JobTitle).SetHeading("Job Title") - .AddField(p => p.Email) - ) - .Editor(editorConfig => editorConfig - .AddTab("General", tabConfig => tabConfig - .AddFieldset("General", fieldsetConfig => fieldsetConfig - .AddField(p => p.JobTitle).MakeRequired() - .AddField(p => p.Age) - .AddField(p => p.Email).SetValidationRegex("[a-zA-Z0-9_.+-]+@[a-zA-Z0-9-]+.[a-zA-Z0-9-.]+") - .AddField(p => p.Telephone).SetDescription("inc area code") - ) - .AddFieldset("Media", fieldsetConfig => fieldsetConfig - .AddField(p => p.Avatar).SetDataType("Upload File") - ) - ) - ) - ) - ) - ); - -}) -... -``` - -## Access your UI - -With your configuration defined and your project compiled, there is one last step to perform before you can access your UI. And that is to give your backoffice user account permission to access the newly defined section. To do this you'll need to login to the backoffice, head to the user's section, and update the user group. There you will need to make sure that your user belongs to the allowed access. - -![User group permissions](../images/permissions.png) - -With the permissions set, you can refresh your browser and you should now see your new section available in the site navigation. - -![People list view](../images/listview.png) - -![People editor](../images/editor.png) - -## Summary - -As you can see, with little code you can start to create powerful interfaces for your custom data structures. diff --git a/14/umbraco-ui-builder/images/bulk_actions.png b/14/umbraco-ui-builder/images/bulk_actions.png deleted file mode 100644 index 9447f4d3179..00000000000 Binary files a/14/umbraco-ui-builder/images/bulk_actions.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/bulk_actions_menu.png b/14/umbraco-ui-builder/images/bulk_actions_menu.png deleted file mode 100644 index 0de260da545..00000000000 Binary files a/14/umbraco-ui-builder/images/bulk_actions_menu.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/cards.png b/14/umbraco-ui-builder/images/cards.png deleted file mode 100644 index 31e2c20c3af..00000000000 Binary files a/14/umbraco-ui-builder/images/cards.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/child_collection_groups.png b/14/umbraco-ui-builder/images/child_collection_groups.png deleted file mode 100644 index 4cb9e5ca297..00000000000 Binary files a/14/umbraco-ui-builder/images/child_collection_groups.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/child_collections.png b/14/umbraco-ui-builder/images/child_collections.png deleted file mode 100644 index b0f844ceeb8..00000000000 Binary files a/14/umbraco-ui-builder/images/child_collections.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/comments_listview.png b/14/umbraco-ui-builder/images/comments_listview.png deleted file mode 100644 index fee43943a15..00000000000 Binary files a/14/umbraco-ui-builder/images/comments_listview.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/container_actions_menu.png b/14/umbraco-ui-builder/images/container_actions_menu.png deleted file mode 100644 index 1e6871db48d..00000000000 Binary files a/14/umbraco-ui-builder/images/container_actions_menu.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/content_apps.png b/14/umbraco-ui-builder/images/content_apps.png deleted file mode 100644 index 23604f20f04..00000000000 Binary files a/14/umbraco-ui-builder/images/content_apps.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/context_app.png b/14/umbraco-ui-builder/images/context_app.png deleted file mode 100644 index b9f509ddfd8..00000000000 Binary files a/14/umbraco-ui-builder/images/context_app.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/dashboard.png b/14/umbraco-ui-builder/images/dashboard.png deleted file mode 100644 index 6e7f09e3d8b..00000000000 Binary files a/14/umbraco-ui-builder/images/dashboard.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/dashboards.png b/14/umbraco-ui-builder/images/dashboards.png deleted file mode 100644 index aec51a0777f..00000000000 Binary files a/14/umbraco-ui-builder/images/dashboards.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/data_views.png b/14/umbraco-ui-builder/images/data_views.png deleted file mode 100644 index c577f854dc5..00000000000 Binary files a/14/umbraco-ui-builder/images/data_views.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/editor.png b/14/umbraco-ui-builder/images/editor.png deleted file mode 100644 index 81a6b02af94..00000000000 Binary files a/14/umbraco-ui-builder/images/editor.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/entity_actions_menu.png b/14/umbraco-ui-builder/images/entity_actions_menu.png deleted file mode 100644 index 2757026dd17..00000000000 Binary files a/14/umbraco-ui-builder/images/entity_actions_menu.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/entity_picker_config.png b/14/umbraco-ui-builder/images/entity_picker_config.png deleted file mode 100644 index fee19974ea0..00000000000 Binary files a/14/umbraco-ui-builder/images/entity_picker_config.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/entity_picker_picked.png b/14/umbraco-ui-builder/images/entity_picker_picked.png deleted file mode 100644 index a09f97ee97b..00000000000 Binary files a/14/umbraco-ui-builder/images/entity_picker_picked.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/entity_picker_search.png b/14/umbraco-ui-builder/images/entity_picker_search.png deleted file mode 100644 index 5278a64ffcf..00000000000 Binary files a/14/umbraco-ui-builder/images/entity_picker_search.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/entity_picker_setup.png b/14/umbraco-ui-builder/images/entity_picker_setup.png deleted file mode 100644 index 2f202127cea..00000000000 Binary files a/14/umbraco-ui-builder/images/entity_picker_setup.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/filterable_properties.png b/14/umbraco-ui-builder/images/filterable_properties.png deleted file mode 100644 index 161eac28ede..00000000000 Binary files a/14/umbraco-ui-builder/images/filterable_properties.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/listview.png b/14/umbraco-ui-builder/images/listview.png deleted file mode 100644 index b9a90f0f82e..00000000000 Binary files a/14/umbraco-ui-builder/images/listview.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/menu_items.png b/14/umbraco-ui-builder/images/menu_items.png deleted file mode 100644 index 3662552ba18..00000000000 Binary files a/14/umbraco-ui-builder/images/menu_items.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/permissions.png b/14/umbraco-ui-builder/images/permissions.png deleted file mode 100644 index ebb680c3fe3..00000000000 Binary files a/14/umbraco-ui-builder/images/permissions.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/related_collections_child.png b/14/umbraco-ui-builder/images/related_collections_child.png deleted file mode 100644 index 16f9bf58cfb..00000000000 Binary files a/14/umbraco-ui-builder/images/related_collections_child.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/related_collections_diagram.png b/14/umbraco-ui-builder/images/related_collections_diagram.png deleted file mode 100644 index 007436a85bf..00000000000 Binary files a/14/umbraco-ui-builder/images/related_collections_diagram.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/related_collections_parent.png b/14/umbraco-ui-builder/images/related_collections_parent.png deleted file mode 100644 index 7c763aebab5..00000000000 Binary files a/14/umbraco-ui-builder/images/related_collections_parent.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/row_actions_menu.png b/14/umbraco-ui-builder/images/row_actions_menu.png deleted file mode 100644 index a0fcf0ef886..00000000000 Binary files a/14/umbraco-ui-builder/images/row_actions_menu.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/save_actions_menu.png b/14/umbraco-ui-builder/images/save_actions_menu.png deleted file mode 100644 index cf818ba674a..00000000000 Binary files a/14/umbraco-ui-builder/images/save_actions_menu.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/search.png b/14/umbraco-ui-builder/images/search.png deleted file mode 100644 index 3892741bbfd..00000000000 Binary files a/14/umbraco-ui-builder/images/search.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/sections.png b/14/umbraco-ui-builder/images/sections.png deleted file mode 100644 index bfcea850b44..00000000000 Binary files a/14/umbraco-ui-builder/images/sections.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/tree.png b/14/umbraco-ui-builder/images/tree.png deleted file mode 100644 index c9956e07e08..00000000000 Binary files a/14/umbraco-ui-builder/images/tree.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/ui_01.png b/14/umbraco-ui-builder/images/ui_01.png deleted file mode 100644 index ac15c165bd9..00000000000 Binary files a/14/umbraco-ui-builder/images/ui_01.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/ui_02.png b/14/umbraco-ui-builder/images/ui_02.png deleted file mode 100644 index dd7e6610094..00000000000 Binary files a/14/umbraco-ui-builder/images/ui_02.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/ui_03.png b/14/umbraco-ui-builder/images/ui_03.png deleted file mode 100644 index b7024f5a0ad..00000000000 Binary files a/14/umbraco-ui-builder/images/ui_03.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/ui_04.png b/14/umbraco-ui-builder/images/ui_04.png deleted file mode 100644 index c22e7b82fe1..00000000000 Binary files a/14/umbraco-ui-builder/images/ui_04.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/ui_05.png b/14/umbraco-ui-builder/images/ui_05.png deleted file mode 100644 index 54552b1c2cf..00000000000 Binary files a/14/umbraco-ui-builder/images/ui_05.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/ui_06.png b/14/umbraco-ui-builder/images/ui_06.png deleted file mode 100644 index 9eeddc5c48f..00000000000 Binary files a/14/umbraco-ui-builder/images/ui_06.png and /dev/null differ diff --git a/14/umbraco-ui-builder/images/virtual-sub-tree.png b/14/umbraco-ui-builder/images/virtual-sub-tree.png deleted file mode 100644 index a2d4f5763b1..00000000000 Binary files a/14/umbraco-ui-builder/images/virtual-sub-tree.png and /dev/null differ diff --git a/14/umbraco-ui-builder/installation/installation.md b/14/umbraco-ui-builder/installation/installation.md deleted file mode 100644 index a92e0322301..00000000000 --- a/14/umbraco-ui-builder/installation/installation.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -description: Installing Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Installation - -Umbraco UI Builder is installed via the NuGet package manager by issuing the following command in your web project. - -```bash -dotnet add package Umbraco.UIBuilder -``` - -If you wish to install Umbraco UI Builder into a class library without the UI elements, you can add a reference to the `Umbraco.UIBuilder.Startup` package instead. - -```bash -dotnet add package Umbraco.UIBuilder.Startup -``` - -Alternatively, you can also find and install the NuGet package via the NuGet Package Manager graphical user interface (GUI) in Visual Studio. - -## Installing a License - -See the [Licensing page](licensing-model.md#installing-your-license) for details on how to install a license. diff --git a/14/umbraco-ui-builder/installation/licensing-model.md b/14/umbraco-ui-builder/installation/licensing-model.md deleted file mode 100644 index fffd9bdbd0e..00000000000 --- a/14/umbraco-ui-builder/installation/licensing-model.md +++ /dev/null @@ -1,131 +0,0 @@ -# Licensing - -Umbraco UI Builder is a commercial product. You can run an Umbraco UI Builder unrestricted locally without the need a license. Running Umbraco UI Builder on a public domain will display a warning banner in the backoffice and will limit usage to a single editable collection. To remove these restrictions, you'll need to have a **valid license**. - -## How does it work? - -Licenses are sold per backoffice domain and will also work on all subdomains. If you have alternative staging/qa environment domains, additional domains can be added to the license on request. - -{% hint style="info" %} -The licenses are not bound to a specific product version. They will work for all versions of the related product. -{% endhint %} - -Let's say that you have a license configured for your domain, `mysite.com`, and you've requested two development domains, `devdomain.com` and `devdomain2.com`. - -The license will cover the following domains: - -* `localhost` -* `*.local` -* `*.mysite.com` -* `www.mysite.com` -* `devdomain.com` -* `www.devdomain.com` -* `devdomain2.com` -* `www.devdomain2.com` - -{% hint style="info" %} -You can have only 1 license per Umbraco installation. -{% endhint %} - -## What does a license cover? - -There are a few differences as to what the licenses cover: - -* A single license covers the installation of Umbraco UI Builder in 1 production backoffice domain, as well as in any requested development domains. -* The production domain includes **all subdomains** (e.g. `*.mysite.com`). -* The development domains work with or without the `www` subdomain. -* The license allows for an unlimited number of editable collections. -* The license also includes `localhost` and `*.local` as a valid domain. - -{% hint style="info" %} -If you have multiple backoffice domains pointing at the same installation, you can purchase and [add **additional domains**](licensing-model.md#add-additional-domains) to your license. - -This is an add-on domain for existing licenses. Refunds will not be given for this product. -{% endhint %} - -## Configuring your license - -You can look at the pricing, features, and purchase a license on the [Umbraco UI Builder](https://umbraco.com/products/add-ons/ui-builder/) page. On this page, you can fill out the form with your project details and requirements. A member of the Sales team will manage this process. In the process, you will need to provide all domains you wish to have covered by the license such as primary and staging/QA domains. You should then receive a license code to be installed in your solution. - -### Add additional domains - -If you require to add additional domains to the license, [reach out to the sales team](https://umbraco.com/products/add-ons/ui-builder/). They will manage your request and take care of the process. - -## Installing your license - -Once you have received your license code it needs to be installed on your site. - -1. Open the root directory for your project files. -2. Locate and open the `appSettings.json` file. -3. Add your Umbraco UI builder license key to `Umbraco:Licenses:Umbraco.UIBuilder`: - -```json -"Umbraco": { - "Licenses": { - "Products": { - "Umbraco.UIBuilder": "YOUR_LICENSE_KEY" - } - } -} -``` - - -{% hint style="info" %} -You might run into issues when using a period in the product name when using environment variables. Use an underscore in the product name instead, to avoid problems. - -```json -"Umbraco_UIBuilder": "YOUR_LICENSE_KEY" -``` -{% endhint %} - -### Verify the license installation - -You can verify that your license is successfully installed by logging into your project's backoffice and navigating to the settings section. Here you will see a license dashboard which should display the status of your license. - -### Validating a license without an outgoing Internet connection - -Some Umbraco installations will have a highly locked down production environment, with firewall rules that prevent outgoing HTTP requests. This will interfere with the normal process of license validation. - -On start-up, and periodically whilst Umbraco is running, the license component used by Umbraco UIBuilder will make an HTTP POST request to `https://license-validation.umbraco.com/api/ValidateLicense`. - -If it's possible to do so, the firewall rules should be adjusted to allow this request. - -If such a change is not feasible, there is another approach you can use. - -You will need to have a server, or serverless function, that is running and can make a request to the online license validation service. That needs to run on a daily schedule, making a request and relaying it onto the restricted Umbraco environment. - -To set this up, firstly ensure you have a reference to `Umbraco.Licenses` version 13.1 or higher. If the version of UIBuilder you are using depends on an earlier version, you can add a direct package reference for `Umbraco.Licenses`. - -Then configure a random string as an authorization key in configuration. This is used as protection to ensure only valid requests are handled. You can also disable the normal regular license checks - as there is no point in these running if they will be blocked: - -```json - "Umbraco": { - "Licenses": { - "Umbraco.UIBuilder": "" - }, - "LicensesOptions": { - "EnableScheduledValidation": false, - "ValidatedLicenseRelayAuthKey": "" - } -``` - -Your Internet enabled server should make a request of the following form to the online license validation service: - -``` -POST https://license-validation.umbraco.com/api/ValidateLicense -{ - "ProductId": "Umbraco.UIBuilder", - "LicenseKey": "", - "Domain": "" -} -``` - -The response should be relayed exactly via an HTTP request to your restricted Umbraco environment: - -``` -POST http:///umbraco/licenses/validatedLicense/relay?productId=&licenseKey= -``` - -A header with a key of `X-AUTH-KEY` and value of the authorization key you have configured should be provided. - -This will trigger the same processes that occur when the normal scheduled validation completes ensuring your product is considered licensed. diff --git a/14/umbraco-ui-builder/known-issues.md b/14/umbraco-ui-builder/known-issues.md deleted file mode 100644 index 30a65ec93a2..00000000000 --- a/14/umbraco-ui-builder/known-issues.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -description: Known issues in Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Known Issues - -Umbraco UI Builder tries its best to mimic the content pipeline as closely as possible whilst sticking to public and supported APIs. This is so that the Data Type suite can be used fully for editing properties. There are some features in the Umbraco Core that are locked away in internal methods. This means that some features may not be fully supported. Below is a list of known issues to date. - -{% hint style="warning" %} -This page is a work in progress and may undergo further revisions, updates, or amendments. The information contained herein is subject to change without notice. -{% endhint %} - -## Property Editors - -### Tags - -Whilst we have support for persisting the tag's value, we don't currently have the ability to write these tags to the `cmsTags` DB table. This is all handled via a `tagsRepository` which is internal so we currently can't save to it as core does. diff --git a/14/umbraco-ui-builder/miscellaneous/conventions.md b/14/umbraco-ui-builder/miscellaneous/conventions.md deleted file mode 100644 index 3715219a956..00000000000 --- a/14/umbraco-ui-builder/miscellaneous/conventions.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -description: Conventions used by Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Conventions - -## Fluent Conventions - -Most configuration methods in Umbraco UI Builder aim to be fluent. This means that they return a relevant config instance allowing to chain multiple methods calls together in one. For those who prefer to be a bit more verbose, many methods also accept an optional lambda expression. This allows you to pass in a delegate to perform the inner configuration of the element being defined. - -```csharp -// Chaining example -config.AddSection("Repositories").Tree().AddCollection(p => p.Id, "Person", "People"); - -// Delegate example -config.AddSection("Repositories", sectionConfig => { - sectionConfig.Tree(treeConfig => { - treeConfig.AddCollection(p => p.Id, "Person", "People"); - }); -}); -``` - -## Naming Conventions - -Throughout the API, where a method name starts with **Add** then multiple configurations can be declared. Whereas if a method name starts with **Set** then only one instance of the configuration can be declared within the current configuration context. diff --git a/14/umbraco-ui-builder/miscellaneous/umbraco-aliases.md b/14/umbraco-ui-builder/miscellaneous/umbraco-aliases.md deleted file mode 100644 index a8a49526190..00000000000 --- a/14/umbraco-ui-builder/miscellaneous/umbraco-aliases.md +++ /dev/null @@ -1,92 +0,0 @@ ---- -description: A list of useful Umbraco aliases for use with Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Umbraco Aliases - -In a number of places in the Umbraco UI Builder API, you are required to know the aliases of other elements. For example, when you are adding sections, context apps, or dashboards before/after other instances. This is basic enough when it's referencing aliases of things defined in the Umbraco UI Builder config. However, for existing Umbraco instances it can be hard to find them so below is documented a number of known aliases for different elements. - -## Dashboard aliases - -### **Content** - -| Name | Alias | -| -- | -- | -| Getting Started | `contentIntro` | -| Redirect URL Management | `contentRedirectManager` | - -### **Media** - -| Name | Alias | -| -- | -- | -| Content | `mediaFolderBrowser` | - -### **Settings** - -| Name | Alias | -| -- | -- | -| Welcome | `settingsWelcome` | -| Examine Management | `settingsExamine` | -| Published Status | `settingsPublishedStatus` | -| Models Builder | `settingsModelsBuilder` | -| Health Check | `settingsHealthCheck` | - -### **Members** - -| Name | Alias | -| -- | -- | -| Getting Started | `memberIntro` | - -## Content App aliases - -### **Content** - -| Name | Alias | -| -- | -- | -| Content | `umbContent` | -| Info | `umbInfo` | - -### **Media** - -| Name | Alias | -| -- | -- | -| Content | `umbContent` | -| Info | `umbInfo` | - -### **Members** - -| Name | Alias | -| -- | -- | -| Content | `umbContent` | -| Info | `umbInfo` | - -### **ContentTypes** - -| Name | Alias | -| -- | -- | -| Design | `design` | -| List View | `listView` | -| Permissions | `permissions` | -| Templates | `templates` | - -## Section aliases - -| Name | Alias | -| -- | -- | -| Content | `content` | -| Media | `media` | -| Settings | `settings` | -| Packages | `packages` | -| Users | `users` | -| Members | `member` | -| Forms | `forms` | -| Translation | `translation` | - -## Tree aliases - -| Name | Alias | -| -- | -- | -| Content | `content` | -| Media | `media` | -| Members | `member` | -| Member Groups | `memberGroups` | diff --git a/14/umbraco-ui-builder/property-editors/entity-picker.md b/14/umbraco-ui-builder/property-editors/entity-picker.md deleted file mode 100644 index 16e23ab2f5f..00000000000 --- a/14/umbraco-ui-builder/property-editors/entity-picker.md +++ /dev/null @@ -1,48 +0,0 @@ ---- -description: Using the entity picker property editor with Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Entity Picker - -The Entity Picker property editor is an Umbraco property editor that lets you select one or more entities from an Umbraco UI Builder collection. - -## Configuring an entity picker - -To configure an entity picker you need to create a Data Type in the Umbraco backoffice. From the property editor dropdown choose 'Umbraco UI Builder Entity Picker'. - -![Data Type config](../images/entity_picker_config.png) - -From there choose 'Section' and 'Collection' you wish to pick entities from. You can also choose an optional list view 'Data View' if there are any configured. - -You can also set a minimum and maximum number of items to be able to pick if required. - -With an entity picker Data Type defined, finish off the configuration by adding it to the desired Document Type definition. - -![Document Type config](../images/entity_picker_setup.png) - -## Using an entity picker - -Using the entity picker should be pretty familiar as it aims to mimic the content picker as closely as possible. - -To pick an entity click the 'Add' link to launch the picker dialog. The dialog should present a paginated list of entities to pick from. If any searchable fields were configured for the entity type, you can perform a search by typing a search term in the search input field. - -![Entity picker dialog](../images/entity_picker_search.png) - -To pick your items click on the entity names and then click 'Select' in the bottom right-hand corner. - -The picker should display a summary of the selected entities which can be sorted by dragging the selected entities into the desired order. - -![Entity picker values](../images/entity_picker_picked.png) - -To save the value either **save** or **save and publish** the current document. - -## Getting the value of an entity picker - -The entity picker property editor comes with a built-in [value converter](https://docs.umbraco.com/umbraco-cms/extending/property-editors/property-value-converters/). This means that whenever you retrieve the property value from Umbraco it will return the actual selected entities, even converting them to the relevant type. - -````csharp -// Example -foreach(var p in Model.People){ - ... -} -```` diff --git a/14/umbraco-ui-builder/property-editors/overview.md b/14/umbraco-ui-builder/property-editors/overview.md deleted file mode 100644 index 59f17f6be6b..00000000000 --- a/14/umbraco-ui-builder/property-editors/overview.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -description: Property Editors available with Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Property Editors - -As well as the API for managing your custom data source, Umbraco UI Builder also comes with some property editors. Those property editors help you work with your data inside Umbraco content nodes. - -The property editors available are: - -{% content-ref url="entity-picker.md" %} -[Entity Picker](entity-picker.md) -{% endcontent-ref %} diff --git a/14/umbraco-ui-builder/release-notes.md b/14/umbraco-ui-builder/release-notes.md deleted file mode 100644 index 976f87a2a25..00000000000 --- a/14/umbraco-ui-builder/release-notes.md +++ /dev/null @@ -1,50 +0,0 @@ ---- -description: >- - Get an overview of the things changed and fixed in each version of Umbraco UI - Builder. ---- - -# Release Notes - -In this section, we have summarized the changes to Umbraco UI Builder released in each version. Each version is presented with a link to the [UI Builder issue tracker](https://github.com/umbraco/Umbraco.UIBuilder.Issues/issues) showing a list of issues resolved in the release. We also link to the individual issues themselves from the detail. - -If there are any breaking changes or other issues to be aware of when upgrading they are also noted here. - -{% hint style="info" %} -If you are upgrading to a new major version, check the breaking changes in the [Version Specific Upgrade Notes](upgrading/version-specific.md) article. -{% endhint %} - -## Release History - -This section contains the release notes for Umbraco UI Builder 14 including all changes for this version. - -#### [**14.0.3**](https://github.com/umbraco/Umbraco.UIBuilder.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.0.3) **(February 5th 2025)** - -* Fixed an issue with filter input values persistence for filterable properties. -* Filterable properties UI updates - -#### [**14.0.2**](https://github.com/umbraco/Umbraco.UIBuilder.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.0.2) **(January 22nd 2025)** - -* Added updates to the licensing engine. -* Fixed an error in the entity update action. - -#### [**14.0.1**](https://github.com/umbraco/Umbraco.UIBuilder.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.0.1) **(December 16th 2024)** - -* Added previously validated license resolver, to validate a license if a validation process was already executed successfully in the past 7 days. -* Fixed an issue caused by `where` clauses for filter expression and deleted property. -* Allow entity properties to be searched based on pattern: `StartsWith` | `Contains` [#116](https://github.com/umbraco/Umbraco.UIBuilder.Issues/issues/116) -* Switch entity create/edit header to label view for read-only collections [#111](https://github.com/umbraco/Umbraco.UIBuilder.Issues/issues/111) - -#### [**14.0.0**](https://github.com/umbraco/Umbraco.UIBuilder.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.0.0) **(November 11th 2024)** - -* Release major version of `Umbraco.UIBuilder 14` - -#### [**14.0.0-alpha1**](https://github.com/umbraco/Umbraco.UIBuilder.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.0.0) **(September 2nd 2024)** - -* Product migrated to support the new Web Component-based Umbraco - -You can read more about the new Backoffice [in the Umbraco CMS documentation](https://docs.umbraco.com/umbraco-cms/extending/customize-the-editing-experience). - -## Legacy release notes - -You can find the release notes for **Konstrukt** in the [Change log file on GitHub](changelog-archive/changelog.md). diff --git a/14/umbraco-ui-builder/searching/overview.md b/14/umbraco-ui-builder/searching/overview.md deleted file mode 100644 index 3d91fcb6f60..00000000000 --- a/14/umbraco-ui-builder/searching/overview.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -description: Configuring searching in Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Searching - -Beyond listing collection entities, if you need to be able to locate specific entities within a collection then Umbraco UI Builder provides a search API. - -![Search](../images/search.png) - -Get started by reviewing how to define searchable properties. - -{% content-ref url="searchable-properties.md" %} -[searchable-properties.md](searchable-properties.md) -{% endcontent-ref %} diff --git a/14/umbraco-ui-builder/searching/searchable-properties.md b/14/umbraco-ui-builder/searching/searchable-properties.md deleted file mode 100644 index 9e7acf3a322..00000000000 --- a/14/umbraco-ui-builder/searching/searchable-properties.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -description: Configuring searchable properties in Umbraco UI Builder, the backoffice UI builder for Umbraco. ---- - -# Searchable Properties - -Searchable properties allow you to define any `String` based properties on a model. They will be searchable via Umbraco UI Builder's list view and entity picker search controls. - -You can also use any `String` based property of nested objects of a model, as long as the parent object is not null. - -![Search](../images/search.png) - -## Defining searchable properties - -### **AddSearchableProperty(Lambda searchablePropertyExpression) : CollectionConfigBuilder<TEntityType>** - -Adds the given property to the searchable properties collection. - -````csharp -// Example -collectionConfig.AddSearchableProperty(p => p.FirstName); -collectionConfig.AddSearchableProperty(p => p.Address.Street); -```` - -## Search Expression Pattern - -Up to version 14.0.1, the search was performed using the `StartsWith` method call. -From 14.0.1 and up, search operations can be performed using the `Contains` method call. - -````csharp -// Example -collectionConfig.AddSearchableProperty(p => p.FirstName); // will search for keywords that start with. -collectionConfig.AddSearchableProperty(p => p.FirstName, SearchExpressionPattern.Contains); // will search for keywords that are contained. -```` diff --git a/14/umbraco-ui-builder/upgrading/migrating-from-konstrukt-to-umbraco-ui-builder.md b/14/umbraco-ui-builder/upgrading/migrating-from-konstrukt-to-umbraco-ui-builder.md deleted file mode 100644 index 7d806be207d..00000000000 --- a/14/umbraco-ui-builder/upgrading/migrating-from-konstrukt-to-umbraco-ui-builder.md +++ /dev/null @@ -1,115 +0,0 @@ ---- -description: Learn how to migrate a Konstrukt solution to Umbraco UI Builder. ---- - -# Migrate from Konstrukt to Umbraco UI Builder - -This guide provides a step-by-step approach to migrating a default Konstrukt solution to Umbraco UI Builder. - -## Key changes - -Before outlining the exact steps, there are a few key changes to be aware of. - -These changes will dictate the steps to take in the process of migrating to Umbraco UI Builder. - -### Project, Package, and Namespace changes - -| Konstrukt | Umbraco UI Builder | -| ------------------------------- | --------------------------------------- | -| Konstrukt.Core | Umbraco.UIBuilder.Core | -| Konstrukt.Infrastructure | Umbraco.UIBuilder.Infrastructure | -| Konstrukt.Web | Umbraco.UIBuilder.Web | -| Konstrukt.Web.UI | Umbraco.UIBuilder.Web.StaticAssets | -| Konstrukt.Startup | Umbraco.UIBuilder.Startup | -| Konstrukt | Umbraco.UIBuilder | - -
- -C# Class changes - -* Namespace changes as documented above. -* Most classes prefixed with the `Konstrukt` keyword have had this prefix removed. - * Examples: `IKonstruktRepository` is now `IRepository` - * Exclusions: The root level `KonstruktConfig` and `KonstruktConfigBuilder` have a `UIBuilder` prefix instead, and the `AddKonstrukt` extension for `IUmbracoBuilder` has been replaced by `AddUIBuilder` - -
- -
- -JavaScript changes - -* All `Konstrukt` controllers have changed namespace to `Umbraco.UIBuilder`. -* All `Konstrukt` prefixed directives, services, and resources are now prefixed with `uibuilder`. - -
- -
- -UI Changes - -* All static UI assets are served via a Razor Compiled Library (RCL) and are no longer found in the `App_Plugins` folder. -* The folder with `App_Plugins` has been renamed from `Konstrukt` to `UmbracoUIBuilder`. - -
- -## Step 1: Replace dependencies - -In this first step, we will be replacing all existing Konstrukt dependencies with Umbraco UI Builder dependencies. - -1. Remove any installed Konstrukt packages: - -```bash -dotnet remove package Konstrukt -``` - -2. Delete the Konstrukt `App_Plugins` folder: - -```bash -rmdir App_Plugins\Konstrukt -``` - -3. Install `Umbraco.UIBuilder`: - -```bash -dotnet add package Umbraco.UIBuilder -``` - -4. Compile your project against .NET 7.0. - -## Step 2: Update namespaces and entity names - -Based on the [Key Changes](./#key-changes) outlined above update all Konstrukt references to the new Umbraco UI Builder alternatives. Ensure you update any Views/Partials that also reference these. - -## Step 3: Update your configuration - -If all your configuration is in a single statement, it would be a case of swapping `AddKonstrukt` to `AddUIBuilder`. If you broke your configuration into multiple steps, or are using `Action` or `Card` classes, you will need to update the config builder/base classes. Those classes need to be updated to their UI Builder alternative names as detailed in [Key Changes](./#key-changes). - - -```csharp -builder.CreateUmbracoBuilder() - .AddBackOffice() - .AddWebsite() - .AddDeliveryApi() - .AddComposers() - .AddUIBuilder(cfg => { - // The rest of your configuration - }) - .Build(); -``` - -## Step 4: Finalizing the migration - -1. Delete any obj/bin folders in your projects to ensure a clean build. -2. Recompile all projects and ensure all dependencies are restored correctly -3. Delete the existing Konstrukt license files in the `umbraco\Licenses` folder. -4. Add your new Umbraco.UIBuilder license key to the `appSettings.json` file: - -```json -"Umbraco": { - "Licenses": { - "Umbraco.UIBuilder": "YOUR_LICENSE_KEY" - } -} -``` - -5. Run the project. diff --git a/14/umbraco-ui-builder/upgrading/upgrade.md b/14/umbraco-ui-builder/upgrading/upgrade.md deleted file mode 100644 index 711a4715aed..00000000000 --- a/14/umbraco-ui-builder/upgrading/upgrade.md +++ /dev/null @@ -1,46 +0,0 @@ -# Upgrading Umbraco UI Builder - -This article shows how to manually upgrade Umbraco UI Builder to run the latest version. -When upgrading Umbraco UI Builder, be sure to also consult the [version specific upgrade](version-specific.md) notes to learn about potential breaking changes and common pitfalls. - -{% hint style="warning" %} -Before upgrading, it is always advisable to take a complete backup of your site and database. -{% endhint %} - -## Get the latest version of Umbraco UI Builder - -To upgrade to the latest version of Umbraco UI Builder you can use: - -- NuGet -- Visual Studio - -### NuGet - -- NuGet installs the latest version of the package when you use the `dotnet add package Umbraco.UIBuilder` command unless you specify a package version: `dotnet add package Umbraco.UIBuilder --version ` - -- After you have added a package reference to your project by executing the `dotnet add package Umbraco.UIBuilder` command in the directory that contains your project file, run `dotnet restore` to install the package. - - -### Visual Studio - -1. Go to `Tools` -> `NuGet Package Manager` -> `Manage NuGet Packages for Solution...` in Visual Studio, to upgrade Umbraco UI Builder: -2. Select **Umbraco.UIBuilder**. -3. Select the latest version from the Version drop-down and click Install. -4. When the command completes, open the **.csproj** file to make sure the package reference is updated: - -```xml - - - -``` - -If you are using one or more of the below sub-packages, they also need to be upgraded as well: - -| Sub-package | Description | -| -- | -- | -| Umbraco.UIBuilder.Core | Core UI Builder functionality that doesn't require any infrastructure-specific dependencies | -| Umbraco.UIBuilder.Infrastructure | Infrastructure-specific project containing implementations of core UI Builder functionality | -| Umbraco.UIBuilder.Web | The core UI Builder logic that requires a web context | -| Umbraco.UIBuilder.Web.StaticAssets | The static assets for the UI Builder presentation layer | -| Umbraco.UIBuilder.Startup | The main logic for registering UI Builder with Umbraco | -| Umbraco.UIBuilder | The main UI Builder package | \ No newline at end of file diff --git a/14/umbraco-ui-builder/upgrading/version-specific.md b/14/umbraco-ui-builder/upgrading/version-specific.md deleted file mode 100644 index ccc0bc72d0c..00000000000 --- a/14/umbraco-ui-builder/upgrading/version-specific.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -description: >- - Version specific documentation for upgrading to new major versions of Umbraco UI Builder. ---- - -# Version Specific Upgrade Notes - -This page covers specific upgrade documentation for when migrating to major 14 of Umbraco UI Builder. - -{% hint style="info" %} -If you are upgrading to a new minor or patch version, you can find information about the breaking changes in the [Release Notes](../release-notes.md) article. -{% endhint %} - -## Version Specific Upgrade Notes History - -Version 14 contains a number of breaking changes from the previous, Konstrukt product. - -See the [Migrate from Konstrukt to Umbraco UI Builder guide](./migrating-from-konstrukt-to-umbraco-ui-builder.md) for full details. - -## Legacy version specific upgrade notes - -You can find the version specific upgrade notes for versions out of support in the [Legacy documentation on GitHub](https://github.com/umbraco/UmbracoDocs/tree/umbraco-eol-versions). diff --git a/14/umbraco-workflow/.gitbook.yaml b/14/umbraco-workflow/.gitbook.yaml deleted file mode 100644 index f96d3e18778..00000000000 --- a/14/umbraco-workflow/.gitbook.yaml +++ /dev/null @@ -1,12 +0,0 @@ -root: ./ - -​structure: - readme: README.md - summary: SUMMARY.md - -redirects: - installing-workflow: installation/installing-workflow.md - licensing: installation/licensing.md - version-specific-upgrade-notes: upgrading/version-specific.md - upgrading-workflow/migrating-workflow: upgrading/migrating-workflow.md - upgrading-workflow/upgrading: upgrading/upgrading.md diff --git a/14/umbraco-workflow/.gitbook/assets/Community.png b/14/umbraco-workflow/.gitbook/assets/Community.png deleted file mode 100644 index 2755aceaf8a..00000000000 Binary files a/14/umbraco-workflow/.gitbook/assets/Community.png and /dev/null differ diff --git a/14/umbraco-workflow/.gitbook/assets/Documentation_blogpost_styleguide_b (1).png b/14/umbraco-workflow/.gitbook/assets/Documentation_blogpost_styleguide_b (1).png deleted file mode 100644 index cd175671fe8..00000000000 Binary files a/14/umbraco-workflow/.gitbook/assets/Documentation_blogpost_styleguide_b (1).png and /dev/null differ diff --git a/14/umbraco-workflow/.gitbook/assets/Documentation_blogpost_styleguide_b.png b/14/umbraco-workflow/.gitbook/assets/Documentation_blogpost_styleguide_b.png deleted file mode 100644 index cd175671fe8..00000000000 Binary files a/14/umbraco-workflow/.gitbook/assets/Documentation_blogpost_styleguide_b.png and /dev/null differ diff --git a/14/umbraco-workflow/.gitbook/assets/umbraco-workflow-1.png b/14/umbraco-workflow/.gitbook/assets/umbraco-workflow-1.png deleted file mode 100644 index cb0fb06fa0c..00000000000 Binary files a/14/umbraco-workflow/.gitbook/assets/umbraco-workflow-1.png and /dev/null differ diff --git a/14/umbraco-workflow/README.md b/14/umbraco-workflow/README.md deleted file mode 100644 index 27df4c61e2e..00000000000 --- a/14/umbraco-workflow/README.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -meta.Title: Umbraco Workflow Documentation -description: Documentation on how to work with Umbraco Workflow in just a few steps ---- - -# Umbraco Workflow Documentation - -Umbraco Workflow allows the creation of multi-stage approval workflows when writing and publishing content. Umbraco Workflow extends Umbraco's out-of-the-box publishing model with multi-stage and configurable approval workflows. A workflow process comprises multiple steps and multiple users assigned to the group responsible for providing approval at each step. - -[Learn more or purchase Umbraco Workflow to get all the features and support.](https://umbraco.com/products/umbraco-workflow/) - -
Installing Umbraco WorkflowInstall Umbraco Workflow in a few steps./installation/installing-workflow.mdumbraco-workflow-1.png
Content Approval Workflows for UmbracoAllows you to design the approval process to fit your organizationapproval-groups.mdCommunity.png
Workflow Section OverviewApproving, rejecting, content reviews, and scheduling workflows are natural additions to the existing toolbox.workflow-section-dashboard.mdDocumentation_blogpost_styleguide_b (1) (1).png
- -{% embed url="" %} -Umbraco Workflow Overview -{% endembed %} - -## Quick Links - -{% content-ref url="getting-started/dashboards-and-buttons.md" %} -[dashboards-and-buttons.md](getting-started/dashboards-and-buttons.md) -{% endcontent-ref %} - -{% content-ref url="getting-started/notifications.md" %} -[notifications.md](getting-started/notifications.md) -{% endcontent-ref %} - -{% content-ref url="getting-started/configuration.md" %} -[configuration.md](getting-started/configuration.md) -{% endcontent-ref %} diff --git a/14/umbraco-workflow/SUMMARY.md b/14/umbraco-workflow/SUMMARY.md deleted file mode 100644 index 4eb15f67680..00000000000 --- a/14/umbraco-workflow/SUMMARY.md +++ /dev/null @@ -1,43 +0,0 @@ -# Table of contents - -* [Umbraco Workflow Documentation](README.md) -* [Legacy Documentation](legacy-documentation.md) -* [Release notes](release-notes.md) - -## Installation - -* [Installing Umbraco Workflow](installation/installing-workflow.md) -* [Licensing](installation/licensing.md) - -## Upgrading - -* [Upgrading Umbraco Workflow](upgrading/upgrading.md) -* [Version Specific Upgrade Notes](upgrading/version-specific.md) -* [Migrate from Plumber to Workflow](upgrading/migrating-workflow.md) - -## Getting Started - -* [Dashboards and Buttons](getting-started/dashboards-and-buttons.md) -* [Submitting Content for Approval](getting-started/submitting-changes.md) -* [Content App](getting-started/workflow-content-app.md) -* [Notifications](getting-started/notifications.md) -* [Configuration](getting-started/configuration.md) -* [Approval thresholds](getting-started/approval-thresholds.md) -* [History Cleanup](getting-started/history-cleanup.md) - -## Workflow Section - -* [Workflow Section](workflow-section/workflow-section-dashboard.md) -* [Active Workflows](workflow-section/active-workflows.md) -* [Approval Groups](workflow-section/approval-groups.md) -* [Content Reviews](workflow-section/content-reviews.md) -* [Workflow History](workflow-section/workflow-history.md) -* [Workflow Settings](workflow-section/workflow-settings.md) - -## Advanced Search - -* [Advanced Search dashboard](advanced-search/advanced-search-dashboard.md) - -## Data Generator - -* [Data Generator](data-generator/data-generator.md) diff --git a/14/umbraco-workflow/advanced-search/advanced-search-dashboard.md b/14/umbraco-workflow/advanced-search/advanced-search-dashboard.md deleted file mode 100644 index 873949ce19d..00000000000 --- a/14/umbraco-workflow/advanced-search/advanced-search-dashboard.md +++ /dev/null @@ -1,41 +0,0 @@ -# Advanced Search Dashboard - -Advanced Search further expands Workflow's functionality outside its original content-approval focus, adding a new dashboard for performing deep searches of your website content. - -The Advanced Search dashboard is added in the content section for all users. - -![Workflow Advanced Search Dashboard in the Content Section](../advanced-search/images/workflow-advanced-search-v14.png) - -Advanced Search allows searching any number of content types, optionally filtered to a subset of variants. The search can be performed across all indexed fields, a subset of fields, or all fields using a particular Data Type or Property Editor. - -You can do an approximate Search using Lucene's default similarity measurement algorithm. - -![Workflow Advanced Search with selected content types](../advanced-search/images/approximate-search.png) - -## Search Types - -The search types are described below: - -* **All properties**: Searches for a single value across all indexed fields for the selected content types. -* **Some properties**: Searches the selected properties. A different search term can be provided for each selected property. -* **Single property**: Searches for a single value in the selected property. -* **Data Type**: Searches for a single value in all fields where the indexed property uses the selected Data Type (for example, all Textstring type). -* **Property Editor**: Searches for a single value in all fields where the indexed property uses the selected Property Editor (for example, all types using the Umbraco.TextBox editor). - -![Workflow Advanced Search with selected search type](../advanced-search/images/single-property-search-type.png) - -## Optional Fields - -Searches can be further refined by restricting results to particular editors, created, or updated date ranges. - -The additional fields are all optional. - -![Workflow Advanced Search optional fields](../advanced-search/images/additonal-optional-fields.png) - -## Search results - -Results are displayed in a familiar format, linking to nodes in an infinite editors, which allows users to retain their search results. - -Search results include published, unpublished and trashed content, and are filtered according to the current user's content start node(s). - -![Workflow Advanced Search search results](../advanced-search/images/search-type.png) \ No newline at end of file diff --git a/14/umbraco-workflow/advanced-search/images/additonal-optional-fields.png b/14/umbraco-workflow/advanced-search/images/additonal-optional-fields.png deleted file mode 100644 index cb270928dd5..00000000000 Binary files a/14/umbraco-workflow/advanced-search/images/additonal-optional-fields.png and /dev/null differ diff --git a/14/umbraco-workflow/advanced-search/images/approximate-search.png b/14/umbraco-workflow/advanced-search/images/approximate-search.png deleted file mode 100644 index 7f52f6227ec..00000000000 Binary files a/14/umbraco-workflow/advanced-search/images/approximate-search.png and /dev/null differ diff --git a/14/umbraco-workflow/advanced-search/images/search-type.png b/14/umbraco-workflow/advanced-search/images/search-type.png deleted file mode 100644 index d91ea28f8ce..00000000000 Binary files a/14/umbraco-workflow/advanced-search/images/search-type.png and /dev/null differ diff --git a/14/umbraco-workflow/advanced-search/images/single-property-search-type.png b/14/umbraco-workflow/advanced-search/images/single-property-search-type.png deleted file mode 100644 index da597a383de..00000000000 Binary files a/14/umbraco-workflow/advanced-search/images/single-property-search-type.png and /dev/null differ diff --git a/14/umbraco-workflow/advanced-search/images/workflow-advanced-search-v14.png b/14/umbraco-workflow/advanced-search/images/workflow-advanced-search-v14.png deleted file mode 100644 index 3aed4eb27d4..00000000000 Binary files a/14/umbraco-workflow/advanced-search/images/workflow-advanced-search-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/data-generator/data-generator.md b/14/umbraco-workflow/data-generator/data-generator.md deleted file mode 100644 index 90db9d30da3..00000000000 --- a/14/umbraco-workflow/data-generator/data-generator.md +++ /dev/null @@ -1,63 +0,0 @@ -# Data Generator - -The Umbraco Workflow DataGenerator tool is an extension package for quickly generating Umbraco users and Workflow approval groups and permissions. - -The generator gets you up and running for testing or product evaluation without having to manually create any Workflow configuration. - -## Installation - -{% hint style="info" %} -The package must only be installed into an empty Umbraco application. -{% endhint %} - -To install the Umbraco Workflow DataGenerator package (Umbraco.Workflow.DataGenerator), follow these steps: -1. Update appSettings.development.json to enable the Workflow test license. This removes limits on group creation, and enables all features: - -``` -{ - ... - "Umbraco": { - "Workflow": { - "EnableTestLicense": true - } - } -} -``` - -2. Run the following command to add the required package references to your Umbraco project: - -``` -dotnet add package Umbraco.Workflow // if not already installed -dotnet add package Umbraco.Workflow.DataGenerator -``` - -3. Restart the web application using the following command: - -``` -dotnet run -``` - -When the application restarts, it will automatically install [The Starter Kit](https://docs.umbraco.com/umbraco-cms/tutorials/starter-kit). - -## Getting started - -The package adds an additional view in the Workflow settings, which provides controls for the data generation task. - -
Data Generator dashboard
- -The available settings are explained below. - -* **Number of approval groups** - determines how many Workflow approval groups will be created. Defaults to two. -* **Number of users** - determines how many Umbraco users will be created. Defaults to two. -* **Number of groups per workflow** - determines how the created groups are allocated into the generated workflows. Defaults to 0, which allocates a random number of groups to each workflow. -* **Number of users per group** - determines how the created users are allocated into the generated workflow approval groups. Defaults to 0, which allocates a random number of users to each approval group. - -When the generator task completes, you will be prompted to take a Workflow tour. The tours can be resumed at any time from the Data generation view. - -Groups and users are created with arbitrary names, feel free to rename these to suit. - -### Reset - -Once Workflow configuration has been updated, the environment must be reset before regenerating. Resetting cancels all active workflows and deletes all workflow configuration. Umbraco users are not deleted, but will be reused in future data generation actions. - -
Data Generator dashboard - reset
diff --git a/14/umbraco-workflow/data-generator/images/data-gen-dashboard.png b/14/umbraco-workflow/data-generator/images/data-gen-dashboard.png deleted file mode 100644 index 31447236a39..00000000000 Binary files a/14/umbraco-workflow/data-generator/images/data-gen-dashboard.png and /dev/null differ diff --git a/14/umbraco-workflow/data-generator/images/data-gen-reset.png b/14/umbraco-workflow/data-generator/images/data-gen-reset.png deleted file mode 100644 index 03e4aaf02c9..00000000000 Binary files a/14/umbraco-workflow/data-generator/images/data-gen-reset.png and /dev/null differ diff --git a/14/umbraco-workflow/getting-started/approval-thresholds.md b/14/umbraco-workflow/getting-started/approval-thresholds.md deleted file mode 100644 index 7be22b3e15b..00000000000 --- a/14/umbraco-workflow/getting-started/approval-thresholds.md +++ /dev/null @@ -1,59 +0,0 @@ ---- -description: >- - Use thresholds to configure how many approvals a workflow in Umbraco Workflow - requires to be considered complete. ---- - -# Approval thresholds - -{% hint style="info" %} -This feature requires a license - learn more about [Workflow's licensing model](https://umbraco.com/products/umbraco-workflow) -{% endhint %} - -Umbraco Workflow's default behavior requires one member of an approval group to approve a pending task to advance it through the workflow. - -The approval thresholds feature introduces configuration options to set the required number of approvals for a given workflow stage. - -The threshold options are: - -| Option | Description | -| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| One (_default_) | Pending tasks require approval from **any** member of the assigned approval group. | -| Most |

Pending tasks require approval from an absolute majority of group members.
Example: A group with 3 members requires 2 approvals and a group with 4 members requires 3 approvals.

| -| All | Pending tasks require approval from **all** group members. | - -The workflow detail UI displays the following: - -* The status of the current task. -* Approval status for members of the current group. -* Progress towards meeting the threshold for the current approval stage. -* Future tasks and the assigned group and its users. - -![Tasklist with approval thresholds](images/tasklist-with-approval-thresholds-v14.png) - -Approving a task as an administrator immediately satisfies the approval threshold for the task, and will advance to the next workflow stage. - -When a task is rejected in a workflow stage where the approval threshold is Most or All, existing approvals can be managed via configuration: - -* Existing approvals can be reset, resetting progress toward the approval threshold. In this case, all users in the approval group will be able to approve the resubmitted content. -* Existing approvals can be kept. In this case, users in the approval group who have already approved the task will not be able to approve the resubmitted content. - -## Related settings and configuration - -Approval thresholds are managed via settings in the Workflow section or in the `appsettings.json` file. Node-specific thresholds are set directly on the workflow configuration in the Workflow content app. - -### Settings - -The settings below can be set from the Backoffice or via settings customization in the `appsettings.json` file (refer to [Settings customization](configuration.md#settingscustomization) for implementation instructions). - -| Setting | Default | Description | -| ---------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------ | -| Approval threshold | `0` (One) | Sets the global approval threshold. | -| Rejection resets approvals | `false` | When `true`, and the approval threshold is Most or All, rejecting a task resets the previous approvals for the workflow stage. | -| Configure approval threshold | `false` | When `true`, enables setting the approval threshold for any stage of a workflow (on a content node or Document Type). | - -### Configuration - -The approval threshold for an individual workflow stage can be set using the control below the stage name. Setting the stage threshold requires the **Configuring approval threshold** setting to be `true`. - -![Setting approval threshold for individual workflow stages](images/approval-flow-with-thresholds-v14.png) diff --git a/14/umbraco-workflow/getting-started/configuration.md b/14/umbraco-workflow/getting-started/configuration.md deleted file mode 100644 index 5d0e6316ddd..00000000000 --- a/14/umbraco-workflow/getting-started/configuration.md +++ /dev/null @@ -1,293 +0,0 @@ ---- -description: >- - Get an overview of various options for customizing the configuration of your - Umbraco Workflow installation. ---- - -# Configuration - -With Umbraco Workflow, it is possible to customize the functionality with different configuration values. - -## Editing configuration values - -All configuration for Umbraco Workflow is held in the `appSettings.json` file found at the root of your Umbraco website. If the configuration has been customized to use another source, then the same keys and values discussed in this article can be applied there. - -The convention for Umbraco configuration is to have package-based options stored as a child structure. The child structure is added below the Umbraco element and as a sibling of the CMS. Workflow configuration follows this pattern, i.e.: - -```json -{ - ... - "Umbraco": { - "CMS": { - ... - }, - "Workflow": { - ... - } - } -} -``` - -All Workflow configuration is optional and will fallback to defaults, if not set. The following structure represents the full set of configuration options along with the default values: - -```json -{ - "Workflow": { - "ReminderNotificationPeriod": Timespan.FromHours(8), - "ActionNotificationPeriod": Timespance.FromMinutes(5), - "EnableTestLicense": false, - "EmailTemplatePath": "~/Views/Partials/WorkflowEmails", - "DateFormats": { - "DateFormat": "MMMM d, yyyy h:mm tt", - "DateFormatNoMinute": "MMMM d, yyy h tt", - "DateFormatShort": "MMMM d, yyyy", - "TimeFormat": "h:mm tt", - "TimeFormatShort": "HH:mm" - }, - "SettingsCustomization": {...} - } -``` - -### Workflow Configuration - -#### ReminderNotificationPeriod - -A `string` that represents the period between checking for, and sending, reminder notifications for overdue workflows. This setting is used in conjunction with `ReminderDelay` to determine if a workflow is overdue. The default value is eight hours. The permitted value is a `TimeSpan`-parseable string, for example, `0.00.01:00` for one minute. - -#### ActionNotificationPeriod - -A `string` that represents the period between checking for and sending action notifications for active workflows. The default value is five minutes. The permitted value is a `TimeSpan`-parseable string, for example, `0.00.01:00` for one minute. - -#### EnableTestLicense - -A `bool` value used to enable or disable the test license. When true, and running Umbraco in development mode, all licensed features are available on local domains. - -#### EmailTemplatePath - -A `string` value representing the path to the email notification templates. - -#### DateFormats - -An instance of `DateTimeSettings` allowing customization of date string formats. The `DateTimeSettings` class contains properties for long and short date and time strings, plus a long date variation with no minutes. - -#### Colors - -An instance of `ColorSettings` allowing customization of colors used in email notifications. Allows setting alternate values for red, orange, and green use to highlight workflow status in emails. - -## SettingsCustomization - -All Workflow settings can be customized in the `appSettings.json` file. Settings can be read-only or hidden entirely in the BackOffice. Optionally you can set the values here. - -The `SettingsCustomization` object has two child properties: - -* `General` -* `ContentReviews` - -Both are dictionaries of `SettingsCustomizationDetail` objects. The value is set to the following structure that contains three settings: - -```json -{ - … - "MySettingKey": { - "IsHidden": false, - "IsReadOnly": false, - "Value": 42 - } - … -} -``` - -* `IsHidden` - When true, the corresponding property is not displayed in the backoffice UI -* `IsReadOnly` - When true, the corresponding property is displayed in the backoffice UI but is not editable -* `Value` - Sets the value for the corresponding property. This value takes priority over existing values set via the backoffice - -All available `SettingsCustomization` options are illustrated below along with their respective values: - -```json -{ - "Workflow": { - … - "SettingsCustomization": { - "General": { - "FlowType": 0|1|2 matching the FlowType enum values, - "ApprovalThreshold": 0|1|2 matching the ApprovalThreshold enum values, - "ConfigureApprovalThreshold": bool, - "RejectionResetsApprovals": bool, - "LockIfActive": bool, - "ScheduledContentLock": 0|1|2 matching the ScheduledLockMode enum values, - "MandatoryComments": bool, - "AllowAttachments": bool, - "AllowScheduling": bool, - "RequireUnpublish": bool, - "ExtendPermissions": bool, - "SendNotifications": bool, - "Email": string, - "ReminderDelay": int, - "EditUrl": string, - "SiteUrl": string, - "NewNodeApprovalFlow": *, - "DocumentTypeApprovalFlow": *, - "ExcludeNodes": *, - }, - "ContentReviews": { - "EnableContentReviews": bool, - "ReviewPeriod": int, - "ReminderThreshold": int, - "SendNotifications": bool, - "PublishIsReview": bool - } - } - } -} -``` - -{% hint style="info" %} -These are complex types and having values set from Configuration is not recommended. Instead, these values can be set to hidden or read-only from the backoffice to prevent further changes. -{% endhint %} - -### General - -#### FlowType (int) - -Sets the workflow type to one of Explicit (0), Implicit (1), or Exclude (2): - -| Value | Name | Description | -| ------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------- | -| 0 (_default_) | Explicit | Requires all steps be approved, including steps where the original change author is a group member. | -| 1 | Implicit | Auto-approves steps where the author is a member of the approving group. | -| 2 | Exclude | Behaves similarly to Explicit, but excludes the original author from any notifications (that is the author can not approve their own work). | - -#### ApprovalThreshold (int, requires a license) - -Sets the default approval threshold to one of One (0), Most (1), or All (2): - -| Value | Name | Description | -| ------------- | ---- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| 0 (_default_) | One | Pending tasks require approval from **any** member of the assigned approval group. | -| 1 | Most |

Pending tasks require approval from an absolute majority of group members.
Example: A group with 3 members requires 2 approvals and a group with 4 members requires 3 approvals.

| -| 2 | All | Pending tasks require approval from **all** group members. | - -#### ConfigureApprovalThreshold (bool, requires a license) - -When true, allows configuring the approval threshold on individual workflow stages. - -#### RejectionResetsApprovals (bool, requires a license) - -When true, and ApprovalThreshold is Most or All, rejecting a task resets progress towards the approval threshold for the current workflow stage. - -#### LockIfActive (bool) - -When true, prevents editing content where the node is in an active workflow. When false, content can be edited at any stage of a workflow. - -#### ScheduledContentLock (int) - -Sets the scheduled content lock to one of None (0), Workflow (1), or All (2): - -| Value | Name | Description | -| ------------- | -------- | -------------------------------------------------| -| 0 (_default_) | None | Scheduled content is not locked | -| 1 | Workflow | Content scheduled via Workflow can not be edited | -| 2 | All | All scheduled content can not be edited - -#### MandatoryComments (bool) - -When true (default), comments are required when approving a workflow task. When false, comments are optional when approving a workflow task. Comments are always required when submitting changes for approval. - -#### AllowAttachments (bool) - -When true, displays an optional media picker when initiating a workflow. The selected media item can be used to provide further context or explanation of the content changes. - -#### AllowScheduling (bool) - -When true, displays optional controls for scheduling publish/unpublish when initiating a workflow. The scheduling uses Umbraco's existing content scheduling functionality. - -#### RequireUnpublish (bool) - -When true, content must be approved via a workflow when unpublishing. When false, user with appropriate permission can unpublish content without workflow approval. - -#### ExtendPermissions (bool) - -When true, Workflow adds additional buttons to the editor footer (Request publish and Request unpublish, if the latter is required). When false, Workflow replaces the existing editor footer buttons. - -#### SendNotifications (bool) - -When true, Workflow will send email notifications in response to workflow changes. When false, no emails are sent. - -#### Email (string) - -The from address for email notifications. - -#### ReminderDelay (int) - -The number of days after which to start sending reminder emails for incomplete workflows. - -#### EditUrl (string) - -The URL at which editors access the BackOffice eg `https://edit.mysite.com`. Used for generating links to nodes in email notifications. Must be fully qualified and not include the `/umbraco` path. - -#### SiteUrl (string) - -The URL at which users access the live site eg `https://mysite.com`. Used for generating links in email notifications. Must be fully qualified. - -#### NewNodeApprovalFlow (complex type) - -When set, this flow is used for all new nodes on the first approval request. Subsequent workflows use the permissions set on the node (or content type, or inherited from an ancestor node). This is a complex type and ideally would not be set via configuration. - -#### DocumentTypeApprovalFlow (complex type, requires a license) - -Sets workflow permissions for Document Types (that is: all items of `BlogItem` type use the same workflow). The Document Type flow is used when a content node has no explicit permissions set. This is a complex type and ideally should not be set via configuration. - -#### ExcludeNodes (complex type, requires a license) - -Allows excluding segments of the content tree from the workflow model. This is a complex type and ideally would not be set via configuration. - -### ContentReviews - -#### EnableContentReviews (bool) - -When true, the content review engine will monitor publication dates to determine content review requirements. - -#### ReviewPeriod (int) - -Sets the number of days between mandatory reviews. This is a global value that can be overridden at the node or content type level. - -#### ReminderThreshold (int) - -Sets the date on which to send notification emails, prior to the review date elapsing. For example, if the `ReviewPeriod` is 20 and the `ReminderThreshold` is 3, notifications will be sent in 17 days or 3 days before the review date. - -#### SendNotifications (bool) - -When true, Workflow will send email notifications to approval groups, with a digest of expiring and expired content. - -#### PublishIsReview (bool) - -When true, publishing a node is treated as a review, and will generate a new review date. When false, content must be explicitly reviewed via the review banner rendered at the top of the editor. - -For example: To set the site URL, hide it in the backoffice, and set the content review period but keep the property read-only. The configuration would look like this: - -```json -{ - "Workflow": { - "SettingsCustomization": { - "General": { - "SiteUrl": { - "IsHidden": true, - "Value": "https://www.myawesomesite.com" - } - }, - "ContentReviews": { - "ReviewPeriod": { - "IsReadOnly": true, - "Value": 42 - } - } - } - } -} -``` - -Your Integrated Development Environment (IDE) will provide intellisense for the available settings but does not provide the valid value types. Settings are validated on startup and Umbraco will throw an exception if a known setting is provided with an invalid value. - -{% hint style="info" %} -It is possible to include settings outside of those referenced by Workflow. These can be useful for providing values for use in extensions and customizations. These settings are not validated on startup so can have any value. -{% endhint %} diff --git a/14/umbraco-workflow/getting-started/dashboards-and-buttons.md b/14/umbraco-workflow/getting-started/dashboards-and-buttons.md deleted file mode 100644 index 5f76ecececa..00000000000 --- a/14/umbraco-workflow/getting-started/dashboards-and-buttons.md +++ /dev/null @@ -1,32 +0,0 @@ -# Dashboards and Buttons - -Umbraco Workflow has its default Dashboards. By default, when you install Umbraco Workflow, you receive two Dashboards: the _User Dashboard_ and the _Admin Dashboard_. Additionally, Umbraco Workflow replaces the default Umbraco button set in the editor drawer. - -## Dashboards - -Umbraco Workflow adds two Dashboards to your Umbraco project: - -* **User Dashboard** - This Workflow Dashboard is added in the **Content** section. It displays the tasks requiring approval from the user, current user’s submissions, and stale content (content that needs to be reviewed). - - ![Workflow Dashboard in the Content Section](../images/WorkflowDashboard-ContentSection-v14.png) -* **Admin Dashboard** - This Workflow Dashboard is the default view in the **Workflow** section. It displays a chart of recent workflow activity, chart of content review activity, licensing details, and any relevant upgrade-related messages. You can also view the workflow and content review activity chart for the specified range of days. - - ![Workflow Dashboard in the Workflow Section](../images/Workflow-Admin-Dashboard-v14.png) - -## Buttons - -When a workflow is active on the current node, the **Publish** button is replaced, linking to the workflow content app. - -![Buttons](../images/Buttons.png) - -When no workflow is active, the button state is determined by the current user's permissions. - -Umbraco Workflow overrides Umbraco's User/Group publishing permissions. If the user has permission to update the node, they will be able to initiate a workflow process on that node. Umbraco Workflow shifts Umbraco from a centrally administered publishing model (controlled by a site administrator) to a distributed model. In this model, editors publish content based on their responsibilities assigned during the workflows. - -In cases, where the content is already in a workflow, a notification is displayed at the top of the editor. Depending on the Workflow **Settings**, you can enable/disable editing access on a content node in a workflow. - -![Disabled content edits](../images/blocked_content.png) - -For nodes where the workflow has been disabled, the default Umbraco options are displayed. - -![Default Button](../images/Default_Buttons.png) diff --git a/14/umbraco-workflow/getting-started/history-cleanup.md b/14/umbraco-workflow/getting-started/history-cleanup.md deleted file mode 100644 index 401a0094fbc..00000000000 --- a/14/umbraco-workflow/getting-started/history-cleanup.md +++ /dev/null @@ -1,141 +0,0 @@ -# History Cleanup - -Every new workflow stores multiple records in the database - one for the workflow instance and one for each task in the workflow. In a multi-lingual site, depending on how you use Workflow, there may also be records generated for each culture variation. These records are used to build the workflow history views in the Umbraco backoffice. - -Depending on your requirements, this information may not be required or may only be useful for a short period of time. - -{% hint style="info" %} -The workflow History exists in addition to Umbraco's audit trail information. It will always show the identity of the user who completes the workflow. -{% endhint %} - -Umbraco Workflow 11.1.0 introduces a history cleanup feature similar to those already available in Umbraco CMS and Umbraco Forms. - -## How it works - -The History Cleanup feature is disabled by default. Applying the default history cleanup policy will: - -* Delete history older than 28 days. See the `KeepHistoryForDays` setting. -* Only delete history where the workflow status is `Approved`, `Cancelled`, `CancelledByThirdParty`, or `Errored`. See the `StatusesToDelete` setting. - -The feature can be enabled in the `appSettings.json`: - -```json -{ - "Umbraco": { - "Workflow": { - "HistoryCleanupPolicy": { - "EnableCleanup": true, - // Below settings are optional - "FirstRunTime": string; the time to first run the scheduled cleanup task, in crontab format - "Period": string; how often to run the task, in timespan format - "KeepHistoryForDays": int; delete history after this many days - "StatusesToDelete": refer to StatusesToDelete configuration below - "CleanupRules": refer to Configuration examples below - } - } - } -} -``` - -## Overriding global settings - -For sites with stricter or more complex requirements, it is possible to override the global settings for individual content nodes and Document Types. This is also managed through `appSettings.json` configuration. Configuration rules defined in application settings are prioritized over any rules set via the backoffice. It allows the developers to restrict clean up of critical history, while allowing site administrators flexibility to manage non-critical history. - -## Configuration examples - -The below example will apply the following policies: - -* History cleanup is enabled globally. -* History items with `Approved` or `Cancelled` status are deleted after 90 days. -* Workflow history for node `dcf18a51-6919-4cf8-89d1-36b94ce4d963` will never be deleted. -* Workflow history for node `31523089-f648-4883-9087-ef9a0b83129f` will be deleted after 10 days for the statuses defined in the global `StatusesToDelete` property. -* Workflow history for all nodes using the `ContentPage` Document Type will never be deleted. -* Workflow history with `Cancelled` status for all nodes using the `NewsItem` Document Type will be deleted after 100 days (see also [StatusesToDelete configuration](history-cleanup.md#statusestodelete-configuration)). - -```json -{ - "Umbraco": { - "Workflow": { - "HistoryCleanupPolicy": { - "EnableCleanup": true, - "KeepHistoryForDays": 90, - "StatusesToDelete": { - "Approved": true, - "Cancelled": true, - "CancelledByThirdParty": false, - "Errored": false - } - "CleanupRules": { - "dcf18a51-6919-4cf8-89d1-36b94ce4d963": { - "EnableCleanup": false - }, - "31523089-f648-4883-9087-ef9a0b83129f": { - "KeepHistoryForDays": 10 - }, - "ContentPage": { - "EnableCleanup": false - }, - "NewsItem": { - "KeepHistoryForDays": 100, - "StatusesToDelete": { - "Approved": false, - "Cancelled": true, - "CancelledByThirdParty": false, - "Errored": false - } - } - } - } - } - } -} -``` - -When calculating node and Document Type policies, the Document Type rules will not be processed if the current workflow instance matches a node rule. Using the above configuration as an example, consider both nodes in the `CleanupRules` dictionary are using the Document Type `ContentPage`. In this case, the Document Type rules will not be applied as the node rules are prioritized. - -If a value is omitted from the node or Document Type policy, the global value will be used instead. In the above example, the node policy for `31523089-f648-4883-9087-ef9a0b83129f` uses the `StatusesToDelete` value from the global policy that is deleting `Approved` or `Cancelled` workflow history. - -### StatusesToDelete configuration - -`StatusesToDelete` uses a dictionary built from the `WorkflowStatus` enum type. The default configuration is: - -```json - "HistoryCleanupPolicy": { - "StatusesToDelete": { - "Approved": true, - "Cancelled": true, - "CancelledByThirdParty": true, - "Errored": true, - "PendingApproval": false, - "Rejected": false, - "NotRequired": false, - "Resubmitted": false - } - } -``` - -It is possible for a cleanup rule (or the global configuration) to declare a `StatusesToDelete` property without the full set of status keys. This will not modify the default values. - -For example, adding `"Approved": false` will remove `Approved` from the deletable statuses, but all other default values will remain. Therefore, to delete approved workflows only, the configuration would look like below, where the default values have been negated: - -```json - "HistoryCleanupPolicy": { - "EnableCleanup": true, - "StatusesToDelete": { - "Approved": true, - "Cancelled": false, - "CancelledByThirdParty": false, - "Errored": false - } - } -``` - -## Backoffice configuration - -Backoffice users with access to the Workflow section will have permission to modify history cleanup rules, while all backoffice users have read-only access. - -Rules for content items and their Document Type are set from the History tab of the Workflow content app. The History view in the Workflow section provides a read-only overview of all the history cleanup rules and global configuration. - -Content items with no custom cleanup rules defined will display the global defaults. - -![Workflow History Cleanup Modal](images/workflow-history-cleanup-v14.png) diff --git a/14/umbraco-workflow/getting-started/images/Active-Workflow-detailed-info-v14.png b/14/umbraco-workflow/getting-started/images/Active-Workflow-detailed-info-v14.png deleted file mode 100644 index 7abde933dfd..00000000000 Binary files a/14/umbraco-workflow/getting-started/images/Active-Workflow-detailed-info-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/getting-started/images/Active-workflow-initiate-request.png b/14/umbraco-workflow/getting-started/images/Active-workflow-initiate-request.png deleted file mode 100644 index 0478888a065..00000000000 Binary files a/14/umbraco-workflow/getting-started/images/Active-workflow-initiate-request.png and /dev/null differ diff --git a/14/umbraco-workflow/getting-started/images/Buttons.png b/14/umbraco-workflow/getting-started/images/Buttons.png deleted file mode 100644 index 3cc8d7e7ad1..00000000000 Binary files a/14/umbraco-workflow/getting-started/images/Buttons.png and /dev/null differ diff --git a/14/umbraco-workflow/getting-started/images/Configuration-sub-section-v14.png b/14/umbraco-workflow/getting-started/images/Configuration-sub-section-v14.png deleted file mode 100644 index b930d80dfa5..00000000000 Binary files a/14/umbraco-workflow/getting-started/images/Configuration-sub-section-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/getting-started/images/Content-reviews-v14.png b/14/umbraco-workflow/getting-started/images/Content-reviews-v14.png deleted file mode 100644 index 7a3c7878f53..00000000000 Binary files a/14/umbraco-workflow/getting-started/images/Content-reviews-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/getting-started/images/Default-Buttons.png b/14/umbraco-workflow/getting-started/images/Default-Buttons.png deleted file mode 100644 index 45cace64303..00000000000 Binary files a/14/umbraco-workflow/getting-started/images/Default-Buttons.png and /dev/null differ diff --git a/14/umbraco-workflow/getting-started/images/History-sub-section-v14.png b/14/umbraco-workflow/getting-started/images/History-sub-section-v14.png deleted file mode 100644 index 7c4d0c402d7..00000000000 Binary files a/14/umbraco-workflow/getting-started/images/History-sub-section-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/getting-started/images/Workflow-Content-app-Details-overlay-v14.png b/14/umbraco-workflow/getting-started/images/Workflow-Content-app-Details-overlay-v14.png deleted file mode 100644 index cfe50524e20..00000000000 Binary files a/14/umbraco-workflow/getting-started/images/Workflow-Content-app-Details-overlay-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/getting-started/images/Workflow-section.png b/14/umbraco-workflow/getting-started/images/Workflow-section.png deleted file mode 100644 index 9bc148d2e37..00000000000 Binary files a/14/umbraco-workflow/getting-started/images/Workflow-section.png and /dev/null differ diff --git a/14/umbraco-workflow/getting-started/images/WorkflowDashboard-ContentSection.png b/14/umbraco-workflow/getting-started/images/WorkflowDashboard-ContentSection.png deleted file mode 100644 index b1a885dc671..00000000000 Binary files a/14/umbraco-workflow/getting-started/images/WorkflowDashboard-ContentSection.png and /dev/null differ diff --git a/14/umbraco-workflow/getting-started/images/approval-flow-types.png b/14/umbraco-workflow/getting-started/images/approval-flow-types.png deleted file mode 100644 index c58ac608eb9..00000000000 Binary files a/14/umbraco-workflow/getting-started/images/approval-flow-types.png and /dev/null differ diff --git a/14/umbraco-workflow/getting-started/images/approval-flow-with-thresholds-v14.png b/14/umbraco-workflow/getting-started/images/approval-flow-with-thresholds-v14.png deleted file mode 100644 index 60f82da35b7..00000000000 Binary files a/14/umbraco-workflow/getting-started/images/approval-flow-with-thresholds-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/getting-started/images/approval-groups-roles-v14.png b/14/umbraco-workflow/getting-started/images/approval-groups-roles-v14.png deleted file mode 100644 index 911c1dba850..00000000000 Binary files a/14/umbraco-workflow/getting-started/images/approval-groups-roles-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/getting-started/images/approval-request-overlay-detailed-v14.png b/14/umbraco-workflow/getting-started/images/approval-request-overlay-detailed-v14.png deleted file mode 100644 index 46cf7efc278..00000000000 Binary files a/14/umbraco-workflow/getting-started/images/approval-request-overlay-detailed-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/getting-started/images/approval-request-overlay-variants-v14.png b/14/umbraco-workflow/getting-started/images/approval-request-overlay-variants-v14.png deleted file mode 100644 index c9a7782081d..00000000000 Binary files a/14/umbraco-workflow/getting-started/images/approval-request-overlay-variants-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/getting-started/images/assign-rejected-task.png b/14/umbraco-workflow/getting-started/images/assign-rejected-task.png deleted file mode 100644 index 365b4969a4b..00000000000 Binary files a/14/umbraco-workflow/getting-started/images/assign-rejected-task.png and /dev/null differ diff --git a/14/umbraco-workflow/getting-started/images/blocked-content.png b/14/umbraco-workflow/getting-started/images/blocked-content.png deleted file mode 100644 index 0f23d2b8114..00000000000 Binary files a/14/umbraco-workflow/getting-started/images/blocked-content.png and /dev/null differ diff --git a/14/umbraco-workflow/getting-started/images/content-approval-flow-v14.png b/14/umbraco-workflow/getting-started/images/content-approval-flow-v14.png deleted file mode 100644 index 43369a7cda3..00000000000 Binary files a/14/umbraco-workflow/getting-started/images/content-approval-flow-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/getting-started/images/tasklist-with-approval-thresholds-v14.png b/14/umbraco-workflow/getting-started/images/tasklist-with-approval-thresholds-v14.png deleted file mode 100644 index 7ec1fe7f805..00000000000 Binary files a/14/umbraco-workflow/getting-started/images/tasklist-with-approval-thresholds-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/getting-started/images/workflow-history-cleanup-v14.png b/14/umbraco-workflow/getting-started/images/workflow-history-cleanup-v14.png deleted file mode 100644 index f9f45c16f01..00000000000 Binary files a/14/umbraco-workflow/getting-started/images/workflow-history-cleanup-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/getting-started/notifications.md b/14/umbraco-workflow/getting-started/notifications.md deleted file mode 100644 index 2f5c60bf953..00000000000 --- a/14/umbraco-workflow/getting-started/notifications.md +++ /dev/null @@ -1,86 +0,0 @@ -# Notifications - -Umbraco Workflow uses Notifications to allow you to hook into the processes for the backoffice. For example, you might want to execute some code every time an approval group is updated. Notifications allow you to do that. For more information on how Umbraco implements Notifications, see the [Using Notifications](https://docs.umbraco.com/umbraco-cms/reference/notifications) article. - -## Notifications - -All notifications reside in the `Umbraco.Workflow.Core.Notifications` namespace and are postfixed with `Notification`. - -Typically, available notifications exist in pairs, with a "before" and "after" notification. For example, the `SettingsService` class publishes both a `WorkflowSettingsSavingNotification` and a `WorkflowSettingsSavedNotification` when settings are modified. - -Which one you want to use depends on what you want to achieve. If you want to cancel the action, you will use the "before" notification and use the CancelOperation method on the notification to cancel it. If you want to execute some code after the settings have been updated, then you would use the "after" notification. - -## ContentReviewService Notifications - -| Notification | Members | Description | -| ----------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| WorkflowContentReviewsConfigSavingNotification |
  • IEnumerable SavedEntities
  • EventMessages Messages
  • IDictionary<string,object> State
  • bool Cancel
|

Published when ContentReviewService.SaveContentReviewConfig is called in the API.
SavedEntities: Gets the collection of IWorkflowConfig objects being saved.

| -| WorkflowContentReviewsConfigSavedNotification |
  • IEnumerable SavedEntities
  • EventMessages Messages
  • IDictionary<string,object> State
|

Published when ContentReviewService.SaveContentReviewConfig is called in the API after the entities have been saved.
SavedEntities: Gets the collection of saved IWorkflowConfig objects.

| -| WorkflowContentReviewsEmailNotificationsSendingNotification |
  • Dictionary<UserGroupPoco, List<ContentReviewConfigPoco>> Target
  • EventMessages Messages
  • IDictionary<string,object> State
  • bool Cancel
|

Published when ContentReviewReminderEmailer.SendReviewReminders is called in the API before email notifications are sent.
Target: Gets a dictionary containing information about the nodes requiring review, and the assigned review groups.

| -| WorkflowContentReviewsEmailNotificationsSentNotification |
  • Dictionary<UserGroupPoco, List<ContentReviewConfigPoco>> Target
  • EventMessages Messages
  • IDictionary<string,object> State
|

Published when ContentReviewReminderEmailer.SendReviewReminders is called in the API after email notifications are sent.
Target: Gets a dictionary containing information about the nodes requiring review, and the assigned review groups.

| -| WorkflowContentReviewsReviewingNotification |
  • ContentReviewNodePoco Target
  • EventMessages Messages
  • IDictionary<string,object> State
  • bool Cancel
|

Published when ContentReviewService.MarkAsReviewed is called in the API before the node review status is updated.
Target: Get an object with information about the node being reviewed.

| -| WorkflowContentReviewsReviewedNotification |
  • ContentReviewNodePoco Target
  • EventMessages Messages
  • IDictionary<string,object> State
|

Published when ContentReviewService.MarkAsReviewed is called in the API after the node review status is updated.
Target: Get an object with information about the reviewed node.

| - -## ConfigService Notifications - -| Notification | Members | Description | -| --------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| WorkflowContentTypeConfigDeletingNotification |
  • IEnumerable<IWorkflowConfig> DeletedEntities
  • EventMessages Messages
  • IDictionary<string,object> State
  • bool Cancel
|

Published when ConfigService.DeleteContentTypeConfig is called in the API before the config items are deleted.
DeletedEntities: Gets the collection of IWorkflowConfig objects being deleted.

| -| WorkflowContentTypeConfigDeletedNotification |
  • IEnumerable<IWorkflowConfig> DeletedEntities
  • EventMessages Messages
  • IDictionary<string,object> State
|

Published when ConfigService.DeleteContentTypeConfig is called in the API after the config items are deleted.
DeletedEntities: Gets the collection of deleted IWorkflowConfig objects. Note these items are no longer in the database and exist only in memory.

| -| WorkflowContentTypeConfigSavingNotification |
  • IEnumerable<IWorkflowConfig> SavedEntities
  • EventMessages Messages
  • IDictionary<string,object> State
  • bool Cancel
|

Published when ConfigService.UpdateContentTypeConfig is called in the API.
SavedEntities: Gets the collection of IWorkflowConfig objects being saved.

| -| WorkflowContentTypeConfigSavedNotification |
  • IEnumerable<IWorkflowConfig> SavedEntities
  • EventMessages Messages
  • IDictionary<string,object> State
|

Published when ConfigService.UpdateContentTypeConfig is called in the API after the entities have been saved.
SavedEntities: Gets the collection of saved IWorkflowConfig objects.

| -| WorkflowNodeConfigDeletingNotification |
  • IEnumerable<IWorkflowConfig> DeletedEntities
  • EventMessages Messages
  • IDictionary<string,object> State
  • bool Cancel
|

Published when ConfigService.DeleteNodeConfig is called in the API before the config items are deleted.
DeletedEntities: Gets the collection of IWorkflowConfig objects being deleted.

| -| WorkflowNodeConfigDeletedNotification |
  • IEnumerable<IWorkflowConfig> DeletedEntities
  • EventMessages Messages
  • IDictionary<string,object> State
|

Published when ConfigService.DeleteNodeConfig is called in the API after the config items are deleted.
DeletedEntities: Gets the collection of deleted IWorkflowConfig objects. Note these items are no longer in the database and exist only in memory.

| -| WorkflowNodeConfigSavingNotification |
  • IEnumerable<IWorkflowConfig> SavedEntities
  • EventMessages Messages
  • IDictionary<string,object> State
  • bool Cancel
|

Published when ConfigService.UpdateNodeConfig is called in the API.
SavedEntities: Gets the collection of IWorkflowConfig objects being saved.

| -| WorkflowNodeConfigSavedNotification |
  • IEnumerable<IWorkflowConfig> SavedEntities
  • EventMessages Messages
  • IDictionary<string,object> State
|

Published when ConfigService.UpdateNodeConfig is called in the API after the entities have been saved.
SavedEntities: Gets the collection of saved IWorkflowConfig objects.

| - -## NotificationsService Notifications - -| Notification | Members | Description | -| --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| WorkflowEmailNotificationsSendingNotification |
  • IEnumerable<IWorkflowInstance> Target
  • EmailType EmailType
  • EventMessages Messages
  • IDictionary<string,object> State
  • bool Cancel
|

Published when NotificationsService.SendEmailNotifications is called in the API before email notifications are generated and sent.
Target: Gets the object describing the workflow instance used to build the email messages
EmailType: Gets the enum value describing the email type

| -| WorkflowEmailNotificationsSentNotification |
  • IHtmlEmailModel Target
  • List<EmailUserModel> Recipients
  • EmailType EmailType
  • EventMessages Messages
  • IDictionary<string,object> State
|

Published when WorkflowReminderEmailer.Send is called in the API after email notifications are sent.
Target: Gets the object describing the email
Recipients: Gets the collection of email recipients
EmailType: Gets the enum value describing the email type

| -| WorkflowEmailRemindersSendingNotification |
  • IEnumerable<IWorkflowInstance> Target
  • EmailType EmailType
  • EventMessages Messages
  • IDictionary<string,object> State
  • bool Cancel
|

Published when NotificationsService.SendEmailReminders is called in the API before email notifications are generated and sent.
Target: Gets the collection of objects describing the workflow instances used to build the email messages
EmailType: Gets the enum value describing the email type. Will always be `EmailType.Reminder`

| -| WorkflowEmailRemindersSentNotification |
  • IEnumerable<IWorkflowInstance> Target
  • List&EmailTaskListModel> Tasks
  • EmailType EmailType
  • EventMessages Messages
  • IDictionary<string,object> State
|

Published when WorkflowReminderEmailer.Send is called in the API after email notifications are sent.
Target: Gets the collection of objects describing the workflow instances used to build the email messages
Tasks: Gets the collection of objects describing the overdue workflows for each notified user
EmailType: Gets the enum value describing the email type. Will always be `EmailType.Reminder`

| - -## GroupService Notifications - -| Notification | Members | Description | -| --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| WorkflowGroupCreatingNotification |
  • IWorkflowGroup SavedEntities
  • EventMessages Messages
  • IDictionary<string,object> State
  • bool Cancel
|

Published when GroupService.CreateUserGroupAsync is called in the API before the entity is created.
CreatedEntity: Gets the created IWorkflowGroup object.

| -| WorkflowGroupCreatedNotification |
  • IWorkflowGroup SavedEntities
  • EventMessages Messages
  • IDictionary<string,object> State
|

Published when GroupService.CreateUserGroupAsync is called in the API after the entity has been created.
CreatedEntity: Gets the created IWorkflowGroup object.

| -| WorkflowGroupDeletingNotification |
  • IEnumerable<IWorkflowGroup> DeletedEntities
  • EventMessages Messages
  • IDictionary<string,object> State
  • bool Cancel
|

Published when GroupService.DeleteUserGroupAsync is called in the API before the group is deleted.
DeletedEntities: Gets the collection of IWorkflowGroup objects being deleted.

| -| WorkflowGroupDeletedNotification |
  • IEnumerable<IWorkflowGroup> DeletedEntities
  • EventMessages Messages
  • IDictionary<string,object> State
|

Published when GroupService.DeleteUserGroupAsync is called in the API after the group is deleted.
DeletedEntities: Gets the collection of deleted IWorkflowGroup objects.

| -| WorkflowGroupSavingNotification |
  • IEnumerable<IWorkflowGroup> SavedEntities
  • EventMessages Messages
  • IDictionary<string,object> State
  • bool Cancel
|

Published when GroupService.UpdateUserGroupAsync is called in the API before the group is updated.
SavedEntities: Gets the collection of IWorkflowGroup objects being saved.

| -| WorkflowGroupSavedNotification |
  • IEnumerable<IWorkflowGroup> SavedEntities
  • EventMessages Messages
  • IDictionary<string,object> State
|

Published when GroupService.UpdateUserGroupAsync is called in the API after the group is updated.
SavedEntities: Gets the collection of saved IWorkflowGroup objects.

| - -## WorkflowProcess Notifications - -| Notification | Members | Description | -| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| WorkflowInstanceApprovingNotification |
  • IWorkflowInstance Target
  • WorkflowAction Action
  • EventMessages Messages
  • IDictionary<string,object> State
  • bool Cancel
|

Published when WorkflowProcess.ActionWorkflow is called in the API before the workflow stage is approved.
Target: Gets the IWorkflowInstance object being approved.
Action: Gets the WorkflowAction being executed. Will be WorkflowAction.Approve.

| -| WorkflowInstanceApprovedNotification |
  • IWorkflowInstance Target
  • WorkflowAction Action
  • EventMessages Messages
  • IDictionary<string,object> State
|

Published when WorkflowProcess.ActionWorkflow is called in the API after the workflow stage is approved.
Target: Gets the approved IWorkflowInstance object.
Action: Gets the WorkflowAction being executed. Will be WorkflowAction.Approve.

| -| WorkflowInstanceCancellingNotification |
  • IWorkflowInstance Target
  • WorkflowAction Action
  • EventMessages Messages
  • IDictionary<string,object> State
  • bool Cancel
|

Published when WorkflowProcess.ActionWorkflow is called in the API before the workflow stage is cancelled.
Target: Gets the IWorkflowInstance object being cancelled.
Action: Gets the WorkflowAction being executed. Will be WorkflowAction.Cancel.

| -| WorkflowInstanceCancelledNotification |
  • IWorkflowInstance Target
  • WorkflowAction Action
  • EventMessages Messages
  • IDictionary<string,object> State
|

Published when WorkflowProcess.ActionWorkflow is called in the API after the workflow stage is cancelled.
Target: Gets the cancelled IWorkflowInstance object.
Action: Gets the WorkflowAction being executed. Will be WorkflowAction.Cancel.

| -| WorkflowInstanceCompletedNotification |
  • IWorkflowInstance Target
  • WorkflowType WorkflowType
  • EventMessages Messages
  • IDictionary<string,object> State
|

Published when WorkflowProcess.HandleCompleteNow or WorkflowProcess.HandleCompleteLater is called in the API after the workflow is completed.
Target: Gets the completed IWorkflowInstance object.
WorkflowType: Gets the WorkflowType enum value representing the workflow type. Will be either Publish or Unpublish.

| -| WorkflowInstanceCreatingNotification |
  • IWorkflowInstance CreatedEntity
  • EventMessages Messages
  • IDictionary<string,object> State
  • bool Cancel
|

Published when WorkflowProcess.InitiateWorkflow is called in the API before the workflow is initiated.
CreatedEntity: Gets the IWorkflowInstance object being created.

| -| WorkflowInstanceCreatedNotification |
  • IWorkflowInstance CreatedEntity
  • EventMessages Messages
  • IDictionary<string,object> State
|

Published when WorkflowProcess.InitiateWorkflow is called in the API after the workflow is initiated.
CreatedEntity: Gets the created IWorkflowInstance object.

| -| WorkflowInstanceRejectingNotification |
  • IWorkflowInstance Target
  • WorkflowAction Action
  • EventMessages Messages
  • IDictionary<string,object> State
  • bool Cancel
|

Published when WorkflowProcess.ActionWorkflow is called in the API before the workflow stage is rejected.
Target: Gets the IWorkflowInstance object being rejected.
Action: Gets the WorkflowAction being executed. Will be WorkflowAction.Reject.

| -| WorkflowInstanceRejectedNotification |
  • IWorkflowInstance Target
  • WorkflowAction Action
  • EventMessages Messages
  • IDictionary<string,object> State
|

Published when WorkflowProcess.ActionWorkflow is called in the API after the workflow stage is rejected.
Target: Gets the rejected IWorkflowInstance object.
Action: Gets the WorkflowAction being executed. Will be WorkflowAction.Reject.

| -| WorkflowInstanceResubmittingNotification |
  • IWorkflowInstance Target
  • WorkflowAction Action
  • EventMessages Messages
  • IDictionary<string,object> State
  • bool Cancel
|

Published when WorkflowProcess.ResubmitWorkflow is called in the API before the workflow stage is resubmitted.
Target: Gets the IWorkflowInstance object being resubmitted.
Action: Gets the WorkflowAction being executed. Will be WorkflowAction.Resubmit.

| -| WorkflowInstanceResubmittedNotification |
  • IWorkflowInstance Target
  • WorkflowAction Action
  • EventMessages Messages
  • IDictionary<string,object> State
|

Published when WorkflowProcess.ResubmitWorkflow is called in the API after the workflow stage is resubmitted.
Target: Gets the resubmitted IWorkflowInstance object.
Action: Gets the WorkflowAction being executed. Will be WorkflowAction.Resubmit.

| -| WorkflowInstanceUpdatingNotification |
  • IWorkflowInstance Target
  • WorkflowAction Action
  • EventMessages Messages
  • IDictionary<string,object> State
  • bool Cancel
|

Base notification class for Approving, Cancelling, Creating, Rejecting, Resubmitting. Can be used in place of these, using the Action value to identify the executed workflow action.
Published when WorkflowProcess.ResubmitWorkflow is called in the API before the workflow is updated.
Target: Gets the IWorkflowInstance object being updated.
Action: Gets the WorkflowAction being executed.

| -| WorkflowInstanceUpdatedNotification |
  • IWorkflowInstance Target
  • WorkflowAction Action
  • EventMessages Messages
  • IDictionary<string,object> State
|

Base notification class for Approved, Cancelled, Created, Rejected, Resubmitted. Can be used in place of these, using the Action value to identify the executed workflow action.
Published when WorkflowProcess.ResubmitWorkflow is called in the API after the workflow stage is updated.
Target: Gets the updated IWorkflowInstance objects.
Action: Gets the WorkflowAction being executed.

| -| WorkflowResubmitTaskCreatingNotification |
  • IWorkflowInstance CreatedEntity
  • EventMessages Messages
  • IDictionary<string,object> State
  • bool Cancel
|

Published when WorkflowProcess.ResubmitWorkflow is called in the API before the workflow task is persisted.
CreatedEntity: Gets the IWorkflowTask object being created.

| -| WorkflowResubmitTaskCreatedNotification |
  • IWorkflowInstance CreatedEntity
  • EventMessages Messages
  • IDictionary<string,object> State
|

Published when WorkflowProcess.ResubmitWorkflow is called in the API after the workflow task is persisted.
CreatedEntity: Gets the created IWorkflowTask.

| -| WorkflowTaskCreatingNotification |
  • IWorkflowInstance CreatedEntity
  • EventMessages Messages
  • IDictionary<string,object> State
  • bool Cancel
|

Published when WorkflowTaskManager.CreateApprovalTask is called in the API before the workflow task is persisted.
CreatedEntity: Gets the IWorkflowTask object being created.

| -| WorkflowTaskCreatedNotification |
  • IWorkflowInstance CreatedEntity
  • EventMessages Messages
  • IDictionary<string,object> State
|

Published when WorkflowTaskManager.CreateApprovalTask is called in the API after the workflow task is persisted.
CreatedEntity: Gets the created IWorkflowTask.

| -| WorkflowTaskUpdatingNotification |
  • IWorkflowInstance Target
  • EventMessages Messages
  • IDictionary<string,object> State
  • bool Cancel
|

Published when WorkflowTaskManager.ResubmitWorkflow is called in the API before the workflow task is updated.
CreatedEntity: Gets the IWorkflowTask object being updated.

| -| WorkflowTaskUpdatedNotification |
  • IWorkflowInstance Target
  • EventMessages Messages
  • IDictionary<string,object> State
|

Published when WorkflowTaskManager.ResubmitWorkflow is called in the API after the workflow task is updated.
CreatedEntity: Gets the updated IWorkflowTask.

| - -## SettingsService Notifications - -| Notification | Members | Description | -| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| WorkflowSettingsSavingNotification |
  • IEnumerable<ISettings> SavedEntities
  • EventMessages Messages
  • IDictionary<string,object> State
  • bool Cancel
|

Published when SettingsService.UpdateSettings is called in the API before the settings are saved.
SavedEntities: Gets the collection of ISettings objects being saved.

| -| WorkflowSettingsSavedNotification |
  • IEnumerable<ISettings> SavedEntities
  • EventMessages Messages
  • IDictionary<string,object> State
|

Published when SettingsService.UpdateSettings SavedEntities: Gets the collection of saved ISettings objects.

| diff --git a/14/umbraco-workflow/getting-started/submitting-changes.md b/14/umbraco-workflow/getting-started/submitting-changes.md deleted file mode 100644 index fd420a87e82..00000000000 --- a/14/umbraco-workflow/getting-started/submitting-changes.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -description: >- - Learn how to submit content changes for Workflow approval ---- - -# Submitting Content for Approval - -When requesting workflow approval for content changes, editors must provide additional information detailing the change. - -To submit the content changes, click the **Request publish** button in the editor footer. - -![Buttons](../images/Buttons.png) - -The button opens the request approval overlay: - -![Request approval overlay](images/approval-request-overlay-detailed-v14.png) - -Depending on the Document Type and Workflow settings, the overlay will provide inputs for: - -| Fields | Description | Visibility Conditions | -|---|---|---| -| **Describe the changes** | A field for adding comments to describe the changes made to the content. | Always visible. | -| **Action** | Allows to choose the workflow type - either Publish or Unpublish. | Visible only when **Use Workflow for unpublish** is set to true. To enable this setting, go to **Workflow** > **Settings** > **Use Workflow for unpublish**. | -| **Attachment** | Upload media or files attachment. | Visible only when **Allow attachments** is set to true. | -| **Publish on** | A date picker for scheduling the content's publishing date. | Editable only when **Allow scheduling** is set to true and the workflow type is **Publish**. It is not possible to schedule a **Publish on** date in an Unpublish workflow. | -| **Unpublish on** | A date picker for scheduling the content's unpublishing date. | Visible only when **Allow scheduling** is set to true. | -| **Variants** | Allows selection of language variants to publish. | Visible only for variant content. | - -It is possible to schedule both **Publish on** and **Unpublish on** dates in a Publish workflow. Once content has been unpublished, a new workflow process is required to republish the content. - -## Variant Workflows - -If the document varies by culture, the editor must select one or more variants to submit for approval. - -When a document is invariant, the variants selector is not displayed, and the approval flow follows the [default permissions inheritance pattern](workflow-content-app.md#approval-flow-types). - -![Request approval overlay](images/approval-request-overlay-variants-v14.png) - -The editor will not be able to select variants where: - -* They do not have permission to edit the language, or -* The variant is already in a workflow. - -When submitting multiple variants, a workflow process is started for each variant, using the [default permissions inheritance pattern](workflow-content-app.md#approval-flow-types). Newly created variants are automatically assigned the configuration from the default language. - -Alternatively, all variants can be submitted in an invariant workflow, where they will be approved in a single workflow process. Invariant workflows use the permissions set on the default language. Editors must have permission to edit all the current node's variants to be able to initiate an invariant workflow. - -The invariant workflow will publish all variants, regardless of their node state, that are not already in workflows. This means that previously unpublished variants will be republished when using invariant workflows. In most cases, it is preferable to select the individual variants. - -## Content Validation and Pending Changes - -When submitting for approval, Workflow will automatically save variants with pending changes. - -Validation errors are reported in the UI using Umbraco's validation messages. diff --git a/14/umbraco-workflow/getting-started/workflow-workspace-view.md b/14/umbraco-workflow/getting-started/workflow-workspace-view.md deleted file mode 100644 index 5d1bd4aabf4..00000000000 --- a/14/umbraco-workflow/getting-started/workflow-workspace-view.md +++ /dev/null @@ -1,102 +0,0 @@ -# Workspace View - -Umbraco Workflow adds a [Workspace View](https://docs.umbraco.com/umbraco-cms/customizing/extending-overview/extension-types/workspaces/workspace-views) to all content nodes in the **Content** section where a workflow is enabled. The Workflow workspace view includes three sub-sections: - -* [Active Workflow](workflow-workspace-view.md#active-workflow) -* [Configuration](workflow-workspace-view.md#configuration) -* [History](workflow-workspace-view.md#history) - -## Active Workflow - -The Active workflow sub-section provides an interface for managing workflows for the current content node. - -When the current node is pending workflow approval, the **Active workflow** sub-section displays detailed information such as: - -* Option to [approve, reject, or cancel pending workflow tasks](workflow-workspace-view.md#approve-reject-or-cancel-pending-workflow-tasks). -* View change description and track differences across pending and completed workflows. -* View the group responsible for approving the pending workflow. -* View pending language variant(s) workflow. -* View the workflow activity (eg. pending approval/task approvals/rejects) for the current workflow process. - -![Active Workflow sub-section](images/Active-Workflow-detailed-info-v14.png) - -You can access Active Workflows from two places - the **Content** section and the **Workflow** section (depending on your user permission). Workflow Administrators (those users with access to the Workflow section) can access workflows assigned to a different group. In the **Workflow History**, these are noted as being performed by the admin. - -### Approve, Reject, or Cancel pending workflow tasks - -#### Approve Workflow Tasks - -To approve a Workflow task, click on the **Approve** button in the Action section. - -#### Reject Workflow Tasks - -To reject a Workflow task, click on the **Reject** button in the Action section. Depending on the approval stage, the reviewer can decide where to send the rejected task. - -For first-stage approvals, the rejected task is sent back to the original editor/author. For second-stage approvals and above, the reviewer can send the rejected task either to the original editor or any other previous workflow group. - -![Reject Workflow Tasks](../../../10/umbraco-workflow/getting-started/images/assign-rejected-task.png) - -#### Cancel pending Workflow Tasks - -To cancel a pending Workflow task, click on the **Cancel** button in the Action section. - -## Configuration - -The Configuration sub-section provides an interface for configuring the content approval flow for the current node. It also displays any Inherited or Document type approval flows applied to the current content node. - -In multi-lingual sites, each variant can have its own approval flow. By default, new variants inherit the configuration set on the default language. - -For example, German variants can be approved by the German speakers group, while English variants are approved by the English speakers group. - -![Configuration sub-section](images/Configuration-sub-section-v14.png) - -### Content Approval Flow - -You can add different groups for different stages of content approval flow. Content Approval flow groups can be reordered via drag and drop. You can also apply the approval flow either for publish and unpublish workflows or only publish workflow. - -![Content approval flow](images/content-approval-flow-v14.png) - -#### Approval Flow Types - -Approval Flows are available in three types: Content approval flow, Inherited approval flow, and Document type approval flow. - -A given content node may have all three approval flow types applied but only one will be applied as per the following order of priority: - -| Flow Type | Description | Priority | -|---|---|---| -| **Content approval flow** | Set directly on a content node via the **Configuration** section in the **Workflow** tab. | Highest | -| **Document type approval flow** | Set in the **Settings** section. Applies to all content nodes of the selected Document Type unless overridden by a Content approval flow set directly on the node. Requires a license. | Secondary | -| **Inherited approval flow** | Used when a content node has no Content approval flow set, nor a flow applied to its Document Type. Umbraco Workflow will traverse the content tree upwards to find a Content approval flow. | Lowest | - -![Approval Flow Types](images/content-approval-flow-v14.png) - -Review the current Permissions for Approval Groups in the **Approval Groups** section for **Node-based approvals** and **Document type approvals** only. For more information see the [Roles](../workflow-section/approval-groups.md#roles) section in the [Approval Groups](../workflow-section/approval-groups.md) article. - -![Approval Groups Roles](images/approval-groups-roles-v14.png) - -Document type approval flows may contain conditional stages, such as including **Translators** in the workflow only when the **Description** property has changed. For more information on settings conditions in Document type approval flows, see the [Document type approval flows](../workflow-section/workflow-settings.md#document-type-approval-flows) section in the [Workflow Settings](../workflow-section/workflow-settings.md) article. - -Configuration cannot be modified when a content node is in a workflow process. - -#### Content reviews - -Content reviews is a tool that allows content editors to keep their content up-to-date. For more information, see the [Content reviews](../workflow-section/content-reviews.md) section. - -![Content reviews](images/Content-reviews-v14.png) - -## History - -The History sub-section provides a chronological audit trail of workflow activity for the current node. It displays a table containing the following information: - -* Type of Publish -* Who the workflow is requested by -* The date the workflow was requested -* Comments - -![History sub-section](images/History-sub-section-v14.png) - -You can also **Filter** the records based on the information listed above. Additionally, you can adjust the total number of records displayed on a page. - -The **Detail** button at the end of the record displays an overlay with content similar to the Active workflow sub-section. - -![Details overlay](images/Workflow-Content-app-Details-overlay-v14.png) diff --git a/14/umbraco-workflow/images/Active-workflow-initiate-request.png b/14/umbraco-workflow/images/Active-workflow-initiate-request.png deleted file mode 100644 index 0478888a065..00000000000 Binary files a/14/umbraco-workflow/images/Active-workflow-initiate-request.png and /dev/null differ diff --git a/14/umbraco-workflow/images/Active_Workflow_detailed_info.png b/14/umbraco-workflow/images/Active_Workflow_detailed_info.png deleted file mode 100644 index a10f9ca1800..00000000000 Binary files a/14/umbraco-workflow/images/Active_Workflow_detailed_info.png and /dev/null differ diff --git a/14/umbraco-workflow/images/Approval-group-settings-v14.png b/14/umbraco-workflow/images/Approval-group-settings-v14.png deleted file mode 100644 index 1360288c3fd..00000000000 Binary files a/14/umbraco-workflow/images/Approval-group-settings-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/images/Approval-groups.png b/14/umbraco-workflow/images/Approval-groups.png deleted file mode 100644 index 5c16278c585..00000000000 Binary files a/14/umbraco-workflow/images/Approval-groups.png and /dev/null differ diff --git a/14/umbraco-workflow/images/Buttons.png b/14/umbraco-workflow/images/Buttons.png deleted file mode 100644 index 3cc8d7e7ad1..00000000000 Binary files a/14/umbraco-workflow/images/Buttons.png and /dev/null differ diff --git a/14/umbraco-workflow/images/Configuration-sub-section.png b/14/umbraco-workflow/images/Configuration-sub-section.png deleted file mode 100644 index a48ae7e7507..00000000000 Binary files a/14/umbraco-workflow/images/Configuration-sub-section.png and /dev/null differ diff --git a/14/umbraco-workflow/images/Content-review-dashboard-v14.png b/14/umbraco-workflow/images/Content-review-dashboard-v14.png deleted file mode 100644 index e99aa91a062..00000000000 Binary files a/14/umbraco-workflow/images/Content-review-dashboard-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/images/Content-review-permissions-v14.png b/14/umbraco-workflow/images/Content-review-permissions-v14.png deleted file mode 100644 index 094af804328..00000000000 Binary files a/14/umbraco-workflow/images/Content-review-permissions-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/images/ContentSectionAfterInstall.png b/14/umbraco-workflow/images/ContentSectionAfterInstall.png deleted file mode 100644 index 46c4c1c4899..00000000000 Binary files a/14/umbraco-workflow/images/ContentSectionAfterInstall.png and /dev/null differ diff --git a/14/umbraco-workflow/images/Create-approval-group-v14.png b/14/umbraco-workflow/images/Create-approval-group-v14.png deleted file mode 100644 index 9531f844d4f..00000000000 Binary files a/14/umbraco-workflow/images/Create-approval-group-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/images/Default_Buttons.png b/14/umbraco-workflow/images/Default_Buttons.png deleted file mode 100644 index 45cace64303..00000000000 Binary files a/14/umbraco-workflow/images/Default_Buttons.png and /dev/null differ diff --git a/14/umbraco-workflow/images/Enable-content-reviews-v14.png b/14/umbraco-workflow/images/Enable-content-reviews-v14.png deleted file mode 100644 index af1f4b37517..00000000000 Binary files a/14/umbraco-workflow/images/Enable-content-reviews-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/images/Getting-Started-workflow.png b/14/umbraco-workflow/images/Getting-Started-workflow.png deleted file mode 100644 index bcf83a62547..00000000000 Binary files a/14/umbraco-workflow/images/Getting-Started-workflow.png and /dev/null differ diff --git a/14/umbraco-workflow/images/History-sub-section.png b/14/umbraco-workflow/images/History-sub-section.png deleted file mode 100644 index 1315413ea85..00000000000 Binary files a/14/umbraco-workflow/images/History-sub-section.png and /dev/null differ diff --git a/14/umbraco-workflow/images/Inherited-group-membership-v14.png b/14/umbraco-workflow/images/Inherited-group-membership-v14.png deleted file mode 100644 index d99af1cba53..00000000000 Binary files a/14/umbraco-workflow/images/Inherited-group-membership-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/images/Manage-packages-v11.png b/14/umbraco-workflow/images/Manage-packages-v11.png deleted file mode 100644 index 5be8f8f03db..00000000000 Binary files a/14/umbraco-workflow/images/Manage-packages-v11.png and /dev/null differ diff --git a/14/umbraco-workflow/images/Manage_packages_v10.png b/14/umbraco-workflow/images/Manage_packages_v10.png deleted file mode 100644 index 0478d7ffdb7..00000000000 Binary files a/14/umbraco-workflow/images/Manage_packages_v10.png and /dev/null differ diff --git a/14/umbraco-workflow/images/Manage_packages_v11.png b/14/umbraco-workflow/images/Manage_packages_v11.png deleted file mode 100644 index 97c3312c20e..00000000000 Binary files a/14/umbraco-workflow/images/Manage_packages_v11.png and /dev/null differ diff --git a/14/umbraco-workflow/images/Notifications-tab-v14.png b/14/umbraco-workflow/images/Notifications-tab-v14.png deleted file mode 100644 index 518288eb332..00000000000 Binary files a/14/umbraco-workflow/images/Notifications-tab-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/images/VS_Installation-v14.png b/14/umbraco-workflow/images/VS_Installation-v14.png deleted file mode 100644 index ae250a8d574..00000000000 Binary files a/14/umbraco-workflow/images/VS_Installation-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/images/Workflow-Admin-Dashboard-v14.png b/14/umbraco-workflow/images/Workflow-Admin-Dashboard-v14.png deleted file mode 100644 index 43e0e45066e..00000000000 Binary files a/14/umbraco-workflow/images/Workflow-Admin-Dashboard-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/images/Workflow-Content-app-Details-overlay.png b/14/umbraco-workflow/images/Workflow-Content-app-Details-overlay.png deleted file mode 100644 index 0c019a88c6a..00000000000 Binary files a/14/umbraco-workflow/images/Workflow-Content-app-Details-overlay.png and /dev/null differ diff --git a/14/umbraco-workflow/images/WorkflowDashboard-ContentSection-v14.png b/14/umbraco-workflow/images/WorkflowDashboard-ContentSection-v14.png deleted file mode 100644 index d5f4091f23a..00000000000 Binary files a/14/umbraco-workflow/images/WorkflowDashboard-ContentSection-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/images/WorkflowDashboard_WorkflowSection.png b/14/umbraco-workflow/images/WorkflowDashboard_WorkflowSection.png deleted file mode 100644 index 66d6181a8ce..00000000000 Binary files a/14/umbraco-workflow/images/WorkflowDashboard_WorkflowSection.png and /dev/null differ diff --git a/14/umbraco-workflow/images/Workflow_dashboard.png b/14/umbraco-workflow/images/Workflow_dashboard.png deleted file mode 100644 index 10402b30313..00000000000 Binary files a/14/umbraco-workflow/images/Workflow_dashboard.png and /dev/null differ diff --git a/14/umbraco-workflow/images/Workflow_section.png b/14/umbraco-workflow/images/Workflow_section.png deleted file mode 100644 index 9bc148d2e37..00000000000 Binary files a/14/umbraco-workflow/images/Workflow_section.png and /dev/null differ diff --git a/14/umbraco-workflow/images/active-workflow-detail-overlay.png b/14/umbraco-workflow/images/active-workflow-detail-overlay.png deleted file mode 100644 index 9c015834a93..00000000000 Binary files a/14/umbraco-workflow/images/active-workflow-detail-overlay.png and /dev/null differ diff --git a/14/umbraco-workflow/images/active-workflows-section.png b/14/umbraco-workflow/images/active-workflows-section.png deleted file mode 100644 index 816bda36569..00000000000 Binary files a/14/umbraco-workflow/images/active-workflows-section.png and /dev/null differ diff --git a/14/umbraco-workflow/images/add-approval-flow-v14.png b/14/umbraco-workflow/images/add-approval-flow-v14.png deleted file mode 100644 index e3ba5f262bd..00000000000 Binary files a/14/umbraco-workflow/images/add-approval-flow-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/images/add-doc-type-approval-flows-settings-v14.png b/14/umbraco-workflow/images/add-doc-type-approval-flows-settings-v14.png deleted file mode 100644 index 1166617a49b..00000000000 Binary files a/14/umbraco-workflow/images/add-doc-type-approval-flows-settings-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/images/add-group-member-v14.png b/14/umbraco-workflow/images/add-group-member-v14.png deleted file mode 100644 index b4c769ed60c..00000000000 Binary files a/14/umbraco-workflow/images/add-group-member-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/images/approval-flow-types.png b/14/umbraco-workflow/images/approval-flow-types.png deleted file mode 100644 index c58ac608eb9..00000000000 Binary files a/14/umbraco-workflow/images/approval-flow-types.png and /dev/null differ diff --git a/14/umbraco-workflow/images/approval-group-history-v14.png b/14/umbraco-workflow/images/approval-group-history-v14.png deleted file mode 100644 index 5e59bd5aaa9..00000000000 Binary files a/14/umbraco-workflow/images/approval-group-history-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/images/approval-group-members-v14.png b/14/umbraco-workflow/images/approval-group-members-v14.png deleted file mode 100644 index ebb48dfb7b8..00000000000 Binary files a/14/umbraco-workflow/images/approval-group-members-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/images/approval-groups-role-v14.png b/14/umbraco-workflow/images/approval-groups-role-v14.png deleted file mode 100644 index 2c61e4460a2..00000000000 Binary files a/14/umbraco-workflow/images/approval-groups-role-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/images/approval-groups-roles.png b/14/umbraco-workflow/images/approval-groups-roles.png deleted file mode 100644 index 281b1d36a29..00000000000 Binary files a/14/umbraco-workflow/images/approval-groups-roles.png and /dev/null differ diff --git a/14/umbraco-workflow/images/assign-rejected-task.png b/14/umbraco-workflow/images/assign-rejected-task.png deleted file mode 100644 index 365b4969a4b..00000000000 Binary files a/14/umbraco-workflow/images/assign-rejected-task.png and /dev/null differ diff --git a/14/umbraco-workflow/images/blocked_content.png b/14/umbraco-workflow/images/blocked_content.png deleted file mode 100644 index 0f23d2b8114..00000000000 Binary files a/14/umbraco-workflow/images/blocked_content.png and /dev/null differ diff --git a/14/umbraco-workflow/images/content-app.png b/14/umbraco-workflow/images/content-app.png deleted file mode 100644 index 312a09792dd..00000000000 Binary files a/14/umbraco-workflow/images/content-app.png and /dev/null differ diff --git a/14/umbraco-workflow/images/content-approval-flow.gif b/14/umbraco-workflow/images/content-approval-flow.gif deleted file mode 100644 index b2b078cacb3..00000000000 Binary files a/14/umbraco-workflow/images/content-approval-flow.gif and /dev/null differ diff --git a/14/umbraco-workflow/images/content-item-reviews-select-content-v14.png b/14/umbraco-workflow/images/content-item-reviews-select-content-v14.png deleted file mode 100644 index 01e7bf2372d..00000000000 Binary files a/14/umbraco-workflow/images/content-item-reviews-select-content-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/images/content-item-reviews-settings.png b/14/umbraco-workflow/images/content-item-reviews-settings.png deleted file mode 100644 index 8b68fb47d94..00000000000 Binary files a/14/umbraco-workflow/images/content-item-reviews-settings.png and /dev/null differ diff --git a/14/umbraco-workflow/images/content-item-reviews-v14.png b/14/umbraco-workflow/images/content-item-reviews-v14.png deleted file mode 100644 index c60a9cac09c..00000000000 Binary files a/14/umbraco-workflow/images/content-item-reviews-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/images/content-review-date-v14.png b/14/umbraco-workflow/images/content-review-date-v14.png deleted file mode 100644 index f51e5fc0ae6..00000000000 Binary files a/14/umbraco-workflow/images/content-review-date-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/images/content-review-message-banner-v14.png b/14/umbraco-workflow/images/content-review-message-banner-v14.png deleted file mode 100644 index 0b0aa54e4ca..00000000000 Binary files a/14/umbraco-workflow/images/content-review-message-banner-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/images/content-reviews-filter-v14.png b/14/umbraco-workflow/images/content-reviews-filter-v14.png deleted file mode 100644 index 7e26e61ceaa..00000000000 Binary files a/14/umbraco-workflow/images/content-reviews-filter-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/images/content-reviews-general-settings-v14.png b/14/umbraco-workflow/images/content-reviews-general-settings-v14.png deleted file mode 100644 index 33aa0f55415..00000000000 Binary files a/14/umbraco-workflow/images/content-reviews-general-settings-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/images/content-reviews-pagesize-v14.png b/14/umbraco-workflow/images/content-reviews-pagesize-v14.png deleted file mode 100644 index 249401a2058..00000000000 Binary files a/14/umbraco-workflow/images/content-reviews-pagesize-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/images/details-overlay.png b/14/umbraco-workflow/images/details-overlay.png deleted file mode 100644 index 8790cad0869..00000000000 Binary files a/14/umbraco-workflow/images/details-overlay.png and /dev/null differ diff --git a/14/umbraco-workflow/images/doc-type-approval-flows-v14.png b/14/umbraco-workflow/images/doc-type-approval-flows-v14.png deleted file mode 100644 index c330b4cdc64..00000000000 Binary files a/14/umbraco-workflow/images/doc-type-approval-flows-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/images/document-type-review-settings-v13.png b/14/umbraco-workflow/images/document-type-review-settings-v13.png deleted file mode 100644 index f2989cd709a..00000000000 Binary files a/14/umbraco-workflow/images/document-type-review-settings-v13.png and /dev/null differ diff --git a/14/umbraco-workflow/images/document-type-review-settings.png b/14/umbraco-workflow/images/document-type-review-settings.png deleted file mode 100644 index 5a2084b7036..00000000000 Binary files a/14/umbraco-workflow/images/document-type-review-settings.png and /dev/null differ diff --git a/14/umbraco-workflow/images/document-type-reviews-select-content-v14.png b/14/umbraco-workflow/images/document-type-reviews-select-content-v14.png deleted file mode 100644 index 9ed524ff80b..00000000000 Binary files a/14/umbraco-workflow/images/document-type-reviews-select-content-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/images/document-type-reviews-v14.png b/14/umbraco-workflow/images/document-type-reviews-v14.png deleted file mode 100644 index 4e4a5ac3091..00000000000 Binary files a/14/umbraco-workflow/images/document-type-reviews-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/images/edit-doc-type-approval-flows-settings-v14.png b/14/umbraco-workflow/images/edit-doc-type-approval-flows-settings-v14.png deleted file mode 100644 index ae6c6f9ccb9..00000000000 Binary files a/14/umbraco-workflow/images/edit-doc-type-approval-flows-settings-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/images/edit-doc-type-approval-flows-v14.png b/14/umbraco-workflow/images/edit-doc-type-approval-flows-v14.png deleted file mode 100644 index 501dc8ecd27..00000000000 Binary files a/14/umbraco-workflow/images/edit-doc-type-approval-flows-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/images/exclude-nodes-v14.png b/14/umbraco-workflow/images/exclude-nodes-v14.png deleted file mode 100644 index 4c73fbf02ce..00000000000 Binary files a/14/umbraco-workflow/images/exclude-nodes-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/images/general-settings-v13.png b/14/umbraco-workflow/images/general-settings-v13.png deleted file mode 100644 index bab01c20694..00000000000 Binary files a/14/umbraco-workflow/images/general-settings-v13.png and /dev/null differ diff --git a/14/umbraco-workflow/images/general-settings.png b/14/umbraco-workflow/images/general-settings.png deleted file mode 100644 index e4a6b20446e..00000000000 Binary files a/14/umbraco-workflow/images/general-settings.png and /dev/null differ diff --git a/14/umbraco-workflow/images/history-detail-button.png b/14/umbraco-workflow/images/history-detail-button.png deleted file mode 100644 index 660014094ca..00000000000 Binary files a/14/umbraco-workflow/images/history-detail-button.png and /dev/null differ diff --git a/14/umbraco-workflow/images/history-filter-v14.png b/14/umbraco-workflow/images/history-filter-v14.png deleted file mode 100644 index e936604f13f..00000000000 Binary files a/14/umbraco-workflow/images/history-filter-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/images/history-pagesize.png b/14/umbraco-workflow/images/history-pagesize.png deleted file mode 100644 index 8d55160e9f9..00000000000 Binary files a/14/umbraco-workflow/images/history-pagesize.png and /dev/null differ diff --git a/14/umbraco-workflow/images/lic.png b/14/umbraco-workflow/images/lic.png deleted file mode 100644 index ac07a7f0428..00000000000 Binary files a/14/umbraco-workflow/images/lic.png and /dev/null differ diff --git a/14/umbraco-workflow/images/new-node-approval-flow-v14.png b/14/umbraco-workflow/images/new-node-approval-flow-v14.png deleted file mode 100644 index 3436bff17f9..00000000000 Binary files a/14/umbraco-workflow/images/new-node-approval-flow-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/images/select-content-from-tree-v14.png b/14/umbraco-workflow/images/select-content-from-tree-v14.png deleted file mode 100644 index 8e065b8a608..00000000000 Binary files a/14/umbraco-workflow/images/select-content-from-tree-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/images/workflow-content-app-configuration.png b/14/umbraco-workflow/images/workflow-content-app-configuration.png deleted file mode 100644 index 20f3d9ec942..00000000000 Binary files a/14/umbraco-workflow/images/workflow-content-app-configuration.png and /dev/null differ diff --git a/14/umbraco-workflow/images/workflow-history-v14.png b/14/umbraco-workflow/images/workflow-history-v14.png deleted file mode 100644 index d9a6d22ae08..00000000000 Binary files a/14/umbraco-workflow/images/workflow-history-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/images/workflow-section-v14.png b/14/umbraco-workflow/images/workflow-section-v14.png deleted file mode 100644 index 1493d5e21de..00000000000 Binary files a/14/umbraco-workflow/images/workflow-section-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/images/workflow-settings-v14.png b/14/umbraco-workflow/images/workflow-settings-v14.png deleted file mode 100644 index 58d540aac88..00000000000 Binary files a/14/umbraco-workflow/images/workflow-settings-v14.png and /dev/null differ diff --git a/14/umbraco-workflow/installation/installing-workflow.md b/14/umbraco-workflow/installation/installing-workflow.md deleted file mode 100644 index 425ac1bb83a..00000000000 --- a/14/umbraco-workflow/installation/installing-workflow.md +++ /dev/null @@ -1,71 +0,0 @@ -# Installation - -In this article, we will cover the steps required to install Umbraco Workflow on your website. - -## Prerequisites - -* [Microsoft Visual Studio](https://visualstudio.microsoft.com/) - -### Video Tutorial - -{% embed url="https://www.youtube.com/embed/OUD-PbWESAs?rel=0" %} -Installing Umbraco Workflow. -{% endembed %} - -## Umbraco Workflow Installation - -There are different ways to install Umbraco Workflow: - -* [.Net CLI Installation](installing-workflow.md#net-cli-installation) -* [Visual Studio Installation](installing-workflow.md#visual-studio-installation) - -### .Net CLI Installation - -To install the Umbraco Workflow package (Umbraco.Workflow), follow these steps: - -1. Run the following command to add a package reference to your Umbraco project: - -``` -dotnet add package Umbraco.Workflow -``` - -2. Restart the web application using the following command: - -``` -dotnet run -``` - -### Visual Studio Installation - -To install via Visual Studio, follow these steps: - -1. Open your project in Visual Studio. -2. Go to **Tools** -> **NuGet Package Manager** -> **Manage NuGet Packages for Solution...**. -3. Browse for **Umbraco.Workflow**. -4. Select the appropriate version from the Version drop-down depending on the Umbraco version you are using. -5. Click **Install**. - - ![Installing Umbraco Workflow](../images/VS_Installation-v14.png) -6. Once the package is installed, open the **.csproj** file to make sure the package reference is added: - -```xml - - - -``` - -{% hint style="info" %} -To test-drive Umbraco Workflow consider installing the [Umbraco.Workflow.DataGenerator package](../data-generator/data-generator). -{% endhint %} - -## Using Umbraco Workflow - -Once the installation is completed, you will see the following in the Umbraco Backoffice: - -### A Workflow Dashboard - -![Workflow dashboard.](../images/ContentSectionAfterInstall.png) - -### A Workflow section - -![Workflow section.](../images/workflow-section-v14.png) diff --git a/14/umbraco-workflow/installation/licensing.md b/14/umbraco-workflow/installation/licensing.md deleted file mode 100644 index 6d5bbaa0951..00000000000 --- a/14/umbraco-workflow/installation/licensing.md +++ /dev/null @@ -1,160 +0,0 @@ -# Licensing - -Umbraco Workflow is a licensed product that does not require a purchase. New installations default to a trial license while the paid license is available for purchase. - -## Purchasing an Umbraco Workflow License - -If you want to buy an Umbraco Workflow license, use [the contact form to get in touch](https://umbraco.com/products/add-ons/workflow#order). - -### Free vs licensed versions - -Umbraco Workflow is available in free and licensed versions. While the licensed version includes all features and no restrictions, the free version has some limitations. - -In the free version, the following features are disabled: - -- Document Type workflow configuration -- Document Type content review configuration -- History cleanup and related configuration -- Approval thresholds and related configuration -- Content comparison -- Exclude nodes - -In the free version, a maximum of five approval groups can be created. - -## Installing your license - -Once you have received your license code it needs to be installed on your site. - -1. Open the root directory for your project files. -2. Locate and open the `appSettings.json` file. -3. Add your Umbraco Workflow license key to `Umbraco:Licenses:Umbraco.Workflow`: - -```json -"Umbraco": { - "Licenses": { - "Products": { - "Umbraco.Workflow": "YOUR_LICENSE_KEY" - } - } -} -``` - -{% hint style="info" %} -You might run into issues when using a period in the product name when using environment variables. Use an underscore in the product name instead, to avoid problems. - -```json -"Umbraco_Workflow": "YOUR_LICENSE_KEY" -``` -{% endhint %} - -### Verify the license installation - -You can verify that your license is successfully installed by logging into your project's backoffice and navigating to the settings section. Here you will see a licenses dashboard which should display the status of your license. - -### When and how to configure an `UmbracoApplicationUrl` - -The website domain used for validating the license is determined from your Umbraco instance. To ensure the correct one is used, you can configure the `UmbracoApplicationUrl`. - -If you are running on a single domain for both your frontend and backend environments, it's not necessary to configure a `UmbracoApplicationUrl`. - -If you have different domains for your frontend and backend, then it's advised that you configure an `UmbracoApplicationUrl` set to your backoffice URL. This helps the licensing engine know which URL should be used for validation checks. Without this configuration setting, the licensing engine will try and work out the domain to validate from the HTTP request object. This can lead to errors when switching between domains. - -An `UmbracoApplicationUrl` can be configured in your `appSettings.json` file like so: - -```json -{ - "Umbraco": { - "CMS": { - "WebRouting": { - "UmbracoApplicationUrl": "https://admin.my-custom-domain.com/" - } - } - } -} -``` - -See the [Fixed Application URL](https://docs.umbraco.com/umbraco-cms/extending/health-check/guides/fixedapplicationurl) documentation for more details about this setting. - -#### Configuring `UmbracoApplicationUrl` on Umbraco Cloud - -If you are hosting on Umbraco Cloud you will find the configuration described above won't be reflected in your environment. The reason for this is that Umbraco Cloud sets this value as an environment variable set to the Cloud project domain (`.umbraco.io`). This overrides what is set via the `appSettings.json` file. - -There are two options in this case: -- Either the domains for each of your Cloud environments can be added to your license. -- Or, for more control and to ensure this value is set correctly for other reasons, you can apply the configuration via code. - -For example, in your `Program.cs` file: - -```csharp -builder.Services.Configure(o => o.UmbracoApplicationUrl = ""); -``` - -In practice, you will probably want to make this a bit more sophisticated. You can read the value from another configuration key, removing the need to hard-code it and have it set as appropriate in different environments. You can also move this code into a composer or an extension method if you prefer not to clutter up the `Program.cs` file. - -### Using a Trial License - -The trial license introduces some restrictions around advanced features but is otherwise a full-featured workflow platform. The paid license is valid for one top-level domain and all its subdomains. - -To impersonate the full license on a local site, set `EnableTestLicense` to `true` in the `appSettings.json` file: - -```json -{ - "Umbraco": { - "Workflow": { - "EnableTestLicense": true - } - } -} -``` - -{% hint style="info" %} -The test license is restricted to sites running in a development environment with a debugger attached. Hit F5 in Visual Studio, in Debug mode to enable the test license. -{% endhint %} - -### Validating a license without an outgoing Internet connection - -Some Umbraco installations will have a highly locked down production environment, with firewall rules that prevent outgoing HTTP requests. This will interfere with the normal process of license validation. - -On start-up, and periodically whilst Umbraco is running, the license component used by Umbraco Workflow will make an HTTP POST request to `https://license-validation.umbraco.com/api/ValidateLicense`. - -If it's possible to do so, the firewall rules should be adjusted to allow this request. - -If such a change is not feasible, there is another approach you can use. - -You will need to have a server, or serverless function, that is running and can make a request to the online license validation service. That needs to run on a daily schedule, making a request and relaying it onto the restricted Umbraco environment. - -To set this up, firstly ensure you have a reference to `Umbraco.Licenses` version 13.1 or higher. If the version of Workflow you are using depends on an earlier version, you can add a direct package reference for `Umbraco.Licenses`. - -Then configure a random string as an authorization key in configuration. This is used as protection to ensure only valid requests are handled. You can also disable the normal regular license checks - as there is no point in these running if they will be blocked: - -```json - "Umbraco": { - "Licenses": { - "Umbraco.Workflow": "" - }, - "LicensesOptions": { - "EnableScheduledValidation": false, - "ValidatedLicenseRelayAuthKey": "" - } -``` - -Your Internet enabled server should make a request of the following form to the online license validation service: - -``` -POST https://license-validation.umbraco.com/api/ValidateLicense -{ - "ProductId": "Umbraco.Workflow", - "LicenseKey": "", - "Domain": "" -} -``` - -The response should be relayed exactly via an HTTP request to your restricted Umbraco environment: - -``` -POST http:///umbraco/licenses/validatedLicense/relay?productId=&licenseKey= -``` - -A header with a key of `X-AUTH-KEY` and value of the authorization key you have configured should be provided. - -This will trigger the same processes that occur when the normal scheduled validation completes ensuring your product is considered licensed. diff --git a/14/umbraco-workflow/legacy-documentation.md b/14/umbraco-workflow/legacy-documentation.md deleted file mode 100644 index 721d81f2a37..00000000000 --- a/14/umbraco-workflow/legacy-documentation.md +++ /dev/null @@ -1,7 +0,0 @@ -# Legacy Documentation - -This documentation platform covers only major versions of the Umbraco Workflow since Umbraco 9+. If you are using Umbraco Plumber, you will need to go elsewhere. - -The documentation for Umbraco 7 and 8 lives on [our.umbraco.com](https://our.umbraco.com/documentation/Add-ons/). - -
Umbraco 11 Documentationhttps://github.com/umbraco/UmbracoDocs/tree/umbraco-eol-versions/11/umbraco-workflow
Umbraco 8 Documentationhttps://our.umbraco.com/documentation/Add-ons/Umbraco-Plumber/
diff --git a/14/umbraco-workflow/release-notes.md b/14/umbraco-workflow/release-notes.md deleted file mode 100644 index 4e4e03cb53a..00000000000 --- a/14/umbraco-workflow/release-notes.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -description: >- - Get an overview of the things changed and fixed in each version of Umbraco Workflow. ---- - -# Release notes - -In this section, we have summarized the changes to Umbraco Workflow released in each version. Each version is presented with a link to the [Workflow issue tracker](https://github.com/umbraco/Umbraco.Workflow.Issues/issues) showing a list of issues resolved in the release. We also link to the individual issues themselves from the detail. - -If there are any breaking changes or other issues to be aware of when upgrading they are also noted here. - -{% hint style="info" %} -Check the [Version Specific Upgrade Notes](upgrading/version-specific.md) article for breaking changes when upgrading to a new major version. -{% endhint %} - -## Release History - -This section contains the release notes for Umbraco Workflow 14 including all changes for this version. - -### [14.1.4](https://github.com/umbraco/Umbraco.Workflow.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.1.4) (January 16 2025 ) -* Fixes workflow task summary generation in email body [#91](https://github.com/umbraco/Umbraco.Workflow.Issues/issues/91) -* Fixes localization in email body -* Updates Umbraco.Licenses dependency -* Refactors migration plan naming to align with the broader DXP product suite. - -### 14.1.3 (December 16th 2024) -* Fixes column type mismatch in migration -* Correctly implements delay time in History Cleanup hosted service - -### 14.1.2 (November 14th 2024) -* Adds abstraction over `UmbContentWorkspaceContext.readOnlyState` to consistently implement readonly document workspaces. -* Fixes invariant culture handling when unlocking a scheduled document. - -### 14.1.1 (November 7th 2024) -* Fixes a bug causing migrations from Workflow 13 to fail on SQL Server. -* Fixes the above exposed a secondary issue where the migration from integer to GUID identifiers was incomplete. This resulted in incorrect relationships between approval groups and tasks in historic Workflow data, and incorrect information displaying the backoffice. -* Adds SQL query performance improvements. -* Adds loading indicator to Workflow tables in the backoffice. - -### [14.1.0](https://github.com/umbraco/Umbraco.Workflow.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.1.0) (October 23rd 2024 ) -* Adds scheduled content locking feature. Documents can be made readonly until the scheduled release date passes, to ensure approved content is not modified without workflow approval. [#84](https://github.com/umbraco/Umbraco.Workflow.Issues/issues/84) -* Adds support for readonly mode when a document is pending workflow approval. Along with the scheduled content lock, this feature requires Umbraco 14.3.0, which is now the minumum version dependency for Umbraco Workflow v14. -* Adds support for content segments. Segment names are displayed when requesting approval and in workflow history [#60](https://github.com/umbraco/Umbraco.Workflow.Issues/issues/60) -* Adds support for Arabic. -* Improves UI in workflow detail overlay. Reduces the number of elements and shifts appropriate data points into tag elements. -* Adds email queue for thread-safe email notifications. Emails are now processed in the hosted service, via a first-in first-out queue. This resolves a reported issue where sending large numbers of emails could result in data reader errors. [#85](https://github.com/umbraco/Umbraco.Workflow.Issues/issues/85) - -### [14.0.3](https://github.com/umbraco/Umbraco.Workflow.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.0.3) (October 3rd 2024) -* Ensure scheduling information is displayed in workflow history [#82](https://github.com/umbraco/Umbraco.Workflow.Issues/issues/82) -* Fixes an issue where dates were not correctly localized for scheduled workflows [#81](https://github.com/umbraco/Umbraco.Workflow.Issues/issues/81) -* Fixes an issue where scheduled workflows did not apply the release/expire date if the content node was already scheduled [#81](https://github.com/umbraco/Umbraco.Workflow.Issues/issues/80) -* Ensure converting integers to strings uses the invariant culture to avoid unexpected formatting -* Fixes an issue related to sending notification emails in sites with a large number of workflow groups [#79](https://github.com/umbraco/Umbraco.Workflow.Issues/issues/79) - -### [14.0.2](https://github.com/umbraco/Umbraco.Workflow.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.0.2) (August 5th 2024) - -* Fixes an issue where available approval group names were not displayed in Document Type approval flow condition configuration [#76](https://github.com/umbraco/Umbraco.Workflow.Issues/issues/76) -* Updates to allow editing approval group roles (content and/or Document Type) via overlay [#75](https://github.com/umbraco/Umbraco.Workflow.Issues/issues/75) -* Fixes an issue where adding status filters did not update the filter context [#74](https://github.com/umbraco/Umbraco.Workflow.Issues/issues/74) -* Updates workflow history table to include status column [#72](https://github.com/umbraco/Umbraco.Workflow.Issues/issues/72) -* Updates incorrect localization in Document Type review settings overlay [#71](https://github.com/umbraco/Umbraco.Workflow.Issues/issues/71) -* Fixes clear button functionality in filter modal [#67](https://github.com/umbraco/Umbraco.Workflow.Issues/issues/67) -* Fixes approval group options in reject task modal [#65](https://github.com/umbraco/Umbraco.Workflow.Issues/issues/65) -* Updates incorrect localization in workflow detail modal when the state is `pending approval` [#64](https://github.com/umbraco/Umbraco.Workflow.Issues/issues/64) -* Fixes conditional display of core workspace actions when `extend permissions` is set to true [#62](https://github.com/umbraco/Umbraco.Workflow.Issues/issues/62) -* Updates submit-for-approval notification to remove invariant workflow indicator [#61](https://github.com/umbraco/Umbraco.Workflow.Issues/issues/61) -* Fixes issues related to requesting approval on newly created variant content - * [#69](https://github.com/umbraco/Umbraco.Workflow.Issues/issues/69) - * [#68](https://github.com/umbraco/Umbraco.Workflow.Issues/issues/68) - * [#66](https://github.com/umbraco/Umbraco.Workflow.Issues/issues/66) -* UI updates in workflow detail modal - -### [14.0.1](https://github.com/umbraco/Umbraco.Workflow.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.0.1) (July 24 2024) - -* Fixes an issue where changes to approval group membership were not correctly persisted - -### [14.0.0](https://github.com/umbraco/Umbraco.Workflow.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.0.0) (May 30 2024) - -* Compatibility with Umbraco 14 - * For full details of breaking changes refer to the [Version Specific Upgrade Notes](upgrading/version-specific.md) - -## Legacy release notes - -You can find the release notes for versions out of support in the [Legacy documentation on GitHub](https://github.com/umbraco/UmbracoDocs/blob/umbraco-eol-versions/11/umbraco-workflow/release-notes.md) diff --git a/14/umbraco-workflow/upgrading/migrating-workflow.md b/14/umbraco-workflow/upgrading/migrating-workflow.md deleted file mode 100644 index bd08c7ec8b8..00000000000 --- a/14/umbraco-workflow/upgrading/migrating-workflow.md +++ /dev/null @@ -1,33 +0,0 @@ -# Migrate from Plumber to Workflow - -Umbraco Workflow is backwards compatible with Plumber data. However, with a new default namespace constituting a major breaking change any existing customization or extension needs to be updated. - -To migrate from an Umbraco installation with an existing Plumber installation to Umbraco Workflow, follow these steps: - -{% tabs %} -{% tab title="Site running on SQL Server database" %} -1. Uninstall Plumber and remove the `/App_Plugins/Plumber` folder. -2. Upgrade your project to Umbraco 11. -3. Install Umbraco Workflow 11. See the [Installing Umbraco Workflow](../installation/installing-workflow.md) article. -4. Build the application. - -{% hint style="info" %} -SQL is the preferred database provider for production websites. -{% endhint %} -{% endtab %} - -{% tab title="Site running on SQLite database" %} -1. Uninstall Plumber and remove the `/App_Plugins/Plumber` folder. -2. Upgrade your project to Umbraco 11. -3. Make a copy of the `Value` column from the `WorkflowSettings` table. -4. Delete the `WorkflowSettings` table. -5. Update `WorkflowTaskInstance` table to allow null values in the GroupId column. -6. Install Umbraco Workflow 11. See the [Installing Umbraco Workflow](../installation/installing-workflow.md) article. -7. Build the application. -8. Update the `WorkflowSettings` table to restore the previous data to the `Value` column. -{% endtab %} -{% endtabs %} - -{% hint style="info" %} -All your existing workflow data and settings are not affected and will be available on your upgraded site. -{% endhint %} diff --git a/14/umbraco-workflow/upgrading/upgrading.md b/14/umbraco-workflow/upgrading/upgrading.md deleted file mode 100644 index 5dd85d868b7..00000000000 --- a/14/umbraco-workflow/upgrading/upgrading.md +++ /dev/null @@ -1,36 +0,0 @@ -# Upgrading - -This article shows how to manually upgrade Umbraco Workflow to run the latest version. Umbraco Workflow displays a prompt in the **Workflow** section when a new version is available. - -{% hint style="info" %} -If you are migrating from Plumber to Umbraco Workflow, see the [Migrate from Plumber to Workflow](migrating-workflow.md) article. -{% endhint %} - -## Get the latest version of Umbraco Workflow - -To get the latest version of Umbraco Workflow, you can upgrade using either of the two options: - -* [NuGet](upgrading.md#nuget) -* [Visual Studio](upgrading.md#visual-studio) - -### NuGet - -* NuGet installs the latest version of the package when you use the `dotnet add package Umbraco.Workflow` command unless you specify a package version: - - `dotnet add package Umbraco.Workflow --version ` -* Run `dotnet restore` to install the package. - -### Visual Studio - -* Go to `Tools` -> `NuGet Package Manager` -> `Manage NuGet Packages for Solution...` in Visual Studio, to upgrade Umbraco Workflow: -* Select **Umbraco.Workflow**. -* Select the latest version from the **Version** drop-down and click **Install**. - - ![NuGet Package Manager](../images/VS_Installation-v14.png) -* Open the **.csproj** file to make sure the package reference is updated: - - ```xml - - - - ``` diff --git a/14/umbraco-workflow/upgrading/version-specific.md b/14/umbraco-workflow/upgrading/version-specific.md deleted file mode 100644 index 5a47bbb9f4f..00000000000 --- a/14/umbraco-workflow/upgrading/version-specific.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -description: >- - Version specific documentation for upgrading to new major versions of Umbraco - Workflow. ---- - -# Version Specific Upgrade Notes - -This page covers specific upgrade documentation for when migrating to Umbraco Workflow version 14. - -{% hint style="info" %} -If you are upgrading to a new minor or patch version, you can find information about the breaking changes in the [Release Notes](../release-notes.md) article. -{% endhint %} - -## Version Specific Upgrade Notes History - -Version 14 of Umbraco Workflow has a minimum dependency on Umbraco CMS core of `14.1.0`. It runs on .NET 8. - -#### **Breaking changes** - -Version 14 contains a number of breaking changes, primarily due to the new backoffice introduced in Umbraco 14. The details are listed here: - -#### **Behaviour** - -* A new management API has been introduced at `umbraco/workflow/management/api` - -#### Dependencies - -* Umbraco CMS dependency was updated to `14.1.0` - -#### **Code** - -Workflow 14 includes a non-trivial number of breaking code changes, primarily related to namespace changes. The majority of these related to removing the `Implement` namespace for services, and moving appropriate models to `Umbraco.Workflow.Core.ViewModels` or `Umbraco.Workflow.Core.Interfaces`. - -* The serialization library has been changed from `Newtonsoft.Json` to `System.Text.Json`. -* Approval group identifiers changes from int to Guid. -* Workflow instance author identifier changes from int to Guid. -* Workflow task indentifiers for approving user, assigned user and actioning user change from int to Guid. -* Services return `Attempt` or `Attempt`, in line with similar changes in the CMS. - -## Legacy version specific upgrade notes - -You can find the version specific upgrade notes for versions out of support in the [Legacy documentation on GitHub](https://github.com/umbraco/UmbracoDocs/tree/umbraco-eol-versions). diff --git a/14/umbraco-workflow/workflow-section/active-workflows.md b/14/umbraco-workflow/workflow-section/active-workflows.md deleted file mode 100644 index ebecbdf4854..00000000000 --- a/14/umbraco-workflow/workflow-section/active-workflows.md +++ /dev/null @@ -1,22 +0,0 @@ -# Active Workflows - -The Active Workflows view in the **Workflow** section provides an administrator view of the active Workflows. It displays a table containing the following details: - -* Page name/Node with the Language variant. -* Type of Publish. -* Date the workflow was requested on. -* Comment describing the changes. - -![Active Workflows](../../../10/umbraco-workflow/images/active-workflows-section.png) - -You can also **Filter** the records based on the Node, Requested by, Created date, Completed date, Page Language, Workflow Type, and Workflow Status. - -![Workflow history Filters](../images/history-filter-v14.png) - -Additionally, you can adjust the total number of records displayed on a page. - -![Workflow history PageSize](../images/content-reviews-pagesize-v14.png) - -The **Detail** button at the end of the record displays an overlay with content similar to the [Active workflow](../getting-started/workflow-content-app.md#active-workflow) sub-section. - -![Details overlay](../getting-started/images/Active-Workflow-detailed-info-v14.png) diff --git a/14/umbraco-workflow/workflow-section/approval-groups.md b/14/umbraco-workflow/workflow-section/approval-groups.md deleted file mode 100644 index 3edb18124ce..00000000000 --- a/14/umbraco-workflow/workflow-section/approval-groups.md +++ /dev/null @@ -1,98 +0,0 @@ -# Approval Groups - -The **Approval groups** view in the **Workflow** section lists the active groups name, group members, their permissions, and a quick link to email the group. - -![Approval groups](../getting-started/images/approval-groups-roles-v14.png) - -To add an approval group, follow these steps: - -1. Go to the **Workflow** section. -2. Click on **Approval groups**. -3. Click **Create**. -4. Enter a **Name** for the Approval Group. For example: Danish Editors. -5. Enter the **Group Email** address in the **Settings** section to which the notifications will be sent. -6. Select the **Group Language** from the drop-down list in the **Settings** section. -7. Click **Save**. - - ![Create Approval Group](../images/Create-approval-group-v14.png) - -{% hint style="info" %} -You can create a total of 5 groups on unlicensed installations. The paid license removes this restriction. -{% endhint %} - -You can search for a specific group using the Search bar. Select a group from the list to edit its Settings, Roles, Members, and view the group's History. - -## Approval Groups Settings - -The **Settings** tab consists of the following fields: - -* **Group Email:** Workflow notifications are sent to a generic inbox (a group's email address) rather than the individual group members. -* **Group Language:** Select a language variant for the email. -* **Workflow Activity:** Provides a chart displaying an overview of the workflow activity such as approved, cancelled, rejected, or pending approvals for the current group. - -![Approval group Settings](../images/Approval-group-settings-v14.png) - -## Members - -The **Members** tab manages the membership for the given user group. Add members to approval groups to determine which member will be responsible for approving content changes. Group Members can be explicitly added to the group or can inherit group membership from an existing Umbraco group. Ideally, group members are set explicitly to ensure changes made to Umbraco groups do not cause unexpected changes to workflow permissions. - -![Approval group Members](../images/approval-group-members-v14.png) - -To add a Group member, follow these steps: - -1. Go to the **Workflow** section. -2. Click on **Approval groups**. -3. Select a group from the list to edit its Members. -4. Go to the **Members** tab. -5. Click **Choose** in the **Group members** section. -6. Select the **Users** you want to add to the approval group. - - ![Add group Members](../images/add-group-member-v14.png) -7. Click **Submit**. -8. Click **Save**. - -To remove a Group member, click **Remove**. - -To inherit an existing Umbraco group membership, follow these steps: - -1. Go to the **Workflow** section. -2. Click on **Approval groups**. -3. Select a group from the list to edit its Members. -4. Go to the **Members** tab. -5. Click **Choose** in the **Inherited group membership** section. -6. Select the **User groups** you want to add to the approval group. - - ![Inherited group membership](../images/Inherited-group-membership-v14.png) -7. Click **Submit**. -8. Click **Save**. - -To remove a Group membership, click **Remove**. - -## Roles - -The **Roles** tab provides an overview of the current workflow roles for the Group: - -* **Node-based approvals**: This workflow applies only to the specified node. -* **Document-type approvals**: This workflow applies to all the nodes of a given Document Type. - -You can set these **Roles** in the Workflow **Settings** section. For more information, see the [Workflow Settings](workflow-settings.md) article. - -![Approval group Roles](../images/approval-groups-role-v14.png) - -## History - -The History tab provides an overview of the workflow activity for the current group. It displays a table containing the following details: - -* Page name with the Language variant -* Type of Publish -* Workflow requested by -* Date the workflow was requested on -* Comment describing the changes - -![Approval group history](../images/approval-group-history-v14.png) - -You can also **Filter** the records based on the Document Type, Requested by, Created date, Completed date, Page Language, Workflow Type, and Workflow Status. Additionally, you can adjust the total number of records displayed on a page. - -The **Detail** button at the end of the record displays an overlay with content similar to the [Active workflow](../getting-started/workflow-content-app.md#active-workflow) sub-section. - -![Details overlay](../getting-started/images/Workflow-Content-app-Details-overlay-v14.png) diff --git a/14/umbraco-workflow/workflow-section/content-reviews.md b/14/umbraco-workflow/workflow-section/content-reviews.md deleted file mode 100644 index 493bc59c6f7..00000000000 --- a/14/umbraco-workflow/workflow-section/content-reviews.md +++ /dev/null @@ -1,158 +0,0 @@ -# Content Reviews - -Content reviews is a tool that allows content editors to keep their content up-to-date. **Content reviews** adds a new dashboard to the **Workflow** section. By default, Content reviews are disabled and can be enabled from **Content reviews Settings** in the **Workflow** section. - -![Enable Content Reviews](../images/Enable-content-reviews-v14.png) - -## Video overview - -{% embed url="https://youtu.be/mnSL7nrn10o" %} -Watch this video to learn how to use the Content Review feature in Umbraco Workflow -{% endembed %} - -## Content Reviews Dashboard - -The Content reviews Dashboard provides an overview of the expired content. The dashboard displays a table containing the following details: - -* Page name/Node with the Language variant -* Next review due date -* Last reviewed date -* Review period in days -* Review group - -![Content Reviews Dashboard](../images/Content-review-dashboard-v14.png) - -Selecting a content node takes you to the content node in the **Content** section where you can see the Content review banner. The Content review banner is displayed only when the node has passed its review date. Also, the review banner is displayed only to users assigned as reviewers for the node. For more information, see the [Content Reviews Permissions](content-reviews.md#content-review-permissions) section - -![Content Review Message Banner](../images/content-review-message-banner-v14.png) - -Clicking on **Mark as reviewed** allows the review group member to mark the content as reviewed. Optionally, the review group member can also set the next review date on the content node. The next review date must fall inside the review period set in the **Content Reviews Settings**. - -![Content Review Date](../images/content-review-date-v14.png) - -You can also **Filter** the records based on the Document Type, Review Group, Next review due date, Last reviewed date, and Expired review Status. - -![Content Reviews Filters](../images/content-reviews-filter-v14.png) - -Additionally, you can adjust the total number of records displayed on a page. - -![Content Reviews PageSize](../images/content-reviews-pagesize-v14.png) - -## Content Reviews Settings - -The Content reviews Settings tab provides a range of settings for configuring email notifications, review period days, reminder days, and so on. Using Content reviews, all content has a default review period. - -### General Settings - -You can configure the **General** Settings from the **Content reviews** tab in the **Workflow** section. The following settings are available: - -![General settings](../images/content-reviews-general-settings-v14.png) - -* **Enable content reviews** - Enable this setting if you wish to remind users to review their content. By default, this option is disabled. -* **Send notifications** - Enable this setting to send email notification to approval groups when content requires review. -* **Treat saving as a review?** - Enable this setting to reset the review date when content is saved. Saving a content node recalculates the review date, using the review period assigned to the content node, its Document Type, or the default Review period value. If disabled, content must be explicitly reviewed via the review banner displayed on the content item. -* **Review period (days)** - The default number of days between content reviews. -* **Reminder threshold (days)** - Determines how many days prior to the review date the Workflow should notify editors of required reviews. By default, the number of days is set to 1. - -### Content Review Permissions - -You can configure specific review groups to review designated content nodes or Document Types. The review group responsible for reviewing content is determined by the workflow configuration. This means a site with workflow already configured can leverage the existing permissions model for assigning content review responsibilities. By default, content reviews are assigned to the approval group defined in the first stage of the workflow. - -Content review permissions can be set at the node or Document Type level, both of which take precedence over any existing Workflow permissions. Permissions are assigned to user roles or groups within each workflow stage. For example: - -* Internal Reviewers: Users assigned to roles like *Editors* or *Content Managers* may have permissions to review content during the Internal Review stage. They ensure content quality, compliance with standards, and provide feedback for improvements before the content is published. -* External Reviewers: External reviewers are users who are invited to participate in the content review process but do not have Backoffice access. Their main role is to provide feedback or suggest changes based on their expertise or stake in the content being published. This feedback is not managed by Workflow. - -![Content review permissions](../images/Content-review-permissions-v13.png) - -The current permissions for a content node are displayed in the **Workflow** content app on the **Configuration** tab. - -![Workflow Content App - Configuration tab](../getting-started/images/content-approval-flow-v14.png) - -### Content Item and Document Type Reviews - -You can configure content reviews for individual content nodes or for all nodes of a given Document Type. For both Content Item and Document Type Reviews, the following settings are available: - -* **Language** - Allows you to specify which language version of the content is being reviewed. -* **Exclude from review** - Enable this setting to ignore the specific content node (or all content nodes of this Document Type) when determining nodes to review. -* **Review period (days)** - The review period in days between required reviews. -* **Review group** - The group responsible for reviewing the content node. Can contain more than one group. -* **External reviewers** - Assign email addresses for reviewers without CMS access. Feedback from external reviewers is not managed by Workflow. - -{% hint style="info" %} -When reviews are enabled or any changes to content review settings are saved, Workflow determines the review status. It assesses all the content needing review and provides this data in the Content reviews Dashboard. For large sites, or on the first run, this may take a few seconds to complete. -{% endhint %} - -#### Content Item Reviews - -To add a content item review, follow these steps: - -1. Go to the **Workflow** section. -2. Go to the **Settings** tab in the **Content reviews** menu. -3. Click **Add** in the **Content item reviews** section. - - ![Content Item Reviews](../images/content-item-reviews-v14.png) -4. Select **Content node** to add to the Content item reviews section. - - ![Select Content Node](../images/content-item-reviews-select-content-v14.png) -5. Select **Choose**. -6. Select the **Language** from the drop-down. -7. *[Optional]* Enable **Exclude from Review** if you wish to exclude this content node from content review. If you enable this setting, skip to step 12. -8. Enter the **Review period** in days. -9. Click **Choose** to add the **Review Group**. -10. Select an **approval group**. -11. Select **Submit**. -12. *[Optional]* Enter a user in the **External reviewers** field. For example: `john.doe@workflow.com`. - - ![Edit Content Item Review Settings](../images/Content-review-permissions-v14.png) -13. Click Submit. -14. Click **Save**. - -To Edit a content item review, click on the Content item and update the settings as per your requirement. - -To remove a content item review, click **Remove**. - -#### Document Type Reviews - -To add a Document Type review, follow these steps: - -1. Go to the **Workflow** section. -2. Go to the **Settings** tab in **Content reviews**. -3. Click **Add** in the **Document-type reviews** section. - - ![Document Type reviews](../images/document-type-reviews-v14.png) -4. Select **Content type** to add to the Document-type reviews section. - - ![Select Content Type](../images/document-type-reviews-select-content-v14.png) - -5. Select **Choose** -6. Select the **Language** from the drop-down. -7. *[Optional*] Enable **Exclude from Review** if you wish to exclude this Document-type from content review. If you enable this setting, skip to step 12. -8. Enter the **Review period** in days. -9. Click **Choose** to add the **Review Group**. -10. Select an **approval group**. -11. Click Submit. -12. *[Optional]* Enter a user in the **External reviewers** field. For example: `john.doe@workflow.com`. - - ![Add Document Type Review Settings](../images/document-type-review-settings-v13.png) -13. Click Submit. -14. Click **Save Settings**. - -To Edit a Document-type review, click **Edit** and update the settings as per your requirement. - -To remove a Document-type review, click **Remove**. - -## Content Review Notifications - -Content review notifications use the email template available at `~/Views/Partials/WorkflowEmails/ContentReviews.cshtml`, which can be customized as required. For example to add a corporate branding or send customized messages. - -To add templates for other languages: - -1. Go to the `~/Views/Partials/WorkflowEmails/` folder. -2. Copy the required template and paste it into the same folder. -3. Append the culture code to the file name prefixed with an underscore. - -For example: - -* **Default approval request template:** `~/Views/Partials/WorkflowEmails/ContentReviews.cshtml` -* **Danish approval request template:** `~/Views/Partials/WorkflowEmails/ContentReviews_da-DK.cshtml` diff --git a/14/umbraco-workflow/workflow-section/workflow-history.md b/14/umbraco-workflow/workflow-section/workflow-history.md deleted file mode 100644 index a1cd299c79a..00000000000 --- a/14/umbraco-workflow/workflow-section/workflow-history.md +++ /dev/null @@ -1,25 +0,0 @@ -# Workflow History - -The Umbraco Workflow History provides a chronological audit trail of workflow activity for all the nodes. - -It displays a table containing the following details: - -* Page name/Node with the Language variant. -* Type of Publish. -* Editor/Original author requesting the workflow. -* Date the workflow was requested on. -* Comment describing the changes. - -![Workflow history](../images/workflow-history-v14.png) - -You can also **Filter** the records based on the Document Type, Requested by, Created date, Completed date, Page Language, Workflow Type, and Workflow Status. - -![Workflow history Filters](../images/history-filter-v14.png) - -Additionally, you can adjust the total number of records displayed on a page. - -![Workflow history PageSize](../images/content-reviews-pagesize-v14.png) - -The **Detail** button at the end of the record displays an overlay with content similar to the [Active workflow](active-workflows.md) sub-section. - -![Details overlay](../getting-started/images/Workflow-Content-app-Details-overlay-v14.png) diff --git a/14/umbraco-workflow/workflow-section/workflow-section-dashboard.md b/14/umbraco-workflow/workflow-section/workflow-section-dashboard.md deleted file mode 100644 index ab298d114a9..00000000000 --- a/14/umbraco-workflow/workflow-section/workflow-section-dashboard.md +++ /dev/null @@ -1,5 +0,0 @@ -# Workflow Section - -The Workflow section provides an administrator view Workflow Dashboard. It displays a chart of recent workflow activity, chart of content review activity, licensing details, and any relevant upgrade-related messages. You can also view the workflow and content review activity chart for the specified range of days. - -![Workflow section](../images/Workflow-Admin-Dashboard-v14.png) diff --git a/14/umbraco-workflow/workflow-section/workflow-settings.md b/14/umbraco-workflow/workflow-section/workflow-settings.md deleted file mode 100644 index 0d8660b8407..00000000000 --- a/14/umbraco-workflow/workflow-section/workflow-settings.md +++ /dev/null @@ -1,235 +0,0 @@ -# Workflow Settings - -When working with Umbraco Workflow, you can handle the workflow settings directly in the Backoffice from the **Workflow** section. You can configure the following from the Workflow Settings section: - -* [General settings](workflow-settings.md#general-settings) -* [New node approval flow](workflow-settings.md#new-node-approval-flow) -* [Document Type approval flows](workflow-settings.md#document-type-approval-flows) -* [Exclude nodes](workflow-settings.md#exclude-nodes) -* [Notification Settings](workflow-settings.md#notifications-settings) -* [Email templates](workflow-settings.md#email-templates) - -![Workflow settings](../images/workflow-settings-v14.png) - -## General Settings - -You can configure the **General** Settings from the **Settings** menu in the **Workflow** section. The following settings are available: - -![General settings](../images/workflow-settings-v14.png) - -* **Flow type** - Determines the approval flow progress. These options manage how the Change Author is included in the workflow: - * **Explicit** - All steps of the workflow must be completed and all users will be notified of tasks (including the Change Author). - * **Implicit** - All steps where the original Change Author is _not_ a member of the group must be completed. Steps where the original Change Author is a member of the approving group will be completed automatically and noted in the workflow history as not required. - * **Exclude** - Similar to Explicit. All steps must be completed but the original Change Author is not included in the notifications or shown in the dashboard tasks. -* **Approval threshold** - Sets the global approval threshold to One, Most or All: - * **One** - Pending task requires approval from any member of the assigned approval group. This is the default behavior for all installations (trial and licensed). - * **Most** - Pending task requires an absolute majority of group members. For example, a group with three members requires two approvals and a group with four members requires three approvals. - * **All** - Pending task requires approval from all group members. -* **Rejection resets approvals** - When true, and the approval threshold is Most or All, rejecting a task resets the previous approvals for the workflow stage. -* **Allow configuring approval threshold** - Enables setting the approval threshold for any stage of a workflow (on a content node or Document Type). -* **Lock active content** - Determines how the content in a workflow should be managed. Set to `true` or `false` depending on whether the approval group responsible for the active workflow step should make modifications to the content. Content is locked after the first approval in the workflow - until then, the content can be edited as normal. -* **Administrators can edit** - Set to true to allow administrators to edit content at any stage of the workflow, ensuring flexibility and control over the content approval process. -* **Mandatory comments** - Set to true to require comments when approving workflows. Comments are always required when submitting changes for approval, and are always optional for admin users. -* **Allow attachments** - Provide an attachment (such as a supporting document or enable referencing a media item) when initiating a workflow. This feature is useful when a workflow requires supporting documentation. -* **Allow scheduling** - Provides an option to select a scheduled date when initiating a workflow. -* **Use workflow for unpublish** - Determines if unpublish actions require workflow approval. Set to true to display the **Action** option when submitting the content for approval. -* **Extend permissions** - Determines if Umbraco Workflow should extend or replace the users' save and publish permissions. The default behavior is to replace the users' permissions. - -### New node approval flow - -All new nodes use this workflow for initial publishing. You can add, edit, or remove an approval group to/from the workflow. - -To add an approval group to the workflow: - -1. Go to the **Workflow** section. -2. Go to the **General** tab in the **Settings** menu. -3. Click **Choose** in the **New node approval flow** section. - - ![New Node Approval Flow](../images/new-node-approval-flow-v14.png) - -4. Select an **approval group** to add to the workflow. - - ![Add Workflow Approval Groups](../images/add-approval-flow-v14.png) -5. Click **Submit**. -6. Click **Save**. - -When you click on the approval group, you are presented with different configuration options for that group. For more information on the approval group settings, see the [Settings](approval-groups.md#approval-groups-settings) section in the [Approval Groups](approval-groups.md) article. - -To remove an approval group, click **Remove**. - -### Document type approval flows - -Configure default workflows that should be applied to all content nodes of the selected Document Type. This feature requires a license. - -To add a Document type approval flow: - -1. Go to the **Workflow** section. -2. Go to the **General** tab in the **Settings** menu. -3. Click **Add document type** in the **Document type approval flows** section. - - ![Document Type Approval Flows](../images/doc-type-approval-flows-v14.png) -4. Select a **Document Type** from the drop-down list. -5. Select a **Language** from the drop-down list. -6. Click **Choose** in the **Approval groups**. -7. Click **Submit**. -8. Click **Add condition** to add a condition to the workflow process. - - ![Configure Document Type Approval Flow Settings](../images/add-doc-type-approval-flows-settings-v14.png) -9. Click **Submit**. -10. Click **Save**. - -To edit a Document type approval flow: - -1. Go to the **Workflow** section. -2. Go to the **General** tab in the **Settings** menu. -3. Click the content node in the **Document type approval flows** section. - - ![Edit Document Type Approval Flow](../images/edit-doc-type-approval-flows-v14.png) -4. **Add**, **Edit**, or **Remove** approval groups from the current workflow. -5. Click **Add condition** to add or edit a condition to the workflow process. - - ![Configure Document Type Approval Flow](../images/edit-doc-type-approval-flows-settings-v14.png) -6. Click **Submit**. -7. Click **Save**. - -### Exclude nodes - -Nodes and their descendants selected here are excluded from the workflow process and will be published as per the configured Umbraco user permissions. This feature requires a license. - -To exclude a node from the workflow process: - -1. Go to the **Workflow** section. -2. Go to the **General** tab in the **Settings** menu. -3. Click **Choose** in the **Exclude nodes** section. - - ![Exclude Nodes](../images/exclude-nodes-v14.png) -4. Select the **Content node** from the Content tree. - - ![Select Content Node](../images/select-content-from-tree-v14.png) -5. Click **Choose**. -6. Click **Save**. - -## Notifications Settings - -Umbraco Workflow uses Notifications to allow you to configure email notifications for all workflow activities for the backoffice. - -From the **Settings** view in the **Workflow** section, the **Notifications** tab provides access to the following: - -* **Send notifications:** If you wish to send email notifications to approval groups, you can enable it here. If your users are active in the backoffice, email notifications might not be required. -* **Workflow email:** Provide a sender address for email notifications. This is a mandatory field. -* **Reminder delay (days):** Set a delay in days for sending reminder emails for outstanding workflow processes. Set to 0 to disable reminder emails. -* **Edit site URL:** The URL for the editing environment (including schema - http[s]). This is a mandatory field. -* **Site URL:** The URL for the public website (including schema - http[s]). This is a mandatory field. -* [**Email templates**](workflow-settings.md#email-templates)**:** Configure which users receive emails for which workflow actions and modify the templates for those emails. - - ![Notifications tab in the Workflow Section](../images/Notifications-tab-v14.png) - -## Notifications Overview - -Notification emails use HTML templates which render information from the `HtmlEmailModel` type which lives in the `Umbraco.Workflow.Core.Models.Email` namespace. While it is possible to modify the email templates from the backoffice, we recommend making changes via an Integrated Development Environment (IDE) of your choice. - -The `HtmlEmailModel` contains the following fields: - -| Fields | Data Type | Description | -| ------------- | ------------------------- | ----------------------------------------------------------------------------------------------------------------- | -| WorkflowType | WorkflowType | An `enum` value containing either 1 or 2 for Publish and Unpublish respectively. | -| ScheduledDate | DateTime | If a scheduled date exists for the workflow, it is found here. | -| Summary | IHtmlString | A pre-generated representation of the current workflow state. | -| CurrentTask | WorkflowTaskViewModel | The view model data for the current workflow task. Contains a lot of useful data, best explored via Intellisense. | -| Instance | WorkflowInstanceViewModel | The view model data for the current workflow. Best explored via Intellisense. | - -The `HtmlEmailBase` contains the following fields: - -| Fields | Data Type | Description | -| ------------ | -------------- | ---------------------------------------------------------------------------------------------------- | -| SiteUrl | string | The public URL of your site. | -| NodeName | string | The name of the node from the current workflow. | -| Type | string | The workflow type including the scheduled date (if exists). | -| EmailType | EmailType | An `enum` value representing the current email type that relates directly to the workflow task type. | -| To | EmailUserModel | The model defining the receiver of the email. | -| Email | string | The user's email address or a group address (if a group email is being sent). | -| Name | Name | The user's name. | -| Language | string | The user's language. | -| Id | int | The user's ID or group ID (when sending to a group email address). | -| IsGroupEmail | bool | Is the email being sent to a generic group email address? | - -Umbraco Workflow provides **Settings** for determining who receives emails at which stages of a workflow. While these are set to default values during installation, it is recommended to update your Notifications Settings to better suit your installation needs. Emails can be sent to: - -* **All**: All the participants in all workflow stages (previous and current). -* **Admin**: The admin user. -* **Author**: The user who initiated the workflow. -* **Group**: All members of the group assigned to the current task. - -{% hint style="info" %} -Duplicate users are removed from email notifications. -{% endhint %} - -By default, all emails are sent to the **Group**. This might not always be an ideal situation. For example: cancelled workflows would be best sent to the **Author** only, likewise with rejected. - -It might be useful to notify **All** the participants of completed workflows but even this may be excessive. Depending on your website, you can adjust the best configuration. - -## Reminders Overview - -Umbraco Workflow uses a reminder email system to prompt editors to complete the pending workflows. Reminders are sent using Umbraco's internal task scheduler, every 24 hours after an initial delay. For example, setting the **Reminder delay (days)** value to 2 in the Workflow **Settings** section will allow pending workflows to sit for 2 days. After that reminder emails will be sent every 24 hours to all members of the group assigned to the pending workflow task. - -The emails use a similar model to the notification emails, also inheriting from `HtmlEmailBase`. In addition to the inherited fields, `HtmlReminderEmailModel` includes: - -| Fields | Data Type | Description | -| ------------ | --------- | --------------------------------------------------------------------- | -| OverdueTasks | IList | A list containing all the overdue tasks assigned to the current user. | -| TaskCount | int | The count of overdue tasks assigned to the current user. | - -## Email Templates - -All email templates are fully localized where translations exist. You can edit the email templates in the Backoffice or in your IDE. By default, Umbraco Workflow's email templates are available in the default language. - -## Creating an Email Template - -If you wish to have one or more email templates for different languages, you will need to place all the email templates into the `~/Views/Partials/workflow/email/` folder. - -To add templates for other languages: - -1. Go to the `~/Views/Partials/workflow/email` folder. -2. Copy the required template and paste it into the same folder. -3. Append the culture code to the file name prefixed with an underscore. - -For example: - -* **Default approval request template:** `~/Views/Partials/workflow/email/ApprovalRequest.cshtml` -* **Danish approval request template:** `~/Views/Partials/workflow/email/ApprovalRequest_da-DK.cshtml` - -## Sample Email Template - -Below is an example of the `ApprovalRequest.cshtml` email template from the `~/Views/Partials/workflow/email/` folder: - -```csharp -@model Umbraco.Workflow.Core.Models.Email.HtmlEmailModel - -@* - Refer to the documentation for Email templates for a full rundown on the available fields - or (better option), edit the template in Visual Studio where Intellisense will save you -*@ - - - - - - - Workflow: Approval request - - - - - -
-

Hello @Model.To.Name,

-

Please review the following page for @Model.Type.ToLower() approval:

- -
- - -```