Salesforce Project Management Software by Aprika
A new version of Mission Control (version 1.80) will be released on the AppExchange on Friday 1st May 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 ‘Estimates’ feature within Mission Control enables Customers to conduct thorough PERT estimating process when assessing the level of effort required to complete a piece of work.
PERT Estimates are derived from 3 different estimate values:
The ‘PERT Estimate’ is calculated based on:
(Optimistic Estimate + (4 x Most Likely Estimate) + Pessimistic Estimate) / 6
The PERT estimating process is carried out in three stages:
The first step in the PERT estimating process is to create requests for Roles to carry out estimates. This can be done via the ‘Request Estimates’ Component, which is accessible from the following pages:
The ‘Request Estimates’ Component will load as shown below.
The Display Filters enable you to determine which records should be displayed. The ‘Display’ options are:
Once you have selected the Display option, click the ‘Load’ button and the applicable records will be displayed, as shown below.
The next step is to select the Roles you wish to request estimates from. Within the ‘Add Estimators’ section, you can add individual Roles or add all Roles that are assigned ownership on the Project based on the following options:
Once Roles are added, they will be displayed within the Estimator section of the Component, as shown below.
For each piece of work (e.g. Action or Requirement), you can select all Estimators or as many as required, along with setting a Due Date.
Once all Estimates have been configured, click the Save button and the individual Estimate records will be created for the individual Estimators to complete.
This Component can also be used to view the Status of each Estimate that has been requested, allowing Project Managers to have a high level view of the progress the Estimators are making with their Estimates.
You are also able to request an estimate via the mini ‘Request Estimate’ component from the following pages:
For an individual Requirement card, you can click the Cup icon.
The mini component will open, allowing you to create Estimate records.
The second step in the PERT estimating process is for the individual Estimators to use the ‘Estimating Wizard’ to complete their Estimates. This can be done via the ‘Estimating Wizard’ Component, which is accessible by clicking on the ‘Estimate Wizard’ button from the following pages:
The ‘Estimating Wizard’ Component will load as shown below.
The ‘Estimates To Do’ section provides a list of all the Estimates the individual Estimator needs to complete. Clicking on the eye icon will load the ‘Estimate Workspace’ for that individual Estimate, as shown below.
The Estimate Workspace is broken into 3 sections:
Record requiring Estimate
This section displays the details of the record that needs to be estimated.
This will display the details of the Action or the Requirement that was selected from the To Do list. This section has two different display areas:
You can configure which fields are included in this section through the following Field Sets.
Action Object
Requirement Object
You can access the Field Set by going to Setup > Object Manager > [Object] > Field Sets
Estimators Estimate
This section is where the Estimator will complete their own individual estimates.
The Estimator will enter the estimate values for each of the Estimates (Optimistic, Most Likely and Pessimistic) and the PERT Estimate will calculate based on these values.
Note: You can create estimates for the individual related records (e.g. User Stories or Checklist Items) and roll those estimates up to the main Estimate. Refer to the ‘Related Information’ section below for further details.
Whilst you are working on your Estimate values, the Status can be updated to ‘Draft’. This will display on the ‘Request Estimates’ Component, allowing the Project Manager to see that Estimators are working on their Estimates.
Once the Estimate is ready to be submitted, you can update the Status field to ‘Submitted’. Once an Estimate has been submitted, the fields will be disabled, as shown below.
If you need to make amendments to your Estimate, you can click the ‘Recall’ button. This will revert the Status to ‘Draft’ and enable the fields for editing.
Once an Estimate has been submitted, it will be available for the Reviewer when they finalise the PERT estimates.
Related Information
If a Requirement or Action has related User Stories and/or Checklist Items, they will be displayed within the Related Information section.
These related records can be viewed to support the main Estimate. Alternatively, you can toggle on the ‘Enable Related Estimates’ setting in the top-right of the Related Information header.
The Estimator can work through each of the related records, entering the Optimistic, Most Likely and Pessimistic Estimates.
The PERT Estimate is calculated for each individual record and a summary PERT Estimate is available based on all of the individual estimations. If you wish to use these figures as the main Estimate, you can click the upload icon and these summary figures will be populated into the main Estimate fields.
The main Estimate can then be submitted for the Reviewer to finalise the PERT Estimate.
The third step in the PERT estimating process is reviewing all of the Estimates from the individual Estimators. This process is also carried out on the Estimating Wizard Component. However, you will only be able to enter ‘Reviewer Mode’ if the ‘View Reviewer Mode’ field on your Role record is set to TRUE.
To enter Reviewer Mode, you will need to toggle on the ‘Enable Review Mode’ setting located in the top right of the Estimating Wizard, as shown below.
When Reviewer Mode is enabled, the Reviewer will see an ‘Estimates To Review’ list, as shown below.
The ‘Estimates To Review’ section provides a list of all the Estimates the Reviewer needs to review.
Note: the list of records included in this list is based on the value of the ‘Reviewer Mode Access’ field on their Role record:
Clicking on the eye icon will load the ‘Estimate Workspace’ showing all Estimates related to the record requiring estimation.
The Reviewer’s Estimate Workspace is broken into 2 sections:
Record requiring Estimate
This section displays the details of the record that needs to be estimated.
Review Estimates
This section displays all of the Estimates from the individual Estimators. The Reviewer and their team can review and discuss the individual Estimates and agree a final PERT Estimate for the piece of work.
The Final Estimate figures are based on all related Estimates that have not been excluded. If you wish to exclude specific Estimates from the Final Estimate figures, you can set the ‘Exclude’ checkbox to TRUE against the individual Estimates.
The Reviewer will enter the PERT Estimate and Hours Scheduled values manually and click Save. These figures will then be saved directly on the Action or Requirement.
Once the Action / Requirement has a value in the PERT Estimate field, it will no longer be displayed in the ‘Estimates to Review’ list.
The Daily Digest will include an ‘Estimates Summary’ section for any Role that has Estimates that fall into any of the following categories:
No configuration is required to enable this section to be included in the Daily Digest.
If a Role requires access to the ‘Reviewer Mode’ feature of the Estimating Wizard, the following fields need to be set on their Role record.
The RACI Matrix can be viewed on the ‘Overview’ Tab of the Project Overview Component. It provides an ‘at a glance’ view of the areas of interest / level of involvement for various people, whether that’s resources assigned to work on the project, or Project Stakeholders. RACI stands for:
To view the RACI Matrix, the ‘Generate RACI Members’ field on the Project must be set to ‘Manually’ or ‘Automatically’. When the Project meets this criteria, the ‘Enable RACI Matrix’ toggle will be displayed on the Overview Tab, as shown below.
This toggle setting will be persistently remembered for each individual User across all Projects.
Switching the toggle setting to TRUE will display the RACI Matrix, which will be positioned to the left of the first column within the Work Breakdown Structure table. The image below shows the RACI Matrix being displayed with existing RACI Members.
The image below shows the RACI Matrix being displayed without any RACI Members.
You are able to create RACI Members manually, or have them automatically generated as Roles / Project Stakeholders are associated to the Project.
A maximum of 3 RACI Member icons will be displayed for any individual RACI Type.
To view all of the RACI Members within an individual RACI Type, click the resource icon. This will open up the RACI Member Modal.
This Modal shows all existing RACI Members for the RACI Type, including visibility into their level of involvement in the Project.
To manually generate a RACI Member, click on the individual resource icon for the applicable member type (e.g. R, A, C or I).
Once you’ve clicked the icon, the ‘Manage RACI Members’ Modal will load.
From here, you can search for a Role or a Project Stakeholder and add them as a RACI Member.
As you add RACI Members, they will appear in the table. If a RACI Member is assigned as an owner across the WBS layers, that ownership will be displayed.
In the example above, Colin Johnson is the Owner of the Phase – the record we are creating RACI Members for, along with being assigned as the Project Owner.
Mission Control can be configured to automatically create RACI Members for your Projects. This is configured on the Control Pad of the Mission Control Console.
To enable this feature, within the ‘RACI Matrix’ Tile, you will need to carry out the following steps:
Below is an example of how the RACI Matrix Tile settings could be configured.
Note: In order to set ‘Enable Auto Generation by Default’ to TRUE, at least 1 RACI Member setting must be configured.
These Settings enable RACI Member records to be automatically created for all Projects. However, each Project can be opted in or out of having RACI Members automatically generated by setting the ‘Generate RACI Members’ field to the appropriate value.
With these Settings enabled, once a Project has the ‘Generate RACI Members’ field set to Automatically, RACI Members will be automatically created.
Project resources can move between Master Teams and change Function as they get promoted, etc. To ensure Rate Card financials and Role Utilisation reporting remains accurate, you are able to create ‘Role History’ records.
The Role History feature handles scenarios where someone may have been in one Function for a period of time and then moved into a new Function. For example, during 2025 Mick Fanning may have been a Consultant. In 2026, he became a Project Manager. Without using Role History, on a Project with Rate Card financials, that spans 2025 and 2026 would not accurately track Mick’s differing rates between the time he was a Consultant and the time he was a Project Manager.
Changes to a Role’s ‘Master Team’ could also impact a Role’s figures on the Role Utilisation Report. For example, Kelly Slater may have been in the Sales Master Team between January and December 2025, and then moved into the Consultants Master Team on the 1st January 2026. When viewing the Role Utilisation Report for Nov 25, Dec 25 and Jan 26, it would inaccurately report that the Consultants Team didn’t hit their target because Kelly’s numbers would be included for November and December before he became part of the team.
By leveraging the Role History feature, these same scenarios can be handled accurately.
For Mick Fanning, we would create a Role History record as outlined in the table below.
| Role History ID | Effective Until Date | Role | Master Team | Function |
| RHID:00001 | 12/31/2025 | Mick Fanning | Consultant |
With these records in place, when calculating financials for the Rate Card Project, the following logic will be applied:
For Kelly switching from Sales to Consultants, we would create a Role History record as outlined below.
| Role History ID | Effective Until Date | Role | Master Team | Function |
| RHID:00001 | 12/31/2025 | Kelly Slater | Sales |
When viewing the Role Utilisation Report, looking at both Sales and Consultants, Kelly’s time would be allocated to each Master Team as outlined in the table below (note the green cells indicate where Kelly’s utilisation figures would be factored in).
| Master Team | Nov 25 | Dec 25 | Jan 26 | Feb 26 |
| Sales | X | X | ||
| Consultants | X | X |
Role History records can be created manually via the ‘Role History’ Related List, which is accessible from the Related Tab of the Role record.
Role History records will be automatically created in the following scenarios:
The Project ‘Grid’ is a Tab accessible from the Project Overview Component. To access the Grid Tab, a User’s Role record must have the ‘View Grid Tab’ field set to TRUE.
The Grid provides a dynamic view to interact with the key activity layers within your Project Work Breakdown Structure (WBS). Within the Grid, you can view:
This is controlled by selecting the ‘Data Source’, which will be persistently remembered per User.
The Grid provides a variety of features to interact with the data, including:
Each of these features are explained in further detail below.
The Grid contains a ‘Group By’ section, located at the top of the Grid.
By dragging Fields from the Grid to the Group By section, the content of the Grid will be grouped by that field.
In the example above, the Grid has been grouped by Milestone, then by Action Owner. To remove the Group By selections you’ve made, simply click the x in the field ‘Pill’ within the Group By section.
Note: The Group By selections will be persistently remembered on a per User basis.
Each column displayed within the Grid features a ‘Quick Filter’ under the Column Header, as shown below.
These Quick Filters can be used to apply a temporary filter to view key datasets. For example, in the image below, the Project Manager wants to view all Actions that have a Priority value of ‘High’. They enter High into the Quick Filter for Priority and the Grid returns the records matching the filter.
To return to the full dataset, simply remove the text string entered into the Quick Filter.
The Grid enables you to make inline edits to the records displayed. Simply double-click into the cell you wish to edit and make the change.
Once you remove focus from that cell, you can click the ‘Save’ button to commit the changes you’ve made.
Note: The warning icon will display next to the Save button when there are unsaved changes on the Grid.
By default, changes you apply to the Grid are not saved until you click the main Save button at the top of the Grid.
However, if you would prefer each change to be saved immediately, you are able to turn on a setting that will automatically save each change. To enable this feature, you will need to set the ‘Enable Auto Save’ setting to TRUE.
This is accessed by clicking the settings icon in the top-right corner of the Grid. With this setting enabled, each time you make an update to any record on the Grid, it will be saved immediately.
When the setting is enabled, the status of Auto Save is displayed as ‘On’ next to the Save button.
There are a variety of icons that provide you with access to key features, each icon is explained below.
| Icon | Function |
 |
