Intelligent Check-Out

[LANSAfolks]

Working in a Shared Visual LANSA development environment

Say you attempt to Check-Out an object in error, forgetting that you had made changes to it previously that were not yet checked-in. The Checkout process should look at the datetime stamps on the current VL code and issue an alert message that the client copy contains newer source code, Are you sure you want to overwrite the existing source code?

This checking would save many developers a lot of hours of frustration, having to rewrite the code once again. Should be something relatively simple to implement and would be quite beneficial to the LANSA development community.

[jyoung]

We've lost a good chunk of work before when multiple developers were sharing a task.

We filed a support request on it and they were able to duplicate it, but I think the only resolution was the advice to not share tasks.

Lesson learned, never ever ever share tasks.

Joe

[LANSAfolks]

Thanks Joe

I our case, multiple developers work on the same coding assignments across multiple timezones. Managing multiple Task_ID's in this context becomes a nightmare. It has been tried and becomes very unproductive after a while. Hence the suggestion to build some intelligence into the check-out which would result in a simple warning to the developer and prevent code from getting overwritten.

[MarkD]

You are not using developer user profiles that have LANSA security officer or partition owner rights are you?
Doing that may allow you to trample over normal checks.