Task Definitions are process tasks. You can make them as detailed or broad as you like. Task Definitions are required to configure a Task Workflows. A Task Definition can also be used to make Task Workflows more granular by appying status changes at the task level to the Assembly or Package.
Time Saving Note: The STRATUS Customer Success Team has configured and can transfer to your company database Filters, Reports, Task Definitions, Task Workflows, Task Categories, Cost Categories, Cost Types, Tracking Statuses and other Admin configurations. See the STRATUS 07/18/2019 Implementation Webinar - GTP Pre-configured Spool Templates, Reports, and Filters to watch an introduction video, or, contact the STRATUS Service Desk for more information. Screen shots below are taken from the Customer Success Team's configuration.
* See the Task Workflow Examples article for more information.
Configure Task Definitions
A Task Definition includes the following:
- Name (Required) - The name of the Task Definition. Tip: Use a standardized naming convention that uses a prefix so that the Task Definitions sort in a logical way. The Name is used to select tasks on the Task Workflows page in the Taks Sequence column.
- Description (Required) - The description can be the same or similar to the Name and is only visible on the Task Definitions page.
- Image - A task image, if added, will display wherever the task displays. If an image is not added to the task, then the Name will be used. One advantage to using an image is that task images can be sized the same giving the list of tasks a neat look to the page.
- Upload - Browse to upload the image file from your computer. The image will be used instead of the Name if it is uploaded.
- Task Category (Required) - Configure Task Categories before Task Definitions. See the Task Categories article for more information. Below are some examples:
- Cost Category (Required) - Configure Cost Categories before Task Definitions. See the Cost Categories article for more information. Below are some examples:
- Cost Type - See the Cost Types article for more information. Below are some examples:
- Apply Tracking Status - The tracking status that will be automatically applied when Apply Tracking Status to Assembly and/or Apply Tracking Status to Package is checked. See the Tracking Statuses article for more information. Below are some examples:
- Apply Tracking Status to Assembly
- When checked, after at least one task in an Assembly has been completed for the associated Task Definition, the tracking status set in the Apply Tracking Status column will be automatically applied to the Assembly.
- When unchecked, no tracking status will be applied to the assembly.
- Apply Tracking Status to Package
- When checked, after at least one task in a Package has been completed for the associated Task Definition, the tracking status set in the Apply Tracking Status column will be automatically applied to the Package.
- When unchecked, no tracking status will be applied to the package.
- Bypass (Update) Tracking Status Dialog
- When checked, after each task is completed for the associated Task Definition, the Update Tracking Status dialog will not display.
- When unchecked, after each task is completed for the associated Task Definition, the Update Tracking Status dialog will display if the Apply Tracking Status value is something other than “No Change”.
- Note: The Update Tracking Status dialog is the only dialog where hours can be entered while work is being done.
- Delete - Delete the Task Definition. Deleting the Task Definition will delete it from Task Workflows.
Example: Task Definitions and Task Workflows
See the Task Definitions and Task Workflows example on the Task Workflow Examples page.