Add Smartview application scope perspective

A perspective in D2 Smartview is loosely defined as something similar to a web-page in case of multi page web application. A perspective renders a view of semantically similar data with relevant UI controls and interactions to operate on the data. D2 Smartview switches from one perspective to another based on user interaction.

D2 Smartview has several perspective implementations like Landing, Doclist, Virtual Documents, Tasks & Workflows etc. Out of all these the Landing persepctive is the default and shown immediately after user login, unless the URL in browser's address bar points to a different hint.

The Landing perspective shows a collection of widget & shortcut tiles, some of them, upon click, opens up another persepctive with a more specialized representation of the corresponding data. The semantic associated with the data in such perspective is generally termed as application scope. All such application scope perspectives (tied to different widget tiles in Landing perspective) visually look similar irrespective of the data semantic that they represent.

This Add smartview application scope perspective option of workspace assistant, helps create the boilerplate if we want to define a new data semantic in addition to those already defined by D2 Smartview.

caution

Use this option when at least one plugin project exists in the workspace.

Associated questions and their meanings -

• This perspective goes to plugin

  Select a plugin project, inside which this boilerplate will be created.

• Name of the widget type to associate

  Which landing page widget this perspective will associate itself with. Each landing page widget tile is configured with a `type` attribute, the possible values that can go against the `type` attribute can be used here.

• Name of the default smartview widget type(from landing config) to associate

  The Smartview landing page has a bunch of default widget configuration name defined. When an end-user navigates directly to an application scope using URL, the widget configuration data might be missin in the URL, in thsoe cases the default widget configuration is used to resolve the metadata requirement while opening the perspective.
  Answer to this question specifies which default widget configuration from the landing page is to be associated with the application scope being defined.

• Application scope of this perspective(also used as URL fragment)

  Name of this application scope. Also used as base part of the URL when this perspective is activated.

• Directory name where generated code will be put into

  Relative location of the boilerplate code w.r.t selected plugin projects widget source directory

• Default title of this perspective

  Default displayable label when this perspective is active.

• How would you describe this perspective?

  Description associated wtih this perspective