A review form works like any other web form in your account. Before reviewers use it, check two areas carefully: the recommendation choices on the form and the page members use to find their reviews.
Prerequisites
- You need access to your account's web forms setup to edit a review form's components.
- The Review Center sits on a Portal page. The person who builds your Portal pages adds it, and you need access to that page in the page designer to change its route setting.
- Your submission form needs at least one page with the required built-in Name field. Custom fields on that page are optional. Your review form needs the built-in components Review Submission, Review Scores, Submit Scores, and Success Message. Its final page needs Submit enabled and the Next transition removed.
- To test a reviewer-facing page, sign in with an account that has reviews assigned in that space or event. An account with no assignments has nothing to show, which can look like a routing problem even when the setup is correct.
Relabeling or Restricting Recommendation Choices
If your review settings ask reviewers for an overall recommendation along with their scores, the recommendation uses four fixed values: definitely not, no, yes, and strong yes. In the form designer, the review form's recommendation component lets you give those choices your own display labels and choose which of the four values reviewers can select on that form.
Warning
Relabeling a recommendation only changes what reviewers see on that review form. Everywhere else the recommendation appears, including the review record, reports, and dashboards, staff see the underlying value in title case. If you relabel "Strong Yes" as "Highly Recommend" on the form, reviewers see "Highly Recommend" while they fill it out, but staff see "Strong Yes" everywhere else. Choose wording your team will recognize later.
Restricting the values on the form only changes the choices reviewers see on that form. It does not stop the value from being recorded another way, so treat the restriction as guidance for reviewers rather than a hard limit on what a review can contain.
Warning
Removing the recommendation component from the visible form does not always remove its validation. Reviewers can still see an error that the recommendation does not have a valid value after the field is no longer shown, which blocks them from advancing. If you need to stop asking for a recommendation, check the review form's validation rules along with the visible component.
Downstream workflow behavior, such as approval routing for a review or transmittal process, can depend on the recommendation value a reviewer selects. For example, routing may advance only when a specific value, such as the affirmative recommendation, is chosen. Check your account's workflow before you relabel or restrict values, because automation may depend on matching one of the four stored values.
Fixed Component Titles and Labels
Some component titles on the abstract review form are hard-coded, so administrators cannot rename them. This is different from the recommendation choices above, which you can relabel. The co-author component works the same way: apart from its heading, its internal wording cannot be changed.
If you need different wording for one of these fixed titles, submit it as a product idea. Support cannot change hard-coded component text through account configuration.
Customizing the Review Form's Final Action Button
A review form works like any other web form, so you can change its transition button labels the same way you would on any page. To show Submit instead of the default Save on a review form's last page, open the form, open that page's Transitions tab, and change the label in Options.
What Reviewers See on the Review Form
A reviewer-facing review page layout can include a submission's review built-in fields and review custom fields. It cannot include built-in contact fields such as institution or job title. If reviewers need that kind of information, capture it as a review field instead.
If you want reviewers to see something like the presenter's email address, collect it on the abstract submission form first. Then add that same field as a component on the review form. The review form can only display data the submission has already captured; it does not pull fields in from elsewhere.
The Accepted Submission Information component, and similar review-data areas, only show values entered earlier on the same form. Those values must come from components above it on the same page or from earlier pages. They cannot pull in values from a separate abstract submission form.
Tip
If a review question appears to be missing when you test a review form, check whether explanatory or prompt text was placed directly over the question instead of in the component's Guidance or Help area. Move that text into Guidance or Help so the question itself stays visible.
Tip
The built-in reviewer Notes field does not appear as a queryable field on the Review 360 page. If you need reviewer notes to show there and be usable in a query, add a custom field to the abstract's page layout instead and assign it for reviewer use in Review Settings. It then appears under a Custom Field tab on Review 360 and can be used in review queries.
Pointing the Review Center at Your Own Page
The Review Center is the Portal element that shows signed-in members every open space where they belong to a review team. It is the page a Reviews Overview menu item should point to, at the route /reviews/overview, and it is the preferred entry point for reviewers looking for their approval processes and reviews. An older page at /abstractReviews/reviewsCenter looks similar, but it is no longer maintained and does not show the abstracts available for review. Avoid linking a Portal menu item to it.
The Review Center displays open spaces as cards. To hide a program from reviewers, open the related space in the Submissions & Reviews app, go to Setup, then Space Details, and change its status from open to closed. The Review Center only lists open spaces where the member belongs to a review team.
When a member selects a card, Rhythm normally opens the built-in review space page. Your Portal page builder can change the Route (View Review Space) setting from its default value, /reviews/viewSpace.
- In your Portal's page designer, select the Review Center element.
- Open its Route (View Review Space) setting.
- Enter the address of your own review space page instead of the default.
Result
When a member selects a space card in the Review Center, Rhythm sends them to your chosen page instead of the default page, with the space's identifier added to the address.
Warning
Rhythm does not check whether the page you enter exists. If you point the Review Center to a page your Portal does not have, members who select a space card land on a page that is not there. Create and test the destination page before you change this setting, then check it again with a real reviewer account after you save.
Tip
The review space page needs a space identifier in its URL. That identifier normally comes from selecting a card on the Reviews Overview page, so a Portal menu item that links straight to the review space page will not resolve on its own. If reviewers say they cannot see abstracts they are assigned to, check that their menu item points to the Reviews Overview page, not the Abstract Center page, and that it includes the route or full URL for the specific event space. If you want reviewers to skip the overview list and go straight to one space, you can edit a menu item to link directly to that space's review-space URL.
Write reviewer notification emails so reviewers know to sign in to the Portal and find their reviews there. Do not imply that the email itself will take them directly into a specific review step. The intended path is always through the Portal, not a deep link.
The Review Center's list of spaces, and other reviewer-facing display limits, are fixed by product design. If you need a different display count, submit it as a product idea. Support cannot change this through account configuration.
Removing the Continue Button from a Review Form
A review form's Review Submission page normally acts as the form's completion page, so it shows a green Continue button that does not lead anywhere useful after a reviewer has finished. To remove it, change the Review Submission page's type from Completion to Fixed. Then add a new page with the Completion type and place the Success Message component on that new page instead. This separates the submission page from the completion step, so the Continue button no longer appears where it does not belong.
Permissions
To edit a review form's components, you need the same access required to edit any other web form in your account. To change the Review Center's route setting, you need access to edit the Portal page where the Review Center appears.
Validation and Errors
Neither setting has its own save validation beyond what your web form editor or Portal page editor already checks for that type of change. Rhythm does not verify that the Review Center's destination page exists, so you will not see an error message if you mistype it. The only sign of a problem is a member reporting that they land on a missing or wrong page after selecting a space.
| What you see | Likely cause | Check or fix |
|---|---|---|
| A reviewer's profile shows assigned reviews, but signing in to the Portal and opening the review page shows nothing | The review page's component may not be configured with the correct abstract code, even though the assignment data is correct | Open the review page component in the page designer and confirm it points to the right abstract code for that space |
| Reviews are missing even though the submission or abstract's Portal display status and dates look correct | The signed-in account may not be the one the review was assigned to | Confirm the reviewer is signed in to the account associated with the assignment, not a different one |
| Reviewers who could previously click into their review spaces no longer can, even though the route and page still look correct | The submission space's review data or the page installation may need to be refreshed | Rerun review-space maintenance to repopulate the target submission space, and reinstall the page, then test again |
| Creating or renaming a review form from the Submission Review (Long Form) template fails with a duplicate page ID error | Renaming during a template copy can create a duplicate identifier | Create a new form manually with the title and configuration you want instead of renaming the template copy |
| Reviewers see duplicated review criteria or an inflated total score even though the review round and form configuration look correct | Portal site map settings can fall out of sync with review configuration | Rebuild the site map settings from Portal maintenance; this has resolved similar cases even when the round and form setup checked out |
| A configured review-page layout looks blank or is missing fields | Rhythm hides fields that have no value, so an empty-looking layout does not necessarily mean the layout failed | Check whether the fields in question actually have data for that submission before assuming the layout is broken |