New

Editable customer defined task attributes

At this release, we’ve added two new attributes to the Task object to help customers track and categorize their tasking requests within the Capella platform. These new attributes are optional but allow customers flexibility in relating a Capella task to internal systems (e.g., Purchase Order ID) or associating metadata to the task that cannot be easily captured in the existing Task Name and Task Description fields (e.g., Project Name).

Not only are these fields definable at task creation, but in contrast to other task fields, they are also editable after task submission and can be modified at any point throughout the task lifecycle.

Console User Interface

Tasking Form

Two new fields have been added to the Optional Parameters section of the tasking form in the Console UI for both Single and Repeat tasks:

These text fields allow customers to add information to a new tasking request for tracking in the Capella platform.

Task Review Page

The new task attributes are displayed on the Task Review page if set.

Task Details Page

The new task attributes are also displayed on the Task Details page if set.

An Edit button has also been added at the top right of the Task Details page:

Edit Task Page

When the Edit button on the Task Details page is clicked, the Edit Task page is displayed:

The Custom Attribute fields can be modified from the Edit Task page. After clicking the Update Task button or cancelling by clicking Cancel, the user is taken back to the Task Details page.

Public API

POST /task and POST /repeat-requests

The new task attributes are also supported in the existing POST /task and POST /repeat-requests endpoints of the Public API tasking service.

The new task attributes can be added to a new Single task or Repeat task by including the following parameters to the Properties of a new task submission:

PATCH /task/{taskingrequestId} and POST /repeat-requests/{repeatrequestId}

In addition, two new API endpoints have been added to the Public API tasking service at this release to support the ability to edit the new attribute values after task submission.

The body of the request should take the following format:

Archive holdback at task level

Archive holdback for a task restricts the resulting imagery from being included in the public archive for a pre-defined period from the date of collection (30 days, 1 year, Permanent) for image sensitivity or other purposes. Previously, archive holdback was applied across all tasking for an organization. At this release, the archive holdback tasking parameter is now available as a task-level attribute. The default value is set by the contract for the user’s organization (to support current workflows) but can be changed on a per-task basis via the Archive Catalog Holdback dropdown selector in the Optional Parameters section of the tasking form for both Single and Repeat tasks.

This task level property is also supported in the POST /task and POST /repeat-requests endpoints of the Public API tasking service.

Improved

• Ability to click ‘Refresh Access Times’ in Mission Awareness without waiting for the previous request to finish

Fixed

• Border display of UTC / Local time toggle button in Mission Awareness