In order to work effectively, the CRM system provides you a set of tools.
coreBos is built based on the modularity property, so the software contains modules that execute specific actions and operation based on different customers that we are offering coreBOS as consulting CRM. coreBOS, for now, contains nearly 90 modules in total but some of them are not yet in activity. Every module has the same interface structure. So if we access one of the modules in coreBOS the list view of the module will appear.
List View is a view group that displays a list of scrollable items. The list items are automatically inserted to the list using an Adapter that pulls content from a source such as an array or database query and converts each item result into a view that's placed into the list.
The main goal of this extension in coreBOS is to permit installations with a large number of documents to access a structured list view of the records. By default, the document list view shows a list of all records with a set of records of each module. coreBOS has clients with over 30000 records in their list view so the list view is necessary and an advantage that coreBOS offers because we can see and access every record. List View in coreBOS is organized in a table form where each row represents a record of the module retrieved from the database. The table contains information about each field.
Rights of Access
List views are visible to your community users with Community, if Visible to all users setting is enabled for views of objects in community user profiles. To make list views visible only to your Helpdesk users, select Visible to certain groups of users. Then share the view with the All Internal or a selected set of internal groups and roles.
When implementing a community, create custom views that contain only relevant information for community users. Then make those views visible to community users by sharing them with a set of community groups and roles.
Creating Custom List Views
One of the main features that ListView offers is that at any time we can Create Custom ListViews based on the criteria or conditions that a user is searching or working into. This facilitates the work of every system analyst or client that is searching for a specific document. The different clients may have a massive volume of data records so searching from one page to another is a time-consuming process.
Searched Based Custom List Views
In every list view of any module, users can create custom views based on search criteria. Every user can create views based on field names on every field that the table includes. Also, we can filter the records in listview while doing a simple search in Search for Field in case we know information about the record we are searching for. Also, CoreBos Advance Search is a list view based on logic conditions one specific field of the records contains a letter, number, etc…
Filter-Based Custom List Views
In coreBOS, every user can create filters about recent works of clients or conditions. In the interface of every module, we can create custom list views based on filters built by different users to minimize the exhausting search of the record for specific fields such as campaigns or organization name.
Filters are an effective search tool that can quickly group records into a form. You can limit the search to selected columns and search criteria.
Filters are just as important as the modules themselves. They serve to create searches in the record even if they are not just a persistent resilient search. We have 1.9 million different tasks for each account and around 2000 possible filters to find the information we need.
We have chosen to display only 20 records in a standard way, but if we want to change it, we can do it (in code). This selection is performed with only 20 records so that the visual appearance of the page is not loaded. If we have client requests that do not match any of the actual filters, then we would like to create more standard or advanced filters.
Steps to create a Custom Filter:
Select a module and click Create Filter link (highlighted below) in the list view of a module.
Provide a name to your filter in View Name and select the columns that you want to be displayed in the list view when the filter is selected.
The module's link field should be mapped or you will not be able to access the detail view.
On save you will be able to see the filter in action. At this point, you can see the list of records in the selected columns.
Both Standard Filters and Advanced Filters are used to enhance and refine your filter.
Standard Filters refine the search depending upon date intervals or a particular period. You can find these options available:
|Select a Column||This picklist allows users to refine search depending upon record Date fields.|
|Select Duration||This picklist allows users to select time duration by the Select a Column option above.|
|Start Date and End Date||You can fill these fields manually or if you select the duration, these fields will be automatically filled.|
Advanced Filters refine the search depending upon field values conditions specified.
This block contains three columns. Select the desired field name from the picklist in the first column, set the desired condition from a picklist in the second column and enter one or multiple items in the third column manually. Items you enter in the third column should be separated with commas.
After saving you will see the list of records that fulfill the conditions in the list view.
|List in Metrics||This option if enabled will show the count and details of the filter in the Key Metrics widget on the Home Page.|
|Set as Default||If this option is enabled, then this filter will be the default view loaded when you first access the module. Once you have selected another filter that selection will prevail until you exit the system.|
|Set as public||If this option is enabled, every user of the application, irrespective of role/position can view it. When a user marks a custom filter as public, it should be first approved by the admin user. It remains in a pending state until an administrator approves it. Administrators can see the request in the Pending section.|
The rule is: when a user makes a filter, only he and administrator users can select/edit it. If the filter is marked as Public AND approved, all users can select it, but only he, administrator users and users in a superior role can edit it.
Meta variables for special fields
When searching on user fields like Assigned To, Creator or Modified By the system expects you to give the full user name to search on. In other words, you have to use the first and last name of the user like this:
assigned_to = user.first_name + ' ' + user.last_name
A typical situation that arises often is the need to create a filter and show only the “current user”'s records. So you create a filter of activities to be done “today” and you don't want to have to create 50 “today” filters. one for each of your 50 users. The same way you don't have to create 365 filters for each day of the year for your “today” filter.
To accomplish this we can use a special meta-variable when defining our filters for the user fields. This field is called “current_user” as can be seen in the next image.
You can search on blank dates using the dollar sign $.
You can use the word null to search for empty values on related and text fields.
Detail View shows detailed information about a record in the module. Every record in each module we can Edit, Duplicate or Delete. If we want to change the value of a field we edit the information the detailed view. The user after making the changes can save it with the new information.
If we want to group records or duplicate records to form a standardized record we use the mass edit option in coreBOS to built a single record for selected records by the users. This is useful for duplicate records and creates a single record for them.