Changes

Benefits of a Shadow Application

275 bytes added, 20:39, 13 January 2010
no edit summary
* Providing the same [[UTA]] in a different language. In this scenario the labels of the standard fields in the shadow [[Application|application]] would be added in the alternative language. Alternative language versions of each [[Custom Field|custom field]] would be created, and each field mapped to the original [[Custom Field|custom field]].
* Providing simplified Access to an existing [[UTA]]. In this scenario, limited standard fields would be selected (though the parent [[Application|application]] may include all standard fields), [[Custom Field|custom fields]] are restricted by [[Role|role]], and the list views of the [[Application|application]] can be controlled separately to the original [[Application|application]].
* You can control how many levels from the parent application you wish to use.
* You can control which [[Templates]] (Level 1) or [[Types]] (Level 2 '''only''') are available in the Shadow Application.
: '''Note:''' if you enable Level 3 in the Shadow Application all Level 3 '''Types''' defined in the parent [[UTA]] will automatically be available.
You can control how many levels from the parent application you wish to use.
Each Shadow [[Application|application]] has its own security matrix so you can control access within each [[Application|application]] separately.
0
edits