PHP RT Documentation

Between the online FAQ and this Documentation, we hope to provide you with all the information you need to make the decision to help us get your company online and ontrack with action items



Here you can see some of the requirements that were implemented:

Requirements for the Header Section

These were the requirements used to create the project:

  1. The date shall be displayed at the top of every page. Top Left corner.
  2. The title of the tool shall be displayed at the top of ever page. Top Center.
  3. The user profile link shall be displayed at the top of every page only when the user is currently logged in. Top Right.
  4. The name [First Last] of a user logged in shall be displayed at the top of every page when a user is logged in. Top Right.
  5. The label “Guest” shall be displayed at the top of each page when the user is not logged in. The link “Login” shall be displayed next to it. Top Right.
  6. When a user is logged in, and that user is a database admin, a row of links for the DB Admin shall be displayed.
    – Users, Projects, Database, AccessTimes
  7. When a user is logged in, and that user is a project admin or a database admin, a row of links for the Project Admin shall be displayed.
    – Admin Projects, Items, Access, Distributions, States, Templates
  8. A button and select list shall be displayed at the top of each page for viewing ALL or any one of the projects this user has at least display access to. If the user is on a page specific to any of those projects, then that project will by default be selected in this select list. If none applies, then the default is ALL. Top Left. [user must be logged in]
  9. A button and select list shall be displayed at the top of each page for creating a ticket in any of the projects that this user has access to create tickets in. If the user is on a page specific to any of those projects, then that project will by default be selected in this select list. If none applies, then the default is “-Choose Project-“. Top Right. [user must be logged in]
  10. A text box and form submit button shall be displayed at the top of each page if a specific project is being displayed. This will be how a user can enter a ticket number of that specific project and go directly to that project. When no specific project is selected, this option will not appear. Top Center. [user must be logged in]

Requirements for the Login Page

  1. User shall be required to enter a username and a password to log in. Their username must be valid, and password must match, and the account must be active.
    Note. When a user logs in, if their password was created on a date that is older
    than the Database-Admin setting, then their password will be expired.
  2. In the case where the password is expired, a new password shall be created and sent via email to that user’s email address.
  3. In the case where the password is expired, the user shall be allowed to login and continue for this session.
  4. Accounts that are attempted to be logged into with an invalid password consecutivly greater than 3 times shall have their account disabled.
  5. When an account becomes disabled due to login failure, a re-enable link is sent to the user’s email address.
  6. When a disabled account is re-enaled via the HREF link that is sent that user, the account shallb e reactivated.
    Note: If a user does not perform an action of any kind beyond the SessionTimeOut time, then that session is suspended.
  7. A suspended account must have the user enter their username and password to un-suspend the account.
  8. All actions being performed when the account is suspended must be continued after the user re-authenticates to un-suspend the account.
  9. When any user logs in, the time of the login shall be recorded in the database.
  10. When any user logs in, their succesive bad counter is reset to 0.
  11. When a user fails to log in with the correct password, the successive bad counter is incremented by 1.
  12. When a user fails to log in with the correct password, the total bad password counter is incremented by 1.
  13. When a user logs in correctly, the total login counter is incremented by 1.
  14. After a user logs in correctly, they shall be sent to the ticket listing page.
  15. When a user is not logged in, the user log in page shall have only one link to another page on this page, to the Forgot-Password page.