Consideration for implementing Record Type
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.
Table of Contents
For records generated by RIO Education UI, introducing a new record type can be a challenge. For example:
In all RIO Education objects, you can introduce a new record type. Here are the considerations before you do so:
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.
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:
- Set a default Record Type per profile so that the existing screen flow can still work, OR,
- Create separate screen flows for each record type to map the field specifically.
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.
Different record types can support different page layouts. Please make sure that you set the fields accordingly based on the record type page layout.
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?
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.