Global HTML fields UNDER REVIEW

4

It certainly makes sense to have an HTML field available as a global field. We'll evaluate it against other requests and priorities.

Hi Daniel, could you please outline use case/use cases for the global HTML field? It would help us evaluating it internally.

Hi Michal,

let's assume you are using HTML fields to introduce some functionality like a bread crumb. Then you will want to have this in all workflows. If there's a change to it, let's assume somehow the DOM changed with a new release, you will need to touch each field in all processes.

But maybe these kind of options the HTML fields offer is used by a small group.
Perhaps someone else can add the results of the following script:
/****** Script for SelectTopNRows command from SSMS ******/
SELECT WFCON_Prompt, Count(*) as [Count]
FROM [dbo].[WFConfigurations] join DicWFFieldTypes on WFCON_FieldTypeID = TypeID and ObjectName = 'HTML'
group by WFCON_Prompt
order by [Count] desc

This will group the html fields by name and count them. If a field is created again and again with the same name, it should come up at the top.

Best regards,
Daniel