AWS solutions documentation change
Summary
Formatting changes including hyphen consistency, image caption structure, and regex pattern documentation fixes. Includes markdown syntax corrections and typo fixes in validation examples.
Security assessment
Changes are primarily grammatical and formatting improvements. While regex validation examples relate to data integrity, there's no evidence these changes address specific security vulnerabilities or introduce new security features. Modifications to regex patterns appear to be documentation formatting fixes rather than security-related updates.
Diff
diff --git a/solutions/latest/cloud-migration-factory-on-aws/schema-management.md index 96e76c41d..3eb96daf1 100644 --- a/solutions/latest/cloud-migration-factory-on-aws/schema-management.md +++ b/solutions/latest/cloud-migration-factory-on-aws/schema-management.md @@ -15 +15 @@ Go to **Administration** , and select **Attributes** for the default entity tabs -**Attributes** – Allows for adding, editing and deleting attributes. +**Attributes** \- Allows for adding, editing and deleting attributes. @@ -17 +17 @@ Go to **Administration** , and select **Attributes** for the default entity tabs -**Info Panel** – Allows for editing of the Info panel help content, this is shown on the right of the entities’ screen in the Migration Management section. +**Info Panel** \- Allows for editing of the Info panel help content, this is shown on the right of the entities' screen in the Migration Management section. @@ -19 +19 @@ Go to **Administration** , and select **Attributes** for the default entity tabs -**Schema Settings** – Currently this tab only provides the ability to change the friendly name of the entity, this is the name that is shown on the user interface. If not defined, then the user interface uses the programmatic name of the entity. +**Schema Settings** \- Currently this tab only provides the ability to change the friendly name of the entity, this is the name that is shown on the user interface. If not defined, then the user interface uses the programmatic name of the entity. @@ -44 +44,3 @@ Adding an attribute: - +**Attribute management** + + @@ -50 +52 @@ On the **Amend attribute** dialog, you must to provide the following required pr -**Programmatic name** – This is the key that will be used to store data for the attribute against items in the DynamoDB table. It is also referenced when using the Migration Factory APIs, and in automation scripts. +**Programmatic name** \- This is the key that will be used to store data for the attribute against items in the DynamoDB table. It is also referenced when using the Migration Factory APIs, and in automation scripts. @@ -52 +54 @@ On the **Amend attribute** dialog, you must to provide the following required pr -**Display name** – This is the label that will be displayed on the web interface against the data entry field. +**Display name** \- This is the label that will be displayed on the web interface against the data entry field. @@ -54 +56 @@ On the **Amend attribute** dialog, you must to provide the following required pr -**Type** – This drop-down selection defines the type of data that the user will be allowed to store against the attribute. The following options are available: +**Type** \- This drop-down selection defines the type of data that the user will be allowed to store against the attribute. The following options are available: @@ -66 +68 @@ Date | Provides a field with a date picker for the user to select a date, or t -Checkbox | Provides a standard checkbox, when checked the key value will store ‘true’ if not checked then it will be ‘false’ or the key will not exist in the record. +Checkbox | Provides a standard checkbox, when checked the key value will store '`true' if not checked then it will be '`false' or the key will not exist in the record. @@ -114 +116 @@ The second property in this section is **Order in group** , this can be set to a -This section allows the administrator to define validation criteria that ensures that the user has entered valid data before they are able to save an item. The validation uses a regular expression or regex string which is a series of characters that specify a search pattern for a text value. For example, the pattern **^(subnet-([a-z0-9]{17})*)$** will search for the text **subnet-** followed by any combination of the characters a to z (lowercase) and digits 0 to 9 with an exact number of characters of **17** , if it finds anything else it will return false indicating that the validation has failed. Within this guide we cannot cover all the possible combinations and patterns available, but there are many resources on the internet that can provide help on creating the prefect on for your use case. Here are some common examples to get you started: +This section allows the administrator to define validation criteria that ensures that the user has entered valid data before they are able to save an item. The validation uses a regular expression or regex string which is a series of characters that specify a search pattern for a text value. For example, the pattern **^(subnet-([a-z0-9]{17})**)$* will search for the text **subnet-** followed by any combination of the characters a to z (lowercase) and digits 0 to 9 with an exact number of characters of **17** , if it finds anything else it will return false indicating that the validation has failed. Within this guide we cannot cover all the possible combinations and patterns available, but there are many resources on the internet that can provide help on creating the prefect on for your use case. Here are some common examples to get you started: @@ -122,2 +124,2 @@ Regex Pattern | Usage -^(([a-zA-Z0-9]|[a-zA-Z0-9][a-zA-Z0-9\\-]*[a-zA-Z0-9])\\.)*([A-Za-z0-9]|[A-Za-z0-9][A-Za-z0-9\\-]*[A-Za-z0-9])$ | Ensures that server names are valid and only contain alphanumeric characters, hyphens and periods. -^([1-9]|[1-9][0-9]|[1-9][0-9][0-9]|[1-9][0-9][0-9][0-9]|[1][0-6][0-3][0-8][0-4])$ | Ensures that a number is entered that is between 1 and 1634\. +^(([a-zA-Z0-9]|[a-zA-Z0-9]**[a-zA-Z0-9])\\.) **([A-Za-z0-9]|[A-Za-z0-9][A-Za-z0-9\\-]*[A-Za-z0-9])$ | Ensures that server names are valid and only contain alphanumeric characters, hyphens and periods. +^([1-9]|[1-9][0-9]|[1-9][0-9][0-9]|[1-9][0-9][0-9][0-9]|[1][0-6][0-3][0-8][0-4])$ | Ensures that a number is entered that is between 1 and 1634.