From afd78a41334d00b09e8e9a3fe9ee0febcb851642 Mon Sep 17 00:00:00 2001 From: Andy Butland Date: Mon, 17 Mar 2025 14:46:54 +0100 Subject: [PATCH 1/3] Removed reference to ExecuteWorkflowAsync, removed in Forms 13 --- 14/umbraco-forms/developer/configuration/README.md | 5 ----- 15/umbraco-forms/developer/configuration/README.md | 5 ----- 2 files changed, 10 deletions(-) diff --git a/14/umbraco-forms/developer/configuration/README.md b/14/umbraco-forms/developer/configuration/README.md index e4a973279ba..af1326b65d2 100644 --- a/14/umbraco-forms/developer/configuration/README.md +++ b/14/umbraco-forms/developer/configuration/README.md @@ -77,7 +77,6 @@ For illustration purposes, the following structure represents the full set of op }, "Options": { "IgnoreWorkFlowsOnEdit": "True", - "ExecuteWorkflowAsync": "False", "AllowEditableFormSubmissions": false, "AppendQueryStringOnRedirectAfterFormSubmission": false, "CultureToUseWhenParsingDatesForBackOffice": "", @@ -339,10 +338,6 @@ Defines the default summary label for multi-page forms. 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`. -### ExecuteWorkflowAsync - -This configuration key is _experimental_ and will allow Workflows to be executed in an asynchronous manner. The value can be a `True` or `False` string value, or a comma-separated list of form names. Defaults to `False`. - ### 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`. diff --git a/15/umbraco-forms/developer/configuration/README.md b/15/umbraco-forms/developer/configuration/README.md index 1d925967aff..051fce82a91 100644 --- a/15/umbraco-forms/developer/configuration/README.md +++ b/15/umbraco-forms/developer/configuration/README.md @@ -76,7 +76,6 @@ For illustration purposes, the following structure represents the full set of op }, "Options": { "IgnoreWorkFlowsOnEdit": "True", - "ExecuteWorkflowAsync": "False", "AllowEditableFormSubmissions": false, "AppendQueryStringOnRedirectAfterFormSubmission": false, "CultureToUseWhenParsingDatesForBackOffice": "", @@ -335,10 +334,6 @@ Defines the default summary label for multi-page forms. 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`. -### ExecuteWorkflowAsync - -This configuration key is _experimental_ and will allow Workflows to be executed in an asynchronous manner. The value can be a `True` or `False` string value, or a comma-separated list of form names. Defaults to `False`. - ### 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`. From 7871112dfbc02771360e9c30ae32bb293af5363f Mon Sep 17 00:00:00 2001 From: Andy Butland Date: Mon, 17 Mar 2025 14:52:22 +0100 Subject: [PATCH 2/3] Documented AllowedUserNameCharacters on security settings --- 13/umbraco-cms/reference/configuration/securitysettings.md | 5 +++++ 14/umbraco-cms/reference/configuration/securitysettings.md | 5 +++++ 15/umbraco-cms/reference/configuration/securitysettings.md | 5 +++++ 3 files changed, 15 insertions(+) diff --git a/13/umbraco-cms/reference/configuration/securitysettings.md b/13/umbraco-cms/reference/configuration/securitysettings.md index 4f2bb1bd022..dcfa5ade40f 100644 --- a/13/umbraco-cms/reference/configuration/securitysettings.md +++ b/13/umbraco-cms/reference/configuration/securitysettings.md @@ -19,6 +19,7 @@ A full configuration with all default values can be seen here: "AuthCookieDomain": "", "UsernameIsEmail": true, "MemberRequireUniqueEmail": true, + "AllowedUserNameCharacters": "abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789-._@+\\", "UserPassword": { "RequiredLength": 10, "RequireNonLetterOrDigit": false, @@ -77,6 +78,10 @@ This setting specifies whether the username and email address are separate field By default Umbraco will not allow creation of more than one member account with the same email address. If you wish to allow this, set this value to `false`. +### Allowed user name characters + +Defines the allowed characters for a username. + ## User password settings This section lets you define the password rules for users. diff --git a/14/umbraco-cms/reference/configuration/securitysettings.md b/14/umbraco-cms/reference/configuration/securitysettings.md index 88d0f252e1d..f4523cb7346 100644 --- a/14/umbraco-cms/reference/configuration/securitysettings.md +++ b/14/umbraco-cms/reference/configuration/securitysettings.md @@ -18,6 +18,7 @@ A full configuration with all default values can be seen here: "AuthCookieName": "UMB_UCONTEXT", "AuthCookieDomain": "", "UsernameIsEmail": true, + "AllowedUserNameCharacters": "abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789-._@+\\", "UserPassword": { "RequiredLength": 10, "RequireNonLetterOrDigit": false, @@ -72,6 +73,10 @@ The authentication cookie which is set in the browser when a backoffice user log This setting specifies whether the username and email address are separate fields in the backoffice editor. When set to "false", you can specify an email address and username, only the username can be used to log on. When set to "true" (the default value) the username is hidden and always the same as the email address. +### Allowed user name characters + +Defines the allowed characters for a username. + ### User default lockout time Use this setting to configure how long time a User is locked out of the Umbraco backoffice when a lockout occurs. The setting accepts an integer which defines the lockout in minutes. diff --git a/15/umbraco-cms/reference/configuration/securitysettings.md b/15/umbraco-cms/reference/configuration/securitysettings.md index a976f72447e..0af7a3d405c 100644 --- a/15/umbraco-cms/reference/configuration/securitysettings.md +++ b/15/umbraco-cms/reference/configuration/securitysettings.md @@ -19,6 +19,7 @@ A full configuration with all default values can be seen here: "AuthCookieDomain": "", "UsernameIsEmail": true, "MemberRequireUniqueEmail": true, + "AllowedUserNameCharacters": "abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789-._@+\\", "UserPassword": { "RequiredLength": 10, "RequireNonLetterOrDigit": false, @@ -79,6 +80,10 @@ This setting specifies whether the username and email address are separate field By default Umbraco will not allow creation of more than one member account with the same email address. If you wish to allow this, set this value to `false`. +### Allowed user name characters + +Defines the allowed characters for a username. + ### User default lockout time Use this setting to configure how long time a User is locked out of the Umbraco backoffice when a lockout occurs. The setting accepts an integer which defines the lockout in minutes. From 70e186b7a70f25e9cb32f36f1b6d4b1c24a61ef8 Mon Sep 17 00:00:00 2001 From: Andy Butland Date: Mon, 17 Mar 2025 14:55:29 +0100 Subject: [PATCH 3/3] Update. --- 13/umbraco-forms/developer/configuration/README.md | 5 ----- 1 file changed, 5 deletions(-) diff --git a/13/umbraco-forms/developer/configuration/README.md b/13/umbraco-forms/developer/configuration/README.md index 3a797df736f..f7fdfa5dfa1 100644 --- a/13/umbraco-forms/developer/configuration/README.md +++ b/13/umbraco-forms/developer/configuration/README.md @@ -77,7 +77,6 @@ For illustration purposes, the following structure represents the full set of op }, "Options": { "IgnoreWorkFlowsOnEdit": "True", - "ExecuteWorkflowAsync": "False", "AllowEditableFormSubmissions": false, "AppendQueryStringOnRedirectAfterFormSubmission": false, "CultureToUseWhenParsingDatesForBackOffice": "", @@ -340,10 +339,6 @@ Defines the default summary label for multi-page forms. 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`. -### ExecuteWorkflowAsync - -This configuration key is _experimental_ and will allow Workflows to be executed in an asynchronous manner. The value can be a `True` or `False` string value, or a comma-separated list of form names. Defaults to `False`. - ### 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`.