Databases Reference
In-Depth Information
Note
If you try to import a response into an environment it wasn't exported for, you'll get an error.
After importing, you will see that the changes you made in development are reflected in the
feedback of the deployment system, as shown in Figure 4-29. And although the Developer comments
you entered are exported, they are not imported.
Figure 4-29.
Import response into deployment
Once you've imported the response, you have reached the end of the feedback lifecycle. But
sometimes you need some additional information to solve an issue, as in the example above. Of course,
you can call or email the person who submitted the feedback, but there is an option within Team
Development that supports this functionality as well. Unfortunately, it is not automatically
implemented, but you can implement it yourself with some additional easy steps.
Extending Feedback: Create a Report
The first thing to do is to create a report on the feedback, so the user can not only report feedback, but
also has insight on the status. To begin, create a report page, with page number 103 in this example, and
make it accessible according to your standard application navigation style; it can be an entry in a list, a
tab, or a link in the navigation bar. The following
select
statement selects the data from the
apex team feedback
view and should show only the feedback for the current application. You can also
choose to narrow the selection down, so users can only see the feedback they entered themselves, or
feedback with a certain status. That's all up to you.
SELECT feedback number "Nr."
, feedback id "Follow up"
, feedback
, CASE
WHEN feedback type = 1 THEN 'General Comment'
WHEN feedback type = 2 THEN 'Enhancement Requested'
WHEN feedback type = 3 THEN 'Bug'
END "Type"
, CASE
WHEN feedback status = 0 THEN 'No Status'
WHEN feedback status = 1 THEN 'Acknowledged'
WHEN feedback status = 2 THEN 'Additional Info. Requested'
WHEN feedback status = 3 THEN 'Open'
WHEN feedback status = 4 THEN 'Closed'
