What a copy leaves behind
A copy makes a new Button in the OneClick of a customer. The copy does not take secret values with it. It also does not take the settings that have a meaning only in the source company. Before the customer uses the copy, an admin of the customer must complete these settings in OneClick.
The source Button stays
Section titled “The source Button stays”A copy does not move the Button. The source Button stays in its company and does not change. To remove the copy, an admin of the customer deletes it in OneClick.
Copy and transfer are the same operation
Section titled “Copy and transfer are the same operation”The Partner Portal calls the operation Copy. OneClick calls it a Partner portal transfer. It is the same copy as a transfer in OneClick, with two differences:
- You do not need a transfer-enabled API key. Your Partner owns the customer, and this gives the permission.
- OneClick shows Zimple Partner Portal in place of the label of an API key.
What the copy leaves behind
Section titled “What the copy leaves behind”| Setting | What the copy has |
|---|---|
| Header values | Each header has the value “Set your own value”. No header is confidential. |
| Confidential Interface variables | The values are empty. The key of each variable ends with “(recreate this variable with the correct value)”. |
| Auth token | The copy has no auth token. |
| Visibility limits | The pipelines, the stages, the users and the groups are removed. The scopes stay. |
| Default values of filter fields and user fields | The values are empty. Filter fields also lose their allowed filters. |
| Signed link | The parameter name and the token lifetime stay. The secret is empty. |
| Button group | The copy is not in a group. |
| Template | The copy of a Template Button is not a Template Button. |
The copy shows in all pipelines to all users until an admin of the customer sets the visibility limits again.
Complete the copy
Section titled “Complete the copy”An admin of the customer does these steps in the OneClick settings of the customer.
- Open the copy. Its name ends with “(transferred)”.
- Type the correct value of each header.
- Make the secret headers confidential again.
- Type the values of the confidential Interface variables.
- Remove “(recreate this variable with the correct value)” from the key of each confidential Interface variable.
- Set the visibility limits again. See Limit visibility.
- Select the Pipedrive custom fields of the customer company again. A custom field of the source company is not in the customer company.
- Set the allowed filters and the default values of the filter fields and the user fields again.
- Make a new secret for the Signed link.
- Save the Button.