microsoft / microsoft/BCApps

[Vendor] [Quality Management] Separate support for Assembly and Production scenarios in Quality Management

Open
#5,638 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Approved Team: SCM
Dominant language
AL
Stars
683
Forks
459
Avg merge
3d 26m
Merged PRs (30d)
633

Description

Describe the issue

Linked to AB#614485

Separate Assembly and Production in Quality Management

Current, Assembly and Production is set up together and the implementation is very tightly coupled with each other.

You see them together in the Quality Management Setup page
Image

You can create generation rule for either Production Orders OR Assembly Orders
Image

This creates issues for Essential users where the UI seems a bit odd. It exposes bits of production to the user who does not have premium license.

Image Image Image

This tight coupling in the UI, translates into code with code blocks like

Image

and

Image

The ask here is to separate the Quality Management to support both Assembly and Production separately so that both Essential and Premium users get cleaner experience with Quality Management.

Expected behavior

Support for Assembly and Production is setup and executed separately.

Steps to reproduce

Go through Quality Managemnt Setup page or the wizard, you can see Assembly and Production goes together and for Essential User, the user experience is a bit odd

Additional context

No response

I will provide a fix for a bug
  • I will provide a fix for a bug

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Quality Management Setup page and wizard, then trace how Assembly and Production setup and execution are currently coupled. Review the related code paths shown in the issue and define separate behavior for both scenarios, including the Essential and Premium user experiences. Done means Assembly and Production can be configured and executed independently.

Written by the indexing model from the issue text.

Assessment

Domain
backend, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.