Site Object

This page provides detailed information on how to configure and manage a site object.

What is a site object?

A site is a custom, well-tailored web app that provides users with quick access to the pages, tasks, and information that they need. A site object allows you to define and customize the settings and content for your site. This includes defining interfaces to use for pages and customizing the site's navigation bar and branding. The site object makes it easy to both build and troubleshoot a site in one place.

A site object can be referenced in other objects. To learn more about this concept, see Referencing Objects in Expressions.

When to use a site

Use a site when you need to:

• Create a branded experience: Build a custom, branded experience for your application users.
• Provide focused access: Give users quick and focused access to specific pages, tasks, and information.
• Build custom navigation: Create dynamic dashboards, landing pages, or other custom navigation experiences.

To create a public web app that users can access without signing in to Appian, create a portal object instead.

Elements of a site

A site object contains the following elements:

Scroll or drag to pan · ⌘+/⌘− to zoom · Esc to close

#	Section	Available Actions
1	Build tab	Configure the basic elements of your site object.
2	Troubleshoot tab	View error details to help debug issues with the site.
3	Customization settings	Configurations: Modify the primary site settings that determine how users experience the site. Pages: Add, remove, modify, and organize the pages and page groups displayed in the navigation bar. Navigation Bar: Configure the layout, style, and branding of the navigation bar. Branding: Define the look and feel of the site, including colors, shapes, and logos.
4	Branding Preview	View what the navigation bar and branding configurations will look like.

Configurations

This section allows you to modify the primary site configurations that determine how users experience the site.

You can configure the following fields in this section:

Field	Action
Display Name	Enter the name to display in the site navigation menu and browser tab. To configure a dynamic name, choose Expression and enter an expression that evaluates to a string. To avoid your sites loading slowly, don't use long-running expressions, like queries.
Web Address	Click Edit to edit the Web Address Identifier used to construct the site's URL. The web address identifier appears in the URL and in log files.
Show Tempo link in Navigation Menu	Select whether to always show, never show, or conditionally show the Tempo link in the navigation menu when the user is on the site.
Show Record News	Choose whether to show the News view. When enabled, all records displayed in the site will include the News view. In addition, the latest news will be displayed on the summary view when viewing user records.
Show Task List on Mobile	Select whether to always show, never show, or conditionally show the mobile site task list in the Appian Mobile app. When enabled, after a user selects the site, the Appian Mobile menu displays a Tasks list which shows all tasks assigned to the user. Appian Mobile users can access offline-enabled tasks from this list, even when they are not connected to the internet.

Pages

This section allows you to build the structure of your site by adding and organizing pages and page groups. A site can contain up to ten top-level pages or page groups.

For more information on organizing top-level navigation items for the best user experience, see Designing Sites and Portals: Organizing pages and page groups and Mobile Considerations for guidance about mobile-first sites.

Page types

A site page can be one of the following types:

• Action: Displays a start form for a process model that allow users to initiate a process, like submitting a new service request.
• Interface: Displays an interface object. Interface type pages are the only pages that can be added to page groups or use URL parameters in a!urlForSite().
• Record List: Displays a record list configured in a record type.
• Process HQ - Full Library: Displays an embedded Process HQ Reports and Dashboards Library.
• Process HQ - Dashboard: Displays an embedded Process HQ dashboard.

Add a page

To add a page to the site:

1. In the Pages section, click ADD PAGE.

