How to exclude mandatory field from CQ in defect/UC template

Hi,

Perhaps we don't fully understand your question, but if the fields are mandatory for the CQ record, there is nothing in the CQ connector to override this.

Some alternatives:

- add hook code to provide the mandatory fields
- change the schema to not make those fields mandatory
- add custom attributes to the work item, give them some defaults, and include them in the sync rule.

Rich
Jazz CQ Connector team

Are you asking whether the synchronization process can somehow violate the constraints of your CQ schema design by not providing values for required fields? If so, the answer is no; the schema constraints apply, no matter how a record is being created. It may be possible to define default values in your sync rules for required fields, depending upon the type of the field.

Hi Team,

We are doing RTC-CQ integration. We have few mandatory fields in CQ form which i want to exclude in the rule for sync.

Means: I do not want to add fields (which are mandatory in CQ) to the RTC defect/Use case template.

How to do this?

Hi,

Perhaps we don't fully understand your question, but if the fields are mandatory for the CQ record, there is nothing in the CQ connector to override this.

Some alternatives:

- add hook code to provide the mandatory fields
- change the schema to not make those fields mandatory
- add custom attributes to the work item, give them some defaults, and include them in the sync rule.

Rich
Jazz CQ Connector team

Rich,

I'm trying to make sure I'm understanding this discussion correctly. Are you saying that RQM has no mechanism to facilitate the enforcement of required field specs in ClearQuest? Our CQ schema has fields that are required during certain actions and optional during others. At the moment, the only records I can't sync are those with required field mismatches. I'm looking for a way to resolve the incongruency other than making the CQ fields optional.

The CQ Connector is really nothing more than another CQ client, when it comes to creating and updating records. If there are mandatory fields then they must be provided via the sync rules.

Please consult the following url, steps 5, 6 and 7, for advice on how to
handle this situation:

http://publib.boulder.ibm.com/infocenter/rtc/v1r0m0/index.jsp?topic=/com.ibm.team.connector.cq.doc/topics/t_planning_synch_rules.html

(The 2.0 document is found using the same url, except use v2, but
not much has changed since 1.0).

Rich
Jazz CQ Connector team

BTW, if anyone can figure out how one would automate the satisfaction of
CQ required field constraints, when the CQ schema can define arbitrary
hook code to define those constraints, please let us know (:-).

Cheers,
Geoff

perrysmith wrote:

rpiazzawrote:
Hi,
Perhaps we don't fully understand your question, but if the fields
are mandatory for the CQ record, there is nothing in the CQ connector
to override this.
Some alternatives:

- add hook code to provide the mandatory fields
- change the schema to not make those fields mandatory
- add custom attributes to the work item, give them some defaults,
and include them in the sync rule.
Rich
Jazz CQ Connector team

Rich,

I'm trying to make sure I'm understanding this discussion correctly.
Are you saying that RQM has no mechanism to facilitate the
enforcement of required field specs in ClearQuest? Our CQ schema has
fields that are required during certain actions and optional during
others. At the moment, the only records I can't sync are those with
required field mismatches. I'm looking for a way to resolve the
incongruency other than making the CQ fields optional.