Differences

This shows you the differences between two versions of the page.

adminhelp:generalsettings:deploysendchanges [2018/06/05 03:23]
atadic [Deploy Custom Fields]
adminhelp:generalsettings:deploysendchanges [2018/11/05 06:10] (current)
mnikolic
Line 1: Line 1:
 ====== Deploy / Send Changes ====== ====== Deploy / Send Changes ======
  
-The Deploy / Send Changes feature enables you to copy products and permission groups from one CPQ environment to another. You are able to create several versions of the same product and make any of those active at any time.\\+The Deploy / Send Changes feature enables you to copy products and permission groups from one SAP CPQ environment to another. You are able to create several versions of the same product and make any of those active at any time.\\
 Typical use: Typical use:
   * Promoting Product Models from Sandbox to Production   * Promoting Product Models from Sandbox to Production
Line 21: Line 21:
  
 <note> <note>
-If your product has any attribute of type **button**, which has a script attached to it, then when you send product to another destination, scripts are also sent along with the attribute. This was not supported by CPQ in versions earlier than 2016.1 but now it is. This is useful feature, since you do not have to manually add scripts to button attributes upon product deploy anymore.+If your product has any attribute of type **button**, which has a script attached to it, then when you send product to another destination, scripts are also sent along with the attribute. This was not supported by SAP CPQ in versions earlier than 2016.1 but now it is. This is useful feature, since you do not have to manually add scripts to button attributes upon product deploy anymore.
 </note> </note>
 \\ \\
Line 55: Line 55:
 ===== Deploy Permission Groups ===== ===== Deploy Permission Groups =====
 \\ \\
-When permission groups are copied between environments, CPQ will copy permission groups from source environment to destination environment.+When permission groups are copied between environments, SAP CPQ will copy permission groups from source environment to destination environment.
 If permission group that doesn’t exist in destination environment, it will be created there. All new relevant objects – manually created permission group, brands, user types, markets and companies will be copied from one environment to another. This does not include permissions based on users. New users will not be created in destination environment if manually created permission groups is used that contains users specified in it. If permission group that doesn’t exist in destination environment, it will be created there. All new relevant objects – manually created permission group, brands, user types, markets and companies will be copied from one environment to another. This does not include permissions based on users. New users will not be created in destination environment if manually created permission groups is used that contains users specified in it.
 If certain permission group exists in destination environment, no changes will be performed on it in destination environment by default. Admin can change this behavior by selecting checkbox ‘Update Existing Permission Groups’ if he wants to update existing permission groups with received data. If certain permission group exists in destination environment, no changes will be performed on it in destination environment by default. Admin can change this behavior by selecting checkbox ‘Update Existing Permission Groups’ if he wants to update existing permission groups with received data.
Line 62: Line 62:
 === Send New Change === === Send New Change ===
 \\ \\
-Admin is able to send changes to the desired CPQ environment. He has to select change type and click on button Continue in order to be redirected to Send New Change Page. When admin selects Permission Groups and clicks on ‘Continue’, page will be displayed where admin will be able to define details of the Permission Groups change:+Admin is able to send changes to the desired SAP CPQ environment. He has to select change type and click on button Continue in order to be redirected to Send New Change Page. When admin selects Permission Groups and clicks on ‘Continue’, page will be displayed where admin will be able to define details of the Permission Groups change:
   * Name (admin define name for the change)   * Name (admin define name for the change)
   * Description   * Description
Line 91: Line 91:
 //View sent change// //View sent change//
 \\ \\
-When admin clicks on ‘View’ sent change (for permission group), CPQ will display page that is similar to the one for sending new change. Difference will be that all fields will be read-only and button at the bottom will be labeled ‘Go Back’. +When admin clicks on ‘View’ sent change (for permission group), SAP CPQ will display page that is similar to the one for sending new change. Difference will be that all fields will be read-only and button at the bottom will be labeled ‘Go Back’. 
 \\ \\
 {{ adminhelp:generalsettings:permissionview2.png }}\\ {{ adminhelp:generalsettings:permissionview2.png }}\\
Line 97: Line 97:
 //Delete// //Delete//
 \\ \\
