This analyzer helps solve problems with OmniScripts that would need to be activated after an OmniScript it has embedded is deployed.
What triggers this problem analyzer?
If you try and deploy an OmniScript that is reused in other OmniScripts, the analyzer will also suggest including that dependency in your deployment package.
For the component that you are trying to deploy, Gearset will have detected which OmniScripts depend on it and highlighted them. Within Gearset's UI the following problem analyzer message will be presented, along with a list of the components that the analyzer suggests you include in your deployment. Checking the boxes will include the suggested components in your deployment package.
In this example where the Contract_Signature_English OmniScript is being deployed, Gearset has detected that the OmniScript named Contract_New_English has changed and that should be included to make this deployment succeed.
What problem is it solving?
If you don't include these changed dependencies, your deployment may cause unexpected behavior in your target environment due to dependent OmniScript not being up-to-date or activated.
How does it work?
Gearset will automatically add the OmniScript components that are reusing the changed OmniScript to your deployment package.