2. In the Add Page dialog, configure the following fields.

   Field	Action
   Title	Enter the page title to display in the navigation bar and browser tab. The title can be configured as a static string or as an expression that evaluates to a string.
   Web Address Identifier	Enter the unique URL identifier for the page. If left blank, a random alphanumeric string will be generated.
   Icon	Select an icon to display with the page title in the navigation bar. When using Mercury style for the header bar, the icon won't display in web browsers, but will always display in Appian Mobile. By default, the file-o icon is selected.
   Type	Select the type of content for the page. See Page types for more information.
   Content	Select the specific design object to display on the page based on the selected Type. For Interface page types, you can create a new interface object by clicking .
   Content Filters	Select whether you want to filter the content for the Reports and Dashboards Library page. Reports and dashboards that use data from the selected record types will be visible in this site. See configure content filters for more information.
   Rule Input Configuration	If the page uses an interface object with URL parameter-compatible rule inputs, configure default values and URL behavior. See rule input configuration for more information.
   Appearance	For Process HQ pages, specifies the page theme and whether to use the site's branding configurations.
   Width	Select the width of the content area for the page (Narrow, Medium, Wide, or Full).
   Visibility	Set the page to be always visible or conditionally visible based on an expression. If Only show when is selected, the page is only visible when the entered expression evaluates to true. Otherwise the page is hidden. See visibility for more information.

3. Click ADD.
4. Reorder pages using the and arrows.

Configure content filters

By default, the Reports and Dashboards Library page shows Process HQ reports and dashboards that use base record types from any application in your environment. You can filter the content users will see in the page by selecting base record types. Only reports and dashboards that use data from the selected base record types will be visible in the Reports and Dashboards Library site page.

For example, let's say you have site for your Customer Onboarding app. With no filters applied, the Reports and Dashboards Library page contains reports and dashboards from your Marketing and Employee Management apps. To focus the content so it's relevant to your users, you can apply a filter that excludes record types that are not in the Customer Onboarding app.

Configure rule inputs

When you set up your site page and select Interface for the page Type, the interface you select can use rule inputs of any type. However, certain types of rule inputs can use URL parameters to set their value. Site pages that use these types of rule inputs will display Has rule input configurations under the interface name. When you edit the page, the Rule Input Configuration displays, which allows you to configure the rule inputs.

To link to site pages using URL parameters, use a!urlForSite().

For more information on using URL parameters, see Use URL Parameters for Site and Portal Navigation.

You can configure the following fields in this section:

Property	Description	Default
Encrypt URL parameters	Determines whether to use encrypted or plaintext URL parameters. To help keep data secure, URL parameters are encrypted by default. See Determine whether to encrypt url parameters for more information about when to use encrypted versus plaintext URL parameters.	Selected
Rule Input	The rule inputs from the selected interface. Only certain types of rule inputs that work with URL parameters will appear.	Read only
Enable in URLs	This only appears when Encrypt URL parameters is deselected. It allows you to opt in to using only the URL parameters that are safe to display in plaintext. To help keep your data secure, only enable the rule inputs that you need to use with URL parameters.	Toggled off
URL Parameter Name	The name used when constructing links to the page. You can change this if you want to rename a rule input and make sure existing links don't break, or if you just want to make the name shorter or more clear.	Rule input name
Default Value (optional)	The value to use whenever the URL doesn't provide a value. See Determine whether to use a default value for more information. The evaluated default value must be 100 characters or less. Otherwise, the default value will be ignored.	Null
Update URL when rule input values change	Determines whether to update the web address when rule input values change. For example, on page that has filters that work with URL parameters, the URL parameters in the web address will update with the selected filter value.	Selected*

*If the site object was originally created in an environment earlier than Appian 24.2, Update URL when rule input values change will be deselected by default.

Configure content filters

By default, the Reports and Dashboards Library page shows Process HQ reports and dashboards that use record types from any application in your environment. You can filter the content users will see in the page by selecting base record types. Only reports and dashboards that use data from the selected record types will be visible in the Reports and Dashboards Library site page. Dashboards containing only process KPIs will not be visible when content filters are applied.

For example, let's say you have site for your Customer Onboarding app. With no filters applied, the Reports and Dashboards Library page is cluttered with reports and dashboards from your Marketing and Employee Management apps. To focus the content so it's relevant to your users, you can apply a filter that excludes record types that are not in the Customer Onboarding app.

