Udemy
    •  
    •  
    •  
    •  
    •  
    •  
    •  
    •  
Subscribe
Turn what you know into an opportunity and reach millions around the world.
Learn More
Your cart is empty.
Keep shopping
ALM Octane - The Basics of Business Rules Customization
Rating: 4.7 out of 5(17 ratings)
713 students

ALM Octane - The Basics of Business Rules Customization

This course provides an overview on how to use the business rules customization based on real project examples.
Created byAmir Khan
Last updated 1/2021
English

What you'll learn

  • Introduction to Workflow Customization

Course content

2 sections • 15 lectures • 1h 40m total length

  • Introduction to Workspace Customization18:50

    Space and workspace configuration This section provides instructions that admins can use to configure spaces and workspaces. In addition to the instructions below, space admins can also set configuration parameters for relevant spaces.


  • Create Custom Forms and Views4:49

    Create customized views and forms by cloning an edit view, grouping fields into a release info section, and removing unused fields to improve defect form usability.

  • Create a User defined Field and Add it to Form3:08

    Create a custom field named risk, add it to defect module form via workspace customization, configure its list values to match severity list, and drag it into the desired area.

  • Apply Set Field Value Business Rule5:44

    Apply set field value business rules to auto-calculate overall risk from severity and priority in the defect module, configuring timing, rules, and field updates across the customisation interface.

  • Use the Send Email Action on the Business Rule3:27

    Learn to create a business rule that sends an email when a defect's risk is marked as critical, configure subject and remarks, apply the rule, and verify email delivery.

  • Modify Lookup List Selection as Business Rule3:21

    Create a business rule to modify the localized severity lookup in a defect workspace, restricting options to low, high, and critical and applying the change across the workspace.

  • Make Fields required based on Condition3:21

    Learn to use business rules to make the owner field required when defect type equals escaped, by configuring workspace customization and adding a conditional rule.

  • Apply Alert User Business Rule6:42

    Learn to apply the alert user business rule in ALM Octane to prevent deleting or modifying entities with tasks or test cases, using backlog items and conditional logic.

  • Apply Set Field Value Business Rules when related Entities change6:50

    Use a set field value business rule to auto-update a user story based on related tasks and test cases, moving from in progress to in testing and done.

  • Apply Increment Value by Number as a Business Rule6:34

    Apply a number-based business rule to increment a field by one when the test's old value is ready and new value becomes design, enabling tracking of design rework.

  • Record Manual Test Execution Time6:14

    Record manual test execution time by automatically filling end dates when status changes. Use a business rule, duration calculations, and a dashboard widget to analyze results.

  • Data Access Control for Defects6:20

    Learn to implement data access control in ALM Octane by using roles and business rules to restrict defect visibility across internal and external users based on data categories.

  • Data Access Control for Tests18:44

    Define security classifications and assign data access in ALM Octane to control visibility for internal employees, customers, partners, and vendors; automate rules as defects move from opened to closed.

Requirements

  • You have to be an ALM Octane User and understand its Entity Model.

Description

OpenText™ ALM Octane is a web-based application lifecycle management platform that enables teams to collaborate easily, manage the product delivery pipeline, and visualize the impact of changes.

ALM Octane is flexible. You can perform some of the stages at any point. For example, you can define your backlog before you create requirements. On the other hand, some stages must precede other stages. For example, you must define manual tests or automated tests and execute them before you can track quality.


Depending on your development methodology, you can create high-level requirements, or build a detailed backlog tree with epics, features, and stories. For details, see Backlog.

Create tests to track release quality, including functional, sanity, acceptance, security, and performance tests. For details, see Manual testing flow.

You can also integrate with a CI server to get results of automated tests. As you implement user stories, you can report defects and monitor their progress. For details, see CI server integration flow and Automated testing flow.

When you run manual tests and CI server pipelines, results are automatically incorporated into the dashboard. You can then use the dashboard to analyze release quality. For details on the dashboard, see Dashboard.

For details on analyzing the release quality, see Analyze release quality.

You are an ALM Octane workspace Administrator and want to learn more about business rules and how to use it? Then this overview course provides a basic understanding on the business rules of ALM Octane.

Learn how to work with :

  • Set Field Value

  • Modify Lookup List

  • Alert User

  • Send Email

  • Make Field required

  • Increment Value by Number

  • New forms and fields

  • Email templates

  • Data access control

  • Module visibility

  • Add fields

  • Add lookup lists

Upon successful completion of this course, you will be eligible to:

  • be more productive

  • better collaborate

  • use agile methodologies in a smarter way

  • support the software delivery lifecycle

  • take on lead roles in your projects and advance in your career


Who this course is for:

  • Administrators
  • Testers
  • Test Managers
  • Quality Manager
  • Defect Manager

Report abuse