1.2.6 Frame I/O to Workfront Fusion to AEM Assets
In the previous exercise you configured a scenario that automatically generates variations of an Adobe Photoshop PSD file using Adobe Firefly, Photoshop APIs and Workfront Fusion. The output of that scenario was a new Photoshop PSD file.
The business teams however don’t need a PSD file, they need a PNG file or a JPG file. In this exercise, you’ll configure a new automation that will result in a PNG file being generated once the asset in Frame I/O is approved, and that PNG file will be stored in AEM Assets automatically.
1.2.6.1 Create a new scenario
Go to https://experience.adobe.com/. Open Workfront Fusion.
In the left menu, go to Scenarios and select your folder --aepUserLdap--. Click Create a new scenario.
Use the name --aepUserLdap-- - Asset Approved PNG AEM Assets. Next, click the ? module, enter the search term webhook and then click Webhooks.
Click Custom webhook.
Click Add to create a new webhook.
Use the name --aepUserLdap-- - Frame.io Webhook. Click Save.
You should then see this. Click Copy address to clipboard.
1.2.6.2 Configure Webhook in Frame.io
Go to Postman and open the request POST - Get Access Token in the collection Adobe IO - OAuth. Next, click Send to request a new access_token.
In the left menu, go back to Collections. Open the request POST - Create Webhook in the collection Frame.io V4 - Tech Insiders, in the folder Webhooks.
Go to the Body of the request. Change the field name to --aepUserLdap-- - Fusion to AEM Assets and then change the field url to the value of the Webhook URL you copied from Workfront Fusion.
Click Send.
Your Frame.io V4 Custom Action has now been created.
Go to https://next.frame.io/project and go to the project that you created before, which should be named --aepUserLdap-- and open the folder CitiSignal Fiber Campaign. You should now see the assets that was created in the previous exercise.
Click the field Status and change the status to In Progress.
Switch back to Workfront Fusion. You should now see that the connection was Successfully determined.
Click Save to save your changes, and then click Run once to do a quick test.
Switch back to Frame.io and click the field In Progress and change the status to Needs review.
Switch back to Workfront Fusion and click the bubble on the Custom webhook module.
The detailed view of the bubble shows you the data that was received from Frame.io. You should see various ID’s. As an example, the field resource.id shows the unique ID in Frame.io of the asset citisignal-fiber.psd.
1.2.6.3 Get Asset Details from Frame.io
Now that the communication between Frame.io and Workfront Fusion has been established over a custom webhook, you should get more details about the asset for which the status label was updated. To do this, you’ll once again use the Frame.io connector in Workfront Fusion, similar to the previous exercise.
Hover over the Custom webhook object and click the + icon to add another module.
Enter the search term frame. Click Frame.io.
Click Frame.io.
Click Make a custom API call.
Verify that the connection is set to the same connection that you created in the previous exercise, which should be named --aepUserLdap-- - Adobe I/O - Frame.io S2S.
For the configuration of the module Frame.io - Make a custom API call, use the URL: /v4/accounts/{{1.account.id}}/files/{{1.resource.id}}.
{{1.account.id}} and {{1.resource.id}}. The number in the variable references the module in the scenario. In this example, you can see that the first module in the scenario is called Webhooks and has a sequence number of 1. This means that the variables {{1.account.id}} and {{1.resource.id}} will access that field from the module with sequence number 1. Sequence numbers can sometimes be different so pay attention when copying/pasting such variables and always verify that the sequence number used is the correct one.Next, click + Add item under Query String.
Enter these values and click Add.
includemedia_links.original
You should now have this. Click OK.
Click Save to save your changes and then click Run once to test your configuration.
Switch back to Frame.io and change the status to In Progress.
Go back to Workfront Fusion and click the bubble on the Frame.io - Make a custom API call module. You should then see a similar overview.
Next, you should set up a filter to ensure that only for assets that have a status that is Approved, a PNG file is rendered. To do that, click the Wrench icon between the modules Custom webhook and Frame.io - Make a custom API call and then select Set up a filter.
Configure the following fields:
- Label: use
Status = Approved. - Condition:
{{1.metadata.value[]}}. - Basic Operators: select Equal to.
- Value:
Approved.
Click OK.
You should then have this. Click Save to save your changes.
1.2.6.4 Convert to PNG
Hover over the module Frame.io - Make a custom API call and click the + icon.
Enter the search term photoshop and then click Adobe Photoshop.
Click Convert Image Format.
Verify that the field Connection is using your previously created connection, which is named --aepUserLdap-- - Adobe IO.
Under Input, set the field Storage to External and set the File Location to use the variable Original that is returned by the module Frame.io - Make a custom API call.
Next, click Add item under Outputs.
For the Outputs configuration, set the field Storage to Fusion internal storage and the Type to image/png. Click Add.
Click OK.
Click Save to save your changes and then click Run once to test your configuration.
Switch back to Frame.io and click the field In Progress and change the status to Approved.
Go back to Workfront Fusion. You should now see that all modules in your scenario have been executed successfully. Click the bubble on the Adobe Photoshop - Convert image format module.
In the details of the execution of the Adobe Photoshop - Convert image format module, you can see that a PNG file was now generated. The next step is to then store that file in AEM Assets CS.
1.2.6.5 Store PNG in AEM Assets CS
Hover over the Adobe Photoshop - Convert image format module and click the + icon.
Enter the search term aem and select AEM Assets.
Click Upload an asset.
You now need to configure your connection to AEM Assets CS. Click Add.
Use the following settings:
- Connection Type: AEM Assets as a Cloud Service.
- Connection Name:
--aepUserLdap-- AEM Assets CS. - Instance URL: copy the instance URL of your AEM Assets CS Author environment, which should look like this:
https://author-pXXXXX-eXXXXXXX.adobeaemcloud.com. - Access details fill options: select Provide JSON.
You now need to provide the Technical account credentials in JSON format. To do this, there are a number of steps to follow using AEM Cloud Manager. While you do that, keep this screen open.
Go to https://my.cloudmanager.adobe.com. The org you should select is --aepImsOrgName--. You’ll then see something like this. Click to open your program, which should be named --aepUserLdap-- - Citi Signal.
Click the 3 dots … and select Developer Console.
Click Sign in with Adobe.
Go to Tools > Integrations.
Click Create new technical account.
You should then see something like this. Open the newly created technical account. Click the 3 dots … and then select View.
You should then see a similar technical account token payload. Copy the full JSON payload to your clipboard.
Go back to Workfront Fusion and paste the full JSON payload in the Technical account credentials in JSON format field. Click Continue.
Your connection will then be validated and when successful, your connection will be automatically selected in the AEM Assets module. The next thing to do is to configure a folder. As part of the exercise, you should create a new dedicated folder.
To create a new dedicated folder, go to https://experience.adobe.com. Ensure that the right Experience Cloud instance is selected, which should be --aepImsOrgName--. Then, click Experience Manager Assets.
Click Select on your AEM Assets CS environment, which should be named --aepUserLdap-- - Citi Signal dev.
Go to Assetss and click Create Folder.
Enter the name --aepUserLdap-- - CitiSignal Fiber Campaign and click Create.
Your folder is then created.
Go back to Workfront Fusion, select Click here to choose folder and then choose the folder --aepUserLdap-- - CitiSignal Fiber Campaign.
Verify that the destination is set to --aepUserLdap-- - CitiSignal Fiber Campaign. Then, under Source File, select Map.
Under File name, choose the variable {{3.filenames[1]}}.
Under Data, choose the variable {{3.files[1]}}.
{{3.filenames[1]}}. The number in the variable references the module in the scenario. In this example, you can see that the third module in the scenario is called Adobe Photoshop - Convert image format and has a sequence number of 3. This means that the variable {{3.filenames[1]}} will access the field filenames[] from the module with sequence number 3. Sequence numbers can sometimes be different so pay attention when copying/pasting such variables and always verify that the sequence number used is the correct one.Click OK.
Click Save to save your changes.
Next, you need to set specific permissions for the Technical Account that you just created. When the account was created in Developer Console in Cloud Manager, it was given Read access rights but for this use case, Write access rights are required. You can do that by going to your AEM CS Author environment.
Go to https://my.cloudmanager.adobe.com. The org you should select is --aepImsOrgName--. Click to open your program, which should be named --aepUserLdap-- - Citi Signal. You’ll then see something like this. Click the Author URL.
Click Sign in with Adobe.
Go to Settings > Security > Users.
Click to open the Technical Account user account.
Go to Groups and add this Technical Account user to the group DAM-Users.
Click Save & Close.
Go back to Workfront Fusion. Click Run once to test your scenario.
Switch back to Frame.io and make sure the status of your asset is changed to Approved again.
Your Workfront Fusio scenario will then be activated and should complete successfully. By viewing the information in the bubble on the AEM Assets module, you can already see that the PNG file was successfully stored in AEM Assets CS.
Go back to AEM Assets CS and open the folder --aepUserLdap-- - Frame.io PNG. You should now see the PNG file that was generated as part of the Workfront Fusion scenario. Double-click the file to open it.
You can now see more details about the metadata of the PNG file that was generated.
You’ve now successfully completed this exercise.
Next steps
Go to Summary and Benefits of Creative Workflow Automation with Workfront Fusion
Go back to Creative Workflow Automation with Workfront Fusion
Go back to All Modules