Best practices on naming conventions for record producers

[charri04]

Hello developers,

I have a question around best practices for naming record producers (I know that this should be easy but hear me out). The background story is that I have two separate portals. Portal 1 is the EC Pro Portal (internal facing) and the second portal is the Supplier Collaboration Portal (external facing). I have a record producer, let's call it "Document Request." The "Document Request" record producer will be visible on both portals with the same variables and same processes but its getting created on two different tables. So far, no issues with that.

However, is it best practice to have the same name of a record producer on two different portals (catalogs)? 

Best regards, 

cnharris1

[Brian Lancaster · Accepted solution]

I would suggest different names. It will help you know which one you are working on much quicker if you need to make modification. I know that you could just look at which portal it is on but this would just be an extra layer of protection if you need to add a new field in the table and record producer of the one facing external users.

[charri04]

Hi Brian Lancaster, 

Thanks for that suggestion. I wanted to keep it consistent with the same names from a UI perspective but I agree and think it would help the admin team troubleshoot the record producers easier with different names.

Best regards,

Corey

[Deepak Shaerma]

Hi @charri04 

1. User Experience (UX): From a UX perspective, having the same name for a record producer that performs the same function in different portals can be a good practice. It ensures consistency across your platforms, which helps users who may have access to both portals understand that the “Document Request” feature operates similarly, regardless of where they access it.

2. Backend Clarity: While it makes sense from a user perspective to keep names consistent for similar functions, it’s critical to maintain clarity in the backend configuration. As these record producers are creating records in different tables, you’ll want to ensure that your administrative and development team can easily distinguish between the two when managing the system.

Please mark it helpful and accepted if this helps you in somehow. This will help both community and me.

Thanks and Regards 

Deepak Sharma 

[Brian Lancaster]

I don't think I agree with number 1. Since these are going to 2 different table there may be completely different processes around them. As a user if I had access to both portals I would want to be able to know which one easily is for external vs internal. I know it would be a different URL for each portal but what if I had it in my browser favorites and I click on the wrong one by accident. A different record producer name would help with that.