Version Stack Data on Custom Actions

Feedback
,
1

Hi Frame and community,

I just wanted to drop a quick bit of feedback for the custom actions payloads. I’m working on an integration with our application (Bynder.com). One of our core features is version control on assets for distribution, and ideally we’d have an easy way to track versions between systems. I noticed that the custom action triggered on an asset or a version stack is the same, which makes it complicated for us to determine whether an asset is part of a stack or not.

I know we’ve got some workarounds we can handle, but thought I’d suggest something in the action payload to identify that an asset belongs to a stack. Even just a single field identifying the stack ID would make version control between applications a bit easier.

2

hi @BillKeiffer just so I’m understanding correctly, are you saying that if you use a custom action on a file or version stack (they are separate asset types in frame), there is no way to differentiate between the two in the response that is returned?

3

Yeh, that’s been my experience in testing so far. A triggered action on a single asset and a triggered action on a version stack are the same…with the version stack being the payload of the top asset in the stack.

4

Got it, thanks for the confirmation. I will add a ticket to address this in the future.