Sharing 

Cloning an existing custom form to other projects.

• Existing customized forms can easily cloned to other projects you have access to. Take the following steps to clone an existing form to other projects
• Start from within the project by selecting ...More on the forms header bar.
• Click "Configure" next to the form you wish to clone.
• In the form properties, click the "...ellipses" button next to "Edit" selecting "Clone to another project".
• In the "Clone Form To Other Projects" dialog box, place a checkmark in the box next to each project you wish to clone the form to.
• With your desired projects selected, click the "Clone Form" button. If the form does not already exist in the destination project, you should receive a confirmation that the form has been cloned to the project.

Fields that you have at least 'Read' access to will be cloned over to the selected projects. Note that forms cloned to other projects apply permissions on the cloned fields on that form in the destination project to you only. For more information on applying form permissions, please reference the help section on Sharing

Cloning an existing system form to other projects.

Existing system forms come with standard system fields which are the same throughout all projects. Any system form can be cloned to other projects similar to the process noted above for custom forms. The purpose of cloning a system form would be to clone any custom fields that may have been added to the system form. For example if you created an Account Code field on the Contracts system form, you could clone the Contracts form to another project and that project would inherit the Account Code field.

Cloning Rules.

1. Forms are cloned based on the form's plural name.
2. Custom forms can only be cloned to a project if that form does not already exists for that user with that same form label.
   1. Examples
      1. User A clones Form A created by User A from Project 001 to Project 002. User A cannot clone this same form from Project 001 to Project 002.
      2. User B clones Form A created by User A from Project 001 to Project 002. User B is successful because Form A does not exist in Project 002 as User B being the creator of Form A
      3. User A changes the Form A label to Form B and clones this form to Project 001. Form B is cloned to Project 001 with the new form label name.
3. System forms can be cloned an indefinite number of times to another project including a project that the form has already been cloned to.
   1. Custom fields on system forms that already exist in the destination project that were created by the cloning user are skipped.
      1. Examples -
         1. User A creates Custom Field 1 on the Submittal Items form in Project 001 and clones Submittal Items to Project 002. User A then creates Custom Field 2 on the Submittal Items form and clones Submittal Items again to the same project, Project 002. Since Custom Field 1 already exists on the Submittal Items form in both the source and destination project for User A, this field will be skipped and only Custom Field 2 will be cloned.
         2. User B created Custom Field 1 on the Submittal Items form in Project 001 and clones that form to Project 002. Even though Custom Field 1 already exists on the form in Project 002, the clone is successful because each user can clone their own custom field with the same label to the same destination project.
4. Cloning a system form that contains both a system collection and custom collection apply the following rules.
   1. System Collection - Custom fields added to a system collection such as Contracts - Schedule of Values are cloned to the destination project. Additional custom fields that have been added to the system collection can also be cloned over to the project.
   2. Custom Collections - Custom fields added to a custom collection on a system form such as Contracts are cloned to the destination project. Additional custom fields that have been added to the custom collection are not cloned over to the project. Custom collections are only cloned once for any form.
5. All custom fields that you have Read or Read/Write access to will be cloned with the form.
6. Fields that are cloned along with the form are set to Read/Write access to the user who cloned the form, even if the source field was Read Only for the cloning user.
   1. Example
      1. User A creates a custom field on a form and grants User B and User C Read Only access to that field. User B clones that form to another project. Results - Only user B has Read/Write access to the custom field on the cloned form in the destination project.
7. Custom Fields that are not cloned or have special restrictions.
   1. Reference Collections - Not cloned.
   2. Account Codes - While the Account Code field itself is cloned, the Account Codes setup under Project Administration are project specific and therefore not cloned with the Account Code field.
      1. Account Code fields can only be cloned once per company, per project.
   3. Project Picklists - Project Picklists are project specific and therefore not cloned.
   4. Project Directory - Project Directory Company and Contact fields can be cloned to other projects, however only the field is cloned and not the actual Project Directory.
8. Custom Fields in Collections - Custom fields that have been created in a collection, including system form collections, can be cloned to another project.
9. Field Properties -
   1. Include Total - When cloning a form that contains collection fields Currency and Number where 'Include Total' is specified, the cloned fields will also show 'Include Total'.
   2. Include Row # - When cloning a form that contains a custom collection where 'Include Row #' is specified, the cloned collection will also show 'Include Row #l'
   3. Help Text - Cloning a form where Help Text is identified on custom fields, that Help Text will be cloned over to the destination project for that field.

Helpful Screenshots