Feb 22, 2024 / State types, resizable Timeline lanes

[antoniokov]

State Types

One of the most recurring confusions across Fibery have been why cards in some states are greyed out:

my tasks are dimming even when i have marked the state as “awaiting others.” (a GTD convention). what am i doing wrong?

and why some states have a checkmark while others don’t:

Hi, I’m having trouble making a workflow state be the final one. If i create a new state it juste adds it as another step in the process.

Previously, this depended on a well-hidden Final checkbox. From now on, the Workflow Field features state types instead.

Drag’n’drop a state to Finished to grey out the cards and get a checkmark:

Also, feel free to distinguish between Not started and Started states: this only adjusts the progress icon for now but later will be used in cycle time and flow efficiency calculations.

Check out more details in the Workflow Field guide.

Resizable Lanes on Timeline

Our Timeline View is full of papercuts, and we are fixing the first one today. If the lane section is too narrow and the names are cut, you are now able to resize it.

Minor Improvements

• There is a new easier-to-find > icon for hiding the right column on Entity View. We also remember the collapsed state per User per Database now.
• If you @mention yourself, you won’t get a notification (“improvement” reverted).
• Your preferred date and time format is applied in the Report filters and integration configuration.

There have been no improvements to expanded pinned Fields as we consider alternative approaches to the Entity View layout.

Fixed Bugs

• Weird navigation bug: wrong entity has unexpectedly loaded on the right panel
• New Table view (grid): if user scrolls down, opens entity and returns back to table, it scrolls up to the top
• “Could not load source info” message once account start being invalid
• Automatically watch entities I add into Favorites should also work for Documents
• Loader blinking when changing value for Reference Unit/Collection Unit
• Slack bot duplicates entries
• UI is broken when you press Cmd+K with opened comments
• There is no Open in a new tab option for Spaces
• Changing comments order does not work

[YvetteLans]

Love this release These kind of improvements give such joy on a daily basis. Thank you so much guys!

[YvetteLans]

@antoniokov

There have been no improvements to expanded pinned Fields as we consider alternative approaches to the Entity View layout.

Really curious I hope we can also edit pinned/left column fields in the future. That’s currently not possible (i.e. edit a state field, change the name of a field, delete a field etc.) and therefor we can’t work without the right column.

[ccollins]

@antoniokov

There is a new easier-to-find > icon for hiding the right column on Entity View. We also remember the collapsed state per User per Database now.

This is so much better!!! Great update

[interr0bangr]

@antoniokov

There is a new easier-to-find > icon for hiding the right column on Entity View. We also remember the collapsed state per User per Database now.

Don’t undersell this feature. It’s a huge quality of life improvement!

Also love the improved state type management stuff.

[interr0bangr]

What’s the right way to use state types in formulas?

It seems to accept string values without an error, but then when I try and filter an array on it, it doesn’t seem to work.

Related_Entity.Filter(State.Type = “Not Started”).Sort().First() isn’t working for me.

[Chr1sG]

“Not Started” “Not started”

[Lod]

Is there any change on Calendar View?
I am using Stylus to customize css tofill an entity with one color. The customization not work today.

What CSS do you use to adapt the Fibery interface?

Full background color coding (calendar cards) .c12jeug2 { width: 100%; opacity: 1; } .t8g2uh7.title-wrapper.card_container, .t1mu84wd { z-index: 1; } Before: [image] After: [image]

[njyo]

@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?

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.

[njyo]

@antoniokov

• If you @mention yourself, you won’t get a notification (“improvement” reverted).
• Your preferred date and time format is applied in the Report filters and integration configuration.

[antoniokov]

@Lod

Is there any change on Calendar View?

No, at least not intentionally — perhaps, this is a butterfly effect from updating a component somewhere else but hard to say…

Unfortunately, custom CSS is a fragile technique so we can offer no guarantees here.

[Chr1sG]

@njyo

However, I wish that things would have gone a bit further and also support an Archive state:

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.

There’s no reason why you can’t add a field (e.g. checkbox) to support an ‘Archive’ option for workflow states, which would allow you to do various useful things (e.g. filter out items based on State.Archive = true

Unfortunately, it wouldn’t have all the workspace implications that the workflow final state has (e.g. greying out in search)

[Yuri_BC]

State Types is a pretty amazing improvement. I used it in Clickup a lot. Thanks!

[njyo]

@Chr1sG

There’s no reason why you can’t add a field (e.g. checkbox) to support an ‘Archive’ option for workflow states, which would allow you to do various useful things (e.g. filter out items based on State.Archive = true

That is exactly what I have done in a good amount of entities. And I think 70% of my entities have a state field. So yeah, I love the solution given for the Finished state, I’d just want more.

Alternatively, if I can add two workflows, then that’s also solved. I can technically use the approach you have with the Users and have an Active? checkbox.
Sadly, all these approaches do not bring the benefits of greying out or automatic filtering/prioritising search results, etc.

As we see in my linked item, some others share my needs.
Anyway, thanks for the improvement already.

[SantiagoAGR]

@antoniokov

There is a new easier-to-find > icon for hiding the right column on Entity View. We also remember the collapsed state per User per Database now.

The collapsed state per user per database is huge! this is something I asked in this post. I wanted to hide, but collapsing is good enough!

Customizable Entity View. Shown Fields per User

1 sentence request: Show/hide fields state in an entity view (for a specific database) per user (I say specific database because I expect the hidden fields settings to apply to all entities in the same database just like it is now, no craziness about unique settings per unique entity) I created a draft of a solution for a company in my free plan. I have a Contracts database that links to Operations orders and Invoices (just an example, in the future could link to many other databases). The pr…

Love the release, I hope performance improvements are coming soon for the “new” table view