1. Data Management
  2. RapidValue
  3. Flows

Set up Azure DevOps integration
Activity Flow

Before you can use the Azure DevOps integration, you must set up:

  • The DevOps mapping. This includes the connection to DevOps and the relevant project and the mapping of RapidValue field values to DevOps field values.
  • Which DevOps mapping applies to a solution.
  • If you want to use work packages to synchronize with DevOps. To do so, set up work package groups and work packages, and assign a work package group and a work package to each of the relevant business processes.

Consultant Consultant Consultant Set up work packages

Set up work packages

In project management, you can use a work package to combine related tasks. You can combine tasks in work packages based on, for example, geographical area, engineering discipline, technology, or the time budget.
If you want to use work packages to synchronize with Azure DevOps, set up work package groups and work packages, and assign a work package group and a work package to each of the relevant business processes.
In the DevOps mapping, typically, you map a work package group to an epic and a work package to a feature.
If you synchronize business processes with the Azure DevOps project, for each business process, the related requirements are combined in the defined work package groups and work packages. The synchronization is done based on the DevOps mapping as defined for the solution.

 Start Start Use work packages  to synchronize  with Azure DevOps? Use work packages  to synchronize  with Azure DevOps? Use task templates to  synchronize requirements  with Azure DevOps? Use task templates to  synchronize requirements  with Azure DevOps? Set up task templates Set up task templates You can apply a task template on creation of a requirement in Azure DevOps. Use a task template to set up a predefined set of tasks to be created for a requirement in DevOps. In DevOps, these tasks are added as work item with the requirement as parent work item. Example: In DevOps, for a requirement, always these tasks must be done: Design Develop Test Document Release You can set up and apply a task template with these tasks. So, when during DevOps synchronization a work item is created for a requirement, automatically work items are created for these tasks as well. Note: The task template is only applied on creation of the requirement in DevOps. So, for example, if you have made changes to the task template and the requirement already exists in DevOps, the task template is not applied. To apply a task template, in the DevOps mapping, add an entity mapping for 'RapidValue table name': Requirement In the Task template field, define the desired task template. Fill in the other entity mapping fields as desired. Also set up the entity field mapping as desired. Note: You can, for example, apply different task templates to different requirement types. To do so, make sure to fill in these fields accordingly: 'RapidValue field name' and 'RapidValue value'. Task template In the Work item type field, select 'Task'. Fill in the other fields as desired. Also set up the entity field mapping as desired. Note: Usually, only one task template mapping is required. Also if you have several requirement mappings. Example: Example of an entity mapping setup for requirements and applying task templates: Procedure 1. Click Business process management. 2. In the Links section, click Task templates. 3. Click New. 4. In the Task template field, type a value. 5. Expand the Description section and enter a description. 6. Expand the Lines section. 7. Click Add line. 8. In the Task identifier field, type a value. 9. Define a template description for the task. In the Description field, type a value. Note: To enter a more extended text, you can use HTML tags. 10. Close the page. 11. Close the page. Set up Azure DevOps mapping Set up Azure DevOps mapping Before you can use the Azure DevOps integration, you must set up the DevOps mapping. This includes: Which RapidValue records map to which DevOps work item types. If you use work packages, to which DevOps work item types the work package groups and work packages are mapped.Which fields of these RapidValue records map to which fields of the DevOps work item. The synchronization direction of the mapping, which defines whether RapidValue (Out) or DevOps (In) owns the data.In case of an enum type field, which RapidValue field value maps to which DevOps work item field value. Procedure 1. Click Business process management. 2. In the Links section, click DevOps mapping. 3. In the list, click the link of the desired mapping. 4. Click the Mapping tab. 5. Sub-task: Set up entity mapping. 6. Set up which RapidValue records map to which work item types. In the Entity mapping section, click Add. Note: You can also copy an existing entity mapping to create a new entity mapping. To do so, select the entity mapping that you want to copy, and in the Entity mapping section, click Copy, fill in the fields as desired, and click OK. 7. In the RapidValue table name field, select an option. 8. In the RapidValue field name field, enter or select a value. 9. In the RapidValue value field, enter or select a value. 10. In the Work item type field, enter or select a value. 11. Select the Parent work package check box. 12. You can apply a task template on creation of a requirement in Azure DevOps. A task template has a predefined set of tasks to be created for a requirement in DevOps. In DevOps, these tasks are added as work item with the requirement as parent work item. In the Task template field, enter or select a value. Note: Only apply a task template to a mapping record if the RapidValue table name is 'Requirement'. 13. Sub-task: Set default parent for mapped entity. 14. In the Entity mapping section, click Set default parent. 15. For the RapidValue entities which do not have a parent in the business process hierarchy, define a default parent work item. Otherwise no DevOps work item is available to which the created work item can be linked. Use this, for example, to synchronize requirements only. In the Work item ID field, type a value. Note: Copy the work item ID in DevOps and paste it in this field. 16. Click Check. 17. Click OK. Note: As a result, the Default parent for the selected entity mapping record is filled. 18. Sub-task: Define additional conditions. 19. In the Entity mapping section, in the Conditions pane, click Add. 20. In the RapidValue field name field, enter or select a value. 21. In the RapidValue value field, enter or select a value. 22. Sub-task: Set up entity field mapping. 23. Set up which fields of the RapidValue record map to which fields of the DevOps work item. Also define the synchronization direction. In the Entity details section, click Add. Note: You can also copy an existing entity field mapping to create a new entity field mapping. To do so, select the entity field mapping that you want to copy, and in the Entity details section, click Copy, fill in the fields as desired, and click OK. 24. In the Name field, type a value. 25. In the Sync direction field, select an option. 26. In the RV field name field, enter or select a value. Note: Fewer fields are allowed for the synchronization direction 'In' than for the direction 'Out'. 27. In the 'DevOps field' field, enter or select a value. 28. Sub-task: Set up entity field value mapping. 29. In the Entity details section, in the Values pane, click Add. 30. In the RapidValue value field, enter or select a value. Note: Do not define a field mapping for the RapidValue field that you defined in the entity mapping. 31. In the DevOps value field, enter or select a value. 32. Close the page. 33. Close the page. Link Azure DevOps mapping to solution Link Azure DevOps mapping to solution Before you can use an Azure DevOps integration for a solution, apply a DevOps mapping to the solution. Procedure 1. Click Business process management. 2. In the list, find and select the desired record. 3. Click Edit. 4. Click the Parameters tab. 5. Expand the DevOps integration section. 6. In the DevOps mapping field, enter or select a value. 7. Close the page. End End Set up Azure DevOps connection Set up Azure DevOps connection Before you can use the Azure DevOps integration, you must set up the connection to DevOps and the relevant project. You can connect with a personal access token. Before you set up the connection, create your personal access token in your Azure DevOps environment. Make sure to copy the created personal access token. For more information, refer to Use personal access tokens. Procedure 1. Click Business process management. 2. In the Links section, click DevOps mapping. 3. Sub-task: Create DevOps mapping. 4. Click New. 5. In the Mapping field, type a value. 6. In the Language field, enter or select a value. 7. In the Description field, type a value. 8. Sub-task: Set up connection. 9. Click the Connection tab. 10. Click Set connection. 11. In the DevOps URL field, type a value. 12. In the Authentication field, select 'Personal access token'. 13. In the Personal access token field, paste the copied personal access token. 14. In the DevOps project field, enter or select the DevOps project to which you want to connect. 15. Click OK. 16. Refresh the page. 17. Click the form caption. Yes No Yes No

