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
    2
  • Subscribers subscribers
    12
  • Views views
    71
  • Users 0 members are here
Related
Options

Using the Workflow Step Name in a Request Command with tokens

puthar

Hi,

I have the following Workflow Step token in a workflow exection step: [WF.WFS.STEP_NAME]

I am trying to derive the same from the Request Command event Apply after save.

If I use [WF="[REQ.WORKFLOW_NAME]".WFS.STEP_NAME] then I get a failure in the request command.

If I used the following in the command: [WF="[REQ.WORKFLOW_NAME]".WFS.STEP_ID] with the following result [WF="MTN Boost Project Workflow V1".WFS.STEP_ID]

I have also tried to use a couple of other variations of the token but I don't get the Stape Name.

What am I missing with the token builder?

Regards,

Alfred Puth

iOCO: Senior PPM Consultant

Tags:

  • 0  

    Hi Alfred,

    I see the PPM notifications are using:

    [WFS.STEP_NO].[WFS.STEP_NAME]

    I have not tested it but if it still does not help - maybe you can open a support case about this to be checked.

    Best Regards,

    Iliya

    Iliya Iliev
    PPM NSE
    Although I am an OpenText employee, I am speaking for myself and not for OpenText.
    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

  • 0 in reply to   

    Hi Iliya,

    I tried but it does not work in the Request Command.

    I think I need to get the request Workflow ID and the workflow step ID but I struggle to get the tokens to work.

    I will log a support case, thanks

    Regards,

    Alfred Puth

    iOCO: Senior PPM Consultant

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.