-Admin will be able to delete change that was sent from current environment. When admin click on ‘Delete’ icon, CPQ will prompt admin: ‘Are you sure you want to delete this change?’ Upon deleting change, message “Change ‘’ has been deleted “ will be displayed to admin.+Admin will be able to delete change that was sent from current environment. When admin click on ‘Delete’ icon, SAP CPQ will prompt admin: ‘Are you sure you want to delete this change?’ Upon deleting change, message “Change ‘’ has been deleted “ will be displayed to admin.
  
 ===== Deploy Products ===== ===== Deploy Products =====
Line 130: Line 130:
 {{:adminhelp:generalsettings:namecolumn.jpg?700}}\\ {{:adminhelp:generalsettings:namecolumn.jpg?700}}\\
 \\ \\
-When products are copied between environments, CPQ copies the permission groups used to define product visibility from the source environment to the destination environment.\\+When products are copied between environments, SAP CPQ copies the permission groups used to define product visibility from the source environment to the destination environment.\\
 If a permission group used for defining product visibility does not exist on the destination environment, it will be created there. All new relevant objects such as manually created permission groups, categories, brands, user types, markets and currencies will be copied from one environment to another (along with files used to describe the objects  - xslt files, branding images, CSS files, etc. New users will not be created on the destination environment if a manually created permission group that contains users specified on the destination environment is used. User identification will be done by using the username (System Id is not needed for users). If a user with the same username exists on the destination environment when a manually created permission group is being copied (and created), the user will be used in the permission group. If a user does not exist on the destination environment, the user will not be created and therefore not added to the manually created permission group.\\ If a permission group used for defining product visibility does not exist on the destination environment, it will be created there. All new relevant objects such as manually created permission groups, categories, brands, user types, markets and currencies will be copied from one environment to another (along with files used to describe the objects  - xslt files, branding images, CSS files, etc. New users will not be created on the destination environment if a manually created permission group that contains users specified on the destination environment is used. User identification will be done by using the username (System Id is not needed for users). If a user with the same username exists on the destination environment when a manually created permission group is being copied (and created), the user will be used in the permission group. If a user does not exist on the destination environment, the user will not be created and therefore not added to the manually created permission group.\\
 If a certain permission group exists on the destination environment, no changes will be performed on this permission group on the destination environment (the permission group will not be updated with new data from the source environment).\\   If a certain permission group exists on the destination environment, no changes will be performed on this permission group on the destination environment (the permission group will not be updated with new data from the source environment).\\  
Line 136: Line 136:
 ===== Deploy Cart Level Aggregates ===== ===== Deploy Cart Level Aggregates =====
 \\ \\
-When cart level aggregates are copied between environments, CPQ will copy cart level aggregates from source environment to destination environment, their name and expression. If cart level aggregates that is sent doesn’t exist in destination environment, it will be created there. If cart level aggregates that is sent exists in the destination environment, CPQ will update existing aggregates only if checkbox ‘Update existing Cart Level Aggregates’ is selected.+When cart level aggregates are copied between environments, SAP CPQ will copy cart level aggregates from source environment to destination environment, their name and expression. If cart level aggregates that is sent doesn’t exist in destination environment, it will be created there. If cart level aggregates that is sent exists in the destination environment, SAP CPQ will update existing aggregates only if checkbox ‘Update existing Cart Level Aggregates’ is selected.
  
 User can choose whether he wants to send all cart level aggregates or to define which cart level aggregates will be sent to desired environment. User can choose whether he wants to send all cart level aggregates or to define which cart level aggregates will be sent to desired environment.
Line 147: Line 147:
 If certain workflow data exists in destination environment, no changes will be performed on it in destination environment by default (it will not be updated with new data from source environment). Admin can change this behavior by selecting checkbox ‘Update Existing Workflows’ if he wants to update existing workflow tabs with received data. If certain workflow data exists in destination environment, no changes will be performed on it in destination environment by default (it will not be updated with new data from source environment). Admin can change this behavior by selecting checkbox ‘Update Existing Workflows’ if he wants to update existing workflow tabs with received data.
  
-When workflow tabs are deployed between environments, if it doesn’t exist, CPQ will create following data in destination environment+When workflow tabs are deployed between environments, if it doesn’t exist, SAP CPQ will create following data in destination environment
  
   * Statuses   * Statuses
Line 168: Line 168:
 ===== Deploy CRM Mappings ====== ===== Deploy CRM Mappings ======
 \\ \\
-Admin is able to deploy CRM Mappings from one CPQ environment to another. Admin is able to deploy following sections:+Admin is able to deploy CRM Mappings from one SAP CPQ environment to another. Admin is able to deploy following sections:
  
   * CRM Objects   * CRM Objects
Line 197: Line 197:
 ===== Deploy Markets, Territories and Currencies ===== ===== Deploy Markets, Territories and Currencies =====
 \\ \\
-Admin is able to deploy markets, currencies and territories from one CPQ environment to another one. He is able to deploy all markets, all currencies and all territories. +Admin is able to deploy markets, currencies and territories from one SAP CPQ environment to another one. He is able to deploy all markets, all currencies and all territories. 
  
 On page ‘Deploy/Send Changes’ under General sub menu, new entries will be added as option in Change type dropdown field: Markets, Territories, Currencies.  On page ‘Deploy/Send Changes’ under General sub menu, new entries will be added as option in Change type dropdown field: Markets, Territories, Currencies. 
-When Markets are copied between environments, CPQ will copy markets from source environment to destination environment:+When Markets are copied between environments, SAP CPQ will copy markets from source environment to destination environment:
   * If an market that is sent doesn’t exist in destination environment, it will be created there.   * If an market that is sent doesn’t exist in destination environment, it will be created there.
   * If certain market exists in destination environment, no changes will be performed on it in destination environment by default (Admin can change this behavior by selecting checkbox ‘Update Existing markets’ if he wants to update existing markets with received data).    * If certain market exists in destination environment, no changes will be performed on it in destination environment by default (Admin can change this behavior by selecting checkbox ‘Update Existing markets’ if he wants to update existing markets with received data). 
Line 208: Line 208:
 {{ adminhelp:generalsettings:markets.png }} {{ adminhelp:generalsettings:markets.png }}
 \\ \\
-When Currencies are copied between environments, CPQ will copy Currencies from source environment to destination environment.+When Currencies are copied between environments, SAP CPQ will copy Currencies from source environment to destination environment.
   * If an Currency that is sent doesn’t exist in destination environment, it will be created there.   * If an Currency that is sent doesn’t exist in destination environment, it will be created there.
   * If certain Currency exists in destination environment, no changes will be performed on it in destination environment by default (Admin can change this behavior by selecting checkbox ‘Update Existing data’ if he wants to update existing Currencies with received data).   * If certain Currency exists in destination environment, no changes will be performed on it in destination environment by default (Admin can change this behavior by selecting checkbox ‘Update Existing data’ if he wants to update existing Currencies with received data).
Line 217: Line 217:
 {{ adminhelp:generalsettings:currencies.png }} {{ adminhelp:generalsettings:currencies.png }}
 \\ \\
-When territories are copied between environments, CPQ will copy territories from source environment to destination environment:+When territories are copied between environments, SAP CPQ will copy territories from source environment to destination environment:
   * If an territory that is sent doesn’t exist in destination environment, it will be created there.   * If an territory that is sent doesn’t exist in destination environment, it will be created there.
   * If certain territory exists in destination environment, no changes will be performed on it in destination environment by default (Admin can change this behavior by selecting checkbox ‘Update Existing data’ if he wants to update existing territories with received data).   * If certain territory exists in destination environment, no changes will be performed on it in destination environment by default (Admin can change this behavior by selecting checkbox ‘Update Existing data’ if he wants to update existing territories with received data).
Line 229: Line 229:
 ===== Deploy Categories ===== ===== Deploy Categories =====
 \\ \\
-Admin is able to send changes to desired CPQ environment. He has to select change type and click on button Continue in order to be redirected to Send New Change Page (found under Setup->General->Deploy/Send Changes).+Admin is able to send changes to desired SAP CPQ environment. He has to select change type and click on button Continue in order to be redirected to Send New Change Page (found under Setup->General->Deploy/Send Changes).
 When admin selects Categories and clicks on ‘Continue’, page will be displayed where admin will be able to define details of the categories change:  When admin selects Categories and clicks on ‘Continue’, page will be displayed where admin will be able to define details of the categories change: 
   * Name (admin defines name for the change)    * Name (admin defines name for the change) 
Line 239: Line 239:
 {{ adminhelp:generalsettings:categ2.png }} {{ adminhelp:generalsettings:categ2.png }}
 \\ \\
- When categories are copied between environments, CPQ will copy categories from source environment to destination environment:+ When categories are copied between environments, SAP CPQ will copy categories from source environment to destination environment:
   * If a category that is sent doesn’t exist in destination environment, it will be created there. (All new relevant objects – images will be created if they don’t exist)   * If a category that is sent doesn’t exist in destination environment, it will be created there. (All new relevant objects – images will be created if they don’t exist)
   * If certain category exists in destination environment, no changes will be performed on it in destination environment by default (it will not be updated with new data from source environment). Admin can change this behavior by selecting checkbox ‘Update Existing category’ if he wants to update existing categories with received data. Following data are sent automatically to destination environment:  Categories, Images, Permissions, Parent categories. Sub categories are not sent automatically and has to be manually copied.   * If certain category exists in destination environment, no changes will be performed on it in destination environment by default (it will not be updated with new data from source environment). Admin can change this behavior by selecting checkbox ‘Update Existing category’ if he wants to update existing categories with received data. Following data are sent automatically to destination environment:  Categories, Images, Permissions, Parent categories. Sub categories are not sent automatically and has to be manually copied.
Line 248: Line 248:
 \\ \\
 For change that was sent, admin is able to:  For change that was sent, admin is able to: 
-  * View sent change (CPQ will display page that is similar to the one for sending new change, but all fields are read-only and button at the bottom is labeled ‘Go Back’)+  * View sent change (SAP CPQ will display page that is similar to the one for sending new change, but all fields are read-only and button at the bottom is labeled ‘Go Back’)
   * Delete (Admin is able to delete change which means removing entry about change that was sent from the table in current environment))   * Delete (Admin is able to delete change which means removing entry about change that was sent from the table in current environment))
 \\ \\
