Add Triggers to Determine When Your Pipelines Run

 

About Triggers

Triggers control component activation based on the incoming request (caller plus the input data).

  • Triggers can be specified for any/all of the AutoClassifier components.

  • By default, all of the triggers that are listed in the UI are called.

  • You can choose to select one or more filters within the features that you add.

Important! If the trigger evaluation for multiple pipelines determined that processing should be done, only one (the first one) pipeline will be processing the item. 

See the Triggers UI.

Specify Trigger Settings

Use the following steps to specify your Component trigger settings.

  1. <selected component/component> - AutoClassifier page > Trigger: Expand:

    See the AutoClassifier oage.
  2. Trigger is enabled:
    1. You must enable this setting before you can select any specific Triggers.
    2. Click the check box if you want to select one or more specific triggers.
    3. If not enabled, the Pipeline is always called.
  3. Triggers
    1. Optional
    2. If no specific triggers are selected, the Pipeline is always called.
    3. Select one or more specific triggers and if the trigger evaluates to True, the pipeline is called:
      • AutoClassifier Annotator
      • Connector Document Service
      • Connector Test Bench
      • Recommend
      • Connector Crawler
      • Connector External Content Service
      • External Access Point
      • SharePoint Crawler
      • Connector Railroader
      • Connector DocLoader:
      • Connector Target:
      • Playback or Testing:
      • Suggestions:
  4. Trigger Script (optional):
    1. Enter a C# or a VB script.
    2. Return True in the trigger script to run the pipeline stage. 
    3. Return False to skip running the pipeline stage.

Configure Your Triggers Using Scripts

  1. <selected component/component> - AutoClassifier page > Trigger: Expand to see the scripting section:

    See the script section of the UI.

  2. Trigger is enabled: Click. You must select Trigger is enabled before you can make any selections/entries.
  3. C# or VB.NET: Select the script language.
  4. Type in the script.
  5. Compile: Click to verify the validity of the script.
    See the following scripting examples:

Example: Retrieving an Item Property

To get an item property, use the generic GET method on item object:

C# 
string propertyValue = item.Get<string>("propertyName");
VB 
Dim propertyValue As String = item.[Get](Of String)("propertyName")

Example: Property Values

Property values can be changed in a similar way by the generic SET method:

C# 
item.Set<string>("propertyName", "propertyValue");
VB 
item.[Set](Of String)("propertyName", "propertyValue")

Example: Item Raw Data

Raw data can be retrieved as a byte buffer using the RawData property.

C# 
byte[] content = item.RawData;
VB 
Dim content As Byte() = item.RawData

Example: Logging

Use static methods to write entries into the log at different levels:

C#
Copy 
Log.Debug("Debug message");
Log.Info("Info message");
Log.Warning("Warning message");
Log.Error("Error message");



VB
Copy 
Log.Debug("Debug message");
Log.Info("Info message");
Log.Warning("Warning message");
Log.[Error]("Error message");
  • Assemblies and namespaces: Click See the gear icon. to define the assemblies and namespaces to import.