1. Data Management
  2. RapidValue
  3. Flows

Define business process settings
Activity Flow

For each business process, you can define these settings:

  • See also references
  • Categories
  • Work package

Architect Architect Define 'see also' references for business process Define 'see also' references for business process For each business process, you can define 'see also' references. You can use this to refer to entities where information can be found that is relevant for the business process.You can refer to:ConceptsFlowsActivities Procedure 1. Click Business process modeling. 2. Click Business processes. 3. In the tree, select 'the desired business process'. 4. Click the Details tab. 5. Expand the See also section. 6. Click Add. 7. In the list, find and select the desired records. 8. Click OK. 9. Close the page. Define categories for business process Define categories for business process You can use categories to link business processes to a specific purpose. So, in one solution, you can combine business processes for several purposes. Purposes can be, for example, training, user assistance, RSAT (Remote server administration tool), or security. For each business process, you can define to which categories it belongs. You can use business process categories to:   Publish a subset of business processes to a business process library in Lifecycle Services. Only the business processes to which the selected categories are linked are published to Lifecycle services. You can do so, for example, to publish the task guides to be delivered in a solution package or to publish the task guides to be used in RSAT. Record or play task guides in another D365 FO environment. You can, for example, maintain your RapidValue solution in a central D365 FO environment and do task recording in another D365 FO environment. For example, task guides to be used for training are recorded in the training environment. On a category, you can define a connection to another D365 FO environment. If you record or play a task guide, and a category with a connection is applicable, the connection 'Internet address' defines which environment is opened. So, you automatically record or play the task guide in the other environment. Procedure 1. Click Business process modeling. 2. Click Business processes. 3. In the tree, select 'the desired business process'. 4. Click Edit. 5. Click the Details tab. 6. Expand the Category section. 7. Click Add. 8. In the Category field, enter or select a value. 9. In the Notes field, type a value. 10. Close the page. Notes If you define, for a business process, several categories with a connection, the first one to defines to which remote environment. Use the Move up and Move down buttons to define the desired category sequence. Start Start End End 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.

Activities

Name Responsible Description

Define 'see also' references for business process

Architect

 		For each business process, you can define 'see also' references. You can use this to refer to entities where information can be found that is relevant for the business process.
You can refer to:
  • Concepts
  • Flows
  • Activities

Define categories for business process

Architect
You can use categories to link business processes to a specific purpose. So, in one solution, you can combine business processes for several purposes. Purposes can be, for example, training, user assistance, RSAT (Remote server administration tool), or security.
For each business process, you can define to which categories it belongs. You can use business process categories to:  
  • Publish a subset of business processes to a business process library in Lifecycle Services. Only the business processes to which the selected categories are linked are published to Lifecycle services. You can do so, for example, to publish the task guides to be delivered in a solution package or to publish the task guides to be used in RSAT.
  • Record or play task guides in another D365 FO environment. You can, for example, maintain your RapidValue solution in a central D365 FO environment and do task recording in another D365 FO environment. For example, task guides to be used for training are recorded in the training environment. On a category, you can define a connection to another D365 FO environment. If you record or play a task guide, and a category with a connection is applicable, the connection 'Internet address' defines which environment is opened. So, you automatically record or play the task guide in the other environment.

Set up work packages

Architect
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.

Activities

Name Responsible Description

Define 'see also' references for business process

Architect

 		For each business process, you can define 'see also' references. You can use this to refer to entities where information can be found that is relevant for the business process.
You can refer to:
  • Concepts
  • Flows
  • Activities

Define categories for business process

Architect
You can use categories to link business processes to a specific purpose. So, in one solution, you can combine business processes for several purposes. Purposes can be, for example, training, user assistance, RSAT (Remote server administration tool), or security.
For each business process, you can define to which categories it belongs. You can use business process categories to:  
  • Publish a subset of business processes to a business process library in Lifecycle Services. Only the business processes to which the selected categories are linked are published to Lifecycle services. You can do so, for example, to publish the task guides to be delivered in a solution package or to publish the task guides to be used in RSAT.
  • Record or play task guides in another D365 FO environment. You can, for example, maintain your RapidValue solution in a central D365 FO environment and do task recording in another D365 FO environment. For example, task guides to be used for training are recorded in the training environment. On a category, you can define a connection to another D365 FO environment. If you record or play a task guide, and a category with a connection is applicable, the connection 'Internet address' defines which environment is opened. So, you automatically record or play the task guide in the other environment.

Set up work packages

Architect
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.
Related to Notes

Define business process settings

 		 

See also

Provide feedback