August 11, 2015, update for Project Server 2013 (KB3055018)

• New API to bulk update project custom fields to improve performance of demand management workflows.
  
• Fixes the following issues:
  • You cannot update a local custom field by using the Project Server Interface (PSI) if the field is associated with a lookup table. Additionally, you may receive a "GeneralUnhandledException" exception.
    
  • Consider the following scenario:
    • A team member adds himself or herself to an existing task.
    • The team member adds actual work to the task.
    • The team member submits the task and actual work for approval.
    • The status manager rejects both the new task request and the actual work on the task.
    In this scenario, the rejected task still appears in the timesheet. If you try to submit the timesheet before deleting the task, you receive the following error message:
    The submitted timesheet contains lines that have been rejected. Update these lines on your timesheet and then resubmit it.
  • After you unlink a project site from a project server, you cannot create a new project site by using a new name, and no project site update job is triggered.
    
  • You cannot use the QueueUpdateProject2 method in a PSI application to update values of custom fields.
    
  • Approved status updates are delayed from being applied to a project schedule of a project on a Project server until they are checked out and checked in again. Usually, status updates are applied to a project as soon as they are checked in. However, in this case, it takes an additional check-out or check-in cycle before updates are applied.
    
  • In the Project Web App Project Center, you cannot select to open or edit a project in Project Professional when you use Chrome or Firefox.
    
  • When you use a PSI application to update a project-level custom field of a project, values of calculated custom fields are blank on tasks when you view them in Project Web App.
    

Restart information

Prerequisite