Core Fields: Change Request (Feedback)

Modified on Thu, 3 Sep at 4:58 PM

Core Fields: Change Request (Feedback)

The fields available for the Change Request module, and what each one is for

Contents

1. Introduction & Context
2. Key Features & Functions
3. Requirements
4. Step-by-Step Guide
- Change Request: Field Reference
5. Common Issues & Troubleshooting
6. Related Articles

1. Introduction & Context

This article lists the fields available for the Change Request module and what each one is for, and shows how to choose which fields appear as columns in the Change Request list view.

Who is it for? This is configured by Clew Admins in Admin Settings, under Custom Types > Change Request.

What does it impact? These settings control what your team sees and can enter on Change Request records, not the underlying data itself.

Note: Controlling where a field appears (New Form, Edit Form, Mass Edit Form, Show View) works the same way for Change Request as for every other module, using the eye icons and Mass Edit in Core Field Settings. See Core Fields: Overview for how that works; this article focuses on what the Change Request-specific fields are and what they mean.

2. Key Features & Functions

Field coverage: covering ownership & assignment, complaint / feedback details, complainant information, dates & scheduling, and record & system fields, listed in full in Section 4.
Default list view columns: out of the box, the Change Request list view shows Type, ID #, Summary, sensitivity, Status, Register, Location, Business Unit, and Initial Response Due Date.

3. Requirements

Clew Admin access, to open Admin Settings and Custom Types > Change Request.
The Change Request module must already be enabled in Clew.

4. Step-by-Step Guide

Change Request: Core Field Visibility

Go to Admin Settings and open Custom Types.
Select Change Request.
Scroll to Core Field Settings. Use the search box to find a specific field if the list is long.
Update fields individually using the eye icons, or select several rows and use Mass Edit. See Core Fields: Overview for how these controls work.

By default, the Change Request list view's Selected Fields include Type, ID #, Summary, sensitivity, Status, Register, Location, Business Unit, and Initial Response Due Date.

Change Request: Field Reference

The fields available for the Change Request module, grouped by what they're used for. For how to control where each one appears (New Form, Edit Form, Mass Edit Form, Show View), see Core Fields: Overview.

Ownership & Assignment

Field	What it's for
Approver	The person responsible for approving the change request or feedback item.
Approver Role	The role the Approver holds.
Assignee	The person the record is currently assigned to.
Assignees	Everyone currently assigned to the record, where more than one person can be assigned.
Assignee Role	The role the assignee holds.
Owner Role	The role the Owner holds.

Complaint / Feedback Details

Field	What it's for
Details of Feedback	A written description of the feedback or complaint raised.
Feedback Type	The type of feedback this record is classified as.
Complaint Type	The type of complaint, where the feedback raised is a complaint.
Conduct Category	The category of conduct the complaint relates to.
Business Objectives	The organisational objective(s) that this record relates to.
sensitivity	How sensitive the record is, likely controlling who can view it.
Business Unit	The business unit the record belongs to.

Complainant Information

Field	What it's for
Complainant Email	The email address of the person raising the feedback or complaint.
Complainant Phone	The phone number of the person raising the feedback or complaint.
Preferred contact method	How the complainant prefers to be contacted.
Is the Complainant a member of the public?	Flags whether the person raising the complaint is a member of the public, as distinct from an employee or contractor.
Have you raised this issue before?	Flags whether the complainant has raised this same issue previously.

Dates & Scheduling

Field	What it's for
Date and Time of Event	The date and time the event being reported occurred.
Original Review Date	The review date originally set, before any extension.
Initial Response Due Date	The date by which an initial response to the complainant is due.
Closed at	The date and time the record was closed.

Record & System Fields

Field	What it's for
Type	The record type classification, distinguishing this custom type (Change Request / Feedback) within its module.
ID #	The unique identifier number automatically assigned to the record.
Summary	A short summary of the change request or feedback item (equivalent to a title field, labelled Summary in this module).
Status	The record's current position in its workflow, for example Draft, Open, or Closed.
Register	The register the record belongs to.
Location	The physical or organisational location the record relates to.
Created at	The date and time the record was first created.
Updated at	The date and time the record was last updated.
Created by	The user who created the record.
UUID	A unique identifier automatically generated for the record, in addition to the sequential ID #.

5. Common Issues & Troubleshooting

These issues apply to Change Request (Feedback) the same way they do to every module. See Core Fields: Overview for the general troubleshooting table and best practices.

Issue	Likely Cause	Solution
A Change Request (Feedback) field doesn't appear on a form or Show View	That specific column is switched off for the field in Change Request (Feedback)'s Core Field Settings	Open Custom Types > Change Request (Feedback) > Core Field Settings and switch on the relevant column for that field
A field isn't listed under Change Request (Feedback)'s Available Fields or Core Field Settings at all	The field has not been enabled for your organisation	Raise a request with Clew support to have the field enabled for Change Request (Feedback)

Recent Searches

Core Fields: Change Request (Feedback)

Was this article helpful?

Recent Searches

Popular Articles

Articles

Topics

Tickets

Core Fields: Change Request (Feedback)

Was this article helpful?