RoboFlowHelp.1.15

!!! warning "Legacy Documentation" This page contains documentation for the original RoboFlow application. Some features described here may not exist in the new Damtoolkit WAP interface.

Hotcollection

Hotcollection workflow that launches a record-query in a every time-loop. (unless using Roboflow Triggers-see below) The result of the query are records (called hot-record), which are processed one by one.

For each record the "Action Script for records" is executed and if e-mail specified the "mail" text is evaluated and bundled per e-mail. When all records are processed that mail(s) is sent.

Parameters

CumulusCatalog

The name of the Catalog you want to use

Type in the name or click on the button to connect and select a catalog

This workflow can also process multiple catalogs (one after the other). In that case type in the names separated by ;

CumulusQuery

The cumulus-record-query. For details on the syntax of the query see Cumulus Query Syntax.

e.g. ("Status" ! *) || ("Status" != "offline")

e.g. ("Status" ! *) || ("Status" != "offline") order by Record Name

e.g. ("Status" ! *) || ("Status" != "offline") order Asset Name DESC

EmailNotify

E-mail-address of person to notify for every record being processed (multiple e-mail-addresses separated by ;)

E-mail-Message-Configuration

Parameter file for the e-mail mail-subject,mail-body and mail message per record.

For each record the mail message is stored and bundled per e-mail.

When all records are processed the e-mail(s) are inserted into the mail-body and are sent.

Per e-mail address only 1 mail is sent; referred to as bundled mail

To attach a file to the mail add the following to the body or mail message:

ImportFromStoredRecordTriggerFolder

Path of folder where trigger-files from the cumulus server are stored for importing records instead of querying the whole catalog

To be able to use this functionality you need to install the AutoCatalogTrigger/RoboFlowTrigger in the CumulusServer

-> copy AutoCatalogTrigger.jar into esp folder of the Cumulus 7 Server

-> OR copy RoboFlowTrigger.jar into esp folder of the Cumulus 8 Server

-> setup the record-trigger or category-trigger in Cumulus Client (the targetfolder that you define in this trigger is the same folder you specify here)

Now, for every record, new or deleted (depending on your trigger-settings) a trigger-log-file is written to this folder, containing the Catalog Name and Category or Record ID.

In every loop of the workflow, if you specified this ImportFromStoredRecordTriggerFolder here, it will read these trigger-log-files and add the categories (watchcategories) or records (hotcollection) to this collection and delete the processed trigger-log-files.

Now, the workflow will perform the query specified above on these records or categories instead of on the whole catalog.

If no trigger-log-files are found, no records or categories will be processed. Since the query on an empty collection is still an empty collection.

If you leave the ImportFromStoredRecordTriggerFolder empty, the workflow will have its standard behavior, thus quering on the whole catalog...

TargetProcessedTriggerFolder

Path of folder where processed trigger-files are stored, if left empty no trigger-files are stored.