Feature Requests

An additional recipe / drawer variant to allow for a mid-size nav drawer icons and labels stacked vertically on top of one another

Multiple clients have requested the ability to jump to a specific page within search results. The paginator currently requires paging through each one. "When I do a search for say 2019 permits and it gives me a list of 2200. I can choose how many I have on a page (say 100), but it would also be nice if after I sort it by permit # to be able to choose which page to skip to instead of having to go through each page to get to the page I'm now working with."

Having a recipe that is a focused on a vertical filter experience within a drawer. This is a use case in a few apps and divisions. Here are some examples below. Some requirements We can discuss these as a board and tweak as needed hideable (drawer) expandable sections (should be able to control whether it's expanded or collapse by default) multiselect capabilities (checkboxes) a way to see all options in a section vs truncate (default to 5) clear controls for sections a space for counts per option configurable to show options as checkboxes or a multiselect (or single select) field a footer for either submitting filters or just closing depending on whether this is shown in a modal context. Optional

We have a number of different old notification centers and the one referenced in the Forge Documentation that would be launched from the App Bar isn't available as code (as far as I know). It would be nice to have one built that we could use https://forge.tylertech.com/components/omni/notifications/

From Corp Dev Forum Discussiona re: Admin Center types of messages and display: Examples include: 1) Informative (such as new features) 2) Acknowledgement 3) Action Requested 4) Action Required (task)

I also call this an add list with optional ability to reorder. It's essentially a list with multiple columns that may contain form fields. It may be a fixed list or have the ability to add new rows/items to the list. Here's some documentation for the pattern. Notes many of these will be configurable (on/off) reordering add new row may have multiple columns column headers for the list can be able to remove rows cells may contain input fields https://www.figma.com/file/92FoOvy0tkUbTXx9Wc0ix4/D%26I-Design-System?type=design&node-id=2388%3A5574&mode=design&t=5e8ThIAPh7ha4EN1-1

We have a lot of features that leverage some kind of regular schedule such as email delivery or data pulls. There are a few areas where we have duplicately implemented a schedule UI. It would be nice to put together a general use Schedule UI pattern. Requirements frequency (hours/days/weeks/etc) days of the week number of occurrences start on date end after built-in validation for numbers outside of expected ranges (etc hours in a day)

This is a pattern that we use in a few places where we build a "rule" that controls a behavior. Some uses cases are filters, triggers, alerts, and rules for formatting. It can get pretty complex so I'm not sure how far we want to go with the nesting but there's a pretty clear structure to these UIs such as [object] [operator] [value] with some logic structures for blocks of arguments.

We have in a few places patterns for showing filters across the top of a page in a "Quick filter" way. This leverages a combination of chips, popovers, and various type controls. Here's a few different patterns from our apps, I'm sure there are others in other divisions. Very similar to our multiselect fields but with a more configurable experience for when the control is open beyond a simple list Some Notes Need to show a summary of chosen options in the chip when closed popover will have some custom content depending on the control, mostly it will be a richer experience than a multiselect as it will have some advanced filtering settings such as "contains" or "equals" ability to add additional filters optionally. Some areas may configure some to show by default in an empty state.

When searching a term that provides no results in the autocomplete dropdown, configuration for easily providing empty text such as "No results found" in the dropdown would be a nice addition. This would help inform users when their search does not yield any results rather than not showing a dropdown at all, or having to manually provide a static option with this text as many do currently. Issue Added : https://github.com/tyler-technologies-oss/forge/issues/514