Issue
Follow this example that shows how to use the breadcrumb widget. This widget uses an event dispatching system from Angular.
The breadcrumb widget listens on the $rootscope for a widget to broadcast a JSON object following this shaping:
[{label: "label to be displayed", url: "Link relative to the instance"}, {etc}]
If you aren't familiar with the broadcast system from Angular, see Angular Broadcast Documentation.
Resolution
Depending on how you want the breadcrumbs to display and the architecture of your business case, this process may vary.
This example shows the same breadcrumb to your users in their incidents, problems, requests, and so on.
Home > My Stuff > Table Label > Record Number
Here, Home is the index, My Stuff is a custom page that displays a list of my incidents, requests, problems, and other task-related records that you might be able to see.
From there when you select an incident, the breadcrumb on the top of the ticket or request shows the example breadcrumb.
In this case, there is a common widget on the sc_requests and ticket pages: the ticket conversation widget. If you select the widget, you can log $scope.data. This shows you key and value pairs that you can use in your breadcrumb.
If you want the table label and record number, use $scope.data.tableLabel and $scope.data.number respectively.
After identifying the data to use in the breadcrumb, add the following to the ticket conversation widget client script:
// Breadcrumbs
var bc = [{label: 'My Stuff', url: '?id=myStuff'}]; // This would be the pagename, myStuff is an example
if ($scope.data.tableLabel)
bc[bc.length] = {label: $scope.data.tableLabel, url: '#'};
bc[bc.length] = {label: $scope.data.number, url: '#'};
$rootScope.$broadcast('sp.update.breadcrumbs', bc);
}
Here, the code is broadcasting the JSON for what the breadcrumb is waiting to consume. This can be manipulated to create your own breadcrumb path by manipulating the JSON data for your business case.
