Hi

This is a suggestion for AM9 that came out of a discussion on the support forum the other day.

It would be useful for a task with multiple scheduled triggers to be able to identify WHICH of the schedules was used to trigger the task. This would be useful for tasks that have to be executed a various times and that need to execute slightly different, depending on the schedule that is active.

With AM9 today, I have to create multiple copies of the same task, each with their own schedule(s), and then adapt one or two variables in each task.

Ideally, each trigger would have an ID that I can examine within the task, or the trigger would set a variable that I can read.

Thanks,
Dan

Daniel,
I fully support this suggestion. For tracking purposes, it is indeed necessary that the AMTrigger dataset contains both a TriggerName and a TriggerID data element.
Same thing applies to Conditions as well as to Triggers.
Currently there is no practical workaround to this problem.
I wish N/A can consider this request.

-------------------------
Jean Delfosse - Automate Beta Tester
Win7 Pro 64 bits -Win XP Pro SP3 32 bits - AM8, AM7, BPA10, BPA9, BPA8, BPA7, AM6 Enterprise, AM4

%AMTrigger.AML% will provide the trigger AML code for the specific trigger that fires the task. You can then use the trigger ID to differentiate how the task should proceed.


Task Steps: (Right click, Select All, Copy to copy to the clipboard. Steps can then be pasted into the AutoMate Task Builder)
<AMFILETRIGGER AM5_TRIGGERID="{12d0c43f-bc18-448f-acdb-3b36d5b26f69}" AM_IGNOREEXISTINGCONDITION="NO" ASSOCIATEDTASKID="" FOLDER="c:\test" ADDED="YES" POLLINGINTERVAL=10 INCLUDE="test1.txt" USERTYPE="NOUSER" />

-------------------------

Leonard Amabile | Director, Cross Platform Support
AutoMate | InterMapper | Skybot | Divisions of HelpSystems
T: +1.213.738.1700 | F: +1.213.738.7665