Activities

Add a menu entry of type Action. You can use this type to refer to:

• An action in D365 FO.
• A (action-like) element in another type of application.

Use a business process of type Activity to add an activity directly to the business process hierarchy.

Add a business process of type Activity to a business process of type Process.

For each application, you can add the user interface forms of that application. You can use these forms, for example, to refer to from an activity.

You can set up a flow for business processes of these types:

• Value chain
• Phase
• Group
• Supporting process

You usually do so to indicate how the business processes in the business process hierarchy are related.

To add a business process to a flow, you can choose from the business processes that are defined in the business process hierarchy of the current solution.

If you add a business process to a flow, and you select:

• A lane, the business process is added to the lane.
• A flow element, the business process is added to the right of the selected element.
• No lane or flow element, the business process is added to the top lane.

If during the preparation of a test, a new configuration is used, you can add this configuration to the solution.

Add the required events to the flow. An event is something that happens during the process. Events affect the flow of the process and usually have a cause or an impact and in general require or allow for a reaction. You can use these types of events:

• Start: the usual start of a flow.
• Start timer: the flow is started when a time condition is true.
• Start message: the flow is started when a specified message is received.
• Intermediate: explicitly indicates an important state change or milestone in the flow.
• End: the usual end of a flow.
• Cancel: indicates that the flow is canceled, usually following a gateway.
• Error: indicates where to go if an error or unexpected exception occurs.

If you set up a process flow, usually, you first define the things to be done in the process. So, you first add the activities or (sub-)processes. This activity describes how to add an existing activity to a flow.

If you add an activity to a flow, it is automatically added to the lane for the related role. If, in the flow, no lane is available for the role, a new lane is created.

You can choose an existing activity from these lists:

• [Area] (first tab of the dialog): only the activities are shown that are in the same area as the process of the flow. The shown activities are of the current solution and its referenced solutions.
• All: all activities of the current solution and its referenced solutions are shown.

Add a menu entry of type Form. You can use this type to refer to:

• A form in D365 FO.
• A (form-like) element in another type of application.

Add gateways to the flow where required. A gateway is a decision point where the flow is directed in a certain way based on criteria or user action. You can use these types of gateways:

• Exclusive: you can choose but one of the paths.
• Inclusive: you can choose any of the paths. So, this can be one path ore several paths.
• Parallel: you must do all paths.

Add a lane if required. Each lane represents a specific role. The lanes are used to indicate responsibility for activities, processes, and objects.

If you add activities, and no lane is yet available for the related role, a new lane is added automatically.

However, a business process, flow, or data object are not related to a role. If you want to add such an element and the required lane is not available, you can add a lane manually.

To add a lane, you can choose from the roles that are defined for the current solution and its referenced solutions.

• Phase, Group = Topic
  
• Process, Scenario, Activity = Lesson
  

You can add an object to the flow design. An object is a data object, document or deliverable such as an item, invoice, physical document, or product. 

Objects can represent, for example, inputs and outputs of processes and activities, or the content of messages exchanged internally or externally.

To add an object, you can choose from the objects as defined for the current solution and its referenced solutions.

If you add an object to a flow, and you select:

• A lane, the object is added to the lane.
• A flow element, the object is added to the right of the selected element.
• No lane or flow element, the object is added just somewhere on the design grid.

Use phases to divide a value chain into a high-level grouping of the processes by function or purpose. Phases represent logical parts of the end-to-end flow.

Add a business process of type Phase to a business process of type Value chain.

You can use groups to structure the processes in a phase or a supporting process. Usually, you use groups to group processes that have a similar purpose or are done by similar roles. However, you can use them to provide any structure.

Add a group to these types of business processes:

• Phase
• Group
• Supporting processes

Use a business process of type Process to define the process and the related flow to be done.

Add a business process of type Process to these types of business processes:

• Phase
• Group
• Process
• Supporting processes

Add a menu entry of type Report. You can use this type to refer to:

• A report in D365 FO.
• A (report-like) element in another type of application.

Use a business process of type Scenario to define a scenario for a process. A scenario can be, for example, a specific route through an existing flow.

