New commit detected on ManageIQ/manageiq/euwe:
https://github.com/ManageIQ/manageiq/commit/166c703906fed68236023d53f702b431e4a1ef8b

commit 166c703906fed68236023d53f702b431e4a1ef8b
Author:     Greg McCullough <gmccullo@redhat.com>
AuthorDate: Mon Nov 28 14:12:23 2016 -0500
Commit:     Satoe Imaishi <simaishi@redhat.com>
CommitDate: Mon Jan 9 09:48:05 2017 -0500

    Merge pull request #11669 from mkanoor/bugzilla_1378606
    
    Support provider name & template name to uniquely identify a template
    (cherry picked from commit 76c643b434e10061a7d5e93db62f3eff17ecfacf)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1411359

 .../Job.class/__methods__/launch_ansible_job.rb    | 22 ++++++++++++---
 .../method_validation/launch_ansible_job_spec.rb   | 33 +++++++++++++++++++++-
 2 files changed, 50 insertions(+), 5 deletions(-)

Hi Pavol,
You would create a dialog drop down list with the name 'ansible_provider_name', this drop down would list all the known ansible tower providers in CFME. The user would pick one of the providers and then based on that the user would make a selection of the job template to use.

To test this you would need at least 2 ansible providers with the same named job templates. So that we can pick the correct one based on user selection.

Thanks,
Madhu

Not sure about the name convention, I will check with Brandon. But in your case you should be using a drop down list and not have to type in the name of the provider.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2017-0320.html