Community in read only mode June 18 & 19
This community will be set in READ ONLY mode for a while on Tuesday June 18 into Wednesday June 19 while we import content and users from our Micro Focus Forums community site. MORE INFORMATION
Absent Member.. Madhu84 Absent Member..
Absent Member..
232 views

Assignee name validation not working

Jump to solution

Hi Experts,

 

We have noticed a strange issue in Incidents and interactions , When the assignment grp is selected and when clicking on Fill from Assignee name then it opens the relevant assignee name belonging to that assignment grp , Also in case if wrong name is typed ( uusers not listed in contact table then it displayes a warning message that " Assignee is not valid" , but when typing any user name from contact list and without clicking on fill , when the user saves the incident then it gets saved though the user doesnt belong to that assignment grp, we are running on SM 9.33 with Process designer.

0 Likes
1 Solution

Accepted Solutions
Absent Member.. John Stagaman Absent Member..
Absent Member..

Re: Assignee name validation not working

Jump to solution

The validation that the assignee is a member of the selected assignment group is not configured and needs to be added. Validations are in place for: assignment group is a valid group, and assignee is a valid  operator. You could configure the rule set as follows (this may not be correct, I'm not at an SM system right now):

 

Configure a Validate Field Against Table rule.

--Set the condition as: Assignment Group is not NULL and Assignee is not NULL

Field to validate: Assignee

Validate against table: Assignment

Validate against field: Operators

Filter: name=assignment in $L.file

 

You could add this rule at the workflow level (or Object level in 9.40) so that it applies to all phases. 

 

This example is specific to Incidents. Bacuase the assignment field in an Interaction is an array, it would need to be configured differently. 

----------------------------------------------------
Kudos - what, where, how, and why
Want Good Answers? Ask Good Questions...
3 Replies
Highlighted
Outstanding Contributor.. Ngoc_Ngo_SM Outstanding Contributor..
Outstanding Contributor..

Re: Assignee name validation not working

Jump to solution

Hi,

 

 

Could you please try to reproduce the issue and send me the sm.log file with the time stamp for a deep investigation?

 

Thank you and best regards,

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation.
Absent Member.. John Stagaman Absent Member..
Absent Member..

Re: Assignee name validation not working

Jump to solution

The validation that the assignee is a member of the selected assignment group is not configured and needs to be added. Validations are in place for: assignment group is a valid group, and assignee is a valid  operator. You could configure the rule set as follows (this may not be correct, I'm not at an SM system right now):

 

Configure a Validate Field Against Table rule.

--Set the condition as: Assignment Group is not NULL and Assignee is not NULL

Field to validate: Assignee

Validate against table: Assignment

Validate against field: Operators

Filter: name=assignment in $L.file

 

You could add this rule at the workflow level (or Object level in 9.40) so that it applies to all phases. 

 

This example is specific to Incidents. Bacuase the assignment field in an Interaction is an array, it would need to be configured differently. 

----------------------------------------------------
Kudos - what, where, how, and why
Want Good Answers? Ask Good Questions...
Absent Member.. Madhu84 Absent Member..
Absent Member..

Re: Assignee name validation not working

Jump to solution

Hi John,

 

Issue fixed the way you suggested.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.