# Considerations - to UG

- Users should be able to select any displayable columns from any available clinical forms and display all selected columns in a recordlisting view format named as custom view.
- Only clinical forms that have been cooked into the current InForm trial and have been activated will be available as selectable forms for generating this custom view. Columns of different forms are paired to each other based on site, subject, and visit.
- Columns that are not allowed to be displayed in the recordlistings view because of user rights or blinding restriction will not be available as selectable columns.
- Columns that have no data or its form has not been activated will be displayed as blank.
- Current filtering criteria on the recordlistings view will be applied to the custom view.
- Locales used for the current recordlistings view will be used for generating the custom view.
- The resulting custom view selections will be saved on the server and available to its owner for retrieving data. The owner will be able to delete existing custom views from the UI. No other maintenance operations will be implemented for this purpose. No sharing of custom view will be allowed.
- The only operations available for custom view are "Export to Excel", create query, and source verify on selected data item. Export to Excel makes it possible to export data together from multiple forms.
- Query icon will be displayed for appropriate data point to indicate data that has an open or answered query.
- No form states or review states will be available for custom view since it is not an actual clinical form.
- In order to ensure the resulting dataset is kept under a reasonable size and will not deteriorate the server’s performance, we are going to restrict the number of columns for custom view. The maximum number of forms and columns that can be selected for a custom view will be set to 5 forms and 15 columns. However, these restrictions only apply to flat forms only. Itemsets and repeating forms (i.e. non-flat forms) are displayed by its own as a secondary view under comparison view so they are not count under the columns and forms restrictions. This restriction can be changed at the end of development to adjust for a better solution. This maximum column count is set internally and cannot be changed by customer.
- Number of rows per page will follow existing rows per page options that is applicable throughout the recordlistings view.
- All custom views will be displayed in the same look and feel as existing recordlistings view.

Copyright © 2009 - 2012 Oracle and/or its affiliates. All rights reserved.