Is there any tooling that will convert Query Rules to a!queryEntity Expression Rules? We are going to upgrade from 18.1 to 19.2 soon and we have a couple hundred Query Rules.
Discussion posts and replies are publicly visible
A migration is not necessary as Appian will support existing Query Rules for the time being. Just do not create new ones. It is a good idea to migrate existing ones as you enhance your applications.
"For the time being...." That is the question. When does deprecated turn into removed? We don't want to hit a hard stop of functionality support.
Wouldn't be hard for appian to build a migration tool. Unfortunately, there is no run time tooling available to create appian design objects like expression rules.
In my experience, started 2010, Appian supports stuff for a very long time. You can execute processes using the old forms designer which was deprecated about 4 years ago. Any removals will be listed in the release notes. So I think you are pretty save here.
There is no automated functionality, but I suggest that you go around creating new Query Entity expression rules for every Data Store Entity that you currently query on using Query Rules, and start with the heaviest-used Query Rules and replace them manually. As Stefan already said, we most likely have a very long lead time before Query Rules are removed outright, as many legacy systems (one of mine included) have hundreds of query rules in use which will require manual changeover. If they ever do remove the functionality, I hope and expect that they'll give us a very long warning period beforehand (at least a year).
I would not worry about your Query Rules being unusable, as Appian support will provide ample notice before any removals happen. Notice for example that the application portal is still supported even though it is recommended to use Tempo / Sites: https://docs.appian.com/suite/help/latest/portal-support-notice.html
I would focus your efforts for conversion on rules that would have a performance impact. Since a!queryEntity() allows you to query a subset of columns and has more options for filtering / paging, you can often see performance improvements from using Querey Entity with a more focused query. However, a full conversion of all query rules to a!queryEntity() is probably not necessary.