Hi,

It is not possible to grey out certain statuses or let them disappear as domain elements are not subjected to the layout procedure for example to be hidden. You could throw a message in the default if the user selects a status that is not allowed and empty the status accordingly.

Best alternative is by having the statuses as part of you application. Create a status table for this list in your application and make a reference to the Task. That way you have more control over what the user can see or select. This comes with the downside that translations for these statuses then also have to be present in your application. Luckily we do now provide a session variable to obtain the user's language so you can show the correct translation for the user (assuming you have multiple languages. If only English is present in your application, this is not needed)

We are planning on introducing Domain variants. Also another user has created an idea to be able to change the visibility of domain elements based on logic: Ability to hide Domain element based on logic | Thinkwise Community (thinkwisesoftware.com)

Does this help?

@Blommetje, does my previous reply help you out?

Hi,

Yes, making the list part of the app is sometimes a good solution. But for short lists with like this example, statuses, I still think a layout proc to disable certain options would be very handy. 

I think it’s nicer to grey out an option than to show a message after selecting it that its not allowed.

And sometimes that scenario happens. 

But for now i’m good. thnx! 

I'm sure you'll like these ideas :

• Ability to hide Domain element based on logic | Thinkwise Community (thinkwisesoftware.com)
• Domain (elements) Variant | Thinkwise Community (thinkwisesoftware.com)

We currently also support making domain elements unavailable in case elements should be present but not selectable anymore

I assume is only relevant to phase out certain values, correct? 

Correct