Ability for P&D to handle merging better during package deployment
If or when two solutions share a common artifact i.e. View, with rule(s) configured at the Form level. When deploying the two solutions to the same target environment, whichever of the two packages get deployed last will maintain the Form level rule configuration.
This is a known issue with P&D in the area of extended rule merging (where the rule is added onto an existing view event from the form context) when the relevant SmartForms artifacts is shared between artifacts for instance, as described in more detail on http://jhbtfs:8080/tfs/labs/WorkItemTracking/WorkItem.aspx?artifactMoniker=862760