2.1 Regulatory Authorization Types & Application Intake

2.1 Regulatory Authorization Types & Application Intake

Public Sector Solutions (PSS) digitizes the end-to-end management of Licenses, Permits, and Inspections (LPI) by transforming disparate paper-based workflows into unified, automated digital services. At the foundation of every licensing regime lies the requirement to categorize government authorizations, capture complex applicant details, enforce jurisdictional pre-requisites, and collect mandatory documentation through modern digital portals.

Understanding the structural components of the intake data model—and how OmniStudio automation binds constituent requests to enterprise records—is a heavily tested domain on the AP-222 examination.

---

The Regulatory Authorization Type Object: Catalog Master

In Salesforce Public Sector Solutions, the RegulatoryAuthorizationType standard object acts as the centralized catalog and configuration blueprint for all credentials issued by an agency. Rather than creating custom objects or schemas for every new permit or license, administrators define authorization archetypes declaratively within this single master table.

Every commercial building permit, salon operating license, retail liquor license, mobile food vendor permit, or medical practitioner registration is represented as a distinct RegulatoryAuthorizationType record.

Key Architectural Attributes

• Name & Description: The formal legal title of the authorization (for example, Commercial General Contractor Class A, On-Premises Tavern Liquor License, or Cosmetology Establishment License).
• Regulatory Authority (RegulatoryAuthorityId): A master lookup linking the authorization type to the governing board, commission, or municipal department that exercises statutory jurisdiction (such as the State Board of Cosmetology or the Department of Building and Safety).
• Regulatory Authorization Category: A standard picklist that categorizes the nature of the credential, including License, Permit, Certification, and Registration. This categorization drives reporting, search indexing, and security policies.
• Validity Duration & Unit: Defines the lifespan of the credential once granted (such as 1 Year, 2 Years, or 6 Months), which automated flows use to compute expiration dates.
• Renewal Cycle Type: Specifies whether the authorization requires annual renewal, biennial recertification, or represents a one-time transactional permit (such as a residential demolition permit).
• Prerequisite Authorizations: Enables administrators to define dependency trees where an applicant must possess an active foundational credential (such as a Journeyman Plumber License) before applying for an advanced authorization (Master Plumbing Contractor License).

[!NOTE] Exam Trap Alert: RegulatoryAuthorizationType contains the catalog metadata definition of what can be issued. It never represents an individual citizen's actual granted credential or a submitted filing. Confusing RegulatoryAuthorizationType with BusinessLicense or BusinessLicenseApplication is one of the most frequent errors on the AP-222 exam.

---

Application Intake Data Model: Preliminary vs. Formal Applications

Public sector agencies process millions of constituent interactions annually. To prevent administrative backlogs and avoid charging constituents non-refundable statutory fees for non-viable ventures, Public Sector Solutions implements a two-tier intake model: Preliminary Applications and Formal Applications.

┌────────────────────────────────┐         ┌────────────────────────────────┐
│   Preliminary Application      │         │   Business License Application │
│   (PreliminaryApplicationRef)  │───────> │   (IndividualApplication)      │
│   • Pre-screening & Triage     │ Qualified│   • Formal Filing & Legal PII  │
│   • Zoning / Land Use Check    │ Applicant│   • Fee Settlement             │
│   • No Statutory Filing Fee    │         │   • Inter-Agency Review Engine │
└────────────────────────────────┘         └────────────────────────────────┘

1. Preliminary Applications (PreliminaryApplicationRef)

A preliminary application serves as an eligibility screener, feasibility assessment, or zoning pre-check before a constituent commits significant capital. For example, an entrepreneur intending to open a microbrewery can submit a preliminary inquiry detailing their proposed parcel number and operational concept. The municipal planning team conducts a high-level review to verify whether municipal zoning bylaws permit alcohol production at that location.

• Low Friction: Collects minimal identifying data without requiring extensive documentation.
• Cost Efficiency: Eliminates upfront statutory application fees for requests that face immediate disqualification.
• Triage Routing: Generates early guidance for the citizen, indicating specific variance hearings or environmental assessments they must complete before formal submission.

2. Formal Applications (BusinessLicenseApplication / IndividualApplication)

