When the above conditions are met, the Publish Control Template dialog will list the candidate rules (see next screenshot) allowing you to select the ones you want to publish with the control. Note that as soon as at least one rule is selected the read-only checkbox will also be selected: you can only publish controls with rules in read-only mode. Since it is not possible to edit rules after the control is published, this restriction exists to make sure that no changes that could break the rules will be allowed when using the template.
If you mark a custom group control read-only=true, then when it is used from the Custom Area and dropped back onto any form, it will not be editable. This means that you cannot delete or rename controls from within a read-only group. You can only delete the entire read-only group, and change the styling, validation, etc.. properties.
Custom group controls marked read-only=false can be edited completely. You can drag other controls into the group and delete any one or more controls from within the group.
Any rules used by a custom group controls can be carried along with the custom group. The wizard will show you all the rules used by the group and will allow you to pick and choose among them. As soon as you choose one or more rules, the group is automatically marked as read-only=true. This is because editing the name of one of the controls in the group could break the rule.
Rules carried along into a custom group control are not visible when dropped into another form. This is because they are not editable. The only rules that can be carried into a custom group control are those that entirely reference controls within the group. If a rule references controls both within and outside the group they cannot be included in the custom group since they would not be functional. The custom group wizard will exclude such rules automatically.
Custom groups with rules included when dropped back onto the same or another form, will contain a special "Prefix" property. The property will automatically be given a unique value if you drop the group onto the same form 2 or more times. This ensures that the group controls have unique element name. You can view the impact the prefix has on the element names by viewing the form's schema.
Custom Section groups will include the prefix on the parent XML element only. This is enough to make all the child XML elements and the parent (the section itself) unique. Panels, Tabs & Repeats are not created in the schema as Complex Types. Thus all the top level controls inside these custom group types will be named with the prefix. Any Sections within these types will, as a top level control itself, have the prefix. But all it's child elements will not have the prefix since it's again not required to make them unique.
You can edit the "Prefix" property but frevvo will not allow you to make it non-unique.
Adding/Removing Templates to/from the Custom Panel