The URL field allows you to store hyperlinks in GraceBlocks. Use the URL field to store website addresses that you want users to be able to easily click to support easy navigational access. To store a URL, a builder must choose the URL field type when managing fields.
This article reviews the properties of URL fields and provides tips to aid in user adoption of this type of field.
You can view the available properties for email fields on the Edit field properties modal when you select Field type of URL.
Properties of URL fields
After specifying a Field name (which controls how this field is referenced inside the tab) and that the field is of the type URL, you can toggle on More field attributes to show the options below. Complete the transaction at the end but clicking Save.
If every row should have a URL value by default as soon as a record is created, specify it here. The value can be changed by users to another URL value, but setting a default can help to minimize having null value records. In some cases, that is relevant.
If you enter any text into the Field callout textbox, the information (i) icon appears to the left of the field name, and the text you entered displays when users move the cursor over this icon. Enter text here if you want to provide information to help the user learn more about how to use the field.
🔔 URL fields have validation. This means that if you enter a value that is not recognized as a URL, it cannot be stored in the field. Invalid entries display in red when they occur and will disappear on a refresh of the page because the data is not stored.
|Visual illustrating invalid URLs||Notes|
|\||In this example, there are three formats that GraceBlocks will accept as a URL. If the value is accepted, the cell appears as a clickable blue hyperlink, and clicking the value launches the URL in a new browser tab. Invalid URLs are shown in red.|
🔔 If a data-conversion impact can occur during a field type change to or from a URL field, a warning message accompanies the field-conversion process to ensure that the builder understands what to expect. It's important to read these messages carefully. Users must follow the instructions provided on the warning page to complete field change transactions.