Skip to main content

Inquiry submission

At a high level, the Inquiry Submission feature creates a form on the component which, when submitted, creates an Inbound Form record in the connected Salesforce org. Inbound Forms are then automatically processed in Medical Information Cloud to create corresponding Interaction and Request records. Visit Inbound Forms for more details.

Submitting a medical inquiry

Once configured on your organization's website, the users will able to see the component and click to expand it, revealing the inquiry submission form. The user can then input the following information:

  • Requester Name

  • Email

  • Phone Number (optional)

  • Inquiry Text

Note

The fields above are configurable using the Inbound Form Fields (mvn__MED_Inquiry_Submission_FIelds__c) custom field in the Engagement Component Configuration (mvn__MED_Engagement_Component_Settings__mdt) custom metadata type.

Once all required fields are complete, the user will click Submit, thereby creating an Inbound Form record. The record is then sent to the connected Salesforce Org where it will be routed to the Medical Information team.

Supported field types

The Engagement Web Component component supports a subset of available Salesforce Data Types. See the table below for details about supported types and corresponding details.

  • Component Input Type: How the type is displayed in the component.

  • Field Data Types: Salesforce setup UI Data Type equivalent.

  • Default Value: Default value displayed in the component form field unless otherwise specified.

  • Form Validation Rules: Validation rules are applied to the field type when a user attempts to submit the form.

  • Default Value Override JSON Format: Accepted JSON value types to set field default values directly from component configuration attribute type.

    Note

    Validation rules only apply to fields displayed on the form at the time of submission except for picklist values.

Table 141. Component types

Field data types

Component input type

Default value

Form validation rules

Default value override JSON format

Checkbox

Checkbox

Unchecked

None

Boolean or string value

Example:

true, false, or "True" (as a case-insensitive string)

Email

Phone

Text

Text

Empty

Max Length

Email Regex:

/^[^@\s><)()[\];:\\]*@[A-Z0-9.-]+\.[A-Z0-9.-]{1,}$/i

String value

Example:

"My Text Value"

Text Area

Text Area (Long)

Text Area (Rich)

Text Area

Empty

Max Length

String value

Example:

"My Test Area Value"

Currency

Number

Percent

Number

Empty

(Length - Decimal Places). (Decimal Places)

Number or string representation of a number

Example:

1.23 or "1.23"

Date

Date Picker

Current Date

None

Iso 8601 valid string

Example:

"2023-08-22"

Date/Time

Date Time Picker

Current Date / Time

None

Iso 8601 valid string

Example:

"2023-08-22T16:00:00.000Z"

Time

Time Picker

Current Time

None

Iso 8601 valid string

Example:

"01:00.000Z"

Picklist

Picklist

Picklist Default Value or None

Value Exists in Defined Values

String of a valid picklist value (case-insensitive)

Example:

"Email" or "email"

Picklist (Multi-Select)

Picklist with multi-select

Picklist Default Value or None

Value Exists in Defined Values

String of a valid picklist value (case-insensitive)

Example:

"Email" or "email"



Note

Dependent picklists are supported. If used, both the controlling and dependent fields should be included on the form, otherwise, the dependent field will not be displayed.

Special fields

Certain Inbound Form fields in the Inbound Form (MED_Inbound_Form__c) custom object have automatically set default values or are otherwise handled in special ways.

For example:

  • MED_Product__c: This field is defined as a String data type but is handled as a picklist in the component user interface. The available and default values are controlled by the mvn__MED_Available_Product_IDs__c and mvn__MED_Default_Product_ID__c.

  • Fields with automatic default values: These fields will have default values applied and will be sent with inquiry submissions regardless of whether they are displayed on the form.

    • MED_Country__c: Automatically set to the mvn__MED_Country_Code__c value from the custom metadata type.

    • MED_Language__c: Automatically set to browser-detected language (if a valid picklist value) or mvn__MED_Default_Language__c from custom metadata type.

    • MED_Channel__c: Automatically set to the mvn__MED_Inquiry_Channel__c value from the custom metadata type.

  • Fields with automatic values that cannot be overridden and should not be added to the form UI: These fields will have default values applied and will be sent with inquiry submissions. Do not add them to the form directly, as their values will always be overridden.

    • MED_External_ID__c: Automatically set to the mvn__MED_Inquiry_External_ID_Prefix__c value from the custom metadata type and a random UUID.

    • MED_Date_Submitted__c: Automatically set to the date when the submit button is clicked on the form.

    • MED_Datetime_Submitted__c: Automatically set to the date/time when the submit button is clicked on the form.