Custom prompt set up for Keyword filtering | Community
Skip to main content
T
TinoMe
Level 2
June 20, 2022
Question

Custom prompt set up for Keyword filtering

  • June 20, 2022
  • 1 reply
  • 1147 views

Hi WF community!

I am currently struggling a bit with two of my custom prompt setups where I am trying to filter for specific words people have entered into a custom field. (Not ideal, I know :-) )

In the beginning I had one of my prompts working but now they both don't seem to filter properly.

This is how I have set it up: DE:project:Keywords_Mod=in DE:project:Keywords=Manufacturing & Supply Chain

Could it be the space between the words? How do I need to set up the filter inside the Custom prompt to get a functioning prompt?

Thanks in advance

Tino

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

skyehansen
Community Advisor
skyehansenCommunity Advisor
June 21, 2022

hey Tino, I see a couple of things going on here.

1) You don't appear to have the correct syntax for your custom prompt (you can refer to this page to discover the right syntax: https://one.workfront.com/s/document-item?bundleId=the-new-workfront-experience&topicId=Content%2FReports_and_Dashboards%2FReports%2FCreating_and_Managing_Reports%2Fadd-prompt-report.html&_LANG=enus )

2) The keyword you're searching on is problematic. It contains a special character (the ampersand is already in use as part of the syntax). It would be better if you changed the keyword options so that special characters don't show up in items that you intend to do this kind of textmode reporting on.

K
kevinmathew2
Level 2
February 14, 2025

@skyehansen say we already have n number of objects with special characters in their names, do you know if it is absolutely impossible to create prompts on them? Or is it something that could come in the future. We could simply wrap the string in quotes.

skyehansen
Community Advisor
skyehansenCommunity Advisor
February 14, 2025

@kevinmathew2  -- not really in scope for the original post, but it's a question we are often asked so I will try and answer briefly:

 

1) I specifically called out the ampersand in this case, because the custom prompt operates by linking lines together with an ampersand. 

2) can you work around it in some way or is it "absolutely impossible"? Let me pose to you the opposite question: why do you think it's a good idea to introduce elements into your environment that less experienced users will need additional knowledge to implement? Additional to this, there are a lot of areas in the system where you will need to use this same type of text with different syntax rules. I called out a specific problem with custom prompting, but different issues might occur with Fusion, valueexpressions, calculated fields and group and filter text modes. This is even BEFORE you get asked to integrate between workfront and other systems like AEM and Jira.

 

TLDR: Because you cannot predict the use of your objects in the future, I strongly advocate that this is not the best use of any admin's time (trying to figure out workarounds that will work in all cases), because I can pretty much guarantee that there is no "one solution". You will simply create a strong dependency on a field over time, that will fail you in some way when you try to flex a little more on its use.

Terms & ConditionsAccessibility statement

Loading footer...