Add a business process of type Scenario to a business process of type Process to which a flow is assigned. As a result, the flow is also added to the added scenario business process.

You can record activity steps with the Task recorder. You can add the recorded steps to the activity. On an activity, you cannot change or remove the steps as added by the Task recorder. You can only change the steps in the task recorder and save the changes to the activity in RapidValue.

If recording the steps is ready:

1. Stop the task recorder.
   
2. Click Save to RapidValue.

If you set up a process flow, usually, you first define the things to be done in the process. So, you first add the activities or (sub-)flows. This activity describes how to add a sub-flow to a flow.

To add a sub-flow, you can choose from the flows that are defined for the current solution and its referenced solutions.

If you add a sub-flow to a flow, and you select:

• A lane, the sub-flow is added to the lane.
• A flow element, the sub-flow is added to the right of the selected element.
• No lane or flow element, the sub-flow is added just somewhere on the design grid.

You can use a business process of type Supporting processes to group processes that are not part of the main process in the business solution. A supporting process is required to be able to do the main processes. Examples of supporting processes are: HRM and IT.

Add a business process of type Supporting processes is to the root node in the business process hierarchy.

You can manually add test cases to a test suite.

You can only add already existing test cases.

Use a value chain to group a chain of processes and activities to be executed in the business solution to reach the goals of the business solution.

Link a business process of type Value chain to the root node in the business process hierarchy.

Analyze the gaps in the business processes of the relevant solution and specify what is required to make these business processes in line with the customer needs.

You can create a copy of the flow that is currently assigned to the selected business process. The currently assigned flow is the flow that is defined on the Business processes form, in the Process section, in the Flow field.

Once created, the flow copy is directly assigned to the selected business process. So, the flow copy replaces the originally assigned flow for the selected business process.

You can assign an existing flow to a business process in the business process hierarchy.

As a result, both the flow and the related process are assigned to the selected business process.

You can create a flow and directly assign it to a business process in the business process hierarchy on the Business processes form.

As a result, both a process and a flow are created and assigned to the selected business process. The type of the created process is defined by the type of the selected business process. The process type defines the flow design options.

You can use this option if you want to assign a new flow while already a flow is assigned or if you want to only assign and not yet design a new flow.

From RapidValue, you can browse the LCS project that is linked to a RapidValue solution.

Use ownership to indicate which user is responsible for which record.

Use statuses to keep track of the progress on and state of the solution you work on.

You can assign these statuses:

• Open: Work on this record is in progress and anyone can edit it.
• Waiting: The record is editable, but work cannot proceed due to missing information.
• Review: The record is still editable but ready for review.
• Completed: The record is completed, and you cannot edit it. You can change the status, for example, to make a change to the record.
• Canceled: The record is obsolete or due to be deleted, you can reopen or delete it.

For requirements, you can also use these additional statuses:

• Requested: The requirement is defined but not yet approved.
• Approved: The requirement is approved but work is not yet started.
• Test: The requirement is implemented and is ready to be tested.

For translations, the:

• Canceled status is not available.
• Redo status is added: The translation must be reviewed because the reference text is changed.

To tests and test runs, you can assign these statuses:

• Created: The test or test run is created but not yet ready to be done.
• Scheduled: The test or test run is ready to be started.
• Started: The test or test run is started.
• Failed: Errors are found during the test or test run.
• Passed: The test or test run was completed successfully.
• Skipped: The test or test run is not done.

If you have completed a test case, and if required also added requirements, you can assign the appropriate status to the test case.

The test run status is automatically updated based on the test case statuses. However, you can change the test run status manually. You can do so, for example, if the test run has no test cases or if you want to overrule the automatically defined test run status.

To test runs, you can assign these statuses:

• Created: The test run is created but not yet ready to be done.
• Scheduled: The test run is ready to be started.
• Started: The test run is started.
• Failed: Errors are found during the test run.
• Passed: The test run was completed successfully.
• Skipped: The test run is not done.

You can, if required, overrule the automatically defined test run status.

To test runs, you can assign these statuses:

• Created: The test run is created but not yet ready to be done.
• Scheduled: The test run is ready to be started.
• Started: The test run is started.
• Failed: Errors are found during the test run.
• Passed: The test run was completed successfully.
• Skipped: The test run is not done.

You can, if required, overrule the automatically defined test status.

To tests, you can assign these statuses:

• Created: The test is created but not yet ready to be done.
• Scheduled: The test is ready to be started.
• Started: The test is started.
• Failed: Errors are found during the test.
• Passed: The test was completed successfully.
• Skipped: The test is not done.

You can automatically check RapidValue elements for errors.

Which checks are done?

Generally, the checks are done that are also done when you manually enter a record and save it to the database. So, the checks are done that control the data consistency in the database. For example, does a used reference still exist in the database?

What is checked?

If you check for errors, these RapidValue elements are checked:

• The selected element.
• Its references. If a reference is defined, only the reference record itself is checked and not its references and children. For example, almost each RapidValue element has a reference to the solution. In this case, only the solution record itself is checked and not its children and references.
• Its children. If a child is defined, the child itself is checked. But also, its references and its children.

Example:

• Flow: if you check a flow for errors, these RapidValue elements are checked:
  • The flow itself.
  • The flow references: solution and process.
  • The flow children: lanes, objects, connectors. If one of the objects is, for example, an activity, the activity itself is checked. But also, its references: solution, role, area, and application and its children: activity steps.

If a flow is created as a copy of another flow, you can compare the changes between the current flow and its original flow or other copies of the flow.

You can also compare the flow with any other flow. To do so, on the Compare to dialog, set the Show only flows of the '...' process toggle button to No.

You can compare solutions to find the differences.

If you compare solutions, these elements are taken into account:

• All elements that belong to the compared solutions.
• All elements that belong to the reference solutions as defined for the compared solutions.

As a result of the comparison, these differences can be found (B = Base solution; C = Compare-to solution):

• Element in B, element not in C.
• Element not in B, element in C.
• Element both in B and C, with different versions.
• Business process in B and C, with different flows.

• Use the elements that are used in the base solution.
  
• Copy the business process hierarchy of the base solution.
  
• Copy implementation data.
  
• Copy field values.
  

• All settings of the base solution are copied to the new solution.
  
• For each solution, which is found in the reused elements, a reference is added to the new solution.
  

In a solution, you can use elements from reference solutions. To consolidate the current solution, you can merge these elements into the current solution. So, you make these elements unique for the current solution.

You can consolidate one reference solution at a time. If several reference solutions are available, carefully select which one to consolidate first.

Duplicate elements

If you consolidate a solution, duplicate elements can be found. So, elements from the reference solution can already exist in the current solution. You can define what action is taken if a duplicate is found:

• Keep both elements; the copied elements get a suffix
• Use destination element

For each duplicate that is found, a task is created and assigned to the user who does the consolidation. Such a task describes the found duplicate and the action that is taken. You can use the task to check whether the right action is taken and to make changes, if required.

Reference solutions

As a result of the consolidation, the selected reference solution is removed from the reference solutions of the current solution. Note: In a reference solution, you can also use elements from another solution (which is a reference solution of your reference solution). You can have used such elements in your current solution. In this case, the reference solution of your reference solution is added as a reference solution to the current solution.

Example:

Solution 'Base' has a reference solution 'A'.

Solution 'A' has a reference solution '1'.

In solution 'Base', you have used a flow from solution 'A'. This flow in solution 'A' has an activity from solution '1'.

If you consolidate solution 'A' into solution 'Base':

• Solution 'A' is removed as reference solution from solution 'Base'.
• Solution '1' is added as reference solution to solution 'Base'.

You can create a solution based on an existing solution. As a result:

• All settings of the base solution are copied to the new solution.
• The full business process hierarchy, as defined for the base solution, is copied to the new solution.
• All RapidValue elements, which are used in the base solution, are reused in the new solution.
• For each solution, which is found in the elements, a reference is added to the new solution.

If you set up a flow, usually, you first define the things to be done in the process. So, you first add the activities or (sub-)processes. This activity describes how to add a new activity to a flow.