Add a page group

Page groups allow you to group pages under a single navigation menu item. Each page group can have up to ten pages.

Before you can start adding and configuring page groups, you must add at least one page to the site object.

To add a page group to the site:

1. In the Pages section, click ADD PAGE GROUP.

2. In the Add Page Group dialog, configure the following fields.

   Field	Description
   Title	Enter the page group title to display in the navigation bar. The title can be configured as a static string or as an expression that evaluates to a string.
   Web Address Identifier	Enter the unique URL identifier for the page group that will be a part of the URL for all pages in the group. If left blank, a random alphanumeric string will be generated.
   Icon	Select an icon to display with the page group title in the navigation bar. When using Mercury style for the header bar, the icon won't display in web browsers, but will always display in Appian Mobile. By default, the file-o icon is selected.
   Visibility	Set the page group to be always visible or conditionally visible based on an expression. If Only show when is selected, the page group is only visible when the entered expression evaluates to true. Otherwise the page group and all pages in it are hidden. See visibility for more information.

3. Click ADD.
4. In the page group card, click Add Page to add pages to the page group. Only Interface page types can be added to page groups.
5. Reorder page groups or pages within the group using the and arrows.

Delete pages and page groups

To delete a page or page group, click the icon in the page or page group.

Deleting a page group will also delete all page configurations within that group. The interface objects themselves will not be deleted.

Page and page group visibility

The icon displays to the right of the page or page group title if the Visibility option is set to Only show when.

Page group visibility settings take precedence over any visibility settings for pages in that group. This means if a user does not have access to the page group, they will not be able to see any pages in that group even if they have access to the individual pages themselves.

Page hierarchy diagram

Once you've added at least one page to your site, you can view the page hierarchy diagram by clicking the sitemap icon in the Pages section. This diagram is a visual representation of what powers your site and its pages, with each related object appearing as a node. For site pages that use a process model or a report, the diagram also shows the interface behind the corresponding start form or report. Double-click an object in the diagram to open it.

Scroll or drag to pan · ⌘+/⌘− to zoom · Esc to close

Navigation Bar

This section allows you to configure the appearance and layout of the site navigation menu.

There are two different layout options that determine the styling and positioning of your site's navigation bar:

• HEADER BAR: Displays at the top of the site and offers three different style options.
• SIDEBAR: Displays on the side of the site. Page titles display with icons.

Scroll or drag to pan · ⌘+/⌘− to zoom · Esc to close

For information on making design choices for your navigation bar, see Designing Sites and Portals.

You can configure the following fields in this section:

