The Project Management Workspace (PMW) is primarily designed for project managers to view and manage the projects they are responsible for. The default view, "My Projects," filters the project list to show only those projects where the logged-in user is the value in the Project Manager lookup field on the Project record. If a user is not assigned as the Project Manager on any projects, this default view will correctly display no records, leading to the reported issue.

B. The user is missing the Project Management Workspace Permission Control: If the user were missing this permission control, they would be unable to access or view the Project Management Workspace page or component at all.

C. The user is missing the PSA - Project Manager Permission Set: Lacking this permission set would result in more fundamental access errors, such as "Insufficient Privileges," preventing the user from seeing project data, rather than simply seeing an empty list.

1. Certinia PSA Documentation, "About the Project Management Workspace": This document states, "The Project Management Workspace (PMW) provides a centralized location for project managers to view and manage their projects." It further details that the default "My Projects" filter displays projects where the current user is the designated Project Manager. (Reference: help.certinia.com, Project Management > Project Management Workspace > About the Project Management Workspace).

2. Certinia PSA Documentation, "Permission Controls": This section explains that Permission Controls are used to grant or deny access to specific application features and UI elements. The "Project Management Workspace" permission control specifically governs access to the workspace tab. A user without this permission would not be able to navigate to the page. (Reference: help.certinia.com, PSA Administration > Permissions > Permission Controls).

For a user to act as an approver on any record within a Salesforce approval process, they must have the fundamental ability to view the record being submitted. This is governed by Salesforce's security model, which requires the user to have at least "Read" permission on the object in question—in this case, the "Timecard" object. Without this permission, the user cannot access the record's details to make an informed decision, and the system will prevent them from being a valid approver.

A. The approver must be in the same role hierarchy as the submitter

This is incorrect. Approval assignments can be routed to specific users, queues, or related user fields (like a manager), but there is no universal requirement for the approver to be in the submitter's role hierarchy.

C. The approver must be set up as a Delegated Approver for the submitter

This is incorrect. A Delegated Approver is a user designated to approve requests on behalf of another user who is unavailable. It is a substitution feature, not a prerequisite for being an approver.

1. Salesforce Help Documentation: In the guidelines for setting up approval processes, Salesforce explicitly states the permission requirement.

Source: Salesforce Help, "Considerations for Approval Processes"

Reference: Under the "Before You Begin" section, it is noted that "An approver must have read permission for the object they are approving." This is a platform-level requirement that applies to all objects, including Certinia's custom objects like Timecard.

2. Certinia PSA Documentation: Certinia's security model for approvers, such as Project Managers, relies on standard Salesforce permission sets which grant the necessary object permissions.

Source: Certinia PSA Administrator Guide

Reference: The permission set definitions for roles that typically approve timecards (e.g., "PSA - Project Manager" or "PSA - Resource Manager") include Read, Create, and Edit permissions on the Timecard object. This confirms that the necessary permissions are a core part of the configuration for an approver role within the Certinia PSA context.

For the Billing Event Generation process to include approved Miscellaneous Adjustments, two key criteria must be met. First, the Effective Date on the adjustment record must fall within the date range of the Time Period selected for the billing run. This ensures that only transactions relevant to the current billing cycle are processed. Second, the Transaction Category assigned to the Miscellaneous Adjustment must be explicitly listed in the BillingCategories configuration option. This setting acts as a filter, telling the system which categories of transactions are eligible for billing. If either of these conditions is not satisfied, the adjustment will be skipped.

B. This is incorrect because a user lacking this permission would be a reason for the process to fail or exclude the adjustments, not a setting required for it to succeed.

1. Certinia PSA Help Portal, "Configuration Options - Billing": This document details the BillingCategories setting, stating it is a "comma-separated list of transaction categories that are included when you generate billing events." This directly supports option C.

2. Certinia PSA Help Portal, "Billing Event Generation": This guide explains that the process selects transactions for a specific Time Period. It clarifies that transactions, including Miscellaneous Adjustments, are selected for billing based on their date (e.g., Effective Date) falling within the start and end dates of the chosen Time Period. This supports option A.

3. Certinia PSA Help Portal, "Permission Controls": The documentation on permission controls describes the "Billing - Miscellaneous Adjustments" permission. It clarifies that this permission is required to bill these adjustments. Therefore, a user not having this permission would cause the process to exclude the records, making option B an incorrect statement of a prerequisite.

When the Actuals Calculation Mode is set to "Scheduled," a batch job runs periodically to calculate and update project actuals from timecards and other transactions. If this job fails, the actuals will not be updated. The Certinia PSA application is designed to capture exceptions and errors from its asynchronous processes, such as the scheduled actuals calculation, in the "Error Logs" custom object (pse.ErrorLogc). Therefore, the correct and immediate next step for a system administrator is to check these logs to diagnose the specific error preventing the updates.

B. Navigate to "Logs", and check the details of the error in the "Message" field.for each log record: "Logs" is a generic term. The standard, specific object in Certinia PSA for capturing application exceptions from scheduled processes is "Error Logs", not a general "Logs" object.

