Skip to main content

How to use Fin Operator with releases

Use Fin Operator to save proposed changes to a release, check for conflicts, set up a rollout or A/B test, and publish to main.

Written by Dawn Perrott

Use this article to save Fin Operator's proposed changes to a release, check a release for conflicts, set up a gradual rollout or A/B test, and publish a release to main.

Note: Fin Operator is included as part of the Pro add-on. You'll need the Pro add-on to access it.

What can Fin Operator do with releases?

Fin Operator can work with releases by helping you with the following:

  • Save the changes it proposes to a new or existing release.

  • Check a release for conflicts before you roll it out.

  • Set up an A/B test. Operator asks for the traffic split, audience, and any results analysis filter, then shows you a rollout plan to start.

  • Set up a gradual rollout or publish a release to main.

Operator always asks for your approval before it starts a rollout or publishes anything. It also follows your permissions, so you can only do what you could do in the release yourself.

How to save Fin Operator's proposed changes to a release

When Fin Operator proposes a change to an article, you can save it to a release instead of publishing it straight away. To save a proposal to a release:

  1. Ask Fin Operator for the change you want, for example an update to an article.

  2. Review the proposal in the review panel.

  3. Click the arrow next to Publish to open the menu.

  4. Under Save to release draft, choose an existing release, or click New release draft to create one. For a new release, enter a name, add an optional description, and click Create release. The name and description are for your team only, and Fin doesn't use them.

  5. Fin Operator saves the change to that release instead of publishing it to Main Fin.

A Fin Operator chat with an article proposal open in the review panel. The Publish menu is open and shows Save as draft, a Save to release draft list with the releases Refund processing changes, Test, and Alina test, and a New release draft option.
The Create a release dialog over a Fin Operator chat. The Name field is set to pricing change and the optional Description field is set to 29 to 39. A note says the name and description are for your team only and Fin doesn't use them. The dialog has Cancel and Create release buttons.

After you save the change, a release icon with a count appears next to the message box in the chat. Click it to see the release name, its status, and the items in it, then click Open release to go to the release.

The release summary open from the release icon next to the Fin Operator message box. It shows a release named pricing change with the status Draft and 1 edited, the item Managing Your Subscription of type Content with a plus 1 minus 1 change indicator, and an Open release button.

Choose Save as draft instead if you want to save the change as a new draft that isn't part of a release.

How to set up a rollout or A/B test with Fin Operator

To set up a gradual rollout or A/B test with Fin Operator, ask it to roll out the release you want. Operator asks for the traffic split, the audience, and any results analysis filter, then shows you a rollout plan. Nothing starts until you approve the plan.

To publish a release to main, ask Operator to publish it. Operator asks for your approval before it publishes.

Before Operator publishes, it summarizes what is in the release and what will change, and tells you that publishing puts the change on Fin Main immediately. It then asks you to confirm, and nothing is published until you reply yes.

A Fin Operator reply to the request can you publish this release to main. Operator summarizes the one change in the pricing change release, explains that merging puts the change on Fin Main immediately and can't be undone as a whole, and asks whether to merge it. Follow-up suggestions are Yes, merge it to main, Show me what will change, and How do I roll back.

After you confirm, Operator publishes the release and tells you the change is live on Fin Main. The release then shows the status Published. A published release can't be undone as a whole. To revert it, open the published release and click Roll back changes, then restore the earlier version of each item from Fin Main.

A Fin Operator reply confirming the pricing change release is merged, with a note that the merge can't be undone as a whole and to use Roll back changes in the merged release. The release summary shows the release pricing change with the status Published and 1 edited, listing the item Managing Your Subscription of type Content with the label Edited, and an Open release button.

Tip: For what each rollout option does and how to read the results, see How to roll out a release in Fin. New to releases? See Releases for Fin.

What can't Fin Operator do with releases?

  • Roll back a published release. Fin Operator can't roll back a published release. Use Roll back changes in the release instead.

  • Add a Data Connector change to a release. Operator can't add a connector change to a release.

Fin Operator and releases FAQs

Can Fin Operator publish a release without my approval?

Fin Operator can't publish a release or start a rollout without your approval. Operator always asks for your approval before it starts a rollout or publishes anything.

Can Fin Operator roll back a release?

Fin Operator can't roll back a published release. To roll back a release, use Roll back changes in the release. See How to roll out a release in Fin.

Do I need the Pro add-on to use Fin Operator with releases?

You need the Pro add-on to use Fin Operator with releases. Fin Operator is included as part of the Pro add-on.

💡Tip

Need more help? Get support from our Community Forum
Find answers and get help from Intercom Support and Community Experts

Did this answer your question?

Related Articles