No. File have states, not transitions. Transitions move a file from one state to another state. A transition column would be meaningless.
Not so fast Jim...
Showing what Transition a file moved through to get to the current State would be useful if working with a simple WIP-Pending-Released workflow with multiple transistions between them.
However, there is not a method of showing that information directly. You can show it indirectly by setting a variable on the datacard in each Transition that gives any information required, including the name of the transition if wanted (have to enter it manually in each transition). That Variable can then be shown in a column.
How a file got to a particular state should not matter. If a process generates a constant need to know how a file ended up in a particular state, I would argue that the process has some serious flaws.
The only time I need to know where a file came from to get to its current state is when something has gone horribly wrong, in which case, I'll need the full history anyway.
I would balk at the effort required to maintain a workflow where every transition required a Set Variable action just to keep track of the transitions. Change a transition name without changing the Set Variable action and all sorts of confusion will occur.
I have a clarification question about the wording of your post. Based on your comment:
Currently I have to go to the history view to see the transition of a document.
Since the history does not show you the transition "name" but shows state to state movement (transition)
Are you wanting the "name" of the transition (and I'm reading between the lines here so help me out) OR are you wanting to see the transition "comment" the user entered during the last transition?
I have often needed to see the transition comment and have a variable to capture that on my data card and add that variable to my column set.
I am looking at the "name" of the transition. For example from Approved to Work in Progress state, the transistion name is "Request ECR".
As Jim said, you could manually add the "transition name" in a "set variable" action to record the transition name in a data card variable during a transition and create a column for that variable in your column set HOWEVER if that transition name ever ever ever changes and you don't update the "set variable" action that goes with it, you could create a real nightmare to troubleshoot. And if anyone relies on that transition name, it could cause problems in operations.
Change a transition name without changing the Set Variable action and all sorts of confusion will occur.
I see the value in accomplishing what you are after but I do not know of an easy way to get there without an API and I do not recommend doing the "set variable" approach.
My approach is to create a "roadmap" of the workflow for each user group to visually identify where the files are within the workflow:
- Take a screenshot of the workflow
- Highlight their "state"
- Add some text describing what actions are available to the users
- Print the image
- Laminate it & hand them out
- If the workflow changes, create new ones OR have the users justify why the workflow needs to change due to the added expense
Makes for a great way to support your users visually and gives them some skin in the game.
Hope this helps,