If you add an activity to a flow, it is automatically added to the lane for the related role. If, in the flow, no lane is available for the role, a new lane is created.

Before you evaluate the goals and identify opportunities, you create the evaluation.

You can create a flow centrally and, at another time, assign it to a business process in the business processes hierarchy or use it as sub-flow in another flow.

Before you publish a solution to Microsoft Dynamics Lifecycle Services (LCS), you are advised to create the related project in LCS.

During the Analysis phase, you can create questions on the business processes of your solution.

During the gap analysis you can create questions on the business processes that are marked as Gap.

During the process verification you can create questions on business processes. Usually, you do so for the business processes that you mark as Gap.

During the Analysis phase, you can create questions on your solution.

You can create requirements for the business processes when you analyze the gaps. Usually, you do so for the business processes that are marked as Gap.

You can create requirements for business processes when you verify business processes. Usually, you do so for the business processes that you mark as Gap.

During implementation, you can create requirements for your solution and for specific records in your solution.

Besides to the solution, you can assign requirements to:

• Requirements
  
• Activities
  
• Applications
  
• Business processes
  
• Flows
  
• Questions
  
• Test suites
  

• Several elements: business processes, flows, activities, applications, and requirements. 
  
• The relations between these elements.

You create a solution configuration snapshot in these cases:

• The first time you want to explore the solution configuration. 
  
• If changes are made to the solution configuration. So, these changes become available for the solution configuration explorer.

Always create snapshots in the background in batch, as the creation of a snapshot can take quite some time. If you frequently make changes to the solution configuration, you can also define the recurrence.

• Several elements: requirements, business processes, test suites, test runs, and roles. 
  
• The relations between these elements.

You create a test configuration snapshot in these cases:

• The first time you want to explore the test configuration. 
  
• Changes are made to the test configuration. So, these changes become available for the test configuration explorer.

You can create a task to solve an error at another time.

You can create a test based on an existing test suite.

You can create a blank test suite. If you do so, you must manually define most of the settings and information.

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

Define which business processes of the relevant solution are in or out of scope for the implementation project.

One of these scenarios is applicable:

• No milestones defined
  Business processes can have these scope indicators:
  • Not specified - No scoping is done for the business process.
  • In scope - Either the business process itself or one of its child business processes is set to In scope.
  • Out of scope - The business process is set to Out of scope.
• Milestones defined
  Business processes can have these scope indicators:
• Not specified - No scoping is done for the business process.
• [Milestone] - The business process is in scope for the milestone.
• In scope - No scoping is done for the business process itself. One of its child business processes is in scope for a milestone.
  
• Out of scope - The business process is set to Out of scope.

If the test is created or generated, you can review and change its settings, like test type, and priority.

For a web application, you can define a form to open a URL.

net use [drive letter]

If a task recording is linked to a RapidValue activity, you can edit it as well from the activity.

On the Task recorder, you can:

• Change the name and description of the recording.
  
• Add, change, or delete steps.
  

• Click Save to this PC. As a result, the task recording is saved as an AXTR file.
  
• Click Save as developer recording. As a result, the task recording is saved as an XML file.
  

You can configure RapidValue to enable multi-language name display. You can use this to view your RapidValue records in two languages. This can be useful, for example, if your current user language is French and you imported an English solution.

Note: Translated names are only shown for the identification names of your RapidValue records. Multi-language name display only makes sense if the names are translated to your current user language.

To enable multi-language name display, enable the Translations > Translation Fields configuration key.

As a result, on the:

• List pages and dialogs, the name is shown twice:
  • The left name field shows the original name of the record.
  • The right name field shows the record name in the current user language.
• Detail pages, the name is shown twice:
  • The editable name field shows the original name of the record.
  • The non-editable name field shows the record name in the current user language.
• Business process hierarchies, the names in the hierarchy are shown in the current user language.

Note: The original name of the record is the originally entered identifier of the record. So, it can be any language.

If multi-language name display isn't required, disable the Translations > Translation Fields configuration key. This improves performance and simplifies the user interface.

You can configure RapidValue to enable translations.

