From RPM Wiki
| Table of contents |
[edit]
Summary
This feature allows a user to build views that pull information from multiple processes. The merged view defines which process are included and how their different data is merged into common columns.
- The end result is similar to what you would get if you downloaded a bunch of different process views now and pasted them together one after another in a single worksheet.
[edit]
Setup
[edit]
Processes and merged columns
- Process merged views have processes add to them (obviously).
- We don't enforce a minimum, but a merged view with no processes would be useless.
- A maximum of 12 will be set in the global config.
- Process merged have merged columns. A merged column is created in the merged view and has a name and type. The user then maps fields from the processes that are the same type into those columns. This is how merged views display disparate custom data.
- There is no minimum, and useful merged views could be made without merged columns.
- We don't need a maximum since the view will still be subject to the column limits for views and not every merged column has to be selected as a column actually shown in the view (see below).
- The processes and merged columns are managed together in one table. The add/edit page for a process lists each merged column so the user can select a field for each. In a similar fashion, the add/edit page for a merged column lists each process so the user can select a field for each.
[edit]
Filters
Filters are added and edited similar to process custom views, except for merged views the user can select a process for the filter or "(all)". When the all option is selected the "Status" and data field filter variables are hidden. The other filters can apply to any process.
[edit]
Columns
The columns are arranged in the merged view just like other views. To add and remove columns other than the merged columns, the standard column selection interface is used:
- Columns available include all the process view columns common to every process and a "Process" column unique to merged views.
- The full list is here: View_Columns_(spec)#Merged_process_views
- Merged columns aren't listed here, they are completely managed in the table where they are added and removed.
- Default for new merged views: Process, Number, Status, Owner
[edit]
Management
- Merged views are managed from their own page in the process management section.
- A grid of merged views is shown and the user can click on them to go to the view.
- Merged views are only added from the merged view management page. Adding a merged view goes right to the edit page.
- A "Copy" link is shown for each merged view and goes to the edit page with all the same processes, merged columns, filters, columns, and options except the name has " copy" added to it.
[edit]
Merged column types
- Agency
- Rep
- Customer
- Account
- Supplier
- Staff
- Product
- Account group
- Process
- Form
- Text/list
- Paragraph
- Date
- Money
- Number
[edit]
Use
- The merged views have the same paging, sorting, shells and download functionality of regular views.
- Each row has a "View" link column on the far left to take the user to the form.
[edit]
Security
[edit]
Staff users
- Merged view add, edit, delete:
- New security group "processes.merged.design" that requires a new privilege "Setup overall process reporting"
- Merged view use
- New security group "processes.merged" that requires a new privilege "View overall process reporting"
- This overrides individual role process security. A user could have hidden permissions for every process, but if they have this they can see every row in every merged view. This means a user may click "View" from a merged view and get a permission error because they were looking at a form
- This is desirable. This feature is intended for users who have access to all processes. We don't want the accuracy of a merged view compromised because underneath some forms were not being included because of the viewer's security.
- It will be clear that these privileges give a user access to read every field in every process.
[edit]
Agent users
- n/a
[edit]
History
- Shine: Feature added
[edit]
Name
- Rejected names: merge, mix, mixed, united, unified, union, folded, blended, cross, multi, fusion, mesh
- This page was last modified 17:17, 11 Jun 2009.
- This page has been accessed 519 times.