Hi All,
Back in June, I completely missed when the current Release (3670-4684 13-Jun-2016) came out that there was this new feature,
But now we tripped over it we have found some of the larger UX are sooooo much faster now it is amazing... the inability of using security is a real bugger but for many UXs this is amazing performance boost that we are aplyying it to every UX we can...
But... (there is always a but)
We are finding it can do some funny things from time to time most of which we have not been able to completely put our finger on. But have had cases of UX going south and the only recourse is to restore from a backup and start again. Un-checking the option seemed to make it worse.
So I am wondering who has used this feature and what as your experiences been?
Here are the release notes
Back in June, I completely missed when the current Release (3670-4684 13-Jun-2016) came out that there was this new feature,
But now we tripped over it we have found some of the larger UX are sooooo much faster now it is amazing... the inability of using security is a real bugger but for many UXs this is amazing performance boost that we are aplyying it to every UX we can...
But... (there is always a but)
We are finding it can do some funny things from time to time most of which we have not been able to completely put our finger on. But have had cases of UX going south and the only recourse is to restore from a backup and start again. Un-checking the option seemed to make it worse.
So I am wondering who has used this feature and what as your experiences been?
Here are the release notes
A new option in the UX allows you to pre-render the component layout at design-time, thus speeding up the load time for the component at run-time.
NOTE: Not all use cases are appropriate candidates for this option. In particular, if you have controls on your UX that are shown/hidden based on a user's security group, or based on session variables, then you should not use this option. The reason is that at design-time when the component is rendered, it is not know what the value of the session variables or group assignments are.
TIP: You can easily check if a component uses security and/or server-side show hide expressions by click the Menu button and then selecting the 'Security and server-side show/hide settings in component...' menu choice.
To turn on this optimization feature go to the Properties pane in the UX builder and check the 'Pre-render component at design-time' property.
When you check this property you will see two additional properties:
When to compute pre-rendered component - Options are 'Every time component is saved' and 'Prompt when component is saved'. In a large component, computing the pre-rendered component will take a noticeable amount of time and you might not want to compute the pre-rendered component every time the component is saved. If you select the 'Prompt at run-time' option, be sure to re-compute the layout the last time you save the component before exiting the UX builder.
Allow style to be changed at run-time - You will get the most optimization if you do not allow the component style to be changed at run-time. For example consider a situation where you have a parent UX or Grid that opens a child UX. Assume that the parent component uses a style of MobBlue. If the child UX (the component that you are setting to pre-render at design-time) also uses MobBlue, then you can leave this property unchecked. However, if the child UX uses (say) MobRed, then you will need to check this option (and you will not get the maximum amount of optimization).
NOTE: Not all use cases are appropriate candidates for this option. In particular, if you have controls on your UX that are shown/hidden based on a user's security group, or based on session variables, then you should not use this option. The reason is that at design-time when the component is rendered, it is not know what the value of the session variables or group assignments are.
TIP: You can easily check if a component uses security and/or server-side show hide expressions by click the Menu button and then selecting the 'Security and server-side show/hide settings in component...' menu choice.
To turn on this optimization feature go to the Properties pane in the UX builder and check the 'Pre-render component at design-time' property.
When you check this property you will see two additional properties:
When to compute pre-rendered component - Options are 'Every time component is saved' and 'Prompt when component is saved'. In a large component, computing the pre-rendered component will take a noticeable amount of time and you might not want to compute the pre-rendered component every time the component is saved. If you select the 'Prompt at run-time' option, be sure to re-compute the layout the last time you save the component before exiting the UX builder.
Allow style to be changed at run-time - You will get the most optimization if you do not allow the component style to be changed at run-time. For example consider a situation where you have a parent UX or Grid that opens a child UX. Assume that the parent component uses a style of MobBlue. If the child UX (the component that you are setting to pre-render at design-time) also uses MobBlue, then you can leave this property unchecked. However, if the child UX uses (say) MobRed, then you will need to check this option (and you will not get the maximum amount of optimization).
Comment