Line 265: Line 265:
 ===== Deploy Notifications ===== ===== Deploy Notifications =====
 \\ \\
-Admin is able to deploy all notifications or select which notifications to deploy to target CPQ environment. +Admin is able to deploy all notifications or select which notifications to deploy to target SAP CPQ environment. 
-When notifications are copied between environments, CPQ copies notifications from source environment to destination environment:+When notifications are copied between environments, SAP CPQ copies notifications from source environment to destination environment:
   * If a notification that is sent doesn’t exist in destination environment, it will be created there. (All new relevant objects – notifications, parsable attachments, non-parsable attachments, email lists and user types)   * If a notification that is sent doesn’t exist in destination environment, it will be created there. (All new relevant objects – notifications, parsable attachments, non-parsable attachments, email lists and user types)
   * If certain notification exists in destination environment, no changes will be performed on it in destination environment by default (it will not be updated with new data from source environment). Admin can change this behavior by selecting checkbox ‘Update existing Notifications’ if he wants to update existing notifications with received data.   * If certain notification exists in destination environment, no changes will be performed on it in destination environment by default (it will not be updated with new data from source environment). Admin can change this behavior by selecting checkbox ‘Update existing Notifications’ if he wants to update existing notifications with received data.
Line 278: Line 278:
 \\ \\
 For change that was sent, admin is able to:  For change that was sent, admin is able to: 
