Hi @ArunaTunga,
this will be difficult to impossible to achieve... but what you can try is to set the logics on [sys_ui_recent_selection] table where you can see these values from reference fields per user, table and fields:
https://yourinstance.service-now.com/sys_ui_recent_selection_list.do
This is for particular users, not sure if you can use this as a global settings... These are the recent selections per user, so it will vary for most of the profiles. Try to play around with these values, perhaps having a record with empty user would be then applicable for all users (similar to User Preferences) but you must test and validate this... but something like a scratchpad in an onLoad script (to capture logged in user) and glideAjax to update the table with the logged in user in the top...
Another thing would be an attribute in that field's system dictionary. As you want a logged in user to be suggested in the top, then I am worried you will need to do some serious manipulations which I wouldn't recommend you...
When I think about it, perhaps the easiest way would be to set the currently logged in person to the Requested for field and if somebody wants to change it, then they can update it.
What do you say?
The directives used by the variable widgets in the portal use the angular processor com.glide.ui.ng.AngularProcessor (nav_to.do?uri=sys_processor.do?sys_id=87f7ee0147133000ba13a5554ee49005) to interact with the backend. You can observe this from the network tab on your browser devtools while you interact with the requested for variable for example.
It looks like below, payload has things like the table and the query used as an encoded query string
We don't have much control over how the directives work and zero control over how the processor works. The order the results are returned in are baked in. The widget also lazy loads the results so you'll get more results as you scroll down on the dropdown.
I don't recommend this necessarily but it is possible to decorate the oob directives to alter functionality. Here is a demonstration for your requirements. Using a decorator i replaced the filterresults function in the controller of the directive. The new function just pushes the logged in user choice to the top. Of course if the user is not in the first page it will not work until the results/cached array contains the user so it would need to be implemented differently.
// added to catalog item widget as a uiscript js include
angular.module('sn.$sp').config(function ($provide) {
$provide.decorator('spReferenceElementDirective', function ($delegate, $injector) {
var directive = $delegate[0];
var original = directive.controller;
directive.controller = ['$scope', '$rootScope', function ($scope, $rootScope) {
var ctrlInstance = $injector.instantiate(original, {
$scope: $scope,
$rootScope: $rootScope
});
$scope.pageSize = NOW.ac_max_search_matches;
ctrlInstance.filterResults = function (data, page) {
var arr = (data && data.data && Array.isArray(data.data.items))
? data.data.items
: [];
var uid = (window.NOW && NOW.user_id) ? NOW.user_id : null;
if (uid && arr.length) {
var index = arr.findIndex(function (item) {
console.log(item.sys_id)
return item.sys_id === uid;
});
if (index > 0) {
var [match] = arr.splice(index, 1);
arr.unshift(match);
}
}
console.log(arr[0])
return {
results: arr,
more: (page * $scope.pageSize < data.data.total)
};
};
return ctrlInstance;
}]
return $delegate;
})
})In action:
Not quite sure what your requirements are here but you could just add a custom variable with an "add me" button that adds the current user to the requested for.
