US English (US)
ES Spanish

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Log in
English (US)
US English (US)
ES Spanish
  • Home
  • Help & Support
  • RIO Recipe
  • Build & Implementation

Consideration for implementing Record Type

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • RIO Certification
    RIO Certification Program RIO Academy RIO Challenge RIO Recipe Training
  • Releases
    Release Notes
  • Help & Support
    Install RIO Education RIO Insights RIO Recipe Support
  • About Us
    Who is RIO Education? Start Your RIO Journey Housekeeping
  • Experience RIO in action
+ More

Table of Contents

Considerations Security and permission Screen flow Picklist value Page layout Data migration Conclusions

System-generated records

For records generated by RIO Education UI, introducing a new record type can be a challenge. For example:

  • Course Connection is generated via RIO's Enrollment Wizard.
  • Session Connection is generated via RIO's Enrollment Wizard.
  • Session/Session Time is generated via RIO's Session Scheduler.
 

 

In all RIO Education objects, you can introduce a new record type. Here are the considerations before you do so:

 

Considerations

 

Security and permission

Ensure that the designated users have permission to access to the newly created record type(s). The permission can be granted in profile and/or permission set.

 

Screen flow

Do consider the existing screen flow if you are introducing new record type(s).

For example, if you have a screen flow to create Program Application, and you introduce a new record type, you should either:

  1. Set a default Record Type per profile so that the existing screen flow can still work, OR,
  2. Create separate screen flows for each record type to map the field specifically.

 

Picklist value

Record types support different sets of picklist values. Please check carefully before you introduce a new record type.

For example, if your final success status of a Program Application is set to be ‘Accepted’, you will also need to expose the same picklist value for other record types. If not, the conversion from Program Application > Program Enrollment won't work properly.

 

Page layout

Different record types can support different page layouts. Please make sure that you set the fields accordingly based on the record type page layout.

 

Data migration

Last but not least, have a think about your historical data.

If you introduce a new record type today, consider that there are many records that have been created previously without that new record type. Do you want to migrate them into the correct record type? 

 

Conclusions

What needs to be done is really depending on your requirements. The above advice is just general areas you should consider when you design this.

 

 

record type

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Components in the Admissions process
  • Implementing Program Discipline
RIO Education

RIO Education, a WDCi Company. This information is proprietary, confidential and protected by copyright ©2024.

CONTACT

Get in touch

  • Privacy
  • Terms of service

Knowledge Base Software powered by Helpjuice

Definition by Author

0
0
Expand