To enable translations, enable the Translations configuration key. As a result, all translation capabilities in RapidValue are made available in the user interface. Also, the multi-language support in the (pre)views is enabled. If translations are not required, disable the Translations configuration key. This improves performance and simplifies the user interface.

You can enter feedback on entities of a RapidValue solution if you browse the solution in the Business processes view of the Business process presentation.

As an example, in this topic, you browse to and enter feedback on an activity.

If the translation is done inside D365 FO usually, the RapidValue element texts are translated from the Business process translation workspace.

The translator can replace the not-yet-translated text with the translation.

• Importance
  
• Maturity
  
• Complexity
  
• Performance
  
• Opportunity
  

• The related test suite.
  
• The related business processes for the test suite. A test suite can be linked to several business processes.
• The related requirements. Not only the requirements are shown of the pinned test run, but also of the related test suite and business processes.
  
• The related roles. These are the roles as defined for the test cases of both the pinned test run and its related test suite.

• A procedure activity, task guides are created and exported based on the sub activities that are linked to the steps of the procedure activity. Available flow activity task guides aren't exported.
• No procedure activity, the task guides of the flow activities are exported.

You can find where a selection of records is used.

You can do so from most element pages in RapidValue, like Flows, Roles, and Goals.

You can generate a test run based on a test as defined for a selected business process. If the test runs are created, you can review and change the test run settings.

• Business process - You can get a business process link on the Business process modelling workspace (on the Business processes tab), on the Business process designer page, and on the Business processes page.
• Activity - You can get an activity link on the Business process modeling workspace (on the Activities tab) and on the Activities page.
• Requirement - You can get a requirement link on the Business process implementation workspace (on the Requirements tab) and on the Requirements page.

You can directly import a solution or any part of a solution from a content package. A content package consists of configuration data that is stored in RapidValue tables in XML format. For each record in a configuration, a line exists in the content package.
If a record already exists in RapidValue, it is replaced with the record in the content package.
The steps in this topic show how to import a content package from another D365 FO environment with RapidValue installed.
You can also import a content package from the RapidValue file share. If a content package is already available on the file share, it is shown in the grid on the Import wizard.

You can selectively import a solution or any part of a solution from a content package. A content package consists of configuration data that is stored in RapidValue tables in XML format. For each record in a configuration, a line exists in the content package.
On selective import, the content package is analyzed, and its contents is compared with the already existing data in RapidValue. If a to-be-imported record already exists in RapidValue, you can indicate what to do:

• Keep - The existing record in RapidValue is kept without changes.
• Overwrite - The existing record in RapidValue is replaced with the record in the configuration file.

The steps in this topic show how to import a content package from another D365 FO environment with RapidValue installed.
You can also import a content package from the RapidValue file share. If a content package is already available on the file share, it is shown in the grid on the Import wizard.

You can import a solution or any part of a solution, as a new separate solution. You can import from a content package. A content package consists of configuration data that is stored in RapidValue tables in XML format. For each record in a configuration, a line exists in the content package.
As a result of the separate import, none of your existing RapidValue content is overwritten.
The steps in this topic show how to import a content package from another D365 FO environment with RapidValue installed.
You can also import a content package from the RapidValue file share. If a content package is already available on the file share, it is shown in the grid on the Import wizard.

You can directly import a solution or any part of a solution from a data file that is created from a RapidValue content package. A data file is an XML file of type RVDATA that contains all configuration data of the content package.
If a record already exists in RapidValue, it is replaced with the record in the data file.

• The RapidValue file share. Make sure the file is already uploaded as type Data file to the Business process file share workspace. As a result, the data file is shown in the grid on the import wizard.
  
• A file location on the server on which D365 FO is running. Only use this option for big configuration files.
  

You can selectively import a solution or any part of a solution from a data file that is created from a RapidValue content package. A data file is an XML file of type rvdata that contains all configuration data of the content package.

On selective import, the data file is analyzed, and the contents of this file is compared with the already existing data in RapidValue. If a to-be-imported record already exists in RapidValue, you can indicate what to do:

• Keep - The existing record in RapidValue is kept without changes.
• Overwrite - The existing record in RapidValue is replaced with the record in the configuration file.

