(View in full screen)

While building a data pipeline, you may need to collaborate with others to create, maintain, and validate your orchestration work. Trifacta allows you to easily share your work with others, allowing teams to complete the work faster and with more oversight. You can grant another user access to one of your plans to do co-development and take turns updating the plans.

Share your Plans

Users can share plans with other users. The option to share a plan can be found on the Plans Page.

When a plan is shared, the user's permissions determine the available actions.

When a user is provided access to a plan, the user becomes a collaborator on the plan and is assigned a subset of the permissions assigned to the owner of the plan.

A collaborator on a plan cannot delete the plan.

For more details, see Share a Plan

Example

1. In Plans page, hover over the Plan you would like to share and click on the Share option that appears

OR

In the Plan View, click the Share button on top


2. A Share Plan dialog will open.

3. You can enter the names of one or more collaborators into the flow here, so that you may work together on the same objects.

5. Click Save to finish.

Note, when a plan is shared, the Plan object and HTTP Tasks are shared. The following objects are not shared:

  • Underlying flow are not shared

  • Plan schedules are not shared

Similarly, the plan can be executed only if the user has access to all the underlying flow tasks. Learn more about Sharing of Plans here.

Email Notifications

Users will receive notifications whenever a plan is shared with them.

  • The email provides a direct link to view the Plan

Email notifications can be toggled in the Email notifications page of the user's preferences in the application. For more information, see the Email Notifications Page.

Schedule Modification by Collaborators

Starting v8.6, you can edit the schedules of Plans shared with you as a Collaborator

This is based on an option available to the workspace admin called Editor Scheduling. A user will be able to schedule or edit schedules of Plans shared with them if this option is Enabled (default state) in the Admin console > Workspace Settings.


Export your Plans

You can export a Plan to import into another environment. Plan exports are useful for:

  • Copying a plan to another environment.

  • Backing up the work in progress on your plans

  • Archiving of completed development work

  • Integrating with version control software

Plans are exported as a zip file. The exported zip file contains a JSON file for the plan and JSON files for each of its associated flows. The plan and its assets are exported into the plan definition file.

For each flow included in the plan:

  • Each flow is exported only once in a flow definition file, even if it is used in many plan flow tasks.

  • If the flow contains any artifact files, they are included as .data files next to the plan definition file. These files should be imported with the flow, too.

When you export the plan ZIP file, a snapshot of the plan is taken at the time of export.

Learn more about Exporting a Plan here

Import a Plan

An exported plan can be imported into a Trifacta environment of the same version or higher.

Limitations

  • You cannot import a plan that was exported in a later release.

  • You cannot import schedules while importing a plan.

  • You cannot modify plan definitions outside of the Trifacta application.

Note that when you import a plan, the corresponding flow tasks and HTTP tasks in the plan are also imported.

Steps:

  1. Navigate to the Plans page.

  2. From the context menu of the Plans page, select Import.

  3. From the Import Plans window, select the exported zip file from your system and click Open.

Starting v8.8, you may select multiple Plans for Import at once.

The plan is imported and available for use on the Plans Page.

Learn more about Importing a Plan here.

More Info

To know more about Plans, read this detailed article

Visit our detailed documentation guide to learn more about sharing options.

Did this answer your question?