Flows

Flow	Description
Analyze gaps	Analyze the business processes that are marked as a gap during the process verification. This usually results in questions to be answered, answers to questions, and requirement specifications to solve the gaps.
Assess scope and effort	Create the scope of the solution and estimate the effort required to deliver the customer solution. The output of this assessment is an approved Scope statement document. You can use milestones for the implementation project to indicate when each business process is scheduled to be implemented.
Assign procedure activity	Before you record a scenario or a process, usually, you first assign a procedure activity to the relevant business process. If you want to: Model a scenario, you assign the procedure activity to a business process of type Scenario. Record a process, you can assign the procedure activity to any business process. Usually, this is a business process to which no flow is assigned. You can assign procedure activities to a business process in several ways: Assign an existing activity as procedure activity. Create and assign a new activity as procedure activity. By default, this activity is of type Scenario. Assign a copy of an existing activity as procedure activity.
Assign training	Once a training is developed, you can start training people. To do so, you: Set up the trainees. Assign the relevant modules to each of the trainees.
Collect and manage questions	During the analysis phase, you can at any time collect and answer questions with regards to the scope of the implementation project and which business processes fit or don't fit the customer needs.
Collect and manage requirements	During implementation, you can at any time collect and specify requirements with regards to the scope of the implementation project and what need to be done to fit the available business processes to the customer needs. You can also specify requirements when you define the business strategy. You can link: - Several requirements to a business process. - A requirement to several business processes.
Compare flows	You can make a visual comparison between any two flows. For example, if a flow was created based on another flow you may want to view your changes compared to the original flow. You can also compare to other flows in the same process or library.
Create and design exercises	Use exercises to practice, for example, the execution of a process as learned in a lesson. You can create exercises in several ways. The basic flow is: Create the exercise. Assign the exercise to a business process. Assign the business process exercise to a module, topic, or lesson in the module hierarchy. You can do two or all steps in one go: Directly create an exercise for a business process. Generate a module. On module generation, exercises are created and assigned to business processes. These business process exercises are assigned to a module, topic, or lesson in the module hierarchy. Each exercise that you create is stored in the 'exercises library' which you can view on the Exercises page. You can assign these exercises to a business process.
Create and design modules	Use a module to train, for example, a functional area or a phase in your business processes. Examples: procurement or implementation. A module can have several topics, lessons, and exercises.
Create scenario	To model a scenario, first add a business process of type Scenario. Usually, you add a scenario to a business process with a flow assigned. As a result, the flow is also added to the added scenario business process.
Define activities	Create activities and define the steps that are required to do the activity.
Define application elements manually	You can manually define the elements that are part of your application. You can define these types of application elements: Forms Reports Commands Components
Define business process settings	For each business process, you can define these settings: See also references Categories Work package
Define configuration	You can define the configuration of the system on which a test is done. A configuration can contain any information that defines the system, like the software version, the server on which the software is run, the settings to be used, any required devices, and so on. For each solution, you can define several configurations. You can also set 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.
Define D365 FO applications	Define the D365 FO applications that can play a role in your solutions. For each D365 FO application, you can define the elements that are part of the application. You can define these types of application elements: Forms Reports Commands Components You can also define the menu for each application to define how the application elements can be accessed.
Define flows	Define the flows that are related to the business processes in the business process hierarchy. A flow is a detailed description of how to do a process.
Define goals and metrics	Define the strategy for the solution in terms of goals and metrics
Define test cases	Use test cases to define and prepare the test procedures for the test suites. In RapidValue, usually, you use a test case to test an activity. For each test case, you can define: A description of what is to be tested. Where the test case is applicable. The steps to be done to finish the test case. A description of the expected test result. The focus of this flow is on how to create and maintain test cases in the test library.
Define test runs	As a test manager, use test runs to define and manage the actual tests to be done. You generate a test run based on a test. For each test run, you can: Review and change the test run settings like, the test date, priority, and configuration. Assign it to a tester. Make it available to be done.
Define test suites	Use test suites to define and prepare the tests to be done. In RapidValue, usually, you use a test suite to test a flow. For each test suite, you can define: A description of what is to be tested. Where the test suite is applicable. The relevant test cases. A description of the preparations that are required before you can start the test. A description of the expected test results. A description of the required cleanup. For example, delete some data that is created during the test. The focus of this flow is on how to create and maintain test suites in the test library.
Define tests	Use tests to define the tests to be done for a specific node in the business process hierarchy. The basis for a test is a test suite. Besides the test suite, you can also define these test-specific settings: Test type Priority Status Owner Notes
Define web applications	Create a web application that can play a role in one of your solutions. For a web application, you can define forms, reports, or commands that open a URL.
Design business process hierarchy	Design the business process hierarchy of your solution. The business process hierarchy reflects the generic business processes for a typical target company for your solution. In the business process hierarchy, you can use these types of nodes: Value chain Supporting processes Phase Group Process Scenario Activity Notes This flow represents the advised sequence in which the business process hierarchy is designed. If required, you can of course design the business process hierarchy in another sequence.
Design flows	Design a flow to define: The sequence of activities and processes. The decision points and alternative paths in the process. Which role is responsible for which part of the flow. Each flow is related to a process. The process type defines the flow design options: Process: You can design a process flow with activities, lanes, sub-processes, gateways, events, and connect these objects in the sequence to be done. Value chain, Phase, Process group, Supporting process: Additional to the design of a Process type flow, you can add business processes from the hierarchy to the flow design. Notes This flow represents the usual sequence in which the process flows are designed. If required, you can of course design the flow in another sequence.
Evaluate goals and identify opportunities	During implementation, you can evaluate the goals in your strategy to identify the opportunities for your company. You can, for example, schedule evaluations for each phase of the implementation project. You can use the evaluation to do a structured assessment of your business goals and the related business opportunities. During the evaluation, you rate the goals on these properties: Value - Rate the business value of the goal. Maturity - Rate the maturity of the processes and the technology that are used to reach the goal. Complexity - Rate the effort that is required to reach the goal. For example, with regards to regulatory compliance. Performance - Rate the performance of the business with regards to the goal. Are the key objectives met? Based on the result of this assessment, you identify the opportunities for each goal. In general, you rate the opportunity as: High or very high if a goal has high business value, low maturity, high complexity, and low performance. Low or very low if a goal has low business value, high maturity, low complexity, and high performance. The result of an evaluation answers questions like: Where do we really need detailed business process flows first? Where can we, for-the-time-being do with just a textual description of the process? So, the evaluation results in the focus areas for, for example, the implementation phase you are about to start.
Evaluate goals and identify opportunities - Strategy	You can evaluate the goals in your strategy to identify the opportunities for your company. You can, for example, schedule evaluations for each phase of an implementation project. You can use the evaluation to do a structured assessment of your business goals and the related business opportunities. During the evaluation, you rate the goals on these properties: Value - Rate the business value of the goal. Maturity - Rate the maturity of the processes and the technology that are used to reach the goal. Complexity - Rate the effort that is required to reach the goal. For example, with regards to regulatory compliance. Performance - Rate the performance of the business with regards to the goal. Are the key objectives met? Based on the result of this assessment, you identify the opportunities for each goal. In general, you rate the opportunity as: High or very high if a goal has high business value, low maturity, high complexity, and low performance. Low or very low if a goal has low business value, high maturity, low complexity, and high performance. The result of an evaluation answers questions like: Where do we really need detailed business process flows first? Where can we, for-the-time-being do with just a textual description of the process? So, the evaluation results in the focus areas for, for example, the implementation phase you are about to start.
Explore solutions	You can explore the solution configuration of a solution and its related solutions. To explore which elements are related to a specific element in a solution configuration, pin an element. You can pin an element of these types: Business process Flow Activity Application Requirement The solution explorer gets the solution configuration data from the selected snapshot. If the latest snapshot is not up to date, you can create a new snapshot.
Explore tests	You can explore the test configuration of a solution and its related solutions. To explore which elements are related to a specific element in a test configuration, pin an element. You can pin an element of these types: Requirement Business process Test suite Test run Role The test explorer gets the test configuration data from the selected snapshot. If the latest snapshot is not up to date, you can create a new snapshot.
Export business processes to LCS	You can export a business process hierarchy to a business process library in LCS. On export to LCS, you can choose to export: The full business process hierarchy. Only a selected part of the business process hierarchy. Only the business processes with a specific category. The business process library in LCS is structured based on the business process hierarchy and the flow activities, as set up in RapidValue. If a flow activity has a task guide linked to it, this task guide is uploaded as well.
Export configuration	You can export most elements, as defined in RapidValue, to 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 is created in the content package. If you want to use an XML data file instead of a content package, you can create it from a content package. A data file is an XML file of type RVDATA that contains all configuration data of the content package.
Export task guides - Task guide search	You can export task guides to create security scenarios in the Security and compliance studio. On export, the applicable task guides are searched for. The search for and export of task guides is different depending on the business process setup. If the business process has: 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. This diagram shows the task guide search process if you export task guides.
Filter business process hierarchy	You can apply a filter to business process hierarchies to only show the business processes that meet the defined conditions.
Import configuration from content package	You can import a configuration 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. You can import a content package from and into any D365 FO environment with RapidValue installed.
Link sub activities to procedure activity steps - Model scenario	If you have recorded a procedure activity for a scenario, the steps of the procedure activity cover several activities of the related flow. You can link procedure activity steps to the relevant flow activities. You can also link procedure activity steps to existing or new activities. You can also add procedure activity steps to a sub activity or replace the sub activity steps with procedure activity steps.
Link sub activities to procedure activity steps - Record flow	If you have recorded a flow, the steps of the related procedure activity can cover several sub activities. You can link procedure activity steps to existing or new activities. You can also add procedure activity steps to a sub activity or replace the sub activity steps with procedure activity steps.
Manage translations	You can translate RapidValue elements that can be a part of your solution. You can translate the elements inside or outside D365 FO. To translate the elements outside D365 FO, for example by a translation agency, you can create an export file. The D365 FO system language is the original language of your solution and its elements. Prerequisites: You can only use the translations functionality in RapidValue if the Translations configuration key is enabled. If you want to automatically translate RapidValue content, you must activate auto-translation on the RapidValue parameters. You can translate these RapidValue elements: Solution: Solution Business process hierarchy Organization hierarchy Business model: Goals Metrics Areas Concepts Process model: Business processes Flows Activities Processes Objects Applications Organization model: Organizations Roles Skills Training: Module hierarchy Exercises Exercise activities
Model flows	You can model the flows of your solution. A flow is a detailed description of how to do a process.
Model scenarios	You can model scenarios for a business process with a flow assigned. A scenario can be, for example, a specific route through an existing flow.
Monitor tests	As a test manager, you can monitor the tests that are in progress. You can do so on these levels: Progress bars. Tests Test runs
Monitor training	If trainees are assigned to their training, you can monitor the progress they make.
Publish and deploy website	You can publish a website from RapidValue in which you can include your solutions or an already existing website. You can store a published website in several ways: RapidValue file share Local folder Azure file storage You can deploy the website from the location where you stored it. Note If required, you can exclude a part of a solution from publishing to a website. To do so, set the relevant business process to 'Out of scope'. Refer to 'Define project scope'.
Publish business process implementation documents	In RapidValue, you can publish several types of business process implementation documents: Scope statement Process verification Gap analysis
Publish business process modeling documents	In RapidValue, you can publish several types of business process modeling documents: Process specification Flow specification Activity procedure
Publish business process testing documents	In RapidValue, you can publish several types of business process testing documents: Test plan Test specification Test report
Record processes	You can use the task recorder to record a whole process in one go. This results in a longer task recording than usual. Later, you can link steps of this task recording to several related existing or new activities.
Review business definitions	Review or set up the business-related definitions that are available to the relevant solutions.
Review organization definitions	Review or set up the organization-related definitions that are available to the relevant solutions.
Review process definitions	Review or set up the process-related definitions that are available to the relevant solutions.
Review test definitions	Review or set up the test-related definitions that are available to the relevant solutions.
Set up application menu	You can set up a menu for each application to define how the application elements can be accessed. You can, for example, use the application menu to link activities to application elements.
Set up Azure DevOps integration	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.
Set up business process-specific remote task recording using categories	With RapidValue, you can record and play task guides, either directly in the current environment or in another D365 FO environment. You can set up and apply remote task recording on business process level using categories. Note: You can use business process-specific remote task recording only to record procedure activity steps. So, business process-specific remote task recording is applied only if you start recording on the Business process designer page, on the Procedure tab. To use business process-specific remote task recording: On the RapidValue content environment (this is the environment from which you start the task recording): Set up a connection to the remote environment. Of this connection, only the defined 'Internet address' is used! Set up a category to define the purpose of a business process and the connection to the relevant remote environment. Define a category for the applicable business processes. Set up remote task recording for the solution to which the business processes belong. Register the Microsoft Entra ID app that is used to connect back from the remote environment to the RapidValue content environment. This is the Microsoft Entra ID app as defined in the remote task recording parameters on the remote environment. On the remote environment (this is the environment where you want to do the task recording): Set up the remote task recording connection parameters. If you have set up both general and business process-specific remote task recording, the business process-specific remote task recording is applied.
Set up general remote task recording	With RapidValue you can record and play task guides, either directly in the current environment or in another D365 FO environment. You can set up and apply remote task recording on a general level. To use general remote task recording, you: Install RapidValue on both the RapidValue content environment and the remote environment. Enable remote task recording for the applicable solution in the RapidValue content environment. Set up the Task recording parameters in the RapidValue parameters of the remote environment. If you have set up both general and business process-specific remote task recording, the business process-specific remote task recording is applied.
Set up remote task recording	With RapidValue, you can record and play task guides, either directly in the current environment or in another D365 FO environment. You can set up and apply remote task recording on these levels: General To use general remote task recording, you: Enable remote task recording for the applicable solution in the current environment. Set up the Task recording parameters in the RapidValue parameters of the remote environment. Business process-specific using categories To use business process-specific remote task recording, you: Set up a connection to the remote environment. Set up a category to define the purpose of a business process and accordingly the connection to the relevant remote environment. Define a category for the applicable business processes. If you have set up both general and business process-specific remote task recording, the business process-specific remote task recording is applied.
Set up translation parameters	Set up the RapidValue parameters to be able to: Enable translations. Enable multi-language name display. Activate auto-translation.
Set up websites	Before you publish a RapidValue solution as a website, define the contents of the website and where you store it. You can store a published website in several ways: RapidValue file share Local folder Azure file storage
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.
Test	As a tester, use test runs to do the test and report the results. For each test case in the test run, you can: Define the status. Enter a conclusion. Add requirements.
Use Azure DevOps integration	If you have set up an integration between a RapidValue solution and an Azure DevOps project, you can synchronize the data between these two. With this integration you can synchronize RapidValue entities with DevOps work items in both directions. The data is synchronized according to the DevOps mapping setup. You can synchronize: Business processes Requirements You can also: Manually map a RapidValue entity to a DevOps work item. For example, if you have made some changes in the business process hierarchy and the mapping is undone. Monitor the mapped work item info, with its mapped entities, related work items, and synchronization history. Open a mapped work item in DevOps from RapidValue.
Verify processes	Review the business processes of the relevant solution with your customer. To what extent do the business processes fit the customer requirements. Mark the business processes that don't fit the customer needs as a gap. This usually results in questions to be answered and requirements to solve the gaps. You can use fit categories and gap categories to indicate the sort of fit or gap.