What is componentOccurence in the wayfinding widget and how do I programmatically access it?

I checked it further:

- when the waypoint element is already created in UI it has the properties Component Occurrence - internal as  "component-occurrence" and Model Widget ID  internal as 'model' what in that case  the UI will set when you add the waypoints via UI. Later you can get or set that properties on run time. My observation is that this has only infomrative meaning - so you can use it later to create an selection of the item. I could not see that it did some highliting on naivigating to waypoint but possibly I overlooked something.

Highlighting could be implemeted , no issue

But when you try to create the way points dynamicaly you can use the data , (not supported at all ) Such apprauch will work  but it will ingorre the both properties occurance and modelWidget id. When I set it in the data and print the data later then it will omit the both properites.

in my test

 $scope.app.waypointsElementAdd ({"x":(center.x+mod.x),"y":(center.y+mod.y),"z":(center.z+mod.z)},{"x":0,"y":0,"z":-1},{"x":0,"y":1,"z":0},0.2,0.3,
 "WPN_"+(metadata.get(element, 'Display Name')).toString()+"-"+element.toString()); 
// versus setting of the both additional properties
$scope.app.waypointsElementAdd2 ({"x":(center.x+mod.x),"y":(center.y+mod.y),"z":(center.z+mod.z)},{"x":0,"y":0,"z":-1},{"x":0,"y":1,"z":0},0.2,0.3,
 "WPN_"+(metadata.get(element, 'Display Name')).toString()+"-"+element.toString(),
 USED_MODEL_WDG,element); 
 //occurance and model property seems to be ignorred in the data

where the function are defined as

/=======================================================================
//=======================================================================
$scope.app.waypoint_data_el={"position":{"x":-0.5,"y":0.5,"z":0},"gaze":{"x":0,"y":0,"z":-1},"up":{"x":0,"y":1,"z":0},"eventRadius":"0.2","wayfinderDisplayBoundary":"0.2","label":"Waypoint 1"}
//---------------------------------------------------------------------------------------------------------------------------
$scope.app.waypointElementSet=(el,pos,gaze,up,radEvent,radDisplay,label) =>{
el.position.x=pos.x;el.position.y=pos.y;el.position.z=pos.z;
el.gaze.x=gaze.x;el.gaze.y=gaze.y;el.gaze.z=gaze.z;
el.up.x=up.x;el.up.y=up.y;el.up.z=up.z;
el.eventRadius = radEvent;
el.wayfinderDisplayBoundary = radDisplay;
el.label = label;
 
return JSON.parse(JSON.stringify(el));
};

//=======================================================================
//that was for test adding model and occurence but is ignorred in the data at current time 9.24
//---------------------------------------------------------------------------------------------------------------------------
 $scope.app.waypointElementSet2=(el,pos,gaze,up,radEvent,radDisplay,label,model,pathId) =>{
el.position.x=pos.x;el.position.y=pos.y;el.position.z=pos.z;
el.gaze.x=gaze.x;el.gaze.y=gaze.y;el.gaze.z=gaze.z;
el.up.x=up.x;el.up.y=up.y;el.up.z=up.z;
el.eventRadius = radEvent;
el.wayfinderDisplayBoundary = radDisplay;
el.label = label;
el.model=model
el['component-occurrence']=pathId
 
return JSON.parse(JSON.stringify(el));
}; 

//=======================================================================
$scope.app.waypointsReset= () => {$scope.app.waypointsdata=[];}
//=======================================================================
$scope.app.waypointsElementAdd=(pos,gaze,up,radEvent,radDisplay,label)=>{
let el= JSON.parse(JSON.stringify($scope.app.waypoint_data_el))
 
 $scope.app.waypointsdata.push($scope.app.waypointElementSet(el,pos,gaze,up,radEvent,radDisplay,label));
};
//=======================================================================
//that was for test adding model and occurence but is ignorred in the data at current time 9.24
//=======================================================================
 $scope.app.waypointsElementAdd2=(pos,gaze,up,radEvent,radDisplay,labe,model,pathIdl)=>{
let el= JSON.parse(JSON.stringify($scope.app.waypoint_data_el))
 
 $scope.app.waypointsdata.push($scope.app.waypointElementSet(el,pos,gaze,up,radEvent,radDisplay,labe,model,pathIdl));
}; 
//=======================================================================

so I did some test in a deom project selecting  a list of component in the meta data via search critieria and then creating list. Using that list then

Using the list I created there dynamicaly (depending on the search resutls) then waypoints data  - so means  that all found elements and create for them items

and we can then navigate to the list of waypoints: with next and prev:

here the highlighting is via script and using a shader.