Plutora Feature Release Notes For Early July 2021

New Features

Unlimited Orchestration

Now, users can:

• Create custom Integration Hub scripts to trigger events in any application that supports APIs and configure the scripts to be manually triggered from Builds, TECRs, and Deployment Plan Activities by their delivery teams.
  • Use Integration Hub scripts to orchestrate events such as:
    • Builds.
    • Deployments.
    • Execution of test suites.
• Configure Integration Hub jobs as scheduled jobs or automated jobs:
  • Scheduled jobs will continue to run on a recurring schedule as per the existing functionality.
  • Automated jobs can be added to any System and can be manually triggered from Builds, TECRs, and Deployment Plan Activities.
    • Parameters can be defined with default values when creating the job in the Integration Hub and the values can be updated at run time for each Build, TECR, or Deployment Plan Activity.
    • Predefined field values will be available for the script to reference depending on where the job was triggered from:
      • The System’s automated job Name field will always be available.
      • The GUID, ID, or Name fields for the Build, System, Release, Change, and Environment entities will be available when triggering the job from a Build.
      • The GUID, ID, or Name fields for the TECR, Build, System, Release, and Environment entities will be available when triggering the job from a TECR.
      • The GUID, ID, or Name fields for the Deployment Plan Activity, Deployment Plan, Build, System, and Environment entities will be available when triggering the job from a Deployment Plan Activity.
    • Scheduled jobs can only have one In Progress job execution at a time but automated jobs can have multiple concurrent In Progress executions.
    • Scheduled job executions and automated job executions can be aborted from the Integration Hub grid or from the execution history pop up.

Global Parameters

Now:

• Administrators can add Global Parameters to the Integration Hub, which can be accessed from any Integration Hub script during execution.

Owner Field Enhancement

• Previously:
  • The Owner field in Enterprise, Project, and Independent Releases (and Enterprise, Project, and Independent Release Templates) was the first user or user group to be selected as a Stakeholder with an Accountable RACI role.
  • The Owner could only be selected from Stakeholders with an Accountable RACI role.
• Now:
  • The Owner can be selected from all the users and user groups.
  • The selected Owner will be automatically added as a Stakeholder with:
    • An Accountable RACI role.
    • No Stakeholder Role.
  • If a user selects a new Owner, the previous Owner will be kept as an Accountable Stakeholder.
  • This logic has been added to:
    • Adding Releases from Templates.
    • The following API endpoints:
      • POST /Releases
      • POST /Releases/bulk
      • GET /Releases/{id}
      • PUT /Releases/{id}
      • GET /ReleaseTemplates
      • GET /ReleaseTemplate/{id}
      • POST /ReleaseTemplates/CreateRelease
      • POST /Releases/{id}/Stakeholders
      • PUT /Releases/{id}/Stakeholders/{id}
      • DELETE /Releases/{id}/Stakeholders/{id}

Bug Fixes

• 20101: [Blockouts and Environment Schedule] Blockouts that have a Blockout Period Type with the Category Environment Booking now appear on Environment Schedule as expected and not just when a TEBR booked for that time period is present.
• 20740, 20708, 20815: [Release Activities] While saving an Activity or Criteria in a Phase or Gate, only the Activities or Criteria belonging to that Phase or Gate now show.
• 20760: [API] The fields targetRelease and actualDeliveryRelease have been added to calls to GET /Releases/{id}/Changes.

Version Number

2.19.0

Regional Release Schedule

*Subject to change.