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.
Archived
Add "Log File" parameter to WorkspaceRunner
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.
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.
+23- Contributor
What would be the benefit of having this option rather than just publishing the Log File parameter?
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.
+40- Contributor
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.
Would be useful, particularly for child workspaces. What about messages sent back to caller from Logs? Would that work for user-defined log files?
+23- Safer
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.
Login to the community
No account yet? Create an account
An FME Account is required to contribute
LoginEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.