Cloning a Business Object

role minimum version 2026 1 feature eligibility to use this feature, reach out to your ivanti account manager https //www ivanti com/lp/customers/contact/epg contact us to enable the enableclonebo feature flag for you cloning of business objects within ivanti production cloud/hosted environments is disabled off the shelf and is not be supported this feature is for development, staging, or uat environment only you can import the cloned business as a package into an ivanti production cloud/hosted environment the clone business object feature allows you to create a new business object by using an existing one as a template this process retains key configurations such as fields, layouts, grids, forms, and rules when setting up similar objects cloning a business object log in to as an open the configuration console > build > business objects > select the required business object such as grc policy under the details tab click clone business object at the bottom of the business object page enter a name for the new business object in the new bo name field and select the required fields to clone or check all if all the fields are required when you select check all , a dialog box appears so you can review auto generated relationships the cloning process captures relationships up to one level only create additional relationships manually if more levels are required business object names can include only letters, numbers, and underscores they must not start with a number or contain special characters click clone and click ok in the success pop up open the cloned business object and click save select one of the following options in the resolve indexing discrepancies dialog accept database indexes use the indexes stored in the database this ensures the cloned business object matches the database structure choose this if you want the system to follow the existing database configuration accept metadata indexes use only the indexes defined in metadata this ensures the cloned business object matches the metadata definition choose this if you want the system to follow the metadata configuration resolve later save the business object immediately and postpone resolving the indexing differences the next time you open the business object, you will be prompted again to resolve the discrepancies choose this if you need to save quickly, but you must resolve the issue before you can continue working with the business object if an index is created in metadata but the database does not support it (for example, if the name is already in use or reserved), the database does not create the index when the database and metadata become inconsistent, the application detects the discrepancy and prompts you to choose which version to use the cloning process also creates audit table for the cloned business object if the audit tables exist for the original business object does not retain locked permissions of the original business object and can be freely modified add cloned business object to top level tabs to show the cloned business object in the you need to add it to the top level tabs of that particular role for more information refer to defining top level tabs docid\ gt7r35f7dhfuezwdybaao handling non null fields during cloning, any field that is null but used in an index is automatically converted to non null on the clone this conversion allows the index creation to succeed apply full permissions full permissions are applied to cloned business objects, to ensure users can edit fields and manage relationships grant full access to the table in the frs def permissions database this change allows users to make updates and save changes grant full permission to each field so that users can make any changes grant full permission to reverse relationships update reverse relationship names to ensure uniqueness in the relationship designer names cloning a business object example cloning an incident business object requires adjusting null fields, relationships, and triggered actions to ensure the cloned object functions correctly log in to as an complete the cloning process for detailed steps, refer to cloning a business object docid\ bvc9ch9tp 569tgfwrsy3 open the configuration console > build > business objects > select the cloned business object> details and set the default form to \[name of the cloned business object] brief open layout > \[name of the cloned business object]layout servicedesk > formview \[name of the cloned business object] fix or remove entries with the error relationship is not found fix or remove correlated incidents because it contains a plugin click save navigate to business rules > triggered actions , and disable the following triggered actions add my item \[name of the cloned business object] update my item \[name of the business object] remove triggered actions for master incident disable the update correlated \[name of the cloned business object] triggered action update the quick action in the resolve button inside \[name of the cloned business object] defaultform form add the new business object to the top level tabs in roles and permissions for more information refer to defining top level tabs https //help ivanti com/ht/help/en us/ism/2026/admin user/content/configure/roles/setting up roles htm#definingtopleveltabs you can now load the form and create records limitations clone business object works only with the standalone business objects you cannot clone other type of business objects business object names can include only letters, numbers, and underscores they must not start with a number or contain special characters clone business object is designed for simpler business objects when used on very large and complex business objects (for example, an incident with more than 50 relationships), the cloned business object may not function seamlessly because of the number and complexity of relationships in such cases, manual steps are required to make the cloned business object functional cloning the account business object has known issues that will lead to failed operation do not clone the account business object the cloning process copies all other components of the business object except for the following components which you will add or edit them manually the roles , named relationship , and workflows are not copied during the cloning process you have to configure the related roles and workflows manually relationships and reverse relationships can only be cloned to the first degree transitive relationships can not be cloned automatically and must be handled manually self relationships are not cloned, as attempting to do so can create false links between the original business object and the new business object, breaking functionality business rules may need manual updates if they fail due to removed relationships special form command buttons bound by action ids must also be updated manually escalation is not functional when an incident is cloned this can be fixed manually by updating relationships and business rules update all the scripts in quick actions to the newly cloned business object for fields except for full text indexed and semantic enabled , all other field options or columns are cloned by default you need to enable and configure these options manually after cloning to enable full text indexed and semantic enabled , in the fields tab select the required field and select the full text indexed and semantic enabled options clear the cache every time in order to see the cloned business object in the business objects tab and to view any additional or manual changes of the clone business object to clear cache, go to configuration console > configure > cache management and select remove all cache items review both the cloned business object and any subsequent changes before deploying cloning a business object is a major operation use this feature only in development, staging, or test environments import your newly created business objects into production only after you have confirmed that they are functioning properly and as intended