You can import a solution or any part of a solution, as a new separate solution. You can import from a data file that is created from a RapidValue content package. A data file is an XML file of type rvdata that contains all configuration data of the content package.

As a result of the separate import, none of your existing RapidValue content is overwritten.

• The RapidValue file share. Make sure the file is already uploaded as type Data file to the Business process file share workspace. As a result, the data file is shown in the grid on the import wizard.
  
• A file location on the server on which D365 FO is running. Only use this option for big configuration files.
  

You can directly import a solution or any part of a solution as defined in a Microsoft Excel file that you created based on the 'RapidValue data entry template'. If a record already exists in RapidValue, it is replaced with the record in the Microsoft Excel file.

• Keep - The existing record in RapidValue is kept without changes.
  
• Overwrite - The existing record in RapidValue is replaced with the record in the Microsoft Excel file.
  

You can import a solution or any part of a solution as a new separate solution from a Microsoft Excel file that you created based on the 'RapidValue data entry template'. As a result, none of your existing RapidValue content is overwritten.

If the texts in the Microsoft Excel translation file are translated, you can import the translations into RapidValue.

Important

• You can only import a translation file into the solution where the translation is exported from.
• Before you import a translation file, make sure the field tags are in the original structure in which these were exported.

You can link a Microsoft Dynamics Lifecycle Services (LCS) project to the related solution in RapidValue. As a result, you can browse the LCS project directly from the solution in RapidValue.

Often, an answer to a question results in a requirement. You can link this question to the requirement.

Discuss and answer the questions that are created for the solution. All questions that are related to a solution are shown at the solution level.

Review, estimate, and complete the requirements that are created for the solution. All requirements that are related to a solution are shown at the solution level.

If a requirement applies to several records, you can add a relation to these records.

You can manually add the steps of a scenario to a procedure activity. You can link these steps to several relevant existing or new activities.

You can only manually enter procedure activity steps if no task recording is linked to the procedure activity.

If you change text (for example, the name or description) for any record that is already translated, you can mark the translation to be redone. As a result:

• The translation gets the Redo status.
• On the Business process translations workspace, the record is shown on the To be redone tab.

You can monitor the history of changes made to records in RapidValue. On these actions on records, a change is logged in the change history:

• Creation of the record. For example, an activity or a flow.
• Status change.
• Owner change.
• Redo translation.
• Assign gap category to a business process.
• Assign business process to milestone.

You can monitor the history of data imports. All data imports, as done with the RapidValue import wizard are logged in the data import history.

You can monitor the history of operations. For these operations, the results are logged in the operations history:

• Compare
• Check and fix
• Find and replace

You can monitor the test progress in several ways. One of these ways is to monitor the test progress on test run level.

The test run status is automatically updated based on the status of the related test cases.

You can monitor the test progress in several ways. One of these ways is to monitor the test progress on test level.

The test status is automatically updated based on the status of the related test runs.

For each level in the business process hierarchy, a progress bar is shown that reflects the testing progress for the selected business process and, if applicable, its children.

Before you can monitor the test status based on the progress bars, you need to refresh the progress bars.

If modules are assigned to trainees, you can monitor the progress they make by trainee, trainee module, and trainee exercise.

You can monitor the progress for each:

• Trainee - Progress is shown for all modules that are assigned to the selected trainee.
• Trainee module - Progress is shown for the selected module and trainee combination.
• Trainee exercise - Progress is shown for exercises that are assigned (through the assigned modules) to trainees.

If a module is assigned to trainees, you can monitor the general progress on module level. The summarized progress of all trainees to which the module is assigned is shown in one summary view.

You can show an overview of the solution and its business processes.

• The My process guide tab on the My process guide workspace is filled. Based on your role assignment, the relevant business processes are shown. 
  
• The Process guide tab on the Help pane is filled. If business processes are available for both a form and your role assignment, these business processes are shown on the Process guide tab on the Help pane.

You can publish a document with the specifications of a flow. You can configure the level of detail of the information that is added to the document.

You can find and download the published document on the Business process file share workspace, on the Documents tab.

You can publish a document with the result of the gap analysis of a solution.

