Modifying Target Configuration
Once a target has been created, they can be edited as configurations change over time. You edit project scoped data dictionary items on the project orchestration panel, and target scoped configuration on the targets panel.
Procedure for project scoped dictionary values
In order to edit a target follow the procedure below:
- Select 'Projects' and select a project.
- You will enter the project with the 'Orchestration' tab selected.
- Select the 'Data Dictionary' sub-tab.
- Edit the item(s) that require changing in the form or the data dictionary items list
- Select the 'Discover' button in the 'Data Dictionary' panel to find any data dictionary items that have been used in the project but which do not yet have a definition. These will be imported, but the value left blank. You may leave the value blank or enter one. Any Data Dictionary items with blank values at this project scope, will appear in each target scope as a red 'Empty' value. If left blank at both Project and Target scope, the user will be prompted to fill in a value (or leave blank) when a job for this target is being initiated. This is called 'Late Property Injection'.
- Save the configuration
Procedure for target scoped dictionary values
In order to edit a target follow the procedure below:
- Select 'Projects' and select a project.
- Select the 'Targets' tab.
- Each target is listed. Select the edit icon from the right hand side corresponding to the target you wish to edit
- Typically, for most requirements, you will only need to edit the dictionary items relating to this target, and MidVision encourages the use of dictionary parameters to store parameters likely to change for a target over time or between targets on a route to live.
- Save the configuration
Data Dictionary and templates
We recommend that you use data dictionary items wherever possible. This makes editing target definitions easier and also widens the audience of those able to make changes to targets from qualified domain administrators to less technical staff. If the target files are generated from a template, the data dictionary items will be populated automatically, and placeholders inserted into all the other target files.
Editing or Promoting Target Definitions Using Workflow
To request a project target configuration change a user must have the role "Environment Change Requester". To approve or reject a project target configuration change a user must have the role "Environment Editor" and must also be assigned to the work tray named "EnvironmentManagement". From version 3.3.23 users are automatically assigned to this worktray on user creation. A user will not be able to work on changes unless they are assigned the "Environment Editor" role and have access to the project the change is associated with.
When a requestor makes a change to a project target and saves the change a work item is generated for an editor to work on. The files are not saved to disk, the changes are saved into the database. The project target is then indicated as locked through the UI.
When there is a target change requested, a user with the role "Environment Editor" and is assigned to the project will see a new work item the "My Tasks" page. The user can then assign the work item to themselves and then view the request. They then have the option to approve or reject the change made. If they choose "Approve" then the changes are saved to disk. If they choose "Reject" the change is deleted. After the workflow decision the project target is then unlocked through the UI.