Jira Spoke Get Editable Fields Dynamic Inputs failing to retrieve fields

Todd O
Tera Guru

‎06-08-2022 10:08 AM

I'm getting an error response with an Action from the Jira Spoke (V3.2.1) called "Get Editable Fields." It continues to give this error: "Incorrect output was received from a dynamic action." This action has Dynamic inputs that will retrieve from Jira, at design time in Flow Designer, all the editable fields that are available. It then provides ability to pick Jira fields when using actions such as "Create Issue" or "Update Issue." Below is what I've done for trouble shooting on this along with screen shots.

Error that I'm receiving: find_real_file.png

  1. The "Get Editable Fields" action expects two parameters. Both of them are of type string. See image below. For the connection alias, it's supposed to be the sys_id of the alias. I've tried all variations of values in the "Connection Alias" below as you'll notice in subsequent steps below that the Action expects it to be a JSON string.  Here are the values I've tried and all of them are failing.
    1. Here are variations that I've tried in the "Connection Alias" field. None of them work.
  1. '{"value": "629ad2bfdb1893005963ff041d961971"}'
  2. "{'value': '629ad2bfdb1893005963ff041d961971'}"
  3. {"value": "629ad2bfdb1893005963ff041d961971"}
  4. {'value': '629ad2bfdb1893005963ff041d961971'}
  5. 629ad2bfdb1893005963ff041d961971
  • find_real_file.png

2. Below is a snippet of the Get Editable Fields step that parses the sys_id for the connection alias. I know for 100% certainty that my sys_id is valid because I can successfully run that last line of the code shown in image below through a background script. I'm also 100% certain that the Jira issue key (JT01-4168) exists in my Jira instance.

find_real_file.png

 

The only thing I can think of is that my company only has Professional version of IntegrationHub. According to ServiceNow documentation, Dynamic Actions require Enterprise version of IntegrationHub. What's not clear is whether that applies to using Dynamic actions that already exist in spoke we bought (e.g., Jira Spoke) or whether that only exists if I wanted to create a new one myself (which I'm not wanting to do). Thanks for any feedback on this.

Labels:
Preview file
26 KB
Preview file
180 KB
Preview file
156 KB
Preview file
18 KB
0 Helpfuls
  • 2,109 Views
3 REPLIES 3

Brendan N1
Tera Contributor

‎06-23-2022 03:42 PM

Hey Todd - the input it expects is the Issue ID, not the Issue Key. It's a unique numerical value that Jira creates for each issue.

If you want to find out what this is you can either check in Jira directly or run one of the "Look Up Records by JQL" actions & use jql query "issuekey=JT01-4168". You should be able to find the ID in the issues output.

Also, you can use the sys_id of your Connection & Credential alias record. In your case, the input would just be: 629ad2bfdb1893005963ff041d961971

Btw If this still doesn't resolve your connectivity issue, I recommend you double-check that your service account has the correct level of access; you might need to grant it the "Administrators" role on the project.

Preview file
216 KB
Preview file
128 KB
0 Helpfuls

Todd O
Tera Guru
In response to Brendan N1

‎06-27-2022 09:11 AM

Hi @Brendan N, thanks for the suggestion. I've tried both the Issue ID and the Issue Key which resulted in same outcome. That is not what is causing a system error when the action "Get Editable Fields" is called. Please note the specific system error I'm receiving is directly related to the Connection Alias. The action has this defined as a string when I added it to my subflow but in their code (see my previous screen shots) it treats it as an object. Thus the reason for all the variations I tried in my original post.

Again, I've tried both the issue key and the issue id and it produces the same resulting system error in the said action from Jira spoke. And, I've tried all the variations listed in my original post for the Connection Alias. Any other suggestions are welcome. Also, I've had an open support case for this and they've not yet found a solution. Hopefully someone has run into this and can offer a suggestion or support gets back to me with a good answer. Thanks.

Todd 

0 Helpfuls

rickburke
Mega Guru

‎06-28-2022 05:07 AM

We were having a similar problem with the exact same error message, but our spoke wasn't working at all.  We were not able to get anything from the spoke.  No matter what we tried, we got several different errors.  This being one of them.  Our issue was solved by creating the API key in the proper place.  Apparently there are 2 different places that API keys can be created.  I don't know 100% the locations, but it appears that there is an API key generation on the site itself which is what we were using and that did not work.  There should be another place to create an API key.  I beleive it is in the project itself.  Once we got that API key, all of our errors went away. Hope this helps you.

0 Helpfuls