To each business process with requirements defined, a table is added with the requirements. For the not-business-process-specific requirements for the solution, a table is added in a separate 'General requirements' chapter. For each requirement, this information is shown: Requirement, Type, Status, Priority, Estimate, and Activity.

You can configure the level of detail of the information that is added to the document.

You can find and download the published document on the Business process file share workspace, on the Documents tab.

You can publish a document with the business process specifications of a solution. You can configure the level of detail of the information that is added to the document.

You can find and download the published document on the Business process file share workspace, on the Documents tab.

You can publish a document with the result of the process verification of a solution. Only the business processes that are in scope are added to this document. Separate chapters are created for the business processes with gaps and the business processes that fit.

You can configure the level of detail of the information that is added to the document.

You can find and download the published document on the Business process file share workspace, on the Documents tab.

You can publish a document with the scope statement of a solution. For each milestone, only the business processes that are in scope are added to this document. You can configure the level of detail of the information that is added to the document.

You can find and download the published document on the Business process file share workspace, on the Documents tab.

You can publish a document with the test plan for a solution.

To each business process with tests defined, a table is added with the tests. For each test, this information is shown: Test, Type, Milestone, and Status.

You can configure the level of detail of the information that is added to the document.

You can find and download the published document on the Business process file share workspace, on the Documents tab.

You can configure the level of detail of the information that is added to the document.

You can find and download the published document on the Business process file share workspace, on the Documents tab.

You can publish only the title page of a website.

If you use remote task recording, you can create a task recording in a remote environment and save it to the environment where you manage your RapidValue content.

A web service is hosted on the remote environment. For the web service, to connect to the RapidValue content environment, you must register the Microsoft Entra ID app on the RapidValue content environment.

If you want to import content packages from another D365 FO environment, you must register the Microsoft Entra ID app on the remote environment.

On the remote environment, also RapidValue must be installed.

You can release a solution to create a snapshot of it. If you release a solution, a consolidated and no editable copy is created of the solution.

As a result:

• The new solution doesn't have any reference solutions.
• All RapidValue elements, which are used in the base solution, are copied to the new solution.
• If a duplicate element is found, the element that already exists in the new solution is used. So, no copy is created.
• The new solution is blocked for any change. All elements have the status Released.
• Optionally, all elements are assigned to the same owner.

• Status Completed.
  
• A task recording.

You can replace a value in records where it is used with another value.

For example, you create an activity that must in some places be used instead of an existing activity. You first find and review the records in which the existing activity is used. Select the records in which you want to replace the existing activity and replace it with the new activity.

Before the test run is done, it can be required to review the related test cases.

Run workshops to analyze the business processes that are marked as a gap during the process verification.

Run workshops with the customer, and other relevant parties, to determine the scope of the project and the effort required to realize the project.

Review the business processes of the relevant solution with your customer. Do the business processes fit the customer needs?

You can define the default configuration for a solution.

If you generate test runs, the default solution configuration is also the default configuration for the generated test runs.

You can increase the version to a new major version.

In RapidValue the element version number consists of two parts which are divided by a point:

• Major version number in front of the point.
• Minor version number behind the point

Example: version is 2.4; where 2 is the major version number and 4 the minor version number.

You can increase the version to a new minor version.

In RapidValue the element version number consists of two parts which are divided by a point:

• Major version number in front of the point.
• Minor version number behind the point

Example: version is 2.4; where 2 is the major version number and 4 the minor version number.

If you finished the setup of a test run, and the test must be done, change the test run status to Scheduled. As a result, the test run can be started by the tester.

If you decide that a test run is not required, you can change the test run status to Skipped. As a result, the test run is not shown on the My test runs page.

Use areas to classify phases, processes, activities, roles and other business model elements at a high level according to, for example, purpose, required skills, knowledge, and resources.

The area is represented visually with color coding by function. For example, all green objects are related to the Sales area.

Examples of areas are: Sales, Marketing, Finance, Operations, Production, Support, IT, and HR.

You can use Google Translate to automatically translate RapidValue texts. To use the Google Translate translation service, you need a key from Google Translate. To activate the automatic translation, in the RapidValue Parameters, enter the key as provided by Google Translate.

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.

