Use batch jobs to ingress the source system records to Customer 360. After you import the records to Customer 360, you can process the imported records in Customer 360. Use batch jobs to export the processed records from Customer 360 to the source system.
Predefined jobs of HCO business entity
Use the predefined jobs to integrate data from source systems with Customer 360.
Each job uses a taskflow to run a mapping task. Each mapping task includes a mapping that maps source system fields with the business entity fields. When you run a mapping, the Business 360 FEP connector reads data from or writes data to the Business 360 data store.
The following table describes the predefined jobs and lists their related taskflows, mapping tasks, and mappings to integrate data with Salesforce:
Imports incremental data from the Account Hierarchy in Salesforce into the Salesforce Account Hierarchy asset.
Note: When you export data from Customer 360 to Salesforce, the export job extracts all the data in the first run and only incremental data on subsequent runs.
The following table lists the sample jobs and its related taskflow, mapping task, and mapping to ingress data from NPPES:
Job Name
Taskflow
Mapping Task
Mapping
Description
infac360ls_ingress_nppes_hco_inbound
infac360ls_tf_nppes_hco_inbound
- infac360ls_mt_nppes_hco_inbound_legalName
- infac360ls_mt_nppes_hco_inbound_license
- infac360ls_mt_nppes_hco_inbound_identifier
- infac360ls_mt_nppes_hco_inbound_keyPeople
- infac360ls_mt_nppes_hco_inbound_phone
- infac360ls_mt_nppes_hco_inbound_address
- infac360ls_mt_nppes_hco_inbound_alternateName
- infac360ls_mt_nppes_hco_inbound_specialty
- infac360ls_m_nppes_hco_inbound_legalName
- infac360ls_m_nppes_hco_inbound_license
- infac360ls_m_nppes_hco_inbound_identifier
- infac360ls_m_nppes_hco_inbound_keyPeople
- infac360ls_m_nppes_hco_inbound_phone
- infac360ls_m_nppes_hco_inbound_address
- infac360ls_m_nppes_hco_inbound_alternateName
- infac360ls_m_nppes_hco_inbound_specialty
Imports data from the NPPES file to the HCO business entity.
The following table lists the sample jobs and its related taskflow, mapping task, and mapping to ingress data from MedPro Systems:
Job Name
Taskflow
Mapping Task
Mapping
Description
infac360ls_trigger_ingress_medpro_HCO_HCP
infac360ls_tf_medpro_trigger_inbound_job
- infac360ls_mt_medpro_hco_inbound_root
- infac360ls_mt_medpro_hco_inbound_specialty
- infac360ls_mt_medpro_hco_inbound_alternateName
- infac360ls_mt_medpro_hco_inbound_certification
- infac360ls_mt_medpro_hco_inbound_phone
- infac360ls_mt_medpro_hco_inbound_address
- infac360ls_mt_medpro_hco_inbound_license
- infac360ls_mt_medpro_hco_inbound_sampleability
- infac360ls_mt_medpro_hco_inbound_identifier
- infac360ls_m_medpro_hco_inbound_root
- infac360ls_m_medpro_hco_inbound_specialty
- infac360ls_m_medpro_hco_inbound_alternateName
- infac360ls_m_medpro_hco_inbound_certification
- infac360ls_m_medpro_hco_inbound_phone
- infac360ls_m_medpro_hco_inbound_address
- infac360ls_m_medpro_hco_inbound_license
- infac360ls_m_medpro_hco_inbound_sampleability
- infac360ls_m_medpro_hco_inbound_identifier
Imports data from the response files in the MedPro Systems to the HCO business entity.
infac360ls_egress_medpro_hco_outbound
infac360ls_tf_medPro_hco_outbound
infac360ls_mt_medPro_hco_outbound
infac360ls_m_medPro_hco_outbound
Exports data from the HCO business entity to a request file in MedPro Systems.
Predefined jobs of HCP business entity
Use the predefined jobs to integrate data from source systems with Customer 360.
Each job uses a taskflow to run a mapping task. Each mapping task includes a mapping that maps source system fields with the business entity fields. When you run a mapping, the Business 360 FEP connector reads data from or writes data to the Business 360 data store.
The following table describes the predefined jobs and lists their related taskflows, mapping tasks, and mappings to integrate data with Salesforce:
Exports data from the HCP business entity to the Salesforce Person Accounts object.
Note: When you export data from Customer 360 to Salesforce, the export job extracts all the data in the first run and only incremental data on subsequent runs.
The following table lists the sample jobs and its related taskflow, mapping task, and mapping to ingress data from NPPES:
Job Name
Taskflow
Mapping Task
Mapping
Description
infac360ls_ingress_nppes_hcp_inbound
infac360ls_tf_nppes_hcp_inbound
- infac360ls_mt_nppes_hcp_inbound_legalName
- infac360ls_mt_nppes_hcp_inbound_license
- infac360ls_mt_nppes_hcp_inbound_identifier
- infac360ls_mt_nppes_hcp_inbound_phone
- infac360ls_mt_nppes_hcp_inbound_address
- infac360ls_mt_nppes_hcp_inbound_alternateName
- infac360ls_mt_nppes_hcp_inbound_specialty
- infac360ls_m_nppes_hcp_inbound_legalName
- infac360ls_m_nppes_hcp_inbound_license
- infac360ls_m_nppes_hcp_inbound_identifier
- infac360ls_m_nppes_hcp_inbound_phone
- infac360ls_m_nppes_hcp_inbound_address
- infac360ls_m_nppes_hcp_inbound_alternateName
- infac360ls_m_nppes_hcp_inbound_specialty
Imports data from the NPPES file to the HCP business entity.
The following table lists the sample jobs and its related taskflow, mapping task, and mapping to ingress data from MedPro Systems: