Salesforce Project Management Software by Aprika
A new version of Mission Control (version 1.82) will be released on the AppExchange on Friday 28th August 2026. This notification has been issued to existing Mission Control users. It contains an overview of the new features available with this release, along with instructions on how to upgrade to the new version.
This release includes a number of new features, along with some enhancements to existing functionality, including:
Let’s get stuck into the detail…
The Cash Flow Report provides insight into the flow of cash coming into the business from the work being delivered across Projects. This differs from the Revenue Recognition report, which provides insight into when you can recognise the revenue based on the actual delivery of the work. The Cash Flow Report data is based on when Invoices are raised.
To access the Cash Flow Report, you will need to navigate to the Management Pad on the Mission Control Console. You will then need to click the ‘View Report’ button for the Cash Flow Report Tile, as shown below.
There are various attributes to the Cash Flow Report, which can be used to control the data displayed. Each of these attributes is explained in more detail below.
There are a number of settings that can be adjusted to control how the cash flow data is presented, these include:
All of these settings are persistent and will remember the settings each individual User set when last using the Cash Flow Report, with the exception of the Start Date, which defaults to Today.
The Cash Flow Chart provides a visual representation of the data displayed within the Cash Flow Table. The Bar Chart shows the Cash Flow values plotted against the Date Source.
The data will be stacked based on the ‘Group By’ setting. In the example above it is being grouped by Project Owner.
You are able to toggle the Chart to be displayed / hidden based on individual User preference. This is controlled by the ‘Hide Chart’ / ‘Display Chart’ toggle located in the top right corner of the page.
When the Chart is displayed, the User will see the ‘Hide Chart’ toggle.
When the Chart is hidden, the User will see the ‘Display Chart’ toggle.
This setting will be persistently remembered for each User.
The Cash Flow Table provides tabular insight into the Projects and their cash flow across the period of the report.
In the example above, the cash flow data is being grouped by Project Owner.
The fields displayed on the left-hand-side of the Cash Flow Table are configured via a Field Set on the Project Object called ‘Cash Flow Report’. By default, the fields included within the Field Set are:
The Cash Flow Table will support a maximum of 10 Fields and will use the first 10 Fields included within the Field Set.
The Cash Flow Table can be exported to a CSV File by clicking the CSV icon located in the top right section of the page, as shown below.
Clicking this icon will download a CSV file with a file name that is formatted like MC_Cash_Flow_Report_YYMMDD.csv.
The Cash Flow Filters can be accessed by clicking the Filter icon located in the top right section of the page, as shown below.
Clicking the icon will open the Cash Flow Filters modal, enabling you to configure any filters required from Project Fields.
You are able to adjust the Filter Logic (e.g. 1 AND 2, 1 OR 2, 1 AND (2 OR 3)). Filters can be saved using the Pre-set Filter feature and shared with other Users.
The Cash Flow data will be sourced differently, depending on the Project’s Billing Type and Billing Cycle.
| Billing Type | Billing Cycle | |||
| Manual | Milestone | Periodic | Retainer | |
| Fixed Price | Historical periods will be based on Invoice Billing Events using the ‘Invoice Date’ and ‘Amount’
The remaining value (e.g. ‘Project Budget’ – ‘Amount Invoiced’) will be allocated to the Period for the Project ‘End Date’ |
Historical periods will be based on Invoice Billing Events using the ‘Invoice Date’ and ‘Amount’
Future Period values will be determined using the Milestone ‘Invoice on Completion’ field being TRUE and the Milestone ‘End Date’. If ‘Invoice Amount’ != Null, use this value, otherwise use ‘Milestone Budget’, otherwise use ‘Hours Scheduled Value (Billable)’
|
N/A | Historical periods will be based on Invoice Billing Events using the ‘Invoice Date’ and ‘Amount’
Future Period values will be determined using the ‘Retainer Amount’, ‘Periodic Billing Frequency’ and ‘Periodic Billing Next Date’. Values will be reported for each applicable Period within the range of the ‘Periodic Billing Next Date’ and ‘End Date’ |
| Fixed Price + Expenses | Historical periods will be based on Invoice Billing Events using the ‘Invoice Date’ and ‘Amount’
The remaining value (e.g. ‘Project Budget’ + (greater value between ‘Anticipated Project Expenses’ & (‘Actual Project Expenses (Billable)’ + ‘Pending Project Expenses (Billable)’) – ‘Amount Invoiced’)) will be allocated to the Period for the Project ‘End Date’
|
Historical periods will be based on Invoice Billing Events using the ‘Invoice Date’ and ‘Amount’
Future Period values will be determined using the Milestone ‘Invoice on Completion’ field being TRUE and the Milestone ‘End Date’. If ‘Invoice Amount’ != Null, use this value, otherwise use ‘Milestone Budget’, otherwise use ‘Hours Scheduled Value (Billable)’ + (greater value between ‘Anticipated Milestone Expenses’ & (‘Actual Milestone Expenses (Billable)’ + ‘Pending Milestone Expenses (Billable)’)
|
N/A | Historical periods will be based on Invoice Billing Events using the ‘Invoice Date’ and ‘Amount’
Future Period values will be determined using the ‘Retainer Amount’ + Expenses ‘Amount Claimed’ where ‘Invoiced’ = FALSE, ‘Periodic Billing Frequency’ and ‘Periodic Billing Next Date’. Values will be reported for each applicable Period within the range of the ‘Periodic Billing Next Date’ and ‘End Date’ |
| Time & Materials | Historical periods will be based on Invoice Billing Events using the ‘Invoice Date’ and ‘Amount’
The remaining value (e.g. the lower value between ‘Project Budget’ and (‘Hours Scheduled Value (Billable)’ + ‘Material Costs Scheduled’ + (greater value between ‘Anticipated Project Expenses’ & (‘Actual Project Expenses (Billable)’ + ‘Pending Project Expenses (Billable)’) – ‘Amount Invoiced’)) will be allocated to the Period for the Project ‘End Date’
|
Historical periods will be based on Invoice Billing Events using the ‘Invoice Date’ and ‘Amount’
Future Period values will be determined using the Milestone ‘Invoice on Completion’ field being TRUE and the Milestone ‘End Date’. The value will be based on the greater value between ‘Hours Scheduled Value (Billable)’ & ‘Hours Completed Value (Billable)’ + (greater value between ‘Anticipated Milestone Expenses’ & (‘Actual Milestone Expenses (Billable)’ + ‘Pending Milestone Expenses (Billable)’
|
Historical periods will be based on Invoice Billing Events using the ‘Invoice Date’ and ‘Amount’
Future Period values will be determined using the ‘Periodic Billing Frequency’ and ‘Periodic Billing Next Date’. The value will be based on the greater value between ‘Hours Scheduled Value (Billable)’ & ‘Hours Completed Value (Billable)’ + (greater value between ‘Anticipated Milestone Expenses’ & (‘Actual Milestone Expenses (Billable)’ + ‘Pending Milestone Expenses (Billable)’
|
N/A |
| Controlled on Milestones | Historical periods will be based on Invoice Billing Events using the ‘Invoice Date’ and ‘Amount’
Future Period values will be based on the following rules, depending on the ‘Milestone Billing Type’:
Fixed Price The remaining value (e.g. ‘Milestone Budget’ – ‘Amount Invoiced’ will be allocated to the Period for the Milestone ‘End Date’
Fixed Price + Expenses The remaining value (e.g. (‘Milestone Budget’ + (greater value between ‘Anticipated Milestone Expenses’ & (‘Actual Milestone Expenses (Billable)’ + ‘Pending Milestone Expenses (Billable)’) – ‘Amount Invoiced’)) will be allocated to the Period for the Milestone ‘End Date’
Time & Materials The remaining value (e.g. the lower value between ‘Milestone Budget’ and (‘Hours Scheduled Value (Billable)’ + ‘Material Costs Scheduled’ + (greater value between ‘Anticipated Milestone Expenses’ & (‘Actual Milestone Expenses (Billable)’ + ‘Pending Milestone Expenses (Billable)’) – ‘Amount Invoiced’)) will be allocated to the Period for the Milestone ‘End Date’
|
N/A | N/A | N/A |
| Deposit to T&M | N/A | N/A | Historical periods will be based on Invoice Billing Events using the ‘Invoice Date’ and ‘Amount’
Future Period values will be determined by using the ‘Periodic Billing Frequency’ and ‘Periodic Billing Next Date’. The value will be based on the unused balance of Deposit Billing Events, and deducting the ‘Hours Scheduled Value (Billable)’ until there’s no Deposit remaining, the value of the expected T&M Invoices will be based on the Time Log ‘Hours Scheduled Value (Billable)’ + the Expense ‘Amount Claimed’ where ‘Invoiced’ = FALSE
|
N/A |
| Retainer to T&M | N/A | N/A | N/A | Historical periods will be based on Invoice Billing Events using the ‘Invoice Date’ and ‘Amount’
Future Period values will be determined by using the ‘Retainer Amount’, ‘Periodic Billing Frequency’ and ‘Periodic Billing Next Date’. Values will be reported for each applicable Period within the range of the ‘Periodic Billing Next Date’ and ‘End Date’. For each Period, the value will be based on the Retainer Amount plus (‘Hours Scheduled Value (Billable)’ + Expense ‘Amount Claimed’ where Invoiced = FALSE) – ‘Retainer Amount’
|
The Mobile App Action Pad provides a mobile-friendly version of the Action Pad for Users to access their To Do list via the Salesforce Mobile app.
The User is able to access the following functionality:
Details of each feature is included below.
The Action Pad provides Users with access to a list of Actions, and associated Checklist Items. There are a number of filter options to select from, including:
Actions and Checklist Items will be included in the list based on the following criteria:
Action Start Date <= Date
Action End Date >= Date
Action Start Date is empty
Action End Date is empty
User’s Role = Action Owner or Contributor or Checklist Item Owner
Project Template = FALSE
Project Archived = FALSE
Action Status != Cancelled or On Hold or Complete
To complete an Action, the User can click the Checkbox icon located on the left hand side of the Action.
When the User sets this field to TRUE, the Action Status field will be automatically updated to Complete.
The Checkbox will become disabled, and the Status value will show Complete.
To complete a Checklist Item, the User can click the Checkbox icon located on the left hand side of the Checklist Item.
When the User sets this field to TRUE, the Checklist Item Status field will be automatically updated to Complete.
The Checkbox will become disabled, and the Complete Checklists / Total Checklists summary will update to show completion progress.
For each Action included in the list, you will see a row as illustrated by the image below:
Users are able to log time to any Action included in the list. Each of the time logging features are explained below:
| Button/Icon | Function |
 |
Clicking this +15m link will increase the Hours Completed box by 0.25 |
 |
Clicking this +1h link will increase the Hours Completed box by 1.00 |
 |
The Hours Completed box identifies the number of hours you want to log. This can be entered manually or you can use the +15m or +1h links to increment |
 |
The money bag icon indicates whether the Time Log will be created as Billable or Non Billable. If the icon is Green it will be Billable. Click the icon to toggle to a Red icon to make it Non Billable. If the Action ‘Non Billable Indicator’ field is TRUE, the icon will be Red by default and you will not be able to toggle to Green. |
 |
The pencil icon allows you to open a modal to add more information relating to the Time Log, such as Time Long Notes, Time Log Type, etc. |
 |
The cancel icon allows you to cancel the draft Time Log if you no longer want to submit it |
 |
The clock icon allows you to use the Start/Stop time tracking function. If the Clock is Green, you can click it to start tracking time. If it’s Red (it will appear at the top of the list), you can click it to stop tracking time. |
Saving Time Logs
To save your Time Logs, you will need to click the Save Icon, which is in the top right section of the Component, as shown below.
Start/Stop Time Tracking
When you click the Green Clock icon, it will start tracking time for that Action. The Action will appear at the top of the list with a Red Clock icon. This indicates that you are currently tracking time for that Action. You will also see the length of time that has been tracked.
To stop the timer, you need to click the Red Clock icon. Once you’ve done this, you’ll receive a confirmation notification that the timer has been stopped.
At this point, your Time Log has not been saved. You can now choose to toggle the Billable / Non Billable icon and/or click the pencil icon to add more information. To save the record, you need to click the Save icon in the top right.
The fields displayed for the Action & Checklist Item are controlled by Field Sets.
Action
By default, the Action record will display the following fields:
The first field in the Field Set will be displayed in the grey box. The remainder of the fields will be displayed in the sub-section, ordered as they appear in the Field Set.
You can use the ‘Mobile Action Pad Fields’ Field Set on the Action Object to control which fields are displayed on the Mobile App Action Pad for Actions.
Checklist Item
By default, the Checklist Item record will display the following fields:
You can use the ‘Mobile Action Pad Fields’ Field Set on the Checklist Item Object to control which fields are displayed on the Mobile App Action Pad for Checklist Items.
The Purchase Order Manager is a Lightning Web Component that enables Users to manage a Purchase Order, Purchase Order Items and Expenses all within one space. This page is accessed by clicking the New or Edit buttons on the Purchase Order Object.
Instead of having to create a Purchase Order, then go to the Related Tab to create the individual Purchase Order Items, this page provides the ability to view, create, edit and delete them all from one place.
You are able to customize the fields included in each of the sections using Field Sets, as outlined below:
Purchase Order
To control which fields appear in the Purchase Order section of the page, you can use the ‘Purchase Order Manager’ Field Set on the Purchase Order Object.
By default, the following fields are included in this Field Set:
To access the Field Set go to Setup > Object Manager > Purchase Order > Field Sets.
Purchase Order Item
To control which fields appear in the Purchase Order Item section of the page, you can use the ‘Purchase Order Manager’ Field Set on the Purchase Order Item Object.
By default, the following fields are included in this Field Set:
To access the Field Set go to Setup > Object Manager > Purchase Oder Item > Field Sets.
Expense
To control which fields appear in the Expense section of the page, you can use the ‘Purchase Order Manager’ Field Set on the Expense Object.
By default, the following fields are included in this Field Set:
To access the Field Set go to Setup > Object Manager > Expense > Field Sets.
When running a ‘Retainer to T&M’ Project, you can optionally leverage the ‘Retainer Rollover’ functionality. This enables you to rollover the unused balance of a ‘Retainer’ Billing Event to be consumed in future periods.
For example, Acme Technologies LLC provides managed services to their customer Rip Curl. This work is delivered on a ‘Retainer to T&M’ basis. Each week, Acme raises a ‘Retainer’ invoice for $5,000. Rip Curl has agreed if Acme undertakes work that exceeds the $5,000 retainer, they can invoice for the additional work on a T&M basis. Acme has also agreed with Rip Curl that if they do not use the full retainer amount, the unused balance can carry over to be used in future periods, up to a maximum of 4 periods.
When configuring the Project in Mission Control for Rip Curl, Acme sets the following fields:
Billing Type: Retainer to T&M
Periodic Billing Frequency: Weekly
Retainer Amount: $5,000
To allow unused balances to be rolled over, Acme also sets the following fields:
Enable Retainer Rollover: TRUE
Retainer Rollover Periods: 4
Retainer Rollover Consumption Method: Oldest to Newest
The table below illustrates which Billing Event will be consumed first based on these rollover settings.
| Invoice Date | Amount | Balance Remaining | Consumption Order |
| 7 Sep 26 | $5,000 | $5,000 | Used fifth |
| 31 Aug 26 | $5,000 | $5,000 | Used fourth |
| 24 Aug 26 | $5,000 | $5,000 | Used third |
| 17 Aug 26 | $5,000 | $5,000 | Used second |
| 10 Aug 26 | $5,000 | $1,250 | Will be used first as has a Balance Remaining and is the oldest Billing Event within the ‘Retainer Rollover Periods’ window |
| 3 Aug 26 | $5,000 | $1,000 | Will not be used as it falls outside of the ‘Retainer Rollover Periods’ window |
Alternatively, for another client, Quiksilver, Acme has chosen to consume the unused balances with a different consumption method. They have chosen to rollover for 3 months, but want to consume the newest unused balance first.
When configuring the Project in Mission Control for Quiksilver, Acme sets the following fields:
Billing Type: Retainer to T&M
Periodic Billing Frequency: Monthly
Retainer Amount: $5,000
To allow unused balances to be rolled over, Acme also sets the following fields:
Enable Retainer Rollover: TRUE
Retainer Rollover Periods: 3
Retainer Rollover Consumption Method: Newest to Oldest
The table below illustrates which Billing Event will be consumed first based on these rollover settings.
| Invoice Date | Amount | Balance Remaining | Consumption Order |
| 1 Aug 26 | $5,000 | $2,250 | Will be used first as has a Balance Remaining and is the newest Billing Event within the ‘Retainer Rollover Periods’ window |
| 1 Jul 26 | $5,000 | $3,750 | Used second |
| 1 Jun 26 | $5,000 | $2,000 | Used third |
| 1 May 26 | $5,000 | $1,800 | Used fourth |
| 1 Apr 26 | $5,000 | $1,250 | Will not be used as it falls outside of the ‘Retainer Rollover Periods’ window |
| 1 Mar 26 | $5,000 | $1,000 | Will not be used as it falls outside of the ‘Retainer Rollover Periods’ window |
The Clone button on a Phase allows you to clone (make a copy of) of a Phase and all related Milestones, Actions, Contributors & Checklist Items, saving them to the existing Project or to a new Project. Before the records are cloned, you are able to make changes to the records so they are relevant to the new Project if required.
To Clone a Phase, go to the Phase page and click the ‘Clone’ button.
Make the desired changes for the new Phase, Milestones and Actions, and click the Clone Phase button.
Note: If the Phase you are cloning relates to a skills-based Project, you will also be able to view and edit the Skills associated to each Action.
Within the ‘Clone Settings’ section, you are able to specify the following settings:
Adjust Action Dates: Defaults to Today. When changed, all Start Date and End Date values across the related records will be adjusted accordingly.
Clone Checklist Items: Defaults to TRUE. If TRUE, all Checklist Items related to Actions will also be cloned.
Clone Contributors: Defaults to FALSE. If TRUE, all Contributors related to Actions will also be cloned.
The Phase Clone page provides customers with the ability to select which fields are visible in the Phase field sections of the page. Each section (e.g. Phase, Milestone, Action) is controlled by a Field Set as outlined below:
Phase Object: Phase Clone Fields
Milestone Object: Phase Clone fields
Action Object: Phase Clone Fields
Each Field Set has a set of default fields selected, as outlined below.
| Phase | Milestone | Action |
| Phase Name
Project Phase Owner Status Phase Budget Exclude from Client Page Exclude from Status Report |
Milestone Name
Milestone Owner Status Milestone Budget Exclude from Scheduler Exclude from Timesheet Milestone Deadline Milestone Notes Invoice on Completion Invoice Amount |
Action Name
Action Owner Start date End Date Action Notes Status Hours Scheduled – Billable Hours Scheduled – Non Billable |
This provides Customers with the ability to add and remove fields to suit their specific requirements.
When raising Billing Events against a Project, you can include a Customer’s Purchase Order on the Invoice PDF. By default, there is one Purchase Order that can be specified via the ‘Purchase Order #’ field on the Project record.
However, where your Customer may issue multiple Purchase Orders for a single Project, you are able to raise separate Billing Events for each of the applicable Purchase Orders.
For example, Acme Technologies is working on a Project for Rip Curl. Rip Curl has provided Acme with a Purchase Order for the Project. However, as the project progresses, it’s determined that a Change Request is required and Rip Curl issues a separate Purchase Order to cover the additional cost.
The ‘Purchase Order’ Object allows you to create Purchase Orders, specifying the ‘PO Direction’ of the PO using the following values:
Note: where ‘PO Direction’ is left empty, it will be assumed to be a Supplier Purchase Order.
You are able to associate Milestones and Expenses to an individual Purchase Order by populating the ‘Customer Purchase Order’ field.
When Billing Events are raised and multiple Customer Purchase Orders are being used on a Project, the following generation logic is applied, based on the Billing Type & Billing Cycle combinations.
| Billing Type | Billing Cycle | |||
| Manual | Milestone | Periodic | Retainer | |
| Fixed Price | User will populate the ‘Customer Purchase Order’ field manually when creating the Billing Event | If the ‘Customer Purchase Order’ field on the Milestone is populated, the ‘Customer Purchase Order’ field on the Billing Event will be populated with the same value | N/A | By default this will reference the ‘Purchase Order #’ on the Project. User can manually populate the ‘Customer Purchase Order’ field on the Billing Event if required |
| Fixed Price + Expenses | User will populate the ‘Customer Purchase Order’ field manually when creating the Billing Event | If the ‘Customer Purchase Order’ field on the Milestone is populated, the ‘Customer Purchase Order’ field on the Billing Event will be populated with the same value | N/A | By default this will reference the ‘Purchase Order #’ on the Project. User can manually populate the ‘Customer Purchase Order’ field on the Billing Event if required |
| Time & Materials | Multiple Billing Events may be generated based on whether or not the Milestones and / or Expenses have been related to different Purchase Orders | Multiple Billing Events may be generated based on whether or not the Milestones and / or Expenses have been related to different Purchase Orders | Multiple Billing Events may be generated based on whether or not the Milestones and / or Expenses have been related to different Purchase Orders | N/A |
| Controlled on Milestones | On the Billing Generator, when the Project has related Purchase Orders with a ‘PO Direction’ of Customer, the User will need to specify the Purchase Order first
The Billing Event Items will only be displayed based on the Milestone matching the specified ‘Customer Purchase Order’ |
N/A | N/A | N/A |
| Deposit to T&M | User will populate the ‘Customer Purchase Order’ field manually when creating the ‘Deposit’ Billing Event | N/A | Multiple Billing Events may be generated based on whether or not the ‘T&M’ Time Logs relate to Milestones and / or ‘T&M’ Expenses have been related to different Purchase Orders | N/A |
| Retainer to T&M | N/A | N/A | N/A | By default this will reference the ‘Purchase Order #’ on the Project. User can manually populate the ‘Customer Purchase Order’ field on the Billing Event if required
Multiple Billing Events may be generated based on whether or not the ‘T&M’ Time Logs relate to Milestones and / or ‘T&M’ Expenses have been related to different Purchase Orders |
When a Billing Event contains a value in the ‘Customer Purchase Order’ field, then the Purchase Order’s ‘Amount Invoiced’ field will be updated. When a Billing Payment is created, then the Purchase Order’s ‘Amount Paid’ field will be updated.
Within Mission Control, there are numerous ‘Feature Pages’, such as the Scheduler, Whiteboard, etc. that display records in certain colours.
These colours can be controlled by the following settings:
Customers can choose to override the above settings for individual Feature Pages using the ‘Feature Page Colour Settings’ functionality. This can be found on the Control Pad of the Mission Control Console.
You can leverage any Picklist Field on the Action Object to control the colour of records displayed on these Feature Pages.
For example, in the image below, the Customer has chosen to leverage the ‘Action Type’ field. They have set the Hex Colour for each picklist value.
For each Picklist Value, you are able to set the Hex Colour for the Bar and the Font. For each selection, you will see a preview on the right hand side.
They have selected which Feature Pages they want these colour settings to be applied to.
Now, when their Users are using these Feature Pages, the colours will be controlled based on these Feature Page Colour Settings.
Above is an example of the Scheduler leveraging the colour settings.
Above is an example of the Project Grid leveraging the colour settings.
When using the Feature Page Colour Settings, the order of priority over the colour controls will be applied as follows:
Where a setting doesn’t apply, the next setting will be applied.
There are a number of enhancements that have been applied to the Gantt Chart. Details of each enhancement are included below.
Previously you were able to add 3 additional fields to the Data Table of the Gantt Chart. This limit has now been increased to 10 fields.
You can choose to add 10 additional fields in the Data Table that you need to view. From the Control Pad of the Mission Control Console, within the Gantt Chart Settings Tile, you can specify up to 10 fields for each layer, including:
Below is an example of the settings within the Gantt Chart Settings Tile:
Once you’ve set these values on the Control Pad, you can then choose to add them from the Gantt Chart by ensuring the ‘Custom 1’, ‘Custom 2’, Custom 3’, ‘Custom 4’, etc. settings are set to TRUE within the Gantt Chart Settings.
Note: This can be done by each individual User or centrally on the Gantt Chart Settings Tile on the Control Pad by using the Gantt Chart Settings Override feature.
These additional fields will appear on the right-hand side of the Data Table, as shown below.
Note: To prevent the Data Table expanding across the screen and restricting access to the Data Timeline, the Data Table will have a scroll feature enabling you to scroll left to right within the Data Table to view all of the fields.
In version 1.80 the ‘Enable Role Forecast Gantt’ feature was released. This enabled Customers to view Role Forecasts on the Gantt Chart. In that initial release, Users could choose whether to view the Actions (Project WBS) or Role Forecasts. This functionality has been enhanced to now provide the following four options:
There is no impact when viewing one individual Project, but when viewing multiple Projects you previously had to choose to view Actions or Role Forecasts across all Projects. With the introduction of the two additional options, each Project will be able to display the appropriate records.
The above Gantt Chart illustrates a view of some Projects showing Actions, and others showing Role Forecasts. This enables you to get a full view of demand across both datasets.
A new Tab has been added to the Client Read Only page.
If you create Requirements & User Stories and wish to share them with your Client via the Client Read Only Page, you can configure the ‘Requirements’ Tab to be displayed.
The image above shows the list of Requirements related to the Project on the left-hand side of the Tab. When the eye icon is clicked, the individual Requirement will be displayed on the right-hand side, along with any related User Stories.
To include the Requirements Tab on the Read Only Page, you will need to ensure the ‘Display Requirements Tab’ field on the Project is set to TRUE.
You will need to configure a Sharing Rule for the Program Object, as outlined below.
Object: Program
Step 1: Read Only Page
Step 2: Guest user access, based on criteria
Step 3: Created By ID not equal to . (e.g. full stop / period)
Step 4: Share with Read Only Site Guest User
Step 5: Read Only
Note: The Sharing Rule needs to be created for the Program Object rather than the Requirement Object due to the Master-Detail relationship between Programs and Requirements.
By default, the following fields are displayed for the Requirement record view:
You can add/remove fields from this view through the ‘Read Only Page: Requirement Fields’ Field Set on the Requirement Object.
You can access the Field Set by going to Setup > Object Manager > Requirement > Field Sets > Read Only Page: Requirement Fields.
By default, the following fields are displayed for the User Story record view:
You can add/remove fields from this view through the ‘Read Only Page: User Story Fields’ Field Set on the User Story Object.
You can access the Field Set by going to Setup > Object Manager > User Story > Field Sets > Read Only Page: User Story Fields.
A number of minor enhancements have been made to various features. Each enhancement is detailed below.
The Log Time Component can be added to Lightning Pages for other Objects. For example, you may want to add the Log Time Component to the Case Page to enable your Customer Success Reps to log time against a Project.
There are a variety of Lookup Fields on the Log Time Component that enable Users to select which records the Time Log should relate to. These Lookup Fields include:
If your host Object contains a Lookup to any of these Objects, you can leverage parameters on the Component to pre-load these field values.
For example, Acme Technologies has added a Lookup Field on the Case Object, allowing their Customer Success reps to select the Project they want to log time against when working on a customer’s Case. They enter the API Name of the Field into the Log Time Parameter that has been added to the Case Lightning Page, as shown below.
The Project Lookup Field on the Case can be populated by the Customer Success Rep as shown below.
With this field added as a parameter to the Log Time Component, when the Customer Success Rep clicks the ‘Log Time’ Tab, the Project is automatically populated.
The Fields populating the Parameters must be related. For example, you will receive an error if you try to populate the Action field with an Action that does not relate to the Project that is being populated.
In order to provide Users with greater flexibility around when they process Timesheet Approvals, new persistent settings have been added to control which Time Logs are displayed when needing approval.
The Picklist Field in the above image provides 3 options to control the data that is displayed.
The picklist value will be persistently remembered between page visits for each User.
A new Setting has been added to the ‘Time Log Information Modal – Custom Fields’ section of the Timesheet Settings. This new Setting enables Customers to hide the ‘Non Billable’ displayed on the Time Log Information Modal.
The image above shows where you can find the ‘Hide Non Billable’ Setting.
When this Setting is set to TRUE, the Non Billable field highlighted in the image above will be hidden from the Modal.
There is functionality within Mission Control that performs updates to Role records and related Team Assignment records when the ‘Active’ field on a Team is set to TRUE or FALSE.
When a Team ‘Active’ field is set to FALSE, the following updates occur:
When a Team ‘Active’ field is set to TRUE, the following updates occur:
Should you wish to disable these updates from happening, you can do so via the following setting:
Disable Adjustment of Master Team Settings
This Setting can be found in the Project Automation Settings Tile on the Control Pad of the Mission Control Console.
Mission Control includes two external end points that enable Customers to generate the Gantt / Scheduler PDFs and the Gantt Chart PNGs.
Should you wish to disable these features, you can do so via the following setting:
Disable Export Services
Check this box to disable all export services relating to the Gantt / Scheduler file exports
When set to TRUE, the following features will be hidden:
This Setting can be found in the Project Automation Settings Tile on the Control Pad of the Mission Control Console.
The Overview Tab on the Project Overview now provides you with options to enable Pagination of the Work Breakdown Structure. The following options are accessible within the Settings Modal on the Overview Tab.
These settings allow you to enable pagination and control how many top level (e.g. Phase / Milestone) records are displayed per page.
This section includes details of any component changes within the package. This includes changes to existing fields as well as any new fields, validation rules, buttons / actions, Apex Classes, Components, etc. that have been added to the solution as part of this release.
IMPORTANT: We recommend you thoroughly review all of these components. To take advantage of the enhancements within this release, you may need to:
If you are not using the Permission Sets included with Mission Control, we recommend you check the Field Level Security for all of these fields and accessibility to the various Components to ensure all appropriate Profiles/Permission Sets have the required access.
| Field | Field Type | Comments | New/Existing |
| Field 4 | Text (255) | The field for the Specified Object to display on the Gantt | New |
| Field 5 | Text (255) | The field for the Specified Object to display on the Gantt | New |
| Field 6 | Text (255) | The field for the Specified Object to display on the Gantt | New |
| Field 7 | Text (255) | The field for the Specified Object to display on the Gantt | New |
| Field 8 | Text (255) | The field for the Specified Object to display on the Gantt | New |
| Field 9 | Text (255) | The field for the Specified Object to display on the Gantt | New |
| Field 10 | Text (255) | The field for the Specified Object to display on the Gantt | New |
| Field | Field Type | Comments | New/Existing |
| Retainer Rollover Periods | Picklist | Identifies how many Billing Periods a ‘Retainer’ Billing Event can rollover to be consumed by future activity beyond its initial period. Applicable to ‘Retainer to T&M’ Projects only | New |
| Enable Retainer Rollover | Checkbox | Set to TRUE if you want your ‘Retainer’ Billing Events to rollover into future Billing Periods. Applicable to ‘Retainer to T&M’ Projects only | New |
| Retainer Rollover Consumption Method | Picklist | Identifies whether Time Logs and Expenses should be allocated to the newest or oldest ‘Retainer’ Billing Event with a balance. Applicable to ‘Retainer to T&M’ Projects only | New |
| Display Requirements Tab | Checkbox | Identifies if this Tab should be available on the Client Overview Page | New |
| Field | Field Type | Comments | New/Existing |
| PO Direction | Picklist | Identifies whether this is a PO relating to a Supplier or a Customer. If empty, will be considered ‘Supplier’ | New |
| Amount Invoiced | Currency (16, 2) | Identifies how much of the Purchase Order has already been invoiced to the Customer | New |
| Amount Paid | Currency (16, 2) | Help Text adjusted to:
PO Direction = Supplier or Null: Identifies the ‘Amount Claimed’ value of all related Expenses
PO Direction = Customer: Identifies the ‘Amount Paid’ value of Billing Payments from all related Billing Events |
Existing |
| Customer Purchase Order # | Text (100) | Identifies the client’s purchase order number for this Purchase Order | New |
| Field | Field Type | Comments | New/Existing |
| Customer Purchase Order | Lookup (Purchase Order) | Identifies the Customer Purchase Order this Milestone should be billed against | New |
| Field | Field Type | Comments | New/Existing |
| Hours Scheduled Value (Billable) | Currency (16, 2) | This field calculates the Scheduled Value (Billable) of this Contributor by multiplying the Contribution Billable with the applicable Hourly Rate | New |
| Hours Scheduled Value (Cost) | Currency (16, 2) | This field calculates the Scheduled Value (Cost) of this Contributor by multiplying the Contribution Total with the applicable Hourly Rate | New |
| Hours Completed Value (Billable) | Currency (16, 2) | This field calculates the Completed Value (Billable) of this Contributor by multiplying the Hours Completed – Billable with the applicable Hourly Rate | New |
| Hours Completed Value (Cost) | Currency (16, 2) | This field calculates the Completed Value (Cost) of this Contributor by multiplying the Total Hours Completed with the applicable Hourly Rate | New |
| Hours Remaining Value (Billable) | Formula (Currency 16, 2) | This field calculates the Remaining Value (Billable) based on Hours Scheduled Value (Billable) – Hours Completed Value (Billable) | New |
| Hours Remaining Value (Cost) | Formula (Currency 16, 2) | This field calculates the Remaining Value (Cost) based on Hours Scheduled Value (Cost) – Hours Completed Value (Cost) | New |
| Field | Field Type | Comments | New/Existing |
| Customer Purchase Order | Lookup (Purchase Order) | Identifies the Customer Purchase Order this Expense should be billed against | New |
| Field | Field Type | Comments | New/Existing |
| Customer Purchase Order | Lookup (Purchase Order) | Identifies the Customer Purchase Order this Billing Event relates to | New |
| Purchase Order # | Formula (Text) | Identifies the Customer’s Purchase Order # for this Billing Event | New |
The following Components have been included or updated in this Release.
| Component Type | Component Name | Description |
| Apex Class | CashFlowReport | Required to use the Cash Flow Report |
| Apex Class | MobileActionPadController | Required to use the Mobile App Action Pad |
| Apex Class | PurchaseOrderPageController | Required to use the Purchase Order Manager |
| Apex Class | phaseCloneController | Required to use the Phase Clone page |
| Apex Class | ReadOnlyRequirementsController | Required to use the Requirements Tab on the Client Read Only Page |
| Visualforce Page | PurchaseOrderPage | Required to use the Purchase Order Manager |
| Visualforce Page | phaseclone | Required to use the Phase Clone page |
| Custom Tab | Cash Flow Report | Required to use the Cash Flow Report |
The following Validation Rules have been included or updated in this Release. It is recommended you review each Validation Rule and determine whether you wish for the rule(s) to be active or inactive.
| Object | Rule | Description | Active |
| Project | Validate Retainer Rollover Settings | Ensures the Retainer to T&M Rollover Configuration Settings are correct | TRUE |
| Project | Prevent Enable Retainer Rollover | Prevents Enable Retainer Rollover being set to TRUE if Billing Type does not equal Retainer to T&M | TRUE |
| Expense | Expense Cant Relate To Customer PO | Ensure the Expense does not relate to a Customer Purchase Order | TRUE |
| Expense | Ensure Customer PO Matches Milestone | Ensure the Customer Purchase Order matches the Purchase Order set on the Milestone | TRUE |
| Expense | Expense Cant Relate To Supplier PO | Ensure the Expense does not relate to a Supplier Purchase Order | TRUE |
| Milestone | Milestone Cant Relate To Supplier PO | Ensure the Milestone does not relate to a Supplier Purchase Order | TRUE |
| Billing Event | Billing Event Cant Relate To Supplier PO | Ensure the Billing Event does not relate to a Supplier Purchase Order | TRUE |
| Purchase Order | Must Contain Customer Purchase Order | Ensure the Customer Purchase Order # field contains a value if PO Direction = Customer | TRUE |
Mission Control will be made available based on the following release schedule.
Note: Due to the ongoing 2GP Migration (communicated July 17th), the release process will be different than normal for 1.82.
Initial Go Live: 28th August 2026
Available for manual upgrade from the AppExchange to 2GP Orgs.
For 1GP Orgs, please reach out to [email protected] for assistance with the 2GP upgrade.
Sandbox Org Upgrade
There will be no automated Sandbox Upgrade. To review in a Sandbox prior to the Production Org Upgrade, please follow the steps below based on 1GP or 2GP status:
1GP: Reach out to [email protected] for assistance with the 2GP upgrade
2GP: Available for manual upgrade from the AppExchange
Production Org Upgrade: 26th September 2026
Automatic upgrade to all Production Orgs
To identify whether you are on 1GP or 2GP, go to Setup > Apps > Packaging > Installed Packages > Mission Control and check the ‘Packaging Model’ number.
To manually upgrade to the new version of Mission Control in your organisation, please follow the steps below:
We have pre-recorded the ‘What’s New’ webinar to provide further information on how to get the best out of the new features. To access this webinar, please view the ‘Release Notes’ section of the Mission Control Support Centre – www.aprika.com/mc-support
Some of the new features included in this release of Mission Control have come from ideas submitted from existing clients. If you have an idea for enhancing Mission Control, you can submit it via email to [email protected].
If you have any questions regarding this release notification, please do not hesitate to contact us at [email protected].
©2026 Aprika Business Solutions Ltd. All rights reserved.
Simply enter your details below, and we will set you on your way to your Free Trial. Enjoy the ride!
See exactly how Mission Control Project Management can help your business, and improve your project management.
