User guide · Chapter 18

Native Screen Flow Components

These components will ship in an upcoming Native Rent package version.

Overview

Native Rent includes four screen components for Flow Builder. Use them to present choices, search for a record, or move the flow on after a delay.

ComponentAPI nameUse it for
NC Buttons & Tilesnativerent:ncButtonsVisual choices: icon tiles, image cards, list rows, button rows, small buttons, or a dropdown.
NC Picklistnativerent:ncPicklistForm-style choice fields: a dropdown, a radio or checkbox list, or buttons, including small buttons.
NC Lookupnativerent:ncLookupType-ahead search for one record.
NC Timernativerent:ncTimerMoving the flow on automatically after a delay. A hidden mode can run the timer with nothing visible on the screen.

The labels in the Component column are the metadata MasterLabel values. In Flow Builder, search for NC Buttons & Tiles, NC Picklist, NC Lookup, or NC Timer in the Custom components list.

Each component has its own setup panel, with help text and a live preview of the component with your settings. Flow resources are filled in when the flow runs, so the preview cannot show them. For NC Lookup, the preview appears once you set an object or a record collection. With a record collection, the preview stays empty, because the records are loaded when the flow runs. The NC Timer preview never moves the flow on.

The Basic section holds the settings most screens need:

Advanced sections start collapsed. Open them for the rest of the properties.

A Style fills only the settings you leave blank. You can still change each one under Advanced. Leave Style blank, or choose Custom, to keep the original defaults.

The property tables in this chapter are grouped by topic for reading. They are not the same as the Basic and Advanced sections in the setup panel. For words that cover more than one setting, see Terms used in this chapter.

All four components:

Which component to use

You wantUse
A few options shown as large, tappable choices, with icons or imagesNC Buttons & Tiles
Compact icon-only or short-label buttons, with the full label as a tooltipNC Buttons & Tiles (Style Small buttons, or Layout iconbuttons) or NC Picklist (Layout iconbuttons)
A normal form field that looks like the other fields on the screenNC Picklist
A choice of one record from many, searched by typingNC Lookup
A choice of records you already have in the flowNC Buttons & Tiles or NC Picklist, with Data Source set to records. For larger collections, use NC Lookup with Data Source set to records.
A confirmation screen that continues by itself, or a timed "thank you" screenNC Timer
An action that runs after a delay, with nothing visible on the screenNC Timer, with Layout hidden, or with the Silent timer style

NC Buttons & Tiles

NC Buttons & Tiles shows options as tiles, cards, list rows, buttons, small buttons, or a dropdown. People can pick one option or several. Choices can come from typed text, a text collection, a record collection, a picklist field, or a query.

Use it when the choice should be easy to tap and when icons or images help, for example a plan, add-ons, or a size.

NC Buttons & Tiles on desktop: icon tiles with multi select, a maximum of 2 choices, and a compact 4-column single-select row.
NC Buttons & Tiles on desktop: icon tiles with multi select, a maximum of 2 choices, and a compact 4-column single-select row.
NC Buttons & Tiles with Layout set to Auto on a phone: icon tiles become list rows, short labels become one button row, and image choices become 2-column cards.
NC Buttons & Tiles with Layout set to Auto on a phone: icon tiles become list rows, short labels become one button row, and image choices become 2-column cards.

Add it to a screen

Flow Builder setup panel for NC Buttons & Tiles: the Basic section, Style presets, and help text.
Flow Builder setup panel for NC Buttons & Tiles: the Basic section, Style presets, and help text.
  1. Open the flow in Flow Builder and add or open a Screen element.
  2. Add NC Buttons & Tiles. The setup panel opens.
  3. In Basic, choose a Style if you want one: Big buttons, Icon tiles, Cards, or Small buttons. A style fills only the settings you leave blank. Leave Style blank, or choose Custom, to keep the original defaults.
  4. Set Label. Choose where the choices come from. Turn on Required if the user must pick a value.
  5. A live preview shows the component with your settings.
  6. Leave Data Source set to auto, and the component uses whichever of the following you fill in:
SourceFill inExample
textChoices, and optionally Choice Values, Choice Descriptions, Choice Icons, and Choice Image URLs, all comma-separated in the same orderSmall,Medium,Large. Write \, for a comma inside a label.
collectionChoice Labels (Collection), and optionally the matching Values and Descriptions collectionsA Text collection built with an Assignment or a Loop.
recordsRecords (a record collection from Get Records), plus Record Label Field, Record Value Field, and Record Description Field. First set Record Object.Rentables from a Get Records element.
picklistObject API Name and Picklist Field API Name. Optionally Record Type Id and Controlling Field Value for a dependent picklist.Account / Industry
queryObject API Name, and optionally Filter Field, Filter Operator, and Filter Value (two filters, joined with AND), Order By Field, Sort Direction, and Maximum Record Choices (default 200)A Rentable object, with Filter Field Status__c equal to Available.
  1. Set Selection Mode to single or multi. Optional: Minimum Selections, Maximum Selections, and Default Value.
  2. Leave Layout set to auto, or pick tiles, cards, list, buttons, dropdown, or iconbuttons (Small buttons). Auto uses cards when there are images or descriptions, tiles when there are icons, buttons for up to 5 short labels, a dropdown for more than 12 single-select choices that have no images, and list rows or cards on phones and in a narrow column. On a phone, Auto does not use tiles. Auto never picks Small buttons. Small buttons show an icon or a short label, and the full label as a tooltip. You can also set Columns (Desktop) (0 means automatic, up to 6), Columns (Phone) (1 or 2), and Image Shape.
  3. Open Advanced for selection details, colors, navigation, and the other properties.
  4. Under Store Output Values, map Value (the selected value), Values (Collection), and Selected Label. For record sources, also map Selected Record or Selected Records. Map the same Value variable in and out to keep the choice when the user goes back.

Properties

