能否通过API重新打开Workfront已关闭的PROJ或TSHET对象？

Great questions about integrating Workfront with your financial systems—let’s break down the answers with practical details you can use:

1. Can you reopen closed PROJ (Project) or TSHET (Timesheet) objects via the Workfront API? #

Yes, you absolutely can reopen these closed objects using the API, but there are a few critical things to account for:

• Permissions First: Your API service user needs the right access—think system admin privileges or a custom role with explicit permissions to edit projects/timesheets and modify their statuses. Without this, the API calls will fail with a permission error.
• Follow Status Workflows: Workfront enforces status transition rules set up in your instance. You might not be able to jump straight from "Closed" to "Active" if your company uses intermediate statuses (like "Pending Reactivation"). Double-check your instance’s valid status transitions for the object type first.
• API Call Example: Use the PUT endpoint to update the object’s status. For a project:

  PUT /proj/{projectID}
  Request Body: { "status": "ACTIVE" }
  

  For a timesheet:

  PUT /tshet/{timesheetID}
  Request Body: { "status": "OPEN" }
  

  Note: Status labels might be custom in your instance—use the internal status ID or the exact label string configured for your Workfront environment to avoid issues.

2. Can you temporarily reopen closed PROJ/TSHET objects for billing-adjustment hour transfers? #

This is a super common use case for financial integrations, and yes, you can absolutely implement this temporary reactivation workflow. Here’s a step-by-step approach to do it safely:

1. Verify the Current Status: First, fetch the object’s current status to confirm it’s closed (this prevents unnecessary status changes if it’s already active).
2. Reactivate Temporarily: Use the same PUT status update call from the first question to switch the project/timesheet to an active state, following your instance’s workflow rules.
3. Perform the Hour Transfer: Update the projectID field on the relevant HOUR objects via API to move the hours between projects.
4. Revert the Status: Once the transfer is confirmed successful, switch the project/timesheet back to its original closed status.

• Key Best Practices:
  • Document the Change: Add a note or use a custom field on the object to log why the status was changed (e.g., "Temporarily reopened for billing adjustment hour transfer")—this helps with audit trails and transparency.
  • Watch for Locked Timesheets: Some closed timesheets might be locked (e.g., after payroll processing). If that’s the case, you’ll need additional permissions to unlock them before reopening—check your Workfront settings for timesheet locking policies.
  • Build Error Handling: Make sure your integration checks for failures at each step. If reactivation fails, roll back any partial hour transfers to keep your data consistent.

内容的提问来源于stack exchange，提问作者Michael Ross