Documentation

These two modules allow pastors and churches to login to their respective dashboards and fill out and submit 3 specific forms related to their pastor or church appointments.

A Video Walkthrough

Description

The People controller has 8 primary views as well as additional views for common functionality such as login, change password, and 'forgot my login'. The 8 primary views allow the user (church or password) to see all the forms they need to complete ("PeopleIndex" and "ChurchIndex" views) as well as views to display each of the 3 forms they must complete (People/Church Profile, People/Church Ministry Reflection, and People/Church Appointment Preference).

For the churches, each church has a new menu item when logging in to their church dashboard. This new item, called "Church Appointment Forms", takes them to a new page that lists the 3 forms that they are required to complete and submit online. Upon submission, the link on the index page is grayed out indicating that the form is complete. Churches are able to save their work as many times as needed before officially submitting the form, giving them the ability to partially complete the forms and come back later to continue working on them.

For the pastors, there is a new login area where they will login and see the same 3 forms related to their church appointments. Each pastor will be given a unique username and password and allowed to login and complete the forms. These will work the same way as the church forms, where the user is able to save their work and come back later to continue working on the form until they are finished and officially submit the form using a checkbox at the end. Once submitted, the form is unable to be edited.

Sample Images

These images are examples of the layout of the forms to be completed by the churches and pastors.

Tables Created

We created two new tables to store all the content for the people and church forms. oPastor_Appt stores all the data entered by the pastors, and oChurch_Appt stores all the data entered by the churches. Both are related to the oPeople and oChurches tables respectively, using a Many To Many relationship. This allows a console user to view the data entered by the pastor/church using a new tab when looking at the person or church.

Forms Created

Using the Brick River Forms Builder and some custom CSS, we were able to very closely reproduce the existing 3 forms currently in Microsoft Word. Here are some images of the forms created using the form builder.

SQL Examples & Explanation

Upon login of the church or pastor, the system first checks if they have a record in the corresponding table (oPastor_Appt or oChurch_Appt) for that year. If no record exists, we first create an empty record for that year and relate it to the person or church logging in. We execute this SQL in the people controller and then redirect them to their corresponding index page displaying the forms to be completed.

BEGIN
DECLARE @id INTEGER;
SELECT @id=oPastor_Appt.oPastor_Appt_ID FROM oPastor_Appt
    INNER JOIN roPeople_2_oPastor_Appt ro
ON ro.r_oPastor_Appt_ID = oPastor_Appt.oPastor_Appt_ID
WHERE ro.r_oPeople_ID = @peopleID;
IF @id IS NULL
BEGIN
    INSERT INTO oPastor_Appt (year) VALUES ('2010');
    SET @id = @@IDENTITY;
    INSERT INTO roPeople_2_oPastor_Appt (r_oPeople_ID, r_oPastor_Appt_ID) VALUES (@PeopleID, @id);
END
SELECT @id;
END

BEGIN
DECLARE @id INTEGER;
SELECT @id=oChurch_Appt.oChurch_Appt_ID FROM oChurch_Appt
INNER JOIN roChurches_2_oChurch_Appt ro
ON ro.r_oChurch_Appt_ID = oChurch_Appt.oChurch_Appt_ID
WHERE ro.r_oChurches_ID = @ChurchID;
IF @id IS NULL
BEGIN
INSERT INTO oChurch_Appt (year) VALUES ('2010');
SET @id = @@IDENTITY;
INSERT INTO roChurches_2_oChurch_Appt (r_oChurches_ID, r_oChurch_Appt_ID) VALUES (@ChurchID, @id);
END
SELECT @id;
END