DriveWorks Pro 17: View Manager [send feedback...]

View Manager

The View Manager lets you Add, Edit and Delete Views from the DriveWorks CPQ Template. Here you can setup Views, set their type and what data they will show based on a Rule.

The DriveWorks CPQ Template is made up of Views. When you enter the DriveWorks CPQ Template, you enter the Dashboard View. When you select Accounts, you go to the Customers View.

Every core bit of user interface is a View. Things like Menu Buttons get added to Views. This is done so each DriveWorks Project knows what View it is showing and what button are assigned to that View.

Location in the DriveWorks CPQ Template:

Dashboard > Admin Panel > View Manager

Using the View Manager

CPQ View Manager Screen

Down the left hand side of this View, you have a list of all the current Views within the DriveWorks CPQ Template. On the right hand side, you have the current Views Properties and Column Aliases

View Properties

The following properties can be set on a View:

View NameThis is the name of the View you want to add. This must be unique.Contacts
View Type

Give the View a type so each DriveWorks Project knows how to handle it.

Group Table NameIf a list View gets data from a DriveWorks Group Table enter the name of the Group Table.Contacts
List QueryEnter the rule used to get the data to display in the list View. This could be a Group Table.

This text is turned into a rule in DriveWorks using an Indirect function.

Parent List NameViews can be parented to other Views using this property. For example, Contacts could be parented by Customers. This field lets DriveWorks know what the parent View is.Customers
Skip project with Parent IDEach project will pass through the selected item index to the next project. This property prevents that from happening in the current project, passing it through to the next project that is opened. For example, Customer > Sales Orders > Order. If Sales Orders has this property checked it will pass the selected index from Customers to Order skipping Sales Orders.FALSE

Adding a View

  1. In the left hand list of Views, select Add.
    Add may be on another page, use the up and down arrows to navigate to the Add button.
  2. The Properties Form on the right hand side will clear and allow you to add a View.
  3. Fill out the form and press Add View. Give the View a name that has not been used already.
  4. The new View will appear in the list on the left hand side.

Editing a View

  1. In the left hand list of Views, select a View.
  2. The Properties Form on the right hand side will be set with the Views values.
  3. Modify the Views properties and select Update View.
  4. The data will be stored and saved for the View.

Column Aliases

List Views can have Column Aliases assigned to the View. This means that you can show alternative table headers to the ones that may come from the data source.

  1. In the left hand list of Views, select a View. The View must be a List View.
  2. Select the tab called Column Aliases.
  3. In Column Aliases on the left you will have Existing Names and on the right you will have text boxes to enter new names for each column.
  4. Enter the new name for each column.
Some Data Queries (Rules) do not produce data immediately. For example, the Order View will not show column headers. This is because it references a Child Specification List inside a specific DriveWorks Project.
Data Queries (Rules) to external sources should pull data straight away. Headers for these sources should be shown. These are Group Tables, SQL Queries, Plugins, etc.

Data Storage

View data is stored in the Group Table called ViewSource.

Table of Contents