Taking the Plunge: Migrating Legacy Reader to the Workflow Editor

Tips, Tricks and Code

How to query portfolio items using Configurable Joins (CJs)

Note: These two options produce exactly the same SQL in the background, so there is no efficiency difference. Choose whichever you like best!

Option 1: Subquery Comparison Filter

In a subquery filter, join from Application to Materials. Change the aggregate to comparison. Export the Materials Key and a literal of 'portfolio' and set them to equal each other in the comparison.



Option 2: Formula

In a subquery filter, join from Application to Materials. Change the aggregate to formula. Export the Materials Key and put the following in the formula box:

How to query on a transcript being received after a reader review form was submitted

In order to create this subquery filter, we'll need to find the date that the transcript was received, as well as the date of the reader review form submission. Then, we will compare the two dates.

First, let's set up the comparison in the subquery filter so the dates are nested in the right place for the comparison to work.


Then, we can build out the subquery export for the date that the transcript was received. Since we are on the application base and transcripts are school-scoped materials, we will need to join from Application to Person to Schools to Materials. Also, be sure to sort by created date (descending) so we're sure that we're grabbing the most recently created transcript date. 



Then, we can create the subquery export for the submission date of the reader review form. There are a number of ways you can narrow down to the specific reader review form you're looking for. Below, we're filtering on the scope of Reader, which is the most broad way to do this. However, if you need to, you can instead filter on the titles or folders of specific forms to make sure you're looking at the correct reader review form. Just like above, be sure to sort (descending) by form submission date so you're only pulling the most recently submitted reader review form.



Now, we're ready to finish setting up comparison and save the subquery filter.



If you want to set this up for application-scoped materials instead of school-scoped materials, you'll largely follow the same logic, but instead of joining from Application to Person to Schools to Materials for the transcripts, you will simply join from Application to Materials for the most recently created material date. 

Don't want to build this yourself? Import the Application Query Library in the suitcase above and adjust the filter as needed! 

Understanding Workflow Join Options

Legacy Reader information and New Workflow Editor information does not coexist in the same tables. This means that any configurable joins queries that you have that reference Current Bin, Application Reader Queue, or Bin History will not pull any data about your Workflow (just your Legacy Reader information). This chart shows you equivalencies of Legacy Reader and Workflow Editor joins.



Note that the join from Application to Workflow Bin is a one-to-many join (as denoted by the one-to-many symbol in the join), whereas a join from Application to a specific workflow (e.g. Workflow Records: Scholarship Review) is a one-to-one join. This is because an application can only be in one bin at a time within a single workflow, but an application can be in multiple workflows concurrently.

Code to hide Default Workflow information on app tab

Before:

After:

Go into source code of the application dashboard and add this code:

.dashboard div[style="float: left; margin-bottom: 0; width: 33%;"] {
display: none;
}

Code to hide Default Workflow on app tab (bin structure)

Before:


After:


Go into source code of the application dashboard and add this code:

<style type="text/css">div[style*="margin-top: 10px;"]:first-of-type
{display: none ;}
</style>