Protected mApp™ Solution FAQs
Frequently Asked Questions (FAQs) about Protected mApp Solutions to help you quickly understand how to get the most from this feature.
For help on how a Protected mApp Solution differs from any other mApp Solution, see: Upgradable mApp Solutions.
- Why should I protect content by using a Protected mApp Solution?
Content protection gives you the ability to lock down your mApp Solution and control customizations to ensure smooth upgrades in the future.
Content Protection is optional but brings benefits. For example, you can create a Protected mApp Solution on your development system and protect it. This allows you to install it on your test and production systems secure in the fact that no-one can make changes to the Protected mApp Solution.
- Can any mApp Solution be protected or just CherwellmApp Solutions?
Protecting a mApp Solution and making it potentially upgradable is part of the mApp Solution authoring process so anyone can do it. You just select a checkbox when you are creating the mApp Solution.
- Are all properties of a field protected or can you protect individual properties?
Some field properties can be changed. For example, the display name of a field can be changed to suit your requirements and the length of the field can be extended. New indexes can also be added to field properties.
- If a form is protected, can I change the form name?
No, the form name cannot be changed. This also applies to Business Object names.
- How does merging work? For example, what happens to existing fields that are changed?
If field A (from the Protected mApp Solution) is merged with field B (in the target system), this results in fields A and B in your system after the merge.
If field A (from the Protected mApp Solution) is merged with an identical field A (in the target system) from a previous mApp Solution, this results in an upgraded field A with the protected properties from the mApp Solution and the customized properties from the target system.
If field A (from the Protected mApp Solution) and field B (in the target system) have the same field name, the field in your target system will be renamed with an underscore (_) prefix.
Automatic renaming of duplicate names with an underscore (_) also applies to Item Managers, forms, relationships and other Business Object Definitions.
- When you refer to protecting fields in existing Business Objects, do you mean new fields or can a Protected mApp Solution protect existing fields?
Both. New fields added by a Protected mApp Solution are critical to that mApp Solution and will be protected. Existing fields that are merged with new content from the Protected mApp Solution will also be protected after the Protected mApp Solution is applied.
- Can we modify relationships after a mApp has been applied?
Yes, you can. If the relationship is protected, you cannot modify that relationship but you can replace the relationship. You can make a copy, make the changes, and replace the relationship. You can add all the new relationships that you need; it is the relationships defined in the Protected mApp Solution that are protected.
- Can I switch on content protection for an existing mApp Solution?
Yes, you can. Open your mApp Solution in the mApp Editor, go to mApp Properties, and select the Protect mApp content on publishing check box. Publish your Protected mApp Solution in a Blueprint and then Apply a mApp Solution to your system.
- How do I remove the content protection after applying a Protected mApp Solution?
Protection cannot be removed from the system itself once installed. However, you can rollback the mApp Solution by publishing a Rollback Blueprint file.