What is the Difference and link between `sc_item_option_mtom` table and the `sc_task` table

[Harrys09]

Hi , I had a few questions please:

1. what is the Difference and the key link between `sc_item_option_mtom` table and the `sc_task` table?

2. On which table is the state value for a particular catalog task variable stored and in flow designer if I created a look up action where I want to look up the variable name and the state which table do I look up?

3.what is the difference `sc_item_option_mtom` table and the sc_item_variables_task table?

thank you

[Punit S]

Hello Harry, 

Happy to help with your question . 

1. Difference and Key Link betweensc_item_option_mtom and sc_task  tables:

   • sc_item_option_mtom: This table is used to store the relationships between catalog items (sc_cat_item) and their associated options (sc_item_option). It acts as a many-to-many relationship table, as indicated by the "mtom" in its name. Each record in this table represents a specific option selected for a particular catalog item by a user during the request process.
   • sc_task: This table is used to store individual tasks or activities that are generated from the fulfillment of catalog items. Each catalog request typically generates one or more tasks, representing the various activities required to fulfill the request. The sc_task table holds information about the tasks, including their state, assignment, priority, etc.
   • Key Link: The key link between these tables is that when a user requests a catalog item, the selected options from the sc_item_option_mtom table can impact the fulfillment process, which generates tasks stored in the sc_task table. The selected options influence the tasks that are created, assigned, and managed throughout the fulfillment process.

2. State Value for Catalog Task Variable and Look-Up in Flow Designer:

   • The state value for a particular catalog task variable is typically stored in the sc_item_option_mtom table. The state of a variable indicates its current status or value within the context of a catalog item request.
   • If you've created a look-up action in Flow Designer to retrieve the variable name and state, you would l

3. Difference between sc_item_option_mtom and sc_item_variables_task tables:

   • sc_item_option_mtom: This table manages the relationships between catalog items and their options. It stores the selected options for a catalog item in a many-to-many relationship, enabling the dynamic configuration of a catalog item based on user choices.
   • sc_item_variables_task: This table stores the values of variables associated with catalog tasks. When a catalog item generates tasks for fulfillment, these tasks might have associated variables that need values. This table stores those variable values at the task level.
   • Difference: While both tables store information related to catalog items and their variables, they serve different purposes. The  sc_item_option_mtom table focuses on storing user-selected options, whereas the sc_item_variables_task table focuses on storing the values of variables associated with tasks generated from catalog item fulfillment.

Please mark my answer a solution accepted/helpful in case it adds value and moves you a step closer to your desired ServiceNow solution goal.

Thanks,
Punit

[Harrys09]

Thank you so much for your reply and help! @Punit S very helpful.

just to confirm then the state of a particular catalog task E.g. (if task open/ closed complete E.t.c) is stored on the sc_item_option_mtom?