Mono Mode AKA Single User Mode AAKA Administrator Mode AAAKA MONO Function

3 minute read time.

Today I have a short topic for some easy reading. I had someone ask me about it and I thought it might be a nice function to discuss. Plus, I didn’t see it out there on the blog pages, so…

Mono Mode!

We are going to look at what Mono Mode is, and no, not mono as in audio output on your Radio or for Sage X3. Mono mode, AKA Single User Mode, is a function that allows the Administrator (or a user of the Administrator group) to lock-down an Endpoint to where only one Single Administrator user may access that specific endpoint at any given time. Essentially, you can lock an Endpoint folder to where only a “Single User” can access it at a time (hints the single user mode). And…. That one user has-to-be part of the administrator group.

So, why would you want to do that? Why only one? Well, the most obvious reason is updates. If your applying a Custom patch or addon or Standard patch, etc…, you cannot apply stuff like that while users are using the application. Specifically, if they are in the folder you want to update. So, locking the folder so you (the admin) can work, keeps people from messing up your updates or interrupting you or whatever... May not sound like a huge deal because most people have a maintenance window. Right? Well what if that “Director” wanted to take a peek at an inquiry while you’re working, or that “manager” forgot to run a report. That user hops on for like 2-minutes and WHAM, you patch stops because it just hit the Subprogram to update that the use is mid using. Now you have to rerun the 4-hour patch set over again. Lame… All of that is preventable by switching to Mono Mode. Now, that’s just one example of the probable many out there. It just happens to be the reason I use it.

I’m guessing you want to see how it works, right? Well lets jump right to it.

First thing you’ll need is an admin user and a folder you do not mind locking. Once you are logged in and ready to go you’re going to want to go to Development, Utilities, Folders, Mono mode.

As soon as you click on Mono mode function it will automatically run for the endpoint folder you are signed into at that time. You will get a short spinning hourglass and then you will get a message; “You are in single-user mode”.

And that’s it. Super simple I know. Now the folder is in Mono mode and now you can work without anyone else being able to log in.

.

.

.

.

.

Oh yeah, you probably want to know how to turn it off… I should probably mention that.

So, to turn off Mono mode, is very simple too. All you have to do is set it back to multi-user mode.  To get to Multi mode you need to navigate to Development, Utilities, Folders, Multi mode.

As soon as you click on Multi mode function it will automatically run for the endpoint folder you are signed into at that time. You will get a short spinning hourglass and then you will get a message; “You are in multi-user mode”.

Huh, sounds and works just like the single user mode… nice.

 

There, now you have a way to lock and unlock the folder so that only an admin can use the folder. I hope this was enlightening to review as it was for me to write.

Until next time (which will probably be in a day or two because I am behind track)

  • Mono Mode allows for one user with one session. the original point of mono mode was to essentially lock all users out of the folder while the ADMIN would preform patches, hotfixes, etc... it is not the same a single user.. the reason i mention Single User Mode, because this was also a loosely based term customers would refer to mono mode, as single user mode. In the olden days  customers would refer to it as Administrator Mode. 

  • This is very informative! Thank you! 

    Does Single User = Single session? Under Mono Mode, does the system allow the user to be in multiple functions at the same time? Can you also comment on the "Single User" Checkbox on the Task Management function (GESABT)? 

    We have setup a recurring task for FUNSMI task without knowing it's been set as "single user" for a few months, and just recently it started to cause batch server failure. When the task runs, there are usually multiple users in the system. I am surprised that it has not cause issue until now. So I'd like understand more on how the system treats the single user tasks when it get triggered.

    Thank you!