✔ Problem with Claimant(s) field
Completed by Morgan M.
- Assigned to
-
Melissa C.
Naomi J.
- Notes
-
Further to the video below, the "Claimant(s)" field in the Disputes form is pulling entries from the People master list. This is a problem, because claimants can be both People and Organizations. The Meta Field Map had directs creating a separate Claimant list, which could be done through Miscellaneous Lists, but this would limit our ability to assign the claimant value a specific nationality. I've suggested in the video that we have the field pull values from both the People and Organizations master lists, and then create a feature that allows the user to add new value to either master list (e.g., "Add new person" and "add new organization"), but I understand if that solution is not technically feasible.
Alternatively, we could create a "Claimant Type" dropdown above the field where the admin user needs to select "People" or "Organization", which would determine the master list tied to the field. Note that this would apply to each instance of the field. Therefore, if the user selects "add another" they would be prompted select "Claimant Type" for the second instance of the field, which could be a different type from the first instances.
Also, because the claimant values will be tied to People or Organizations values, which both contain "Nationality" fields, there is no need for the dependent "Nationality" field under the "Claimant(s)" field, because that data can be pulled from the People or Organizations forms, or the field should be auto-populated with the nationalities already entered for that value.
Further to my call with
Therefore, we need to change the source list for the Claimant(s) field from "People" to "Disputes: Claimant(s)":
However, before we make the change
Does that mean Argentina will be associated specifically with Claimant 1 and Germany with Claimant 2?
We need to confirm this to ensure each claimant value is assigned a nationality for the purposes of the dispute. Note that it's not necessary for the Nationality value to be assigned to the Claimant(s) value across all disputes (i.e., it does not need to be integrated into the miscellaneous list record). We just need to ensure that within the Subscriber reporting tools, the user has the ability to filter disputes by the nationality of the claimants, and that when those filters are activated it will only pull the Claimant(s) values with the selected Nationality value.
For example, if the subscriber selected "Argentina" as the filtered value, would the relationship in the database allow us to show "Claimant 1" as associated with "Argentina", but not "Claimant 2"?
Thanks,
Morgan
While you are doing master entry that time it is not possible to fetch only associated nationality with specific claimants.
For Ex. When you select claimant 1 then all countries you can see in Nationality field.
Once you select any nationality in field and save the master entry that time associated relationship we can build in database.
For ex. Claimant 1
- Argentina
- Canada
- America
Now, when you select any of nationality (Argentina) for claimant 1 and save the master entry that time associated relationship data will be saved into database.
In short, during the data entry you can see all countries in Nationality field and once you associated the nationality field with particular claimants and save the we can make that relationship.
Please confirm.
Morgan
For example, When you select claimant 1 that time you can see all countries in nationality dependent field.
Once you select any nationality and save the master entry then associated relationship will be saved in database.
Hope you are getting what i want to say.
Just to clarify the above; based on a chat with Harsh this morning, the nationality field will pull from ALL nationalities/countries in the application. However once the master list record is saved the nationality data WILL be associated with the Claimant data based on the parent/dependent relationship.
Mel
Understood. That's exactly what I was hoping for. Also, confirming the ability to associated values based on the parent/dependent relationship is an important feature that we'll use for other managed fields.
Thanks,
Morgan
Hope this is fine.
Morgan
Thats why, we will enter 3 new test claimant for your refrence.
Thanks,
Morgan
This change has been done. We pull claimants data from miscellaneous list and nationality data pull from country master.
Morgan