Discussion

83
Views
BrendanHoran_GCS Member since 2011 79 posts
MOD
Posted: July 27, 2015
Last activity: July 27, 2015
Closed

Community Tip: Reference Your Support Requests

One of the many goals of this Support Community is to offer a place to discuss issues and questions with a large audience instead of entering a support request. By using this community, you can (hopefully) get quick feedback from many different perspectives while capturing a historical record of your discussion for anyone who might have the same question. This not only benefits you and other participants, but the entire Global Customer Support organization; allowing us to work with you and focus on the more complex and/or proprietary issues that cannot be openly discussed in a community such as this.

All that said, we realize that many of the discussions posted here have an associated support request. Perhaps you've raised an SR without knowledge of this community and have been referred here by one of our support engineers. Or maybe you've entered an SR and have posted your issue here while you wait to see what kind of feedback you get from the global community. Perhaps your discussion didn't have an SR to begin with, but based on the direction of your conversation, it was determined you should raise an SR to further investigate your issue with a support engineer.

Whatever the case, help us help you by associating your SR number with your discussion and tagging it appropriately.

To associate your SR, just enter the ID number in your discussion's Related Work field. Then tag your discussion based on whether it existed prior to posting to the community or not. If the SR existed prior to posting to the community, tag your discussion with srexisted. If the SR was created after you posted to the community, tag your discussion with srcreated.

Be aware that the associated SR number will show up as a link, but rest assured only people in your organization with the appropriate permissions and GCS personnel will be able to access it.

Moderation Team has archived post
Share this page LinkedIn