Best practice for collecting ad-hoc Demand details without creating custom fields?

[rleandro]

Hi everyone,

I am looking for architectural advice regarding Demand Management.

We need a way to collect additional, varying technical information during the Demand creation phase. However, we want to avoid custom field inflation (adding dozens of new columns to the dmn_demand table).

What are the best alternatives or native features to handle this? I am considering options like:

How have you solved this in your instances?
What are the pros/cons of the different approaches?

Thanks in advance!

[Brad Bowman]

The HTML fields in the Business Case section are meant to house whatever data helps assess or qualify the demand.  You should only create custom fields in cases where you need to capture specific data separately on all/most demands for the purpose of reporting on that data or using it to automate decisions/steps, or data that will feed into the possible resulting project record.

[Tanushree Maiti]

Hi @rleandro 

If you do not want to customize ( create fields for your requirement) then select any of the OOB HTML field which you think  for your project generally that is not used. Like Enablers or In scope etc. 

If all the OOB field is used , according to me, last option would be keep the details in Description field.

[jameswoodfo]

Hello, @rleandro,

I want to echo what already been said. Start with the baseline HTML fields. I you are using a record producer to create demands you could even combine multiple intake questions into something like business justification.

Here's another option: use multiple intake form to create demands. For those fields that don't have an existing representation in the baseline dictionary for demands, use a variable editor to show the questions that were asked.