Service Order Task Actions - Requirements

Target release	2019.4
Epic	PCR360-4036
Document status	done
Last Updated	2019-03-27

Goals

Convert "Service Order Only" Actions to "Task" Actions.
Rework the Actions Form from a Service focus to a one-time Task focus.

Background and strategic fit

Customers have requested more generic ways of tracking work on a Service Order, not all work relates directly to a Service. " Service-Order Only" Actions were already very similar to a generic "Task" type, so it makes sense to change this. Making this change opens up the usefulness of Service Orders and Actions to groups outside of Telecommunications.

Assumptions

There will be no functional differences between "Service Order Only" Actions and "Task" Actions.

Requirements

	Title	User Story	Importance
1	Change Service Order Only Actions into Task Actions	Functionally, Task Actions and Service Order Only Actions will work exactly the same. These Actions are used for one-time tasks that can be billed independent from the rest of the Order. Service Catalog Type list will be changed from "Service Order Only" to "Task" Service Desk Action "Action" list will be changed to include "Task" option ("Service Order Only" will be removed) New list Options: Add Change Types Add Locations Miscellaneous Move Owner Service ID Swap Upgrade/Downgrade Remove Task Service Desk Actions form will be adjusted: Hide Service ID field Hide Service Host field Hide Service Options Add new Task Details field? Hide Communications tab Hide Cabling tab	Must Have
2	SDC logic enhancements to support Task Actions	Action selector on the SDC form will mimic the Action selector on the Service Order Action form	Must Have
3	Task Actions creation via Imports	Allowing imports to create Task actions will allow users to bulk load Tasks	Must Have
4	Task Action updates for API	Allowing API to create Task actions will allow outside interfaces to add Tasks	Must Have

User interaction and design

We don't have a way to export this macro.

Questions

Below is a list of questions to be addressed as a result of this requirements document:

Question	Outcome
Should the new Task Actions have a new tab for "Task Details"	No. We recommend using Remarks to track Task Details. This allows customers to have a running log of task notes.
Should we add a "Task Details" field?	No. We recommend using Remarks to track Task Details. This allows customers to have a running log of task notes.
Will Tasks be added to CustomerCenter?	No.