This is the only change you need to make. The rest must be identical to the incident configuration. In general, you need 3 things for this setup to work. 1) An `onChange` client script in the table for which you want to make assignments. You must make sure to modify the field that corresponds to the onChange client script. 2) An assignment rule for your new table. This mapping rule must be the same as the one used for the incident. 3) A mapping search record that tells the mapping rule which category, subcategory, and CI to trigger the assignment. I just found (and fixed) a problem with this feature that only occurs in Internet Explorer.

If you have already configured assignment rules using the above article or its update set, you must update all AJAX assignment client scripts in your instances with the new code in the « AJAX Assignment Client Script » section above. Assignment rules return only one user and one group. If you want to fill in other information, you must define it with a separate client script or template. 2- Do SN/you have a better suggestion in such cases (lots of mapping rules) and how to deal with them easily?! Based on this list, it appears that the actual mapping rule for the change request table is missing. In some circumstances, business rules take precedence over assignment rules. Thank you for your reply. Unfortunately, I haven`t seen your comment so far and I`m sorry I was late. Their solution is wonderful, but I`ve made several customizations to the client instance that make it difficult to use.

This client has more than 1500 choices for category/subcategory/activity/problem and had to filter the CI database by the combined selection of these ITAs. As a result, we had to design a separate incident classification table that filters the list of available CIs based on Cat/Subcat options. This means that we are not pointing to sys_choices table on the incident table and instead looking at this incident classification table. How do you think I can use assignment rules and create them with this complexity? Thank you in advance for your time. My problem is that this script is not called by the client scripts « AJAX Assignment (…)  » that I created on the sc_task form. The only change I make to this script is to change the name in the table from to //Construct the URL to ask the server to assign var url = « xmlhttp.do?sysparm_processor=AJAXAssignment&sys_target=incident »; to var url = « xmlhttp.do?sysparm_processor=AJAXAssignment&sys_target=sc_task »; 5. Assign your mapping rule to a selected user or group. This changes the value of the fields assigned_to and assignment_group in the specified record. 8.

We want the mapping rule to be triggered when the Category field is set to « Request/Help » AND if the Subcategory field is set to « Email ». It depends entirely on your specific configuration. Typically, requests and requirement elements are not assigned to groups at all. It is the tasks under these elements that are affected. If for some reason you are making direct request assignments, you don`t need a solution like the one I`ve described here. You probably only need a standard assignment rule script that retrieves the location of the person requested_for and then queries the group at that location. Groups do not have out-of-the-box locations by default, so the script depends entirely on your system configuration. Ultimately, your mapping rule script should define the assignment group as follows. 7. Navigate to the specified table for which you defined your mapping rule. In this example, we set our assignment rule to the incident table to Incident > All. This module appears on the System Policy Enforcement menu.

It allows you to automatically assign tasks to a specific user or group by selecting the fields assigned_to or assignment_group be used, depending on the specified conditions. You can easily define these mapping rules for the desired table. This module appears on the System Policy Enforcement menu. This table is essentially generated immediately because its definition is provided in the instance`s Data Search Definition table, especially for field assignments in the incident table. Mapping search rules primarily allow you to change any field value, not just assignment fields. I implemented ™the assignment search for the incident. It works very well! Thank you. The first step in applying this customization is to create a mapping lookup table that can store all the different combinations of values used to determine the mappings. The update set contains this table for you (which can be managed via the `System Policy -> Assignment Search` module).

The security configuration for this table is also included, but is not documented in this article. This is a great feature and it would help a lot.

Catégories :