14Page Composer Personalizations supported for migration
There are certain Page Composer personalizations that you can migrate. These properties are supported in Visual Builder Studio: Rendered, Visible, Read Only, Disabled, Required, and Editable. Properties not relevant in the Redwood user experience will be ignored.
| Personalization | Parameter | Migrate | Comments |
|---|---|---|---|
| Fields | Rendered | Yes | rendered=false is equal to hidden=true in VBS |
| Visible | Yes | visible=false is equal to hidden=true in VBS | |
| Read Only | Yes | ||
| Disabled | Yes | disabled=true is equal to readOnly=true in VBS | |
| Required | Yes | ||
| Editable | Yes | editable=false is equal to readOnly=true in VBS | |
| Regions | Yes | ||
| Flexfields | Yes | ||
| Country | Yes | EL expressions with country condition aren't migrated. Only country level personalizations are migrated. | |
| EL expression | Role | Yes | Only personalizations using the EL expression
#{securityContext.userInRole['role']} are migrated. Personalizations using the EL expression #{securityContext.userInAllRoles['roleList']}aren't migrated. |
| ADF page binding | Yes |
EL expressions based on ADF page bindings are migrated, for example: #{row.bindings.CountryOfBirth.inputValue != 'AL'} #{row.bindings.AttachmentId.inputValue == '12345' && row.bindings.AttachmentCreatedBy.inputValue =='admin_user'} #{row.bindings.CountryName.inputValue == 'US' || row.bindings.AddressType.inputValue == 'HOME'} |
|
| Other Conditions | Yes |
Ternary conditions, for example, #{securityContext.userInRole['MY_HR_ROLE']} ? true : false #{1==1}, #{2==2} #{true}, #{false} |