Field	Description	Default	More Info
Layout	Select HEADER BAR or SIDEBAR to determine the position and style of the navigation bar.	HEADER BAR	This setting doesn't apply to Appian Mobile.
Style	Select HELIUM, MERCURY, or OXYGEN to determine the header bar style.	MERCURY	Only appears when Layout is set to HEADER BAR. This setting doesn't apply to Appian Mobile.
Background Color	Set the background color for the navigation bar using a hex code or expression.	Sidebar: #2A3445 Helium: #46708c Mercury: #0f203a Oxygen: #343A40	For browsers, this is the background color of the navigation bar. For mobile, this is the color of the top and bottom navigation bars. For information about applying dark color schemes to the navigation bar, see Site Color Schemes.
Selected Page Highlight Color	Set the color used to indicate the currently active page.	Sidebar: #546686 Helium: #083d5c Mercury: #3fa7ce Oxygen: #F6AE2D	For Mercury and Oxygen style header bars, this is the underline color of the selected page. For Appian Mobile, sidebars, and Helium style header bars, this is the background color of the selected page.
Logo	Choose a logo to display in the navigation bar. Use an image with a transparent background for best results. To hide the logo, select NONE.	Appian logo	See Configuring logo and favicon images for more information.
Logo Alternative Text	Enter descriptive text for the logo to be read by screen readers. We recommend updating the default value to convey the same information as the logo, such as the organization name or text used in the logo.	Logo	This field is hidden when Logo is set to NONE.
Show site display name in navigation bar	Choose whether to display the Display Name from the Configurations section in the navigation bar.	Turned off	This setting doesn't apply to Appian Mobile.
Use uppercase capitalization for page titles	When turned on, applies uppercase letters to all page titles. If you want to control capitalization for each page title, turn this off.	Turned on for header bar layout, turned off for sidebar layout	In Appian Mobile, the page title always appears exactly as you enter it in the page's display name.
Show user menu	Choose whether to display the user menu in the navigation bar. When turned off, the user menu is hidden for users signed in via single sign-on, such as OpenID Connect, PIEE, and SAML authentication. Users signed in via LDAP or Appian authentication will still see the menu, but it will only display the user name and sign out link.	Turned on	Important: If you turn this off, make sure users have a way to sign out by configuring single logout or providing another logout method. Users can still access the user menu from other sites even when this is turned off. In Appian Mobile, turning this off will hide the profile link in the mobile menu, but nothing else will be affected.
Enable profile link in user menu	Choose whether users can access the Profile option in the user menu when they are on this site.	Turned on	Users can still access their profile from user record links and other sites even when this is turned off. For more information about profile visibility and access, see User Profile Visibility. Additional profile options are available in the Admin Console. This option is only visible when Show user menu is turned on.
Enable user settings link in user menu	Choose whether users can access the Settings option in the user menu when they are on this site.	Turned on	Users can still access settings from other sites, unless this is turned off for every site. This setting doesn't apply to Appian Mobile, since the Settings menu option in Appian Mobile only configures mobile app settings. This option is only visible when Show user menu is turned on.

Branding

This section allows you to define a consistent visual style across your site.

When you edit these configurations, the site object's branding preview automatically updates with your changes.

To ensure you are working with the most accurate representation of your interfaces, we recommend configuring the branding for your site early on in your app development. This allows you to take full advantage of the interface object Branding preview throughout your design process. When you are editing interface objects, use this menu to select the site that the interface will display in and see how your branding applies while you are designing.

For further information on configuring site branding, see Designing Sites and Portals.

You can configure the following fields in this section:

Field	Action	Default Value
Accent Color	Set the primary color for buttons, links, and other key elements. Avoid gray scale colors (black, white, and gray) as the accent color, since these are similar to colors used for interface elements. Avoid green/red colors as the accent color, since these are commonly used to indicate positive/negative values. See Configuring colors for more information.	#1d659c
Loading Bar Color	Set the color for the loading indicator. Select a loading bar color with sufficient contrast against the navigation bar color to ensure users notice it. If using a sidebar layout, select a color with sufficient contrast against the page background color used for site pages. See Configuring colors for more information.	Accent color
Favicon Image	Upload an ICO file to be used as the browser tab icon. The file must be 16x16 or 32x32 pixels and smaller than 100 KB. See Configuring logo and favicon images for more information.	Appian "a" icon
Use uppercase capitalization for button labels	Choose whether to use uppercase letters for all button labels. Turn this off if you want to control capitalization for each button component.	Turned on
Button Shape	Set the shape for all buttons in the site (Squared, Semi-rounded, or Rounded).	Squared
Input Shape	Set the shape for input, selection, and picker fields, as well as tooltips, on all pages in the site (Squared or Semi-rounded).	Squared
Dialog Shape	Set the shape for all dialogs displayed in the portal (Squared, Semi-rounded, or Rounded).	Squared
CSS Profile	If CSS profiles are available in your environment, you can set a CSS profile to apply to the site. Select Default to use whichever CSS profile is set as the default in the Admin Console, or select a specific profile. CSS profiles don't apply to Appian Mobile.	Default
Typeface	If CSS profiles are available in your environment, the typeface configured in the site's selected CSS profile displays. To change the typeface, edit the CSS profile in the Admin Console. If CSS profiles are not available in your environment, the default typeface for the environment displays. Administrators can configure the default typeface in the Admin Console.	Open Sans

