Environment names - ask the customer what names they want to use
181
Views
3
Comments
New
Install Processes

Our customer subscribes to OutSystems hosted infrastructure. The environment names were really strange, "non-production environment #3" etc.

Please ask your customer what names they prefer and install those. This way admin (me in this case) doesn't have to create tickets to change the names.

Hi,

Just create a support case to OutSystems, and they will rename them for you, with a bit of luck the same day.

If you share the preferred names before the infrastructure is provisioned to OutSystems, they will also use the names that you suggest.

Regards,

Daniel

Perhaps you didn't read my comment? I want to avoid creating tickets, I've got better things to do. The way this works now is totally stupid.

It should be part of you installation procedure to ask for the names. It should not be the customer's responsibility to know that you will assign useless names to environments unless told otherwise.

And where do these names come from anyway? Why not use as defaults something common, such as Development, Test, and Production?

Is there a reason for changing environment names not being possible in Lifetime or License Portal? Would be simplest if an admin could do it.

I did read your idea, it is not totally stupid, it is just not efficient. I t takes you an extra step of a few minutes.

I just commented to give context to  the idea and how the current process works, for others that are interested in this discussion.

But you are right with your idea, that it should be 100% self-service.