Documentation
    {{docApp.userSession.userId}}
    {{docApp.userSession.userName}}
    {{docApp.userSession.email}}
    Issuer : {{docApp.userSession.issuerInstance}}
    Expires : {{new Date(docApp.userSession.validUntil).toLocaleDateString()}}

{{docApp.title}}

{{docApp.description}}

How can we help?

{{docApp.searchError}}
{{product.name}}

Searching in {{docApp.searchFilterBySpecificBookTitle}}

{{docApp.searchResultFilteredItems.length}} results for: {{docApp.currentResultsSearchText}} in {{docApp.searchFilterBySpecificBookTitle}}
Search results have been limited. There are a total of {{docApp.searchResponse.totalResultsAvailable}} matches.

You have an odd number of " characters in your search terms - each one needs closing with a matching " character!

{{docApp.libraryHomeViewProduct.title || docApp.libraryHomeViewProduct.id}}

{{docApp.libraryHomeViewProduct.description}}

  1. {{book.title}}

{{group.title || group.id}}

{{group.description}}

  1. {{book.title}}

{{group.title}}

{{book.title}}
More...

Ideas / Update

  • Article
  • 4 minutes to read

Operation Information

Updates the details of an idea in Aha!.

This is a Premium Integration.

Authentication

This operation requires authentication, the details of which can be securely stored on your instance in a KeySafe Key of type oAuth 2.0.

To create a key of this type:

  • In the Configuration area of your Hornbill instance, navigate to Platform Configuration > Security > KeySafe;
  • Click on the + Create New Key button;
  • On the resulting Create New Key form, choose oAuth 2.0 in the Type pick list;
  • Give the oAuth 2.0 KeySafe key a Title (this is the name / identifier for the oAuth 2.0 account as you will see it when using the cloud automation node in your workflows);
  • Optionally populate the Description field;
  • Populate the following fields accordingly, then click the Create Key button to create your new key:
Name Type Description
Client Id string Application Client Id
Client Secret string Application Client Secret
oAuth Scope string Application oAuth Scope
Authorize URL string Application Authorize URL
Access URL string Application Access UR
Response Type string Application Response Type
Additional Params string Application Additional Params
Additional Access Token Params string Application Additional Access Token Request Params
Grant Type string Application Grant Type
Refresh URL string Application Refresh URL
Refresh Grant Type string Application Refresh Grant Type
Refresh Body string Application Refresh Body
Revoke URL string Token Revoke URL
Token string Authentication Token
Refresh Token string Refresh Token
API Endpoint string Optional API Endpoint

Tip

In order to integrate with Aha!, you will first need to register Hornbill as an authorized application within your Aha! instance.

To do this, visit the Personal Settings page in your Aha! account, then click on the Developer option on the left-hand menu, and then click the OAuth Applications tab. Once the tab had loaded, click the Register OAuth Application button.

This will present you with a form containing 2 inputs:

  • In the first input, give the registered application a name. i.e. Hornbill
  • In the second input, enter the following: https://admin.hornbill.com/oauthcallback.php
  • Click the Create button
  • Once the application has been registered, Aha! will provide you with the information you need to populate the above fields.

Revoking Access

If at any point you wish to revoke access to any of the above accounts from your Hornbill instance, just delete the relevant KeySafe key(s) from the KeySafe list.

Warning

This will revoke the rights of any existing Cloud Automation Node in your Hornbill Workflows that are using the revoked oAuth 2.0 account, so you will need to manage these workflows accordingly.

Input Parameters

Display Name ID Type Description Required Supported Values
Idea Key id string Reference key of the Idea to be updated. Yes None provided
Name of the Idea name string Name No None provided
Description description string Description of the idea and it can include HTML formatting. No None provided
Workflow Status workflow_status string Status of the idea and it must be one of the valid status values for the selected product. No None provided
Tags tags string Tags can be automatically assigned to the new idea. If more than one tag is used then tags should be separated by commas. No None provided
Categories categories string Names of the existing categories the idea should be assigned to. If more than one category is used then categories should be separated by commas - note that in a CSV, quotes must be used around fields that contain commas. No None provided
Assign To Email assigned_to_user string Email address of user that is assigned the idea. No None provided
Feature ID feature string Feature ID of the feature that the idea was promoted to. No None provided
Initiative ID initiative string Initiative ID of the initiative that the idea was promoted to. No None provided
Master Feature ID master_feature string Master feature ID of the master feature that the idea was promoted to. No None provided
Initial Votes initial_votes integer Number of votes to seed the vote count with. No None provided
Visibility visibility string Initial visibility of the idea (‘aha’, ‘employee’, or ‘public’ - ‘aha’ is the default) No None provided

Output Parameters

Display Name ID Type Description
ID id string Idea ID
Reference reference string Idea Reference Key
URL url string Idea URL
  • Version {{docApp.book.version}}
  • Node {{docApp.node}} / {{docApp.build}}
In This Document