User Tools

Site Tools


common_request_format

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
common_request_format [2017/12/03 21:59]
paul [Common Request Format]
common_request_format [2019/02/13 22:59]
timothy.pike [Outbound Table Maps]
Line 32: Line 32:
 |psp_group_approval | embedded_group_approval | Group approval [sysapproval_group]| Map for building embedded group approvals| |psp_group_approval | embedded_group_approval | Group approval [sysapproval_group]| Map for building embedded group approvals|
 |psp_recurring_price | embedded_recurring_price | Recurring Price [sc_recurring_rollup]| Map for building embedded recurring prices | |psp_recurring_price | embedded_recurring_price | Recurring Price [sc_recurring_rollup]| Map for building embedded recurring prices |
 +
 +__**NOTE**__**:​** As of the [[https://​doc.perspectium.com/​display/​fluorine|Fluorine release]], the Catalog Task (**sc_task**) table map is included as part of the **Common Request** update set. To learn more about catalog tasks, see [[https://​docs.servicenow.com/​bundle/​madrid-it-service-management/​page/​product/​procurement/​task/​t_ViewAndEditACatalogTask.html|view and edit a catalog task]].
  
 ==== Inbound table Map ==== ==== Inbound table Map ====
Line 80: Line 82:
 {{::​request_attachment_onafter.jpg|}} {{::​request_attachment_onafter.jpg|}}
    
-==== Customer Customization ==== 
-If you are a customer who is installing a common document format update set into your ServiceNow instance, ​ you will want to make a slight change in the import set table'​s transform map in order to properly share records with a MSP gateway ServiceNow instance, ​ 
-  - Open the "PSP Common Request to Request"​ table transform map and then go to the "Field Maps" section 
-  - If a field map with "​u_correlation_id"​ as the source field does not exist, create it as follows:​{{:​psp_common_request_field_map_correlation_id.jpg|}} 
-  - If the u_correlation_id field map does exist, change Coalesce to true 
-  - Change the field map with "​u_number"​ as the source field so Coalesce is false 
-  - Your two field maps for u_correlation_id and u_number should now be as follows:​{{:​correlation_id_number_field_maps.jpg|}} 
-  
-<WRAP center round important 80%> 
-Changing the correlation_id and number transform map field maps is only necessary on the customer ServiceNow instance and not the MSP ServiceNow instance 
-</​WRAP>​ 
- 
-NOTE: The above customization is based on using the record'​s number field as the correlation ID between the customer and provider (i.e. the customer'​s number field will be the correlation ID in the provider instance while the provider'​s number field will be the correlation ID in the customer'​s instance). ​ You can use other fields to correlate instead (such as sys_id) and if you decide to use another field, change both customer and provider table maps and transform maps to use this field where the number field is being used. 
- 
 ==== Sample Output ==== ==== Sample Output ====
  
common_request_format.txt ยท Last modified: 2019/02/13 22:59 by timothy.pike