Provides access to the Resource Assignment Wizard. Will display Green if the Action has Contributors |
 |
Provides access to the Log Time component |
 |
Provides access to the Checklist Item Manager. Will display Green if the Action has related Checklist Items |
 |
Provides access to the Issue Manager. Will display Yellow if there are unresolved Issues |
 |
Provides access to the Action Splitter component |
 |
Provides access to the Edit Modal for the record |
 |
Click to delete the record |
By default, the Grid will be sorted using the following fields:
Actions
Checklist Items
You can apply custom sorting, using up to 3 columns, for both the Action and Checklist Item layers of the Grid. This is achieved by clicking the Column Header for the column you wish to sort by. In the example below, the User has clicked on the Milestone column to sort by the Milestone Name.
To apply custom sorting to a second or third column, you will need to hold down the Shift key whilst clicking on the column you wish to sort by. In the example below, the User has selected Action Owner as the second column to sort by.
Custom Sorting will be remembered persistently on a per User basis. To clear any Custom Sorting that has been applied, click the ‘Clear Sort’ button as shown in the image below.
When Custom Sorting is cleared, the Grid will revert to the default sorting behaviour.
Filters can be applied to the WBS dataset on the Grid. This enables you to remove records that you may not wish to currently view. For example, you may wish to filter the records to only show those where you are the Action Owner, or remove any that have already been Completed or Cancelled.
To access the Filters Modal, you will need to click the filter icon located on the right-hand side of the Grid, as shown below.
You can apply Filters at each of the following layers:
Filters applied at the Action layer can comprise of Filters on the Action, Checklist Item and Contributor Objects. For example, you may want to filter Actions based on you being the Action Owner, or a Contributor, or an Item Owner of a related Checklist Item.
You are able to adjust the Filter Logic for each layer. Filters can be saved using the Pre-set Filter feature and shared with other Users.
By default, the following fields are displayed for Action and Checklist Items on the Grid:
Action
You can add/remove fields from this view through the ‘Action Grid Fields’ Field Set on the Action Object.
You can access the Field Set by going to Setup > Object Manager > Action > Field Sets > Action Grid Fields.
Checklist Item
You can add/remove fields from this view through the ‘Checklist Item Grid Fields’ Field Set on the Checklist Item Object.
You can access the Field Set by going to Setup > Object Manager > Checklist Item > Field Sets > Checklist Item Grid Fields.
A number of enhancements have been made to the Client Read Only Page. Details of each enhancement are included below.
If you create Project Health Checks and wish to share them with your Client via the Client Read Only Page, you can configure the ‘Health Checks’ Tab to be displayed.
The image above shows the list of Health Checks related to the Project on the left-hand side of the Tab. When the eye icon is clicked, the individual Project Health Check will be displayed on the right-hand side.
To include the Health Checks Tab on the Read Only Page, you will need to ensure the ‘Display Health Checks Tab’ field on the Project is set to TRUE.
You will need to configure a Sharing Rule for the Project Health Check Object as outlined below.
Object: Project Health Check
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
By default, the following fields are displayed for the individual Project Health Check record view:
You can add/remove fields from this view through the ‘Read Only Health Check Fields’ Field Set on the Project Health Check Object.
You can access the Field Set by going to Setup > Object Manager > Project Health Check > Field Sets > Read Only Health Check Fields.
Within the Time Logs Tab of the Read Only Page, you can choose to display the ‘Generate PDF’ button, as shown below.
This enables your Client to export a PDF of the Time Logs. When the button is clicked, they have the option to set the timeframe for the export, as shown below.
Once the ‘Generate’ button is clicked, the PDF Report will be displayed.
To display the ‘Generate PDF’ button on the Read Only Page, you will need to ensure the ‘Display Time Logs Generate PDF Button’ field is set to TRUE on the Project.
By default, the Overview Tab on the Read Only Page will display the following fields:
If you wish to remove any of the above fields, you can do so on the ‘Customer Read Only Page’ Tile on the Control Pad of the Mission Control Console.
Within the ‘Default Field Columns’ section, set the Checkbox to TRUE for each Field you wish to be displayed on the Overview Tab and click the Save button within the Tile.
Note: An install script will update these Settings to TRUE for all existing customers.
By default the Gantt Chart will display the Project ‘Work Breakdown Structure’, which comprises of Phases, Milestones, Actions and Checklist Items, as per the example below.
It can be configured to allow Users to toggle the data source to view Role Forecasts instead, as per the example below.
On the Standalone Gantt Chart, you are able to view Role Forecasts for both Projects and Opportunities. Where a Role Forecast relates to both a Project and an Opportunity, the Project will be displayed as the parent record.
When viewing the Forecasts view, Users are able to drag and drop Role Forecasts to reschedule the date range.
Note: Dependencies are not supported on Role Forecasts.
Users can double-click the individual Role Forecast to access the Edit Modal, which will provide access to the following tabs:
The visibility and default loading of these Tabs is controlled on the Role record, using the following fields:
You can control which fields are displayed on the ‘Role Forecast’ Tab of the Edit Modal.
This is controlled via the ‘Role Forecast Gantt Edit Modal’ Field Set on the Role Forecast Object. This can be accessed via Setup > Object Manager > Role Forecast > Field Sets.
You can control which fields are displayed in the Tooltips Box when hovering over the Role Forecast on the Gantt Chart.
This is controlled via the ‘Role Forecast Gantt Chart Tooltip Fields’ Field Set on the Role Forecast Object. This can be accessed via Setup > Object Manager > Role Forecast > Field Sets.
Enabling the Role Forecast Gantt Chart
To enable the ‘Role Forecast Gantt Chart’ feature, you will need to set the ‘Enable Role Forecast Gantt Chart’ Setting to TRUE. This Setting can be found on the Gantt Chart Tile on the Control Pad of the Mission Control Console.
When this Setting is TRUE, a Picklist will be displayed on the Gantt Chart, as shown in the image below.
By default, it will be set to ‘Actions’, this will show the Work Breakdown Structure of the Project. To view Role Forecasts instead, Users can click the picklist and select ‘Forecasts’.
Note: This is a persistent setting that will be remembered on a per User basis each time they visit the Gantt Chart.
A number of enhancements have been applied to the Resource Planner. Details of each enhancement are included below.
Two new ‘Group By’ options have been added. Previously, Users had the ability to group the Planner Tab data using the following options:
The two additional options are:
Master Team > Role
This Group By option will display all Roles within their Master Teams. Master Teams will be sorted alphabetically in ascending order. The image below shows an example of this Group By option.
Note: Any Role that does not have a Master Team assigned will be grouped into a Team called ‘None’.
Function > Role
This Group By option will display all Roles within their Function. Functions will be sorted alphabetically in ascending order. The image below shows an example of this Group By option.
Note: Any Role that does not have a Function assigned will be grouped into a Team called ‘None’.
The ‘Exclude Capacity Figures for Placeholder Roles’ Setting enables the use of Placeholders to assign upcoming resource demand, without having the Placeholder Role’s ‘Hours per Week’ factored into the available capacity of the team.
A Role is identified as a Placeholder by setting the ‘Placeholder’ field to TRUE, as shown in the image below.
If this Setting is FALSE, the Placeholder’s ‘Hours per Week’ will be factored into the capacity calculations on the Resource Planner.
The ‘Period Cell Value Display’ Setting enables Customers to control the information displayed in each cell relating to a particular period. The options available include:
Value
When set to ‘Value’, the hours will be displayed, as shown below.
This is the sum of hours assigned to the Role for that particular period.
Value & Percentage
When set to ‘Value & Percentage’, the hours will be displayed, along with the percentage of the Role’s availability that these hours are consuming, as shown below.
This is the sum of hours assigned to the Role for that particular period, and the percentage calculates based on the sum of hours / sum of availability. For example, if Kelly Slater works 40 hours per week and has 24 hours assigned for the period, the percentage would be 60%.
Percentage
When set to ‘Percentage’, it will display the percentage value derived by calculating how much of the Role’s availability is being consumed by the hours they’ve been assigned, as shown below.
This is the percentage of their availability already assigned, which is calculated based on the sum of hours / sum of availability. For example, if Kelly Slater works 40 hours per week and has 24 hours assigned for the period, the percentage would be 60%.
The ‘Exclude Roles with Capacity Allocation >=’ Filter allows you to filter out Roles that have already been assigned enough work to exceed a specified percentage of their capacity.
In the example above, any Role that has already been assigned work for 100% of their availability for all periods within the date range, will be excluded from the Planner Table.
This Filter will allow Resource Managers to filter out any Role that already has sufficient work and be able to focus in on those Roles that still have capacity to take on additional assignments.
When using this Filter, a toggle button will be displayed on the Planner. This will allow you to toggle between those Roles that are ‘Included’ or ‘Excluded’ based on the Filter.
In the example above, the Roles that are ‘Included’ are being viewed.
In the example above, the Roles that are ‘Excluded’ are being viewed.
The ‘Do not exclude Placeholder Roles from Capacity’ Filter provides Users with the flexibility of optionally including Placeholder availability within the Capacity figures for a particular filter.
With this Filter set to TRUE, Placeholder Roles will be included in capacity calculations even if the ‘Exclude Capacity Figures for Placeholder Roles’ Setting is enabled.
Two new Generation Methods have been included, to support additional auto-generation scenarios when generating Projects from Opportunities.
The Product Quantity x Hours ‘Generation Method’ provides you with the ability to build up a Project Plan based on the Products associated to the Opportunity.
The Project record will be cloned based on the ‘Project Template’ specified on the Opportunity. The remainder of the Project Plan (e.g. Phases, Milestones, Actions, Checklist Items, Contributors & Dependencies) will be added only if the Product has been associated to a ‘Milestone Template’ or has related ‘Product Milestones’. If a Product is associated to the Opportunity, the associated Milestone(s) will be added to the Project. The ‘Hours Scheduled – Billable’ and ‘Hours Scheduled – Non Billable’ of all Actions, Checklist Items and Contributors will be multiplied by the Opportunity Line Item ‘Quantity’ field.
The Base Template + Product Quantity x Hours ‘Generation Method’ provides you with the ability to clone a generic Project Plan from one Project Template, as well as building up the Project Plan based on the Products associated to the Opportunity.
This Generation Method lets you include standardized Milestones on your Project, as well as including additional Milestones based on the Products sold. For example, you may want to include standard Milestones into every Project Plan, such as ‘Kick-off’, ‘Go Live’, and ‘Customer Success Handover’, but they’re not included as Products that will be added to the Opportunity.
To use this Generation Method, you’ll need your standard Milestones to be on one Project Template, and your Product related Milestones on a different Project. The Project Template containing your standard Milestones will be considered your Base Template, and all of the Milestones within this Project will be added to the Project when it is auto-generated from the Opportunity. Any Milestones related to the Products will also be added to the Project. The ‘Hours Scheduled – Billable’ and ‘Hours Scheduled – Non Billable’ of all Actions, Checklist Items and Contributors will be multiplied by the Opportunity Line Item ‘Quantity’ field.
When specifying the ‘Project Template’ on the Opportunity, you would enter the Project that is your Base Template.
A number of minor enhancements have been made to various features. Each enhancement is detailed below.
Previously the Gantt Filters were only accessible when viewing the Standalone Gantt Chart. The Filters have been made available on the Project Overview Gantt Chart and on Gantt Anywhere.
For example, when using Gantt Anywhere on the Account record, you would see all of the Projects related to the Account. With the Filters, you will now be able to filter to exclude Projects with a Status of Complete or where Archived = TRUE.
To access the Filters via the Overview Gantt or Gantt Anywhere, you will need to click the Filter button, as shown in the image below.
The Filter Modal will load, Users can apply filter parameters and save Pre-set Filters.
Note: Some of the Filter Parameters are not available when on the Project Overview. For example, any Filter related to a Portfolio, Program or Project will not be available as you are already viewing the Gantt Chart in context of an individual Project.
The Filter functionality of the Role Utilisation has been enhanced to provide you with the ability to save pre-set filters.
When you initially load the Role Utilisation Report, you will be required to select who you’re wanting to view details for. This selection can be made by selecting Master Team, Team or Role. You’re also able to specify the timeframe and whether you’d like to view the data Daily, Weekly, Monthly or Quarterly. Finally, you can also choose how the data is grouped – Role or Master Team.
By default, the End Date will always be set to Today and the Start Date will be 3 months prior to the End Date.
Filter By
You are able to filter the Role Utilisation Report by three options:
Pre-Set Filters
You are able to save a filter selection using the ‘Pre-set Filters’ feature within the Report Settings section of the report.
In the example below, the User has selected the ‘Consultants’ and ‘Developers’ Master Team values.
As this is a filter the User wants to use frequently, they want to save it as a pre-set filter. To do this, they click the ‘Create’ link, enter a Filter Name and click ‘Create’.
The filter parameters are saved and applied to the Role Utilisation Report. As this is a pre-set filter, it will be persistently remembered on a per User basis. To remove a pre-set filter, the User can click the Clear button, as shown below.
When a pre-set filter is cleared, the User will be required to select an existing pre-set filter or manually apply filters.
The Role Allocation Object has had 3 new fields added in order to track the ‘baseline’ hour values. The 3 new fields are:
These 3 fields will be automatically populated to match the original values entered into the Hours Scheduled fields. This will enable comparisons between the baseline and actual hours scheduled.
A number of enhancements have been made to the ‘Create Milestones’ page. Details of these enhancements are included below.
Multi Line Editing
You are able to apply edits to multiple lines on the Create Milestones page at the same time. Click the checkbox at the top of the page, or selecting the checkbox for the individual rows you wish to edit, as shown below.
Applying an edit to one of the selected rows will apply the same change to all of the selected rows. For example, in the image below, the User has selected rows 1, 5 and 9.
The User adjusts the ‘Invoice on Completion’ field for row 1 and the same change is automatically applied to rows 5 and 9.
Copy Milestone Owner
The copy icon located to the right of the Milestone Owner field on the Create Milestones page enables you to copy the Milestone Owner from the row above to the selected row.
For example, in the image below, row 1 has Colin Johnson specified as the Milestone Owner. If Colin is also required to be the Milestone Owner of the Milestone on row 2, the User can click the icon to copy the value from row 1, rather than having to use the lookup functionality.
Note: clicking this icon will not work in conjunction with the multi-line edit functionality.
Phases can now be marked as Non Billable in the same way Projects, Milestones and Actions can be.
If the Project ‘Non Billable’ field is set to TRUE, this will filter down to the Phase ‘Non Billable Indicator’ field.
If a Phase ‘Non Billable’ field is set to TRUE, this will filter down to the Milestone ‘Non Billable Indicator’ field.
To enable Customers to void a Billing Event, the Status field contains a ‘Void’ value. This can be used to void a Billing Event that has been raised and no longer required.
When a Billing Event is updated to have a Status value of Void, The ‘Total Amount’ field will default to 0 and the ‘Tax Amount Outstanding’ field will default to 0.
A Validation Rule will prevent the Status being set to Void if ‘Total Paid’ is greater than 0.
To provide greater control over the Timesheet Submission and Exception emails being sent out, you can specify which Time Logs should be factored into the calculation of their ‘Hours per Week’ percentage.
For example, Acme Inc. expects all of their project resources to have 90% of their time logged by 4pm on Friday. If this target hasn’t been met, the Timesheet Submission email will be sent out. However, they would like this percentage to only be based on Time Logs that have been submitted or approved. If the person has created the Time Log, but not yet submitted it, it should not be counted.
To specify which Time Logs should be included when determining if the Role has logged sufficient time for the week, Acme Inc. configures the ‘Approval Status’ setting within the Timesheet Notifications Tile on the Control Pad of the Mission Control Console.
In the example above, only Time Logs that have an Approval Status of ‘Submitted’ or ‘Approved’ will be factored in when determining if the Role has achieved the percentage target.
When using the ‘1 Month’ timeframe view on the Timesheet, you are able to specify which day of the month will be displayed as the first day on the Timesheet.
For example, you ask your team to log their time and track it on a monthly basis. You have set up the Timesheet to display 1 month. However, you monitor this from the 26th of the month through to the 25th of the following month.
To ensure the Timesheet displays the correct dates to ensure your team can view their entire Timesheet for the reporting period, you can set the ‘Select the Start Day to be used for the 1 Month view. Will default to 1 if left empty’ setting to 26, as shown below.
When the Users load the Timesheet, the first day displayed on the Timesheet will be the 26th of the prior month and will display each day through to the 25th of the current month.
A new Permission Set has been added to Mission Control, which provides the minimum level of access required across the system for a User to use the Timesheet.
If you have Users that only use the Timesheet, and you wish to restrict their access across the rest of the application, you can assign the ‘Mission Control Timesheet Only’ Permission Set.
A Delete Trigger has been added to the Role Forecast Object. Previously, when a Role Forecast record was deleted manually (rather than via the Manage Forecast Component), the related Role Allocation records were not deleted until the Role Forecast Batch Process ran. Therefore, there was a period of time where orphaned Role Allocations were remaining in the system. This Delete Trigger will now immediately delete related Role Allocations.
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 |
| Estimate ID | Auto Number | Identifies the unique ID for this record | New |
| Requirement | Lookup (Requirement) | Links to the Requirement record this Estimate relates to | New |
| Action | Lookup (Action) | Links to the Action record this Estimate relates to | New |
| Checklist Item | Lookup (Checklist Item) | Links to the Checklist Item this Estimate relates to | New |
| User Story | Lookup (User Story) | Links to the User Story this Estimate relates to | New |
| Estimator | Lookup (Role) | Links to the Role record that is the Estimator for this Estimate | New |
| Optimistic Estimate | Number (16, 2) | Identifies the Optimistic Estimate | New |
| Most Likely Estimate | Number (16, 2) | Identifies the Most Likely Estimate | New |
| Pessimistic Estimate | Number (16, 2) | Identifies the Pessimistic Estimate | New |
| PERT Estimate | Formula (Number 16, 2) | Formula: PERT Estimate is based on (Optimistic + (4 x Most Likely) + Pessimistic) / 6 | New |
| Due Date | Date | Identifies the date the Estimate is required by | New |
| Status | Picklist | Identifies the current Status of the Estimate | New |
| Estimate Notes | Rich Text (5000) | Captures any notes related to the Estimate | New |
| Field | Field Type | Comments | New/Existing |
| View Review Mode | Checkbox | Identifies whether the User linked to this Role has the ability to enable Reviewer Mode on the Estimate Wizard | New |
| Review Mode Access | Picklist | Identifies the access level when in Reviewer Mode on the Estimate Wizard | New |
| View Grid Tab | Checkbox | Identifies if the User can view the Grid Tab on the Project Overview | New |
| Project Overview Default Tab | Picklist | Add the following value:
Grid |
Existing |
| Gantt Role Forecast Default Tab | Picklist | Identifies which Tab on the Gantt Role Forecast Modal is displayed by default | New |
| View Gantt R/Forecast Tab | Checkbox | Identifies whether the User linked to this Role has the ability to view this Tab on the Gantt Modal | New |
| View Gantt R/Forecast Record Detail Tab | Checkbox | Identifies whether the User linked to this Role has the ability to view this Tab on the Gantt Modal | New |
| View Gantt R/Forecast Chatter Tab | Checkbox | Identifies whether the User linked to this Role has the ability to view this Tab on the Gantt Modal | New |
| Placeholder | Checkbox | Set this field to TRUE to indicate this Role is used as a Placeholder | New |
| Field | Field Type | Comments | New/Existing |
| PERT Estimate | Number (16, 2) | Identifies the agreed PERT Estimate from related Estimates | New |
| Field | Field Type | Comments | New/Existing |
| PERT Estimate | Number (16, 2) | Identifies the agreed PERT Estimate from related Estimates | New |
| Field | Field Type | Comments | New/Existing |
| RACI ID | Name (Auto Number) | Identifies the unique ID for this record | New |
| Role | Lookup (Role) | Links to the Role record for this RACI Member Type | New |
| Project Stakeholder | Lookup (Project Stakeholder) | Links to the Project Stakeholder for this RACI Member Type | New |
| RACI Member Type | Picklist | The responsibility assignment for the RACI Role | New |
| Phase | Lookup (Phase) | Links to the Phase this RACI Member record relates to | New |
| Milestone | Lookup (Milestone) | Links to the Milestone this RACI Member record relates to | New |
| Action | Lookup (Action) | Links to the Action this RACI Member record relates to | New |
| Checklist Item | Lookup (Checklist Item) | Links to the Checklist Item this RACI Member record relates to | New |
| Project ID | Formula (Text) | System Field: Identifies the Id of the Project record | New |
| RACI Origin | Picklist | System Field: Identifies why the RACI Member was created | New |
| Field | Field Type | Comments | New/Existing |
| Generate RACI Members | Picklist | Identifies whether RACI Members are required for this Project | New |
| Auto-Generate RACI Members | Formula (Checkbox) | Identifies whether RACI Member records should be automatically generated for this Project | New |
| Display Time Logs Generate PDF Button | Checkbox | Identifies whether the ‘Generate PDF’ button is displayed on the Time Logs Tab of the Client Read Only Page | New |
| Display Health Checks Tab | Checkbox | Identifies if this Tab should be available on the Client Read Only Page | New |
| Field | Field Type | Comments | New/Existing |
| Role History ID | Name (Auto Number) | Identifies the unique ID for this record | New |
| Role | Lookup (Role) | Links to the Role this History record relates to | New |
| Effective Until Date | Date | Prior to this date, the Role will be part of the specified Master Team / Function | New |
| Master Team | Lookup (Team) | Identifies the Master Team this Role was assigned to during this period of time | New |
| Function | Picklist | Identifies the Function this Role was assigned to during this period of time | New |
| Field | Field Type | Comments | New/Existing |
| Baseline Hours Scheduled – Billable | Number (16, 2) | Captures the original Hours Scheduled – Billable value | New |
| Baseline Hours Scheduled – Non Billable | Number (16, 2) | Captures the original Hours Scheduled – Non Billable value | New |
| Baseline Total Hours Scheduled | Formula (Number 16, 2) | Captures the original Total Hours Scheduled value | New |
| Field | Field Type | Comments | New/Existing |
| Gantt Collapsed | Checkbox | When checked, indicates the Opportunity is collapsed on the Gantt | New |
| Generation Method | Picklist | Add the following values:
Product Quantity x Hours Base Template + Product Quantity x Hours |
Existing |
| Field | Field Type | Comments | New/Existing |
| Non Billable | Checkbox | Identifies if the Phase is Non Billable | New |
| Non Billable Indicator | Formula (Checkbox) | Indicates if this Phase is classified as Non Billable. If the Phase ‘Non Billable’ Field is set to TRUE, it takes this value, otherwise it takes the value from the Project ‘Non Billable’ Field | New |
| Field | Field Type | Comments | New/Existing |
| Non Billable Indicator | Formula (Checkbox) | Indicates if this Milestone is classified as Non Billable. If the Milestone ‘Non Billable’ Field is set to TRUE, it takes this value, otherwise if the Phase ‘Non Billable Indicator’ Field is set to TRUE, it takes this value, otherwise it takes the value from the Project ‘Non Billable’ Field. | Existing |
| Field | Field Type | Comments | New/Existing |
| Status | Picklist | Add new value:
Void |
Existing |
| Total Amount | Formula (Currency) | Formula modified to be:
IF(ISPICKVAL(Status__c, “Void”), 0, Total_Amount__c – Total_Paid__c) |
Existing |
| Tax Amount Outstanding | Formula (Currency) | Formula modified to be:
IF(ISPICKVAL(Status__c, “Void”), 0, if(amc__Tax_Amount_Paid__c = 0, amc__Tax_Amount__c ,If( amc__Tax_Amount__c > 0 ,amc__Total_Outstanding__c – (amc__Total_Outstanding__c / (1 + amc__Tax_Rate__c)), 0))) |
Existing |
The following Components have been included or updated in this Release.
| Component Type | Component Name | Description |
| Visualforce | Estimate Wizard | Visualforce component to access the Estimate Wizard page |
| Visualforce | RequestEstimatesPage | Visualforce component to access the Request Estimates page |
| Visualforce | grid | Visualforce component to access the Grid page |
| Apex Class | EstimateWizard | Apex Class required to use the Estimate Wizard page |
| Apex Class | GridController | Apex Class required to use the Grid page |
| Apex Class | ReadOnlyHealthChecksController | Apex Class required to use the Health Checks Tab on the Read Only page |
| Apex Class | RequestEstimates | Apex Class required to use the Request Estimates page |
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 |
| Billing Event | Unable To Void If Paid | Ensures the Status cannot be set to Void if Total Paid is greater than zero | TRUE |
As part of the upgrade process, an Install Script will execute to set default values for the following Fields / Settings.
Role records:
Control Pad: Customer Read-Only Page Settings
Mission Control will be made available based on the following release schedule.
1st May 2026 – Available for manual upgrade from the AppExchange
16th May 2026 – Automatic upgrade to all Sandbox Orgs
30th May 2026 – Automatic upgrade to all Production Orgs
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 email address below, and we will set you on your way to your Free Trial. Enjoy the ride!
Simply enter your email address below, and we will set you on your way to your Free Trial. Enjoy the ride!
