1Implementing Compliance and Regulation Using Functional Setup Manager
Using Functional Setup Manager
This topic discusses how to use the Functional Setup Manager.
Oracle Functional Setup Manager provides an integrated, end-to-end process for functional administrators to manage the implementation and maintenance of Oracle Public Sector Compliance and Regulation services.
Business users configure features and manage setup data using the Functional Setup Manager. Subscription to offerings, enabling functional areas, opting in features, and setting up guided end-to-end tasks pertaining to the offerings are all driven through the Functional Setup Manager.
To view the Public Sector offerings and their functional areas in Functional Setup Manager:
Select Setup and Maintenance tile on the springboard.
or select theSelect a Public Sector offering from the Setup drop-down list.
The page lists all the functional areas on the left and the corresponding tasks on the right.
Documentation Help Links
You enable Help links in Functional Setup Manager during your implementation so that you can directly access related documentation. To enable Help links:
Select Setup and Maintenance tile on the springboard.
or select theSelect a Public Sector offering from the Setup drop-down list.
The page lists all the functional areas on the left and the corresponding tasks on the right.
Click View in the Task section and select . This option is turned off by default.
To view Help icons in the tasks list, select the Settings and Actions button in the header and click Show Help Icons.
For a detailed understanding of the Functional Setup Manager, see the documentation Using Functional Setup Manager.
Setting Up Transactions Using Functional Setup Manager
This topic provides the list of required tasks for the implementation of Public Sector Compliance and Regulation offerings, which are organized under the functional areas in the Functional Setup Manager (FSM).
You must complete the tasks in these task lists to add the required setup data, configuration settings, and processes that your agency will use across all Oracle Public Sector Compliance and Regulation services.
Functional Area |
Task List |
Description |
---|---|---|
Initial Users |
Define Initial Users for Public Sector |
Prepare the groundwork for defining access through roles and privileges for the users who will access your service. Tasks include running the user and role synchronization process, creating implementation users, setting the next URL target for new users, and running the Public Sector Security setup process. |
Agency Profile |
Define Foundation Data |
Set up general foundational data that will be used by the agency when conducting transactions for the community. Tasks include setting up address formats, city information, county information, country information, currencies, units of measurements, and so on. |
Define Calendars for Public Sector |
Set up the Holiday calendar for your agency to define when your agency is available for conducting business. |
|
Define Schedules |
Work schedules establish the days of the week and daily hours of operation for agency employees. For example, defining a work schedule for an inspector establishes when an inspector can be scheduled for an appointment. |
|
Define Agency |
Define fundamental information for an agency, including the agency ID, agency name, country, currency, time zone, and so on. |
|
Solution Packages |
Import Solution Packages |
Create a Process Cloud Service Proxy user and assign the necessary PSCR Proxy user role. Import Solution Packages from the Solution Package Library for Permits and Planning and Zoning applications. |
Fees and Payments |
Set Up Billing |
Set up your agency’s billing system. Tasks include defining invoice forms, setting the auto-numbering scheme, and selecting bill types. |
Set Up Payments |
Configure how payments will be processed within your agency. Tasks include setting up the payment gateway, configuring the cash drawer, defining department and agency payment processing options, and so on. |
|
Inspections |
Define Inspections |
Configure the information required for your inspection system to enable you to define, organize, and schedule inspections. Tasks include setting up assessment types, defining rating methods and passing requirements, configuring inspection calendars, and so on. |
Plan Review |
Define Plan Review |
Set up the required information for your agency to review plans associated with permit applications. Tasks include defining plan review statuses and setting up the resulting plan review decision types, such as approved, rejected, revision required and so on. |
Permit Types |
Define Permits |
Create and configure the types of permits your agency will offer. Tasks include setting up permit categories, defining permit statuses, setting up workflows and fee models, creating permit types, designing permit application forms, and so on. |
Accounting |
Define Accounting |
Set up the processing system to be used by your accounting department. Tasks include setting up accounts, funds, and ledgers as well as defining accounting events and rules. |
Digital Assistant |
Set up and configure Digital Assistant |
Create and configure digital assistants and their parameters to suit your agency. |
Agency Staff |
Define Agency Staff |
Set up the service to accommodate the information used to define and support your agency staff. Tasks include setting up business units, setting up legal addresses, creating job titles, configuring staff access, and so on. |
Public Users |
Define Public Users |
Configure how public users will interact with the implementation of your service. Tasks include defining terms of use, selecting public user options, assigning roles to define public user access, and so on. |
Analytics and Reporting |
Define Reporting for Public Sector |
Add or modify parameters associated with delivered reports to filter data per your requirements. |
GIS |
Define GIS |
Configure the integration between your service and the GIS application. Tasks include managing map profiles and mapping GIS attributes. |
System Administration |
Define Attachments for Public Sector |
Define categories and subcategories for files, such as plans and images that are attached to pages as part of the permit application process. |
Define Comments for Public Sector |
Configure the comments feature that will be used throughout the permit application process. Tasks include setting up comment categories, adding and modifying standard comments, and so on. |
|
Define Communication for Public Sector |
Delivered communication events are triggered by transactions and processes within the application. For example, scheduling an inspection triggers the "Inspection Scheduled" communication event. You can define the content and recipients of the communication events using communication templates. |
|
System Administration |
Define Lookup Values for Public Sector |
Add and change values that appear in lookup lists. Lookup lists are referenced by various fields in the application and display a static set of values from which the end user can select a value when entering information. |
Define Conditions for Public Sector |
Add, modify, or remove a dependency or contingency for completing the permit process. Conditions are defined with a severities that can affect the permit process when applied. |
|
Branding |
Define and Assign Themes |
Create custom branding themes for your agency to reflect your desired look and feel. Tasks include adding logo images, modifying header and footer colors, designing your welcome banner, and so on. Once a branding them is created, you then assign it to apply its attributes. |
Define Tiles |
Tiles are the icons that appear on the Agency Springboard and public landing pages. Users click tiles to access selected pages and transactions. You can configure which tiles appear, hide tiles, modify tile labels, and so on |
|
Define Summary Details |
Define the summary section that appears on the public landing pages. The summary section includes a summary title, summary text, and a Read More button that links either to a more detailed message that you define or to an external URL. |
|
Define Alerts |
Add, modify, and enable alert messages that will appear on the Agency Springboard and public landing pages to notify users of timely information. |
|
Planning and Zoning Application Types |
Define Planning and Zoning Application Types |
Define application groups, categories, subcategories, record statuses, fee schedules, document categories, and planning and zoning application types for agency. |
Public Hearing |
Define Public Hearings |
Define public hearing calendars and escalation path for agency. |
Incidents and cases |
Set up and configure code enforcement Incidents and cases |
Reported code enforcement incidents are inspected and violations are processed as cases. Define and manage autonumber rules for incident, case, notice, citation, and inspection. Manage inspection counts, referral bodies, time rules, corrective actions, and code references. |
Business License Types |
Define Business License Types |
Create and configure the types of business licenses your agency will offer. Tasks include setting up business license categories, defining business license statuses, setting up workflows and fee models, creating business license types, designing business license application forms, and so on. |
Migrating Data From Your Test Environment to Your Production Environment
This topic describes the utilities used to migrate setup data from your test environment to your production environment.
In your pod you have these environments:
Environment |
Description |
---|---|
Test |
The test environment is where you learn about the product, enter your setup and configuration data, and test your changes. For example, this is where you add the data for setting up your agency, create your permits, specify branding modifications for your site, and so on. |
Production |
The production environment is the environment your agency employees and your end users access to complete transactions. The production environment reflects the “finished product” of what was configured and tested in the test environment. |
After you have made changes and tested them in the test environment, you then migrate any changed metadata and setup data from your test environment to your production environment. You use the Functional Setup Manager export and import utilities to complete these tasks.
For more information on the Functional Setup Manager export and import utilities, see Using Functional Setup Manager: “Exporting and Importing Setup Data”.
For more information on managing transaction type data, see:
Oracle Public Sector Community Development: Test to Production (Doc ID 2551940.1) on My Oracle Support.