Better system for lean tags
We use lean tags a lot and some of the most frustrating things with this feature are we had to create work around because we didn't want the user experience to be polluted by potential improvement ideas found during the writing process. We hide our lean tags in 'hidden activities' but it doesn't hide it on the procedure view, only on the map view.
In addition, there is no way to track whether a lean tag has been actioned (implemented, reviewed, not accepted) in Promapp.
It would be great to see:
(1) an option for lean tags to have a status update
(2) when a lean tag is added anywhere (note, activity, task) it is automatically hidden from the user to view
(3) lean tag reporting picks up lean tags wherever they are located not just the activity or the task
Thank you for this Michelle. I’ll add to our request backlog for consideration. Much appreciate the use cases!
Matt Upton commented
To expand on Michelle's comment, we currently add our lean tags as a final Activity in the process, and assign the role of 'NON DISPLAY' to stop it displaying (atleast in map view) - this however means we need to structure any comments to include a reference to the actual Activity/Task it is referring to when we run an extract.
It would be great to see a system where it is included as another tab in edit view, similar to the way we have 'Summary' 'Triggers & Inputs' 'Procedure' etc at the moment
For us, a major challenge we face comes from the actual reporting side of things, as more and more processes are added into Promapp, the report is growing. It'd be fantastic to be able to pre filter further than the current system allows so we can choose to only include, for example, maps that have been edited or published in a certain time frame in the extract
Peter Lawrence commented
Michelle mentioned hiding lean tags in 'hidden activities'. How is this done? I can't see instructions for this in Promapp Help.
Jerome Deveix commented
I'd love to have the option to create a new lean tag group (similar to Document, General Tagging, Incident, etc which come out of the box). Result is we're using General Tagging to host a number of items that have little or nothing to do with each other.
Marcus Kueppers commented
We can also use a separate filed (dropdown) and the user can select one from the list. If the process need more than one you can select more. For me as a new employee it was it a little irritating how to use the tags.
I wanted to hide these too. or i would prefer them in the overview / keywords area. especially when I just wanted to use this function to create a register / list of processes which related to a certain market access requirement.
Rachel Lowe commented
I have requested very similar also. It is messy to see the #tag in the text of our processes. We do often want the want the tag itself visible, but the way to get it to present is very messy.