Object Configuration

You can configure any custom object to play the role of the Application and you can configure any objects to play the roles of the “RIO”s or Requirement Item objects. For example, you may configure the EDA Application (hed__Application__c) object to play the role of the application and you can configure the EDA Test (hed__Test__c) and Education History (hed__Education_History__c) objects to play the roles of requirement item objects.

There are many permutations of this arrangement. For example:

• You can continue to use the ERx Core Application object (API name EnrollmentrxRx__Enrollment_Opportunity__c), and create new RIOs, for example Work History or Family Members, provided that these objects look up to either the Application or the Contact. You can use a non-ERx object for the application.
• You can use a non-ERx object for the application:
  • You might use either the EDA Application object, the standard Salesforce Opportunity object, or another custom object to play the role of the Application
  • But in that case, you cannot use the three ERx Core RIOs—Education History, Recommendation, and Test Score—because these are in master-detail relationship with the ERx Core Application object (and Salesforce does not allow us to change this)
  • You may, however, in that case, use the ERx Core Admissions Document object as a RIO, because it has only a lookup relationship to the ERx Core Application, and this lookup can be taken out of use and replaced by a new lookup to the new application object

All of the features of ERx Core will work with the objects that you configure to play these roles (of either application or RIO). Those features are: