A job profile contains all of the steps needed to complete an individual data import job - field mapping, action, and/or matching. Typically it is easier to think of a job profile "from the bottom up" in the interface and begin by configuring your field mapping profile, then its related action profile, then the match profile if applicable, and finally compiling them into an appropriate job profile.
...
| Info |
|---|
| title | Poppy (R2 2023) Fix Version 2.1.0 |
|---|
|
With the flower released called Poppy, there was the introduction of Profile Wrappers. These wrappers explained in detail in | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MODDICONV-310 |
|---|
|
help maintain the links of profiles in jobs. Before Poppy, some action profiles would disappear from the job or be unlinked or unassociated. For an example of these issues, see | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MODDICONV-361 |
|---|
|
and | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MODDICONV-365 |
|---|
|
. This is work being continued until Ramsons (R2 2024) with | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MODDICONV-312 |
|---|
|
. |