PropertyAPI nameDefaultDescription
StylestylePresetOptional. A style fills only the settings you leave blank. You can still change each one under Advanced. Leave it blank, or choose Custom, to keep the original defaults.
buttons (Big buttons): Layout buttons, Text Size large.
icons (Icon tiles): Layout tiles, Color Map Style stripe, and, with a query source, the object's icon on choices that have no icon of their own.
cards (Cards): Layout cards, Image Shape landscape, Color Map Style stripe, and, with a records or query source, one detail field as the second line.
smallbuttons (Small buttons): Layout iconbuttons.
LabellabelQuestion or field label shown above the component.
Help TexthelpTextOptional hint shown under the label, for example Pick the plan that fits your team.
Data SourcesourceautoWhere the choices come from: auto, text, collection, records, picklist, or query. With auto, the component uses the first of these that you filled in:
1. records: Records is set.
2. collection: Choice Labels (Collection) has values.
3. picklist: Object API Name and Picklist Field API Name are set.
4. query: only Object API Name is set.
5. text: Choices.
Example: if you fill in Records and Choices, Records wins. Set Data Source to text to use Choices.
ChoiceschoiceLabelsText source: comma-separated labels. Use \, for a comma inside a label.
Choice ValueschoiceValuesText source, optional: comma-separated values in the same order. A blank entry uses the label.
Choice DescriptionschoiceDescriptionsText source, optional: comma-separated second lines in the same order.
Choice IconschoiceIconsText source, optional: comma-separated SLDS icon names, for example utility:home,utility:company.
Choice Image URLschoiceImagesText source, optional: one image per choice, separated by commas, in the same order as Choices, for example /resource/PlanImages/starter.png,/resource/PlanImages/team.png. Only https:// links or same-org paths (/resource/..., /sfc/...). http:// links are not shown.
Choice Labels (Collection)choiceLabelsCollectionCollection source: a Text collection variable.
Choice Values (Collection)choiceValuesCollectionCollection source, optional: values in the same order as the labels.
Choice Descriptions (Collection)choiceDescriptionsCollectionCollection source, optional: second lines in the same order.
Record ObjectNone (object type)Records source, and the Selected Record outputs: the object of the record collection. Example: Records comes from a Get Records element on Contact, so Record Object is Contact. The setup panel fills it in when you pick Records or set Object API Name.
RecordsrecordsRecords source: a record collection from the flow. Shown as they are, with no extra query.
Record Label FieldrecordLabelFieldRecords or query: field for the label. Default is Name (for a query, the object's name field). Relationship paths such as Account.Name work for records.
Record Value FieldrecordValueFieldRecords or query, optional: field for the value. Default is Id.
Record Description FieldrecordDescriptionFieldRecords or query, optional: field for the second line.
Record Image URL FieldrecordImageFieldRecords or query, optional: a text or URL field with an image URL, in the same formats as Choice Image URLs.
Record Icon FieldrecordIconFieldRecords or query, optional: field holding an SLDS icon name per record.
Label FormatlabelFormatRecords or query, optional: builds the label from fields. Put each field's API name in braces, and type any other text as it should appear, for example {Name} ({Code__c}). Overrides Record Label Field. Plain text only. HTML is shown as text.
Description FormatdescriptionFormatRecords or query, optional: builds the second line the same way, for example {City__c} - {Capacity__c} seats. If a field is blank, a spaced separator such as - left at the start or end of the line is dropped, and empty brackets are removed. Plain text only.
Object API NameobjectApiNamePicklist or query source: the API name of the object, for example Account. Custom object API names end in __c.
Picklist Field API NamefieldApiNamePicklist source: the API name of the picklist or multi-select picklist field, for example Industry.
Record Type IdrecordTypeIdPicklist source, optional: shows only the picklist values allowed for this record type. Enter a record type Id (it starts with 012) or a resource, for example {!Get_Record_Type.Id}. Blank, or a value that is not a record type Id, uses the object's default record type.
Controlling Field ValuecontrollingValuePicklist source, optional: for a dependent picklist, the current value of its controlling field, for example {!varRegion}. Only the values allowed for it are shown. A value that matches no controlling value shows no choices.
Filter FieldfilterFieldQuery source, optional: the API name of the field to filter on, for example Status__c. One relationship step is allowed, for example Account.Type.
Filter OperatorfilterOperatoreqeq (equals), ne (not equal), in (in a list), nin (not in a list), like (text pattern), gt (greater than), gte (greater than or equal), lt (less than), or lte (less than or equal). See Filter Value for how to write the value.
Filter ValuefilterValueQuery source: the value to compare with Filter Field. Type it, or use a resource such as {!recordId}. Values are passed as query variables. How to write it:
eq, ne, gt, gte, lt, lte: one value, for example Available or 100.
in, nin: values separated by commas, for example Available,Reserved. Use \, for a comma inside a value.
like: use % for any text. Exc% finds values that start with Exc. %tor finds values that end with tor.
Checkbox field: true or false.
Filter Field 2filterField2Second filter, joined with AND.
Filter Operator 2filterOperator2eqSame operators as Filter Operator.
Filter Value 2filterValue2Value for Filter Field 2, written the same way as Filter Value.
Order By FieldorderByQuery source, optional: the API name of the field to sort by, for example CreatedDate. If blank, the choices are sorted by Record Label Field, or by the object's name field when Label Format is set.
Sort DirectionsortDirectionascasc (A to Z, lowest first) or desc (Z to A, highest first).
Maximum Record ChoicesmaxChoices200Query source. From 1 to 2,000.
Icon (All Choices)iconNameOptional SLDS icon for every choice that has no icon or image of its own, for example standard:account.
Selection ModeselectionModesinglesingle or multi.
RequiredrequiredfalseRequire a choice before Next or Finish.
Required MessagerequiredMessageShown when the user presses Next with nothing picked (Required is on, or Minimum Selections is set), for example Choose a plan to continue. Blank uses the translated default.
Minimum SelectionsminSelections0Multi only. 0 means no minimum. The component accepts up to 1,000. Example: Minimum 1 and Maximum 2 for "Pick up to two add-ons".
Maximum SelectionsmaxSelections0Multi only. 0 means no limit. The component accepts up to 1,000.
DisableddisabledfalseShows the choices and the current selection read-only: the user cannot change them. Example: show a plan picked on an earlier screen as a reminder.
Default ValuedefaultValueThe choice selected when the screen opens and Value is blank. Enter the value, not the label.
Single select: Medium (or M if Choice Values is S,M,L).
Records or query source: the record Id, or the Record Value Field value.
Multi select: values separated by commas, Parking,Breakfast, or by semicolons, Parking;Breakfast.
Picklist source: leave it blank to use the field's default value.
Dropdown PlaceholderplaceholderDropdown layout: text shown before a choice is made, for example Select a size. Blank uses the translated default.
Include --None--includeNonefalseDropdown layout, when Required is off: adds an empty first option, so the user can clear the choice.
Layoutlayoutautoauto, tiles, cards, list, buttons, dropdown, or iconbuttons (Small buttons). Auto never picks Small buttons. A requested dropdown becomes a list when Selection Mode is multi.
Densitydensitycomfortablecomfortable or compact. Compact applies only when the component is wide and used with a mouse. On phones and on narrow layouts, the component keeps larger touch targets.
Columns (Desktop)columns00 means automatic. You can set 1 to 6. Extra columns are not left empty when there are fewer choices. Not used for list or buttons.
Columns (Phone)phoneColumns1Tiles or cards per row on a phone or a narrow screen: 1 or 2. Use 2 for short labels with images.
Image ShapeimageAspectlandscapeThe shape of choice images: landscape (wider than tall), square, or portrait (taller than wide).
Accent ColoraccentColorColor for selection and focus, for example #0B5CAB. See Colors and formatting.
Background ColorbackgroundColorOptional color behind the whole component, for example #F3F3F3. Leave blank to follow the theme and dark mode.
Tile ColortileColorOptional color of each choice (tile, card, row, or button), for example #FFFFFF. Leave blank to follow the theme and dark mode.
Text ColortextColorOptional, for example #181818. Used only if it reaches 4.5:1 contrast.
Text Sizesizemediumsmall (87.5%), medium (100%), large (112.5%), or xlarge (125%) of the normal text size. Example: large for a kiosk screen.
Corner Shapeshaperoundedrounded (default), square (slightly rounded corners), or pill (the roundest corners).
Alignmentalignstartstart, center, or end. Lines up the icon and text inside each choice, and the row of buttons in the buttons and Small buttons layouts. Example: center for big Yes and No buttons. In a right-to-left language, start is the right side.
Color Map FieldcolorFieldOptional field whose value is looked up in the Color Map (records or query), for example Status__c. If blank, the choice value and then the label are used.
Color MapcolorMapOptional colors by value. See Colors and formatting.
Color Map StylecolorCuestripestripe, tint, fill, or dot. Use tint if users work in dark mode.
Navigate After SelectionnavigateOnSelectnonenone, next, back, finish, or pause. See Navigation and the screen footer.
Show Continue ButtonshowContinueButtonfalseShows a button that moves the flow on. With Navigate After Selection set, multi select always shows the button.
Continue Button LabelcontinueLabelYour own text for the Continue button, for example Book now. Blank uses the translated Next, Previous, Finish, or Pause label.
Available ActionsavailableActionsSet by Flow. Do not map.
ValuevalueThe picked value, not the label. Example: Choices Small,Medium,Large with Choice Values S,M,L.
Single select: L.
Multi select: comma-separated, S,L. With a picklist source, semicolon-separated, ready for a multi-select picklist field.
Map the same variable in and out to keep the choice on Back.
Values (Collection)valuesOutput: the selected values as a collection.
Selected LabelselectedLabelOutput: the label the user saw, for example Large. In multi select, the labels separated by a comma and a space, Small, Large.
Selected RecordselectedRecordOutput, records or query source: the picked record. In multi select, the first picked record.
Selected RecordsselectedRecordsOutput, records or query source: all picked records, as a record collection.

NC Picklist

NC Picklist shows options as a dropdown, a radio or checkbox list, or buttons, including small buttons. People can pick one option or several. Choices can come from the same sources as NC Buttons & Tiles (typed text, a collection, records, a picklist field, or a query). NC Picklist has no image properties.

Use it when the choice should look like the other fields on the screen.

NC Picklist with the List layout on desktop: radio rows from a query source, and a multi-select picklist.
NC Picklist with the List layout on desktop: radio rows from a query source, and a multi-select picklist.
NC Picklist with Layout set to Auto on a phone: up to 5 short options become one segmented button row.
NC Picklist with Layout set to Auto on a phone: up to 5 short options become one segmented button row.

Add it to a screen

Flow Builder setup panel for NC Picklist: the Basic section, Style presets, and the Label field.
Flow Builder setup panel for NC Picklist: the Basic section, Style presets, and the Label field.
  1. Open the flow in Flow Builder and add or open a Screen element.
  2. Add NC Picklist. The setup panel opens.
  3. In Basic, choose a Style if you want one: Radio list, Checkbox list, or Compact. A style fills only the settings you leave blank. Leave Style blank, or choose Custom, to keep the original defaults.
  4. Set Label. Choose where the choices come from, the same way as NC Buttons & Tiles (auto, text, collection, records, picklist, or query). NC Picklist has no Choice Image URLs or Record Image URL Field. Turn on Required if the user must pick a value.
  5. A live preview shows the component with your settings.
  6. Set Selection Mode to single or multi. Optional: Minimum Selections, Maximum Selections, and Default Value.
  7. Leave Layout set to auto, or pick dropdown, list, buttons, or iconbuttons (Small buttons). Auto uses a list for multi select. For a single selection, Auto uses a dropdown when there are more than 5 options, on every device, including phones. For 5 or fewer short labels with no descriptions, Auto uses buttons when they fit, or a list. Auto never picks Small buttons. Small buttons show an icon or a short label, and the full label as a tooltip.
  8. Open Advanced for selection details, colors, navigation, and the other properties.
  9. Map Value, Values (Collection), and Selected Label. For record sources, also map Selected Record or Selected Records. Map the same Value variable in and out to keep the choice when the user goes back.

Properties

NC Picklist has the same properties as NC Buttons & Tiles, except Choice Image URLs, Record Image URL Field, Columns (Desktop), Columns (Phone), and Image Shape. Layout values are auto, dropdown, list, buttons, and iconbuttons (Small buttons). A requested dropdown becomes a list when Selection Mode is multi.

PropertyAPI nameDefaultDescription
StylestylePresetOptional. A style fills only the settings you leave blank. You can still change each one under Advanced. Leave it blank, or choose Custom, to keep the original defaults.
radio (Radio list): Layout list, Selection Mode single.
checkbox (Checkbox list): Layout list, Selection Mode multi.
compact (Compact): Layout dropdown, Density compact.
LabellabelQuestion or field label shown above the component.
Help TexthelpTextOptional hint shown under the label, for example Pick the plan that fits your team.
Data Sourcesourceautoauto, text, collection, records, picklist, or query. Auto follows the same order as NC Buttons & Tiles.
ChoiceschoiceLabelsText source: comma-separated labels. Use \, for a comma inside a label.
Choice ValueschoiceValuesText source, optional: values in the same order. A blank entry uses the label.
Choice DescriptionschoiceDescriptionsText source, optional: second lines in the same order.
Choice IconschoiceIconsText source, optional: SLDS icon names in the same order.
Choice Labels (Collection)choiceLabelsCollectionCollection source: a Text collection variable.
Choice Values (Collection)choiceValuesCollectionCollection source, optional: values in the same order.
Choice Descriptions (Collection)choiceDescriptionsCollectionCollection source, optional: second lines in the same order.
Record ObjectNone (object type)Records source, and the Selected Record outputs: the object of the record collection, for example Contact. The setup panel fills it in when you pick Records or set Object API Name.
RecordsrecordsRecords source: a record collection from the flow.
Record Label FieldrecordLabelFieldRecords or query: field for the label. Default is Name.
Record Value FieldrecordValueFieldRecords or query, optional. Default is Id.
Record Description FieldrecordDescriptionFieldRecords or query, optional: field for the second line.
Record Icon FieldrecordIconFieldRecords or query, optional: field holding an SLDS icon name per record.
Label FormatlabelFormatRecords or query, optional: builds the label from fields. Put each field's API name in braces, and type any other text as it should appear, for example {Name} ({Code__c}). Overrides Record Label Field. Plain text only. HTML is shown as text.
Description FormatdescriptionFormatRecords or query, optional: builds the second line the same way, for example {City__c} - {Capacity__c} seats. If a field is blank, a spaced separator such as - left at the start or end of the line is dropped, and empty brackets are removed. Plain text only.
Object API NameobjectApiNamePicklist or query source: the API name of the object, for example Account. Custom object API names end in __c.
Picklist Field API NamefieldApiNamePicklist source: the API name of the picklist or multi-select picklist field, for example Industry.
Record Type IdrecordTypeIdPicklist source, optional: shows only the picklist values allowed for this record type. Enter a record type Id (it starts with 012) or a resource, for example {!Get_Record_Type.Id}. Blank, or a value that is not a record type Id, uses the object's default record type.
Controlling Field ValuecontrollingValuePicklist source, optional: for a dependent picklist, the current value of its controlling field, for example {!varRegion}. Only the values allowed for it are shown. A value that matches no controlling value shows no choices.
Filter Field / Operator / ValuefilterField, filterOperator, filterValueoperator eqFirst query filter. Filter Field is the API name of the field, for example Status__c or Account.Type. The operators and the way to write each value are the same as on NC Buttons & Tiles. See Filter Operator and Filter Value in its properties.
Filter Field 2 / Operator 2 / Value 2filterField2, filterOperator2, filterValue2operator eqSecond query filter, joined with AND.
Order By FieldorderByQuery source, optional: the API name of the field to sort by, for example CreatedDate. If blank, the choices are sorted by Record Label Field, or by the object's name field when Label Format is set.
Sort DirectionsortDirectionascasc (A to Z, lowest first) or desc (Z to A, highest first).
Maximum Record ChoicesmaxChoices200Query source. From 1 to 2,000.
Icon (All Choices)iconNameOptional SLDS icon for every choice without its own icon, for example standard:account.
Selection ModeselectionModesinglesingle or multi.
RequiredrequiredfalseRequire a choice before Next or Finish.
Required MessagerequiredMessageShown when the user presses Next with nothing picked (Required is on, or Minimum Selections is set), for example Choose a plan to continue. Blank uses the translated default.
Minimum SelectionsminSelections0Multi only. 0 means no minimum. Example: Minimum 1 and Maximum 2 for "Pick up to two add-ons".
Maximum SelectionsmaxSelections0Multi only. 0 means no limit.
DisableddisabledfalseShows the choices and the current selection read-only: the user cannot change them. Example: show a plan picked on an earlier screen as a reminder.
Default ValuedefaultValueThe choice selected when the screen opens and Value is blank. Enter the value, not the label.
Single select: Medium (or M if Choice Values is S,M,L).
Records or query source: the record Id, or the Record Value Field value.
Multi select: values separated by commas, Parking,Breakfast, or by semicolons, Parking;Breakfast.
Picklist source: leave it blank to use the field's default value.
Dropdown PlaceholderplaceholderDropdown layout: text shown before a choice is made, for example Select a size. Blank uses the translated default.
Include --None--includeNonefalseDropdown layout, when Required is off: adds an empty first option, so the user can clear the choice.
Layoutlayoutautoauto, dropdown, list, buttons, or iconbuttons (Small buttons). Auto never picks Small buttons.
Densitydensitycomfortablecomfortable or compact. Compact applies only when the component is wide and used with a mouse. On phones and on narrow layouts, the component keeps larger touch targets.
Accent Color, Background Color, Tile Color, Text ColoraccentColor, backgroundColor, tileColor, textColorSee Colors and formatting.
Text Sizesizemediumsmall (87.5%), medium (100%), large (112.5%), or xlarge (125%) of the normal text size. Example: large for a kiosk screen.
Corner Shapeshaperoundedrounded (default), square (slightly rounded corners), or pill (the roundest corners).
Alignmentalignstartstart, center, or end. Lines up the icon and text inside each choice, and the row of buttons in the buttons and Small buttons layouts. Example: center for big Yes and No buttons. In a right-to-left language, start is the right side.
Color Map Field, Color Map, Color Map StylecolorField, colorMap, colorCuestyle stripeStyle: stripe, tint, fill, or dot.
Navigate After SelectionnavigateOnSelectnonenone, next, back, finish, or pause.
Show Continue ButtonshowContinueButtonfalseWith Navigate After Selection set, multi select always shows the button.
Continue Button LabelcontinueLabelYour own text for the Continue button, for example Book now. Blank uses the translated action label.
Available ActionsavailableActionsSet by Flow. Do not map.
ValuevalueThe picked value, not the label. Example: Choices Small,Medium,Large with Choice Values S,M,L.
Single select: L.
Multi select: comma-separated, S,L. With a picklist source, semicolon-separated, ready for a multi-select picklist field.
Map the same variable in and out to keep the choice on Back.
Values (Collection)valuesOutput collection of selected values.
Selected LabelselectedLabelOutput: the label the user saw, for example Large. In multi select, the labels separated by a comma and a space, Small, Large.
Selected Record / Selected RecordsselectedRecord, selectedRecordsOutputs, records or query source. Selected Record is the picked record (in multi select, the first one). Selected Records holds all picked records.

NC Lookup

NC Lookup is a type-ahead search for one record. People type, see matching results, and pick one. Search can run against the org, or against a record collection you already have in the flow.

Use it when the list is long, or when the user should find a record by typing part of the name.

If you set only the object, NC Lookup uses the object's name field as the title. If you also choose a Style, it picks detail and search fields for you. For Contact, that is Name, Email, and Phone. You can still set each field yourself.

NC Lookup with the Cards layout on a phone: an open rentable search list with Color Map status dots and a keep-typing hint.
NC Lookup with the Cards layout on a phone: an open rentable search list with Color Map status dots and a keep-typing hint.
NC Lookup on desktop: a selected rentable card with a Color Map dot and a Change button, and a second search field.
NC Lookup on desktop: a selected rentable card with a Color Map dot and a Change button, and a second search field.
Preview. NC Lookup with the Dropdown layout on desktop in dark mode: matches highlighted, secondary fields on the second line, a keep-typing hint, and the required message.
Preview. NC Lookup with the Dropdown layout on desktop in dark mode: matches highlighted, secondary fields on the second line, a keep-typing hint, and the required message.

Add it to a screen

Flow Builder setup panel for NC Lookup: the Basic section, Style presets, and help text for Search picker, Dropdown, and Cards.
Flow Builder setup panel for NC Lookup: the Basic section, Style presets, and help text for Search picker, Dropdown, and Cards.
  1. Open the flow in Flow Builder and add or open a Screen element.
  2. Add NC Lookup. The setup panel opens.
  3. In Basic, choose a Style if you want one: Search picker, Dropdown, or Cards. A style fills only the settings you leave blank. Leave Style blank, or choose Custom, to keep the original defaults.
  4. Set Object, for example Contact. Set Label. Turn on Required if the user must pick a record.
  5. With the object set, and a Style chosen, the component picks the title, detail, and search fields. For Contact, that is Name, Email, and Phone. A "Picked for you" summary lists those fields. You can change them under Advanced.
  6. A live preview appears once you set an object or a record collection. You can search in the preview to try records you can see. With a record collection, the preview stays empty, because the records are loaded when the flow runs.
  7. Choose a data source:
    • Search the org (search): the default when you set Object. Optional settings under Advanced include Title Field, Detail Fields, Search In Fields, Match Mode (contains, or startswith for a very large object), up to two filters, Maximum Results (default 10, from 1 to 50), and Minimum Characters (default 2).
    • Use a record collection (records): set Records and Record Object. It filters the records already in the flow, in the browser, and does not search the org.
  8. Open Advanced for field mapping, filters, colors, navigation, and the other properties.
  9. Map Selected Record Id, Selected Label, and Selected Record. Map Selected Record Id in and out to keep the choice when the user goes back.

Properties

PropertyAPI nameDefaultDescription
StylestylePresetOptional. A style fills only the settings you leave blank. You can still change each one under Advanced. Leave it blank, or choose Custom, to keep the original defaults.
search (Search picker): Layout auto, up to 2 detail fields, Maximum Results 10, Color Map Style stripe.
dropdown (Dropdown): Layout dropdown, Density compact, 1 detail field, Maximum Results 8, Color Map Style dot.
cards (Cards): Layout cards, up to 3 detail fields, Maximum Results 6, Color Map Style dot.
With any style, the component also picks search fields when Search In Fields is blank.
LabellabelField label shown above the component.
PlaceholderplaceholderText in the empty search field, for example Search rentables.... Blank uses the translated "Search {object}..." text, or "Search..." for a records source.
Help TexthelpTextOptional hint shown under the label, for example Start typing a customer name.
Data Sourcesourceautoauto, search, or records. Auto uses records when Records is set, otherwise search.
Record ObjectNone (object type)The object of the Records collection and of the Selected Record output, for example Contact. The setup panel fills it in when you set Object.
RecordsrecordsRecords source: a record collection from the flow, searched in the browser.
ObjectobjectApiNameSearch source: the API name of the object to search, for example Contact.
Title FielddisplayFieldField shown as the result title, for example Name. If you leave this blank, the component uses the object's name field (for Contact, the full name).
Detail FieldssecondaryFieldsOptional comma-separated fields for the second line, for example Email,Phone. If you leave this blank and set a Style, the component picks them for you, for example Email and Phone on Contact.
Label FormatlabelFormatOptional template for the title. Put each field's API name in braces, and type any other text as it should appear, for example {Name} ({Code__c}). Plain text only.
Secondary FormatsecondaryFormatOptional template for the second line, built the same way, for example {Email} - {Phone}. If a field is blank, a spaced separator such as - left at the start or end of the line is dropped, and empty brackets are removed. Plain text only.
Search In FieldssearchFieldsOptional comma-separated text fields to search, for example Name,Email. If you leave this blank, the component searches the title field. With a Style, it also adds text detail fields such as Email, up to 3 fields in total.
Match ModematchModecontainscontains (default) finds the typed text anywhere: cav finds Excavator. startswith finds only values that begin with it: Exc finds Excavator, cav does not. startswith is faster on a very large object.
Filter Field / Operator / ValuefilterField, filterOperator, filterValueoperator eqFirst filter, for the search source. Filter Field is the API name of the field, for example Status__c or Account.Type. The operators and the way to write each value are the same as on NC Buttons & Tiles. See Filter Operator and Filter Value in its properties.
Filter Field 2 / Operator 2 / Value 2filterField2, filterOperator2, filterValue2operator eqSecond filter, joined with AND.
Order By FieldorderBySearch source, optional: the API name of the field to sort the results by, for example CreatedDate. If blank, the results are sorted by the title field.
Sort DirectionsortDirectionascasc (A to Z, lowest first) or desc (Z to A, highest first).
Maximum ResultsmaxResults10From 1 to 50.
Minimum CharactersminCharsHow many characters the user types before results show, from 0 to 10. If blank, 2 for search and 0 for records (the list opens on click, tap, typing, or the Up or Down arrow key, not on focus). Example: 3 for an object with many records.
Search IconiconNameOptional SLDS icon in the empty search field. Default is utility:search. It has the same API name, iconName, as Icon (All Choices) on NC Buttons & Tiles and NC Picklist.
Object IconobjectIconNameIcon on results and on the selection, for example standard:account. If blank, the component uses the standard object icon, or standard:record.
RequiredrequiredfalseRequire a record before Next or Finish.
Required MessagerequiredMessageShown when the user presses Next without picking a record, for example Choose a rentable to continue. Blank uses the translated default.
DisableddisabledfalseShows the field and the picked record read-only: the user cannot search, clear, or change it.
LayoutlayoutautoHow the results appear.
auto: dropdown on wide screens, inline on phones and in narrow columns.
dropdown: the results float over the content below the field.
inline: the results push the content below them down, so they are never cut off.
cards: the results show as cards, and the picked record becomes a card with a Change button.
Densitydensitycomfortablecomfortable or compact. Compact applies only when the component is wide and used with a mouse. On phones and on narrow layouts, the component keeps larger touch targets.
Accent ColoraccentColorSee Colors and formatting. NC Lookup has no Tile Color or Alignment property.
Background ColorbackgroundColorOptional color behind the whole component, for example #F3F3F3. Leave blank to follow the theme and dark mode.
Text ColortextColorOptional. Used only if it reaches 4.5:1 contrast.
Text Sizesizemediumsmall (87.5%), medium (100%), large (112.5%), or xlarge (125%) of the normal text size. Example: large for a kiosk screen.
Corner Shapeshaperoundedrounded (default), square (slightly rounded corners), or pill (the roundest corners).
Color Map FieldcolorFieldOptional field whose value is looked up in the Color Map, for example Status__c.
Color MapcolorMapOptional colors by value.
Color Map StylecolorCuestripestripe, dot, or tint. There is no fill style on NC Lookup.
Navigate After SelectionnavigateOnSelectnonenone, next, back, finish, or pause.
Show Continue ButtonshowContinueButtonfalseShows a button that moves the flow on after the selection.
Continue Button LabelcontinueLabelYour own text for the Continue button, for example Book now. Blank uses the translated action label.
Available ActionsavailableActionsSet by Flow. Do not map.
Selected Record IdvalueThe Id of the picked record. It has the same API name, value, as Value on the other components. To show a record as already picked, map a Text variable that holds a record Id in, for example {!varContactId}, and store the output in the same variable.
Selected LabelselectedLabelOutput: the title of the picked record as it was shown, for example the contact's name.
Selected RecordselectedRecordOutput: the selected record, including the Id and the fields shown.

NC Timer

NC Timer moves the flow on after a delay. Use it for a confirmation or "thank you" screen that should continue by itself, or (with Layout hidden, or the Silent timer style) for a delay with nothing visible on the screen.

NC Timer with the Bar layout on a phone: a countdown with Continue now, Pause, and Stop timer, and a second timer that only counts down.
NC Timer with the Bar layout on a phone: a countdown with Continue now, Pause, and Stop timer, and a second timer that only counts down.
NC Timer with the Compact layout on desktop: a countdown ring with a Continue button, and a second timer with icon-only controls.
NC Timer with the Compact layout on desktop: a countdown ring with a Continue button, and a second timer with icon-only controls.

Add it to a screen

Flow Builder setup panel for NC Timer: the Basic section, Style presets, and Seconds.
Flow Builder setup panel for NC Timer: the Basic section, Style presets, and Seconds.
  1. Open the flow in Flow Builder and add or open a Screen element.
  2. Add NC Timer. The setup panel opens.
  3. In Basic, choose a Style if you want one: Countdown, Silent timer, or Progress bar. A style fills only the settings you leave blank. Leave Style blank, or choose Custom, to keep the original defaults.
  4. Set Seconds (1 to 3,600, default 10). Set Then (After the Timer) to what should happen when the countdown ends: next, back, finish, pause, or none. Optionally set Message. In the message, {0} is replaced with the seconds left. In the compact and large layouts, leave {0} out, because the ring shows the seconds.
  5. A live preview shows the timer with your settings. The preview never moves the flow on.
  6. Open Advanced for pause, stop, continue, announcements, look, and outputs.
  7. If the screen should have no footer buttons, turn off the footer's Previous, Next, Finish, and Pause buttons in the Screen properties, and use the timer (and, if you want, Continue now) to move on.
  8. Map Completed if you turn off Run Every Visit, so the timer runs only the first time the screen is shown. Map Stopped by User if you need to know that the user pressed Stop timer. Map Timer Fired if you need to know that the countdown ran out and the Then (After the Timer) action ran. Timer Fired is true only in that case. It is false if the user pressed Stop timer, pressed Continue now, or moved on before the countdown ended.

Properties

PropertyAPI nameDefaultDescription
StylestylePresetOptional. A style fills only the settings you leave blank. You can still change each one under Advanced. Leave it blank, or choose Custom, to keep the original defaults.
countdown (Countdown): Layout large, with Pause, Stop timer, and Continue now.
silent (Silent timer): Layout hidden, with no buttons.
progress (Progress bar): Layout bar, with Pause and Stop timer, and no Continue now.
All three turn on Announce to Screen Readers.
Secondsseconds10Delay in seconds, from 1 to 3,600.
After the TimerafterActionnextnext, back, finish, pause, or none. Next becomes Finish on the last screen. none only sets Completed. In the setup panel, this setting is labeled Then.
Run Every VisitrepeattrueOn (default): the timer starts each time the screen is shown, including after Previous. Off: it runs only the first time. When you turn it off, also create a Boolean variable, for example varTimerDone, set Completed to it, and store Completed in the same variable. Use case: a welcome screen that moves on by itself the first time, but not when the user comes back to it.
LayoutlayoutautoHow the timer looks.
auto: bar on wide screens, compact on phones and in narrow columns.
bar: the message, the buttons, and a thin progress bar.
compact: one line with a countdown ring that shows the seconds, a short message, and small buttons.
large: a big centered ring with the message and buttons, for a kiosk, check-in, or confirmation screen.
hidden: nothing is visible, but the timer still runs and moves the flow on, for example on a "Saving..." screen.
Announce to Screen ReadersannouncetruePolite announcements at the start, at 60, 30, 10, and 5 seconds, and at the end. This also applies in the hidden layout.
MessagemessageOptional text next to the countdown. Put {0} where the seconds go, for example Saving your booking in {0} seconds. In the compact and large layouts the ring already shows the seconds, so leave {0} out, for example Thanks! Starting over shortly. Blank uses the built-in text, for example Continuing in {0} seconds, or Continuing automatically in the ring layouts.
Allow PauseallowPausetrueShows Pause and Resume.
Allow StopallowStoptrueShows Stop timer.
Allow Continue NowallowContinueNowfalseShows a Continue now button, so the user can skip the wait. It runs the Then (After the Timer) action at once, for example moves to the next screen. Not shown when After the Timer is none.
Accent ColoraccentColorColor for the countdown and focus. NC Timer has no Tile Color, Color Map, or Density property.
Background ColorbackgroundColorOptional color of the timer panel.
Text ColortextColorOptional. Used only if it reaches 4.5:1 contrast.
Text Sizesizemediumsmall (87.5%), medium (100%), large (112.5%), or xlarge (125%) of the normal text size. Example: large for a kiosk screen.
Corner Shapeshaperoundedrounded (default), square (slightly rounded corners), or pill (the roundest corners).
Alignmentalignstartstart, center, or end. Lines up the timer message. In a right-to-left language, start is the right side.
Available ActionsavailableActionsSet by Flow. Do not map.
CompletedcompletedTrue once the timer ran out, or when the user pressed Continue now. Map it in and out of the same Boolean variable when Run Every Visit is off.
Stopped by UserstoppedByUserOutput: true if the user pressed Stop timer.
Timer FiredtimerFiredOutput: true when the countdown ran out and the Then (After the Timer) action ran (also with none and in the hidden layout). False if the user pressed Stop timer, pressed Continue now, or moved on before the countdown ended.

Shared behavior

Terms used in this chapter

Some words in this chapter cover more than one setting. This table uses one term for each idea and says which property it means on each component. Setting names are written as they appear in the property list, and the values you type or pick are in code style, for example Layout auto.

TermMeaning
ValueThe stored choice: the choice's value, not its label. For a picklist source, that is the picklist value's API name. On NC Lookup the same property (API name value) is labeled Selected Record Id, and it holds the record Id.
Label and titleThe text the user sees for a choice is its label. Record Label Field or Label Format sets it for records and queries. On NC Lookup, each result shows a title instead, set by Title Field or Label Format. On NC Buttons & Tiles, NC Picklist, and NC Lookup, Selected Label returns the text of the pick. The Label property is something else: the question or field label above the component.
Second lineThe smaller line under a choice or a result. NC Buttons & Tiles and NC Picklist fill it from Choice Descriptions, Record Description Field, or Description Format. NC Lookup fills it from Detail Fields or Secondary Format.
Record Object and ObjectRecord Object is the object of a record collection (Records) and of the Selected Record outputs. Object API Name (NC Buttons & Tiles, NC Picklist) and Object (NC Lookup, the same API name objectApiName) name the object to read from the org.
Reading records from the orgData Source query (NC Buttons & Tiles, NC Picklist) and search (NC Lookup) both read records from the org, with the running user's access. A query loads the choices when the screen opens. A search runs as the user types.
Then (After the Timer)The NC Timer setting for what happens when the countdown ends. The setup panel labels it Then. The property list labels it After the Timer (afterAction).
Small buttonsOne look, two settings with different values. Layout iconbuttons (Small buttons) is the layout, on NC Buttons & Tiles and NC Picklist. Style smallbuttons (Small buttons) exists only on NC Buttons & Tiles, and fills in Layout iconbuttons. NC Picklist has no Small buttons style, so set its Layout to iconbuttons.
Big buttons and Icon tilesStyle names, not layouts. Style buttons (Big buttons) fills in Layout buttons and Text Size large. Style icons (Icon tiles) fills in Layout tiles.
CompactThree separate settings use this word.
NC Picklist Style compact (Compact) fills in Layout dropdown and Density compact. NC Lookup Style dropdown also fills in Density compact.
Density compact (NC Buttons & Tiles, NC Picklist, NC Lookup) tightens spacing only when the component is wide and used with a mouse.
NC Timer Layout compact is a one-line countdown with a ring.
Footer buttonsThe footer's Previous, Next, Finish, and Pause buttons: Flow's standard screen buttons. You turn them on or off in the Screen properties.
Continue button and Continue nowContinue button: on NC Buttons & Tiles, NC Picklist, and NC Lookup. It appears only when Navigate After Selection is set (not none) and either Show Continue Button is on or, on NC Buttons & Tiles and NC Picklist, multi select is on. It runs Navigate After Selection. Continue now: on NC Timer. It appears with Allow Continue Now, and runs Then (After the Timer) at once.
Icon (All Choices) and Search IconThey share the API name iconName but set different icons. Icon (All Choices), on NC Buttons & Tiles and NC Picklist, is for choices without their own icon. Search Icon, on NC Lookup, is the icon in the empty search field.

Layout

With Layout set to auto, each component measures its own width and also checks whether the device is a phone.

On NC Buttons & Tiles, NC Picklist, and NC Lookup, Density set to compact tightens spacing only when the component is wide and used with a mouse. On phones and on narrow layouts, the component uses larger touch targets. NC Timer has no Density property.

On phones, on narrow layouts, and on touch, a dropdown in NC Buttons & Tiles or NC Picklist uses the device's native select list.

Required messages

If Required is on and the user presses Next without a valid choice, the component shows its own required message in bold red text, and the field gets a red outline. The message clears when the user makes a valid pick. Flow does not add a second message.

Record search and detail lines

On NC Lookup, search matches the name field. On Contact, with Match Mode set to contains, typing a last name such as Fox finds Annie Fox.

If a detail or description line would have only a separator, for example when one of the fields is blank, the component leaves that separator out.

Colors and formatting

These properties are shared, with the exceptions noted above (NC Lookup has no Tile Color or Alignment; NC Timer has no Tile Color, Color Map, or Density).

PropertyWhat it does
Accent ColorColor for selection and focus, for example #0B5CAB. Hex, rgb(), or a color name. It must reach 3:1 contrast against the tile or panel. If it does not, the component lightens or darkens it, or keeps the theme color. Leave it blank to follow the org theme and dark mode.
Background Color / Tile Color / Text ColorOptional. Hex, rgb(), hsl(), or a color name, for example #F3F3F3, rgb(243,243,243), or white. Background Color is behind the whole component. Tile Color is each choice. Leave blank to follow the theme and dark mode. Text Color is used only if it is readable at 4.5:1 contrast. Otherwise the component picks a dark or white text color. In dark mode, a light tile or background color is mixed into the theme surface.
Text Sizesmall (87.5%), medium (default, 100%), large (112.5%), or xlarge (125%) of the normal text size. Example: large for a kiosk screen.
Corner Shaperounded (default), square (slightly rounded corners), or pill (the roundest corners).
Alignmentstart (default), center, or end. On NC Buttons & Tiles and NC Picklist, it lines up the icon and text inside each choice, and the row of buttons in the buttons and Small buttons layouts. On NC Timer, it lines up the message. In a right-to-left language, start is the right side. NC Lookup has no Alignment property.
Label Format / Description Format (NC Lookup also has Secondary Format)Build a line from fields: put each field's API name in braces, and type any other text as it should appear. Examples: {Name} ({Code__c}) or {City__c} - {Capacity__c} seats. Plain text only. HTML is shown as text.
Color MapGive each choice its own color. Write one entry per value, with a semicolon or a new line between entries.
Option 1, the simple format: Value:background color/text color (text color optional).
Gold:#FFF4CC/#5C4400
Silver:#EEEEEE
Option 2, the Mobile Data Table format, so you can paste colors you already set up there (background, then a semicolon, then the text color):
[{'key':'Gold','value':'#FFF4CC;#5C4400'},{'key':'Silver','value':'#EEEEEE'}]
Color Map FieldOptional field whose value is looked up in the Color Map (records or query), for example Status__c. If blank, the choice value and then the label are used.
Color Map Stylestripe (default), a colored bar on the edge. tint, a light background; use it if users work in dark mode. fill, a solid background (NC Buttons & Tiles and NC Picklist only). dot, a small colored dot. NC Lookup supports stripe, tint, and dot.
Icon (All Choices) / Object Icon / Search IconSLDS icon names, for example standard:account.
NC Buttons & Tiles with colors and a Color Map on desktop: custom tile colors, a fill Color Map on Priority, and a stripe Color Map on a query list.
NC Buttons & Tiles with colors and a Color Map on desktop: custom tile colors, a fill Color Map on Priority, and a stripe Color Map on a query list.

NC Buttons & Tiles, NC Picklist, and NC Lookup can move the flow on as soon as the user chooses. Set Navigate After Selection:

ValueEffect
noneDefault. The user presses the footer's Next.
nextMoves to the next screen. On the last screen, this becomes Finish.
backGoes to the previous screen.
finishFinishes the flow.
pausePauses the flow, if pausing is allowed.

Next and Finish check Required first. The action runs only if the screen offers it.

To hide the footer:

  1. Open the Screen properties and turn off the footer's Previous, Next, Finish, and Pause buttons. The component then provides the only way forward.
  2. Turn on Show Continue Button if users should confirm first. The button label is translated, or you can set your own with Continue Button Label.
  3. When Navigate After Selection is set, multi select always shows the button, because the flow cannot know when the user has finished choosing.
NC Buttons & Tiles with the screen footer hidden. The flow moves on when a plan is selected.
NC Buttons & Tiles with the screen footer hidden. The flow moves on when a plan is selected.
NC Picklist with the screen footer hidden. Picking Yes or Back stores the value and moves the flow to the next screen.
NC Picklist with the screen footer hidden. Picking Yes or Back stores the value and moves the flow to the next screen.
NC Timer with the Bar layout and the screen footer hidden.
NC Timer with the Bar layout and the screen footer hidden.

Hidden timer mode: set Layout to hidden, or choose the Silent timer style. Nothing is visible, but the timer still runs and navigates. Screen-reader users hear polite announcements at the start, at 60, 30, 10, and 5 seconds, and at the end. Turn Announce to Screen Readers off for full silence. Use this for screens that only show a message, then continue.

NC Timer with Layout set to hidden: nothing is visible on the screen. The flow's Previous and Next buttons remain. After the timer ends, the flow moves on.
NC Timer with Layout set to hidden: nothing is visible on the screen. The flow's Previous and Next buttons remain. After the timer ends, the flow moves on.

Translations

Built-in texts appear in the running user's language (Personal Settings, Language). The translations ship inside the components. There is nothing to set up: no Translation Workbench, no languages to enable, and no flow changes.

The components include US English and 15 other languages: English (UK), German, Swedish, French, Spanish, Dutch, Portuguese (Brazil), Japanese, Hebrew, Slovak, Czech, Finnish, Hungarian, Greek, and Korean. English (UK) shows the same wording as US English. Any Portuguese user language, including Portuguese (Portugal), uses the Brazilian Portuguese texts. Dutch (Belgium) uses the Dutch texts, and Austrian and Swiss German use the German texts. Hebrew also matches the he language code. Every other language, including Italian, shows US English.

What is translated: buttons (Next, Previous, Finish, Pause, Continue, Change, Stop timer), placeholders (--None--, Search...), status and error messages, countdown texts, and screen-reader texts.

What is not translated: the texts you enter in Flow Builder (Label, Help Text, Choices, Message, Placeholder, Continue Button Label). Whatever you enter always replaces the built-in text. Translate your own texts with Flow's translation features, or map translated values from Custom Labels or fields.

In a right-to-left language such as Hebrew, the layout follows the page direction.

Preview. German user language: the built-in placeholder, the result hint, and the required message are translated automatically.
Preview. German user language: the built-in placeholder, the result hint, and the required message are translated automatically.

Long labels wrap onto more lines.

Limits