Add Or Edit Systems

Contents

DUE EARLY NOVEMBER 2020: Now, users clicking the Contact Stakeholders button can select from a list of Stakeholders to email.

Add or edit Systems from the Systems Manager page. Users can also duplicate a system.

Now, you can click the Systems back button and easily navigate back to the Systems grid or the previous page.

Add or Edit a System

To add or edit a System:

Add or edit:
1. Add:
  1. By + New:
    1. Go to + New > Other > System.
  2. By System Manager:
    1. Go to Environment > Systems.
    2. Click + New System.
  3. Under the Information panel:
    1. Type the Name. (Mandatory field.)
2. Edit: Click a blue-linked System Name to edit a System.
  1. To edit the Name:
    1. Hover your mouse cursor over the Name until the pen appears.
    2. Click the Name and starting typing to edit.
Under the Information panel:
1. Click to edit the Description.
  
  Description field now has a WYSIWYG editor and expands to fit the content.
Under the Additional Information panel:
- Additional Information is now a panel instead of a tab:
- Field controls now only appear when the mouse cursor hovers over them.
- Empty fields only show the field name, which saves space.
- The Additional Information panel contains custom fields, which administrators have added using System Custom Fields Customization.
- These fields will vary between each Plutora installation.
- Please consult your administrator for the procedure for filling in these fields.
- If a user lacks permission to see a custom field tab’s fields, that tab will now be hidden for that user. (The permission is set in System Custom Fields Customization.)
Under the Recent Builds panel:
1. View a list of the most recent Jenkins builds for all the Jenkins jobs associated with the System. Jobs run by associated TECRs and Environments will appear here.
2. Jobs run from the top of the list to the bottom.
  1. Reorder jobs by dragging and dropping.
  2. The version number produced by the top job is used as the version number in the Environment, but only if all jobs run successfully.
3. Click + New Build to add a new build:
  1. System contains the current System and is not editable.
  2. Select a Linked Release.
  3. Select one or more Linked Change.
  4. Select an Environment.
  5. Click to select the Automated button.
  6. Click Set Parameters to select or change the Parameters added in Jenkins.
  7. Click to select one or more Jenkins jobs.
  8. Click Create New Build.
4. Add more Jenkins jobs to the System:
  
  The full list of Jenkins jobs is found in the Jenkins Customization.
  1. Click + New Job.
  2. Jenkins is currently the only Application that can be selected.
  3. Select a Jenkins Instance.
  4. Select a Job created in Jenkins Customization.
  5. Select Approved Users. If selected, only these users or User Groups can run the job. Otherwise, anyone with permission to edit the System can run the job.
  6. Select the Job Type.
  7. Click Save & Close.
5. Edit selected Jenkins jobs:
  1. Hover your mouse cursor of the job to be edited and click the pen icon.
  2. Jenkins is currently the only Application that can be selected.
  3. Select a Jenkins Instance.
  4. Select a Job created in Jenkins Customization.
  5. Select Approved Users. If selected, only these users or User Groups can run the job. Otherwise, anyone with permission to edit the System can run the job.
  6. Select the Job Type.
  7. Click Save & Close.
Under the Details panel:
1. Click the Status toggle switch to label the System as active or inactive. (Mandatory field.)
2. Type a Vendor. (Mandatory field.)
  
  Vendors now appear as a column on the Systems page and the Systems XLS export file.
3. Click Portfolio Association and select from the tree menu. (Mandatory field.)
4. Manage Aliases:
  
  Aliases are alternative names for the System. They must be unique and cannot be the same as the System’s Name.
  1. Add an Alias:
    
    System Aliases can now be managed through Plutora’s API.
    1. Type an Alias in the Alias field.
    2. Press the Enter key on your keyboard.
  2. Delete an Alias:
    1. Click the X.
Under the People panel:
1. Manage Stakeholders:
  1. Manage Stakeholders:
    1. Add a Stakeholder:
      1. Click the circle with a plus sign.
        
        When users are added as stakeholders more than once, they will appear as a stakeholder only once with all their Roles and Stakeholder RACI Roles merged.
        
        For example, if a stakeholder with Role A and all the RACI Roles was added again with Role B and no RACI Roles, the stakeholder would appear only once with Roles A and B and all the RACI Roles.
      2. Select a User Name or a User Group from the Name or User Group drop-down menu.
      3. Select a role from the Role(s) drop-down menu.
        
        Administrators can add roles using the Stakeholder Role Customization.
      4. The Email field is not editable.
      5. Click to select a Stakeholders RACI checkbox.
      6. To save the Stakeholder and add another Stakeholder: Click Save & Add New.
      7. To save the Stakeholder and close: Click Save & Close.
      8. The Stakeholder will have a red exclamation mark until the System has been saved.
    2. Delete a Stakeholder:
      1. Hover your mouse cursor over the Stakeholder.
      2. Click the delete icon.
        
        DUE EARLY NOVEMBER 2020: Now, users clicking the Contact Stakeholders button can select from a list of Stakeholders to email.
2. Once there are Stakeholders saved, click the contact Stakeholders button:
  1. Choose one of the following:
    1. To send the email to all the Stakeholders click to select the Send to all Stakeholders radio button.
    2. To select from a list of Stakeholders who will receive the email, click to select the Send to selected Stakeholders radio button:
      1. Click the combo box and click to select the checkboxes of the Stakeholders you would like to email.
        
        Stakeholders are listed from the selected System, all related Environments, and all related Environment Groups.
  2. Type a single email address into the From field. (Mandatory field.)
  3. Type an email Subject. (Mandatory field.)
  4. Type an email Body. (Mandatory field.)
  5. Click Send.
3. Click Environment Booking Approvers and select users or User Groups who will be capable of approving bookings for Environments linked to this System:
  - Any user in the group can approve or reject bookings.
  - Only one user in the group needs to approve or reject bookings.
Under the System Dependencies panel:
1. Click the pen icon to open the System Dependencies pop up.
  
  Click Save & Create New first if adding a new System.
2. Drag and drop Systems into Upstream System Dependencies or Downstream System Dependencies:
  
  Now, drag and drop UI styling is consistent throughout Plutora. Where an item can be dragged and dropped, the mouse cursor turns into a four-headed arrow. Areas where the item can be dropped will be marked Drop Here and will be highlighted in blue, with a darker blue dotted border.
  - Upstream and Downstream Dependencies are consistent across all Systems.
  - If System A is added as an Upstream Dependency in System B, if you open System A, System B will be marked as a Downstream Dependency.
  - Circular references are no longer possible. Selected Systems will not appear for selection in the left-hand panel.
Click:
1. New System: Save & Create New. (If you haven’t clicked it already. Otherwise, click Save.)
2. Edited System: Save.