Setting

Definition

Name

Name of catch point.  It is recommended to assign names based on catch point type, such as "*SCREEN - " for all screens and "*FEED - " for all feeds, etc.  

Picture

Any picture uploaded can be referenced by the catch point screen HTML and displayed when the catch point screen is used.

Primary location

If the catch point applies to a specific location, it is noted here.

Owner

Any change to the screen, feed, and/or process associated with this catch point should be approved by this person.

Primary accountable person

The person noted here is the one accountable for ensuring compliance with the defined catch point process.

Data elements assigned to the catch point

This defines the data elements, from the data dictionary, that will be sourced by this catch point.  This comes from initial catch point and process design work.

RDC tasks assigned to the catch point

(Not used)

Data elements most trusted for the catch point

Of the data elements sourced by this catch point, you can define this catch point as the MOST trusted source of one or more of those data elements.  When a data element has been defined as being most trusted by a catch point, then any other catch point that attempts to source that same element, after it has been sourced by the most trusted catch point, will be ignored.  Until the data element is sourced by the most trusted catch point, it will be accepted by any catch point.  However, once it has been sourced by the most trusted, then the only catch point that can change its value is another sourcing from the most trusted catch point.

Calculate accuracy based on these elements

If you select one or more data elements via this multi-select list box, the MIE will calculate current accuracy of the Assets table based on data presented via this catch point.  The elements selected must all be sourced by this catch point.  Each time Consolidate runs, if it encounters records from this catch point, it will compare values presented in each of the elements specified to what is currently in the Assets table.  It will record the number of columns presented for comparison along with the number that agreed with what was currently in the database.  It will also record the number of records that were presented along with the number of records that completely agreed (all elements specified were compared and agreed) with what was currently in the database..

