Advanced Filters

There are different combinations of files that maybe used for filters. Both Easy Build and Expert Build can create filters using the file called Contact. Only Expert Build can be used to search on these files:

Contact one data layout on the CUST file for data field information

Activity one data layout on the TRAN file for activity field data

Contact/Activity one data layout with a combination of CUST and TRAN files for data field and activity data

Contact/Contact two data layouts on the CUST file for data field information

Activity/Activity two data layouts on the TRAN file for activity data

All filters search on data in the file and display corresponding contact records based on the criteria chosen. Contact file filters use data fields and Activity file filters use activity data fields. Let's look at how and why you might use the other files for filters

Activity File (TRAN file)

Activity filters let you search for data in activity data fields found on Panel 7, the activity panel. The fields used on the activity panels are ActionWare programmed fields which means that they have the same field ID's, always. Contact (CUST file) fields ID's can vary greatly from application to application because of the program ability to create your own contact data fields. Contact data field ID's are always 3 characters long. Activity field ID's vary in length. Some of the most used fields in filter searches are:

Other than the Filter Header using a different value for file, focus and type - the Filter Maintenance screen looks the same. An example of a filter using the Activity file would be the need to display all contact records with pending activities for a specific PID. We are using a PID of ACTION in this example. The filter would look like this:

Filter Maintenance
and /or	include if field	position /length		upper case	compare type	compare number, or "characters" or &fieldName	or %V (dept) or %T (date) or %U (user id)
	TRPID	____	____	__	EQ	"ACTION"_______________________
AND	TRSTAT	____	____	__	EQ	"P"_____________________________
____	______	____	____	__	____	________________________________
____	______	____	____	__	____	________________________________

The result of this search would be an active filter display of each contact record with a PID of ACTION that has an pending activity. The resulting contact records would be displayed with the focus on the activity panel and the pending activity would be highlighted on each contact record.

Contact/Activity (CUST file and TRAN file)

The Contact/Activity filter combines a search of data fields and activity data fields.

Other than the Filter Header using a different value for file, focus and type - the Filter Maintenance screen looks the same. An example of a filter using the Contact/Activity file would be the need to display all contact records in the City of San Francisco with pending activities. The City field ID is CIT and the activity status field ID is TRSTAT. The filter would look like this:

Filter Maintenance
and /or	include if field	position /length		upper case	compare type	compare number, or "characters" or &fieldName	or %V (dept) or %T (date) or %U (user id)
	CIT	____	____	__	EQ	"San Francisco"_________________
AND	TRSTAT	____	____	__	EQ	"P"____________________________
____	______	____	____	__	____	_______________________________
____	______	____	____	__	____	_______________________________

The result of this search would be an active filter display of each contact record in the city of San Francisco with any activities pending. These filtered contact records would be displayed with the focus on the activity panel and the pending activity would be highlighted on each contact record.

Contact/Contact (CUST file and CUST file):

Contact/Contact filters are useful because they let you filter for criteria stored in two different data layouts in the database. The result is a group of records that meet the criteria of both data layout selections. When creating a Contact/Contact filter you need to decide WHICH group of records you want to end up with. C1 and C2 are the database ID's (DB/id) that are used in Contact/Contact filters. C1 is the group that is searched first and C2 is used for the contact records you want to end up with. This type of filter can also be very useful to compare data with a resulting display of contact records meeting your criteria.

When you finish filling out the Filter Header Screen and press enter. The DB/id column appears to the right of the and/or column. It is in the DB/id column that you designate C1 or C2 for the filtering.

An example of a filter using the Contact/Contact file would be the need to display all contact records with a particular product interest who are are already customers. The field that designates product interest is on data layout 3 in a one character field ID of PRD. The field that designates a customer is a one character field ID of CUS on data layout 1. The data in these fields is the same, it is either Y (Yes) or N (No). These fields are made up field IDs for this example only. You would need to determine what if any field ID is used to identify product interest or customer data. We want to end up with all contact records who have product interest Y in field PRD on data layout 3 and have customer Y on data layout 1. The filter would look like this:

Filter Maintenance
and /or	DB Id	include if field	position /length		upper case	compare type	compare number, or "characters" or &fieldName	or %V (dept) or %T (date) or %U (user id)
	C1	PRD	____	____	__	EQ	"Y"_________________________
AND	C2	CUS	____	____	__	EQ	"Y"_________________________
_____	__	______	____	____	__	____	___________________________
_____	__	______	____	____	__	____	____________________________

The result of this search would be a display in the active filter of each contact record with Y (Yes) in PRD (product interest field who has a Y (Yes) in the CUS (customer) field. The filter displays contact records in data layout 1 because we used C2. Effectively the program build a filter of all contact records with Y (Yes) for product interest in data layout 3. It than used that group of contact records for a second filter to display all customers represented by a Y (Yes) in the CUS field on data layout 1.

Activity/Activity (TRAN file and TRAN file)

Activity/Activity filters let you compare data in activity fields to produce a single result. The result is a group of records that meet the criteria of both selections. When creating a Activity/Activity filter you need to decide WHICH group of records you want to end up with. A1 and A2 are the database ID's (DB/id) that are used in Activity/Activity filters. A1 is the group that is searched first and A2 is used for the contact records you want to end up with. This type of filter can also be very useful to compare data with a resulting display of contact records meeting your criteria.

When you finish filling out the Filter Header Screen and press enter. The DB/id column appears to the right of the and/or column. It is in the DB/id column that you designate A1 and A2 for filtering. An example of a filter using the Activity/Activity file would be the need to display all contact records that have completed HDOC (hard document or letter) activities with pending TELE (telephone call) activities.

 The filter would look like this:

Filter Maintenance
and /or	DB Id	include if field	position /length		upper case	compare type	compare number, or "characters" or &fieldName	or %V (dept) or %T (date) or %U (user id)
	A1	TRMET	____	____	__	EQ	"H"________________________
AND	A1	TRSTAT	____	____	__	EQ	"C"________________________
AND	A2	TRMET	____	____	__	EQ	"T"________________________
AND	A2	TRSTAT	____	____	__	EQ	"P"________________________

The result of this search would be an active filter display of all contact records that had pending telephone activities using first a search of every contact record with completed hard document activities.