Business Applications
Enterprise Interactions
Interaction fields and their behaviour
1 min
the following table details the fields available {{ootb}} within servicely's interaction table field label field type field behaviour purpose reference number auto sequence (prefix is int) read only automatically set display value used as a unique reference to an interaction and its display value short description string mandatory the short description is used as the primary classifier source for sofi first contact resolved boolean (radio button) read only automatically set this is automatically set if someone presses the resolve interaction button, rather than the classify interaction button requestor reference (user table) mandatory (if person has no account is no) this holds the person who is requesting the interaction, but does not necessarily mean it has been raised for them requested for reference (user table) mandatory (if person has no account is no) automatically set as requestor if empty this holds the person who the interaction is requested for person has no account boolean this is if the requestor / requested for does not have an account in the system and the name needs to be tracked name of person string mandatory and visible only if person has no account is yes holds the name of the requested for / requestor if they don't have an account location reference (location table) automatically set with requested for's location when requested for changes location must be selectable this is the location that the interaction is for, which can be different to the requestor's and requested for's location phone string either the phone or email needs to be populated before saving automatically set with requested for's mobile phone when requested for changes this is the phone number that should be used as a contact mechanism for this interaction this can be different to the one on the user's record, to help cater for situations where the interaction is about their phone or another mechanism is required to contact the user email string either the phone or email needs to be populated before saving automatically set with requested for's email when requested for changes this is the email that should be used as a contact mechanism for this interaction this can be different to the one on the user's record, to help cater for situations where the interaction is about their email or another mechanism is required to contact the user sla status string read only automatically set based on a combination fields on a primary sla related to this interaction this highlights the status of the primary sla against a record, to ensure that the interaction is being updated in a timely matter work type choice values hr case incident itsm request mandatory this is the table that this interaction will create a record within once it has been resolved or classified this can currently be automatically set by sofi source choice values email phone self service slack virtual agent mandatory automatically set from the source defaults to phone this is the source of the interaction for sources other than phone, for example sofi, it needs to be implemented in the flow rather than assuming what the source of the interaction was attached knowledge reference (knowledge table) read only automatically set when knowledge is attached from sofi this is the knowledge that was attached to the record and as a result was used in the client journal if this knowledge article is related to an open major incident or problem, there will be automated actions based on the major incident or problem process resulting record generic reference read only automatically set when the interaction is resolved or classified this is the record that resulted from the interaction being classified or resolved it's table will be the work type assignment group reference (group table) group must be selectable, have interaction listed in the accessible from table field or the accessible from table field must be empty this is used if an interaction needs to be assigned to a certain group, but does not necessarily need to be set, as the initial interaction with a customer is often a last used to assist with the "interactions assigned to my groups" menu item restricted group multiple reference (group table) group must be selectable, have interaction listed in the accessible from table field or the accessible from table field must be empty this field is used to restrict the visibility of an interaction if a group or multiple group(s) have been entered here, non administrators need to be part of one of the groups to be able to see the interaction description string extra information that can be provided as part of the interaction closure notes string mandatory when an interaction is resolved rather than classified this will be used as the closure notes of the resulting record, if the user resolves an interaction, rather than just classifies it follower multiple reference (user table) this is the list of the followers for an interaction, which will be carried over to the resulting record this is also used to assist with the "interactions i'm following" menu item client journal journal this is the method to communicate with the client or the client to communicate with the service desk via an interaction when a knowledge article is attached from sofi, it will automatically enter this field