Use goals to define various business objectives, project goals, or compliance requirements.

You can use goals that are:

• Measurable: Measurable goals are also known as performance goals. Measurable goals set a quantifiable objective for the activities performed within a business domain and metrics can be used to monitor progress towards these goals.
• Non-measurable: Non-measurable goals are strategic in nature and express high-level objectives for the business, although not quantifiable.

You can set up metrics for these types:

• Metric
• KPI

An object is a data object, document or deliverable such as an item, invoice, physical document or product. An object can consist of other objects. For example, a sales order contains sales lines. Each object can have named attributes (fields).

Objects can represent, for example, inputs and outputs of processes and activities, or the content of messages exchanged internally or externally.

Objects are also used to relate application specific objects from different applications to each other.

Set up the organization structure of a typical target company for your solution.

You can use organizations as defined in the Organization administration module or create organizations in RapidValue.

You can set up general available process definitions that you can re-use within or over solutions.

Each process can have several flows. For example, you can create a separate flow for each different scenario of a process.

If you use remote task recording, set up the remote environment to allow task recordings to be retrieved from and saved to the environment where you manage your RapidValue content.

If you use remote task recording, you can specify for each applicable solution in the RapidValue content environment:

Define the roles in your solution.

A role is a business function that is done by a person. You can distinguish between two types of roles:

• Organizational roles: the lowest tier on the organization model.
• Functional roles: business processes are done by the organization to produce products or services for its customers. The horizontal flow of the process is divided into activities, which can be further divided into more detailed activities. Roles are assigned to these detail-level activities to reflect individual process responsibility and accountability.

You can use end-user guidance to indicate which processes and activities are applicable to the user. To do so, assign solutions to any combination of company accounts, specific users, and a specific language. Based on the role and position setup, the relevant processes for the user are searched for in the defined solutions.

In the Role setup field, you can indicate which role setup is used to create the end-user guidance:

• The roles as assigned to positions and persons in the RapidValue organization setup for the solution.
• The D365 FO security roles. To be able to use this, only the role setup in RapidValue is required as well. You don't have to set up the organization in RapidValue. Make sure to link each role in RapidValue to a D365 FO security role.

For each solution, you can define the solution references. You define a reference to another solution if you want to use elements of that solution in the current solution. Besides the elements of the current solution, you can only re-use elements of its referenced solutions.

In the dialogs, where you can select and assign existing elements, only the relevant elements of the current solution and its referenced solutions are shown.

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:

You can manually set a new version number.

In RapidValue the element version number consists of two parts which are divided by a point:

• Major version number in front of the point.
• Minor version number behind the point

Example: version is 2.4; where 2 is the major version number and 4 the minor version number.

For each solution, you can view its calculated solution statistics. You can use these high-level statistics to identify areas where you must put more effort in and keep track of how they change over time. You can also use the solution statistics for basic diagnostics and verification of solutions.

Verify the processes as described in the business process flow and mark them accordingly as Fit or Gap.

One of these scenarios is applicable:

• No gap categories defined
  Business processes can have these gap/fit indicators:
  • Not specified - No process verification is done for the business process.
  • Gap - Either the business process itself is set to Gap or one of its child business processes is set to Gap or to Fit.
  • Fit - The business process is set to Fit.
• Fit/gap categories defined
  Business processes can have these fit/gap indicators:
• Not specified - No process verification is done for the business process.
• [Gap category] - The business process is verified as a gap with a specific gap category.
• Gap - No process verification is done for the business process itself. One of its child business processes is set to Gap or to Fit.
  Note: Such a business process can have its own flow in which, for example, a gap can occur. In this case, you must manually reset the business process to the applicable gap category! If you do so, make sure to choose No in the Apply to child processes dialog.  
  
• Fit - The business process is set to Fit.
• [Fit category] - The business process is verified as a fit with a specific fit category.

You can view which applications are used in which processes. You can only do so for the applications that are defined for the solution.

You can view how the solution goals map to the business processes. The Goal map shows a matrix that indicates which business processes are used to reach which goals.