Activities

Name Responsible Description

Set up work packages

Consultant
In project management, you can use a work package to combine related tasks. You can combine tasks in work packages based on, for example, geographical area, engineering discipline, technology, or the time budget.
If you want to use work packages to synchronize with Azure DevOps, set up work package groups and work packages, and assign a work package group and a work package to each of the relevant business processes.
In the DevOps mapping, typically, you map a work package group to an epic and a work package to a feature.
If you synchronize business processes with the Azure DevOps project, for each business process, the related requirements are combined in the defined work package groups and work packages. The synchronization is done based on the DevOps mapping as defined for the solution.

Set up task templates

Consultant

You can apply a task template on creation of a requirement in Azure DevOps.

Use a task template to set up a predefined set of tasks to be created for a requirement in DevOps. In DevOps, these tasks are added as work item with the requirement as parent work item.

Example:

In DevOps, for a requirement, always these tasks must be done:

  • Design
  • Develop
  • Test
  • Document
  • Release

You can set up and apply a task template with these tasks. So, when during DevOps synchronization a work item is created for a requirement, automatically work items are created for these tasks as well.

Note: The task template is only applied on creation of the requirement in DevOps. So, for example, if you have made changes to the task template and the requirement already exists in DevOps, the task template is not applied.

To apply a task template, in the DevOps mapping, add an entity mapping for 'RapidValue table name':

  • Requirement
    In the Task template field, define the desired task template. Fill in the other entity mapping fields as desired. Also set up the entity field mapping as desired.
    Note: You can, for example, apply different task templates to different requirement types. To do so, make sure to fill in these fields accordingly: 'RapidValue field name' and 'RapidValue value'.
  • Task template
    In the Work item type field, select 'Task'. Fill in the other fields as desired. Also set up the entity field mapping as desired.
    Note: Usually, only one task template mapping is required. Also if you have several requirement mappings.

