59.109 REPLY_TO_FEEDBACK Procedure
This procedure enables you to submit a reply to a feedback.
Syntax
APEX_UTIL.REPLY_TO_FEEDBACK (
p_feedback_id IN NUMBER,
p_type IN NUMBER DEFAULT NULL,
p_status IN NUMBER DEFAULT NULL,
p_tags IN VARCHAR2 DEFAULT NULL,
p_developer_comment IN VARCHAR2 DEFAULT NULL,
p_public_response IN VARCHAR2 DEFAULT NULL,
p_followup IN VARCHAR2 DEFAULT NULL )
Parameters
Parameter | Description |
---|---|
p_feedback_id |
The ID of feedback. |
p_type |
The type of feedback (1 is General Comment, 2 is Enhancement Request, 3 is Bug). |
p_status |
The status of the feedback (0 is No Action, 1 is Acknowledged, 3 is Open and 4 is Closed). |
p_tags |
Used to categorize feedback, only to be displayed to developers (not in the current feature implementation). |
p_developer_comment |
Comments not displayed to the users but could be displayed to developers (not in the current feature implementation). |
p_public_response |
Text that will be displayed to the users. |
p_followup |
The text of the follow-up. When the Feedback feature is added to an application, it only uses p_public_response . It does not support passing data to p_followup .
|
Example 1
In this example, the app admin replies to a feedback submitted by a user reporting a bug.
BEGIN
apex_util.reply_to_feedback (
p_feedback_id => 12345,
p_type => 3,
p_status => 1,
p_developer_comment => 'Created JIRA BUG-123!',
p_public_response => 'Thank you for letting us know about this! We will fix it in the upcoming release!',
p_followup => 'We really appreciate your support of our application.' );
END;
Example 2
In this example, the developer leaves a comment about creating a ticket for the bug reported by the user, and closes the feedback workflow.
BEGIN
reply_to_feedback (
p_feedback_id => 12345,
p_type => 3,
p_status => 4,
p_developer_comment => 'Filed ticket BUG-123!',
p_followup => 'We really appreciate your support of our application.' );
END;
Parent topic: APEX_UTIL