What’s new?

Documentation changes for version:

5.4 | 5.3 | 5.2 | 5.1 | 5.0 | 4.23 | 4.22 | 4.21 | 4.20

5.4

New

  • Reorder the Project Survey’s sections and subsections

    • Added details for reordering the project survey.

    • Please note that the Project Survey is undergoing enhancements and may not be accurately reflected in existing user guide screenshots. These screenshots will be updated once the Project Survey redesign has been completed.

Updated

  • Automations

    • Updated Automations with changes to permissions and location in UI.

    • Added new dropdown lists for Business Unit, Application, Task ID, and Task Status fields.

  • Pivotal Tracker

  • Azure DevOps

    • Updated these integration tools with custom status mapping.

5.3

New

Updated

  • Profiles

    • Updated Profiles to reflect the new changes from the Content Pack Selector.

  • Remote Integration Agent

    • Updated details for installing the Remote Integration Agent on Linux.

5.2

New

Updated

5.1

Updated

  • Process Task Automation has been renamed to Automations.

  • Microsoft Team Foundation Server / Visual Studio Team Services has been updated to Microsoft Azure DevOps.

  • CA Agile Central (formerly Rally) has been updated to Rally (formerly CA Agile Central).

5.0

New

  • Project Classification

    • Added guidance for using Project Classification to assign levels of risk to your projects.

  • Process Task Automation (PTA) - Beta

    • Added information about what you can expect from the introduction of Process Task Automation in SD Elements.

    • Note: Process Task Automation has been renamed to 'Automations' and is reflected as such in all existing documentation.

  • Phases

    • Added a new section for Activities tasks.

  • Verification Supported Tools

    • Added OWASP Dependency Check, Sonarqube, and Tenable Nessus.

Updated

  • LDAP Synchronization

    • Fixed an error in the documentation.

  • Veracode

    • Updated authentication details for Veracode based on its new authentication requirements.

    • Veracode has shifted their authentication for XML from basic authentication (username, password) to HMAC authentication, which requires an API ID and Key.

4.23

New

Updated

4.22

New

4.21

New

  • Hidden phases

    • Added explanation for how phases are made hidden or visible after completing the project survey.

Updated

4.20

New

results matching ""

    No results matching ""