My workflow adds fields depending on the process. The issue is that i want the fields to be in a specific order i need, not in alphabetical order.
My workflow adds fields depending on the process. The issue is that i want the fields to be in a specific order i need, not in alphabetical order.
Hi Alvaro,
Is this ultimately about a user reviewing the document and the independent fields in an application like the desktop Client? The Client currently will display the independent fields in alphabetical order regardless of the actual order the fields were added in, but we can look into adding flexibility for modifying the display order in a future release.
Regards
Just curious - is there a particular reason you can't use a template for this? Organizing fields into a specific order is basiclaly what it does.
These fields are specifically for process usage. Depending on the stage of this process, some fields are needed, other aren't. So the user, besides the template fields, only sees the "process" fields he/she needs, not more than that. Because the process is long and there are many stages and participants i cant show them all the fields, as a template, because they dont need all the "process" fields at a particular stage. I add and remove "process" fields regarding the stage we are. It works fine for me, the only issue is the order in which the fields appear, i really would like to have the choice at workflow designer to order this "process" fields in the order i want them to be.
Could you have the WF hide the fields that aren't relevant for that step of the process? You could use field security and have the different steps show different fields. Then the users won't see the one's that aren't relevant to them.
Yes, i found that when you assign "" (null) value to an independent field, it disapears.
I dont use security configurations at this point because as i said these fields are only used at specific stages of my process, so once they are used i dont need them anymore, not even as index information.
Hi Alexander, yes it is. It would be very useful to add this flexibility.
Any other ideas on how to deal with this need?
If there will not be too many different combinations of independent fields, then perhaps they can just use different templates for the different scenarios for now. This may make searching a little more complex as users would probably then need to search the independent fields instead of having to remember what template might be assigned to a document. If the order/position of the fields is of utmost importance, then that may be the way to go.