We are creating an Inbound Web Service that can do 3 things. Create, update and close an Incident. What would best practice be here? Should I create 3 services? Should I create a single Service with 3 transform maps? Should I create a single service with a single TM that covers all situations?
I thought about all situations but all of them had bad points to them. So I thought I'd turn to you guys who are much smarter than me.
1. 3 Services & 3 Transform Maps
+: Easier for the external customer, as the name of the service is clear and they will receive only a single result
-: Double work for field maps/values that are the same for all services
2. 1 Service & 3 Transform Maps
+: Single interface, so customer does not need to worry about what to call
+: Only need maps for those fields that are needed for the current service
-: The external customer will receive the results of 3 TMs
-: All TMs need onBefore maps to check whether they should run
-: Double work for field maps/values that are the same for all services
3. 1 Service & 1 Transform Map
+: Everything is centralized
-: Cannot use coalesce field 'number', because it will not be present when creating a new ticket. This will cause the TM to fail.
PS: As a bonus question, where should I put default values. For example, for the contact_type field, I'd like to enter 'Automated Event', which is not the overal default. Where would I put this assignment? Field Map? Transform Script?
