See which training, bids, requirements, market watches and organisations a product change reaches, confirm or dismiss each proposed follow-up with a reason, and ask the assistant to explain or trace the impact.
When a product changes, other parts of ComplyTrain may depend on the old state: people trained on a configuration, a tender that bids it, requirements whose evidence describes it, a market watch that should follow it, and organisations that must be told. ComplyTrain asks every connected module what the change reaches and reports the answer in two ways:
Notifications go straight to a person's My Tasks on the Dashboard. Telling someone that something changed cannot do damage, so these are not held back.
Proposals are changes another module would make, such as re-issuing a course. They wait on the product's Bill of materials tab under What this change affects, and nothing happens until someone confirms them.
A module can only report what it knows about, so the review depends on the connections recorded on the product. See connected records.
Product location: /products/{productId}/bom (fallback: /products). Open the product in Products and select the Bill of materials tab.
Task | Who can do it |
|---|---|
See proposals, Explain the impact and Trace a change | Anyone with View Products ( |
Confirm, Dismiss or Mark as read a proposal | Change Product Lifecycle State ( |
An Admin can do both. People without the permission see the proposals but not the buttons.
Each notification and proposal goes to the person responsible for the affected record in its own module: the course owner in Training, the bid lead in Tenders or the requirement owner in Requirements. When the record has no responsible person, it goes to the product owner, and when the product has no owner, or the owner is no longer a user, to the person who made the change. Organisations have no responsible person in Stakeholders, so their notifications go to the product owner. Set the product owner as described in maintaining a product record. A proposal describes a product, so only people cleared to open the product can see it.
Product location: /products/{productId}/bom (fallback: /products). Open the product in Products and select the Bill of materials tab.
Change | Where you make it | Modules asked |
|---|---|---|
Release a version | Release this version on the Overview tab | Training, Tenders, Requirements, Stakeholders |
Withdraw a version | Withdraw on the Overview tab | Training, Tenders, Requirements, Stakeholders |
Mark the product obsolete | On the product record | Training, Tenders, Stakeholders |
Place a version on a market | Place, or Place on the market now when adding a market | Media Monitoring |
Take a version off a market | Withdraw on the Markets tab, or placing another version on the same market | Stakeholders, Media Monitoring |
Record a part going out of production | Obsolescence on the Bill of materials tab, setting Not for new designs, Last buy or Obsolete | Stakeholders |
A release is checked against the new version, every version it replaces on any market, and everything linked to the product as a whole. Most links point to the versions being replaced, so this is where the affected training and bids are found. For releases and markets, see versions and release and markets.
Product location: /products/{productId}/bom (fallback: /products). Open the product in Products and select the Bill of materials tab.
Every result has a priority. Act now means something is wrong and stays wrong until someone acts. Look at this means someone should check. For information means there is nothing to decide.
Module | What it reports | Priority | Proposal |
|---|---|---|---|
Training | People part-way through a linked course | Look at this | None; notification only |
Training | People whose qualification on a linked course has lapsed | Act now | Re-issue the course to everyone who has held it, when the link is set to Re-issued on change |
Training | People whose completion of a linked course is current, when the link is set to Re-issued on change | Look at this | Re-issue the course to those current holders |
Tenders | Each tender workspace that bids an affected configuration | Act now once the response is submitted, won or lost; otherwise Look at this | Flag the product binding in the tender |
Requirements | Linked requirements that apply to the product or to an affected version and have critical or major criticality, grouped by standard | Act now when any is critical; otherwise Look at this | Record that the requirements need re-assessing |
Media Monitoring | A new market that none of the product's watches covers | Look at this | Extend a watch to cover the market |
Media Monitoring | Watches that still cover a market the product has left | For information | None; notification only |
Stakeholders | Organisations linked to the product or configuration whose relationship has not ended, grouped by relationship, for example "2 distributors may need telling" | Act now for notified bodies and regulators; otherwise Look at this | None; contact them yourself |
Requirements marked Excluded, and requirements of minor or recommended criticality or with none recorded, are not reported. A re-assessment of every clause would bury the ones that matter.
Product location: /dashboard. Open Dashboard and find My Tasks.
Every result becomes a task in the recipient's My Tasks on the Dashboard, with its priority. Select the task to open the affected record in its module. A notification-only task can be marked complete from My Tasks; a task that carries a proposal cannot, because ticking a box must not stand in for a decision. Decide on it on the product instead. See the dashboard.
Proposals appear in What this change affects at the top of the product's Bill of materials tab, for every version of the product. The tab badge counts them, and on the Overview tab Needs your review has a button with the number of change proposals that takes you there.
If the same change is assessed again while a proposal for it is still open, no second proposal is raised.
Product location: /products/{productId}/bom (fallback: /products). Open the product in Products and select the Bill of materials tab.
The panel starts with a reminder that nothing in it has happened yet. A red badge, for example 2 need attention now, counts the Act now proposals, which are listed first.
Each proposal card shows:
the priority, the module that raised it and a title, for example "12 people are qualified on the previous configuration for Operating the XR-5";
a description of what changed for that record and the proposed action;
when it was raised;
Open, which takes you to the affected record: the course, the tender, the product's requirements in Requirements, or the watch;
What happens if you confirm, the action in the module's own words.
Product location: /products/{productId}/bom (fallback: /products). Open the product in Products and select the Bill of materials tab.
Read What happens if you confirm and open the record if you need more context.
Choose Confirm.
The module carries out the action on your authority and the proposal leaves the panel. What confirming does:
Module | Result of Confirm |
|---|---|
Training | The course is assigned again to the people the proposal names: those whose completion is current for a current-holder proposal, or everyone who has held it for a lapsed-qualification proposal. People who already have an open assignment of the course are skipped. The assignments appear in Training like any other; see assigning training. |
Tenders | A note is added to the product binding in the tender: "Configuration change: … Review the response against the current configuration." The bid team sees it in the tender's product list. Existing notes are kept. |
Requirements | The proposal itself is recorded as the acknowledgement that the requirements need re-assessing against the new configuration. The requirements are not changed. |
Media Monitoring | The market is added to the named watch, so news for that market reaches its digest. |
If the module cannot carry out the action, the panel gives the module's reason and says that the proposal is still open. Nothing has changed, and you can try again or dismiss it. A proposal can be confirmed only once; if two people act at the same moment, the second is told to reload.
Product location: /products/{productId}/bom (fallback: /products). Open the product in Products and select the Bill of materials tab.
Dismiss a proposal when you decide the action is not needed.
Choose Dismiss. For a proposal with no action to carry out, the button is Mark as read.
Enter the reason in Why not. It is required: without a reason a dismissal cannot be told apart from nobody having looked.
Choose Dismiss, or Cancel to keep the proposal open.
The reason is recorded against the proposal. An auditor asking why a configuration change produced no follow-up will look for it, so write the actual judgement, for example "Block II changes the enclosure only; the operating procedure taught in this course is unchanged."
Product location: /products/{productId}/bom (fallback: /products). Open the product in Products and select the Bill of materials tab.
What these changes affect, at the bottom of the Bill of materials tab, turns the open proposals into prose you can act on or forward.
Choose Explain the impact. The panel shows Reading the data and writing… while the assistant works.
Read the explanation. It describes only the open proposals: it does not add impacts the modules did not find or leave any out.
The explanation is not saved; choose the button again for a fresh one. With no open proposals, the panel says in green that nothing is outstanding. The footer names the brief the assistant wrote under, which an administrator can change. The button needs an assistant set up for your organisation.
Product location: /products/{productId}/bom (fallback: /products). Open the product in Products and select the Bill of materials tab.
Trace a change, in the header of the Bill of materials panel, opens the Product Specialist assistant on the selected version. It reports the parts that are obsolete, not recommended for new designs or in a last-buy window, and what sits above each one in the assemblies. Ask follow-up questions, such as which markets would be hit first.
The assistant cannot make the change, mark a part obsolete or release a version; it only traces. The conversation is not saved to the product. The button appears when an assistant is set up for this task. See the Product Specialist assistant.
Product location: /products/{productId}/bom (fallback: /products). Open the product in Products and select the Bill of materials tab.
The XR-5 radar has Block I released. Block II changes the operator console, and you release it.
The release replaces Block I. Training finds the course "Operating the XR-5", linked to Block I and set to Re-issued on change, with 12 people whose completion is current. Tenders finds the workspace "Coastal surveillance 2027", which bids Block I and was submitted last month. Requirements finds four major EN 60945 requirements linked to the product.
The course owner, the bid lead and the requirement owner each receive a task in My Tasks. The product's Bill of materials tab shows three proposals, with Act now on the submitted tender.
The bid lead opens the tender proposal from the task, sees the response cites Block I and asks the product manager, who holds Change Product Lifecycle State, to confirm it. The note appears on the product binding and the bid team decides whether to tell the customer.
For the course, the product manager confirms, and the 12 current holders receive a new assignment.
For the requirements, the requirement owner checks the clauses. Two concern the console, so the proposal is confirmed, which records that re-assessment is needed, and the work is raised in Requirements. Had none been affected, the proposal would be dismissed with that reason.
The product manager chooses Explain the impact to paste a summary into the change record.
