How to make the userid field required in Service Desk's contacts, without causing the same restriction to be applied to groups.

book

Article ID: 49100

calendar_today

Updated On:

Products

CA IT Asset Manager CA Software Asset Manager (CA SAM) ASSET PORTFOLIO MGMT- SERVER SUPPORT AUTOMATION- SERVER CA Service Desk Manager - Unified Self Service KNOWLEDGE TOOLS CA Service Management - Asset Portfolio Management CA Service Management - Service Desk Manager

Issue/Introduction

Description:

How to make the userid field required in Service Desk's contacts, without causing the same restriction to be applied to groups.

Solution:

In Service Desk, contacts can consist of groups and actual end users. While most contacts have userids, groups generally do not have associated userids. One may wish to make the userid field mandatory by using Schema designer to make the userid field required, but since groups have a userid associated, but is not visible to the facing end user, attempting to create a new group under such conditions will result in a required field error message.

To work around this, it is suggested to remove the schema change made to have userid to be required in the contact record and use the following data partitions to be included to allow for userid to be required for non-group contacts:

Table: ca_contact
Constraint Type: Update
Constraint: userid IS NOT NULL OR (type = 2308)

Table: ca_contact
Constraint Type: Create
Constraint: userid IS NOT NULL OR (type = 2308)

Environment

Release: UAPMAC990JPP-12.6-Asset Portfolio Management-Asset Configuration
Component: