Skip to main content
Archived

Add "Log File" parameter to WorkspaceRunner

Related products:Transformers
  • November 26, 2015
  • 6 replies
  • 43 views

takashi
Celebrity

so that the user can specify the log file path for the target workspace optionally, without publishing the Log File parameter in the target workspace. The parameter should be optional, and accept a constant, string expression, attribute value, and user parameter value.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

6 replies

courtney_m
Contributor
Forum|alt.badge.img+22
  • Contributor
  • October 20, 2016

What would be the benefit of having this option rather than just publishing the Log File parameter?


takashi
Celebrity
  • Author
  • October 20, 2016
I don't think there is any benefit other than that the user does not need to create a published parameter linking to the Log File parameter any longer.

 


jdh
Contributor
Forum|alt.badge.img+40
  • Contributor
  • October 20, 2016

I think I would prefer an option to increment and/or timestamp the logfile name, without going through the effort of creating the logfile name for each trigger feature.


courtney_m
Contributor
Forum|alt.badge.img+22
  • Contributor
  • October 20, 2016
Okay, thank you!

Forum|alt.badge.img
  • May 5, 2021

Would be useful, particularly for child workspaces. What about messages sent back to caller from Logs? Would that work for user-defined log files?


DanAtSafe
Safer
Forum|alt.badge.img+22
  • Safer
  • June 23, 2023

I've been using a scripted Tcl parameter to concatenate the name of the current child workspace, a user parameter, and the time stamp.  e.g.

return [concat $FME_MacroValues(FME_MF_DIR)[file rootname $FME_MacroValues(FME_MF_NAME)].[file tail [file rootname $FME_MacroValues(SourceDataset_ESRISHAPE)]].[clock format [clock seconds] -format %Y%m%d%H%M -gmt false].log]

FYI, this idea is related to FMEFORM-14577.