Absent Member.. Tim_Brandish Absent Member..
Absent Member..
208 views

Workflow Transition Validation with SQL and Tokens - Not Working

Jump to solution

I'm trying to populate workflow step transition buttons based on demand request token values. Instead of displaying the token value, I get the token name. Simple example:

Validation SQL

select '[REQ.REQUEST_ID]', '[REQ.REQUEST_ID]' from dual

Workflow button visible:

[REQ.REQUEST_ID]

The only exception I have found is that the [SYS.USER_ID] token works.

Does anyone know if this is supposed to work with other tokens or not?

0 Likes
1 Solution

Accepted Solutions
Natalia_R_PPM Absent Member.
Absent Member.

Re: Workflow Transition Validation with SQL and Tokens - Not Working

Jump to solution

Hello Tim 

PPM can only resolve the token in request fields, if the token is in the workflow step transition, we only support the SYS token, but you're using a REQ token which means a request token, and the REQ token need a request context so it can be resolve only in request field sections. Is by design

Regards, 

Natalia R

HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
2 Replies
Natalia_R_PPM Absent Member.
Absent Member.

Re: Workflow Transition Validation with SQL and Tokens - Not Working

Jump to solution

Hello Tim 

PPM can only resolve the token in request fields, if the token is in the workflow step transition, we only support the SYS token, but you're using a REQ token which means a request token, and the REQ token need a request context so it can be resolve only in request field sections. Is by design

Regards, 

Natalia R

HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
Absent Member.. Tim_Brandish Absent Member..
Absent Member..

Re: Workflow Transition Validation with SQL and Tokens - Not Working

Jump to solution

Thank you for confirming my findings.  This would be a good enhancement.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.