Object Filter Per User

Object Filter Per User

Using My Object Filters (User Object Filter)


Overview

My Object Filters lets you hide objects you do not want to see in the Dashboard's data views (browsers, lists, and graph diagrams).

Two key characteristics:

  • It is personal. Your filters only affect your screen. Other users are unaffected, and the database is not changed.
  • It is non-destructive and reversible. Objects are hidden from results, not deleted. Turn a filter off and they reappear immediately.

Typical use: reduce noise by hiding object families you are not currently working on. The examples below use the Demo-10.0.031 inventory.

Before you start

  • You must be logged in. Filters are tied to your user account.
  • Decide what to hide: an object type (for example, Program or Copybook), a property to test (usually the name), and the text or rule that identifies the unwanted objects.

1. How to open My Object Filters

1.1 Go to the Dashboard menu → Object Management → User Object Filter

1.2 The My Object Filters view appears, showing a header (Dashboard / My Object Filters), a Filter Text search box, a New button on the right, and a grid of existing filters.


Figure 1: Opening My Object Filters from the Dashboard menu and the My Object Filters view.

The grid columns:

Column

Meaning

Target Object Type

Which object type this rule applies to

Property Name

The object property being tested (usually the name)

Filter Text

The text the rule matches against

Operator

How the text is matched (Contains, Start With, and so on)

Excludes

Number of exception conditions (hover to view them)

Active

On/off toggle; takes effect immediately

Last Modified

When you last changed it

Action

Edit or Delete

2. Create a new filter

2.1 Click New (top right).

Figure 2: The New button used to create a filter.

2.2 Complete the form:

  • Target Object Type: the type to hide (for example, Program). Required.
  • Property Name: the property to test (for example, name). Required.
  • Filter Text: the value to match (for example, IOBAT). Required.
  • Operator: how to match. Defaults to Contains. See the operator reference below.

2.3 Click Add.


Figure 3: The New filter dialog completed for the worked example.

Worked example

Goal: hide the I/O batch routine programs. In this inventory they all end in IOBAT (ACIOBAT, ADIOBAT, AGIOBAT, AHIOBAT, and so on).

  • Target Object Type: Application Program
  • Property Name: name
  • Filter Text: IOBAT
  • Operator: Ends With

Result: ACIOBAT, ADIOBAT, AGIOBAT, and the other IOBAT routines no longer appear in your views.

Figure 4: Before and after applying the filter. IOBAT routines no longer appear.

Note: the available type labels in the Target Object Type list come from your inventory. Pick the one that represents COBOL programs.

3. Add exceptions with Excludes

Excludes act as an allow-list inside your block-list. If an object matches the main rule but also matches an exclude condition, it is kept (shown).

3.1 In the New or Edit dialog, locate the Excludes section.

3.2 Click Add Condition.

3.3 In the inline row, type the Filter Text and choose an Operator. Click the cell to edit it.

3.4 Repeat for additional exceptions. Use the delete action to remove a row.


Figure 5: Adding an exclude condition to keep ACIOBAT visible.

Continuing the example

You hid every IOBAT routine in Step 2, but you are actively working on the AC file routine, ACIOBAT, and want to keep it visible:

  • Exclude: Filter Text ACIOBAT, Operator Exact

Result: ACIOBAT remains visible, while ADIOBAT, AGIOBAT, and the rest stay hidden.

4. Operator reference

Examples use program names from the Demo-10.0.031 inventory.

Operator

Matches when the property

Example match

Contains (default)

contains the text anywhere

IOBAT matches ACIOBAT

Start With

begins with the text

AC matches ACIOBAT and ACNTFIX

End With

ends with the text

IOBAT matches ACIOBAT

Exact

equals the text exactly

ACIOBAT matches only ACIOBAT

Regex

matches the regular expression

^A.IOBAT$ matches ACIOBAT, ADIOBAT, AGIOBAT

All matching is case-insensitive.

5. Verify it is working

5.1 Save the filter and confirm its Active box is checked.

5.2 Open a data view that lists objects (an object browser, a list, or a graph diagram).

5.3 Objects matching your rule no longer appear, and item counts reflect the smaller set. In graph or diagram views, hidden nodes are removed and any connections that only led to those nodes are cleaned up as well.


Figure 6: Before applying the filter. The IOBAT programs are visible.


Figure 7: After applying the filter. Only ACIOBAT remains from the IOBAT family.

Note: if you see no change, confirm the Active toggle is on and that the Target Object Type matches the type shown in that view.

6. Manage existing filters

  • Turn on or off: click the Active checkbox in the grid. It applies immediately, with no dialog.
  • Edit: click the edit action, change any field or exclude, then save.
  • Delete: click the delete action and confirm. You can only edit or delete your own filters.
  • Find a filter quickly: type in the Filter Text search box at the top, or use the per-column filters in the grid header.


Figure 8: Managing a filter with the Active toggle and the Edit and Delete actions.

7. Notes and common issues

  • Per-user always. You only see and manage your own filters; they never affect other users.
  • Hidden, not deleted. Unchecking Active restores the objects.ultiple filters stack. An object is hidden if any active filter would hide it, unless an exclude condition rescues it.
  • Multiple filters stack. An object is hidden if any active filter would hide it, unless an exclude condition rescues it.
  • Where it applies. Filtering is applied to the data-driven views' results after the query runs, so it is safe and reversible, but the underlying query still runs normally.
  • Empty Target Object Type applies to all types. Be specific if you mean only one type.

    • Related Articles

    • CM evolveIT User Manual

      Welcome to CM evolveIT         User Training Manual                                                             Restrictive Rights This document and the product referenced in it are subject to the terms and conditions of the user License Agreement ...

    • Object Style

      Object Style: This document will cover the basics of the CM EvolveIT Object Management-Object Style. There will be a discussion of how we use the Object Style functionality to. After completing this document, you should have a basic understanding of ...

    • User Group

      Dashboard - User Group This document will cover the basics of the CM EvolveIT Dashboard user mapping. There will be a discussion of how to create user groups and set user authority within the group. We will look at how to assign inventories to groups ...

    • CUD and User Mapping

      This document will cover the basics of the CM evolveIT Dashboard user mapping. There will be a discussion of how to create user groups and set user authority within the group. We will look at how to assign inventories to groups as well as how to ...

    • Inventory and Object Group Mapping

      This document will cover the basics of how to map Inventories to Object Groups in the CM evolveIT Dashboard. There will be a discussion of how to assign and remove Inventories form an Object Group. After completing this document, you should have an ...