You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: fern/docs/pages/airdrop/initial-domain-mapping.mdx
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -100,24 +100,24 @@ You can now use the chef-cli web UI to create initial domain mappings.
100
100
101
101
## Use the local UI to create initial domain mappings
102
102
103
-
The chef-cli UI generates an `initial_domain_mapping.json` file that must be embedded in your extractor. This defines the options that the end-user will see when they are mapping the data.
103
+
The chef-cli UI generates an `initial_domain_mapping.json` file that must be embedded in your extractor. This defines the options that the end-user sees when they are mapping the data.
104
104
105
105
Initial domain mappings differ from user mappings in two key ways:
106
106
107
-
1.**Multiple mapping options**: The developer can choose how external record types map to DevRev records (e.g., external *task* can map to either *issue* or *ticket*).
107
+
1.**Multiple mapping options**: The developer can choose how external record types map to DevRev records (for example, external *task* can map to either *issue* or *ticket*).
108
108
2.**Category-based defaults**: Mappings can apply to entire record type categories, automatically handling new record types.
109
109
110
110
<Steps>
111
111
112
112
### Map record types and fields
113
113
114
114
Use the chef-cli UI to map record types and fields.
115
-
The UI will show you the record types that are available in the org and allow you to map them to the external record types.
115
+
The UI shows you the record types that are available in the org and allows you to map them to the external record types.
116
116
You should map one record type at a time.
117
117
118
118
### Specify fallback mappings
119
119
120
-
For most required DevRev fields we require a fallback. This is used on object creation if the extractor doesn't provide a value.
120
+
For most required DevRev fields a fallback is required. This is used on object creation if the extractor doesn't provide a value.
121
121
122
122
The fallback should be a DevRev value that is valid for the field.
123
123
For enum fields, the fallback should be the enum **value** as specified in [Supported object types](./supported-object-types.mdx).
0 commit comments