What’s New?

Dynamic Runset execution using JSON format

User can define virtual Run Set and select which Business Flows to be executed and with what input values in JSON based configuration and Ginger will create the Run Set automatically on runtime and execute it
User can define existing Run set with customization of input values, Applications Agents mapping, Runner level Environments, Business Flows activation and more in JSON based configuration and Ginger will load the existing Run set, will modify (without save) and execute it.

SOAP & Rest Webservice Actions conversion to API Model – Automatic conversion and mapping of SOAP and Rest web services actions to API Models
Java Legacy actions conversion to Page Object Model Actions – Automatic conversion and mapping of Java legacy actions to Page object models

Support adding activities or modifying activity sequence on Activities Group from Shared repository
Modify Activities Groups and publish the changes from Shared repository to selected instance of this group

Business flow pass rate field added in the email report body
Option to customize execution or pass rate calculation level (i.e. Activity or Action) from report template
Auto-Pilot Model edit from Automate tab Model API Action to speed up development
New “TDM” Terminology type added to support terminology for the eTDM application
“Publish” flag added for all solution items like Business flow, Runset, to allow filtering only relevant items from other applications like eTDM, Ginger Business Operations Portal, etc.
User can now control the logging level from CLI configuration using the “VerboseLevel” attribute

Actions loading mechanism improved to do lazy load to improve the Business flow load time and overall solution load time
Variables marked with “Output” and “Publish” flags are printed in console when executing via CLI
Debug logs are now filtered out by default to make logs more readable when running from CLI or Jenkins
Chrome browser Selenium driver was updated to the latest (required version 80+)