Storing mapping values for a custom application?

[nvali-fsi]

Hello All,

I'm working on building a custom app that integrates to my company's software. At a high-level, when an incident record is created I have a business rule setup to hit our API and create a new record. My question is around storing mapping data and how to best do so.

Specifically, there are certain fields on the incident that I wish to map into fields in our external app. The fields in our app are driven by id's, so if I select a priority of 'High' in snow, I need to send the value of 1 (or whatever ID value is equivalent to the corresponding priority in our app). I was wondering what's the best way to store this information.

Note that we'll have several customers who'd install the custom app from the snow store, each of which could have different id values for various fields in my company's software.

Thanks!

[Ravi Peddineni]

@nvali-fsi 

My suggestion would be to manage the field mappings in the third-party application as you will need to write a huge logic in your script to parse the data as per the third-party application. Maybe you can also use System Property to store the mapping and get the mappings from there in your script. But I strongly suggest you to check the mapping mechanism in your third-party app first.