Skip to main content
News

🚀 SENTIMENT ANALYSIS on AdaptiveWork is now Available to all Customers 🚀

  • February 19, 2025
  • 3 replies
  • 112 views
🚀 SENTIMENT ANALYSIS on AdaptiveWork is now Available to all Customers 🚀
Limori
Planview Falcons
Forum|alt.badge.img+4
  • Planview Falcons
  • 75 replies

What is it and how will it benefit customers?

Sentiment Analysis provides an early warning system within status and project views to address potential risks and issues inhibiting the successful completion of projects and programs.


Key features and benefits:

  • Transform unstructured text data into actionable insights by automatically analyzing and classifying sentiments (positive, negative, or neutral) to help you identify potential risks and opportunities for faster, smarter decision-making
  • Fully integrated within AdaptiveWork to provide real-time sentiment scoring powered by LLM technology (no third-party add-ons needed)
  • Easily configurable to your organizational workflows through custom actions and scheduled rules
     

To know more, hit the Customer Success Center links below -

3 replies

Forum|alt.badge.img
  • Bronze Active Participant
  • 3 replies
  • February 19, 2025

Hi, 

Thanks for this information, seems like an interesting feature. 

I have one question: when following your documentation and creating the custom action I had to specify the project id as the work item target. Is there a way to use the “CurrentObject()” function or do I have to hardcode the project ids for it to work?
 

Kind regards, Mathias


Limori
Planview Falcons
Forum|alt.badge.img+4
  • Author
  • Planview Falcons
  • 75 replies
  • February 19, 2025

Hi ​@Mathias - you should be using CurrentObject() and not the project ID. Please make sure to create the custom action on the project and/or program level, but not the work item level, as the ‘calculate sentiment’ is limited to projects and/or programs.

Limor


Forum|alt.badge.img
  • Bronze Active Participant
  • 3 replies
  • February 21, 2025

Thank you ​@Limori !

You were spot on, I had created the custom action on “Work Item” and not on “Project”. Changing it to “Project” solved it. 

Mathias