Because different users have different permissions and access to different fields and constructs and workflow.
Creating one page for all users would be a security violation as users could then see things in the html/javascript that they were not supposed to know about -- even if logic was there to prevent it from running. So, for each unique permission set, you need a unique js page to make sure that you are properly maintaining and managing the security of your system. There is not ONE js page per form/view, there are several. So, yes, there is something that people are missing when thinking about issues in this area. It is more complex to do the right thing in a flexible manner than it at first might seem. Doug Mueller -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of John Baker Sent: Tuesday, January 22, 2013 9:50 AM To: [email protected] Subject: [Info] Midtier Preload: 7604 SP4 Ravi Yes, I'm aware of the difference between the browser and Mid Tier cache, but the Mid Tier element does not seem useful after the Javascript has been created. The problem is Mid Tier is caching arapi objects, not Javascript. Once the JS is available in a Mid Tier cache, the majority of workflow isn't needed again and could be cleverly cached if it was. Tell me: why does Mid Tier need to load a form and all the styling/layout/etc if it was previously loaded and a JS file created? Perhaps I'm missing something. John _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
