Symptoms

Creating a PandD package on one of our environments, fails after the 4.7 upgrade. After looking at the form rules, we noticed that there appears to be a "rogue action" that has been injected into the form. Some of the rules that is supposed to be behind the "Add Attachment" button, has been moved from there, to the "rogue action".
 

Diagnoses

This was an issue with 4.6.9 PandD. The package would get created just fine on the source environment, but when you deploy the package, the rules behind the "Add Attachment" button does not get "refactored" correctly, and results in some rules being left behind the "Add Attachment" button, and the rest of the rules being moved to a "un-configured" action.
 

Resolution

We removed the rules behind the "Add Attachment" button, deleted the "rogue action", and adding the rules back manually. After doing this, all was well.

Additional Information...
The "official workaround" would be to recreate the package on 4.7, and re-deploy the package on the target environment. Seeing as the source (production) is still on 4.6.9, and the target is on 4.7, this was not possible.