Using the {user.shapefile} output key in a Log Action Formatted Message, what does this key add to the Automation log when you trigger after updating a shapefile?

Using the {user.shapefile} output key in a Log Action Formatted Message, what does this key add to the Automation log when you trigger after updating a shapefile?

• A. The path to the Shapefile on FME Server
• B. A link to the source shapefile
• C. The path to the Shapefile on your local machine
• D. A link to download the SpatiaLite database

Answer: (A)

The key expands to the server-side path of the shapefile stored on FME Server. In a Log Action Formatted Message, this means you’ll see exactly where the updated shapefile resides on the FME Server file system, not a link to the source shapefile or a local machine path, and not a download link to a SpatiaLite database. This is useful for quickly locating the file within the server environment after an update.

The key expands to the server-side path of the shapefile stored on FME Server. In a Log Action Formatted Message, this means you’ll see exactly where the updated shapefile resides on the FME Server file system, not a link to the source shapefile or a local machine path, and not a download link to a SpatiaLite database. This is useful for quickly locating the file within the server environment after an update.