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

[charri04]

Hi @Deepak Shaerma 

Thanks for that suggestion. I'm going to go ahead and provide different names just to help out the admin team troubleshooting any issues.

Best regards, 

Corey

[James Chun]

Hi @charri04,

I would suggest thinking from the users' perspective.

For the users, the item must be easy to find and the name should give a clear indication of what they are requesting.

If you believe the name (e.g. 'Document Request') does its job, I don't think having duplicate names would be a bad thing BUT given that only one item is visible for a party. (e.g. internal employees shouldn't end up finding more than one item with the same name in the ESC portal).

With duplicate names, the admins may find it difficult to find which to work on but there are other fields that can be used to distinguish if it's external facing or internal facing. 

Cheers

[charri04]

Hi @James Chun ,

Thanks for that suggestion. I'm going to go ahead and provide different names just to help out the admin team troubleshooting any issues.

Best regards,

Corey