Add Or Edit Environments

Over the next few weeks, we will be updating our user interface to make it more consistent. The icons, buttons, fonts, formatting, and colors that appear in the screenshots below will be temporarily out of date.

Users can add and edit Environments on the Environment Manager page. Users can also duplicate environments.

Now, administrators can use Title Names Customization to customize the name of the Environment module where it appears throughout Plutora.

To add or edit an Environment:

Copy an Environment URL to the clipboard:

  1. Click to open an Environment.
  2. Click the Copy URL to Clipboard  button.
  3. Paste the copied URL into another application or document.
  4. Users who are logged into Plutora when they click the URL will be taken directly to the record. Users who are not logged in will be prompted to do so.

To add or edit an Environment:

Users must have the Update Environment user permission.  

  1. Go to Environments > Environments:
    Add: Click Add New Environment.
    Edit: Click a blue linked Environment Name.
    Click the Contact stakeholders  button to send an email to every stakeholder in the Environment.
    Type a single email in the From field, type a Subject, and an email Body, and click Send.
  2. Fill in the Environment Definition form:
    1. Type an Environment Name.
    2. Add or edit Description.
    3. Select a System from the System drop down menu:
      • The System’s My Environment Booking approvers are listed under the System drop down menu so users know which person to ask for permission to use the System.
      • Administrators can prevent users from selecting Systems outside their Portfolio Association by selecting the My Portfolio Association checkbox for the Restrict Site-Wide View of Environments user permission.
    4. Select an Integrated Environment Group from Integrated with or:
      1. Create a new Environment Group for the Environment:
        1. Click the and see Manage Environment Groups for the procedure.

          Administrators can prevent users from selecting Environment Groups outside their Portfolio Association by selecting the My Portfolio Association checkbox for the Restrict Site-Wide View of Environments user permission
    5.  Type the URL.
    6. Select Used for Phase.
    7. Select a Scheduler Display color or type a Hex color.
    8. Type a Vendor.
    9. Manage Linked Environments:
      To enable Linked Environments, go to Environment Setup Customization. Environments already selected but outside the user’s Portfolio Association will be hidden if administrators select the My Portfolio Association checkbox for the Restrict Site-Wide View of Environments user permission. Environments outside the user’s Portfolio Association will also not be available for selection.

      Linking Environments enables users to select a parent Environment in a TEBR (with or without a Release) or an Enterprise, Project, or Independent Release and drag and drop the Environment, its Child, and Grandchild Environments all at once.

      1. Add a Linked Environment:
        Parent to child of

        1. Click a green cross.
          Green cross TEBR form questions
        2. Click the combo menu and click to select one or more of the Environment checkboxes.
          Add linked environment
        3. Click Save & Close.
      2. Apply Parent Environment Status to Child Environments:
        1. Click Apply Status to all Children.
          Edit Environment May 2017 Apply status to all children
          The Apply Status to all Children button provides a one-off Environment Status push. If you change the Parent Environment status again, the Child Environments will not automatically update and you will need to click Apply Status to all Children again.

      3. Remove an Environment link:
        1. Hover your mouse cursor over the blue Environment link until the delete button appears.
        2. Click the red delete button.
          Red delete button linked changes
    10. Click to select an Environment Status.
    11. Click to select an Icon.
      Icons are displayed in the Environment Map and provide an extra layer of information about the Environment.
    12. Click to select the This is a Shared Environment checkbox if the Environment can be booked multiple times simultaneously.
    13. Click to select the Any booking will be automatically approved to:
      1. Make new TEBRs (with or without a Release) be automatically be approved and,
      2. When users change the date and time of the Release Phases of Enterprise, Project, and Independent Releases, if they choose to also update booked Environments, these changed bookings will not need to be approved.
    14. Manage booking alerts:

      Booking alerts pop up to provide a user with extra information when they try to book the Environment.

      1. Click to select the Display booking alert checkbox to make the alert pop up appear.
        If you cannot see this checkbox, use the scrollbar to scroll down.
      2. Type the Message that will appear in the pop up.
  3. Fill in the Technical Specs and Configuration form:
    Click the copy button Copy buttonto copy all configurations to your clipboard, or click Version to copy the version number only. The user permission Update Environments is not required to copy configurations. 

    1. Click Add Host to add a new Host.
    2. Click to select a host and click Add Layer.
    3. Select a Component Name from the drop down menu.
      • See Jenkins Integration for how to use Update on Build.
      • If no Stack Layers have been added, the Component Name drop down menu contains the default stack layers: Application, Middleware or System.
      • View Stack opens the Environment Map.
  4. Import Technical Specs and Configurations from another Environment:
    Save time by importing configurations rather than creating them from scratch.

    Import Technical Specs and Configurations pop up

    1. Click to select an Environment from the Select Environment to Import Tech Specs & Config from.
    2. Click to select a radio button to choose an Import Behaviour:
      1. Import and replace all existing Tech Specs & Config: Choosing this radio button will delete and replace all existing tech specs and config. This cannot be undone.
      2. Import and append to existing Tech Specs & Config: Choosing this radio button will add the tech specs and config from the selected Environment to the bottom of the existing ones.
    3. Click Import.
  5. Click Click here to hide allocations to toggle the Environment Allocation Schedule panel.
  6. Check the Environment Allocation Schedule (if editing the Environment):
    • Only bookings for Releases and TEBRs with a Release are shown.
    • TECRs, and TEBRs without a Release are not shown.
    • Hover your mouse cursor over TEBR bars to open the tooltip, which now contains the TEBR Requester and TEBR Type.
  7. Click Save.

 

The Additional Information tab contains custom fields, which administrators have added using Environment 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 Release Custom Fields Customization.)

  1. Click Additional Information tab.
  2. Fill in the fields.
  3. Click Save when you have finished.
  4. Click Stakeholders tab.

To manage the stakeholders associated with your Environment:

  1. Add a Stakeholder:
    1. Click Add Stakeholders.

      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.


      Add New Stakeholder to Environment
    2. Select a User Name or a User Group from the Name or User Group drop down menu.
    3. Select a role from the Environment Role 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. Click Add & Close.
    7. Click Save.
  2. Delete a Stakeholder from an Environment:
    1. Click to select a Stakeholder.
      The Stakeholder will highlight in yellow.
    2. Click Remove.

  1. Filter your linked items by clicking the View by radio buttons.
  2. Click Save & Close.

Click the clock-shaped button  to view the Audit History of the record. To see more information about Audit History, click here.

Users can copy an Environment’s URL to the clipboard by clicking the Copy to Clipboard  button on the top right of the pop up.

Back to the top arrow

Was this article helpful?

0 found this helpful.