Adding more than item in Configuration Item in an SCTASK

[arturomacias]

I am trying to add multiple items under an SCTASK in the configuration item, but I cannot. It only allows me to choose one. If I try to make a list, it causes an error.

[Juhi Poddar]

Hello @arturomacias 

• Configure the dictionary of configuration item field.
• Select List type and save.

Result:

Hope this helps!

"If you found my answer helpful, please like and mark it as an "accepted solution". It helps future readers to locate the solution easily and supports the community!"

Thank You
Juhi Poddar

[AshishKM]

Hi @arturomacias , 

Please ensure that you actually need to this CI field type change from reference to list controller, because its @TASK table level and once you change it, it will reflect every where, which you dont need ( or want )  that, and that is the reason it's not allowing you to change it becuase there are existing records with single reference value.

-Thanks,

AshishKM

[Ankur Bawiskar]

@arturomacias 

OOB the CI field is reference type.

Why do you wish to make it select multiple CIs?

What's your business requirement?

Here are some details about the use of that field

The Configuration Item (CI) field on a Service Catalog Task (sc_task) in ServiceNow is used to specify the particular configuration item that the task is related to. Here are some key uses of this field:

1. Tracking and Management:

• It helps in tracking which specific CI (e.g., hardware, software, network component) is associated with the task. This is crucial for managing and maintaining the IT infrastructure.

1. Impact Analysis:

• By linking tasks to CIs, you can perform impact analysis to understand how changes or issues with a particular CI might affect other services or components.

1. Reporting and Metrics:

• It allows for better reporting and metrics. You can generate reports to see how many tasks are associated with specific CIs, which can help in identifying problematic areas or frequently failing components.

1. Automation and Workflows:

• The CI field can be used in workflows and automation scripts to trigger specific actions based on the CI. For example, different approval processes or notifications can be set up depending on the CI involved.

1. Historical Data:

• It provides historical data on the tasks performed on a particular CI, which can be useful for audits and compliance purposes.

In summary, the CI field on sc_task enhances the ability to manage, track, and analyze tasks in relation to the specific configuration items they affect

If my response helped please mark it correct and close the thread so that it benefits future readers.