TAKE of GET? PUT or SET? The BRM Memory Management Conundrum

GET or TAKE? SET or PUT? Which one should I use?

That decision comes down to how you want to manage memory in Oracle BRM.

Why would I want to use TAKE?

Let’s say you have an flist, and you want to edit data on a field. TAKE is perfect for you because it allows you to pull a field off of an flist, edit it, and use PUT to add it back on the flist. I highly recommended using TAKE and PUT together because you don’t have to free the memory.

You get the memory from the flist using TAKE, then give it back using PUT. But wait! If you use TAKE, watch out for these pitfalls.

Articles & Resources

To access this premium content, please fill out the form to receive an email with the access token.

* required fields


DocuSign® is changing how business gets done by empowering more than 250,000 companies and 100 million users in 188 countries to sign, send and manage documents anytime, anywhere, on any device, with confidence. Organizations of all sizes and industries are accelerating contracts, approvals and workflows with DocuSign’s Digital Transaction Management (DTM) platform and eSignature solution. DocuSign keeps life and business moving forward.