Verified Answers


If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Not Answered
  • Replies replies
    0
  • Subscribers subscribers
    8
  • Views views
    64
  • Users 0 members are here
Related
Options

Template_GetDetailsPageName not triggered after the first requirement

Jordan Gottlieb

ALM 24.1p1  I have 2 Requirement Types that have different fieldsets. I have workflow to set up the fields. Each requirement type has a second tab configured with fields on it. I assign the tab name in Template_GetDetailsPageName (select case on req type).  When I log in and select one requirement Template_GetDetailsPageName is triggered and the tab is named correctly. However, when I move to the second requirement (of the other type), Template_GetDetailsPageName is not called at all.  It doesn't matter which one I select first after login, it works like this.

Tags:

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.