Search results: Application

What is the challenge? Aha! Pages (Notes) provide a Status field in the UI, but this field is not available through the API. Because of this, teams cannot automate publishing workflows for documentation, release notes, or knowledge base pages. A...

What is the challenge? Currently, when documenting SOAP or XML request/response examples inside Aha! Knowledge, the preformatted object (used for code blocks) does not allow for direct “copy” functionality. Users must manually highlight text, wh...

What is the challenge? We work in many applications and Aha! can not build custom integrations for all of them. This makes it very hard to users of those applications to capture feedback and store it all in Aha! ideas. What is the impact? This res...

What is the challenge? Currently there is limited support with using prototypes generated from the AI Assistant and adding them as files/assets to other Aha! documents and fields such as record descriptions What is the impact? Limited use ...

I know that Aha includes the ability to attach documents at the Product Level. However, at my company, we want to maintain Policies & Procedures, but take advantage of the version control available in SharePoint. We want to link or integrate a...

We want to automate the documentation of all of our integration points (integration to Jira). We would like to see not only the integration name, rather we would like to see the specifics field mapping information , direction of integration etc...

Today the integration for this feature is not complete. It's not possible to search every document available in G Drive. It should be like this :

What is the challenge? If a KB visitor reviews the documentation and is not able to find the answers they need, we want to provide them two options for getting further help: Submit a Salesforce case directly from the Knowledge Base Open up a chat ...

Hi Aha! We would like to have a full understanding on how the various Aha! API endpoints (https://www.aha.io/api) relate to each other. Understood there is some customer facing documentation that explains the high-level of the Aha! Data Model. The...

Coming from JIRA, I'm finding the lack of keyboard or markup support in fields like this editor field is frustrating. With JIRA, I can use markup like {{monospace}} to make the text inline monospaced or ~strikethrough~ to make the text struck thr...