| appid | | user-identities-commonblackcollegeappid | 1 |
| aid | | | 2 |
| coll1 | | | 3 |
| coll2 | | | 4 |
| coll3 | | | 5 |
| coll4 | | | 6 |
| namel | | user-last-name | 7 |
| namef | | user-first-name | 8 |
| namem | | user-middle-name | 9 |
| dob | | user-dob | 10 |
| ssn | | | 11 |
| add | | user-addresses-home-street1 | 12 |
| city | | user-addresses-home-city | 13 |
| state | | user-addresses-home-state | 14 |
| zip | | user-addresses-home-zip | 15 |
| tele | | user-phone-home-number | 16 |
| telecode | | user-phone-home-country-code | 17 |
| gen | If you are using the default Gender data source, you will need to add replace transformation to translate the incoming CBCA code to the SYS Gender list.
If you are using a Regular data source, so one you have created, un-map the field and re-map it so it can properly pick up the RDS you built. Then continue with building the replace transformations if needed.
Below are the CBCA values:
Value in Import | Description
M | Male
F | Female
U | Unknown | user-gender | 18 |
| rela | If you are using the default religion data source, you will need to add replace transformation to translate the incoming CBCA code to the SYS Religion list.
If you are using a Regular data source, so one you have created, un-map the field and re-map it so it can properly pick up the RDS you built. Then continue with building the replace transformations if needed.
Below are the CBCA values:
Value in Import:
Baptist
Methodist
Catholic
Muslim
Other
I prefer not to identify my religious beliefs | user-religion-name | 19 |
| raceth | If you are using the default IPEDS data source, you will need to add replace transformation to translate the incoming CBCA code to the SYS IPEDS list.
If you are using a Regular data source, so one you have created, un-map the field and re-map it so it can properly pick up the RDS you built. Then continue with building the replace transformations if needed.
Below are the CBCA values:
Value in Import:
Black / African American
Asian
Native Hawaiian / Other Pacific Islander
American Indian / Alaska Native
White
Other
I prefer not to identify my race / ethnic background | user-race-categories | 20 |
| mars | If you are using a custom field for marital status of the student, map that field and use the replace transformation using the CBCA values
Below are the CBCA values:
Value in Import | Description
S | Single
M | Married
D | Divorced | | 21 |
| email | | user-email-address | 22 |
| citiz | If you are using the default citizenship status data source, you will need to add replace transformation to translate the incoming CBCA code to the SYS Citizenship Status list.
If you are using a Regular data source, so one you have created, un-map the field and re-map it so it can properly pick up the RDS you built. Then continue with building the replace transformations if needed.
Below are the CBCA values:
Value in Import | Description
US | US Citizen
F | Foreign Citizen
P | Permanent Resident | | 23 |
| visa | | | 24 |
| sem | | | 25 |
| enroll | If you are using the default academic load data source, no further action required!
If you are using a Regular data source, so one you have created, un-map the field and re-map it so it can properly pick up the RDS you built. Then continue with building the replace transformations if needed.
Below are the CBCA values:
Value in Import | Description
P | Part-Time
F | Full-Time | user-education-academic-load | 26 |
| stat | | | 27 |
| yr | | | 28 |
| ff | | | 29 |
| onc | | | 30 |
| hs | | | 31 |
| ceeb | | user-education-schools-ceeb-* | 32 |
| grady | | | 33 |
| coun | | user-education-schools-counselor-first-name-* | 34 |
| gpa | | | 35 |
| act | | | 36 |
| satv | | | 37 |
| satm | | | 38 |
| sats | | | 39 |
| maj | | | 40 |
| collt | | user-education-schools-name-* | 41 |
| cityt | | user-education-schools-city-* | 42 |
| statt | | user-education-schools-state-* | 43 |
| transstart | | user-education-schools-start-* | 44 |
| transstop | | user-education-schools-end-* | 45 |
| felony | | | 46 |
| felony_desc | | | 47 |
| extra | | | 48 |
| fathn | | | 49 |
| addf | | | 50 |
| cityf | | | 51 |
| statef | | | 52 |
| zipf | | | 53 |
| telef | | | 54 |
| telefcode | | | 55 |
| workf | | | 56 |
| workfcode | | | 57 |
| empf | | | 58 |
| titlf | | | 59 |
| mothn | | | 60 |
| addm | | | 61 |
| citym | | | 62 |
| statem | | | 63 |
| zipm | | | 64 |
| telem | | | 65 |
| telemcode | | | 66 |
| workm | | | 67 |
| workmcode | | | 68 |
| empm | | | 69 |
| titlm | | | 70 |
| nameg | | | 71 |
| addg | | | 72 |
| cityg | | | 73 |
| stateg | | | 74 |
| zipg | | | 75 |
| teleg | | | 76 |
| telegcode | | | 77 |
| workg | | | 78 |
| workgcode | | | 79 |
| empg | | | 80 |
| titlg | | | 81 |
| date_added | | | 82 |
| last_update | | | 83 |
| promocode | | | 84 |
| cellph | | user-phone-cell-number | 85 |
| cellphcode | | user-phone-cell-country-code | 86 |
| satw | | | 87 |
| susps | | | 88 |
| jobs | | | 89 |
| hisplat | | user-race-hispanic | 90 |
| collt2 | | user-education-schools-name-* | 91 |
| cityt2 | | user-education-schools-city-* | 92 |
| statt2 | | user-education-schools-state-* | 93 |
| transstart2 | | user-education-schools-start-* | 94 |
| transstop2 | | user-education-schools-end-* | 95 |
| collt3 | | user-education-schools-name-* | 96 |
| cityt3 | | user-education-schools-city-* | 97 |
| statt3 | | user-education-schools-state-* | 98 |
| transstart3 | | user-education-schools-start-* | 99 |
| transstop3 | | user-education-schools-end-* | 100 |
| country_citiz | | user-citizenship-country | 101 |
| country_birth | | user-citizenship-country-of-birth | 102 |
| alien_registration | | | 103 |
| visa_type | | user-citizenship-visa-type | 104 |
| first_gen | | | 105 |
| veteran | | | 106 |
| term | | | 107 |
| utranscripts_uploaded | | | 108 |
| transcripts_uploaded | | | 109 |
| sat_uploaded | | | 110 |
| act_uploaded | | | 111 |
| test_scores_uploaded | | | 112 |
| fatherfn | | | 113 |
| fatherln | | | 114 |
| emailf | | | 115 |
| motherfn | | | 116 |
| motherln | | | 117 |
| guardfn | | | 118 |
| guardln | | | 119 |
| emailm | | | 120 |
| emailg | | | 121 |
| acte | | | 122 |
| actm | | | 123 |
| actr | | | 124 |
| acts | | | 125 |
| names | | | 126 |
| sups_desc | | | 127 |
| country | | | 128 |
| countryf | | | 129 |
| countrym | | | 130 |
| countryg | | | 131 |
| emailc | | user-education-schools-counselor-email-new-* | 132 |
| collt_ceeb | | user-education-schools-ceeb-* | 133 |
| collt2_ceeb | | user-education-schools-ceeb-* | 134 |
| collt3_ceeb | | user-education-schools-ceeb-* | 135 |
| testoptional | | | 136 |
| DOC_ID | | | 137 |
| DOC_TYPE | | | 138 |
| DOC_DESCRIPTION | | | 139 |
| FileName | | | 140 |
| INST_ID | | | 141 |
| SSN | No further action required. This formula makes sure the SSN is valid, if it is invalid, we do not import the value.
IF([C11],IF([C11]="000000000"|[C11]="555555555" | [C11]="123456789" | [C11]="99999" |[C11]="111111111","",IF(LEN([C11])>8,[C11],IF(LEN([C11])<5,"",PAD([C11],"0",9)))),"") | user-ssn | 142 |
| Family 1 Relationship | CBCA separates the family members by relationship whereas Element451 just sorts by position. This formula checks for the presence of a family member and pulls the relationship in the first position.
If you are not using the System Data Source for family relationships, swap out the lowercase relationship with your codes for the relationships.
IF([C49],"father",
IF([C60],"mother",
IF([C71],"guardian",""))) | user-family-guardian-1-relationship | 143 |
| Family 2 Relationship | CBCA separates the family members by relationship whereas Element451 just sorts by position. This formula checks for the presence of a family member and pulls the relationship in the second position.
If you are not using the System Data Source for family relationships, swap out the lowercase relationship with your codes for the relationships.
IF([C49],IF([C60],"mother",IF([C71],"guardian","")),
IF([C60],IF([C71],"guardian",""),"")) | user-family-guardian-2-relationship | 144 |
| Family 1 Address | No further action required. CBCA separates the family members by relationship whereas Element451 just sorts by position. This formula checks for the presence of a family member and pulls the address in the first position.
IF([C49],[C50],
IF([C60],[C61],
IF([C71],[C72],""))) | user-family-guardian-1-address-street-1 | 145 |
| Family 2 Address | No further action required. CBCA separates the family members by relationship whereas Element451 just sorts by position. This formula checks for the presence of a family member and pulls the address in the second position.
IF([C49],IF([C60],[C61],IF([C71],[C72],"")),
IF([C60],IF([C71],[C72],""),"")) | user-family-guardian-2-address-street-1 | 146 |
| Family 1 City | No further action required. CBCA separates the family members by relationship whereas Element451 just sorts by position. This formula checks for the presence of a family member and pulls the city in the first position.
IF([C49],[C51],
IF([C60],[C62],
IF([C71],[C73],""))) | user-family-guardian-1-address-city | 147 |
| Family 2 City | No further action required. CBCA separates the family members by relationship whereas Element451 just sorts by position. This formula checks for the presence of a family member and pulls the city in the second position.
IF([C49],IF([C60],[C62],IF([C71],[C73],"")),
IF([C60],IF([C71],[C73],""),"")) | user-family-guardian-2-address-city | 148 |
| Family 1 State | No further action required. CBCA separates the family members by relationship whereas Element451 just sorts by position. This formula checks for the presence of a family member and pulls the state in the first position.
IF([C49],[C52],
IF([C60],[C63],
IF([C71],[C74],""))) | user-family-guardian-1-address-state | 149 |
| Family 2 State | No further action required. CBCA separates the family members by relationship whereas Element451 just sorts by position. This formula checks for the presence of a family member and pulls the state in the second position.
IF([C48],IF([C57],[C60],IF([C66],[C69],"")),
IF([C57],IF([C66],[C69],""),"")) | user-family-guardian-2-address-state | 150 |
| Family 1 Zip | No further action required. CBCA separates the family members by relationship whereas Element451 just sorts by position. This formula checks for the presence of a family member and pulls the zip code in the first position.
IF([C49],[C53],
IF([C60],[C64],
IF([C71],[C75],""))) | user-family-guardian-1-address-zipcode | 151 |
| Family 2 Zip | No further action required. CBCA separates the family members by relationship whereas Element451 just sorts by position. This formula checks for the presence of a family member and pulls the zip code in the second position.
IF([C49],IF([C60],[C64],IF([C71],[C75],"")),
IF([C60],IF([C71],[C75],""),"")) | user-family-guardian-2-address-zipcode | 152 |
| Family 1 Phone | No further action required. CBCA separates the family members by relationship whereas Element451 just sorts by position. This formula checks for the presence of a family member and pulls the phone number in the first position.
IF([C49],[C54],
IF([C60],[C65],
IF([C71],[C76],""))) | user-family-guardian-phone-1-number | 153 |
| Family 2 Phone | No further action required. CBCA separates the family members by relationship whereas Element451 just sorts by position. This formula checks for the presence of a family member and pulls the phone number in the second position.
IF([C49],IF([C60],[C65],IF([C71],[C76],"")),
IF([C60],IF([C71],[C76],""),"")) | user-family-guardian-phone-2-number | 154 |
| Family 1 Employer | No further action required. CBCA separates the family members by relationship whereas Element451 just sorts by position. This formula checks for the presence of a family member and pulls the employer in the first position.
IF([C49],[C58],
IF([C60],[C69],
IF([C71],[C80],""))) | user-family-guardian-1-employer | 155 |
| Family 2 Employer | No further action required. CBCA separates the family members by relationship whereas Element451 just sorts by position. This formula checks for the presence of a family member and pulls the employer in the second position.
IF([C49],IF([C60],[C69],IF([C71],[C80],"")),
IF([C60],IF([C71],[C80],""),"")) | user-family-guardian-2-employer | 156 |
| Family 1 Occupation | No further action required. CBCA separates the family members by relationship whereas Element451 just sorts by position. This formula checks for the presence of a family member and pulls the occupation in the first position.
IF([C49],[C59],
IF([C60],[C70],
IF([C71],[C81],""))) | user-family-guardian-1-occupation | 157 |
| Family 2 Occupation | No further action required. CBCA separates the family members by relationship whereas Element451 just sorts by position. This formula checks for the presence of a family member and pulls the occupation in the second position.
IF([C49],IF([C60],[C70],IF([C71],[C81],"")),
IF([C60],IF([C71],[C81],""),"")) | user-family-guardian-2-occupation | 158 |
| Family 1 First Name | No further action required. CBCA separates the family members by relationship whereas Element451 just sorts by position. This formula checks for the presence of a family member and pulls the first name in the first position.
IF([C49],[C113],
IF([C60],[C116],
IF([C71],[C118],""))) | user-family-guardian-1-first-name | 159 |
| Family 2 First Name | No further action required. CBCA separates the family members by relationship whereas Element451 just sorts by position. This formula checks for the presence of a family member and pulls the first name in the second position.
IF([C49],IF([C60],[C116],IF([C71],[C118],"")),
IF([C60],IF([C71],[C118],""),"")) | user-family-guardian-2-first-name | 160 |
| Family 1 Last Name | No further action required. CBCA separates the family members by relationship whereas Element451 just sorts by position. This formula checks for the presence of a family member and pulls the last name in the first position.
IF([C49],[C114],
IF([C60],[C117],
IF([C71],[C119],""))) | user-family-guardian-1-last-name | 161 |
| Family 2 Last Name | No further action required. CBCA separates the family members by relationship whereas Element451 just sorts by position. This formula checks for the presence of a family member and pulls the last name in the second position.
IF([C49],IF([C60],[C117],IF([C71],[C119],"")),
IF([C60],IF([C71],[C119],""),"")) | user-family-guardian-2-last-name | 162 |
| Family 1 Email | No further action required. CBCA separates the family members by relationship whereas Element451 just sorts by position. This formula checks for the presence of a family member and pulls the email in the first position while also preventing any bad email values from coming in.
TRIM(IF([C49],IF([C115]="n/a" | [C115]="na" | [C115]="unk","",[C115]),
IF([C60],IF([C120]="n/a" | [C120]="na" | [C120]="unk","",[C120]),
IF([C71],IF([C121]="n/a" | [C121]="na" | [C121]="unk","",[C121]),"")))) | user-family-guardian-email-1 | 163 |
| Family 2 Email | No further action required. CBCA separates the family members by relationship whereas Element451 just sorts by position. This formula checks for the presence of a family member and pulls the email in the second position while also preventing any bad email values from coming in.
IF(TRIM(IF([C49],IF([C60],[C120],IF([C71],[C121],"")),
IF([C60],IF([C71],[C121],""),"")))="n/a","",TRIM(IF([C49],IF([C60],[C120],IF([C71],[C121],"")),
IF([C60],IF([C71],[C121],""),"")))) | user-family-guardian-email-2 | 164 |
| Family 1 Country | No further action required. CBCA separates the family members by relationship whereas Element451 just sorts by position. This formula checks for the presence of a family member and pulls the country in the first position.
IF([C49],[C129],
IF([C60],[C130],
IF([C71],[C131],""))) | user-family-guardian-1-address-country | 165 |
| Family 2 Country | No further action required. CBCA separates the family members by relationship whereas Element451 just sorts by position. This formula checks for the presence of a family member and pulls the country in the second position.
IF([C49],IF([C60],[C130],IF([C71],[C131],"")),
IF([C60],IF([C71],[C131],""),"")) | user-family-guardian-2-address-country | 166 |
| Country of Birth | No further action required. The formula uses DS_MAP to match the incoming country to one listed in the country data source. If there isn’t a match, the value does not get imported.
DS_MAP("data_source.country",[C102],"name","alpha3","") | user-citizenship-country-of-birth | 167 |
| Graduation Date | No further action required. The formula grabs graduation year and glues it onto June 1st. If you don’t want the defaulted graduation date to be June 1st, you would edit the “06/01/” portion.
DATE_READ(CONCAT("06/01/",[C33]),"m/d/Y") | user-education-schools-graduate_date-* | 168 |
| EDIT: SP App Status | Scope:
Select the Application Type that these applications will feed into.
Select the Spring term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
No further action is needed. The formula checks that the term is spring before storing the submitted status.
IF([C25]="S","submitted","") | user-applications-status-* | 169 |
| EDIT: SP App Major | Scope:
Select the Application Type that these applications will feed into.
Select the Spring term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
Depending on how you map the majors from CBCA to Element451 will depend on what your formula looks like. We strongly recommend building a regular data source where column 1 is the CBCA Code, column 2 is the CBCA Name, column 3 is the Element451 major name, and column 4 is the Element451 GUID code. Using a data source that is structured like that, and knowing CBCA sends major as the name (column 2 in the data source) the formula would look like:
IF([C25]="S",DS_MAP([C40],"example.data_source.1234","column_2","column_4",""),"") | user-applications-major-* | 170 |
| EDIT: SP App Term | Scope:
Select the Application Type that these applications will feed into.
Select the Spring term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
How the formula is built assumes you have your terms set up like Spring XXXX in your data sources. CBCA sends terms as Spring XXXX. If your term name structure is different, you’ll update the yellow highlighted portion.
IF([C25]="S",DB_MAP("term",[C107],"name","guid",""),"")
Below are a few examples if your term naming structure is different:
Spring XXXX Semester
CONCAT([C107]," Semester")
January XXXX
CONCAT("January ",LEFT([C107],4))
XXXX Spring
CONCAT(LEFT([C107],4)," Spring") | user-applications-term-* | 171 |
| EDIT: SP App Start Date | Scope:
Select the Application Type that these applications will feed into.
Select the Spring term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
No further action is needed. The formula checks that the term is spring before storing the start date.
IF([C25]="S",DATE_READ([C82],"m/d/Y"),"") | user-applications-registered-at-* | 172 |
| EDIT: SP App Submit Date | Scope:
Select the Application Type that these applications will feed into.
Select the Spring term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
No further action is needed. The formula checks that the term is spring before storing the submit date.
IF([C25]="S",DATE_READ([C83],"m/d/Y"),"") | user-applications-submitted-time-* | 173 |
| EDIT: SP App Student Type | Scope:
Select the Application Type to the application you want to feed into.
Select the Spring term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
The formula for student type is going to vary. You may want everyone to come in as a First-Time Freshman, or you may want to use the CBCA supplied student type field to determine the student type.
If you are wanting every record to come in as the same student type, you’ll put your student type code inside quotes. In the example below, every record will come over as First-Time Freshman if the code in the instance is FTF.
IF([C25]="S","FTF","")
Ultimately, you want the output of your formula to be the codes or values of the student types you use in Element451.
The following are CBCA Student Type values:
F - Freshman;
T - Transfer;
E - Early Admissions;
N - Non-Degree;
D - Dual Enrollment
Below are a few examples of how to use a data source to map student types in:
Using App Type in CBCA and it matches Column 1 in your Regular Data Source for Student Types in Element451DS_MAP([C7],"example.data_source.1234","column_1","column_2","")
Using an IF statement to determine student type:IF([C27]="F","FTF",IF([C27]="T","TR",..."")))))) | user-applications-student-type-* | 174 |
| EDIT: SU App Status | Scope:
Select the Application Type that these applications will feed into.
Select the Summer term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
No further action is needed. The formula checks that the term is summer before storing the submitted status.
IF([C25]="M","submitted","") | user-applications-status-* | 175 |
| EDIT: SU App Major | Scope:
Select the Application Type that these applications will feed into.
Select the Summer term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
Depending on how you map the majors from CBCA to Element451 will depend on what your formula looks like. We strongly recommend building a regular data source where column 1 is the CBCA Code, column 2 is the CBCA Name, column 3 is the Element451 major name, and column 4 is the Element451 GUID code. Using a data source that is structured like that, and knowing CBCA sends major as the name (column 2 in the data source) the formula would look like:
IF([C25]="M",DS_MAP([C40],"example.data_source.1234","column_2","column_4","insert undecided major guid code"),"") | user-applications-major-* | 176 |
| EDIT: SU App Term | Scope:
Select the Application Type that these applications will feed into.
Select the Summer term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
How the formula is built assumes you have your terms set up like Summer XXXX in your data sources. CBCA sends terms as Summer XXXX. If your term name structure is different, you’ll update the yellow highlighted portion.
IF([C25]="M",DB_MAP("term",[C107],"name","guid",""),"")
Below are a few examples if your term naming structure is different:
Summer XXXX Semester
CONCAT([C107]," Semester")
June XXXX
CONCAT("June ",LEFT([C107],4))
XXXX Summer
CONCAT(LEFT([C107],4)," Summer") | user-applications-term-* | 177 |
| EDIT: SU App Start Date | Scope:
Select the Application Type that these applications will feed into.
Select the Summer term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
No further action is needed. The formula checks that the term is summer before storing the start date.
IF([C25]="M",DATE_READ([C82],"m/d/Y"),"") | user-applications-registered-at-* | 178 |
| EDIT: SU App Submit Date | Scope:
Select the Application Type that these applications will feed into.
Select the Summer term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
No further action is needed. The formula checks that the term is summer before storing the submit date.
IF([C25]="M",DATE_READ([C83],"m/d/Y"),"") | user-applications-submitted-time-* | 179 |
| EDIT: SU App Student Type | Scope:
Select the Application Type to the application you want to feed into.
Select the Summer term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
The formula for student type is going to vary. You may want everyone to come in as a First-Time Freshman, or you may want to use the CBCA supplied student type field to determine the student type.
If you are wanting every record to come in as the same student type, you’ll put your student type code inside quotes. In the example below, every record will come over as First-Time Freshman if the code in the instance is FTF.
IF([C25]="M","FTF","")
Ultimately, you want the output of your formula to be the codes or values of the student types you use in Element451.
The following are CBCA Student Type values:
F - Freshman;
T - Transfer;
E - Early Admissions;
N - Non-Degree;
D - Dual Enrollment
Below are a few examples of how to use a data source to map student types in:
Using App Type in CBCA and it matches Column 1 in your Regular Data Source for Student Types in Element451DS_MAP([C7],"example.data_source.1234","column_1","column_2","")
Using an IF statement to determine student type:IF([C27]="F","FTF",
IF([C27]="T","TR",..."")))))) | user-applications-student-type-* | 180 |
| EDIT: FA App Status | Scope:
Select the Application Type that these applications will feed into.
Select the Fall term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
No further action is needed. The formula checks that the term is fall before storing the submitted status.
IF([C25]="F","submitted","") | user-applications-status-* | 181 |
| EDIT: FA App Major | Scope:
Select the Application Type that these applications will feed into.
Select the Fall term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
Depending on how you map the majors from CBCA to Element451 will depend on what your formula looks like. We strongly recommend building a regular data source where column 1 is the CBCA Code, column 2 is the CBCA Name, column 3 is the Element451 major name, and column 4 is the Element451 GUID code. Using a data source that is structured like that, and knowing CBCA sends major as the name (column 2 in the data source) the formula would look like:
IF([C25]="F",DS_MAP([C40],"example.data_source.1234","column_2","column_4","insert undecided major guid code"),"") | user-applications-major-* | 182 |
| EDIT: FA App Term | Scope:
Select the Application Type that these applications will feed into.
Select the Fall term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
How the formula is built assumes you have your terms set up like Fall XXXX in your data sources. CBCA sends terms as Fall XXXX. If your term name structure is different, you’ll update the yellow highlighted portion.
IF([C25]="F",DB_MAP("term",[C107],"name","guid",""),"")
Below are a few examples if your term naming structure is different:
Fall XXXX Semester
CONCAT([C107]," Semester")
August XXXX
CONCAT("August ",LEFT([C107],4))
XXXX Fall
CONCAT(LEFT([C107],4)," Fall") | user-applications-term-* | 183 |
| EDIT: FA App Start Date | Scope:
Select the Application Type that these applications will feed into.
Select the Fall term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
No further action is needed. The formula checks that the term is fall before storing the start date.
IF([C25]="S",DATE_READ([C82],"m/d/Y"),"") | user-applications-registered-at-* | 184 |
| EDIT: FA App Submit Date | Scope:
Select the Application Type that these applications will feed into.
Select the Fall term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
No further action is needed. The formula checks that the term is fall before storing the submit date.
IF([C25]="F",DATE_READ([C83],"m/d/Y"),"") | user-applications-submitted-time-* | 185 |
| EDIT: FA App Student Type | Scope:
Select the Application Type to the application you want to feed into.
Select the Fall term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
The formula for student type is going to vary. You may want everyone to come in as a First-Time Freshman, or you may want to use the CBCA supplied student type field to determine the student type.
If you are wanting every record to come in as the same student type, you’ll put your student type code inside quotes. In the example below, every record will come over as First-Time Freshman if the code in the instance is FTF.
IF([C25]="F","FTF","")
Ultimately, you want the output of your formula to be the codes or values of the student types you use in Element451.
The following are CBCA Student Type values:
F - Freshman;
T - Transfer;
E - Early Admissions;
N - Non-Degree;
D - Dual Enrollment
Below are a few examples of how to use a data source to map student types in:
Using App Type in CBCA and it matches Column 1 in your Regular Data Source for Student Types in Element451DS_MAP([C7],"example.data_source.1234","column_1","column_2","")
Using an IF statement to determine student type:
IF([C27]="F","FTF",
IF([C27]="T","TR",..."")))))) | user-applications-student-type-* | 186 |
| EDIT: SP App Start Milestone Date | Scope:
Select the Milestone Type to be Application Start Date.
Select the Spring term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
No further action is needed. The formula checks that the term is spring before storing the start date.
IF([C25]="S",DATE_READ([C82],"m/d/Y"),"") | user-milestones-date-* | 187 |
| EDIT: SP App Start Milestone GUID | Scope:
Select the Milestone Type to Application Start Date.
Select the Spring term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
The formula will be the application GUID you are feeding the applicants into. You can find the application GUID by going into the application in your Element451 like you are about to edit it and pull from the url.
IF([C25]="S","example.applications.12345","") | user-milestones-application-guid-* | 188 |
| EDIT: SP App Start Milestone Term | Scope:
Select the Milestone Type to be Application Start Date.
Select the Spring term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
How the formula is built assumes you have your terms set up like Spring XXXX in your data sources. CBCA sends terms as Spring XXXX. If your term name structure is different, you’ll update the yellow highlighted portion.
IF([C25]="S",DB_MAP("term",[C107],"name","guid",""),"")
Below are a few examples if your term naming structure is different:
Spring XXXX Semester
CONCAT([C107]," Semester")
January XXXX
CONCAT("January ",LEFT([C107],4))
XXXX Spring
CONCAT(LEFT([C107],4)," Spring") | user-milestones-term-* | 189 |
| EDIT: SP App Start Milestone Major | Scope:
Select the Milestone Type of Application Start Date.
Select the Spring term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
Depending on how you map the majors from CBCA to Element451 will depend on what your formula looks like. We strongly recommend building a regular data source where column 1 is the CBCA Code, column 2 is the CBCA Name, column 3 is the Element451 major name, and column 4 is the Element451 GUID code. Using a data source that is structured like that, and knowing CBCA sends major as the name (column 2 in the data source) the formula would look like:
IF([C25]="S",DS_MAP([C40],"example.data_source.1234","column_2","column_4","insert undecided major guid code"),"") | user-milestones-major-* | 190 |
| EDIT: SP App Start Milestone Student Type | Scope:
Select the Milestone Type into Application Start Date.
Select the Spring term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
The formula for student type is going to vary. You may want everyone to come in as a First-Time Freshman, or you may want to use the CBCA supplied student type field to determine the student type.
If you are wanting every record to come in as the same student type, you’ll put your student type code inside quotes. In the example below, every record will come over as First-Time Freshman if the code in the instance is FTF.
IF([C25]="S","FTF","")
Ultimately, you want the output of your formula to be the codes or values of the student types you use in Element451.
The following are CBCA Student Type values:
F - Freshman;
T - Transfer;
E - Early Admissions;
N - Non-Degree;
D - Dual Enrollment
Below are a few examples of how to use a data source to map student types in:
Using App Type in CBCA and it matches Column 1 in your Regular Data Source for Student Types in Element451DS_MAP([C7],"example.data_source.1234","column_1","column_2","")
Using an IF statement to determine student type:
IF([C27]="F","FTF",
IF([C27]="T","TR",..."")))))) | user-milestones-student_type-* | 191 |
| EDIT: SP App Submit Milestone Date | Scope:
Select the Milestone Type to be Application Submit Date.
Select the Spring term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
No further action is needed. The formula checks that the term is spring before storing the submit date.
IF([C25]="S",DATE_READ([C83],"m/d/Y"),"") | user-milestones-date-* | 192 |
| EDIT: SP App Submit Milestone GUID | Scope:
Select the Milestone Type to Application Submit Date.
Select the Spring term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
The formula will be the application GUID you are feeding the applicants into. You can find the application GUID by going into the application in your Element451 like you are about to edit it and pull from the url.
IF([C25]="S","example.applications.12345","") | user-milestones-application-guid-* | 193 |
| EDIT: SP App Submit Milestone Term | Scope:
Select the Milestone Type to be Application Submit Date.
Select the Spring term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
How the formula is built assumes you have your terms set up like Spring XXXX in your data sources. CBCA sends terms as Spring XXXX. If your term name structure is different, you’ll update the yellow highlighted portion.
IF([C25]="S",DB_MAP("term",[C107],"name","guid",""),"")
Below are a few examples if your term naming structure is different:
Spring XXXX Semester
CONCAT([C107]," Semester")
January XXXX
CONCAT("January ",LEFT([C107],4))
XXXX Spring
CONCAT(LEFT([C107],4)," Spring") | user-milestones-term-* | 194 |
| EDIT: SP App Submit Milestone Major | Scope:
Select the Milestone Type of Application Submit Date.
Select the Spring term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
Depending on how you map the majors from CBCA to Element451 will depend on what your formula looks like. We strongly recommend building a regular data source where column 1 is the CBCA Code, column 2 is the CBCA Name, column 3 is the Element451 major name, and column 4 is the Element451 GUID code. Using a data source that is structured like that, and knowing CBCA sends major as the name (column 2 in the data source) the formula would look like:
IF([C25]="S",DS_MAP([C40],"example.data_source.1234","column_2","column_4","insert undecided major guid code"),"") | user-milestones-major-* | 195 |
| EDIT: SP App Submit Milestone Student Type | Scope:
Select the Milestone Type into Application Submit Date.
Select the Spring term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
The formula for student type is going to vary. You may want everyone to come in as a First-Time Freshman, or you may want to use the CBCA supplied student type field to determine the student type.
If you are wanting every record to come in as the same student type, you’ll put your student type code inside quotes. In the example below, every record will come over as First-Time Freshman if the code in the instance is FTF.
IF([C25]="S","FTF","")
Ultimately, you want the output of your formula to be the codes or values of the student types you use in Element451.
The following are CBCA Student Type values:
F - Freshman;
T - Transfer;
E - Early Admissions;
N - Non-Degree;
D - Dual Enrollment
Below are a few examples of how to use a data source to map student types in:
Using App Type in CBCA and it matches Column 1 in your Regular Data Source for Student Types in Element451DS_MAP([C7],"example.data_source.1234","column_1","column_2","")
Using an IF statement to determine student type:IF([C27]="F","FTF",IF([C27]="T","TR",..."")))))) | user-milestones-student_type-* | 196 |
| EDIT: SU App Start Milestone Date | Scope:
Select the Milestone Type to be Application Start Date.
Select the Summer term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
No further action is needed. The formula checks that the term is summer before storing the start date.
IF([C25]="M",DATE_READ([C82],"m/d/Y"),"") | user-milestones-date-* | 197 |
| EDIT: SU App Start Milestone GUID | Scope:
Select the Milestone Type to Application Start Date.
Select the Summer term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
The formula will be the application GUID you are feeding the applicants into. You can find the application GUID by going into the application in your Element451 like you are about to edit it and pull from the url.
IF([C25]="M","example.applications.12345","") | user-milestones-application-guid-* | 198 |
| EDIT: SU App Start Milestone Term | Scope:
Select the Milestone Type to be Application Start Date.
Select the Summer term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
How the formula is built assumes you have your terms set up like Summer XXXX in your data sources. CBCA sends terms as Summer XXXX. If your term name structure is different, you’ll update the yellow highlighted portion.
IF([C25]="M",DB_MAP("term",[C107],"name","guid",""),"")
Below are a few examples if your term naming structure is different:
Summer XXXX Semester
CONCAT([C107]," Semester")
June XXXX
CONCAT("June ",LEFT([C107],4))
XXXX Summer
CONCAT(LEFT([C107],4)," Summer") | user-milestones-term-* | 199 |
| EDIT: SU App Start Milestone Major | Scope:
Select the Milestone Type of Application Start Date.
Select the Summer term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
Depending on how you map the majors from CBCA to Element451 will depend on what your formula looks like. We strongly recommend building a regular data source where column 1 is the CBCA Code, column 2 is the CBCA Name, column 3 is the Element451 major name, and column 4 is the Element451 GUID code. Using a data source that is structured like that, and knowing CBCA sends major as the name (column 2 in the data source) the formula would look like:
IF([C25]="M",DS_MAP([C40],"example.data_source.1234","column_2","column_4","insert undecided major guid code"),"") | user-milestones-major-* | 200 |
| EDIT: SU App Start Milestone Student Type | Scope:
Select the Milestone Type into Application Start Date.
Select the Summer term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
The formula for student type is going to vary. You may want everyone to come in as a First-Time Freshman, or you may want to use the CBCA supplied student type field to determine the student type.
If you are wanting every record to come in as the same student type, you’ll put your student type code inside quotes. In the example below, every record will come over as First-Time Freshman if the code in the instance is FTF.
IF([C25]="M","FTF","")
Ultimately, you want the output of your formula to be the codes or values of the student types you use in Element451.
The following are CBCA Student Type values:
F - Freshman;
T - Transfer;
E - Early Admissions;
N - Non-Degree;
D - Dual Enrollment
Below are a few examples of how to use a data source to map student types in:
Using App Type in CBCA and it matches Column 1 in your Regular Data Source for Student Types in Element451DS_MAP([C7],"example.data_source.1234","column_1","column_2","")
Using an IF statement to determine student type:IF([C27]="F","FTF",
IF([C27]="T","TR",..."")))))) | user-milestones-student_type-* | 201 |
| EDIT: SU App Submit Milestone Date | Scope:
Select the Milestone Type to be Application Submit Date.
Select the Summer term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
No further action is needed. The formula checks that the term is summer before storing the submit date.
IF([C25]="M",DATE_READ([C83],"m/d/Y"),"") | user-milestones-date-* | 202 |
| EDIT: SU App Submit Milestone GUID | Scope:
Select the Milestone Type to Application Submit Date.
Select the Summer term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
The formula will be the application GUID you are feeding the applicants into. You can find the application GUID by going into the application in your Element451 like you are about to edit it and pull from the url.
IF([C25]="M","example.applications.12345","") | user-milestones-application-guid-* | 203 |
| EDIT: SU App Submit Milestone Term | Scope:
Select the Milestone Type to be Application Submit Date.
Select the Summer term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
How the formula is built assumes you have your terms set up like Summer XXXX in your data sources. CBCA sends terms as Summer XXXX. If your term name structure is different, you’ll update the yellow highlighted portion.
IF([C25]="S",DB_MAP("term",[C107],"name","guid",""),"")
Below are a few examples if your term naming structure is different:
Summer XXXX Semester
CONCAT([C107]," Semester")
June XXXX
CONCAT("June ",LEFT([C107],4))
XXXX Summer
CONCAT(LEFT([C107],4)," Summer") | user-milestones-term-* | 204 |
| EDIT: SU App Submit Milestone Major | Scope:
Select the Milestone Type of Application Submit Date.
Select the Summer term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
Depending on how you map the majors from CBCA to Element451 will depend on what your formula looks like. We strongly recommend building a regular data source where column 1 is the CBCA Code, column 2 is the CBCA Name, column 3 is the Element451 major name, and column 4 is the Element451 GUID code. Using a data source that is structured like that, and knowing CBCA sends major as the name (column 2 in the data source) the formula would look like:
IF([C25]="M",DS_MAP([C40],"example.data_source.1234","column_2","column_4","insert undecided major guid code"),"") | user-milestones-major-* | 205 |
| EDIT: SU App Submit Milestone Student Type | Scope:
Select the Milestone Type into Application Submit Date.
Select the Summer term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
The formula for student type is going to vary. You may want everyone to come in as a First-Time Freshman, or you may want to use the CBCA supplied student type field to determine the student type.
If you are wanting every record to come in as the same student type, you’ll put your student type code inside quotes. In the example below, every record will come over as First-Time Freshman if the code in the instance is FTF.
IF([C25]="M","FTF","")
Ultimately, you want the output of your formula to be the codes or values of the student types you use in Element451.
The following are CBCA Student Type values:
F - Freshman;
T - Transfer;
E - Early Admissions;
N - Non-Degree;
D - Dual Enrollment
Below are a few examples of how to use a data source to map student types in:
Using App Type in CBCA and it matches Column 1 in your Regular Data Source for Student Types in Element451DS_MAP([C7],"example.data_source.1234","column_1","column_2","")
Using an IF statement to determine student type:
IF([C27]="F","FTF",IF([C27]="T","TR",..."")))))) | user-milestones-student_type-* | 206 |
| EDIT: FA App Start Milestone Date | Scope:
Select the Milestone Type to be Application Start Date.
Select the Fall term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
No further action is needed. The formula checks that the term is fall before storing the start date.
IF([C25]="S",DATE_READ([C82],"m/d/Y"),"") | user-milestones-date-* | 207 |
| EDIT: FA App Start Milestone GUID | Scope:
Select the Milestone Type to Application Start Date.
Select the Fall term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
The formula will be the application GUID you are feeding the applicants into. You can find the application GUID by going into the application in your Element451 like you are about to edit it and pull from the url.
IF([C25]="F","example.applications.12345","") | user-milestones-application-guid-* | 208 |
| EDIT: FA App Start Milestone Term | Scope:
Select the Milestone Type to be Application Start Date.
Select the Fall term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
How the formula is built assumes you have your terms set up like Fall XXXX in your data sources. CBCA sends terms as Fall XXXX. If your term name structure is different, you’ll update the yellow highlighted portion.
IF([C25]="F",DB_MAP("term",[C107],"name","guid",""),"")
Below are a few examples if your term naming structure is different:
Fall XXXX Semester
CONCAT([C107]," Semester")
August XXXX
CONCAT("August ",LEFT([C107],4))
XXXX Fall
CONCAT(LEFT([C107],4)," Fall") | user-milestones-term-* | 209 |
| EDIT: FA App Start Milestone Major | Scope:
Select the Milestone Type of Application Start Date.
Select the Fall term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
Depending on how you map the majors from CBCA to Element451 will depend on what your formula looks like. We strongly recommend building a regular data source where column 1 is the CBCA Code, column 2 is the CBCA Name, column 3 is the Element451 major name, and column 4 is the Element451 GUID code. Using a data source that is structured like that, and knowing CBCA sends major as the name (column 2 in the data source) the formula would look like:
IF([C25]="F",DS_MAP([C40],"example.data_source.1234","column_2","column_4","insert undecided major guid code"),"") | user-milestones-major-* | 210 |
| EDIT: FA App Start Milestone Student Type | Scope:
Select the Milestone Type into Application Start Date.
Select the Fall term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
The formula for student type is going to vary. You may want everyone to come in as a First-Time Freshman, or you may want to use the CBCA supplied student type field to determine the student type.
If you are wanting every record to come in as the same student type, you’ll put your student type code inside quotes. In the example below, every record will come over as First-Time Freshman if the code in the instance is FTF.
IF([C25]="F","FTF","")
Ultimately, you want the output of your formula to be the codes or values of the student types you use in Element451.
The following are CBCA Student Type values:
F - Freshman;
T - Transfer;
E - Early Admissions;
N - Non-Degree;
D - Dual Enrollment
Below are a few examples of how to use a data source to map student types in:
Using App Type in CBCA and it matches Column 1 in your Regular Data Source for Student Types in Element451DS_MAP([C7],"example.data_source.1234","column_1","column_2","")
Using an IF statement to determine student type:
IF([C27]="F","FTF",IF([C27]="T","TR",..."")))))) | user-milestones-student_type-* | 211 |
| EDIT: FA App Submit Milestone Date | Scope:
Select the Milestone Type to be Application Submit Date.
Select the Fall term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
No further action is needed. The formula checks that the term is fall before storing the submit date.
IF([C25]="F",DATE_READ([C83],"m/d/Y"),"") | user-milestones-date-* | 212 |
| EDIT: FA App Submit Milestone GUID | Scope:
Select the Milestone Type to Application Submit Date.
Select the Fall term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
The formula will be the application GUID you are feeding the applicants into. You can find the application GUID by going into the application in your Element451 like you are about to edit it and pull from the url.
IF([C25]="F","example.applications.12345","") | user-milestones-application-guid-* | 213 |
| EDIT: FA App Submit Milestone Term | Scope:
Select the Milestone Type to be Application Submit Date.
Select the Fall term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
How the formula is built assumes you have your terms set up like Fall XXXX in your data sources. CBCA sends terms as Fall XXXX. If your term name structure is different, you’ll update the yellow highlighted portion.
IF([C25]="F",DB_MAP("term",[C107],"name","guid",""),"")
Below are a few examples if your term naming structure is different:
Fall XXXX Semester
CONCAT([C107]," Semester")
August XXXX
CONCAT("August ",LEFT([C107],4))
XXXX Fall
CONCAT(LEFT([C107],4)," Fall") | user-milestones-term-* | 214 |
| EDIT: FA App Submit Milestone Major | Scope:
Select the Milestone Type of Application Submit Date.
Select the Fall term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
Depending on how you map the majors from CBCA to Element451 will depend on what your formula looks like. We strongly recommend building a regular data source where column 1 is the CBCA Code, column 2 is the CBCA Name, column 3 is the Element451 major name, and column 4 is the Element451 GUID code. Using a data source that is structured like that, and knowing CBCA sends major as the name (column 2 in the data source) the formula would look like:
IF([C25]="F",DS_MAP([C40],"example.data_source.1234","column_2","column_4","insert undecided major guid code"),"") | user-milestones-major-* | 215 |
| EDIT: FA App Submit Milestone Student Type | Scope:
Select the Milestone Type into Application Submit Date.
Select the Fall term from the drop down for the current cycle. This field will need to be updated every year when it is time for the next cycle to open up.
Formula:
The formula for student type is going to vary. You may want everyone to come in as a First-Time Freshman, or you may want to use the CBCA supplied student type field to determine the student type.
If you are wanting every record to come in as the same student type, you’ll put your student type code inside quotes. In the example below, every record will come over as First-Time Freshman if the code in the instance is FTF.
IF([C25]="F","FTF","")
Ultimately, you want the output of your formula to be the codes or values of the student types you use in Element451.
The following are CBCA Student Type values:
F - Freshman;
T - Transfer;
E - Early Admissions;
N - Non-Degree;
D - Dual Enrollment
Below are a few examples of how to use a data source to map student types in:
Using App Type in CBCA and it matches Column 1 in your Regular Data Source for Student Types in Element451DS_MAP([C7],"example.data_source.1234","column_1","column_2","")
Using an IF statement to determine student type:IF([C27]="F","FTF",
IF([C27]="T","TR",..."")))))) | user-milestones-student_type-* | 216 |
| EDIT: Labels | Here is where you can add any labels you want to the profiles. If you are wanting these applications moved to decisions, following the Move Application to Decisions instructions, we’ll want to add the label that triggers the rule in this formula. You can also add any other labels you use.
For importing one label:"example.taxonomy.12345"
For importing more labels:"example.taxonomy.12345,example.taxonomy.67890,example.taxonomy.11111" | user-labels-import | 217 |
| Source Date | No further edits on this formula. I pulls the submit date for the source.
DATE_READ([C82],"m/d/Y") | user-sources-source-code-date | 218 |
| EDIT: Source Code | If you want to add an CBCA source to the records as they come in, make sure you create the source under Contacts>Categories>Source Codes. Copy the taxonomy code from there and paste inside quotes.
"example.taxonomy.1234" | user-sources-source-code | 219 |