"On the development system, create a product rule that defines the application package that will be moved through repositories in the pipeline."
I understand that is asking me to create a Product rule that is based on the Application definition, but I don't quite understand why. It seems odd to me that we'd create a single product rule to use for moving all subsequent changes through the pipeline. What if we want to only send the items that changed in the code that was merged? While you could use a Product rule built based on the Application, that seems like it would be overkill if you only need to send the 20-30 rules you changed in your branch.
Can anyone elaborate on the meaning of this sentence in the help? There is no additional explanation given, or an example of how it would be done.
If you don't want to create the Product rule and mention in the application details stage then you can configure the pipeline as branch based deployment (Check merge policy as yes and select highest RSV) and trigger the merge from the development environment.
With this approach you can make changes to the previous rules which were already merged and you can trigger the merge again from the development server without creating any product rule for the pipeline.