@Maik Skoddow: not all variables in record producers should match fields of target table and it’s really important. Usage of variables in multiple record producer allows to save custom information associated with records of target table without extending target tables. For example, one can provides multiple Record Produces for Incident tables with different set to variables. If the user choose specific Category and Subcategory (like Software and Email) one can ask the user for additional set of information (Email address for example) and display the answer in new incident record without expending incident with new field(s). The information will be saved outside of Incident table (in helper tables question_answer, sc_multi_row_question_answer and sc_item_produced_record), but it will be displayed on the corresponding incident record with help of com_glideapp_questionset_default_question_editor Macro used in UI Formatter on the form. It allows to reduce creating custom columns in Incident or other tables and to have flexibly set of additional information (answers) associated and displayed on the form. In my opinion, the way is very important from architecture point of view.
@Sanket Panda: there are exist many ways to implement your requirements, depend on your exact requirements. The most common way would be to place additional sp-variable-editor widget on standard_ticket page. Additionally, you can configure options of the widget to set readonly_variable_editor to true, which would prevent editing of the variables. In JSON form the options would look
{
"readonly_variable_editor": {
"value": "true",
"displayValue": "true"
}
}
Remark: you can edit the standard_ticket page in Designer if you would switch current application to "Service Portal - Standard Ticket" before. After simple modification the old page like
will be change to the following:
