I am looking to log the names of the sections invoked by a given requestor. I understand tracer gives me the options to look at the streams being rendered at run time. However , in an end user mode tracer will not be running. The application/framework should be in a position to keep recording the sections that are being invoked as part of a given requestor session and then log it in to a DB table for producing some reports.
For example , as an end user I invoked 5 sections - Personal Info , Education , Experience , Certification , Demographics. Now while I am invoking those sections ( may be as part of a flow action , a wrapper section , hide/show sections) as i work on a case , the intended solution should capture the names of the sections rendered and persist them in a DB table. By the end of that requestor session , system can pull out a report that this requestor invoked the following sections.
( Similar to right click and view source). I then parse that variable to pull out the section names and then write it to a file , that I create with the ID of the user who was the requestor. I also write the date time stamp in that same file so that I know when did that user invoke a given section.
I would be extremely nervous about a piece of JS in userworkform which runs every 5 seconds. I have seen quite a few impossible-to-reproduce issues involving mysterious Browser hangs or crashes that have come from precisely this type of code in userworkform. It's not clear to me why you want this information, but I think it would be much safer if you just added a button to the portal which ran the above script precisely once, on demand.
Thank you for your suggestion. You bring up a very valid point. I am going to monitor the bhavior of the above implementation and will update with the results as I get them.We can look at the stats then and discuss if this is a go or a no go.