If a new record is presented via this catch point, it will be recorded as a record "miss", and every element specified to be used for accuracy determination will be recorded as a "miss".  (For example, if 5 elements have been specified to be used to determine accuracy, then 5 columns presented and 0 columns passed will be recorded for each new record added.

Records presented by this catch point that are rejected as exceptions will not participate in the accuracy calculation.  However, once the records are cleared as exceptions, they will be compared to current data and accuracy updated accordingly.

Each run of Consolidate that encounters records from this catch point will write a log entry to the Assets Accuracy Log.  The log can then be queried to determine accuracy over any given period of time.

Auto-add hardware

If this setting is checked, then this catch point will automatically add new hardware to the master hardware catalog.  This setting is usually used for the ASN Processor.

Auto-add software

If this setting is checked, then this catch point will automatically add new software to the MSL.  

Note:  It is highly recommended that adding items to the MSL be strictly governed and not done automatically.

Catch point can update only (no adds)

This setting restricts the catch point to only updating existing asset records.  Use this setting for catch points that you do not want to add new asset records.

Cause exception on attempt to change existing serial number

If the catch point attempts to make a change to the existing serial number and the existing serial number is non-blank, the entire record will be marked as an exception and not processed further.

Cause exception on attempt to change existing manufacturer

If the catch point attempts to make a change to the existing manufacturer and the existing manufacturer is non-blank, the entire record will be marked as an exception and not processed further.

Cause exception on attempt to change existing computer name

If the catch point attempts to make a change to the existing computer name and the existing computer name is non-blank, the entire record will be marked as an exception and not processed further.

Do not automatically assign asset to an assignee

The default behavior of the MIE is to automatically establish a link between an assignee and an asset if a catch point presents sufficient information to create that link.  The information necessary depends on how ESI sets up the primary Consolidate settings for you, however last login ID is usually all that is required to create an assignee record and then to link that record to the asset.  Most auto-discovery tools will source last login ID.  If you wish to override the default behavior of automatically assigning assets, check this box.  An assignee record will still be created if sufficient information is presented, however when this box is checked the MIE will not link the assignee record with the asset.

Force immediate archive upon consolidation

This setting is primarily used for import feeds that are importing into the staging table, and therefore being used to simulate a catch point screen.  Catch point screens, when they save their data to the staging table, will first write any existing record to the archive table, thereby preserving all history of every catch point record ever written for a given asset.  Import feeds are general in nature and do not attempt to archive existing records.  When this setting is checked, Consolidate will archive the staging table record as soon as it is successfully consolidated, thereby preserving it for historical purposes.  You do not need to use this setting for any catch point screens.

Fill asset number in staging table from asset table by

If selected, prior to attempting to process the record from the staging table, the asset number value in the staging record will be attempted to be filled in from any existing asset record (in the asset table) using one of the defined matching fields (for example, serial number).  If serial number is chosen, then the serial number in the staging record will be used to do a look-up back into the asset table.  If the look-up succeeds, the asset number from the asset record will be written into the staging record.  Prior to attempting such matches, the value in the staging table is compared to the blank values defined by the setting ConsBlankPhrases.  If it matches a defined blank phrase, no update will be performed.

This feature is used primarily when auto-discovery is being fed to the MIE from another source (such as Altiris) and asset number is not available as part of the feed.  The MIE requires an asset number when performing down-stream software recognition matching, so it is important that an asset number be filled in prior to performing software recognition.

Catch point services a standard (pre-defined) catch point

The MIE has several pre-defined catch points, such as the ASN Processor, WDA scanner, and WTR utility.  If you are using one or more of these utilities to source data to the system, you need to establish a catch point, then connect it to the pre-defined source using this setting.

Catch point fulfills the following common role

There are several common roles for which catch points may be designed for various customers.  The proper role should be assigned to the catch point, if applicable.  Roles are used by the {%CPINFOFORROLE%} general tag.  Roles are also used to determine the retention period for catch point history information.

Default status

This setting allows you to choose one of your asset status values to be automatically written to the asset record each time a new asset record is created or when a status value does not already exist.  It will only be written if a status value does not already exist.  

Note:  If the catch point also sources status, the status defined by this setting will take precedence.

Forced status

This setting allows you to choose one of your asset status values to be automatically written to the asset record.  It will write the value regardless of any value that may currently exist.  It also takes precedence over any status value that may be sourced by the catch point.  If a forced status value overwrites an existing value and thereby changes it, a warning will be logged to the Consolidate Job Log (when the Consolidate warning level is set to 2 or above).  Any changes made to existing status values will also be logged to the Change Log.

Conditional status

A status value that will be written to the asset record if the defined condition is met.  If the condition is not met, the existing status value in the asset record will not be altered (unless a Forced status value has also been defined, in which case the Forced status value will be written).

Condition that must be met to set conditional status

The condition that must be met before the conditional status value will be set.  The condition is tested against the target asset record (an asset record must already exist for conditional status to apply).  Conditional status is overridden by Forced status - if both Forced status and Conditional status are specified for the same catch point, Forced status will always be the value written to the asset's status field, regardless of whether or not the condition is met.

Fire workflow if any of these elements changes value

Allows choosing of one or more fields from the Assets table to form a list of "watch" fields.  If this catch point attempts to change an existing non-blank value in the associated record in the Assets table, the workflow defined will be fired.  All changes to all watch fields are collected in the form of a .CSV file, which is then added as an attachment to the thread of the workflow when fired.

Workflow to fire when one of the fields above changes value

Defines the workflow that will be fired if any of the "watch" fields, defined above, changes value.

Route to approval workflow

This setting allows you to connect the catch point to an established workflow.  This is typically done to solicit approvals.  Generally, the Software Request Portal catch point is connected to its servicing workflow via this setting.

Fire this workflow every time this catch point inserts a record to the staging table

For general purpose catch points, this setting will cause a workflow thread to be created for each insert that happens to the asset staging table.  Only general purpose catch points will honor this setting.  Excluded are catch points that perform the following functions:  Harvest software, Move software authorizations, Request software.

Caution:  Use this setting carefully.  Do not fire workflows that will perform actions on the associated asset record, as such record may not exist yet at the time the workflow fires.  The MIE must perform Consolidate on newly inserted staging records before they may show up in the assets table.

Fire this workflow every time this catch point updates a record in the staging table

For general purpose catch points, this setting will cause a workflow thread to be created for each update that happens to the asset staging table.  Only general purpose catch points will honor this setting.  Excluded are catch points that perform the following functions:  Harvest software, Move software authorizations, Request software.

Percentage of assets expected to pass through catch point

This setting is used by reporting to prepare an audit report of actual volume through the catch points versus expected volume.  Only catch points that have this setting set to a non-zero value will be included in the audit report.

Risk

This is also used in reporting during the catch point design phase.  The risk of capture is assessed, which is used to calculate a data element score.  The score is used to determine the probability of proper and accurate capture, which is then used to determine where process compliance audit should be focused.

Description

Detailed description of the catch point, its function, and purpose.

Audit process

Detailed description of how compliance audit will be achieved.

Notes

Detailed notes.

HTML for catch point screen

This setting requires developer access.  This is the actual HTML used to define the catch point screen.  It accepts both General and Merge tags.

Use this security profile when this screen is used

Causes the screen to use a Security Profile, which governs how the screen can be accessed.

HTML for catch point screen instructions

This setting requires developer access.  If the catch point screen is going to include a link for help or instructions, this is the HTML that will be used to display the help or instructions.