Data360 Govern

We use workflows to trigger the creation of new assets. One step includes an action form where the receipient indicates which type of asset should be created and includes a comment. 

We'd like this comment to map to a field "Reviewer Comments" that we have on the asset, but it is not available in the list of fields for HTTP requests. 

When you say you use it as a trigger to create an asset, I presume you are running the simple Govern workflow and then using Analyze to do the actual creation on the asset based on the type created.

Is that correct or are you using some other method to create the asset?

If you are using Analyze then the workflow itself must be getting pulled into your flow in order to trigger the creation and therefore you have all the workflow details you need to be able to passed the comment to the HTTP node and create the JSON payload for both creation and any fields value to be set.

Hi John - We're using an HTTP request within the Govern workflow (this is a relatively new Govern feature) 

ok, so you are doing the JSON payload creation directly in Govern and using the HTTP node to PUT the request to the end point..

It works in the same way as any PUT payload, so you will just need to include a piece of JSON for the FIELDS: to be set when you create the new asset?

Would you mind sharing the payload you having the Body part of the HTTP at the moment and we can edit it to include the fields to need to set.

We're able to post all of our action fields (from the initital workflow form) to the new asset, but fields that came from subsequent forms aren't able to post. 

Hope this helps: 

The workflow starts with a user completing a form. We then email a data owner asking for comments before building the asset. We're able to create the asset with action fields from the initial form, but the "comment" field in the purple step isn't an option to call: 

I want form fields to be an available field (currently we can only choose from Action Field and Asset Field)

Arrgh ok so now I see the issue. The field from the workflow form can't be used in the payload.

Well you can do it - but you have to think out the box a little bit, it's not a straightforward process.

So what you want to do is add a text field to your original action form, you want to set the field not to be displayed on the detail page and you want to set it not to be editable. The creator / requestor is not going to see that field on their workflow form, but it will be there. That's the trick.

You can then create a lovely workflow in Govern that will allow you to make the Form the first step. Just created the form as you have it today - the True/False approval status and the comments. These will be bound to the workflow form and not the action form, but that doesnt matter.

You can then use a field change workflow node to update that hidden text field from the original action form with the input from the form, thus updating the Action form to have the comments from the Approver and the HTTP will allow you to use the Action field in the payload.

Let me know how you get on with doing it that way and if you struggle I would be more than happy to jump on a quick teams call.

Good luck :)

Thanks John!! I'll give that a try

Hi John - Have you had success changing an action field? I keep getting an error

Yeah I managed to get it working using the Govern workflow I posted in the previous post.

1) Step 1 is the original Action form with then hidden comments field

2) Step 2 is the email sent to the approver.

3) Step 3 is the form sent in the email

4) Step 4 is the creation of the new asset using the comments from Step3  / Approval Form

===========================================================

The field change node in the Govern workflow is the key to swapping the value. The output will show FALSE as mine does below, but the value will still update on the form.

What response code did you get from the HTTP node?

As you can see from the screenshot above, I did manage to use that comments field from the approval form to add in as the action form field in the POST payload.

Did you see your asset created without the comments? or did it fail to create at all?

I'd accidentally entered the API name for the action instead of the asset. This is working now. Thanks John! I really appreciate all of your help.