How do I accomplish this?

Could anyone give me any tips to accomplish the following in Apex please?
I'm building a system to log maintenance requests. I've built a screen which allows the user to create a new maintenance request and put in a request description. This is recorded in a requests table.
I also want to maintain the history of a request in a seperate table (request_history). So for example, if a user adds a comment to a request, this is recorded in the request history table. A new record would be added to the history for each comment recorded.
So for example, a user creates a request. A record is created in the requests table. Later on they add a comment against the request. Afterwards this they add another comment against the request. So you end up with 1 record in the requests table, and 2 records in request_history (which hold the 2 additional comments).
When editing a request, I want the original request details (from the request table) to be displayed but not editable. Plus I want the 2 comments from request_history to be displayed, but again, not editable - in other words everything entered against the request is shown on screen. The user should only be able to add new comments against the request.
I'm a bit stumped as to how to accomplish this in Apex.. is there a type of page that would fit my needs.. or does anyone have a similar example they're created?

Hi Antilles
You're going to need several pages but all of them are easily doable within Apex.
1 - Main page - searchable report of existing requests. Each entry on the report would have a column link to the second page - this link would pass the REQUEST_ID value to that page to be used to filter its reports. There would also be an Add button to create a new request
2 - Request Summary page - this would contain your read-only data. The top half of the page would be a form based on the main table. The bottom half would be a normal report filtered on the same REQUEST_ID. There would also be an Add button to add a new comment. In this instance, you would probably create a page with Form and then add the report afterwards
3 - Request Creation page - called from the first page to allow for the create of a new request record
4 - Request comment creation page - called from the second page to create a new comment for the selected request.
These pages are very typical Apex pages and are quick to set up. If you need more detailed instructions, let us know
Andy

Similar Messages

Maybe you are looking for

  • How do I find and delete old plugins

    Since my leopard days I have been migrating data over as I updraded to the new OSX 10.9. When I start to open apps. Pro tools, Logic x, and otehr DAWs, there are some plug ins that are not compatable. Rather than leave a bug, and taking more time to

  • How do I get Microsoft Outlook Web Access to have the same view in Google Chrome as in IE9?

    In IE9 I can see a reading pane, just like in a PC view of Outlook.  However, I do not know how to get this when using Google Chrome.  Can anyone help?

  • MATCHES and complex queries

    I get an error message when trying to execute the instructions bellow create table publications public_id number, title varchar2(200), constraint publications_pk primary key(public_id) create table profiles profile_id number, rule varchar2(500), cons

  • Keyword selection failure

    When I apply a keyword from the keyword list to a picture, only the first letter in the keyword is added and then that letter becomes part of the keyword list. Does anyone know why? And how do I keep this from happening and getting Bridge to use the

  • Layers (especially text) not "updating" quickly or at all CS5

    When working with text heavy files in CS5 (64bit, windows 7 x64, core i7 920 proc), at some point, seemingly at random, layers will stop updating. Example: I'll edit a text layer, but it will not show in real time, and still won't show until I've cli