Once pre-screening is complete, the constituent submits a formal application. In the underlying PSS schema, this is represented by BusinessLicenseApplication (often surfaced in configurations and console layouts as IndividualApplication for personal professional licenses).

The application record serves as the transactional engine of the intake lifecycle, managing reviews, document verifications, inspections, and fee settlements.

Application Status Lifecycle Stages

1. Draft: The constituent has initiated an online application via Experience Cloud but has not yet executed the final attestation or submitted the package.
2. Submitted: The application has been electronically signed and entered the agency's intake queue.
3. Under Review / In Review: Intake specialists or automated triage flows are evaluating applicant disclosures and verifying supporting documentation.
4. Pending Information / Incomplete: Agency staff have issued a formal request for information (RFI) or rejected an uploaded document, pausing statutory review clocks.
5. Pending Inspection: Desk review is complete; the record is routed to field services for pre-licensure physical site or equipment inspection.
6. Approved: All statutory criteria, inspections, and fee assessments have been satisfied.
7. Rejected / Denied: The applicant failed statutory qualification criteria or zoning mandates, triggering formal notification and appeal rights.
8. Withdrawn: The constituent voluntarily canceled the application prior to final adjudication.

Constituent Entity Modeling: Person Accounts vs. Business Accounts

A critical design decision on the AP-222 blueprint is choosing the correct applicant entity architecture:

• Person Accounts: Used when the license applicant is an individual human practitioner acting in their personal professional capacity (such as an aesthetician, private investigator, master electrician, or physician). Person Accounts combine standard Account and Contact capabilities into a single record, maintaining personal identification numbers (SSN/ITIN), personal addresses, and individual credential histories.
• Business Accounts: Used when the applying entity is a registered commercial legal entity (such as an LLC, C-Corporation, Partnership, or Non-Profit). The Business Account (Account) represents the enterprise, while individual authorized signatories, corporate officers, and licensed qualifiers are linked as related Contact records using AccountContactRelation.
• Operating Locations (Location & AssociatedLocation): A commercial entity often operates across multiple physical sites. Public Sector Solutions links the applying Business Account to standard Location records using the AssociatedLocation junction object. This allows an agency to distinguish between the corporate headquarters and the physical storefront being licensed.

---

Guided Citizen Intake via OmniScript on Experience Cloud

Public Sector Solutions delivers citizen-facing digital intake through OmniStudio OmniScripts deployed onto authenticated or guest Experience Cloud sites. OmniScripts provide a pixel-perfect, responsive, step-by-step wizard that abstracts the underlying CRM complexity away from constituents.

┌───────────────┐     ┌───────────────┐     ┌───────────────┐     ┌───────────────┐
│ Step 1:       │     │ Step 2:       │     │ Step 3:       │     │ Step 4:       │
│ Identity &    │────>│ Entity &      │────>│ Operating     │────>│ Specific      │
│ Applicant     │     │ Structure     │     │ Location      │     │ Criteria      │
└───────────────┘     └───────────────┘     └───────────────┘     └───────────────┘
        │                                                                 │
        ▼                                                                 ▼
┌───────────────┐     ┌───────────────┐     ┌───────────────┐     ┌───────────────┐
│ Step 8:       │     │ Step 7:       │     │ Step 6:       │     │ Step 5:       │
│ Confirmation  │<────│ Attestation & │<────│ Dynamic Fee   │<────│ Document      │
│ & Tracking    │     │ Signature     │     │ Calculation   │     │ Checklists    │
└───────────────┘     └───────────────┘     └───────────────┘     └───────────────┘

Best-Practice OmniScript Step Architecture for LPI Intake

