Sage X3

SUBPROG TEST() Local Integer OK Local Char linput(250) Local Char ztitle : ztitle = 'introduce texto' Local Char zfldtit : zfldtit = "texto:" Local Char zobj : zobj="FRM" # OBJETO O TIPO DE DATO ZOBJ = "CLX" call SAICAR(LINPUT,ZTITLE,ZFLDTIT,ZOBJ ,0,0,"",OK) FROM GESECRAN IF LINPUT <> '' THEN infbox LINPUT ENDIF END

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 3 rd  user logs in under that badge they will get a message stating the “User does not have any badge for Product Sage ERP X3”. 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. 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

Description Error: " Your convergence sessions have been closed because of timeout " when a session has been idle for more 20 minutes. The Timeout parameters  TIMEHGUP1 , TIMEHGUP2  and  TIMEHGUP3  are already set to 0 for no timeout. How do I set the timeout for Sage X3? Note:  This article only applies to X3  v7  and higher . as time out is handled by a Syracuse setting. TIMEHGUPx  settings are no longer used in v7 and higher.   For X3  v6  and lower , see knowledgebase article  18654  below. Disclaimer Backup Warning Use caution when working with the below product functionality. Always create a backup of your data before proceeding with advanced solutions. If necessary, seek the assistance of a qualified Sage business partner, network administrator, or Sage customer support analyst. Database Warning These steps require knowledge of database engines and application databases (DBs) used by your Sage product (including Microsoft/Transact SQL,

Description How to manage user timeouts in Sage Enterprise Management . Time Out Management Parameters - TIMEHGUP1, TIMEHGUP2, TIMEHGUP3 Note : This article applies to Enterprise Management  v6  and prior . For Enterprise Management  v7  and higher , see KB article  41016  below. Resolution Note : This article applies to Enterprise Management   v6  and prior .  For Enterprise Management  v7  and higher , see KB article  41016  below. ( 41016 ) The Parameters  TIMEHGUP1 ,  TIMEHGUP2 ,  TIMEHGUP3  can be set at the User level Parameter Definition  tab of the  User  - under  Module   -   Supervisor  and  Group - SES Parameter -  TIMEHGUP1 This is the time limit, in seconds, that the user has not used the keyboard before which a message is displayed indicating that a user disconnection is imminent.  If nothing has been entered on the keyboard after a second time delay defined by the  TIMEHGUP2  parameter, the user will be disconnected. Parameter -  TIMEHGU

Here how to open an Input Box and get the value inserted by the user Local Integer OK Local Char VALEUR   #SOH = Object Sale Order Call SAICAR(VALEUR, "Title of window" , "Field caption" , "SOH" ,0,0, "" ,OK) From GESECRAN   Infbox VALEUR + " " + num$(OK) Here the screenshot of the Input box as per the previous code example: Sage X3 Input Box The value inserted is stored in the variable VALEUR and to know which button is clicked you can refer at the variable OK: OK = 2 button OK is clicked OK = 1 button Fine is clicked

Often, when our prospects are  evaluating Sage Enterprise Management (Sage X3)  and trying to differentiate it from other competing products, they’re very impressed with the level of personalization and flexibility that comes inherent with the product. You can think of conditional formatting as automatic formatting that’s triggered by conditions you define. For example, you can use conditional formatting to automatically change the color of cells that contain values greater than or less than certain values. Conditional formatting is a great way to visually highlight important information and, as part of our demonstrations, we’re frequently asked to show how Sage Enterprise Management can color code certain fields based on a set of business rules. Request a   Sage Enterprise Management (Sage X3) Demo  » While prospects are typically impressed at Enterprise Management’s ability to do this, we find that they rarely take advantage of it once the system is implement

Origen:  https://en.sagedev.it/sagex3/strings-replace-function/ Autor:  Adonix does not provide an instruction for replacing a string part. The only existent instruction is ctrans(STR,"AB","C") that substitutes into the STR string all occurrences of ‘A’ and ‘B’ letters into ‘C’ letter. Note that it does not replace string “AB”, but all occurrences of ‘A’ letter and all occurrences of ‘B’ letter. We remedy this miss implementing a REPLACE function and a his wrapper too, so we can manage with the same code both simple strings both clobs. # #File YSAGEDEV # ############################################################################# # Author: SageDev.it # It substitutes all occurrences of OLD with NEW # STR is a clob ############################################################################# Funprog REPLACE(STR, OLD, NEW)     Value Clbfile STR()     Value Char OLD()     Value Char NEW()     Local Integer LENOLD     Local Integer LENNEW     #l

In Sage X3 we can setting execution scheduling of a command using the SYSTEME Sage x3 job. You can manage the Sage x3 jobs with  Usage\Batch Server\Task management  menu (GESABT function). As parameter we pass it the system command to execute, for example “ C:\temp\command.bat par1 par2″,   and that’s it. If by chance we need to move this scheduling from a Sage X3 folder to another, to pass the name Sage x3 folder as dynamic parameter can be useful, so we do not have to modify the command to pass to the job SYSTEME every time. To do this just create a job SYSTEME wrapper. The SYSTEME  job  call the homonym SYSTEME  action , which has as unique parameter the command string to execute; to reach our target so we will create a YSYSTEME job and a YSYSTEME action. But this EXESYS action what do it do precisely? It call a subprog of ORDSYS. Here an example: the following code line executes the batch command  Command.bat that is present in the directory  c:\DIR\SUB\ Call SYST