Ir al contenido principal

Disconnecting Web Sessions in Sage X3

NEW - BADGES LICENSING STRUCTURE

With the release of Version 7, Sage implemented a new licensing structure called badges. When you purchase users for Sage X3, you specify the type of badge you are buying and each user in X3 is associated with a badge through their specific group and role. The badges are concurrent licenses so if you have 2 ERPDEV badges, when the 3rd user logs in under that badge they will get a message stating the “User does not have any badge for Product Sage ERP X3”.
X3 Navigation

DETERMINING BADGES IN USE

If you have permissions to the Administration module you can still access the Administration module even if you do not have a badge.  In order to see who may be using the badges in X3, you can go to the Administration module menu, Tools, Web client sessions.
X3 Badges

EXAMPLE

In this example, you can see there are 2 users logged in as admin, but only 1 user has a Badge. If you are using Chrome as your browser, you can hit Ctrl-Shift-I and go to the Resources Tab and choose Cookies from the left menu to see what Session ID you are using with this browser. Hitting Ctrl-Shift-I again will toggle the session detail off on Chrome.
X3 Sessions Example
If you determine that one of the sessions is not in use or shouldn’t be logged in, you can click the action button beside the session id and choose Disconnect to end the session.
X3 Sessions Example
Then you can log out of Sage X3 and log in again to get the badge you just made available
.

Entradas populares de este blog

Valores de fstat

Fstat fstat  is a numeric status that is returned upon execution of a database operation, a sequential file operation, or a lock instruction. Syntax fstat Examples # MYTABLE is a table with a key called KEY1, that has a unique component called KEYVAL # Create a record in the table MYTABLE with they key value 1 if it doesn't exist Local File MYTABLE [MYT] Read [MYT]KEY1=1 If fstat [MYT]KEYVAL=1 : Write [MYT] If fstat MSG="The key was created in the mean time" Else MSG="Key created" Endif Else MSG="Key already exists" Endif Details fstat  is always set to '0' if the operation is successfully completed, and has a non-null value if there is an error: In a sequential read ( Getseq  and  Rdseq ),  fstat  is set to '1' at the end of the file. On  Lock ,  fstat  is set to '1' if the lock could not be performed. For a database operation ( Read ,  Look ,  Readlock ,  For ,  Write ,  ...

SAGE X3 SILENT IMPORT (IMPORTSIL) WITH ERROR CATCHING

FUENTE ORIGINAL: https://pluginx3.com/en/blog/post/sage-x3-silent-import-importsil-with-error-catching.html You already know how to manually generate a CSV file in order to import it threw a template in Sage X3. But If you wonder how to catch detailed errors after a silent import here is the solution. Sometimes you need to catch the incoming errors in order to alert the end-user regarding an issue. Closed period, wrong date etc …. Unfortunalty the standard Sage X3 silent import function doesn’t natively show the detailed errors during the import process. Call IMPORTSIL([M:IMP2]MODIMP,[M:IMP2]NOMIMP) From GIMPOBJ And the standard function ERR_IMPORT will only show the overall status of the importation and not the detailed errors. IMPORTSIL function is pushing all the log data into a tracefile in order to avoid any popup on end-user screen. So you have a log file available in order to search for errors in it. Sage X3 runtime is using the same principals standards as any shell for log...

3 ways to send a mail from code in Sage X3, with more attachments too

Origen Fuente:  https://en.sagedev.it/sagex3/send-mail-from-code-with-attachments-sage-x3/ Autor:  https://en.sagedev.it/category/sagex3/ In this post I’ll show you how to send a mail from adonix code in Sage X3. The points we will face are: 1) Meladx/Send introduction 2) Sending  through  meladx (the best way for me: at the end with just a single code line you send a mail!) 3) Sending  through  Workflow 4) Sending  through  ENVOI_MAIL(…) From AWRKMEL Sending mail from code in Sage X3: Send vs meladx Sage X3 has two native ways for sending mails. The first way is  meladx  executable file, that you can find in  runtime\bin  directory. The seconde one is Send instruction, that was used to send mail through an application of the client station (for more information on “Send GSERMES”  go here ). The Meladx executable Meladx send messages through SMTP/POP3 protocols by means of the mail  ...