1. Applicant Identity & Profile Verification: Verifies the logged-in constituent's identity. If an authenticated user is applying on behalf of a business, an Integration Procedure queries existing AccountContactRelation records to confirm corporate signing authority.
2. Business Entity Structure: Captures legal enterprise structure, Secretary of State filing numbers, Federal Employer Identification Numbers (FEIN), Doing Business As (DBA) names, and ownership percentages.
3. Operating Location & Premise Details: Captures physical parcel identifiers, building suites, zoning codes, and lease agreements. Integrates with mapping APIs or address validation web services via HTTP Actions in Integration Procedures.
4. Authorization-Specific Questionnaires: Dynamic conditional elements display questions tailored to the selected RegulatoryAuthorizationType. For example, selecting a Restaurant Food Service Permit triggers questions regarding commercial grease traps, seating capacity, and liquor service, whereas a Retail Boutique Permit skips these sections.
5. Required Document Uploads: Integrates with Document Checklist Items, allowing applicants to upload PDFs or images with real-time file validation.
6. Dynamic Fee Calculation: Calls the Business Rules Engine (BRE) via an Integration Procedure to evaluate Expression Sets, calculating real-time application and processing fees based on applicant inputs (such as square footage or employee headcounts).
7. Legal Attestation & Electronic Signature: Presents statutory declarations under penalty of perjury. Captures digital signatures, applicant IP addresses, and submission timestamps for evidentiary auditability.
8. Confirmation & Status Dashboard: Generates a unique tracking reference number and redirects the citizen to their Experience Cloud application tracker FlexCard.

Save-for-Later Architectural Pattern

Complex commercial applications often require gathering architectural drawings, financial disclosures, and corporate resolutions over multiple weeks. Public Sector Solutions supports the native OmniScript Save for Later capability for authenticated Experience Cloud users.

• When an applicant saves their session, OmniScript stores the intermediate JSON state in an OmniScriptSavedSession record.
• Constituents can resume intake seamlessly from desktop or mobile devices without losing draft data.
• Guest users cannot utilize secure Save-for-Later without authenticating, ensuring sensitive business data remains protected.

---

Required Documents Mapping per Regulatory Authorization Type

Regulatory compliance mandates that applications cannot be adjudicated without mandatory evidentiary proof. Public Sector Solutions automates document governance through the Document Checklist framework.

Document Requirement Architecture

1. Document Checklist Type (DocumentChecklistType): Defines the standardized category of document required across the agency (for example, Government-Issued Photo ID, Certificate of General Liability Insurance, Site Floor Plan, or State Tax Clearance Certificate).
2. Document Requirement Association: Administrators map DocumentChecklistType records to specific RegulatoryAuthorizationType entries. A Nightclub Entertainment Permit might require four mandatory document types, whereas a Sidewalk Cafe Permit requires two.
3. Automated Instantiation: When an applicant submits a BusinessLicenseApplication or progresses through the intake OmniScript, an automated Flow or Integration Procedure instantiates individual DocumentChecklist items linked to the application.
4. Verification Status Tracking: As documents are uploaded, internal reviewers verify each item using dedicated console components, transitioning individual document statuses across Pending, Accepted, or Rejected (with applicant-facing rejection reasons).

┌──────────────────────────────────────┐
│     RegulatoryAuthorizationType      │
│     e.g., Commercial Restaurant      │
└──────────────────┬───────────────────┘
                   │ Enforces Requirements
                   ▼
┌──────────────────────────────────────┐
│      DocumentChecklistType           │
│  • Certificate of Liability ($1M)    │
│  • Commercial Kitchen Floor Plan     │
│  • Food Manager Certification        │
└──────────────────┬───────────────────┘
                   │ Instantiates on Submission
                   ▼
┌──────────────────────────────────────┐
│     DocumentChecklist (Instance)     │
│  Linked to BusinessLicenseApplication│
│  Status: Pending Review / Accepted   │
└──────────────────────────────────────┘

---

AP-222 Exam Strategy: Core Scenarios & Traps

• Scenario 1: Sole Proprietorship vs. Corporation Intake: When designing an intake flow for individual contractors who work under their own Social Security Numbers, always select Person Accounts. If the customer is an incorporated entity with employees, select Business Accounts linked to authorized signatories via AccountContactRelation.
• Scenario 2: Avoiding Fee Waste with Preliminary Applications: If an exam question describes high volumes of citizen applications being rejected due to immutable municipal zoning rules after paying non-refundable fees, recommend implementing PreliminaryApplicationRef on the citizen portal to validate zoning compatibility before full intake.
• Scenario 3: Declarative Document Requirements: If an agency needs different required documents for Residential Building Permits versus Commercial High-Rise Permits, do not create custom document junction objects. Configure standard DocumentChecklistType associations linked to each respective RegulatoryAuthorizationType.