Hi All,
I know this widget has been brought up many times before, but I haven't found an answer to what I'm trying to do.
We have updated the My Requests page with multiple instances of a modified Simple List widget, one each for the different applications that users could submit tickets for: HR Case, Incident, SC Request, Legal Request, Facilities Request, etc. The idea is to make the data table widget more dynamic, as we have different ticket form pages for certain types. For instance, HR cases load a page called 'hr_case_form' which looks similar to the 'ticket' page, but includes related lists for approvals/tasks. The Requests header menu and the simple list widgets themselves all redirect to the appropriate pages already.
For each of the simple lists, clicking View All will load the mysteriously-hidden "List" page (no idea why 'internal' is checked on that page; just makes it harder to edit) which has nothing but the 'Data Table from URL Definition' widget loaded. There are instance options, but they are set to Incident table with some default fields/columns which seem to be ignored.
Issues
- changing the landing page within the widget code provides inconsistent results
- fields/columns on data table seem to be static, regardless of options chosen
By default, there's a line in the client script for this widget which redirects to the 'form' page when any record is clicked, but there's more to it (line 3 below):
$scope.$on('data_table.click', function(e, parms) {
var oid = $location.search().id;
var p = $scope.data.page_id || 'form';
var s = {id: p, table: parms.table, sys_id: parms.sys_id, view: $scope.data.view};
if (oid == p) {
s.spa = 1;
var t = $location.search();
s = angular.extend(t, s);
$rootScope.$broadcast('$sp.list.click', s);
}
And here's the associated server script for data.page_id. I have no idea what the purpose of this is.
// page is where the record URLs go
var sp_page = $sp.getValue('sp_page');
if (sp_page) {
var pageGR = new GlideRecord('sp_page');
pageGR.get(sp_page);
data.page_id = pageGR.id.getDisplayValue();
}
My Attempts
1. I tried to make this conditional in the server script, but even so, I will still sometimes get the 'form' page when clicking a record. Sometimes the page I want loads just fine. I can't figure out why this isn't consistent. When I used var p='ticket' it seemed to work each time, but I need this to be dynamic. The workaround solution that I'm thinking of is to create new pages for each ticket type and configure a separate instance of this widget for each, so that it can all be hard-coded. I would like to avoid this if possible, mainly because I don't want this to be a need every time we add a new ticket/request type that will need its own landing page for the list/form.
Client script changes:
$scope.$on('data_table.click', function(e, parms) {
var oid = $location.search().id;
//var p = $scope.data.page_id || $scope.data.formPage;
var p = $scope.data.formPage;
Server script addition:
var fp = "";
if ($sp.getParameter('table') == 'hr_case') {
fp = 'hr_case_form';
} else if ($sp.getParameter('table') == 'sc_req_item') {
fp = 'sc_request';
} else {
fp = 'ticket';
}
data.formPage = fp;
2. For the issue with the columns, I tested by creating a new view called 'Portal' and set this in the widget instance, but it did not make any difference. I also added fields directly to the widget instance, but I did not expect any changes there, since the different tables will not all have common fields. Regardless, I still only ever see 4 columns.
Thoughts, experiences, words of wisdom?
