-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
2
-
Severity 3 - Minor
-
Issue Summary
External products restored get included in the Discovered products daily notification as a brand new instance created.
Issue update from engineering team: CCP migration of existing product triggers customer notification email of new discovered product.
Steps to Reproduce
- Get a suspended external/discovered product.
- Reactivate it by renewing the subscription payment.
- The next day, the instance that was existing already is included as a brand new instance created the day before (while it was not).
Updated Steps to reproduce from engineering team:
- Migrate an existing HAMS discovered product to the new billing system (CCP)
- The next day, the product instance that was existing already is included as a brand new instance created the day before (while it was not) and triggers customer notification email about new discovered product.
Expected Results
Renewed instances should not be considered in the daily notification of Discovered Products.
Actual Results
The notification will include the instance renewed with the sentence “__ products were created in the past 24 hours outside of your organization”.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- mentioned in
-
Page Failed to load
[ACCESS-2106] Renewed products are included in the Discovered products daily notification
| Support reference count | Original: 1 | New: 2 |
| Description |
Original:
h3. Issue Summary
External products restored get included in the Discovered products daily notification as a brand new instance created. {+}Issue update from cs-birdo team{+}: CCP migration of *existing* product triggers customer notification email of *new* discovered product. h3. Steps to Reproduce # Get a suspended external/discovered product. # Reactivate it by renewing the subscription payment. # The next day, the instance that was existing already is included as a brand new instance created the day before (while it was not). {+}Updated Steps to reproduce from cs-birdo team{+}: # Migrate an existing HAMS discovered product to the new billing system (CCP) # The next day, the product instance that was existing already is included as a brand new instance created the day before (while it was not) and triggers customer notification email about new discovered product. h3. Expected Results Renewed instances should not be considered in the daily notification of Discovered Products. h3. Actual Results The notification will include the instance renewed with the sentence “{*}__ products were {color:#ff0000}created{color} in the past 24 hours outside of your organization{*}”. h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Issue Summary
External products restored get included in the Discovered products daily notification as a brand new instance created. {+}Issue update from engineering team{+}: CCP migration of *existing* product triggers customer notification email of *new* discovered product. h3. Steps to Reproduce # Get a suspended external/discovered product. # Reactivate it by renewing the subscription payment. # The next day, the instance that was existing already is included as a brand new instance created the day before (while it was not). {+}Updated Steps to reproduce from engineering team{+}: # Migrate an existing HAMS discovered product to the new billing system (CCP) # The next day, the product instance that was existing already is included as a brand new instance created the day before (while it was not) and triggers customer notification email about new discovered product. h3. Expected Results Renewed instances should not be considered in the daily notification of Discovered Products. h3. Actual Results The notification will include the instance renewed with the sentence “{*}__ products were {color:#ff0000}created{color} in the past 24 hours outside of your organization{*}”. h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
| Description |
Original:
h3. Issue Summary
External products restored get included in the Discovered products daily notification as a brand new instance created. Issue update from cs-birdo team: CCP migration of *existing* product triggers customer notification email of *new* discovered product. h3. Steps to Reproduce # Get a suspended external/discovered product. # Reactivate it by renewing the subscription payment. # The next day, the instance that was existing already is included as a brand new instance created the day before (while it was not). h3. Expected Results Renewed instances should not be considered in the daily notification of Discovered Products. h3. Actual Results The notification will include the instance renewed with the sentence “{*}__ products were {color:#ff0000}created{color} in the past 24 hours outside of your organization{*}”. h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Issue Summary
External products restored get included in the Discovered products daily notification as a brand new instance created. {+}Issue update from cs-birdo team{+}: CCP migration of *existing* product triggers customer notification email of *new* discovered product. h3. Steps to Reproduce # Get a suspended external/discovered product. # Reactivate it by renewing the subscription payment. # The next day, the instance that was existing already is included as a brand new instance created the day before (while it was not). {+}Updated Steps to reproduce from cs-birdo team{+}: # Migrate an existing HAMS discovered product to the new billing system (CCP) # The next day, the product instance that was existing already is included as a brand new instance created the day before (while it was not) and triggers customer notification email about new discovered product. h3. Expected Results Renewed instances should not be considered in the daily notification of Discovered Products. h3. Actual Results The notification will include the instance renewed with the sentence “{*}__ products were {color:#ff0000}created{color} in the past 24 hours outside of your organization{*}”. h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
| Description |
Original:
h3. Issue Summary
External products restored get included in the Discovered products daily notification as a brand new instance created. h3. Steps to Reproduce # Get a suspended external/discovered product. # Reactivate it by renewing the subscription payment. # The next day, the instance that was existing already is included as a brand new instance created the day before (while it was not). h3. Expected Results Renewed instances should not be considered in the daily notification of Discovered Products. h3. Actual Results The notification will include the instance renewed with the sentence “{*}__ products were {color:#FF0000}created{color} in the past 24 hours outside of your organization{*}”. h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Issue Summary
External products restored get included in the Discovered products daily notification as a brand new instance created. Issue update from cs-birdo team: CCP migration of *existing* product triggers customer notification email of *new* discovered product. h3. Steps to Reproduce # Get a suspended external/discovered product. # Reactivate it by renewing the subscription payment. # The next day, the instance that was existing already is included as a brand new instance created the day before (while it was not). h3. Expected Results Renewed instances should not be considered in the daily notification of Discovered Products. h3. Actual Results The notification will include the instance renewed with the sentence “{*}__ products were {color:#ff0000}created{color} in the past 24 hours outside of your organization{*}”. h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
| Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
| Support reference count | New: 1 |
| Remote Link | New: This issue links to "Page (Confluence)" [ 983224 ] |