User fillable - secure web forms with a complex process. Residential Assistant hiring process is the first one in the works.
Resjobs - pick students to work in the dorms. Resjobs is a type of workflow, so why not use the same workflow product. But sometimes, if the product is too complicated, it makes sense to split the products back into simple and complex products (so, that's still an option).
Fellowship Matching or Residential Matching is another one of the functions they are looking for.
Functionality Highlights
Roles and Permissions
- Submitter, Owner, Administrator, Reviewer, Viewer
Form Options
- Generic fields, Custom (Multi fields as one), Validation, Integration, Calendar, Encryption
Email Platform
- Email Template with place holders, Batch Email, etc
Work Flow
- Sequential, Parallel, Multiple Status
Work Flow Logic
- Date Triggered, Data Dependent, Ranking/Matching
Administration
- Reports, Notification, Archiving
Integration
- On-Campus Systems (PeopleSoft, Registry,...), Shibboleth, ExploreCourses
(Getting information out of PeopleSoft but not into as that would change the source file.
PeopleSoft feeds People Registry, the results of the view are loaded in LDAP.
Vendor Selection
1. Utilize Open Source Product (ProcessMaker - http://www.processmaker.com/, other?)
2. Proprietary Solution (E-Resource, other?)
3. Custom Built for Our Needs (Outsourced Developer)
4. A Hybrid Product (Drupal, other?)
Other workflow engines are used on campus are NOLIJ and OnBase (used less)
GSB: Using Drupal for one of their forms (not the workflow), but will be moving that and the workflow to force.com. [What's the reason? GSB does have an underlying use of force.com already.]
Another company working with Drupal is TRELLON who did work for Cornell.
Java application used in the Cancer Center called Savoy.
Examples to upload: ProcessMaker screenshots for the workflow engine and form building.
When selecting a product, you need to look at the underlying technology (patches, requirements, etc.) as it can determine how much maintenance the product will require.
Secure Web Forms with Complex Workflow
Proposed by Sergei Rutenberger / Stephen Arod Shirreffs
Where will the conversation continue?
Send email to arod@stanford.edu with your email address to continue the conversation.
Notes

