This article describes the function and use of custom Url fields within the Customs Editor. To store and place clickable links that are unique to specific projects, use Url fields or Url List fields. If you require a set link to a certain webpage, use Link Buttons. To learn how to add custom fields, including Url fields, read the article on using the Customs Editor.
The Customs Editor is an Advanced tool and requires Org Admin privileges.
Using Url Fields
Url fields store plain text that are interpreted as clickable links. They accept characters, numbers, and some symbols indiscriminately, meaning that users should be careful to ensure that the link is entered correctly. Url fields are used when you need to include a unique link to another webpage within a project. These fields might be used to link to insurance forms, personal websites, or research evidence.
A single Url field creates a clickable link that is editable at any time with the project, while a Url List creates a list of clickable links.
Url fields can be converted to a case number field or any text field. Url Lists, however, cannot be converted to anything else once created. Url fields and Url List fields cannot be converted to one another.
Url List fields have very limited reporting criteria, which makes Url List fields best suited for storing multiple Urls that you plan on using infrequently, and that you don’t need to use for reporting.
Url fields include several options for reporting criteria. Reports can be limited by whether the Url field is empty, what each Url contains, and whether Urls have all, any, or none of a list of values. Below is the exact breakdown of reporting criteria for Url fields and Url List fields.
|Url||Contains, Does Not Contain|
is empty is No, Yes
Url List Field
|Url||is Empty, Not Empty|
|Url List||has all of (list) List of Values|
|Url List||has any of (list) List of Values|
|Url List||has none of (list) List of Values|
|Url List||is, contains|