What’s New at Pinkfish – Product Updates
Collections for Data Store, File Store, and Vault We’ve introduced the concept of Collections for Data Store, File Store, and Vault.
A Collection is now scoped to the organization in which it was created—it will only be visible to that org.
You can share or delete an entire Collection as a single unit, making management simpler and more consistent.
Important Note This feature upgrade may require manual steps on your end to ensure the automation functions as expected.
Post Upgrade User Action Required (Show Details)
We have migrated to the new Data Collections model, where your Datastore, Vault, and Filestorage items will now exist within a “Collection” that can be shared to other individuals and to your organization.
We discovered one edge case that we’d like to share with you that will require an automation script change if you fit the criteria below.
If you created an automation prior to March 16th and used the Datastore, Filestore, Vault, or Browser-Login you will need to make a small modification to your script.
Your script will invoke the datastore as shown here:
The fetch path you see in your script will be slightly different depending on the service you are using:
To update to use the new Collections, you’ll need to
config.bearerToken
config.runtimeToken
And then re-run and re-publish.
Billing & Usage Updates - We’ve streamlined billing and usage visibility across plan tiers:
New Org Types: Enterprise Prime & Sub Until now, all organizations functioned the same way. We’re now introducing org types to distinguish between Enterprise and non-Enterprise accounts.
This change ensures better governance and clarity in multi-org enterprise setups.
Happy automating! 🚀
What’s New at Pinkfish – Product Updates
Collections for Data Store, File Store, and Vault We’ve introduced the concept of Collections for Data Store, File Store, and Vault.
A Collection is now scoped to the organization in which it was created—it will only be visible to that org.
You can share or delete an entire Collection as a single unit, making management simpler and more consistent.
Important Note This feature upgrade may require manual steps on your end to ensure the automation functions as expected.
Post Upgrade User Action Required (Show Details)
We have migrated to the new Data Collections model, where your Datastore, Vault, and Filestorage items will now exist within a “Collection” that can be shared to other individuals and to your organization.
We discovered one edge case that we’d like to share with you that will require an automation script change if you fit the criteria below.
If you created an automation prior to March 16th and used the Datastore, Filestore, Vault, or Browser-Login you will need to make a small modification to your script.
Your script will invoke the datastore as shown here:
The fetch path you see in your script will be slightly different depending on the service you are using:
To update to use the new Collections, you’ll need to
config.bearerToken
config.runtimeToken
And then re-run and re-publish.
Billing & Usage Updates - We’ve streamlined billing and usage visibility across plan tiers:
New Org Types: Enterprise Prime & Sub Until now, all organizations functioned the same way. We’re now introducing org types to distinguish between Enterprise and non-Enterprise accounts.
This change ensures better governance and clarity in multi-org enterprise setups.
Happy automating! 🚀