Integration Action Should Not Consider Minor Versions

Organization Name (Required - If you are an Oracle Partner, please provide the organization you are logging the idea on behalf of):

Gallup, Inc.

Description (Required):

Today, when using the Integration action to call a scheduled integration, the action uses the full version (e.g. 1.0.30). However, as we know, only one minor version within a major version can be active at any one time. Including the minor version in the call means that anytime you create a new version of the second integration, you must also update the first integration to call the new version.

Example:

Integration A is calling Integration B (version 1.0.30).