Certinia PSA-Sysadmin Exam Dumps

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

Step-by-Step Comprehensive Detailed Explanation

Understanding the Timecard Approval Process in PSA

By default, the timecard approval process in Certinia PSA (formerly FinancialForce PSA) follows a specific hierarchy.

If the project is a billable project and the Project Manager field is filled, the Project Manager is automatically assigned as the approver for timecards.

If the Project Manager field is blank or the project is non-billable, PSA uses the resource's manager as the approver (based on the Manager field in the Salesforce User record).

How Flows Work in Assigning Approvers

If you have created a Flow to automatically assign the resource's manager as the timecard approver, it means you are trying to override the default approval process.

However, if the Assign Project Manager To Timecard Approver configuration option is enabled, PSA will still prioritize the Project Manager over the resource's manager, regardless of your Flow settings.

This would explain why submitted timecards are still being assigned to the Project Manager instead of the resource's manager.

Why the Other Options Are Incorrect

A . PSA requires that only Project Managers can approve Timecards

This is incorrect because PSA allows timecards to be approved by either the Project Manager or the Resource's Manager, depending on the project settings.

B . The process builder to assign the resource's manager is not active

While this could be a factor, the main reason is the configuration setting that forces the Project Manager to be the default approver.

Even if the Flow was working correctly, the Assign Project Manager To Timecard Approver setting would still take precedence.

How to Fix the Issue

Navigate to PSA Configuration Settings and check the Assign Project Manager To Timecard Approver setting.

If it is set to True, change it to False to allow the Flow to correctly assign the resource's manager as the approver.

Test by submitting a new timecard and verifying the assigned approver.

Reference and Verified Certinia PSA Documentation

PSA System Administration Guide: Timecard Approval Process.

FinancialForce PSA Approval Workflow: Default Approver Rules.

Understanding RPGPR (Region, Practices, Groups, Projects, and Resources) Updates:

The Current Time Period in PSA must be updated regularly to ensure accurate reporting and forecasting.

RPGPR entities are used for structuring project and resource hierarchies, making it essential to maintain updated time periods.

Options Analysis:

Option A: 'Schedule the RPGPR Maintenance Batch in PSA Administration' This is the correct answer because the RPGPR Maintenance Batch resets the Current Time Period to the default value (usually 'All Time Periods') and ensures all RPGPR records remain synchronized.

Option B: 'Manually update the Time Period on all RPGPR records' This is inefficient, error-prone, and impractical for large organizations.

Option C: 'Enable the RPGPR Time Period auto-update feature in Setup' No such direct feature exists in PSA to auto-update the RPGPR Time Period.

Steps to Schedule RPGPR Maintenance Batch:

Navigate to PSA Administration.

Locate the RPGPR Maintenance Batch option.

Configure the job to run at a set interval (e.g., daily or weekly).

Monitor the job execution via Apex Jobs in Salesforce.

PSA Sys Admin Essentials Student Guide.

Project Managers who want to display several fields prominently on the Project Lightning Page should use the FF PSA Field Summary component. This component allows users to highlight key fields related to their projects, improving visibility and accessibility within the Lightning interface.

FinancialForce PSA provides several Lightning components, but among them:

FF Field Overview: This component is not specifically designed for summarizing multiple fields in a prominent way.

FF Highlights: This component typically provides a brief summary but does not allow for multiple field customization.

FF PSA Field Summary: This is the most appropriate component, as it allows displaying multiple PSA fields prominently on the Project Lightning Page.

Thus, the correct answer is C. FF PSA Field Summary.

PSA Sys Admin Essentials Student Guide Fall 20

Understanding Permission Sets and Visibility in PSA:

In PSA, permission sets control which tabs and features a user can see.

If Kevin, a Type 1 employee, sees the Project Planner tab, he likely has a Project Manager-related permission set assigned.

Options Analysis:

Option A: 'Ensure Kevin is not assigned to the Project Manager Permission Set' Correct! The Project Manager Permission Set grants access to the Project Planner.

Option B: 'Ensure Kevin does not have a Permission Control record for the 'Project Planner View' permission' Incorrect. Permission Controls manage functional access, not UI visibility.

Option C: 'Ensure that the Project Planner is not Visible on Kevin's user profile' Incorrect. Profiles in PSA provide base access, but permission sets determine feature visibility.

Steps to Remove Project Planner Access for Kevin:

Navigate to Setup Permission Set Assignments.

Search for Kevin's assigned permission sets.

If Project Manager Permission Set is assigned, remove it.

Log in as Kevin to verify that the Project Planner tab is no longer visible.

PSA Sys Admin Essentials Student Guide.