-
Notifications
You must be signed in to change notification settings - Fork 289
[Quality Management] Documentation #5429
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
ChethanT
wants to merge
3
commits into
main
Choose a base branch
from
private/chethant/QualityManagementDocumentation
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
165 changes: 165 additions & 0 deletions
165
src/Apps/W1/Quality Management/Documentation/qms-assisted-setup-wizard.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,165 @@ | ||
| --- | ||
| title: Assisted setup guide for quality management | ||
| description: Learn how to use the Quality Management assisted setup guide to configure quality inspections, automate test creation, and align workflows with your business processes. | ||
| author: brentholtorf | ||
| ms.author: bholtorf | ||
| ms.reviewer: bholtorf | ||
| ms.topic: overview | ||
| ms.search.form: | ||
| ms.date: 10/20/2025 | ||
| ms.service: dynamics-365-business-central | ||
| ms.custom: bap-template | ||
|
|
||
| --- | ||
|
|
||
| # Assisted setup guide for quality management | ||
|
|
||
| The Quality Management assisted setup guide can help you configure quality management features in [!INCLUDE [prod_short](includes/prod_short.md)]. The guide covers the initial configuration required to do quality inspections, and sets up automatic test creation based on business scenarios. | ||
|
|
||
| ## Start the guide | ||
|
|
||
| 1. [!INCLUDE [open-search](includes/open-search.md)], enter **Assisted Setup**, and then choose the related link. | ||
| 2. Choose **Set Up Quality Management** to start the assisted setup guide. | ||
|
|
||
| ## What to do in each step | ||
|
|
||
| The following sections describe each step in the guide. | ||
|
|
||
| ### Step 1: Welcome and Terms | ||
|
|
||
| This step introduces the guide. To proceed with the setup, agree to the terms and conditions. | ||
|
|
||
| ### Step 2: Getting Started Data | ||
|
|
||
| Choose whether to apply demonstration and sample data: | ||
|
|
||
| - **Apply Getting Started Data**: Downloads and applies basic setup data with useful examples and demonstration data. Getting started data helps you get going quickly or, if you're just exploring, evaluate whether the application fits your needs. | ||
| - **Do Not Apply Configuration**: Skips sample data installation. However, some basic setup data for common integration scenarios is applied. | ||
|
|
||
| > [!NOTE] | ||
| > The guide automatically suggests **Do Not Apply Configuration** if it looks like quality management is already configured or is in use. | ||
|
|
||
| ### Step 3: Permission Awareness | ||
|
|
||
| This step reminds administrators about permission requirements. You must assign the **Quality Inspection** permission set to users who make quality inspection tests. | ||
|
|
||
| ### Step 4: Usage Scenarios | ||
|
|
||
| Specify where you plan to use quality inspection tests: | ||
|
|
||
| - **Production**: Create tests when you record production output. Typical scenarios are when inventory is posted from the output journal, but could also be for intermediate steps or other triggers. | ||
| - **Receiving**: Create tests when receiving inventory from purchase orders, transfer orders, warehouse receipts, or sales returns. | ||
| - **Something Else**: Use quality inspection to create manual tests for other areas in [!INCLUDE [prod_short](includes/prod_short.md)], or if you want to manually configure them later. | ||
|
|
||
| > [!TIP] | ||
| > The steps in the guide differ, based on your selection. | ||
|
|
||
| ### Step 5: Production Test Configuration | ||
|
|
||
| > [!NOTE] | ||
| > This step shows only if you chose **Production** in the previous step. | ||
|
|
||
| Specify how to create production tests: | ||
|
|
||
| - **Create tests automatically**: [!INCLUDE [prod_short](includes/prod_short.md)] creates tests automatically when you record output. Use this option when tests must exist when production output occurs. | ||
| - **Manual test creation**: You manually create tests. Use this option when your process requires a person to create tests, or for ad-hoc testing scenarios like nonconformance reports or tracking rework. | ||
|
|
||
| ### Step 6: Receiving Test Configuration | ||
|
|
||
| > [!NOTE] | ||
| > This step shows only if you chose **Receiving** in the previous step. | ||
|
|
||
| Configure automatic test creation for receiving scenarios: | ||
|
|
||
| - **Purchase Receipts**: Automatically create tests when receiving via purchase orders. | ||
| - **Transfer Receipts**: Automatically create tests when receiving via transfer orders. | ||
| - **Warehouse Receipts**: Automatically create tests when receiving via warehouse receipts. | ||
| - **Sales Return Receipts**: Automatically create tests when receiving via sales returns. | ||
| - **Manual only option**: Choose this option if you only want people to manually create tests. For example, this option is useful for ad-hoc testing or tracking damage for received goods. | ||
|
|
||
| ### Step 7: Test Display Behavior | ||
|
|
||
| > [!NOTE] | ||
| > The options in this step vary, based on whether you set up automatic test creation. | ||
|
|
||
| Specify when to display tests to users: | ||
|
|
||
| - **Show automatic and manually created tests**: Tests show immediately when created. Use this option when the person doing the activity (like posting) is also the person who collects the test results. | ||
| - **Show only manually created tests**: Tests created automatically don't show immediately, but manually created tests do. Use this option when different people handle posting versus data collection. | ||
| - **Never show immediately**: Tests are always created in the background. Use this option when the person who creates tests shouldn't be able to edit them. This option ensures separation of test creation and completion. | ||
| - **Business Consideration**: Activities that trigger tests without direct interaction (background posting, web service integrations like Power Automate) create tests but doesn't immediately show them. | ||
|
|
||
| ### Step 8: Completion | ||
|
|
||
| When you choose **Finish**, the guide: | ||
|
|
||
| - Finalizes all configuration choices and applies them to the setup. | ||
| - Marks the assisted setup guide as completed. | ||
| - Enables quality management features. | ||
|
|
||
| ## Configuration Results | ||
|
|
||
| The guide configures the **Qlty. Management Setup** table based on your choices: | ||
|
|
||
| ### Production Settings | ||
|
|
||
| - Manual tests disable the production trigger. | ||
| - Automatic tests enable the trigger on production output posting. | ||
|
|
||
| ### Receiving Settings | ||
|
|
||
| - You can turn on or turn off each receiving type. For example, purchases, transfers, warehouse, and sales return. | ||
| - Manual-only option disables all automatic triggers. | ||
|
|
||
| ### Display Behavior | ||
|
|
||
| - Controls when to automatically show tests. | ||
| - Aligns with business roles and workflow separation. | ||
|
|
||
| ### System Activation | ||
|
|
||
| - Sets visibility to **Show** to enable quality management features. | ||
| - Refreshes the **Experience** tier settings for the current company on the **Company Information** page. | ||
|
|
||
| ## Technical integrations | ||
|
|
||
| The guide integrates with several [!INCLUDE [prod_short](includes/prod_short.md)] systems: | ||
|
|
||
| - **Guided Experience**: Tracks setup completion status and prevents you from rerunning the assisted setup guide unnecessarily. | ||
| - **Application Area Management**: Updates feature visibility and user experience settings. | ||
| - **Telemetry**: Logs completion events including environment name, company, and user for monitoring and support. | ||
| - **Auto Configuration**: Handles basic setup requirements and sample data deployment through configuration packages. | ||
|
|
||
| ## Best practices | ||
|
|
||
| This section lists recommendations | ||
|
|
||
| ### For administrators | ||
|
|
||
| - Assign the **Quality Inspection** permission sets to users before you run the guide. | ||
| - Consider your business processes when you choose whether to create tests automatically or manually. | ||
| - Align display behavior with organizational roles. Separate posting from inspection duties when that's appropriate. | ||
|
|
||
| ### For implementation | ||
|
|
||
| 1. Test the guide in a sandbox environment first to validate configuration choices. | ||
| 2. Document your selected settings for future reference and training. | ||
| 3. Plan user training based on the resulting test creation and display behaviors. | ||
|
|
||
| ### Examples of typical scenarios | ||
|
|
||
| - **Manufacturing Focus**: Enable production testing with appropriate display behavior for your workflow separation needs. | ||
| - **Distribution Focus**: Enable receiving testing for relevant document types (typically purchase receipts). | ||
| - **Comprehensive Quality**: Enable both production and receiving with **Show only manually created tests** to maintain workflow separation. | ||
| - **Evaluation/Demo**: Enable all features with immediate display for training and demonstration purposes. | ||
|
|
||
| ## Troubleshooting | ||
|
|
||
| - **Insufficient Permissions**: The guide checks for permissions, and displays an error message that instructs users to request permissions from their administrator. | ||
| - **Previous Configuration**: The guide finds an existing configuration and preserves the previous settings. However, it allows updates. | ||
| - **Getting Started Data**: Sample data installation only occurs if you chose that option and quality management isn't already configured, preventing duplicate or conflicting data. | ||
|
|
||
| ## Related information | ||
|
|
||
| [Quality management setup and configuration](qms-setup.md) | ||
| [Configure quality inspection grades](qms-configuring-grades.md) | ||
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove