# Feb 22, 2024 / State types, resizable Timeline lanes **URL:** \ **Category:** Changelog\ **Created:** [February 22, 2024, 2:48pm UTC](https://community.fibery.io/t/feb-22-2024-state-types-resizable-timeline-lanes/5890 "2024-02-22T14:48:43Z")\ **Posts on this page:** 1\ **Showing post:** 10
**Author:** ![njyo](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/njyo/32/923_2.png) [@njyo](https://community.fibery.io/u/njyo)\ **Post date:** [February 23, 2024, 8:37am UTC](https://community.fibery.io/t/feb-22-2024-state-types-resizable-timeline-lanes/5890/10 "2024-02-23T08:37:30Z")
> [@antoniokov](#): > > Previously, this depended on a well-hidden `Final` checkbox. From now on, the Workflow Field features state types. > > Drag’n’drop a state to `Finished` to grey out the cards and get a checkmark: Love that y’all are trying to improve the workflows, and I think this is a step into the right direction. However, I wish that things would have gone a bit further and also support an Archive state: > [@An archive or failure Workflow state?](https://community.fibery.io/t/an-archive-or-failure-workflow-state/1650/14): > > Just to update this thread, I ended up just creating a separate DB for archived entities. This is a clunky solution because you need to manually convert entities to the archived DB and then delete the original entity. This also might possibly breaks some long-term report types, although you might be able to join the entities from the two DBs. But it does have the added benefit that the archived entities are completely separate in search and selection fields. Also has the benefit that you can h… With many entities (e.g. offices, vendors, employees, customers, systems, environments, features etc.) there is a need to sunset/archive them in a way that the information is still in Fibery, but clearly not active anymore. Ideally, that should be a perpendicular dimension so that I can archive something that’s `Released` or something that’s `In Progress` to go with your example. Also, based on workflow, sometimes I may want to grey out (and give less priority when searching) all items that are `finished` while sometimes I may wanna grey out only what’s `archived`. For example, tasks would be greyed out once finished, while for my features we probably want a state like `Released` to mean `finished` but a state like `Deprecated` to be `archived` and greyed out. Thanks! PS: I noticed that the status now has a `Type` text field taht behaves like a formula? Interesting approach. Hope that allows for more flexibility. 🤓 --- _[View the full topic](https://community.fibery.io/t/feb-22-2024-state-types-resizable-timeline-lanes/5890)._