Update steps and screenshots for Forms v14

14/umbraco-forms/developer/healthchecks/README.md

@@ -29,9 +29,9 @@ To run the health check:
 1.  Navigate to the **Health Check** dashboard in the **Settings** section in the Umbraco backoffice.
 
     <figure><img src="images/Umb-backoffice.png" alt=""><figcaption></figcaption></figure>
-2.  Click on the **Forms** button and select **Check Group**. You'll see a result that looks something like this: \\
+2.  Click on the **Forms** button and select **Perform checks**. You'll see a result that looks something like this:
 
-    <figure><img src="images/healthcheck.png" alt=""><figcaption></figcaption></figure>
+    <figure><img src="images/healthcheck-v14.png" alt=""><figcaption></figcaption></figure>
 
 If you have a full set of green ticks, then you're all good - and no need to read on!
 

14/umbraco-forms/developer/security.md

@@ -4,23 +4,24 @@ 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 _Users_ section of the backoffice, within a tree named _Form 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
+## User-based permissions
 
-Within the _Form Security_ tree, each user with a backoffice account is listed. Clicking on a user allows each functional permission to be set:
+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
-* _Manage datasources_ - user can create and edit datasource definitions
-* _Manage prevalue sources_ - user can create and edit prevalue source definitions
+* 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
+* 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
+## 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.
 
@@ -30,7 +31,7 @@ If a single start folder is selected, that will act as the root of the tree view
 
 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](../../../10/umbraco-forms/developer/images/user-start-folders.png)
+![Start folders](images/user-start-folders-v14.png)
 
 ## User group based permissions
 
@@ -59,7 +60,7 @@ Start folders are enabled for User Groups. They work in a similar way as the gro
 * 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
+### 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.
 

14/umbraco-forms/developer/webhooks.md

@@ -4,9 +4,9 @@ Umbraco Forms will register events for workflow operations that you can use with
 
 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** > **Webhooks** dashboard, you can configure webhooks to respond to workflows.
+On the Umbraco **Settings** > **Advanced** > **Webhooks** dashboard, you can configure webhooks to respond to workflows.
 
-![Webhook events](./images/wehbook-events.png)
+![Webhook events](images/wehbook-events-v14.png)
 
 You can amend the registration of workflow events in code.
 

14/umbraco-forms/editor/attaching-workflows/README.md

@@ -10,15 +10,15 @@ By default, when a Form is submitted the record data is stored in the database.
 
 The behaviour 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.png)
+![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.png)
+![Submit message/Go to page](images/MessageOnSubmitRichText-v14.png)
 
 ## Video Tutorial
 
@@ -30,17 +30,17 @@ Attaching Workflows to Umbraco Forms
 
 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.png)
+![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.png)
+![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.png)
+![Workflow add modal](images/WorkflowsAddModel-v14.png)
 
 ### Update Type-specific Settings
 

14/umbraco-forms/editor/attaching-workflows/workflow-types.md

@@ -16,13 +16,13 @@ Workflow Types in Umbraco Forms
 
 ## **Change Record State**
 
-![Change Record state](images/change-record-state.png)
+![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.png)
+![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:
 
@@ -36,7 +36,7 @@ Used to post the Form as an XML to a specified URL. The following configuration
 
 ## **Save as an XML file**
 
-![Save as XML](images/save-as-an-xml-file.png)
+![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:
 
@@ -53,7 +53,7 @@ When storing the files within the `wwwroot` or `App_Plugins` folders, the files
 
 ## **Save as Umbraco Content Node**
 
-![Save as content node](images/save-as-content-node.png)
+![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.
 
@@ -73,7 +73,7 @@ The following configuration can be set:
 
 ## **Send Email**
 
-![Send email](images/send-email.png)
+![Send email](images/send-email-v14.png)
 
 Sends the result of the Form to the specified email address. The following configuration can be set:
 
@@ -121,7 +121,7 @@ The fallback behavior also applies to the other email workflows.
 
 ## **Send Email with Template (Razor)**
 
-![Send email with template](images/send-email-razor.png)
+![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.
 
@@ -143,7 +143,7 @@ The following configuration can be set:
 
 ## **Send Form to URL**
 
-![Send to URL](images/send-to-URL.png)
+![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:
 
@@ -200,7 +200,7 @@ namespace RequestSaver.Controllers
 
 ## **Send XSLT Transformed Email**
 
-![Send XSLT Email](images/xslt-email.png)
+![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:
 
@@ -215,7 +215,7 @@ Sends the result of the Form to an email address with full control over the emai
 
 ## **Slack**
 
-![Send to Slack](images/email-slack.png)
+![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: