Create an entity from a demand

Create an entity, such as a work item, from a demand so that you can track work on the demand.

Before you begin

A demand must have been created. For more information, see Create a demand.

The category and type of a demand and the applications you have installed determine the entity you can create from it. The available entity types and the applications you must have installed to be able to create them are listed in the following table.

Role required: it_demand_manager

Note: The sn_apw_advanced.eap_user role is required to convert a demand to EAP entities.

Procedure

1. Open a demand from the home page of Next Experience for Demand Management.

   For more information, see Access demands.

2. Verify that the values in the Category and Type fields are appropriate for the entity you want to create.

   The options in the Type list change according to the category that you select. For more information, see Demand form.

   Note: The Category and Type fields are set to read only when an entity is created from a demand. If you delete the created entity, these fields become editable again.

3. Select Save.

4. Create the entity by selecting the appropriate option from the More Actions option.

Depending on the category and type of the demand, options related to the entity you can create become available.

|Option|Description|
|------|-----------|
|**Create Project**|This option appears if the **Category** field is set to **Strategic** and the **Type** field is set to **Project**. Creates a project that is associated with this demand. The number of the project record is displayed in the **Project** field. For more information, see [Data migrated from a demand to a created project](data-migrated-from-demand-project-dw.md).|
|**Create Enhancement**|This option appears if the **Category** field is set to **Strategic** and the **Type** field is set to **Enhancement**. Creates an enhancement associated with this demand. Use enhancements to request improvements or new capabilities for existing features or services, for example, a request to add new UI elements. The number of the enhancement record is displayed in the **Enhancement** field.|
|**Create Epic**|This option appears if the **Category** field is set to **Strategic** and the **Type** field is set to **Epic**. Creates an Agile Development 2.0 epic that is associated with this demand. A **Demand** reference field is created in the Agile Development 2.0 Epic form.|
|**Create Story**|This option appears if the **Category** field is set to **Strategic** and the **Type** field is set to **Story**. Creates an Agile Development 2.0 story that is associated with this demand. A **Demand** reference field is created in the Agile Development 2.0 Story form.|
|**Create EAP Epic**|This option appears if the **Category** field is set to **Strategic** and the **Type** field is set to **EAP Epic**. Creates an Enterprise Agile Planning \(EAP\) epic that is associated with this demand. A **Converted from** reference field is created in the EAP epic form.|
|**Create EAP Feature**|This option appears if the **Category** field is set to **Strategic** and the **Type** field is set to **EAP Feature**. Creates an EAP feature that is associated with this demand. A **Converted from** reference field is created in the EAP feature form.|
|**Create EAP Capability**|This option appears if the **Category** field is set to **Strategic** and the **Type** field is set to **EAP Capability**. Creates an EAP capability that is associated with this demand. A **Converted from** reference field is created in the EAP capability form.|
|**Create Change**|This option appears if the **Category** field is set to **Operational** and the **Type** field is set to **Change**. Creates a change that is associated with this demand. The number of the change record is displayed in the **Change** field.|
|**Create Defect**|This option appears if the **Category** field is set to **Operational** and the **Type** field is set to **Defect**. Creates a defect that is associated with this demand. The number of the defect record is displayed in the **Defect** field.|

**Note:**

-   For EAP entities, select the team that you want the EAP entity to be assigned to, in the **Team** field in the **EAP Details** section in the demand form. This field becomes read-only once the entity is created.
-   Alternatively, you can create an entity using the **Confirm details and convert to selected entity** playbook activity. For more information, see [Use Playbook in Next Experience for Demand Management](use-playbooks-in-ppw.md).

Related topics

Use Playbook in Next Experience for Demand Management