-  * View sent change (CPQ will display page that is similar to the one for sending new change, but all fields are read-only and button at the bottom is labeled ‘Go Back’)+  * View sent change (SAP CPQ will display page that is similar to the one for sending new change, but all fields are read-only and button at the bottom is labeled ‘Go Back’)
   * Delete (Admin is able to delete change which means removing entry about change that was sent from the table in current environment))   * Delete (Admin is able to delete change which means removing entry about change that was sent from the table in current environment))
 \\ \\
Line 296: Line 296:
 ===== Deploy User Types ===== ===== Deploy User Types =====
 \\ \\
-Admin is able to send changes to desired CPQ environment. He has to select change type and click on button Continue in order to be redirected to Send New Change Page (found under Setup->General->Deploy/Send Changes).+Admin is able to send changes to desired SAP CPQ environment. He has to select change type and click on button Continue in order to be redirected to Send New Change Page (found under Setup->General->Deploy/Send Changes).
 When admin selects User types and clicks on ‘Continue’, page will be displayed where admin will be able to define details of the User Types change: When admin selects User types and clicks on ‘Continue’, page will be displayed where admin will be able to define details of the User Types change:
   * Name (admin defines name for the change)    * Name (admin defines name for the change) 
Line 305: Line 305:
 {{ adminhelp:generalsettings:deployusertypes.png }} {{ adminhelp:generalsettings:deployusertypes.png }}
 \\ \\
