Domain can not be changed for record producers (create incident or change)

[vanessaheux]

Hello

I have created record producers to create incident and another to create change request.

All records generated are defined in global domain and I would prefer to have them created in the user’s domain.

I tried to force the domain by a script (even by defining the domain as a constant) in the record producer and also with a variable but even with that, the domain is always global.

All changes and incidents created by users without record producers are defined correctly in the users domain.
How can I manage to force the domain with the value of the user’s domain ?

Regards

Vanessa Heux

[vanessaheux]

I don't mind that the record producer is global by default, but the record producer creates incident or changes and table of incident and changes are domain separated.

As they are domain separated, I would like to have the information that the incident or the change has been created by a someone coming from specific domain.

[Shambhu5]

Hi Vanessaheux,

User Criteria itself is an assurity of that. Since, it will be available for those specifically mentioned Domains only (through criteria), no one else will be able to either see that Producer nor create any. 

So, by default, that Record Producer will search (while inserting) for the Criteria Domain OR the user's Domain and will relatively get Inserted in that particular Domain itself.

Please mark my answer as Correct/Helpful in case that helped.

- Vishrut

[vanessaheux]

Thanks Vishrut but my problem is not that the record producer should be seen or not ny one domain or the other.

My issue is to have the field incident.domain or change_request. domain filled with the real domain of the user and not by global.