Public Sector Developer Guide

Public Sector Data Models
Public Sector Standard Objects
PublicSectrSltn Namespace
Public Sector APIs
REST Reference
Resources
Request Bodies
Action Plan Template Items Input
Action Plan Template Item Task Input
Action Plan Item Tasks Input
Benefit Assignment Input
Benefit Disbursements for Benefit Session Input
Benefit Disbursement for Benefit Session Input
Care Plan Input
Care Plan Task Input
Care Plan Tasks Input
Care Plan Template Associations Input
Care Plan Template Benefit Input
Care Plan Template Goal Input
Claim Collection Input
Claim Input
Claim Item Input
Complete File Upload Input
Custom Field Input
Document Input
Excluded Care Plan Task Input
External Storage Search Input
Goal Assignment Input
Initiate File Upload Input
Outbound Payments Address Input
Outbound Payments Custom Field Input
Problem Definition Input
Regulatory Transaction Fee Recompute Input
Submit Claims Input
Tax Constituent Activity Input
Tax Revenue Profile Input
Tax Activity View Input
Data Mapping Object Input
Response Bodies
Public Sector Standard Invocable Actions
Public Sector Tooling API Objects
Public Sector Metadata API Types
Public Sector Associated Objects
StandardValueSet Names and Standard Picklist Fields
Upload Files to Amazon S3
Accounting Subledger
Action Launcher
Business Rules Engine
Criteria-Based Search and Filter
Decision Explainer
Discovery Framework
Engagement
Group Membership and Households
Identity Verification
Intelligent Document Reader
Interest Tagging
Omnistudio Business REST APIs
Outcome Management Developer Guide
Record Alerts
Record Rollup Definitions
Service Process Studio
Timeline
PDF

Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

Tax Constituent Activity Input

Input for a tax constituent activity query including tax year, views, and optional additional DMO fields.
JSON Filing example
1{
2  "taxYear": 2025,
3  "views": {
4"filing": ["lineItem","participants"],
5"document": [],
6}
7}
JSON Payments example
1{
2  "taxYear": 2025,
3  "views": ["payments"]
4}
JSON Refunds example
1{
2  "taxYear": 2025,
3  "views": ["refunds"]
4}
JSON Assessments example
1{
2  "taxYear": 2025,
3  "views": ["assessments"]
4}
JSON All views example
1{
2  "taxYear": 2025
3}
Properties
Name Type Description Required or Optional Available Version
dataMappingObjects Map<String, ConnectApi.DataMappingObjectInput> Per-DMO additional fields beyond defaults. Key = DMO name (TaxFiling, TaxFilingParticipant, TaxFilingLineItem, TaxPayment, TaxRefund, TaxFilingAssessment, TaxFilingLineItemAssessment, TaxDocument, TaxDocumentItem). Value = object with fields array. Maximum 30 additional fields total. 68.0
taxYear Integer Required. The tax year to return activity for. Required 68.0
views Map<String, ConnectApi.TaxActivityViewInput> Scopes which sections are returned and, per section, which child sub-sections to expand. Map of view name to a per-view expansion object whose subViews lists the child sub-sections to expand. Allowed view keys are filings, documents, payments, refunds, and assessments. Sub-view names per view are filings = [participants, lineItems] and assessments = [lineItems]; documents, payments, and refunds have no sub-views. An empty object or omitted subViews for a view (e.g. "documents": {}) selects that view with its default sub-views. An empty or omitted map returns all views with their default sub-views. Unknown view keys are rejected. 68.0