Our Unqork Community facilitates best in class Q&A, averaging a >99% reply rate and >80% answer rate over the past 2+ years. However, how quickly you receive a solution can depend on how you ask your question. 

Use a descriptive title

• Pose your title as a question.
• Use keywords specific to the question, like product features or components. 

These guidelines from StackOverflow are good to consider: 

Write a title that summarizes the specific problem

The title is the first thing that potential answerers will see. If your title isn't interesting, they won't read the rest. Also, without a good title, people may not even be able to find your question. So, make the title count:

• Pretend you're talking to a busy colleague and have to sum up your entire question in one sentence: what details can you include that will help someone identify and solve your problem? Include any error messages, key APIs, or unusual circumstances that make your question different from similar questions already on the site.
  a...]

• If you're having trouble summarizing the problem, write the title last—sometimes, writing the rest of the question first can make it easier to describe the problem.

Provide a detailed description

In the Details field, enter a thorough description for your post. The text field gives you the ability to format text, organize your post, and add screenshots.

Use the following suggestions to help you create a meaningful description:

• Clearly describe your desired result.
• Provide screenshots or sample data.
• Add reproducible steps or share a POC.
• Specify relevant features or components.
• Do not share private information or data.

Share a POC in the Community Collaboration workspace (Training environment) 

A helpful way to accomplish the bullet points above is to share a proof-of-concept (POC). To do so, follow these instructions: 

Example 

Can anyone help explain what the Decisions component’s Editable Output Type does?

Documentation link: https://docs.unqork.io/Content/A05-ModEditor-Data_Event/A05004-Decisions_Component.htm

 

Choose the right forum 

• Platform and Configuration Q&A
  • How do I build…? 
  • Is it possible to…?
• Troubleshooting
  • Unexpected behaviors
  • Can you help me solve…?
• Advice & Strategy
  • Open-ended discussions.
  • Approaches to teams, projects, or careers.
• Use Case Showcase
  • Demos and Overviews
  • When would I use…?
    • Example: 

Mark the answer

Indicating when your question is answered has two benefits: 

1. Prioritizes Open Questions: Experts and others’ in the community can focus their attention elsewhere, rather than adding help when it’s no longer needed.
2. Rewards Others for Helping: Q&A requires the experience and contributions of others. Marking answers grants points that reward and incentivize experts and other Creators to contribute, especially as they pursue SME status. 

As another benefit, you also receive 10 points for marking the answer, helping you move up the leaderboard, earn badges, or work towards SME status.
 

Don’t delete your question, share the answer!

Often times you might solve your question on your own. Rather than delete your question, share how you solved it. 

This helps build our knowledge base while earning you points towards recognition, badges, and SME status. 

Tip: Avoid weekends (if you can)

You can ask a question at any time, but it’s better to ask earlier in the week if you have the option. Data shows that questions asked on Fridays or over the weekend can sometimes get lost in the activity feed.

But don’t fret, our Featured Questions incentives help ensure questions won’t get lost.