Configuring colors

Each color field has three color configuration options to choose from:

• Default: The default color depends on your field.
• Hex Code: Select this option to define a hex code, or choose a color using the color picker.
• Expression: Select this option to dynamically set a color defined by an expression.
  • If an expression's output is an invalid hex code, the field will show the default color.

If you select a predefined dark color scheme, the values for the navigation bar color, selected highlight color, accent color, and loading bar color are all provided for you.

For more information on sites color schemes and color configurations, see the site color scheme design guidance.

Configuring logo and favicon images

The logo and favicon fields have four configuration options to choose from:

• Default: Select this to use the Appian logo.
• Document: Select this to use an image that is stored as an Appian document.
• Web Address: Select this to use a static image hosted on a web server or a content delivery network.
• Expression: Select this to dynamically display an image defined by an expression. The expression must point to a document, output a document ID (integer), or output a text value (web address). If an expression's output is invalid, the default image will display.

For logos, the file must be a JPG, PNG, BMP, JPEG, or GIF file that is less than 100 KB.

Branding preview

The Branding Preview is an interactive panel that allows you to visualize the navigation and branding configurations you've chosen.

It is for visual preview only and does not allow you to test functionality. It does not:

• Allow you to test the expressions, interface components, or functionality of the pages.
• Display component plug-ins. A placeholder image with a plug icon displays in their place.
• Reflect how the site will appear in Appian Mobile.

To see these settings applied to the site, save the site object and click the link under Web Address to open the site.

Troubleshoot tab

This tab allows you to view error details to help troubleshoot issues and ensure your sites are reliable. It displays up to 100 of the most recent error messages encountered by users on the site from the last 90 days.

To view more than 100 errors for a selected date range, or to search, sort, and filter them, download the site error log above the grid. This error log can display errors from the last 90 days.

Scroll or drag to pan · ⌘+/⌘− to zoom · Esc to close

Monitoring sites

Site usage and metrics

You can monitor your site by checking out site usage and metrics in your environment's logs.

Site usage is logged in <APPIAN_HOME>/logs/audit/sites_usage.csv. See Sites Usage Audit for details.

Sites metrics are logged in <APPIAN_HOME>/logs/data-metrics/sites.csv. See Sites Metrics Log for details.

Email error alerts

When users encounter errors in a site, email alerts will be automatically sent to administrators of the site object with details about the error. Click the page name to go to the site page where the user encountered the error.

Only one email will be sent per error message every hour and it is limited to 500 recipients. To see all the instances of an error, check the Troubleshoot tab in the site object or the design error log.

In order to access the system logs or the site object, you must be assigned to the Designer user role, which gives access to Appian Designer.

To receive email error alerts for a site, make sure:

• Outbound emails are turned on for the environment.
• You have Administrator permissions to the site object in that environment.

Site security

Object security is configured through role maps. By default, only the creator has access.

The following table outlines the actions that can be completed for each permission level in a site's security role map:

Actions	Administrator	Editor	Viewer
View the site	Yes	Yes	Yes
View the definition	Yes	Yes	Yes
View the security	Yes	Yes	Yes
Update the definition	Yes	Yes	No
Receive email error alerts	Yes	No	No
Update the security	Yes	No	No
Delete the site	Yes	No	No

System administrators can always access a site object, regardless of object-level permissions.

To access a site, a user must have at least Viewer permissions to the site object. To view a specific page, a user must also have visibility to the site page.

To see content in the branding preview, developers need at least Viewer permissions to the object used for the page content, such as the interface or record type.

Additionally, if your site has a Process HQ page, users will need to be members of the Data Fabric Report Creators system group. The Process HQ Users system group inherits members from the Data Fabric Report Creators system group, so report creators will automatically have access to the Process HQ workspace.

