Hi, I thinking about the registration process - either student or conference attendee - layout with regard to CPS-sections and workspaces. The usual CPS-way, as I understand it, is someone creates a document in a workspace and then it is published in a section. I plan to apply this modell to the conference registration process like so:
Anonymous user registers for the conference means: - registration-form is presented to the user - after successful data entry, an attendee_id is generated and a new attendee_record (ar) is created in the attendee-workspace (aws) for that user. - the ar-workflow for the ar "publishes" this rr in the attendee-section (as) ie. - it sends an email to the attendee - checks payment - and so on. - if the attendee wants to modify her/his ar she/he does this in the aws. The ar-workflow takes care of publishing this modification in the as. Does that make sense ? -- Mit freundlichen Grüßen Joachim Schmitz ...................................................................... AixtraWare eK ..Joachim Schmitz ..www.aixtraware.de ..t: +49-2464-8851 Hüsgenstr. 33a .....d-52457 Aldenhoven .............f: +49-2464-905163 _______________________________________________ cps-users mailing list [email protected] http://lists.nuxeo.com/mailman/listinfo/cps-users
