Since upgrading Orchestrate from version 7.71 or older, the user can only complete some tasks from the actuals tab of edit tasks, but cannot change other tasks to different statuses e.g. Ready To Start.
When a task (operation) is planned on a resource, which is on a view that publishes to SFDC, the actuals will only have a status option to complete the tasks. The tasks on the plan that have all the different task status options available occurs because they are planned on a resource, which is part of a view that does not publish to SFDC.
We recommend using Orchestrate SFDC Access Evo, which has more enhancements than classic SFDC.
For example, when you migrate to SFDC Access Evo, Orchestrate version 7.72 and above offers within the System Settings section in SFDC, two new settings:
Filter by Released Order Status.
Filters the tasks that you've published to SFDC and visible in SFDC by whether the orders for the tasks have status Released.
2. Filter by Key Task Attribute.
Filters the tasks that you've published to SFDC and visible in SFDC by whether the tasks have the Key Task attribute selected in the Attributes tab in Orchestrate.
Also, SFDC Access Evo already offers displaying the operations by start date. As an admin user on Access Evo, with SFDC, you can now force to start 'Not Ready To Start Operations. SFDC Access Evo uses the UseSetupStatuses parameter in the SFDC parameters table to control task statuses.
In Orchestrate version 7.73, SFDC Access Evo also contains an enhancement on the SFDC stored procedure that controls the updating of ready to start tasks for all completed tasks.