Hi everyone,
The input field is deactivated in the AQL condition
I want to perform in a Automation an AQL condition on a specific object. However, in the AQL condition the input field is deactivated. I implement this condition in Global Automation and have the required permissions
Hi!
Unfortunately this is a known bug which arises when you have a Branch on AQL step somewhere in your rule:
The bug is tracked here:
https://jira.atlassian.com/browse/JSDCLOUD-13635
Temporarily removing the Branch step will fix it, adding it again after is then of course possible.
Jeroen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you share the entire automation configuration?
Jeroen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Negjat,
Can you try with issue field tab.
I hope that's help.
Umut
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.