The project folders in Newforma Items to File in Outlook are named with the Project name and the project code.

Is it really necessary for the project code to be visible to users in this location?

My suggestion is hide the project code.

This is something other customer have expressed also. This is a limitation of working with folders in Outlook. The characters following the Job Name is actually the code Newforma uses to know the project to which the folder belongs.

Dan,
Thx for the reply, but I have to say the substance of it is a bit ambiguous.

I knew when I posted why the codes are there and I assumed others had made the same suggestion as me.

Are you saying, “Yes, we know the users want to see it changed, but there’s nothing we can do about it because there is a limitation working with Outlook”?

Are you declaring that Newforma’s programmers have thrown up their hands in defeat?

Is there really no solution whatsoever? Is there absolutely nothing that can be done?

We’re only talking about the visible properties of an email folder. If I am seeing alphanumeric characters on my monitor, isn’t it a product of hex or binary code?

Do you mean to say there are no other means for Outlook and Newforma to understand which project they are synchronizing? Or is it the case that as currently programmed there is a limitation?

Thx -Sam

Hi Sam,

It is something we could look at doing and use an invisible Outlook property to store the code.  The one advantage is that a user with a tagged email can look at the tag and see what folder it is associated with (tag uses the same code as the folder).  Do you think advanced users would use/miss this funcitonality?

Marge

I don’t think anyone at my company would use tags in the manner you describe. So, no, I don’t think it would be missed.

Thx -Sam

It’s been my experience that the project tag codes only add confusion when used in the Outlook folder naming and on the email subject lines.  We would prefer the hidden property option for the Outlook folders and some kind of embedded, non-visible email header instead of the code showing on the email subject line.

There is no other place that I’m aware of in the NPC client where these tag codes are visible to a typical end user, and this is what ends up causing the confusion.  If there are going to be visible cues in folder names and email subject lines, make them match something else that the users can already see and associate with a project (such as the project number).

I understand the need for the codes (an immutable project identifier that makes it possible to rename other things like project name and project number if necessary) but they should be kept in the back-of-house and out of the interface view.

Matt

I agree.  And I also pose that rather than the random string of charaters you include the project number.  I’ve been recently hit by the CA dept (as they just started using Newforma) are having a hard time using the Items to file because the project # is not included.  We’ve already populated 1200-1300 projects and I don’t feel like going back through and renaming the project name to include the # just so it is listed in the Items to file.  So now they are having to cross reference with a spread sheet until they get all the names memorized (that will never happen).

Any ideas on that or if its viable or on the plate for a future release?

Hi Creighton,

I have added you to the +Features related to your posting.  What we really need is a preference setting to allow someone to choose if they want to view Project name or Project number as I have heard of folks working both ways.  Both the suggestion to hide the field and allow for a setting are viable options and will be looked at for a future release.

Thank you for your input!

Marge