-When user types are copied between environments, CPQ will copy user types from source environment to destination environment:+When user types are copied between environments, SAP CPQ will copy user types from source environment to destination environment:
   * If user type that is sent doesn’t exist in destination environment, it will be created there (All new relevant objects – category, all xslt files will also be created if they don’t exist).   * If user type that is sent doesn’t exist in destination environment, it will be created there (All new relevant objects – category, all xslt files will also be created if they don’t exist).
   * If certain user type exists in destination environment, no changes will be performed on it in destination environment by default (it will not be updated with new data from source environment). Admin can change this behavior by selecting checkbox ‘Update Existing User Types’ if he wants to update existing user types with received data.   * If certain user type exists in destination environment, no changes will be performed on it in destination environment by default (it will not be updated with new data from source environment). Admin can change this behavior by selecting checkbox ‘Update Existing User Types’ if he wants to update existing user types with received data.
Line 316: Line 316:
 \\ \\
 For change that was sent, admin is able to:  For change that was sent, admin is able to: 
-  * View sent change (CPQ will display page that is similar to the one for sending new change, but all fields are read-only and button at the bottom is labeled ‘Go Back’)+  * View sent change (SAP CPQ will display page that is similar to the one for sending new change, but all fields are read-only and button at the bottom is labeled ‘Go Back’)
   * Delete (Admin is able to delete change which means removing entry about change that was sent from the table in current environment))   * Delete (Admin is able to delete change which means removing entry about change that was sent from the table in current environment))
 \\ \\
Line 341: Line 341:
 {{ adminhelp:generalsettings:deployapprule.png }} {{ adminhelp:generalsettings:deployapprule.png }}
 \\ \\
-When approval rules are copied between environments, CPQ copies approval rules from source environment to destination environment:+When approval rules are copied between environments, SAP CPQ copies approval rules from source environment to destination environment:
   * If approval rule that is sent doesn’t exist in destination environment, it will be created there. (All new relevant objects – approval rules, custom approver selection logic, user types and companies)   * If approval rule that is sent doesn’t exist in destination environment, it will be created there. (All new relevant objects – approval rules, custom approver selection logic, user types and companies)
   * If certain approval rule exists in destination environment, no changes will be performed on it in destination environment by default (it will not be updated with new data from source environment). Admin can change this behavior by selecting checkbox ‘Update existing approval rules’ if he wants to update existing approval rules with received data.   * If certain approval rule exists in destination environment, no changes will be performed on it in destination environment by default (it will not be updated with new data from source environment). Admin can change this behavior by selecting checkbox ‘Update existing approval rules’ if he wants to update existing approval rules with received data.
Line 350: Line 350:
  
 For change that was sent, admin is able to:  For change that was sent, admin is able to: 
-  * View sent change (CPQ will display page that is similar to the one for sending new change, but all fields are read-only and button at the bottom is labeled ‘Go Back’)+  * View sent change (SAP CPQ will display page that is similar to the one for sending new change, but all fields are read-only and button at the bottom is labeled ‘Go Back’)
   * Delete (Admin is able to delete change which means removing entry about change that was sent from the table in current environment))   * Delete (Admin is able to delete change which means removing entry about change that was sent from the table in current environment))
  
You are here: CallidusCloud SAP CPQ Online HelpAdmin Page HelpGeneral SettingsDeploy / Send Changes