ARMS Project Home

Statement of work for ARMS:

Work Flows

All steps performed using a web browser

The site administrator creates a new activity type, "Initial Eligibility Form".
The site administrator creates custom data fields and a profile or webform which to collect the "initial eligibility" data. This form will include contact data and "initial eligibility" activity data (core and custom fields supported).
The site administrator configures a rule/email template which should be sent to any assignee of a scheduled activity of type "Complete Initial Eligibility Form"; the email would be sent one-day before due and every day thereafter until activity status is "Completed". The email template includes a specially-coded link that references the form (profile ID or webform) and activity ID.

The staff member (site user) creates a contact record for "Amy Adams (amy@a.com)".
The staff member creates an activity of type "Complete Initial Eligibility Form" with target "Amy Adams", assignee "Amy Adams", status "Scheduled", and date-time "2011-08-15 12:00".

Sometime around 2011-08-14 12:00 (give or take an hour), an email is automatically sent to the assignee "Amy Adams (amy@a.com)"
Sometime around 2011-08-15 12:00 (give or take an hour), a second, identical email is automatically sent to the assignee "Amy Adams
(amy@a.com)".
Around 2011-08-15 14:20, Amy clicks the link in either email and begins filling out the form.
Around 2011-08-15 14:25, Amy submits the form – which effectively updates fields for the activity and the target contact ("Amy Adams"). The activity status changes to "Completed" and the Activity Date changes to "2011-08-15 14:25".

Extend Profile to allow editing of Contact (which includes Address, Phone, Email) and Activity + Custom Data related to this set of objects: CRM-8147, CRM-8148
Extend Webform integration to allow "webform admins" to create forms with above fields and save them. The UI for this will be fairly simplistic for the first phase (configuration form will be one screen with all available fields and some form-rules to prevent invalid combinations). CRM-8153
Implement user interface for scheduling emails based on activities as described in schedule.png. CRM-8150, CRM-8151
Implement a cron job subsystem to manage and send those emails. CRM-8152
Integrate hooks in all the above sub-systems so external modules can customize behavior. CRM-8152

Day 2 - All work issues filed in CiviCRM issue tracker
- Top Level Arms Issue
Day 4 - Review and feedback on issues by ARMS completed
End of week 1 - Dev task 1 completed, Dev task 3 in progress
End of week 2 - Dev task 2 in progress, Dev task 3 complete, Dev task 4 in progress, ARMS to do walkthru of work in progress in development sandbox
End of week 3 - Dev task 2 complete, Dev task 4 complete, ARMS to do walkthru of work in progress in development sandbox
End of week 4 - All Dev tasks complete
End of week 5 - Acceptance testing by ARMS, bug fixes completed, project is "complete"*.

"Complete" means the 3 user work flows defined above are functional and accepted by ARMS. Bugs will be fixed as reported for a period of 3 months from the end of week 5.