Turn 'Pre-render' option on for UX Components
Bulk operation that enables 'Pre-render' option for all UX Components in the workspace.
If you have a large number of UX components and you want to turn on the 'Pre-render at design-time' option for each UX component, opening each component, setting the property and then saving the component would be tedious. The Turn 'Pre-render' option on for UX Components bulk operation automatically set this property in one or more UX components in a project. The bulk operation enables pre-rendering in the selected UX components.
To perform a Turn 'Pre-render' option on for UX Components bulk operation, open the Web Projects Control Panel and select Bulk Operations > Turn 'Pre-render' option on for UX Components... from the Edit menu:
In the Bulk Convert UX to Pre-render dialog, optionally check Apply security and server-side show/hide expressions client-side. Enabling this option may make your component less secure. See About Applying Security and Server-side Show/Hide Expressions on the Client below.
Click OK to continue.You can choose to enable or disable Apply security and server-side show/hide expressions client-side in the next step.It is important to understand the difference between applying security and sever-side show/hide expressions server-side and client-side.
Select the UX Components to enable pre-rendering. Optionally enable or disable Apply security and server-side show/hide expressions client-side using the checkbox at the bottom of the dialog.
Click OK to apply the bulk operation.
Alpha Anywhere may prompt you to adjust other settings in a UX Component when pre-render is enabled, such as change the error reporting style. You may optionally change the setting described in the prompt when the dialog is shown. Click OK to continue with the bulk operation.You may see other prompts not shown here.
A notice will be shown when the bulk operation completes. Click OK to close the notice.
When applied server-side, the controls that should not be visible to the user are physically removed from the HTML that is sent to the client.
On the other hand, when applied client-side, the computation about which controls should be hidden is still done server-side, but the controls that should be hidden are still physically in the HTML and are hidden when the component is rendered. Therefore, client-side option is less secure because a user might view the source on the page and see the data for the controls that have been hidden.