Example:

Example of an entity mapping setup for requirements and applying task templates:

Set up Azure DevOps mapping

Consultant

 		Before you can use the Azure DevOps integration, you must set up the DevOps mapping. This includes:
  • Which RapidValue records map to which DevOps work item types.
  • If you use work packages, to which DevOps work item types the work package groups and work packages are mapped.
  • Which fields of these RapidValue records map to which fields of the DevOps work item.
  • The synchronization direction of the mapping, which defines whether RapidValue (Out) or DevOps (In) owns the data.
  • In case of an enum type field, which RapidValue field value maps to which DevOps work item field value.

Link Azure DevOps mapping to solution

Consultant

 		Before you can use an Azure DevOps integration for a solution, apply a DevOps mapping to the solution.

Set up Azure DevOps connection

Consultant

Before you can use the Azure DevOps integration, you must set up the connection to DevOps and the relevant project.
You can connect with a personal access token. Before you set up the connection, create your personal access token in your Azure DevOps environment. Make sure to copy the created personal access token.
For more information, refer to Use personal access tokens.

Activities

Name Responsible Description

Set up work packages

Consultant
In project management, you can use a work package to combine related tasks. You can combine tasks in work packages based on, for example, geographical area, engineering discipline, technology, or the time budget.
If you want to use work packages to synchronize with Azure DevOps, set up work package groups and work packages, and assign a work package group and a work package to each of the relevant business processes.
In the DevOps mapping, typically, you map a work package group to an epic and a work package to a feature.
If you synchronize business processes with the Azure DevOps project, for each business process, the related requirements are combined in the defined work package groups and work packages. The synchronization is done based on the DevOps mapping as defined for the solution.

Set up task templates

Consultant

You can apply a task template on creation of a requirement in Azure DevOps.

Use a task template to set up a predefined set of tasks to be created for a requirement in DevOps. In DevOps, these tasks are added as work item with the requirement as parent work item.

Example:

In DevOps, for a requirement, always these tasks must be done:

  • Design
  • Develop
  • Test
  • Document
  • Release

You can set up and apply a task template with these tasks. So, when during DevOps synchronization a work item is created for a requirement, automatically work items are created for these tasks as well.

Note: The task template is only applied on creation of the requirement in DevOps. So, for example, if you have made changes to the task template and the requirement already exists in DevOps, the task template is not applied.

To apply a task template, in the DevOps mapping, add an entity mapping for 'RapidValue table name':

  • Requirement
    In the Task template field, define the desired task template. Fill in the other entity mapping fields as desired. Also set up the entity field mapping as desired.
    Note: You can, for example, apply different task templates to different requirement types. To do so, make sure to fill in these fields accordingly: 'RapidValue field name' and 'RapidValue value'.
  • Task template
    In the Work item type field, select 'Task'. Fill in the other fields as desired. Also set up the entity field mapping as desired.
    Note: Usually, only one task template mapping is required. Also if you have several requirement mappings.

Example:

Example of an entity mapping setup for requirements and applying task templates:

Set up Azure DevOps mapping

Consultant

 		Before you can use the Azure DevOps integration, you must set up the DevOps mapping. This includes:
  • Which RapidValue records map to which DevOps work item types.
  • If you use work packages, to which DevOps work item types the work package groups and work packages are mapped.
  • Which fields of these RapidValue records map to which fields of the DevOps work item.
  • The synchronization direction of the mapping, which defines whether RapidValue (Out) or DevOps (In) owns the data.
  • In case of an enum type field, which RapidValue field value maps to which DevOps work item field value.

Link Azure DevOps mapping to solution

Consultant

 		Before you can use an Azure DevOps integration for a solution, apply a DevOps mapping to the solution.

Set up Azure DevOps connection

Consultant

Before you can use the Azure DevOps integration, you must set up the connection to DevOps and the relevant project.
You can connect with a personal access token. Before you set up the connection, create your personal access token in your Azure DevOps environment. Make sure to copy the created personal access token.
For more information, refer to Use personal access tokens.
Related to Notes

Set up Azure DevOps integration

 		 

Provide feedback