An application process defines how a school or organization applies for accreditation in one of your programs. It controls the contact forms, organization forms, Portal display, and confirmation email used for that program’s application. There is not a Console or Portal page for this yet, so you need API access to set one up.
Prerequisites
You need API access to your Rhythm account to configure an application process. There is not a Console page for it.
What This Controls
- Whether a program has an application process, and which program the process belongs to.
- The contact form, organization form, Portal display, and confirmation email an applicant uses for each option you switch on.
Where to Find It
There is not a Setup or Portal page for application processes. Configure the process through the Accreditation API for the program that should use it.
Required Fields When You Switch Something On
An application process only requires the pieces you switch on. When you turn on a contact form, organization form, Portal display, or confirmation email, you must also provide that piece’s matching form, option, or template. If it is missing, the save is refused.
| If you switch on… | You must also provide |
|---|---|
| A contact form | The contact form itself |
| An organization form | The organization form itself |
| Portal display | The display option it needs |
| A confirmation email | The email template |
Anything you leave switched off does not require a matching form, option, or template. If you provide a form of the wrong kind for a piece you switched on, the save is refused.
Previewing the Application Email Does Not Currently Work
Warning
Every attempt to preview an application email currently fails, no matter what you send. To check how an application email will look, send a real or test application through the process and review the email it sends.
One Application Process Belongs to One Program
An application process is configured for one specific program. If you run more than one accreditation program, each program can have its own application process, with its own forms and email. There is no shared application process across programs.
Dependencies
The contact form, organization form, and email template named in an application process should already exist before you configure the process around them. When you save the process, Rhythm does not check whether a named form or template exists, or whether it was deleted later.
Permissions
Configuring an application process requires API access to your Rhythm account. There is no Console permission for it, because there is no Console page.
Validation and Errors
| Situation | What happens |
|---|---|
| A switched-on piece (contact form, organization form, Portal display, or email) has no matching form, option, or template | The save is refused with a validation error |
| A form of the wrong kind is supplied for a switched-on piece | The save is refused |
| An email preview is attempted | The request fails |