BreadCrumbs and DefaultAction behaviors

Siva Prasad Salipalli

Hi,

I have implemented a Smart UI Command which routes to a full page widget using perspective router,context plugin, some REST calls etc. I am also able to show the Breadcrumbs with proper name in the new perspective by fetching Ancestor Collection object. But the links/Breadcrumbs when clicked redirect to a undefined node. 

I have encountered same issue while trying to show node names and using DefaultAction behaviour to show clickable links.

I have tried to debug the csui source code, but I couldn't find where this execute is performed and how the node(perespective) is opened. 

While using Breadcrumbs or DefaultAction behaviors are there any addional dependancies ? 

The link being redirected is of the form "<servername>/otcs/cs.exe/app/nodes/undefined". 

 

Ferdinand Prantl

I cannot be more concrete, because I don't know, what you show on your custom perspective. What is the object or objects, which you display there? What are the widgets, which you used for it?

I am afraid, that the global  breadcrumbs control (between the navigation header and the perspective content) can display only a trail of nodes and thus works only on node perspectives. (node.perspective.context.plugin and node.perspective.router) It is not ready to be used with any other objects. The extensible solution would be letting the breadcrumb be implemented by perspective owners, just like they can implement perspective context and plugin and router extensions.

There are widgets, which need a contextual node. For example, nodestable, metadata, document.overview etc. If you place them on the landing page, they will fail.

Breadcrumb trail is not a configurable widget, but it needs a contextual node too. That is why it is hidden on the landing page, search results or other perspectives. As a rule of thumb, if you don't see "/app/nodes/:id" on the URL, you will not see the breadcrumbs.

You could try setting a (some?) contextual node in your perspective context plugin - in the constructor and in the onClear method, for example:

  this.node = this.context.getModel(NodeModelFactory, {                options: fields: {                  properties: []                }              });  this.node.set('id', ...);

It will allow the ancestor collection behind the breacrumb control fetch correctly - it needs some current node to build the path from the root volume to.

DefaultActionBehavior works for nodes only, or for objects, which have their attribute schema "reasonably compatible" with nodes. When you trigger the "execute" request event, you have to provide such model as a parameter. It is usually the model behind the item view, which shows the click control. Most default action rules and UI controls showing node links will work well, if you provide at least the following attributes in your model: id, name, container, type, and optionally mime_type.