View (spec)

From RPM Wiki

Table of contents
1 Summary
2 Categories
3 Types
4 Specs
5 Use cases
6 History

6.1 Need
6.2 Success

[edit]

Summary

Functional spec for Views

[edit]

Categories

he category is used in the page title on the edit views page. For the processes category use the template name.

  • Commission items
  • Processes ("Select a {TEMPLATE}", forms from a specific template)
    • Referred to as a custom view for {TEMPLATE}. Example: Custom view for Orders
  • Agencies
  • Reps
  • Customers
  • Accounts
  • Staff
[edit]

Types

  • Custom views (constructed by a user)
  • Built-in views
    • Can not be deleted. Built-in views can still be loaded to use as a basis for creating other custom views.
  • Temporary views
    • Generated from some pages, for example, viewing all the commission items for a certain agency. Temporary views can be used, but the next temporary view that is generated of this type or ending the session will destroy that view.
[edit]

Specs

[edit]

Use cases

  • Create and save a view. There is a view that a user is going to need every day so they must be able to create and save a view. Example: The user works with “Quote�? forms everyday and wants a private view that just shows their quotes and with certain columns.
  • Refine a view & save it as a new view. The user is viewing a custom or built-in view and needs to refine the view. The user is going to need this view some more so wants to save it. Example: As above the user is viewing the items of an agency and then refines the view to a certain product. This view is going to be used by the commission team over an over again this run so the user wants to save this as a public custom view.
  • Refine & save over. The user is using a saved custom view and makes some changes that improve the custom view so they want to update the saved version. Example: There is a public custom view that everyone uses to see form status and a new field was recently added that should be in the view.
  • Reset a custom view. The user is using a saved custom view and makes some refinements without saving. They user then wants to return the view to how it was saved. Example: The user is looking at the above form view and needs to limit the scope of the view a bit for now, but won’t need this view again.
[edit]

History

  • Venus: Feature added.
  • Luna: Filter by code type custom variables.
  • Mars: Assignment category & more commission columns.
  • Phobos: Linked columns, paging & sorting remembered. Drag & drop column order
  • Ceres: Default views, "Added", "Split", "Supplier exclusion", "Started type" columns.
  • Rockefeller: Customer "City" and "Website" linked columns.
  • Pathfinder: Reconciliation columns & filters, Staff views (of staff users).
[edit]

Need

I realized early on in process management development that the customization being developed for building templates would need to be matched with customization in how the information is displayed.

[edit]

Success

Since its introduction, views have become a very popular and widely used feature in RPM, both for commission management and process management. Views have formed the foundation for the day-to-day work of users across all our customers.

Retrieved from "http://www.rpmsoftware.com/wiki/index.php/View_%28spec%29"
  • This page was last modified 18:52, 26 Sep 2006.
  • This page has been accessed 1459 times.