C. Navigate to "Ag£ Logs", and check the details of the error in the "Message" field for each agg log record: "Ag£ Logs" (likely a typo for Aggregation Logs) is not a standard Certinia PSA object for troubleshooting actuals calculation failures. The designated object for this purpose is "Error Logs".

1. Certinia PSA Administration Guide: In the section "Actuals", the guide details the different calculation modes. For "Scheduled" mode, it explains that calculations are performed by a batch Apex job. The guide's troubleshooting sections consistently direct administrators to the ErrorLogc object to investigate failures in asynchronous processes. (Reference: "Troubleshooting PSA" and "Actuals" sections).

2. Certinia PSA Help Portal - Knowledge Article "Troubleshooting Project Actuals": This type of article typically outlines the standard procedure for diagnosing issues with actuals. It specifies that when using scheduled calculation, the first step after confirming the schedule is to check for corresponding records in the "Error Logs" tab for any exceptions thrown by the ScheduledActualsCalculator batch job. The Message field on the Error Log record provides the stack trace or error detail.

Certinia PSA utilizes Work Calendars to define the standard working hours and days for resources, which is fundamental for calculating capacity and utilization. The scenario explicitly outlines two distinct groups for resource planning: full-time employees and part-time employees, with the latter group being standardized to a 20-hour week for planning purposes. Therefore, the most appropriate and efficient setup is to create two Work Calendars: one to represent the standard full-time schedule and a second one to represent the standardized 20-hour per week part-time schedule. This directly aligns with the system's design and the stated management requirements.

A. Creating a calendar for each unique part-time contract is administratively burdensome and contradicts the management directive to use a standardized 20-hour estimate for planning.

C. The scenario does not provide any information that would necessitate a third, "generic flexible" work calendar. The two defined groups are sufficient to meet the requirements.

1. Certinia PSA Administration Guide, Section: "Work Calendars". This section details that Work Calendars are used to model the different working patterns within an organization, such as for full-time and part-time employees, to accurately calculate resource capacity. The guide recommends creating distinct calendars for such groups.

2. Certinia Help Portal, Article: "Setting Up Work Calendars". The documentation states, "You can create multiple work calendars to reflect the different working patterns in your organization... For example, you might have different calendars for full-time and part-time employees, or for resources in different countries." This directly supports creating one calendar for the full-time group and another for the part-time group.

The Expense Ops Edit permission is specifically designed for this scenario. It grants users the ability to edit expenses that have already been approved and are marked with "Include in Financials". This permission is intended for operational or financial adjustments before the expense is finalized through the creation of a Billing Event. It provides a controlled mechanism to correct data after initial approval but before it impacts billing and revenue recognition processes.

B. Expense Entry: This permission only allows users to create new expense records. It does not grant any rights to edit expenses, especially not after they have been approved.

C. Expense Edit: This permission allows a user to edit an expense before it has been submitted for approval. Once an expense is approved, this permission no longer applies.

1. Certinia PSA Documentation, "Permission Control Fields": This document details the specific functions of each field on the Permission Control object. It explicitly states: "Expense Ops Edit: When selected, gives users permission to edit expenses that have been approved, have 'Include in Financials' selected, but have not yet been billed."

2. Certinia PSA Documentation, "Security and Permissions": In the section covering expense management permissions, the hierarchy is explained. Expense Entry is the base level, Expense Edit allows modification pre-submission, and Expense Ops Edit is the elevated permission for post-approval, pre-billing modifications.

To determine the installed version of Certinia PSA, a system administrator must navigate to the 'Installed Packages' page within Salesforce Setup. The core application package for Professional Services Automation is named "PSA". This page provides a comprehensive list of all managed packages installed in the organization, including their publisher, version number, and installation date. While the option lists "PSA Core", this refers to the primary "PSA" package which contains the essential functionality of the application. This is the standard and correct procedure for verifying application versions within the Salesforce platform.

B. Go to Setup > Installed Packages > PS Enterprise: "PS Enterprise" is not the official name of the Certinia PSA managed package. This option refers to a non-existent or incorrectly named package.

C. Go to Setup > Installed Packaqes > FinancialForce Central: "FinancialForce Central" (now Certinia Central) is a foundational package that provides common components and shared functionality across multiple Certinia applications, but it is not the PSA application itself.

1. Certinia PSA Spring 2024 Administrator Guide: In the "Upgrading PSA" chapter, the guide instructs administrators on the prerequisite steps. It states, "Check the version numbers of the Certinia packages that you have installed. To do this, from Setup, search for and select Installed Packages." This confirms the navigation path and the need to check the package list.

2. Certinia PSA Spring 2024 Release Notes: Page 5, under the section "Packages in this Release", lists the official package names. The primary package is explicitly named "PSA". This document validates that "PSA" is the correct package to check for the application version.

