Overview of Public Landing Pages

The public landing pages give members of the public access to agency services. There are two separate public landing pages, one for anonymous users (guests), and one for registered users who have signed in.

Public user landing pages have elements such as the global header with a welcome message and the Apply and Guide buttons, alerts, search fields, attention needed card, action tiles, map, and so forth.

The registered user landing page showing the Apply, Guide buttons, global search, Quick links and Account summary buttons, attention needed card, the landing page cards in the More actions section and the map.

Landing Page Configuration

The elements on landing pages vary depending on how you configure the pages.

For information on configuring landing pages, see Setting Up the Landing Page for Anonymous Users and Setting Up the Landing Page for Registered Users.

For information on setting up alerts to appear on the landing pages, see Defining Alerts and Working with Ad Hoc Communications.

Tiles on the Anonymous User Landing Page

Also known as guests, anonymous public users are residents, business owners, contractors, and so on, who have not signed in or are not registered. From the anonymous user landing page, they can perform common tasks such as starting an application, accessing an interactive guide that provides recommendations for application types, or accessing an interactive map of the city.

As delivered, the anonymous user landing page includes these tiles:

Page Element	Description
Public Reports	Provides access to all public reports available for the anonymous user.
Estimate Fees	Provides access to the Estimate Fees page, where the user can choose an application type and estimate fees for an application.
Explore Your City	Provides access to a map where the anonymous user can search for and view property details, including applications related to the property.
Report an Issue	Starts the process for reporting a code enforcement issue. During the reporting process, the public user identifies the type of issue, provides the issue location, describes the issue, and answers any additional questions that the agency has configured. See Reporting Issues.
Make CE Payments	If you click the tile as an anonymous user, you are prompted to sign in. Once signed in, you can make online payments for code enforcement fees. See Making Code Enforcement Payments

Tiles on the Registered User Landing Page

Registered users are residents, business owners, contractors, contacts with application access, and so on, who are registered in the system. When a registered user is signed on, the landing page can include additional options related to the registered user’s interactions with your agency.

By default, the registered user landing page has a global header with a welcome message and the Apply and Guide buttons. The Apply button provides access to a page where the user can choose an application type and then start an application. The Guide button provides access to a questionnaire. The user provides information about a project, and the guide uses that information to recommend application types.

Note:

Your agency defines the guide questionnaire using Oracle Intelligent Advisor. If your agency is not using Oracle Intelligent Advisor, this tile will not appear.

The questionnaire comes from the Oracle Intelligent Advisor policy model that you specify for the Permits offering, if one exists. If there's no offering-level policy, the questionnaire comes from the agency-level Oracle Intelligent Advisor policy model. 

As delivered, the registered user landing page includes all the tiles that are available to anonymous users and these additional tiles:

Menu Link	Description
Request Inspections	Displays the page where you can request one or more inspections for a transaction. Registered public users can also add inspections from their Inspections list page by selecting the Inspections tile.
Track My Issues	View status and other information about issues that the user reported while signed in. See Tracking Issues.
Resolve an Issue	Claim responsibility for an issue, and perform actions such as viewing notices or appealing a citation. See Resolving Issues.
Deposit Accounts	Displays a list of the user’s deposit accounts, including the account number, name, and status, in addition to the available balance. From the list, the user can access deposit account details.
Deposit Account User Invites	Displays a list of the invites that the user has received to manage deposit accounts. It displays the account number and name, email address and invite status. From the list, the user can access the invite details. Owners of deposit accounts can void the invite. Invited users can accept or decline the invite.

Attention Needed Cards

Attention needed cards provide information about applications at a glance with recommended actions. Only information for a registered user's own applications is reflected in the cards. Applicants and contacts with application access can take the recommended actions to clear any outstanding issues.

Applicants can view a all of their applications on their Applications list page, including the ones for which they are contacts. Agencies must enable full application access for contacts to see these applications in the list.

These attention needed cards may be available after your agency runs a process to identify the issues to bring to your attention:

Card	Description
Make a Payment	Provides the fees information at a glance and a button to go directly to the payment page when the registered user has a pending payment. Applicants see the total amount due, number of applications with fees due, and a button to navigate to the Make Payments page, where they can review and select application fees for payment. For more information, see Making Payments.
Failed Inspections	Indicates that an active application has at least one failed inspection and no reinspections have been scheduled yet for the failed inspection. The Reinspect button opens the registered user's My Inspections page with a filter to show only failed inspections for active applications that need to be scheduled for reinspection. For more information, see Reviewing Inspection Details.