Copying Notification Events | Fyno Documentation

Notification events can be copied from your workspace to other workspaces you own. The copy process is only available in workspaces where you have the Owner role.

Steps to copy notification events

1. Prepare your destination workspace

It is important to note that when copying notification events, only the notification event-related data will be copied to the destination workspace. Any dependencies must be created or copied manually in the destination workspace.

1Manually create the required integrations in the workspace.

2Go to the templates page (Templates → Fyno from the navigation) and copy the templates and reusable components (if applicable) used by any of the notification events in the notification event via the copy process.

3If applicable, go to the “Routes” pages (Routes → Single Channel and Routes → Omni-Channel from the navigation) and copy the routes used by any of the notification events in the notification event via the copy process.

4If the notification events use Analytics Labels, then manually create the labels on the “Add Ons” page.

5If the notification event uses Subscription Topics, then manually create and configure the topics on the User Preferences page (User → Preferences from the navigation).

2. Copy your notification event(s)

1Ensure you are in the workspace from where you would like to copy the notification event.

2Navigate to the notification events listing page by selecting Notification Events from the navigation.

3Click the “Three Dots” icon on the notification event that you would like to copy. This step will open a menu.

4In the menu options, select “Copy to another workspace”.

5You will now see a checkbox next to every notification event listed on the page. You can select multiple notification events to copy if needed.

6Once you have completed your selection, click “Copy Selected Notification Events” in the alert above the listing.

7When copying a single notification event that has a live version, you will see an option to copy either the latest live or test version. If your notification event only has a test version, that version will be copied.

8When copying multiple notification events, the latest live or the latest test version will be copied, depending on the notification event.

9You will now see a dialog box with an option to select destination workspaces. In the “Destination Workspace(s)” dropdown menu, you will see all the workspaces you are a member of, but only the ones in which you have the “Owner” role will be available for selection. You can select up to five applicable workspaces.

10Once all the workspaces are selected, click “Confirm”. This step will initiate the copy process.

11Now, in all the selected workspaces, you will see the copied notification events.

3. Post copy checklist

1If the copied notification event is associated with a subscription topic, click the “Three Dots” icon on the notification event in the listing page, click “Edit”, select the topic in the “Select Subscription Topic” dropdown, and click “Update”.

2For every copied notification event, re-select the templates (including conditional templates if applicable).

3Re-select the routes and/or integrations and save the notification event.

4Similar steps are needed in other copied dependencies. Please see the post copy checklist for routes.

How versioning works

Let’s say we are copying a notification event from Workspace A to Workspace B. There are two versioning scenarios to keep in mind.

If the notification event does not exist in Workspace B, then the version created by the copy process will always be v1 (Test).

If the notification event already exists in Workspace B, then the copy process will create a new standalone version (neither test nor live). For example, if the version in Workspace B is v1 (Test), then the process will create a new version called v2. You can select this version from the version dropdown beside the notification event name and click “Save” to change the version to v2 (Test), or click the “Go Live” button to promote it to v2 (Live). This ensures that changes to existing versions in the destination workspace are not overwritten and gives you control over when to save or promote the copied notification event.