Automations: Ability to pass workspace published parameters through workflow

Relates to:

https://knowledge.safe.com/questions/93175/how-to-trigger-workspace-using-an-upstream-workspa.html

https://knowledge.safe.com/questions/95024/fme-server-automations.html

I really would like to see this functionality added!

Scenario 2:

My Automation is triggered by a Topic, in this case since the JSON format is not known I must use a workspace to extract these attributes, I would then like to parse these attributes out of the workspace to use in an External Action.

Stems from https://knowledge.safe.com/questions/97102/sending-processed-subscriber-content-from-topic-in.html

This would help a lot in message broker-like scenarios. There's definitely demand for it!

I am pleased to let you know that in FME 2020 we will be releasing a new FME Server Automations Writer which will enable you to pass Feature Types and their associated attributes out of the Workspace and into the Automations workflow.

When an Automations Writer has been added to your workspace this Feature Type will appear as an additional output port on the Run Workspace node in Automations. All attributes that are received by this writer will appear as Output Keys on that action meaning they can be used on their own or within the Text Editor to populate parameters for following actions.

Scenario 1 - Filter & Job Chain

• https://knowledge.safe.com/questions/95024/fme-server-automations.html

• https://knowledge.safe.com/questions/93175/how-to-trigger-workspace-using-an-upstream-workspa.html

• https://knowledge.safe.com/questions/98851/filter-workspace-output-in-fme-server-automations.html

In this example the first workspace validates the incoming data, however if the data is invalid, this is being stored in an attribute value but the translation does not fail, so I need to be able to perform a Filter Action based on the value of this attribute, rather than relying on the translation status to say whether the Automation can proceed.

'

Once filtered I need to set up a job chain but I need to use the output dataset of the first workspace as the source dataset in the next. In the Process-Data workspace I have used a Feature Writer and can then attach the Summary port, which includes an attribute containing the destination dataset file path, to my Automation Writer. Just like with the Filter I can then set the Source Dataset in my final Workspace to this attribute value.

'

Scenario 2 - Parse Topic Message into Email Body

• https://knowledge.safe.com/questions/97102/sending-processed-subscriber-content-from-topic-in.html

In this example, I set up an FME Server Topic to receive Survey123 details when a form was submitted. I would like to send out this information in an email, but the incoming topic message is stored as JSON, so I first want to use a workspace to parse this data into easily readable attributes that can be used to help form part of the email body.

By connecting an Automations Writer to the JSONFragmenter output I can then use the exposed attributes within the Text Editor in Automations.

'

This is great news, thanks!