JMA
Version 2.4.0
API version: 10.2.0
Added
- Action templates and cron triggers can be filed in folders, like Jobs, WorkData and ProcessingSteps. Both have a
MoveToFolderaction (omit the folder to move back to the root), aFolderPathproperty and aParentFolderlink.CreateActionTemplateandCreateCronTriggertake an optionalFolderto create the item directly in a folder. Filing only organizes the item: a template’s own folder does not decide where its jobs go, and a trigger’s schedule and linked templates are unchanged. A trigger and the templates it runs are filed independently. - Action templates have a job folder:
SetJobFoldersets the folder that jobs created from the template (by a trigger orExecuteNow) are filed into, shown asJobFolder. It is a path, like an output slot target: the folder, and any missing folders above it, are created when a job is created, under the job’s owner, and renaming or moving the folder does not update the setting. Their outputs then follow the job’s folder. An empty path or/clears it, and jobs are created at the root as before; unlike an output slot, an unset job folder does not fall back to the template’s own folder. - The template and trigger queries take the
Folder/FolderRecursivefilter of the other foldable queries. - Folder contents list templates and triggers next to Jobs, WorkData and ProcessingSteps, as
ActionTemplateandCronJobTriggerentities. Clients that only know the earlier types can skip them; the total count includes them. - The folder children
Containsfilter acceptsactiontemplateandactiontrigger.
Changed
DeleteFolderalso refuses a folder that holds templates or triggers.- The folder
Clearaction also deletes the templates and triggers in the folder and its descendant folders. It deletes triggers first, then templates, then Jobs, ProcessingSteps and WorkData. Deleting a template unlinks it from every trigger, including triggers outside the folder. The report lists them with the item typesActionTriggerandActionTemplate.