In the process n_websiteuser_register_new_user_with_status_andcontrollercomponent, we can successfully create new website users. However, we are missing the gender field.
From the front-end perspective, we want to keep it simple: Male, Female, or Unknown.
In the REST process, there is a parameter available called gender, which expects a string.
However, whatever I try — “Man”, “man”, “Men”, “men”, etc. — the gender is not set correctly on the contact (N_person).
I did find an interesting community article: Get request enumeration.
However, I can’t apply an enumeration directly inside a process.
What value is expected in the process for the gender field when creating a contact?
Should I submit an ID, a code, or a specific string value?
So “#1638723e-3aa8-4a34-864c-7e6ec85d0022:getnull()” or “#1638723e-3aa8-4a34-864c-7e6ec85d0022:load(0)” for Male and “#1638723e-3aa8-4a34-864c-7e6ec85d0022:load(1)” for Female
~n_geslacht:load(0) would work as well, and the direct name for gender in you application would too, but that could depend on your integration string.
I can not find the process you talk about in the catalog, so maybe it is componentspecific. Therefor I cannot verify what your process expects as input there. If it expects a Gender enumeration type, what I wrote here should work.
Yes, when there is no parameter for gender, it will not be used in the process. So you’ll have to change your process to add a gender option. Please mind that if this component is more widely in use, that you make the gender option not required or create an extra process that uses the gendered version and let the old process use the new one with a default value for that new required value.
If it is only in use in this application, or in applications you control, you can add dataconversion and a TODO item message for users to remind them and yourself that they need to fix their RESTcalls and workflows processes that use this process.
