--- title: Creating Forms slug: portal-sub/creating-forms docTags: createdAt: 2026-03-04T12:03:14.886Z --- Forms are customizable, fully structured data entry tools. Unlike unstructured data, such as text entered into an Encounter, data entered into Forms can be queried and reported on. Their structured form can also enforce standard record keeping between users, ensuring consistency in the clinic or organization. We will use this Personality Questionnaire as an example to go through building a form: ::Image[]{src="https://api.qa.archbee.co/api/optimize/zICxj0dnLereb6UUrBA3-/37VqKN2xaNlgOpcOa-nuq_kfzswy2g3ir5xd0kuqywfptlhiyqhdx3ga.png" size="85" isUploading="false" initialPath="assets/kFZsWY2g3IR5Xd0kuQYWfPTLhIyQhDX3GA.png" githubPath="en/Forms/Forms - General/assets/kFZsWY2g3IR5Xd0kuQYWfPTLhIyQhDX3GA.png" position="flex-start" showCaption="false"} ## Electronic Use Planning Forms designed to be used on paper will often require reconsideration when being translated to an electronic system. Some things to consider: 1. Is everything on the form still necessary? Since the form will be a part of the patient record, some fields may be redundant to what is already stored in Profile. An exception would be if the form needs to be sent elsewhere, in which case personal details might be necessary. In our example above, the fields for Name, Date of Birth, and Address are already in the record, but we’ll leave Name and Date of Birth for identification when printed. 2. Will reporting be required for data entered into the form? Form elements can be designed to be reportable. See the next section on HRIs and Terms. 3. Since Profile’s forms have a defined structure, is everything on the original form possible? Some paper forms have very loose structure, and forms created in other electronic systems may have other functionality, such as repeatable sections, which are not possible in Profile. 4. Are there any calculations that could potentially be automated? Calculating scores, based on answered questions or other values, is possible with macros. Macros are programmed scripts that enable custom functionality. 5. Should the form enforce certain rules, such as mandatory fields? As with calculations, custom logic of how the form should function can be defined by macros. ## Health Record Items (HRIs) Creation and Linking to Terms The first step to creating forms is to create all of the necessary HRIs, which are used to store data. Every text field, checkbox, radio button, or other control that will save a value requires an HRI. HRIs are also linked to codes in the system, known as Terms. Generic terms, such as ‘Form Text’, can be used if reporting is not required, but where reporting is required, unique terms need to be created for every HRI. Ask your Intrahealth contact for more information about creating custom terms, if applicable. 1. Go to **Maintain/Templates/Forms.** 2. Select the folder on the left to categorize the form being created. New root folders or sub-folders can be created from the toolbar. 3. Either use the toolbar icon or right-click in the right side of the window to create a **New Collection**. ::Image[]{src="https://api.qa.archbee.co/api/optimize/zICxj0dnLereb6UUrBA3-/0MwxMScAYIZkosRt4_z6Y_nb6izxzwotbj-vaoztni4pkxa6fcjymgvg.png" size="87" isUploading="false" initialPath="assets/nb6IZXZwOtBJ-vaoZTNi4PkXA6fCjYMgVg.png" githubPath="en/Forms/Forms - General/assets/nb6IZXZwOtBJ-vaoZTNi4PkXA6fCjYMgVg.png" position="flex-start" showCaption="false" indent="2"} 4. The Term selection window will open. If a term has been created specifically for this form, locate it by selecting the Termset from the dropdown list (**intraHealth** in the screenshot) and use the **Search** field to find the appropriate term. For forms that don’t require reporting, the generic term **Clinical \** is generally used. ::Image[]{src="https://api.qa.archbee.co/api/optimize/zICxj0dnLereb6UUrBA3-/9FDwu36gZTe0Apbn-ttJV_cmh6vjx66djmrrfcod3b-zzrhnroqu2a.png" size="77" isUploading="false" initialPath="assets/CMh_6VJX66DJMRrfcOD3b-zZRHnRoqu2_A.png" githubPath="en/Forms/Forms - General/assets/CMh_6VJX66DJMRrfcOD3b-zZRHnRoqu2_A.png" position="flex-start" showCaption="false" indent="2"} 5. Double-click on the newly created Collection to modify it. Right-click on the Collection name from the new window to rename the Form, if necessary. 6. Going back to our Personality Questionnaire example, let’s start creating the HRIs. Click the dropdown arrow beside the **Create a new item** icon. For Name, we will select **Text**. ::Image[]{src="https://api.qa.archbee.co/api/optimize/zICxj0dnLereb6UUrBA3-/cF6h2jPEhJgGsv_wvOHSa_ygo9vyicgouz7th7yrksx143eqdcliwjw.png" size="34" isUploading="false" initialPath="assets/ygo9VyiCgOUz7_Th7yrKsX143EqDCliwJw.png" githubPath="en/Forms/Forms - General/assets/ygo9VyiCgOUz7_Th7yrKsX143EqDCliwJw.png" position="flex-start" showCaption="false" indent="2"} 7. As with creating the collection, the Term selection window will open. Since Name is a standard demographic, we’ll search for the **Patient full name \** Term in the **intraHealth** Termset. 8. For Date of Birth, create another HRI with the type **Date**. Search for the Term **Date of birth \** in the **intraHealth** Termset. 9. Continue creating HRIs and linking them to terms. Use the Item types **Quantity** for numeric values, or **Boolean** for checkboxes or other Yes/No controls. If custom Terms have been created, use them, otherwise generic form control Terms can be used, such as **Form Text \** (others shown in the screenshot, on the right), but rename the HRI to the control itself (See in screenshot, on the left). Use the list below for this example.Combining and using Quantity for the Activity Preferences will be explained later. - **Text** – Favourite Food, Dream Vacation, Cats or Dogs - **Boolean** - South America, Europe, Asia, Africa, Australia, Antarctica - **Quantity** – Hiking, Running, Cycling, Swimming ::Image[]{src="https://api.qa.archbee.co/api/optimize/zICxj0dnLereb6UUrBA3-/JwnviNwyK8X8ztbzZJI35_v03ppbr30jatqawkqjtdv504itmddq0ha.png" size="100" isUploading="false" initialPath="assets/V03PPBR30jAtqAwkQjtDv_504ItMddq0HA.png" githubPath="en/Forms/Forms - General/assets/V03PPBR30jAtqAwkQjtDv_504ItMddq0HA.png" position="flex-start" showCaption="false" indent="2"} ## Visual Layout Once all of the HRIs have been created, we can begin building the visual layout of the form. 1. Click the **Open form editor** icon on the form toolbar. TheForm window, Objector Inspector, and Control Palette will appear. ::Image[]{src="https://api.qa.archbee.co/api/optimize/zICxj0dnLereb6UUrBA3-/K8uMyw5Sa8J_onJPvrEb4_djjlux8nkldiisd9apcxelhciizce4izow.png" size="73" isUploading="false" initialPath="assets/dJjLux8nKLdiISd9APCxeLHcIizce4izOw.png" githubPath="en/Forms/Forms - General/assets/dJjLux8nKLdiISd9APCxeLHcIizce4izOw.png" position="flex-start" showCaption="false" indent="2"} 2. To use a defined paper size, select the form name, which appears at the top of the Object Inspector list, and scroll down to the **PaperName** property. Common formats, such as **Letter**, **Legal**, **A series**, etc., are available. Alternatively the **PaperName** can be left as **Undefined** and the size can be set in millimetres with the properties **PaperHeight** and **PaperWidth**. Commonly these properties will be left at default settings and the form window is adjusted visually to control the size. For this example, we will set the **PaperName** to **A5**. 3. With the Page selected in the Objector Inspector list, the property **Color** can be used to change the background colour. For this example, we’ll use the light grey colour. ## Form Background Image 1. If the form already has a defined format, such as a PDF document, then this can be used as a background image in the Form.Click the **Picture **icon on the **Control Palette **and then click in the form window to place the picture control. ::Image[]{src="https://api.qa.archbee.co/api/optimize/zICxj0dnLereb6UUrBA3-/ZaQnsOAbLVJjMiwZ715At_ktctb0fwh4l0wpnulmdov2b5znf7la4bq.png" size="77" isUploading="false" initialPath="assets/ktctb0Fwh4l0WPnUlMdOv2b5zNF7_La4bQ.png" githubPath="en/Forms/Forms - General/assets/ktctb0Fwh4l0WPnUlMdOv2b5zNF7_La4bQ.png" position="flex-start" showCaption="false" indent="2"} 2. Resize the image control to fill the form area. ::Image[]{src="https://api.qa.archbee.co/api/optimize/zICxj0dnLereb6UUrBA3-/OJPzRskqEMSkemFQn6s6o_zqp8yp7ro1ioazvqrdyxtqemf2evlnhhfq.png" size="100" isUploading="false" initialPath="assets/zqp8YP7ro1ioaZVqrdyxtqEmf2EVLNhhFQ.png" githubPath="en/Forms/Forms - General/assets/zqp8YP7ro1ioaZVqrdyxtqEmf2EVLNhhFQ.png" position="flex-start" showCaption="false" indent="2"} 3. Select the image file to use in the **Picture **property in the **Object Inspector**. Note that this must be an image file such as a **.jpg**, **.png**, of **.gif **file. There are free online tools to convert PDF documents to an image format. ::Image[]{src="https://api.qa.archbee.co/api/optimize/zICxj0dnLereb6UUrBA3-/HH2cJhWlLBXVqUYGuLvGU_sslaey7hjcv-2aoimom9kikfyxob6tbxq.png" size="50" isUploading="false" initialPath="assets/sSlAEy7Hjcv-2AoIMom9KIKFYxOB6TB_xQ.png" githubPath="en/Forms/Forms - General/assets/sSlAEy7Hjcv-2AoIMom9KIKFYxOB6TB_xQ.png" position="flex-start" showCaption="false" indent="2"} ## Form Control Creation and Modification 1. If there isn't a background image defining the field areas, you'll need to create Labels for all of the static text of the form, such as the title and all of the questions. Click the **Label** icon on the **Control Palette** and then click in the form window where the label is to be placed. ::Image[]{src="https://api.qa.archbee.co/api/optimize/zICxj0dnLereb6UUrBA3-/V6LfDyqNVHwut7EG2KJ9W_zuexz0r-c6zkkbpwagt40hpx9cacewqaq.png" size="30" isUploading="false" initialPath="assets/ZuExZ0r-_C6zkKbPwAGt40hpx9cAcEWQaQ.png" githubPath="en/Forms/Forms - General/assets/ZuExZ0r-_C6zkKbPwAGt40hpx9cAcEWQaQ.png" position="flex-start" showCaption="false" indent="2"} 2. With the newly created Label selected, use the properties **Caption** and **Font** in the Object Inspector to change the displayed text and font. ::::hint{type="info"} :::hint{type="success"} Hot Tip ::: If space permits, use a font size larger than the default of 8 for all controls, which can be difficult to read. Also, controls can be copied and pasted which can be quicker than creating each one from scratch. :::: 3. To align multiple controls, select them by clicking and dragging to draw a selection box or by shift-clicking individual controls, and then use the **Left** or **Top** properties to entera position in relation to either the left or top edge of the window. ::Image[]{src="https://api.qa.archbee.co/api/optimize/zICxj0dnLereb6UUrBA3-/z0MVw5ywfkCljs5VtkzpK_uguuwljcza6qlfy0buucqutnsqwaurabmq.png" size="100" isUploading="false" initialPath="assets/UGuUWlJcZa6qLFy0buUcqUTnSQWAurABmQ.png" githubPath="en/Forms/Forms - General/assets/UGuUWlJcZa6qLFy0buUcqUTnSQWAurABmQ.png" position="flex-start" showCaption="false" indent="2"} 4. For the single-line text fields, select **Edit Control** from the Control Palette and click in the form window to place the field. In this example, we’ll need Edit Controls for Name, Date of Birth, and Favourite Food. ::Image[]{src="https://api.qa.archbee.co/api/optimize/zICxj0dnLereb6UUrBA3-/OkOLJnVMEqOUGSB35c6oe_nxd267cjlrlsenbex4txapz9f-ttic3xg.png" size="30" isUploading="false" initialPath="assets/nxD267CJLRlSenBEX_4txaPz9f-Ttic3xg.png" githubPath="en/Forms/Forms - General/assets/nxD267CJLRlSenBEX_4txaPz9f-Ttic3xg.png" position="flex-start" showCaption="false" indent="2"} 5. For each of these controls, use the **HRI** property in the Object Inspector to link them to their respective HRIs created earlier. ::Image[]{src="https://api.qa.archbee.co/api/optimize/zICxj0dnLereb6UUrBA3-/om0534rPJ7yaSREjMx4Qw_wcgtww1fldk5ljpereig-ag80uf5hsyzvg.png" size="100" isUploading="false" initialPath="assets/wCgtWW1flDK5ljpereIG-aG80uF5HsYZVg.png" githubPath="en/Forms/Forms - General/assets/wCgtWW1flDK5ljpereIG-aG80uF5HsYZVg.png" position="flex-start" showCaption="false" indent="2"} 6. For fields that will be populated from data already entered in Profile, such as Name and Date of Birth in this example, use the property **PopulateValue** to open the Populate Value Property window. Check the **Auto Populate** checkbox and select the appropriate **Print Variable**. ::Image[]{src="https://api.qa.archbee.co/api/optimize/zICxj0dnLereb6UUrBA3-/PhHUGETKWAib_hLg7aO4O_rhl6k9eg7nkoidohp8-zviq6xzc0sp9dq.png" size="47" isUploading="false" initialPath="assets/RhL6k9eG7_NKOIDOHp8-zVIQ6Xzc0sp9dQ.png" githubPath="en/Forms/Forms - General/assets/RhL6k9eG7_NKOIDOHp8-zVIQ6Xzc0sp9dQ.png" position="flex-start" showCaption="false" indent="2"} 7. For the Date of Birth field, use the **EditKind** property to change the field from a standard free-text field to one that requires a Date format by selecting **ekdkDate**. 8. Edit Controls can be made to only display information rather than be editable by setting the property **ReadOnly** to **True**. :::hint{type="danger"} **Note** For this example, Name and Date of Birth have been created with HRIs and Edit Controls. If a control is being used only to display information and doesn’t require user input, it is generally better to use Labels rather than Edit Controls. Labels have the same PopulateValue property that can be used to pull data from Print Variables. Also, since the data from these controls don’t need to be stored with the form, they also don’t require HRIs. ::: 9. Select the **Multiple Line Text Editor** from the Control Palette to create the field for the Dream Vacation question, and then link it to its HRI in the Object Inspector. 10. Select the **Check Box** from the Control Palette to create the checkboxes for the Continents question. In the Object Inspector, link each one to its HRI and use the Caption property to enter the displayed text. ::Image[]{src="https://api.qa.archbee.co/api/optimize/zICxj0dnLereb6UUrBA3-/Kr41c5lvi6IFsrr9pZKnx_xrlta2irlulgxatpere3fsd-zcabqjz1g.png" size="75" isUploading="false" initialPath="assets/XRLTa2IrLulGXATPeRe3FSD-Z_CAbqjz1g.png" githubPath="en/Forms/Forms - General/assets/XRLTa2IrLulGXATPeRe3FSD-Z_CAbqjz1g.png" position="flex-start" showCaption="false" indent="2"} 11. Radio Buttons are used when only one selection is permitted. Create five buttons for the rating of Hiking. Since we don’t need the caption, we can resize the width of the control to hide it. ::Image[]{src="https://api.qa.archbee.co/api/optimize/zICxj0dnLereb6UUrBA3-/llfH84fC_Xq0lQwi6hRvO_m27vdt3xlmtpgx8vargcufixjnuczrjog.png" size="53" isUploading="false" initialPath="assets/m27VDt3XlMTpGX8VaRgCUfixjNuCzrJo_g.png" githubPath="en/Forms/Forms - General/assets/m27VDt3XlMTpGX8VaRgCUfixjNuCzrJo_g.png" position="flex-start" showCaption="false" indent="2"} 12. Select all five buttons and use the Object Inspector to set all of their HRIs together. Enter **Hiking** into the **Group** property so that they know that they are all related. :::hint{type="info"} **Hot Tip** By default, the property **CheckedValue** of each radio button is **True**. Rather than have five separate HRIs that each store whether or not each radio button is pressed, we can use only one HRI, and have each Radio Button store a different value when it is pressed. ::: 13. One by one, set the **CheckedValue** of each button to their corresponding 1-5 score. 14. Copy and Paste the Hiking Radio Buttons and modify the **HRI** and **Group** for Running, Cycling, and Swimming. 15. The final question in the example about Cats and Dogs was initially designed using checkboxes, but let’s use a **Combo Box** from the Control Palette instead. 16. Use the **Items** property in the Object Inspector to enter the available selections for the dropdown list. Put each option on its own line. ::Image[]{src="https://api.qa.archbee.co/api/optimize/zICxj0dnLereb6UUrBA3-/fkMN75Z-HpMvmbXUXC2Ek_ixndpwav5cf31cdhdyidzssel7fwmyj5ba.png" size="46" isUploading="false" initialPath="assets/IXNDPwaV5cf31cdHdyiDzSSel7fWMYJ5bA.png" githubPath="en/Forms/Forms - General/assets/IXNDPwaV5cf31cdHdyiDzSSel7fWMYJ5bA.png" position="flex-start" showCaption="false" indent="2"} 17. Finally, let’s add a **Button** to this form for printing. Printing can always be done through **File/Print** but it can be easier to have a button on the form itself. Resize it to make it larger and change the **Caption** property to **Print**. We will add the macro to make it work in the next section. ## Macros 1. ## The Macro Editor window can be accessed from the Form data window toolbar.![](https://api.qa.archbee.co/api/optimize/zICxj0dnLereb6UUrBA3-/ablvo4pcAYBpS8cP64GN6_ga-oj2hk-jxp7tulca4hb0ywjxj1iliba.png) 2. Use the toolbar icons to create and save macros, or use the **Macro Name** dropdown list to open existing macros. ::Image[]{src="https://api.qa.archbee.co/api/optimize/zICxj0dnLereb6UUrBA3-/K35BmJISC_eBkceR054Jf_hcylwlgprqlmfsaw1l-gfat6xfrjynyg.png" size="100" isUploading="false" initialPath="assets/HcYL_wlGpRQlMFSaW1l-gFAt6_XfrJYnyg.png" githubPath="en/Forms/Forms - General/assets/HcYL_wlGpRQlMFSaW1l-gFAt6_XfrJYnyg.png" position="flex-start" showCaption="false" indent="2"} 3. To link the macro to an event, use the Object Inspector to select the appropriate item and select the macro from the appropriate event in the **Events** tab. With different objects selected, different events will be available. For example, by selecting the form itself at the top of the Object Inspector, many Form Events can be used, such as when the form is opened, closed, or saved. ::Image[]{src="https://api.qa.archbee.co/api/optimize/zICxj0dnLereb6UUrBA3-/7FXnwPjpCsTsYEIWj1PRq_yxidxlbuc2s-q1kr96j0qlhbnnijo-tg.png" size="45" isUploading="false" initialPath="assets/yXiDXLBUC2s-q1_kr96J_0QLHBNNijo-Tg.png" githubPath="en/Forms/Forms - General/assets/yXiDXLBUC2s-q1_kr96J_0QLHBNNijo-Tg.png" position="flex-start" showCaption="false" indent="2"} ## Example Macros | **Description** | **Example Macro Script** | | ------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Mandatory Field** - Prevent the user from saving the form if this field is empty. | **Form Event - OnMValidateSave**
```vb if Form.Controls_("EditMandatoryField").Value = "" then Profile.Variable("CanSave").Value = False Profile.Variable("ErrorMessage").Value = "Please enter a value into the Mandatory field." end if ``` | | **Conditional Mandatory Field** - Prevent the user from saving the form if this field is empty when another control has a particular value. | **Form Event - OnMValidateSave**
```vb if Form.Controls_("ComboBoxYesNo").TextValue = "Yes" and Form.Controls_("EditConditionalMandatoryField").AsVariant = "" then Profile.Variable("CanSave").Value = False Profile.Variable("ErrorMessage").Value = "Please enter a value into the Conditional Mandatory field." end if ``` | | **Field Format Validation** - Prevent the user from saving the form if its value isn't in the expected format. | **Form Event - OnMValidateSave**
```vb editFiveDigitsValue = Form.Controls_("EditFiveDigits").Value if not IsNumeric(editFiveDigitsValue) or not Len(editFiveDigitsValue) = 5 then Profile.Variable("CanSave").Value = False Profile.Variable("ErrorMessage").Value = "Please enter a five digit number into the Five Digits field." end if ``` | | **Conditional Disabled Field** - Prevent the user from using the field unless another control has a particular value. | **Condition Control Event (e.g. on Yes and No Radio Buttons ) - OnMClick**
```vb if Form.Controls_("YesRadioButton").Checked then Form.Controls_("EditConditionalDisabled").Enabled = true Form.Controls_("CheckboxConditionalDisabled").Enabled = true else Form.Controls_("EditConditionalDisabled").Enabled = false Form.Controls_("CheckboxConditionalDisabled").Enabled = false end if ``` | ## Final Touches With all of the controls laid, we can make some final touches before finishing the form. 1. Firstly, the A5 size that we chose before ended up being too large, so set a custom size by selecting the form name at the top of the Object Inspector list again, and changing the **PaperHeight** and **PaperWidth** to values that decrease the margin. ::Image[]{src="https://api.qa.archbee.co/api/optimize/zICxj0dnLereb6UUrBA3-/xGpfM9dd8_hkCBw1-Xeyn_absni0veedhywvb6ni8pr1w7obvnnmjabg.png" size="100" isUploading="false" initialPath="assets/aBSnI0VeedHYWvb6ni8Pr1w7obvnNmjabg.png" githubPath="en/Forms/Forms - General/assets/aBSnI0VeedHYWvb6ni8Pr1w7obvnNmjabg.png" position="flex-start" showCaption="false" indent="2"} 2. It is strongly recommended that you use a form once and review it, and if it is to be printed, print it, to confirm that all fields are working as expected, and that there are no obvious font or other alignment issues. Forms often need to be adjusted a few times before they are working as intended. 3. You will be prompted to save the form when the window is closed. You can also save without closing through **File/Save**. 4. **Tab Order** is the order in which Profile will cycle through all of the controls on the form when the \[**Tab**] key is hit. By default, this is in the order that the controls have been created, but it can be fixed if they are not in the correct order. Right-click in the form area and select **Tab Order**. Profile will display in red font the controls that it guesses are out of order. Select an item and use the arrows to re-order the list. ::Image[]{src="https://api.qa.archbee.co/api/optimize/zICxj0dnLereb6UUrBA3-/GEqLbWeXn2t8PDLdZN2kg_blkd1ajdf1x09i0uaj5jzemhf7ewnh5iw.png" size="54" isUploading="false" initialPath="assets/BLkd1Ajdf1X09i0UAj5jZEmHf7ewN_h5iw.png" githubPath="en/Forms/Forms - General/assets/BLkd1Ajdf1X09i0UAj5jZEmHf7ewN_h5iw.png" position="flex-start" showCaption="false" indent="2"} ## Form Access and Use 1. As part of a New Encounter, go to the **Forms** view of the **Actions** panel and press the **Browse** button on the right. Locate the form in the selection window. ::Image[]{src="https://api.qa.archbee.co/api/optimize/zICxj0dnLereb6UUrBA3-/MCAp__gi9cpWnmhzaoeR8_r0zyw4kwuhavxncajjbuuyhxljzglo4jua.png" size="100" isUploading="false" initialPath="assets/R0ZYw4kwuHavxnCAJJBuuyHxlJzglo4JuA.png" githubPath="en/Forms/Forms - General/assets/R0ZYw4kwuHavxnCAJJBuuyHxlJzglo4JuA.png" position="flex-start" showCaption="false" indent="2"} 2. The form will open in a separate window. Complete the form and close the window, at which point you will be prompted to save the form. **File/Save** and **File/Print** are available, or dedicated buttons on the form can be used depending on the form design. 3. Forms can be reviewed, continued, or modified from the **Forms** view of the Patient record. ::Image[]{src="https://api.qa.archbee.co/api/optimize/zICxj0dnLereb6UUrBA3-/GtYrm9MWDcy7cUCv6mHd2_helg3yyhyfpumv4o2fktkkmvyj-mxyb2-a.png" size="98" isUploading="false" initialPath="assets/helG3yyhYfPUMV4o2fkTkKmVyj-MxYb2-A.png" githubPath="en/Forms/Forms - General/assets/helG3yyhYfPUMV4o2fkTkKmVyj-MxYb2-A.png" position="flex-start" showCaption="false" indent="2"} *** ## Attachments ::File{src="https://api.qa.archbee.co/api/presign/zICxj0dnLereb6UUrBA3-/V-nYPPQ-KOgoMycrS6Agh_6000237259-creating-forms.pdf" label="Creating Forms.pdf" initialPath="../../../attachments-export/6000237259-Creating%20Forms.pdf" githubPath="attachments-export/6000237259-Creating Forms.pdf"}