The Timecard Entry Ul Personal is a hierarchy-type custom setting within Certinia PSA. Hierarchy custom settings are designed to be personalized at different levels: Organization, Profile, and User. The system checks for a setting at the most specific level (User) first, then moves up to Profile, and finally to the Organization default. This allows individual users to have unique configurations for their Timecard Entry user interface, such as their preferred default view (e.g., Day, Week, Month), which overrides any broader settings defined at the profile or organization level.

A. Search Resources Global: This is a List custom setting, not a hierarchy setting. List settings contain static, organization-wide data and do not support user-specific overrides.

C. Assignment Settings: While this is a hierarchy custom setting, it controls core business logic and permissions for assignments. It is managed at the organization or profile level to enforce consistent processes, not for individual user personalization.

1. Certinia PSA Administration Guide, "Custom Settings" section: This guide details the different types of custom settings used in PSA. It specifies that settings with "Personal" in their name, such as TimecardEntryUIPersonal, are hierarchy settings intended for user-level configuration. The guide contrasts this with List settings like SearchResourcesGlobal which are for org-wide data.

2. Salesforce Platform Developer I Documentation, "Custom Settings" module: As Certinia PSA is built on the Salesforce Platform, its use of custom settings adheres to Salesforce standards. The official Salesforce documentation defines hierarchy custom settings as those that "use a built-in hierarchical logic that lets you personalize settings for specific profiles or users." This directly supports why Timecard Entry Ul Personal can be user-specific. (Reference: Salesforce Help & Training, "Custom Settings Overview").

3. Certinia PSA Technical Reference, "PSA Custom Settings Definitions": This technical document lists all custom settings, their API names, and their type (List or Hierarchy). It explicitly classifies pse.TimecardEntryUIPersonal as a Hierarchy setting and ffrr.SearchResourcesGlobal as a List setting, confirming the technical basis for the answer.

The majority of Certinia PSA's operational and business logic settings are managed through two primary mechanisms. Configuration Groups are a core PSA feature that allows administrators to define and apply sets of rules and behaviors to different parts of the organization, such as regions, practices, or groups. This provides granular control over features like timecards, expenses, and project management. Custom Settings are a Salesforce platform feature heavily utilized by PSA to store application-wide or profile-level configurations that control global behavior, integrations, and foundational logic. The PSA Administration page acts as a central console but primarily links to these and other setup areas.

C. PSA Administration Page: This page is a central hub for administrative tasks and a starting point for configuration, but it is not where the majority of the detailed business logic settings are directly stored or managed.

1. Certinia PSA Administration Guide, "Configuration Options". This section details how Configuration Groups are used to control the behavior of PSA for different sets of users, covering settings for timecards, expenses, project management, and more. It establishes Configuration Groups as a primary area for settings.

2. Certinia PSA Administration Guide, "Custom Settings". This section lists and describes the numerous custom settings used by PSA to control application-wide behavior. It explicitly states that PSA uses custom settings to store a variety of configuration options, confirming it as a major settings area.

3. Certinia PSA Administration Guide, "Administration Tab". The documentation describes this tab as a central console providing access to various administrative functions, health checks, and links to other setup pages, rather than being the direct location for the bulk of configuration settings itself.

The visibility of the "Availability" column in the Certinia PSA Resource Planner is primarily controlled by two factors. First, the Resource Planner interface is customizable, allowing users to select which columns are displayed. If the "Resource Availability" column is not selected in the user's display settings, it will not appear. Second, visibility is governed by Salesforce's security model. If the managers' user profiles or assigned permission sets lack Field-Level Security (FLS) read access to the underlying field that populates the Availability column, they will be unable to see it, regardless of other settings.

A. Utilization Ermine checkbox is deselected under Utilization custom settings: This setting (likely a typo for "Engine") controls the calculation of utilization data. Disabling it would prevent new availability data from being generated, but it does not directly hide the column from the UI.

1. Certinia PSA Professional Services Automation Documentation, "Resource Planner Overview": This documentation details the user interface components of the Resource Planner, including the ability for users to customize the displayed columns. It specifies that users must select fields to display, which directly supports option B. (Reference: Access the official Certinia Documentation portal and navigate to the Resource Planner section for administrators).

2. Salesforce Documentation, "Field-Level Security": As Certinia PSA is built on the Salesforce platform, it adheres to its security model. Salesforce's core documentation explains that if a user does not have read access to a field via their profile or permission set, that field is hidden from them in all contexts, including list views, reports, and custom application pages like the Resource Planner. This principle directly supports option C. (Reference: Salesforce Help & Training, "Object Permissions" and "Field-Level Security").

3. Certinia PSA Professional Services Automation Documentation, "Utilization Settings": This guide explains the function of the Utilization custom settings, including the main engine switch. Its purpose is described as enabling or disabling the background calculations for utilization, scheduled hours, and availability. The documentation does not state that disabling this setting removes the corresponding columns from the Resource Planner UI. (Reference: Access the official Certinia Documentation portal and search for "Utilization Settings" in the Administrator guides).