1) this one of the tweaking tasks that I need to refine. I am still trying to asses if the user needs to know the next number before or after completing the form.

2)good suggestion.

3)Yes the creation date will be automatic. Some companies have internal ways of keeping RFI's that they have. The PCR(I cant remeber what PCRstands for but it is meant to give the sub a choice if he keeds his own records) number will let them reference back to their system. Some contractors may not have computer based filing methods.

4)The feed back will usually be based on the way the contract is set up between the developer and the architect. Some contractors may have negotiated different responce times, but it may be a policy that a responce time be entered in the text message. The responce will be emailed to any one the responder feels needs to get the responce, the admin gets all responces and may add forwarding to any one ledft out. The program will also log when some one reads the responce, or at least opens that page. Whether they read it or not is a different matter all together but at least the admin can present a report that the responce was received.

MY thought is that the agreement between the architect and all parties involved must communicated via the RFI, but you are right there should be an additional log of none system communications.

Requesters will have access only to RFI's that concern them or their trade or as given permission by the admin.

MY goal is to give the admin full and total control of the RFI process and storage. He will be able to create reports on the fly at meetings rather than waite till he gets back to the office. If he has internet connection he can answer any question concerning the project at any meetings.This goes for all the subs, they will be able to report from the same database any info strictly pertaining to them.

In reply to Re^2: RFC, a web based application by demonlazeros
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.