Projects

SelectProjects > Manage Projects.

Use the Projects page to bring togetherFME Flowitems into groups that share a common solution, or 'project', in your organization. By grouping items in projects, you can reference them in one easy place. You can also export projects and import them to another instance ofFME Flow.

Why Create a Project?

The primary benefit of projects is the ability to migrate them betweenFME Flows. This feature is especially useful when deploying anFME Flowscenario through the enterprise life cycle, from development to testing/staging to production. Instead of backing up and restoring an entireFME Flowconfiguration, you can simply export the project, and import it to anotherFME Flow. The targetFME Flowconfiguration remains intact, with the addition of the new project and all of its contents.

What Can a Project Hold?

A project can include just about anyFME Flowobject you create or upload.

Creating a Project

1. Do any of the following:
   1. ClickCreateto open the New Project page. Or, to create a project from an existing project, select a project and clickDuplicate.
   2. SelectProjects>Create Project.
2. Provide aNameandDescriptionfor the project.
3. (Optional) If desired, update the projectVersion. The specified version is appended to the .fsproject file name when youexportthe project.
4. Add aReadme工具栏项目,使用减记德西red. If you plan to upload the project to FME Hub, either in the next step or at a later time, a readme may help users learn more about your project.
5. To upload the project toFME Hub(optional), enableInclude FME Hub Detailsand complete the following:
   • FME Hub Publisher ID: The Unique ID associated with the FME Hub Publisher.
   • FME Hub Project ID: Enter a unique identifier for the project.
   • Project Icon: To display an icon with the project, clickUpload New Icon. The following image types are supported: .bmp, .jpg, .jpeg, .svg, .webp, .png (transparency supported), .gif (animation not supported). For best results, provide an image that is larger than 200x200 pixels.
6. To add items to the project, clickAdd Items. In the Add Items dialog, specify theItem Typeand any applicable filters (for example, if the item is aWorkspace, specify theRepository). To narrow the list of items, use theSearchfield. UnderNAME, click+beside the items you want to add.

When you add items, they appear under Selected Items. If you have added items that depend on other items to run (for example, a schedule that runs aworkspace), these dependencies are added as well. To view dependencies, click the expand icon beside the name of the item you added.

Note  "> NoteWhen adding items, keep in mind the following:
• To add users (other than your own account), you must belong to the fmesuperuserrole. API tokens owned by users are not included in projects to which they are added, unless the tokens are explicitly added.
• Anyone can add API tokens to a project; however, whenimporting a projectto another system, one of the following must be true: 1) You belong to the fmesuperuser role; and 2) The owner of the project conducting the import has the same user account on the target system.
• Adding Resource folders includes the folder and all of its contents.
7. To remove items already added, clickxbeside the corresponding item.
8. When finished selecting items to add, clickAdd Itemsto close the Add Item(s) dialog.
9. 创建项目页面显示。项目内容lists all the items added, including their dependencies. To remove unwanted items, select them and clickRemove.
10. To add the project, clickSave.

Exporting and Importing a Project

You can export the contents of a project, and import the project to the same instance, or another instance, ofFME Flow. For example, you can migrate a project when you are ready to use it on a production server after you have developed and tested its contents on a separate system. For more information, seeExporting and Importing Projects.

Migrating Projects for Other Users (fmesuperuser only)

When you include users in a project, you can export and import a project for those users to work with on another system. Any permissions a user has on the current system are granted on the system to which the project is imported, if both of the following conditions are true:

• The permission is on an item in the project.
• The permission was granted to the user directly, rather than through membership in a role. (For more information, seeViewing and Configuring User Permissions and Other Settings.)

Any other permissions a user has on the current system do not carry over. API tokens owned by users are not included in projects to which they are added, unless they are explicitly included.

Viewing and Editing Projects

To view or edit a project, click on the name to open the page for the project.

• To edit the project name, description, or version, click the edit icon beside them.
• To view information about items in the project, click the item name.
• To view the dependencies of a project (items that were automatically added to the project because they are required to run items that were explicitly added, such as aworkspacerun by a schedule), click the ellipsis (...) underACTIONScorresponding to the project, and selectView Dependencies.
  Note  "> Note FME Flowautomatically adjusts dependencies to projects based on changes to project contents. For example, if a Run aWorkspaceaction is removed from an automation that is in a project, thatworkspaceis removed as a dependency of the project.
• To add items to the project, clickAdd Items.
• To remove items from the project, select one or more items and clickRemove.

Under theActionsmenu, you can:

• View the FME Hub details for the project, if applicable.
• Duplicate the project.
• Export the project. For more information, seeExporting and Importing Projects.
• Share the project. For more information, seeSharing Projects(below).
• Remove the project. For more information, seeRemoving Projects(below).

Sharing Projects

To share a project, click the Share with Others icon. Through sharing, you can grant levels of permissions on an item to other users. You can share an item if you own it, or if you are a user with Manage permission in Security, such as an administrator. For more information about sharing and ownership, seeRole-Based and User-Based Access Control.

Removing Projects

To delete a project, select it and clickRemove. To remove the contents of the project along with the project, checkAlso remove contentson the Warning dialog. To remove only the project and leave its contents on the Server, leave this box unchecked.

TheAlso remove contentsoption is useful when youexport a project, and then make subsequent changes to it, including deleting items from the project. If you want the project to match the state it was in when it was exported, select this option. Then, perform an in-placeimport, on the same server.

IfAlso remove contentsis checked, keep in mind the following:

• Only items for which the user has permission to delete are removed.
• If the project contains the user performing the remove, or the role to which the user belongs, neither the user nor the role is deleted.
• NoSystem Eventsare triggered. For example, if a repository is removed, the Repository Delete event is not triggered, even if enabled.