For more information, see Secure Data for Process HQ.

Site versions

Site objects have versions which allow you to view a history of all saved versions, compare versions side-by-side, and revert to previous versions.

New versions of a site are created automatically when you save changes to the site object or when you import the site from another environment. Security changes do not create new versions and are not included in version history.

You can access site versions from two places:

• The site object's settings menu in the object.
• The More menu in the toolbar of Designer.

Deleting site versions

Developers with at least Editor permissions can delete older site versions from the versions dialog. You can delete versions individually or in bulk, but you cannot delete all versions of a site object.

Considerations for configuring sites

This section provides you with guidance and tips to keep in mind while you're creating and configuring your site.

See Designing Sites and Portals for design guidelines you should follow to give your users the best user experience.

Interfaces as sites pages

Use interfaces as sites pages to create dynamic dashboards, landing pages, and custom navigation experiences for your users. For design examples and inspiration, check out our complete list of drag and drop patterns to help you craft an efficient and engaging user experience.

Only pages of type Interface can be added to page groups or use URL parameters in a!urlForSite().

Records and actions as sites pages

Configuring sites to show record news can help improve the collaboration around records. Users can collaborate on existing record news entries in sites, but not create new entries. However, records can be designed to include related actions that can generate new record entries via process.

Components that aren't affected by input shape rounding

Input shape rounding is not applied to the following UI elements:

• Layouts
• Display fields
• Actions
• Grids
• Charts
• Browsers
• Record banners

Using site display names in URLs and navigation menus

After you've created a site, the web address identifier (URL) won't automatically update if you edit the site display name or define it using an expression.

Site display names appear in the navigation menu. If you use an expression to create a site display name, that expression will evaluate whenever sites in the environment load or refresh in order for the site display name to appear in the navigation menu. To avoid your sites loading slowly, don't use long-running expressions, like queries.

Common object options

A site supports the following common design object options:

• Versioning: Sites support versioning.
• Renaming: Sites can be renamed.
• Viewing Appian design guidance: Sites support Appian design guidance.
• Object overwrite protection: Sites support object overwrite protection.

The following options are not available for sites:

• Duplicating: Sites cannot be duplicated.
• Viewing performance details: Sites do not support viewing performance details.

To view options available from the toolbar in Appian Designer, see Common view elements.

Create a site

To create a site object:

1. In your application, go to the Build view.
2. Click NEW > Site.

3. In the Create Site dialog, configure the following properties:

   Property	Action
   Name	Enter a name for the object. We recommend following the Standard Object Names convention. Not visible to end users.
   Display Name	Enter a name that will be displayed in the navigation bar and the browser tab. Visible to end users. Follow the recommended naming standard for display names.
   Web Address Identifier	Specify a unique web address identifier to use in the site URL. The identifier must be unique in the Appian environment. By default, Appian constructs this property using the Name property you entered, but you can modify the identifier as needed.
   Description	(Optional) Enter a description for the object.

4. Click CREATE.
5. Review the security and update as needed, then click SAVE.

Edit site properties

To edit the site object properties:

1. In the Build view, click the name of the site object. The object will open in a new tab.
2. In the settings menu, click Properties.

3. In the Site Properties dialog, configure the following properties:

   Property	Action
   Name	Enter a name for the object.
   Description	Enter a description for the object.

4. Click OK.

Delete a site

To delete a site object:

1. In the Build view, select the checkbox next to the object's name.
2. Click DELETE in the toolbar. System administrators can delete multiple objects at once.
3. Review the list of dependent objects before confirming the deletion. See Object Relationships for more information about the impact of deleting objects that rely on each other.

Site related resources

• Designing Sites and Portals: Learn best practices for creating functional and beautiful sites, including guidance on branding, color schemes, and page organization.
• Using Sites: Read about the end-user experience of navigating and interacting with a site.

Feedback