Mapping Foundation and CMDB data
This section explains the details of how you can map and load/onboard Foundation and CMDB data from Remedyforce to Helix ITSM using the Data Management console, by downloading and populating data in the data load spreadsheets.
Important
As part of this process, onboarding and/or data loading of CMDB and ITSM Foundation data is supported. Loading of Transactional data is not supported and is not in scope.
Perform the following steps:
Exporting data from Remedyforce system
Export the data to be mapped from Remedyforce system.
Refer to any one of the following methods to export the data:
Include all objects and fields in the export.
Export the data for the following objects:
- Foundation objects:
- Account
- Category
- Group
- User
- CMDB objects:
- BMCServiceDesk__CMDB_Class
- BMCServiceDesk__BMC_BaseElement
- BMCServiceDesk__BMC_BaseRelationship
Use the reports generated for these objects to update the dataload spreadsheets with the correct mapping; see Mapping the Foundation data
Mapping the Foundation data
To load data into the ITSM Foundation forms, you need to populate data to the following dataload spreadsheets. We recommend to load the data by creating a separate job for each of the objects.
- Company
- PeopleOrg
- Location
- OperationalCatalog
- Support_Group
- People
The People spreadsheet contains sheets to populate data and load for People, Support Group Association, Permissions Groups, and Functional Roles. We recommend to load data into those forms in separate jobs and in the following order:
- Populate the CTM:LoadPeople sheet for all non-support staff and load the data.
- After successfully loading the data, populate the CTM:LoadPeople and CTM:LoadSupportGroupAssociation sheets for all support staff and load the data.
- Populate the CTM_LoadPeoplePermissionGroups sheet with Data access permissions for all users.
- Populate the CTM_LoadPeoplePermissionGroups sheet with the Application Permission required for each user.
You may require a few jobs to be run to cover all your users if you have multiple permissions to be given to many of your users. - Finally populate the CTM_LoadSGPFunctionalRole sheet with the functional roles required for your users and load the data.
The following table shows the respective objects in Remedyforce to map the Foundation data to the respective forms in the BMC Helix Innovation Suite Cloud system:
Remedyforce object name | ITSM form name |
---|---|
Account | COM:Company |
Account | CTM:PeopleOrganization |
Account | SIT:Site |
Account | CTM:Region |
Category | CFG:ServiceCatalog |
Group | CTM:SupportGroup |
User | CTM:People |
To map the Foundation data
Perform the steps in the following procedures to map the identified object in Remedyforce to the respective form in BMC Helix Innovation Suite Cloud.
Map Account to Company
Perform the following steps to map the Account object in Remedyforce to Company form of the BMC Helix Innovation Suite Cloud:
- Make sure that the report exported from Remedyforce includes the following fields:
- Account Name
- Remedyforce Account
- Cost Center
- Website
- Populate the spreadsheet accurately to avoid duplicate account name entries.
- In the Company.xlsx spreadsheet, map the data in the following sheets:
- Open the Company.xlsx spreadsheet.
- Open the COM_LoadCompany sheet.
Use the data from the report exported from Remedyforce and map the objects as per the following table:
Important
An asterisk on a field name in the following table indicates that the field is mandatory and it needs to be mapped.
Fields in the
Sheet name: COM_LoadCompanyFields in the
object: AccountMapping Value
Company*
Account Name
Account Name
Type*
Remedyforce Account
If the value of Remedyforce Account field is true, the Type* is Operating Company; otherwise the Type* is Customer.
Cost Center
Cost Center
Cost Center
Web Page
Website
Website
Status*
Inactive
If the value of the Inactive field is false, set the Status* as Enabled; otherwise the Status* is Offline.
Map Account object to CTM:People Organization form
Make sure that the report exported from Remedyforce includes the Inactive field.
Best Practice
We recommend that you load only Active accounts.
- Populate the spreadsheet accurately to avoid duplicate account name entries.
- In the PeopleOrg.xlsx spreadsheet, map the data in the following sheets:
- Open the PeopleOrg.xlsx spreadsheet.
- Open the CTM_LoadPeopleOrganization sheet.
Use the data from the report exported from Remedyforce and map the objects according to the following table:
Important
An asterisk on a field name in the following table indicates that the field is mandatory and it needs to be mapped.
Fields in the
Sheet name: CTM_LoadPeopleOrganizationFields in the
object: AccountMapping value
Company*
Account Name
Account Name
Organization*
Account Name
Account Name
Department*
Account Name
Account Name
Status*
Inactive
If the value of the Inactive field is false, set the Status* as Enabled; otherwise the Status* is Offline.
Map Account object to SIT:Site form
- Make sure that the report exported from Remedyforce includes the following fields:
- Account Name
- Account Description
- Inactive (We recommend loading only active sites)
- Billing Country
- Billing City
- Account Fax
- Billing Street
- Billing Zip/Postal Code
- Billing Country
- Shipping Country
- Shipping State/Province
- Shipping City
- Shipping Street
- Shipping Zip/Postal Code
- Shipping Country
- In the Location.xlsx spreadsheet, map the data in the following sheets:
- Open the Location.xlsx spreadsheet.
- Open the SIT_LoadSite sheet.
Use the data from the report exported from Remedyforce and map the objects as per the following table:
Important
An asterisk on a field name in the following table indicates that the field is mandatory and it needs to be mapped.
Fields in the
Sheet Name: SIT_LoadSiteFields in the
object: AccountMapping Value
Site Name*
Shipping Street
For Shipping Street record, map the value from Shipping Street field
record map value from Billing Street field.
Street
Shipping Street
Billing Street
For Shipping Street record, map value from Shipping Street field
record map value from Billing Street field.
Country*
BillingCountry
ShippingCountry
For Shipping Street record:
For Country*, map the value from the ShippingCountry field. If the value of the ShippingCountry field is empty, specify the Country* as UNKNOWN.
For Billing Street record:
For Country*, map the value from the BillingCountry field. If the value of the BillingCountry field is empty, specify the Country* as UNKNOWN.
State/Province
Shipping State/Province
Billing State/Province
For Shipping Street record, map the value from Shipping State/Province field.
For Billing Street record, map the value from Billing State/Province field.
City*
BillingCity
Shipping City
For Shipping Street record:
For City*, map the value from the ShippingCity field. If the value of the ShippingCity field is empty, specify the City* as UNKNOWN.
For Billing Street record:
For City*, map the value from the BillingCity field. If the value of the BillingCity field is empty, specify the City* as UNKNOWN.
Zip/Postal Code
Shipping Zip/Postal Code
Billing Zip/Postal Code
For Shipping Street record, map the value from Shipping Zip/Postal Code field
For Billing Street record, map the value from Billing Zip/Postal Code field
CC Site Fax
Account Fax
Account Fax
Area Site Fax
Account Fax
Account Fax
Local Site Fax
Account Fax
Account Fax
Additional Site Details
Shipping Street
Billing Street
For Shipping Street record map value from
record map value from Billing Street field
Status*
Inactive
If the value of the Inactive field is false, set the Status* as Enabled; otherwise the Status* is Offline.
- Open the CTM_LoadRegion sheet.
Use the data from the report exported from Remedyforce and map the objects as per the following table:
Fields in the
Sheet name: CTM_LoadRegionFields in the
object: AccountMapping Value
Region*
Constant
Not applicable
Company*
Account Name
Account Name
Status*
Inactive
If the value of the Inactive field is false, set the Status* as Enabled; otherwise the Status* is Offline.
- Open the SIT_LoadSiteGroup sheet.
Use the data from the report exported from Remedyforce and map the objects as per the following table:
Fields in the
Sheet name - SIT_LoadSiteGroupFields in the
object: AccountMapping Value
Site Group*
Constant
“All”
Company*
Account Name
Account Name
Region
Constant
“All”
Description
Account Description
Account Description
Status*
Inactive
If the value of the Inactive field is false, set the Status* as Enabled; otherwise the Status* is Offline.
- Open the SIT_LoadSiteCompanyAssoc sheet.
Use the data from the report exported from Remedyforce and map the objects as per the following table:
Important
An asterisk on a field name in the following table indicates that the field is mandatory and it needs to be mapped.
Fields in the
Sheet name - SIT_LoadSiteCompanyAssocFields in the
object: AccountMapping Value
Site*
Shipping Street
Billing Street
For Shipping Street record, map the value from Shipping Street field
record map value from Billing Street field
Company*
Account Name
Account Name
Region
Constant
All
Site Group
Constant
All
Status*
Inactive
If the value of the Inactive field is false, set the Status* as Enabled; otherwise the Status* is Offline.
Map Category to CFG:Service Catalog
Check the levels of categories stored in the Category fields and map as per the following points:
- If a category value does not have a parent category:
- Map it to Categorization Tier 1* field. Set the Categorization Tier 2 and Categorization Tier 3 fields as NULL.
- If a category value has a parent category and the category value has two levels. For example, “HR-Onboarding - Telecom setup”
- Map the Categorization Tier 1* field as HR-Onboarding
- Categorization Tier 2 field as Telecom setup
- Categorization Tier 3 field as NULL.
- If a category value has a parent category and the category value has three levels. For example, “Client Services-Application-Enhancement”
- Map the Categorization Tier 1* field as Client Services
- Categorization Tier 2 field as Application
- Categorization Tier 3 field as Enhancement.
Perform the following steps to map the Category object in Remedyforce to CTM:People Organization form of the BMC Helix Innovation Suite Cloud:
- Make sure that the report exported from Remedyforce includes the following fields:
- Parent Category
- Category
- Inactive
- In the OperationalCatalog.xlsx spreadsheet, map the data in the following sheets:
- Open the OperationalCatalog.xlsx spreadsheet.
- Open the CFG_LoadServiceCatalogAssoc sheet.
Use the data from the report exported from Remedyforce and map the objects as per the following table:
Important
An asterisk on a field name in the following table indicates that the field is mandatory and it needs to be mapped.
Fields in the
Sheet name: CFG_LoadServiceCatalogAssocFields in the
object: CategoryMapping Value
Company*
Constant
- Global -
Categorization Tier 1*
Category
Based on the levels of categories stored in the Category field
Categorization Tier 2
Category
Based on the levels of categories stored in the Category field
Categorization Tier 3
Category
Based on the levels of categories stored in the Category field
Status*
Inactive
If the value of the Inactive field is false, set the Status* as Enabled; otherwise the Status* is Offline.
- Open the CFG_LoadServiceCatalog sheet.
Use the data from the report exported from Remedyforce and map the objects as per the following table:
Fields in the
Sheet name: CFG_LoadServiceCatalogFields in the
object: CategoryMapping Value
Categorization Tier 1*
Category
Based on levels of categories stored in Category field
Categorization Tier 2
Category
Based on levels of categories stored in Category field
Status*
Inactive
If the value of the Inactive field is false, set the Status* as Enabled; otherwise the Status* is Offline.
Map Group to CTM:Support Group
- Make sure that the report exported from Remedyforce includes the name of the support groups.
- If you have any duplicate account name entries, ensure that you pick the right one to populate the spreadsheet.
- Map the data in the Support_Group.xlsx spreadsheet:
- Open the Support_Group.xlsx spreadsheet.
- Open the CTM_LoadSupportGroup sheet.
Use the data from the report exported from Remedyforce and map the objects as per the following table:
Important
An asterisk on a field name in the following table indicates that the field is mandatory and it needs to be mapped.
Fields in the
Sheet name: CTM_LoadSupportGroupFields in the
object: GroupMapping Value
Support Company*
Enter the value from COM:Company form
Entries in this required field must match a company already loaded in the COM:Company form.
The combination of Support Company, Support Organization, and Support Group Name must be unique.Support Organization*
Enter the value from COM:Company form
NA
Support Group Name*
Name
Support group name extracted from the report.
Support Group Role*
Constant
Help Desk
Vendor Group*
Constant
1
Status*
Constant
1
Disable Group Notifications
Constant
0
Map User to CTM:People form
Perform the following steps to map the User object in Remedyforce to CTM:People form of the BMC Helix Innovation Suite Cloud:
- Make sure that the report exported from Remedyforce includes the following fields:
- Username
- Locale
- Mobile
- Full Name
- Last Name
- FirstName
- Profile
- Account
- Title
- VIP
- Extension
- Fax
- Mobile
- Phone
- Pager
- Time Zone
- IsActive
- Map the data in the People.xlsx spreadsheet:
- Open the People.xlsx spreadsheet.
- Open the CTM_LoadPeople sheet.
Use the data from the report exported from Remedyforce and map the objects as per the following table:
Important
An asterisk on a field name in the following table indicates that the field is mandatory and it needs to be mapped.
Fields in the
Sheet name: CTM_LoadPeopleFields in the
object: UserMapping Value
Last Name*
Last Name
Last Name
First Name*
FirstName
Map the value of the FirstName field. If the FirstName field is empty, enter a dot ".".
Title
Title
Title
Person ID
User ID
User ID
Client Type*
Constant
2000
VIP*
VIP
If the value of the VIP field is true, map to Yes; otherwise map to No.
Client Sensitivity*
Constant
1
Support Staff*
Profile
- If the Profile value is ServiceDesk Staff or ServiceDesk Change Manager, set the Support Staff* to 0.
- If the Profile value is ServiceDesk Client , set the Support Staff* to 1.
Assignment Availability
Use either of the following values.
- 0 — Yes
- 1 — No
This field is required if the Support Staff field is set to Yes. The assignment menu shows the record of the people for whom you have set the assignment availability.
Company*
Account
Entries in this required field must match a company already loaded in the COM:Company form or a company being loaded by the Company.xlsx spreadsheet.
Email Address*
Email
Email
Site
Obtain the value from the SIT:Site form
Entries in this field must match a site already loaded on the SIT:Site form or a site being loaded by the Location spreadsheet.
Important: This field is required if the Client Type is one of the followings:
- Office-Based Employee
- Field-Based Employee
- Contractor
Home Time Zone
Time Zone
Time Zone
CC Mobile
Mobile
Mobile
Area Mobile
Mobile
Mobile
Local Mobile
Mobile
Mobile
CC Business Fax
Fax
Fax
Area Business Fax
Fax
Fax
Local Business Fax
Fax
Fax
CC Pager
Pager
Pager
Area Pager
Pager
Pager
Local Pager
Pager
Pager
Corporate Email
Email
Email
Notification Availability
Constant
0
CC Pager NT
Pager
Pager
Area Pager NT
Pager
Pager
Local Pager NT
Pager
Pager
Login ID
Username
Username
License Type
Select from the following options:
- 0 or Read
- 1 or Fixed
- 2 or Floating
Map the valid values.
Full Text License Type
Select from the following options:
- 0 or Read
- 1 or Fixed
- 2 or Floating
Map the valid values.
Contact Type
Primary
Primary
Profile Status*
IsActive
If the value of the IsActive field is true, set the Profile Status* as Enabled; otherwise the Profile Status* is Offline.
Map GroupMember object to CTM_LoadSupportGroupAssociation form
- Make sure that the report exported from Remedyforce includes the following fields:
- UserOrGroupId
- Group.Name
- Map the data in the People.xlsx spreadsheet)
- Open the People.xlsx spreadsheet.
- Open the CTM_LoadSupportGroupAssociation sheet.
Use the data from the report exported from Remedyforce and map the objects as per the following table:
An asterisk on a field name in the following table indicates that the field is mandatory and it needs to be mapped.
Fields in the
Sheet name: CTM_LoadSupportGroupAssociationFields in the
object: Group MemberMapping Value
Login ID*
UserOrGroupId
UserOrGroupId
Company*
Enter a valid company name.
Entries in this required field must match a company already loaded in the CTM:SupportGroup form or a company being loaded by the SupportGroup.xlsx spreadsheet.
Support Organization*
Enter a valid support organization.
Entries in this required field must match an organization already loaded in the CTM:SupportGroup form or an organization being loaded by the SupportGroup.xlsx spreadsheet.
Support Group*
Group.Name
Group.Name
Support Group Association Role*
Constant
Member
Assignment Availability*
Constant
0
Default*
Select either of the following values:
- 0 — Yes
- 1 — No
For each Login ID, only one support group record can have the default set to Yes.
Map People to permission group
Create required data access and application permissions for the users using CTM_LoadPeoplePermissionGroups sheet. For more information about people permission groups, see Assigning permission groups and permissions on an individual basis in BMC Helix ITSM documentation.
Important
An asterisk on a field name in the following table indicates that the field is mandatory and it needs to be mapped.
Fields in the Sheet name: CTM_LoadPeoplePermissionGroups | Fields in the object: CTM:People | Mapping Value |
---|---|---|
Mapping Value | Login ID | Login ID |
Permission Group* | Enter a valid permission group | When the Permission Group Type field is set to Application Permission, the Permission Group* field must contain a valid permission group from LIC:SYS-License Permission Map form. When the Permission Group Type field is set to Data Access the Permission Group* field must contain a valid company with the either of the following type from the COM:Company form or a company being loaded by the Company.xls spreadsheet:
You can the obtain the Permission Group associated with the company. The workflow automatically creates the corresponding record on the CTM:People Permission Groups form. |
License Type | Enter either of the following values:
| Enter valid values.
|
Permission Group Type* | Enter either of the following values:
| Application Permission is for loading specific application permissions. For example, Incident User, Data Access is for loading Company level permissions. |
Load support group functional roles of the users using CTM_LoadSGPFunctionalRole sheet.
Fields in the Sheet name: CTM_LoadSGPFunctionalRole | Fields in the object: CTM:People | Mapping Value |
---|---|---|
Login ID* | Login ID | Login ID |
Company* | Enter a valid company | Entries in this required field must match a support company already loaded in the CTM:SupportGroup form or a support company being loaded by the SupportGroup.xlsx spreadsheet. |
Support Organization* | Enter a valid organization | Entries in this required field must match a support organization already loaded in the CTM:SupportGroup form or a support organization being loaded by the SupportGroup.xlsx spreadsheet. |
Support Group* | Enter a valid support group | Entries in this required field must match a support group already loaded in the CTM:SupportGroup form or a support group being loaded by the SupportGroup.xlsx spreadsheet. |
Functional Role Alias* | Enter a valid functional role alias. For example:
| Check function role alias header in the CTM_LoadSGPFunctionalRole sheet from the People spreadsheet and map the values. |
Assignment Availability* | Enter either of the values:
| Map the valid values. |
To map the CMDB data
Remedyforce stores all the CMDB data in the following three API objects:
- BMCServiceDesk__CMDB_Class – CMDB_Class maintains the CMDB metadata that contains the class name. The attributes for each class are maintained in the BMC_BaseElement object.
- BMCServiceDesk__BMC_BaseElement – This object contains all the class attributes information for all the CI types supported in Remedyforce.
- BMCServiceDesk__BMC_BaseRelationship – This object contains the relationship information of all the CI types.
All field names in the Remedyforce database will have a prefix of BMCServiceDesk__ and a suffix with __c. In this procedure, we show only the field names that are visible in the Remedyforce UI/label.
For example, the field name ClassID is shown as BMCServiceDesk_ClassID_c in the Remedyforce database.
The following list shows the spreadsheets needed for loading CMDB data:
- Transactional_CI_Express
- Transactional_Asset
Map the BaseElement class to a report
Each CI from Remedyforce will be created as an entry in the corresponding class form in ITSM. The Transactional_CI_Express spreadsheet has different sheets for different classes such as Computer System, Product, Process.
Make sure that the BMCServiceDesk__BMC_BaseElement data exported from Remedyforce includes the following fields:
- ClassID
- Class Name
- Instance Name
- Id
- Serial #
- Supported
- Primary Capability
- Capabilities
- Description
- CITag
- OwnerName
- OwnerContact
- Manufacturer Name
- Site
- CFRM Site Name
- Maximum Block Size
- Licenses Available
In the BMCServiceDesk_CMDB_Class object, identify the class name for each of the following classes.
The following table shows the mapping between the Remedyforce object name, Class Name, and the spreadsheet.Remedyforce object name
CMDB Class Name/AST Class name
Sheet name/Tab name in spreadsheet ‘Transactional_CI_Express.xlsm’
BMC_BaseElement
BMC_BusinessService / AST_BusinessService
AST_BusinessService
BMC_BaseElement
BMC_ComputerSystem / AST _ComputerSystem
AST _ComputerSystem
BMC_BaseElement
BMC_Product / AST _Product
AST _Product
BMC_BaseElement
BMC_Processor / AST _Processor
AST _Processor
BMC_BaseElement
BMC_OperatingSystem / AST _OperatingSystem
AST _OperatingSystem
BMC_BaseElement
BMC_Application / AST _Application
AST _Application
BMC_BaseElement
BMC_Document / AST _Document
AST _Document
BMC_BaseElement
BMC_Database / AST _Database
AST _Database
BMC_BaseElement
BMC_DiskDrive / AST _DiskDrive
AST _DiskDrive
BMC_BaseElement
BMC_Printer / AST _Printer
AST _Printer
BMC_BaseElement
BMC_UPS / AST _UPS
AST _UPS
BMC_BaseElement
BMC_Equipment / AST _Equipment
AST _Equipment
BMC_BaseElement
BMC_Monitor / AST _Monitor
AST _Monitor
BMC_BaseElement
BMC_Rack / AST _Rack
AST _Rack
BMC_BaseElement
BMC_PhysicalLocation / AST _PhysicalLocation
AST _PhysicalLocation
BMC_BaseElement
BMC_FloppyDrive / AST _FloppyDrive
AST _FloppyDrive
BMC_BaseElement
BMC_CDROMDrive / AST _CDROMDrive
AST _CDROMDrive
BMC_BaseElement
BMC_Card / AST _Card
AST _Card
BMC_BaseElement
BMC_FileSystem / AST _FileSystem
AST _FileSystem
- Get the ID value from the BMCServiceDesk_CMDB_Class object for each unique ClassName value.
- Search for the specific class ID in the CMDB_Class field in the BMCServiceDesk__BMC_BaseElement object in Remedyforce.
You will get a list of CIs for the respective class names. - Export all the CI data for each Class separately.
Make sure that you get the data for all the fields mentions in the mapping table below: Populate each sheet of the Transactional_CI_Express spreadsheet and run separate jobs.
For example: Populate the sheet AST:ComputerSystem and run a job to load the data, and once successfully loaded then repeat the steps and load separate jobs for each of the 20 classes.
Use the following table to perform the mappings:Important
An asterisk on a field name in the following table indicates that the field is mandatory and it needs to be mapped.
Fields in the
Spreadsheet name:
Based on Class TypeFields in the object: BaseElement
Mapping value
Class Id*
ClassID
For both the Class ID and Class Name fields in the spreadsheet, you need to populate the class name value from Remedyforce.
CMDB_Class holds a foreign key reference of the Class Name present in the CMDB_Class table.
Enter the class name in CAPITAL letters. For example, if the class name is BMC_Computer_System, enter BMC_COMPUTERSYSTEM.
CI Name*
ClassName
For both the Class ID and Class Name fields in the spreadsheet, you need to populate the class name value from Remedy Force.
This field uses a static value, so the class name is shown in mixed-case capitalization. For example, the Computer System class shows the value as BMC_ComputerSystem
CI Description*
Instance Name
Instance Name
CI ID+
Id(should we mention the ID, I could not find the ID field in RF Base element form)
This field is not visible on Remedyforce UI. This field is exposed only via export.
Status*
CI_Status
Deployed
For this field, populate only the value Deployed for all CIs you are onboarding.
Submitter*
Constant
Remedy login and user name or ID of who is creating the job
Serial Number
Serial #
Serial #
Supported
Supported
Supported
Primary Capability
Primary Capability
Primary Capability
Capabilities
Capabilities
Capabilities
Additional Information
Description
Description
Tag Number
CITag
This field is not visible on Remedyforce UI. This field is exposed only via export.
Owner Name
OwnerName
OwnerName
Owner Contact
OwnerContact
OwnerContact
Manufacturer
Manufacturer Name
Manufacturer Name
Site+
Site
Site
Site Group
CFRM Site Name
CFRM Site Name
Max Block Size
Maximum Block Size
Maximum Block Size
Licenses Available
Licenses Available
Licenses Available
Map the BaseRelationship class to a report
Make sure that the BMCServiceDesk__BaseRelationship data exported from Remedyforce includes the following fields:
- ImpactDirection
- CMDB_Class
- Destination
To export and load the relationship data for each Parent CI name
- Use Parent CI name in a separate job.
- Create spreadsheets for all the Parent CI names available in Remedyforce.
For each Parent CI spreadsheet, map the following fields:
Important
An asterisk on a field name in the following table indicates that the field is mandatory and it needs to be mapped.
Fields in the
Sheet Name: AST_LoadBMC_BaseRelationshipFields in the object - BaseRelationship
Mapping Value
Relationship Type*
ImpactDirection
ImpactDirection
Parent CI Name*
Source
Source
Child CI Name*
Destination
Destination
Parent ClassId*
Source.ClassId
Parent Class Id
For example: AST: Computer system Class Id is "BMC_COMPUTERSYSTEM"Child ClassId*
Destination.ClassId
Child Class Id
For example: AST: Product Class Id is "BMC_PRODUCT"Parent CI Company*
Enter a valid company name
Get the value from Source field and look up the value in the Instance Name field of the Base Element object to identify the CI. Then get the value in Service Provider field of the Base Element object and look up the value in the Account ID field in the Account object to identify the account details. From the account details, complete the corresponding Account Name in the Parent CI Company.
Child CI Company*
Enter a valid company name
Get the value in Destination field and look up the value in the Instance Name field of the Base Element object to identify the CI. Then get the value in Service Provider field of the Base Element object and look up the value in the Account ID field in the Account object to identify the account details. From the account details, complete the corresponding Account Name in the Parent CI Company.
Where to go from here
Go to Stage 6: Data load/Onboarding in the topic Migration process for Remedyforce to BMC Helix Innovation Suite Cloud.
Comments
Log in or register to comment.