Embedded Help
...
Components
Form & Embedding Support
components for embedding help into forms or pages, including field level help, enabling modes (e g , help enable), and custom backgrounds for layouts auto form ( ihautoform ) use auto form to provide a record detail view with embedded field level help features the improved help auto form component can be used instead of, or as a compliment to, the standard salesforce record details component the auto form offers the following significant advantages field level help provides help on demand, in a variety of callout templates, as chosen by the help author to suit the specific need (and optionally data driven) field list filter to show only those fields that need to be edited in a specific situation (can be data driven) guides to highlight specific fields for orientation and/or data entry use cases for help authors edit mode provides in place editing point and click help enabling and guide enabling modes, allowing non technical help authors to create and embed rich help and training materials for their users without the need for development skills or system administrator input statistics mode interaction monitoring (e g , who has viewed / voted / commented on articular topics); personal form enable optional, read only, 'personal highlights panel' copying user selected fields at the top of their autoform personal form definition data is stored as help interaction records, allowing help analysts to understand in new ways which fields end users find most useful best used for/key features rich field help in page walk throughs dynamic data driven forms in flow screens custom key field styling onboarding / 'help for this record' admin insights & deployment tips drop in place of 'details' or on a 'page help' tab; supports pop ups and field styling; works well with flows and experience cloud example use cases guided opportunity creation with inline field tips dynamic form for case intake expected business outcomes improved data accuracy faster onboarding seamless classic lightning transition default form section state ( defaultsectiontogglestate ) controls whether form sections are expanded or collapsed when first visited by a user, prior to them opening/closing sections as they wish as users expand and collapse sections, their state is recorded for the current object type in help interaction records and their personal settings restored on the basis of these on subsequent page visits callout style ( calloutstyle ) controls how to display callouts when help icons are clicked if the autoform has been configured to show embedded help (i e , callout option is set to "topic selected event plus topic view") embedded opens a space below the help icon and displays the topic in its callout form within it full hides the autoform and shows the entire topic instead, with a 'back' button allowing the user to return to the autoform when ready embedded mode uses a visualforce page to display topic content, whereas in full mode, a lightning component (the topic viewer) is used record type id for use cases involving adding new records only, id of the record type to create in general, this attribute will be populated automatically contact support for more information in the limited circumstances where it might be necessary to supply a specific value manually suppress tools accordion ( suppressmodetools ) hides the accordion area used to present the listing of guides available for the current record set to true (checked) to prevent the accordion area towards the top of the autoform from appearing this may be desired in cases where guides are not anticipated and it is therefore desirable to present the user with a simplified user interface suppress in line editing ( suppressinlineedit ) controls whether or not in line editing is permitted set to true (checked) to stop in line editing tools (pencil icons) being displayed next to editable fields, effectively preventing record edits action on saving ( onsaveaction ) controls the action to take after successfully saving a record via the auto form one can choose to simply report successful saving, or to navigate the entire page to the saved record callout option ( calloutoption ) controls how to respond to helped item clicks the component can open a callout in place, or simply raise a topic selected event to which other components, such as help’s topic viewer, can be made to respond (e g , by displaying the relevant help topic) fields to show ( limitfields ) can be used to limit the fields to display on the autoform enter a comma separated list of field api names to display only those fields, if permitted by the page layout in use override field values ( populatedfields ) can be used to set default field values when adding new records enter \[field api name] ¬ \[field value] | to default fields when adding new records initial sections to display ( initialsections ) the number of form sections to display when first loading the page set a lower number to improve loading speed on lengthy forms set to zero to load all sections regardless of the value specified, all sections will be rendered as soon as the user mouses over the form object api name and layout name ( sobjectname & layoutname ) these settings can be used to hard wire the form to use a particular, named page layout for a named object this can be useful if using the form on custom page layouts more usually, these fields should be left blank, in which case improved help will detect the record type and user profile being used and display the appropriate, allocated page layout both values must be specified if either are non blank object api name should be set to the api name of the object whose data form is to be displayed in built, locally defined and packaged custom objects are supported layout name must follow a precise formula, whose general form is \[object api name] \[object namespace] \[layout plain english name] for example standard objects account account layout local custom objects mylocalobject c my locally defined object (sales) layout object and layout from a managed package, whose namespace is “zzz”, with a packaged layout called main user page zzz somepackagedobjectname c zzz main user page object and layout from a managed package, whose namespace is “zzz”, with a locally defined layout called “main user page” zzz somepackagedobjectname c main user page background ( ihbackground ) decorate custom page layouts with suitable background images that act as static or scrolling wallpaper vertical displacement ( vpad ) amount in pixels by which to displace content appearing on top of the background image vertically by design, the background image essentially occupies no vertical space within its column other components placed in the same column appear directly over the background the vertical displacement figure pushes overlying components in the same page layout column down the screen by the specified pixel amount image sizing option ( stylesize ) controls whether the image grows to fill available space stretch to fill the image will expand in correct aspect ratio to fill the space, as defined by component height and other sizing attributes original size the image will display at its native size, even if more space is available to it resize checking interval ( checkinterval ) time interval (milliseconds) at which the image will refresh / resize itself in the event that the user's viewport (screen) size changes this attribute is only applicable when wallpaper coverage is set to containing column the image will attempt to resize itself to the appropriate column width if and when the user's viewport size changes at the specified checking interval image positioning ( styleposition ) controls how the background image behaves if the page is taller than the user's viewport (screen) if the contents of the layout featuring this component is taller than the user's screen, they will be able to scroll up and down the page to view all available material the image positioning attribute controls how the background image behaves in these cases fixed the image remains static as the user scrolls up and down their page scrolling the image moves with page content as the user scrolls image repeat ( stylerepeat ) controls whether to 'tile' the image vertically and / or horizontally select from none image will not tile and will appear only once horizontal image may repeat horizontally to fill the space available, which may be the width of the containing column or page width depending on the wallpaper coverage setting vertical image may tile vertically, to fill the space available as set by the component height attribute both image may tile horizontally and vertically wallpaper coverage ( stylewidth ) controls whether the background is allowed to 'escape' its containing column select from containing column background image is constrained to a maximum width matching that of the column of the page layout into which the component was placed screen width the background image may (depending on source and related sizing attributes) grow wider than its containing column, extending as far the right hand side of the screen image url (image) url of the image to be used as a background any valid full or relative path to an image that will be accesible to your end users may be specified image x position, image y position (posx, posy) these attributes can be used to offset the background image within its container this can be useful for precise positioning beneath other components on the page layout component height ( height ) display height for this component enter an integer representing height in pixels note that, unlike certain other components, one cannot set 100 percent height using 1 or "viewport height" ( 2) only a fixed pixel height may be specified