When scripting for Webtop, What all values must be parameterised for Import,Navigation,Export operation?
-
Different Request IDs that are being passed in subsequent requests
-
Object IDs of folders and cabinets
-
Folder names and cabinet names
-
UID
Object IDs uniquely identify folders and cabinets in Documentum and must be parameterized for Import, Navigation, and Export operations to work across different environments or user sessions. Request IDs are transient and handled by correlation, folder/cabinet names are display values not used in API calls, and UID is typically static user identification.
Correct answer: Object IDs of folders and cabinets.
In Documentum Webtop (an ECM/DMS platform) automation scripts, folder and cabinet names can vary between environments (dev/test/prod) or even change over time, but their internal object IDs uniquely and stably identify them regardless of naming. So when scripting Import, Navigation, and Export operations, you parameterize the object IDs rather than hard-coding names — this makes scripts portable and resilient to renames.
Request IDs are session/transaction artifacts, not something you'd parameterize for repository navigation; folder/cabinet names are exactly what you want to avoid depending on; and UID typically refers to a user identifier, not a navigation/object reference in this context.