Which statement best describes when to use static data vs dynamic data in CLM?

Which statement best describes when to use static data vs dynamic data in CLM?

• A. Dynamic data updates through workflows and events; static data remains constant metadata
• B. Static data remains constant metadata; dynamic data updates through workflows and events; use fields accordingly
• C. Static data updates automatically; dynamic data requires manual input
• D. Both types updated only on initial creation and never change

Answer: (B)

In CLM, you separate information that defines the contract from information that changes as the contract moves through its lifecycle. Static data is constant metadata—the parts that describe the record and don’t need to be altered by the workflow. Dynamic data is updated through workflows and events as actions are taken, approvals occur, and dates or statuses evolve. Because of that, you should use fields accordingly: designate fields that describe the contract (like template, parties, contract type) as static so they stay the same, and designate fields that reflect progress or process who approved it, current status, renewal or expiration dates, and similar evolving values as dynamic so the system can update them automatically or through tasks. That’s why the statement describing static data as constant metadata, dynamic data as updates via workflows and events, with guidance to use fields appropriately, is the best fit. The other options either invert the behavior or imply no changes occur after creation, which doesn’t align with how CLM handles lifecycle data.

In CLM, you separate information that defines the contract from information that changes as the contract moves through its lifecycle. Static data is constant metadata—the parts that describe the record and don’t need to be altered by the workflow. Dynamic data is updated through workflows and events as actions are taken, approvals occur, and dates or statuses evolve.

Because of that, you should use fields accordingly: designate fields that describe the contract (like template, parties, contract type) as static so they stay the same, and designate fields that reflect progress or process who approved it, current status, renewal or expiration dates, and similar evolving values as dynamic so the system can update them automatically or through tasks.

That’s why the statement describing static data as constant metadata, dynamic data as updates via workflows and events, with guidance to use fields appropriately, is the best fit. The other options either invert the behavior or imply no changes occur after creation, which doesn’t align with how CLM handles lifecycle data.