When I tried to submit an RFI myself, I got this report: 
DBD::mysql::st execute failed: Duplicate entry '010' for key 1 at init
+iate_rfi_send.pl line 173.

[download]
That might just be the test environment, or it might be something you really need to fix. The form for entering the RFI showed this information for the "RFI Number" field: "10 auto increment last RFI number was 9", so I'm wondering if you are assigning this key field prematurely. You should only need to report such an ID number after the RFI has been fully submitted, not before; that is, don't assign an ID (or insert a row in the table) until the person submits all information in an acceptable manner, then report back what the primary ID value is (as assigned by the autoincrement that is done as a result of the insert).

(Just a thought: in terms of reporting ID numbers of requests for use by people who submit requests: you might want something in addition to just an autoincrement numeric key -- e.g. prefix the number with the submitter's initials (or company initials, or some other short letter string), such that two different submitters (or submitters from different companies) get different letters, which are derivable from some other field in the entry for each RFI. This may help identify and sort out problems when people make mistakes like transposing, skipping, adding or changing digits in the numeric ID.)

I noticed that you ask the person submitting the RFI to fill in the "Creation date"; shouldn't that be set automatically upon submission? (ie. the table field for "creation_date" is set to the return value of "NOW()" when the insert is done). You also ask for a "PCR number if any" -- how sure are you that users know what this is?

Finally, you probably have some of this on hand or in mind already, but obviously the RFI submitter will want clear feedback on when to expect a response, how that response will be conveyed, who to contact if the response doesn't arrive as expected, and how to contact that person.

People charged with responding to RFI's will of course need a "response" table that allows them to submit entries reflecting phone conversations, independent email and IM dialogs, and maybe even office visits, in addition to internet transactions. (And requesters should be able to review all response records for a given RFI that they submitted.)

In reply to Re: RFC, a web based application by graff
in thread RFC, a web based application by demonlazeros

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.