Melinda Cozza - Power Platform and CMS Developer

If you are trying to using Power Automate and following "I Am Lu" s Tutorial and you get a Bad Gateway error in your power automate. The Key was not made correctly. I am not sure if it is because I am on a Mac and Lu is on a Windows but if you want the flow to connect to AWS then run the below command in your terminal to get the correct SSH Key.

ssh-keygen -m PEM

The key should start with:

-----BEGIN RSA PRIVATE KEY-----

To add the condition for the Admin token flow here> https://powerautomate.microsoft.com/en-us/blog/automate-flow-governance/

Condition Basic Edit does not exist anymore for you would do this instead.

In the first condition field put an expression containing:

@or(equals(items('Apply_to_each_2')['Operation'], 'CreateFlow'),equals(items('Apply_to_each_2')['Operation'], 'EditFlow'))

in the second field put in an expression containing:

Ran into this issue and the simple answer wasn't too easy to find.

GO into you view

Go to the "PAGER" section (in the middle)

1. First copy and paste the confirmation twig template for webforms in the webforms module.

Then add a div to the twig template like this.

<div id="learning-objective-data">  </div>

In the div place your webform submission data token for the field you would like to grab

{{ webform_submission.data.Your Webform Field }} 

So it looks like this:

<div id="learning-objective-data">
{{ webform_submission.data.question1 }} 
 </div>

<div class="summary">
 {% set text = content.body['#object'].body.summary|render %}
{{ text|length > 80 ? text|slice(0, 80)|raw ~ '...' : text|raw }}
{% set text = content.body['#object'].body.summary|render|striptags %}
{{ text|length > 80 ? text|slice(0, 80) ~ '...' : text }}
      
  </div>

Recreating the process that's on our site.

 Create Media type for the Colorbox image.
 a. Add media type
b. I named mine Lightbox image
c. Media Source
d. Media source configuration = -Create - 
e. Field mapping- I only used "Name" as "Name"
f. Publish options = "Published" is ticked
g. Click the sprocket and change the image size to what suits you
h. sAve
 

Trigger

When content is updated

condition

Text comparison

Data selector:  @rules.current_path_context:current_path.path

Operator: contains

Matching text (direct input mode) : /yourdisplaypath.  (For instance, mine was /steps)

For reference:

Node Author's email address:  {{ node.uid.entity.mail.value }}

Node created:  {{ node.created.value }}

Node Title: {{ node.title.value}}

Author's Username: {{ node.uid.entity.name.value }}

Node Edit Link:  your website/node/{{ node.nid.value }}/edit

Example of my rule message body:

Hi {{ node.uid.entity.name.value }},

I had to make a pretty easy change so yours may be more complex than what I needed.

I need the user to view a piece of content that had the start on our front page so they could follow the flow from the start. So I had the "Preview" button in the Node Add and Node Edit form re-direct them to the front page.
I found the code I needed to adjust in the node.routing.yml in Core Module Node.

We had a custom module where I put the below code into the MyModule.routing.yml file. I changed the path to '/'. which is the path to the front page.