Ir al contenido principal

Creating a Function to Call a Requester in Sage X3 V7 and After - Ejecución peticionario desde un menú

 

Creating a Function to Call a Requester in Sage X3 V7 and After

By:  | Category: ERP

Fuente origen: https://www.netatwork.com/creating-a-function-to-call-a-requester-in-sage-x3-erp-v7-and-after/

Saving a few clicks to open something is a good opportunity to showcase the capabilities of a system like Sage X3, so when a client asked us to create a function to call a requester, we took on the challenge.

function to call a requester

After you create your requester in Sage X3, you can go to the set-up function where you built the requester and click ‘Run.’

function to call a requester
You can also go to Reports > View queries, search for the appropriate query, and run it.

function to call a requester

function to call a requester

To avoid searching for records or giving access to the view queries function, you can follow the steps below to create a function that will call a requester.

The first step is to create a function in the development area. While it sounds complicated, it’s really very straightforward and requires very few pieces of information.

In our example, we’ll create a function that will call the Order to Receive by Supplier requester shown above.

Go to Development > Script dictionary > Functions

function to call a requester

Note: you can use an activity code to protect it against eventual updates or to be able to put it in a patch.

Then go to the second tab, Action, and enter the following:

function to call a requester

Now that you’ve created the function, you need to create the associated menu item. Go to Administration > Authoring > Pages > Menu Items.

Create it by entering the information as follows:

function to call a requester

Choose a self-explanatory title, as it will be the name you see in the menu later. While you can take a look at your work when you create your menu item, the work isn’t finished.

The last piece to this puzzle is specifying where you want this function to appear.

To do so, place this menu item in a module, submodule, and sometimes in a group of functions in a submodule. Right now, what we’ll do is place this new function in the purchasing module under the different Orders inquiries.

Go to Administration > Authoring > Navigation pages and create it in each of the navigation pages you are maintaining for all the roles you created during your security configurations.

In our example, we’ll add it to the out-of-the-box navigation page called Administration dashboard.

Locate it and then edit it by clicking on the pencil on the line.

function to call a requester

Then click on Edit page content on the right-hand side of the page that just opened.

function to call a requester

Click on the purchasing module, then inquiries, and add it to the Orders group by clicking on the magnifying glass to select a menu item.

function to call a requester

Select it from the list as shown below:

function to call a requester

It should now appear in the list of functions available in that group. No need to save anything here; it will save automatically.

The function is also available in the inquiries section of the purchasing module under orders as specified in the navigation page configuration above. (Changes are immediate.)

function to call a requester

Click on the function and it will look exactly as if you were viewing it using the two methods described at the beginning of this tutorial.

function to call a requester

And that’s how you go about creating a fuction to call a requester in Sage X3!

We hope you find this useful. If you need additional information for creating a function that calls a requester or anything Sage X3 related, please contact us. We’re here to help you make the most of this great product.

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 ,  ...

How to create an additional line text (ACLOB) on purchase orders for internal notes

Sin conexión Kyle Klinger hace 1 día Origen:  https://www.sagecity.com/support_communities/sage_erp_x3/f/sage-x3-general-discussion-forum/143870/how-to-create-an-additional-line-text-aclob-on-purchase-orders-for-internal-notes I was trying to add internal notes to the purchase orders at a line level and was thought I would share a how to.  If you have a better way, please share.     Add column to PORDERQ; YLINTEX2, Type TXC   Save and validate table This is where the ID of the text will be stored at the record level, i.e. POQ~00000007, this is similar to field LINTEX  On screen POH2 Add column YLINTEX2, to Block 1. Most likely you will want this field to be hidden. On column NBLIG add a button action ACLOB2, description "Text internal" This button action will require an action parameter "CODE2", it will not be available until after save. Set the parameter "CODE2" to [M:POH2]YLINTEX2(nolign-2), the field that was just added....

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  ...