What is the best option for correlation in case of Documentum application?
-
Mannual Correlation
-
Scan the script for auto correlation while replaying
-
Define the rules and go for auto correlation while recording the script
-
None of the above
Defining correlation rules before recording ensures LoadRunner automatically identifies and captures dynamic values during the recording process itself. This approach is more efficient than manual correlation or scanning during replay. Documentum applications generate many dynamic values (object IDs, session tokens), so proactive rule definition prevents script failures.
In LoadRunner/performance-testing correlation for Documentum (or similar dynamic web apps), the recommended best practice is proactive: define correlation rules ahead of time so the tool automatically detects and replaces dynamic values (like document IDs or session tokens) as it records the script, rather than fixing values after the fact. Manual correlation is more error-prone and time-consuming; scanning for auto-correlation only while replaying is reactive and can miss values needed at record time. So "define the rules and go for auto correlation while recording" is the best/most efficient approach.