In Certinia PSA, a manager’s ability to see and approve timesheets is governed by the resource hierarchy. If the manager’s user record is not correctly associated with their resource record, or if the resource record is not set up as the team members’ manager in the resource hierarchy, the approval relationship will be broken, even with the correct security role.

To enforce a strict, sequential order of approvals, you must configure a single approval process with multiple steps. Each step can have its own entry criteria and a specified approver (user, role, or manager). The process will not proceed to the next step until the current step is approved, ensuring the required sequence.

For batch operations like invoicing, the ‘Batch Size’ in the Scheduled Job configuration controls how many records are processed in a single transaction. A batch size that is too large can cause governor limit issues and timeouts. Reducing the batch size allows the process to commit work in smaller, more manageable chunks, which is often the most direct way to resolve timeout errors for large data volumes.

The ‘Time Entry Method’ on the project (e.g., Time and Materials, Milestone, Fixed Price) directly controls how time is logged. If it’s set to ‘Milestone’ or another non-standard method, it may not generate standard weekly time cards for resources. This is a specific configuration point that differs from general permissions or assignment checks.

To compare budgeted vs. actual costs, you need data from multiple related objects: the Project (for the budget), and the actuals (from Time Sheets, Expenses, etc.). The ‘Project Financials’ standard report type is specifically designed for this purpose, as it provides a pre-built join between these key financial entities, allowing for direct comparison formulas in the report.

The Resource Assignment object in Certinia PSA often has a detail record (like ‘Timecard-Based Assignment Details’ or ‘Milestone-Based Assignment Details’) created alongside it. This child record has its own required fields, validation rules, and record types. An automation creating the parent Resource Assignment must also correctly create and populate the corresponding detail record, or the save will fail.

A validation rule is the standard, declarative way to enforce business logic based on record data (like Stage) and user context (like Profile). It is maintainable because the logic is centralized in the rule’s formula, scalable as it applies to all records meeting the criteria, and provides a clear error message to the user. Page layout changes can be circumvented via API, and triggers or processes that silently modify data are less transparent.

The ‘Remaining Hours’ on assignments is a managed field that is typically updated by a behind-the-scenes scheduled job (often named ‘Recalculate Assignment’ or similar), not in real-time. If this job is deactivated, fails, or is blocked, the field will not refresh. This is a common post-migration check to ensure all automated system processes are running.

For a declarative, point-to-point automation like creating a related record (Project) when an Opportunity reaches a certain stage (Closed Won), a Process Builder flow or, in modern Salesforce, a Record-Triggered Flow is the recommended tool. It allows you to define the criteria (Opportunity Stage = Closed Won) and the action (Create a Project) with field mappings, all without code. Workflow rules cannot create records, and Apex is overkill for this simple requirement.

In Certinia PSA, a manager’s ability to see and approve timesheets is governed by the resource hierarchy. If the manager’s user record is not correctly associated with their resource record, or if the resource record is not set up as the team members’ manager in the resource hierarchy, the approval relationship will be broken, even with the correct security role.0