Limitation Notification
When customers develop verified software using DDC-I Software, the Target Developer Responsibilities in the PSAC indicates: The target system developer is responsible for subscribing to the appropriate DDC-I announcement mechanisms in order to ensure the target system developer is contacted when limitations are discovered. The US CAF Lotus Notes database is used to maintain the subscription list for each baseline.
The Problem Reporting How-To should be followed to create the appropriate PCRs for a Limitation and the affected Software Accomplishment Summary (SAS) documents.
Once the SAS has been published the following process should be used to notify customers of the limitation.
- Determine the set of baselines the affected component versions are a member
- Open the Report Tab in Sales Force
- Select Artifacts and Active Artifact Support
- The list will be all customers that have purchased CertArt. Note the Maintenance End date to identify active support.
- Notifications are limited to customers that have distributions with the impacted component; ie, if the customer's DDS does not include the impacted component, they will not be notified of the limitation.
- TODO: For each of the affected baselines, select the Limitation Notification group.
- You can open each entry and copy the email address. Another option is to export the selected items to another format such as Comma Separated Values and use that to copy the email addresses.
- TODO: The recommended approach for sending the email is:
- Open the Spprt Archive mail database
- Compose a new email to support@ddci.com and bcc the email list. Using bcc prevents customers from seeing other customers in the notification.
- The PCR number and the word Limitation should be in the Subject to allow future filtering of Sent email.
- The updated SAS and SCI should be attached along with a brief description of the new limitation
- TODO: Currently the Artifacts Product Description Form (See US CAF | 3 Artifacts | By Baseline) has a field to store a link to the notification.
Note: When opening an entry in the Notification Mailing List it instructs to send email from Person record in US Contacts database or setup a mass mailing from marketing. This may track an email sent in the person record, but I do not think would update the Artifacts PDF record. If we send from the Spprt Archive email database, there would be a record there. We may want to look at more automation here that can store links to the docs.
Limitations Needing Notification
| Component | Baseline | SAS PCRs | Author | Reviewer | Notification Sent |
|---|---|---|---|---|---|
| cffs-ecl | Fourpeaks (1.8.0) | PCRs:16887,16888 | Done | Done | Yes |
| cffsapi653p2 | Jupiter (3.0.1) | PCR:16736 | Done | Done | No |
| cffs-server | Jupiter (7.2.1) | PCR:16573 | Done | Done | No |
| cffs-server | Indie (7.1.1) | PCR:16574 | Done | Done | Yes |
| cffs-server | Fourpeaks/Elbert (6.1.0) | PCR:16575 | Done | Done | No |
| deos653p1-runtime | Indie (4.9.4) | PCR:16339, PCR:16531, PCR:16534 | Done | Done | Done |
| deos653p1-runtime | Jupiter (5.7.3) | PCR:16337, PCR:16530, PCR:16533 | Done | Done | No |
| deos653p1-runtime | Europa (mainline/5.8.5) | PCR:16529, PCR:16532 | Done | Done | N/A (all limitations resolved) |
| kernel | no name (7.6.1) | PCR:16767, PCR:6942 | Done | Done | No |
| kernel | Denali (7.6.2) | PCR:8004, PCR:8736, PCR:9691, PCR:16766 | Done | Done | No |
| kernel | Elbert (7.10.6) | PCR:16764 | Done | Done | No |
| kernel | Fourpeaks (8.3.1) | PCR:16765 | Done | Done | No |
| kernel | Greys (8.4.2) | PCR:16763 | Done | Done | No |
| kernel | Indie (9.2.3) | PCR:15942 | Done | Done | N/A per Kelly. Title fix only. |
| kernel | Jupiter (mainline/10.8.0) | PCR:16762 | Done | Done | No |
