Mandatory skill property

Joshua Chen MTL
Mega Sage

Hi team,

Can someone explain to me the pros/cons of enabling the mandatory skills property in FSM? 

I understand if i have a combination of mandatory skills + optional skills, it makes sense to turn on this property (see link Configuring the mandatory skills featur)

  • if all my skills are considered "mandatory", and  i set the global domain setting "Auto-selection of agents for tasks requires them to have skil" = all... do i even need the the mandatory skills property?

    JoshuaChenFX_0-1755043041383.png

can i use the task skill embedded list field to add skills level on the WOT, if the mandatory skill property is not turned on?

JoshuaChenFX_2-1755043236249.png

 

 

.
Add me on LinkedIn 🙂 https://www.linkedin.com/in/joshuachen0510/
1 ACCEPTED SOLUTION

Hi Sandeep, 

Documentation says that the property has to be turned on to indicate that  the task skill (embedded list) is being used. Does it mean that if property is not activated, FSM will not consider the task skill and only look at the skills field?

Have you made it work without the property activated (the task skill)? 

JoshuaChenFX_2-1755088956660.png


EDIT: I contacted a SN Senior BPC (works at ServiceNow) specialized in FSM, and he recommended that we always use the task skill + turn on this property. 

 

.
Add me on LinkedIn 🙂 https://www.linkedin.com/in/joshuachen0510/

View solution in original post

5 REPLIES 5

Kelly Logan
Kilo Sage

Has anyone configured Mandatory Skills as described in the documentation? Because there are appear to be several gaps from what I see, namely:

  1. What does the direction "Configure the Work Order form and the Work Order Task form to use the Task Skills [task_m2m_skill] table" mean, precisely? These are two fundamentally different table types with different data. One is a listing of unique values that can be used as a lookup to set string values to match against, while the "Task skill" table is a many-to-many that will likely have multiple entries for each skill type and will return a sys_id rather than a text value. Also, rather than making a choice of text values to populate an array (list field type), entries will need to be generated in the m2m table that are tied to the current WOT sys_id. Does workflow need to be added to do this? Documentation doesn't say. 
  2. It is claimed that the "Manage skills" must also be used or the Dispatch Workplace filters will not work correctly, but this table uses entirely different data than the m2m table which is pointed at the regular Skill [cmn_skill] table. So to do this we will have to double enter every skill name by hand (because who knows where the Manage skill data is) and just hope for no typos? 
  3. Even after setting the system property work.management.use.mandatory.skills to true and adding a task_m2m_skill entry for my work order task, filters are still not set with with skills defined. 

Can someone please explain how this is supposed to work? Note that there are probably answers in the Dynamic Scheduling configuration criterion like "Matching Mandatory Skills For Dynamic Scheduling", but I would prefer to not have to dig through script includes and reverse engineer the directions that should have been just stated in the documentation.