When you come across an EOL notification it can become cumbersome to hunt down the supplier contact information to learn more about the EOL or the products lifecycle.
The two new fields supplierURL and supplierEmail could solve this issue.
supplierURL would obviously be a URL. The creator would have to be instructed that the field SHALL be a "permanent" and "long-living" URL to product information. (In contrast to e.g. a press release.)
supplierEmail would obviously be an email address to get in touch with the supplier. This email-address SHALL be a functional account, not a personal account to avoid tight coupling to an individual. (e.g. support@company.com instead of john.doe@company.com)
When you come across an EOL notification it can become cumbersome to hunt down the supplier contact information to learn more about the EOL or the products lifecycle.
The two new fields supplierURL and supplierEmail could solve this issue.
supplierURL would obviously be a URL. The creator would have to be instructed that the field SHALL be a "permanent" and "long-living" URL to product information. (In contrast to e.g. a press release.)
supplierEmail would obviously be an email address to get in touch with the supplier. This email-address SHALL be a functional account, not a personal account to avoid tight coupling to an individual. (e.g. support@company.com instead of john.doe@company.com)