getSolutionTitle ?

Is there this function? I can’t find it! I find only “application.getSolutionName” but it isn’t what I want.

Under
File → Solution settings
there’s the “Title” field but I can’t retrieve this value for assign it to a label for example (there isn’t in the “Standard tags” list too).

Why would you want that?
You set the title yourself so you already know it :?

The easiest thing could be to create a i18n key and use that. You can always ask for its current value then. We use that in our solution because that has a different name for different customers.

Simply for show it as a label on the header.
So when I clone the solution that I use like a template I have only to change the solution.title and not also the label…

maybe I’m too lazy :)

IT2Be:
Why would you want that?
You set the title yourself so you already know it :?

Might it be useful for a module to know what solution it is being used within?

I like the i18n tip…

kazar

Might it be useful for a module to know what solution it is being used within?

Could be.

The reason I asked is because often people don’t write why they have a question.

When you know why something is asked it is easier to interpret the question and give a pointer into the most appropriate direction…

IT2Be:
The reason I asked is because often people don’t write why they have a question.

When you know why something is asked it is easier to interpret the question and give a pointer into the most appropriate direction…

I agree completely, Marcel, that it’s easiest to get an effective answer in a forum (and easier for others to provide one) if one states one’s goal!!

I did not misunderstand why you asked, “Why would you want that?”. But your question did spark a train of creative thinking (as did Patrick’s i18n tip).

I would think for “axterics” goal of simply showing a label in a header with a specific customer name, that customer’s header label (and many similar customer-specific values as may be needed, such as invoice_address in a billing solution and so on) could (and perhaps “should”) simply be stored in a preferences table as data (or do the i18n key thing).

But if a module does not know in advance what solutions it will eventually become part of, it might help to have a Servoy function that gets the solution name, so that appearance and branching can be fine-tuned according to “what solution I belong to at the moment”.

kazar