Certinia PSA-Sysadmin Exam Dumps

Understanding Backlog and Utilization Calculation in PSA:

Backlog Calculation: Tracks the remaining work (revenue) on projects. It includes scheduled and unscheduled backlog.

Utilization Calculation: Measures how effectively billable resources are utilized, distinguishing between historical and scheduled utilization.

Options Analysis:

Option A: 'Feature Console' Incorrect. The Feature Console is used to enable/disable PSA features, not schedule backlog/utilization calculations.

Option B: 'PSA Administration' Correct! PSA Administration is used to schedule backlog and utilization calculations.

Option C: 'PSA Admin App' Incorrect. The PSA Admin App provides access to administrative tools but is not used for scheduling calculations.

Steps to Schedule Backlog and Utilization Calculation:

Navigate to PSA Administration Tab.

Locate Schedule Backlog Calculation and Schedule Utilization Calculation.

Configure the scheduling parameters (e.g., frequency, time period).

Save and monitor scheduled jobs in Apex Jobs in Salesforce.

PSA Sys Admin Essentials Student Guide.

Understanding Self-Nomination for Resource Requests

PSA allows resources to express interest in upcoming projects using the Self-Nomination feature.

This feature can be enabled through a Custom Setting, which then allows the 'PSA Resource Self-Nomination' Lightning component to be used.

How to Enable Self-Nomination for Resource Requests

Step 1: Navigate to Setup in Salesforce.

Step 2: Search for Custom Settings and select it.

Step 3: Find and enable 'Self-Nominate for Resource Request'.

Step 4: Open the Lightning App Builder and edit the Resource Request Detail Page.

Step 5: Add the 'PSA Resource Self-Nomination' Lightning component to the page.

Step 6: Save and activate the page.

Why This Works?

The 'Self-Nominate for Resource Request' setting allows resources to nominate themselves for work using the Lightning component.

By adding this component to the Resource Request Detail Page, eligible resources can easily apply for available projects.

PSA Sys Admin Essentials Student Guide Fall 20 (2).pdf, Page 65.

Recommended PSA Admin Best Practices

FinancialForce PSA Community: Provides product updates, discussions, and Q&A.

Trailhead Modules: Helps admins stay certified and learn new skills.

Release Previews & Webinars: Covers upcoming changes, best practices, and new tools.

PSA Documentation: Includes release notes, feature console changes, and support guides.

Why Not Other Options?

Option A (SF User Group Instead of Trailhead): Trailhead is directly tied to PSA product updates, while SF User Groups focus more on general Salesforce topics.

Option C (FinancialForceX Summit Events): While valuable, they are not the primary source for ongoing PSA updates.

PSA Sys Admin Essentials Student Guide Fall 20 (2).pdf, Page 134-137.

Editing approved Timecards in PSA is restricted by permissions. However, if no Billing Events are associated with the timecard, an administrator with the correct permission control can make changes.

Timecard Ops Edit Permission Control:

Allows users with this permission to edit approved timecards when necessary.

Ensures that financial records remain accurate while allowing flexibility for adjustments.

System Administrator Profile Does NOT Automatically Grant This:

The System Administrator profile alone does not provide access to modify approved timecards.

Additional Timecard Ops Edit permission control is required.

Why PSA Restricts Editing Approved Timecards:

If Billing Events have been created, Timecards are locked to prevent financial discrepancies.

Only unbilled timecards can be edited under special permissions.

PSA System Administration Guide

To limit expenses company-wide for a particular type of expense, the best solution is:

Use the Expense Limit record -- This allows defining limits based on Expense Type at a global region level.

Set the maximum allowable amount per transaction, period, or user.

Ensure that the Expense Limit applies across all users and regions to enforce company-wide restrictions.

Option B (Using the RPG record) is incorrect because it applies only to specific regions or practice groups, not company-wide.

Option C (Using the Resource Record) is incorrect because it applies at an individual user level rather than enforcing a global limit.

Thus, the correct answer is A.

PSA Sys Admin Essentials Student Guide Fall 20