Cloning and importing objectives
Depending on your organization's project or framework configuration, objectives may also be called sections, processes, cycles, functional areas, application systems, or another custom term.
Clone or import objectives to build out your own templates or programs, re-use existing projects or frameworks, or execute a similar process in a different location.
Before you start
Before you can clone or import objectives, you need to:
- Create the source and target projects and/or frameworks.
- Define objectives in the source project or framework (if you want to clone or import your own objectives).
- Ensure that both your source and target projects and/or frameworks have the custom attributes and fields you need.
Requirements
Cloning or importing objectives requires that both the source and target project and/or framework:
- have project types that are the same workflow (Internal Control or Workplan)
- have the same number of testing rounds (applicable to Internal Control workflow only)
Objectives imported from Content Library are compatible with both Workplan and Internal Control workflows.
How it works
Cloning objectives
When you clone an objective, you are adding an exact copy of the objective to the same project/framework, or to another project/framework. You can clone objectives from active projects and frameworks within the same Diligent One instance or to different Diligent One instances.
You can only clone one objective at a time.
Importing objectives
When you import an objective, you are copying information from one location in Diligent One to another. You can import objectives from active projects, archived projects, frameworks within the same Diligent One instance, or the Content Library.
You can import multiple objectives at one time.
You can import objectives from frameworks as part of your assurance plan setup. For more information, see Overview of Assurance Plans.
Considerations and limitations
Limitations
You can define a maximum of 500 objectives per project or framework.
How items are copied when project types are different
When cloning or importing an objective, if the target project or framework has a required field that is blank, the first available value from the required field is chosen.
Example
You are importing an objective (containing risks and controls) from Project A to Project B. The projects have different project types.
The Prevent or Detect? control field in Project A is blank. When you import the control to Project B, the field will also be blank. However, because the field is required, this will cause the import process to fail.
To complete the import process successfully, the first available value (Prevent) is automatically chosen from the following list of values: Prevent, Detect, N/A.
Items copied only when project types are the same
The following items are copied only if the project type of the source project and target project are the same:
- assessment drivers and linked metrics
- custom risk scoring factors
- custom date fields
- custom attributes
If the project type of the source and target project or framework are not the same, only field values from the above items are copied.
Including project results
You have the option to include project results in the target project when you import an objective from an active or archived project to another active project.
Project results include:
- Execute Procedures/Walkthroughs
- Tests
- Issues (issue information, remediation plan, and retesting information)
- Requests associated with the above items
- Actions
- Latest versions of attachmentsNote
If you have linked files in Citation Mode, only files uploaded on the Objective page, or on pages associated with the Objective (Narrative, Risk, Control, Execute Procedure/Walkthrough, Test Plan, or Testing) are cloned or imported. Any text linked to files that have been uploaded to other pages are displayed as highlights in Citation Mode.
NoteCitation Mode highlights and linked files do not display in framework narratives.
If you choose not to include project results, the above items are excluded from the cloning or import process.
Cleansing sensitive data
When you clone an objective from one project to another, and subsequently edit the objective in the target project, field-level changes containing source project data are reflected under History in the target project.
To avoid cloning confidential information from one project to another or from one Diligent One instance to another:
- Clone the objective to the same project.
- Cleanse any sensitive data.
- Import the objective into the appropriate project.
What happens when I clone or import objectives?
The inclusion or exclusion of project items is based on the method you use to clone or import objectives.
Cloning objectives (Workplan workflow)
Note
- Interface terms are customizable, and fields and tabs are configurable. In your instance of Diligent One, some terms, fields, and tabs may be different.
- If a required field is left blank, you will see a warning message: This field is required. Some custom fields may have default values.
Cloning from an active project to another active project
| Included items/fields | Excluded items/fields | Project results |
|---|---|---|
|
Same as importing from an active project to another active project
|
Cloning within the same Diligent One instance: Same as importing from an active project to another active project Cloning to a different Diligent One instance: Entities, Supporting Files, Custom Risk Scoring Factors, Custom Date fields, Custom Attributes, and Assessment Drivers and linked Metrics not included |
If Include project results is selected, the following items are included in the import:
If Include project results is deselected, the above items are excluded from the import. |
Cloning from a framework to an active project
| Included items/fields | Excluded items/fields | Project results |
|---|---|---|
|
Same as importing or cloning from an active project to a framework |
Cloning within the same Diligent One instance: Same as importing or cloning from an active project to a framework Cloning to a different Diligent One instance: Entities, Supporting Files, and framework synchronization not included |
Not applicable |
Importing objectives (Workplan workflow)
Note
- Interface terms are customizable, and fields and tabs are configurable. In your instance of Diligent One, some terms, fields, and tabs may be different.
- If a required field is left blank, you will see a warning message: This field is required. Some custom fields may have default values.
Importing from an active project to another active project
| Included items/fields | Excluded items/fields | Project results |
|---|---|---|
|
|
If Include project results is selected, the following items are included in the import:
If Include project results is deselected, the above items are excluded from the import. |
Importing from an archived project to an active project
| Included items/fields | Excluded items/fields | Project results |
|---|---|---|
| Same as importing from an active project to another active project | Same as importing from an active project to another active project | Same as importing from an active project to another active project |
Importing from an archived project to a framework
| Included items/fields | Excluded items/fields | Project results |
|---|---|---|
| Same as importing from an active project to another active project | Same as importing from an active project to another active project | Not applicable |
Importing from an active project to a framework
| Included items/fields | Excluded items/fields | Project results |
|---|---|---|
|
Same as importing from an active project to another active project |
|
Not applicable |
Importing from a framework to an active project
| Included items/fields | Excluded items/fields | Project results |
|---|---|---|
| Same as importing from an active project to another active project | Same as importing from an active project to a framework | Not applicable |
Importing from a framework to another framework
| Included items/fields | Excluded items/fields | Project results |
|---|---|---|
|
Same as importing from an active project to another active project |
Same as importing from an active project to a framework
|
Not applicable |
Importing from Content Library to an active project or framework
| Included items/fields | Excluded items/fields | Project results |
|---|---|---|
| Objectives, Risks, Procedures, and Execute Procedures, and their relationships to each other | Not applicable | Not applicable |
Cloning objectives (Internal Control workflow)
Note
- Interface terms are customizable, and fields and tabs are configurable. In your instance of Diligent One, some terms, fields, and tabs may be different.
- If a required field is left blank, you will see a warning message: This field is required. Some custom fields may have default values.
Cloning from an active project to another active project
| Included items/fields | Excluded items/fields | Project results |
|---|---|---|
|
Same as importing from an active project to another active project
|
Cloning within the same Diligent One instance: Same as importing from an active project to another active project Cloning to a different Diligent One instance: Entities, Supporting Files, Custom Risk Scoring Factors, Custom Date fields, Custom Attributes, and Assessment Drivers and linked Metrics not included |
If Include project results is selected, the following items are included in the import:
If Include project results is deselected, the above items are excluded from the import. |
Cloning from a framework to an active project
| Included items/fields | Excluded items/fields | Project results |
|---|---|---|
|
Same as importing or cloning from an active project to a framework |
Cloning within the same Diligent One instance: Same as importing or cloning from an active project to a framework Cloning to a different Diligent One instance: Entities, Supporting Files, and framework synchronization not included |
Not applicable |
Importing objectives (Internal Control workflow)
Note
- Interface terms are customizable, and fields and tabs are configurable. In your instance of Diligent One, some terms, fields, and tabs may be different.
- If a required field is left blank, you will see a warning message: This field is required. Some custom fields may have default values.
Importing from an active project to another active project
| Included items/fields | Excluded items/fields | Project results included |
|---|---|---|
|
|
If Include project results is selected, the following items are included in the import:
If Include project results is deselected, the above items are excluded from the import. |
Importing from an archived project to an active project
| Included items/fields | Excluded items/fields | Project results included |
|---|---|---|
| Same as importing from an active project to another active project | Same as importing from an active project to another active project | Same as importing from an active project to another active project |
Importing from an archived project to a framework
| Included items/fields | Excluded items/fields | Project results included |
|---|---|---|
| Same as importing from an active project to another active project | Same as importing from an active project to another active project | Not applicable |
Importing from an active project to a framework
| Included items/fields | Excluded items/fields | Project results included |
|---|---|---|
|
Same as importing from an active project to another active project |
|
Not applicable |
Importing from a framework to an active project
| Included items/fields | Excluded items/fields | Project results included |
|---|---|---|
| Same as importing from an active project to another active project | Same as importing from an active project to a framework | Not applicable |
Importing from a framework to another framework
| Included items/fields | Excluded items/fields | Project results included |
|---|---|---|
|
Same as importing from an active project to another active project |
Same as importing from an active project to a framework
|
Not applicable |
Importing from Content Library to an active project or framework
| Included items/fields | Excluded items/fields | Project results included |
|---|---|---|
| Objectives, Risks, Controls, Tests Plans, and their relationships to each other | Not applicable | Not applicable |
Permissions
Professional Managers and Professional Users can clone objectives.
Professional Managers, Professional Users, and users assigned the View Archived Projects privilege can import objectives.
Clone objectives from active projects
Note
- Interface terms are customizable, and fields and tabs are configurable. In your instance of Diligent One, some terms, fields, and tabs may be different.
- If a required field is left blank, you will see a warning message: This field is required. Some custom fields may have default values.
-
From the Launchpad home page (www.highbond.com), select the Projects app to open it.
If you are already in Diligent One, you can use the left-hand navigation menu to switch to the Projects app.
The Projects home page opens.
- Open a project you want to clone objectives from.
The project dashboard opens.
- Scroll to the bottom of the page and click Clone Objective.
The Clone Objective dialog box opens.
- Complete the following fields:
- Select an Organization Select the appropriate Diligent One instance to clone to the objective to.
To search for a Diligent One instance, enter a keyword in the search box. Results are automatically filtered as you type.
- Select a project Select the appropriate project to clone the objective to.
To search for a project, enter a keyword in the search box. Results are automatically filtered as you type.
- Select an Organization Select the appropriate Diligent One instance to clone to the objective to.
Clone objectives from frameworks
Note
- Interface terms are customizable, and fields and tabs are configurable. In your instance of Diligent One, some terms, fields, and tabs may be different.
- If a required field is left blank, you will see a warning message: This field is required. Some custom fields may have default values.
- Open Frameworks.
The Frameworks home page opens.
- Open a framework you want to clone objectives from.
The framework dashboard opens.
- Click the Sections tab.
- Click Go To beside the objective to clone and then select Overview.
The Clone Objective dialog box opens.
- Scroll to the bottom of the page and click Clone Objective.
- Specify the target of the cloned objective by selecting the appropriate Diligent One instance and project.
- Click Clone.
Result The objective is cloned.
Import objectives to active projects
Note
- Interface terms are customizable, and fields and tabs are configurable. In your instance of Diligent One, some terms, fields, and tabs may be different.
- If a required field is left blank, you will see a warning message: This field is required. Some custom fields may have default values.
-
From the Launchpad home page (www.highbond.com), select the Projects app to open it.
If you are already in Diligent One, you can use the left-hand navigation menu to switch to the Projects app.
The Projects home page opens.
- Open a project you want to import objectives to.
The project dashboard opens.
- Click the Fieldwork tab.
- Click Import Objective.
- Select the appropriate project under the Active or Archived list, or a framework from the Framework list, or a risk and control framework from Content Library, that you want to import objectives from.
- Select the objectives you want to import.
- Optional. Include project results If you are importing from an active or archived project, select this option to include Execute Procedures/Walkthroughs, Tests, Issues, Actions, and latest versions of attachments in the import.
- Click Import.
Result The objectives are imported.
Import objectives to frameworks
Note
- Interface terms are customizable, and fields and tabs are configurable. In your instance of Diligent One, some terms, fields, and tabs may be different.
- If a required field is left blank, you will see a warning message: This field is required. Some custom fields may have default values.
- Open Frameworks.
The Frameworks home page opens.
- Open a framework you want to import objectives to.
The framework dashboard opens.
- Click the Sections tab.
- Click Import Objective.
- Select the appropriate project under the Active or Archived list, or a framework from the Framework list, or a risk and control framework from Content Library, that you want to import objectives from.
- Select the objectives you want to import.
- Click Import.
Result The objectives are imported.
