Absent Member.. Amanjyot Absent Member..
Absent Member..
390 views

Status Dependency Query

Can anyone please share the query on the editablity(status dependency) of the fields in a request type.. 

 

Thanks in advance..

 

Aman

0 Likes
3 Replies
Established Member.. Utkarsh_Mishra
Established Member..

Re: Status Dependency Query

You can get the details from following reports, including status dependency and all the other details.

 

  1. Request Type detail report
  2. Request header type detail report.

 

If you need the exact SQL, check the SQL code of these reports.

Cheers..
Utkarsh Mishra

-- Remember to give Kudos to answers! (click the KUDOS star)
0 Likes
Absent Member.. Jim Esler Absent Member..
Absent Member..

Re: Status Dependency Query

The interesting part of this effort will be to factor in the effects of UI rules.

0 Likes
Derek Giedd Honored Contributor.
Honored Contributor.

Re: Status Dependency Query

If you want SQL for this, here is what I use (Replace <Request Name> with your request type):

 

select crt.request_type_id, crt.request_type_name, cs.status_name, ns.section_name, npsf.prompt,
cfd.visible_field_flag Visible, cfd.disabled_field_flag Editable,
cfd.required_field_flag Required, cfd.reconfirm_field_flag Reconfirm,
cfd.clear_field_flag Clear, npsf.parameter_token
from KCRT_REQUEST_TYPES crt, KCRT_REQUEST_TYPE_STATUSES crts, KCRT_STATUSES cs,
KCRT_FIELD_DEPENDENCIES cfd, KNTA_PARAMETER_SET_FIELDS npsf, KNTA_SECTION_LAYOUTS nsl,
KNTA_SECTIONS ns
where crt.request_type_name like '<Request Name>'
and crt.request_type_id = crts.request_type_id and
crts.status_id = cs.status_id and crts.request_type_status_id = cfd.request_type_status_id and
cfd.parameter_set_field_id = npsf.parameter_set_field_id and
npsf.section_id = nsl.section_id and nsl.entity_primary_key = crt.request_type_id and nsl.section_id = ns.section_id
order by crt.request_type_name, cs.status_name, nsl.seq, ns.section_name, npsf.prompt;

-- Remember to give Kudos to answers! (click the KUDOS star)
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.