Lightweight lists should not be used if the rule using the list performs operations unsupported by lightweight lists. These features are not supported in PRPC 7.1:
Forward chaining - declarative rules will not fire automatically as the result of changes to properties on a lightweight list.
Reference properties (a property that can link to a source property) - references cannot be established from or to properties on a lightweight list.
Java objects - lightweight lists cannot contain Java pages (a clipboard page with a class derived from the Embed-Java- base class) or Java properties.
Messaging - a lightweight list cannot handle a message, a text clipboard value generated by the system and associated with a page. A message can convey error conditions, progress, or exceptions to a user.
Value vetting - for example, lightweight lists cannot apply the rule-edit-validate rule, which validates type conversion, precision, and encryption.
Page properties as part of Obj-Browse selects - for example, during an Obj-Browse over Data-Admin-Operator-ID, you can select .pyPreferences.pyGeneralPrefs.pyWorkPortal but not .pyPreferences.pyGeneralPrefs, because pyGeneralPrefs is a page property reference.
Single frame issues - if you are using the getPage or get Property function in a Java step while trying to use that reference across iterations, the step may point to an incorrect entry in the list.
Yes, we have gone through this articles before using, we are just getting few properties from an object and copying them into data pages ( we didn't use a lookup to avoid huge date on data pages ), didn't expect too much performance increase with this step. so we removed in all the place.