Ir al contenido principal

How to Modify a Process Flow in Sage Enterprise Management (Sage X3)

How to Modify a Process Flow in Sage Enterprise Management (Sage X3)
At its most rudimentary, a process flow is a collection of functions that allow users to complete a business process, and Sage Enterprise Management (Sage X3) offers more than 700 out-of-the-box process flows. They range in scope from things as simple as managing data to things as complex as analyzing production consumption and costs.

Even with so many options to choose from, there is still the possibility that what comes out of the box might need to be slightly tweaked to cater to the specific needs of your organization. The purpose of this blog is to show you how we can leverage what Enterprise Management gives us and either add to or delete from an existing process flow.

Let’s say you want to create a process flow that includes only the sales orders, deliveries and invoices functions from Enterprise Management. We’ll want to find an existing process flow that’s similar to this so we can use that as our template.

Here's how to modify a process flow in Sage Enterprise Management:

Our first steps will be to log into Enterprise Management, navigate to the setup module, scroll down to the Interactive dashboard block, and open the processes function:
how to modify a process flow in Sage Enterprise Management (Sage X3)

Once inside of this function, you can use the filters on the left-hand side of the screen to search for any process you’d like to use as a template for your custom process flow. I will use “order to cash” for this example, since I know that it contains the 3 functions previously mentioned:
how to modify a process flow in Sage Enterprise Management (Sage X3)


The Drawing tab shows the process flow itself. Note that each of the ‘blocks’ within this flow points to a specific function within Enterprise Management:


how to modify a process flow in Sage Enterprise Management (Sage X3)



Rather than modifying the canned Enterprise Management process flow, I created a new one by changing the process code to “ORDTOINV” and deleting all the ‘blocks’ that will be unnecessary for the flow that I want to create:

how to modify a process flow in Sage Enterprise Management (Sage X3)


Our next set of steps will be to navigate to the Administration module, scroll down to the authoring block, open the menu items function, and click on the “Create Menu Item” button:


how to modify a process flow in Sage Enterprise Management (Sage X3)

 There are many fields to fill in here, but the most important ones are the following:


how to modify a process flow in Sage Enterprise Management (Sage X3)

Our last set of steps will involve creating the landing page for our process flow. Navigate to the upper-right hand corner of the screen and open the ‘home’ icon:

how to modify a process flow in Sage Enterprise Management (Sage X3)


From there, navigate to the left-hand portion of the screen and click on the ‘New’ button:


how to modify a process flow in Sage Enterprise Management (Sage X3)


Assign a page name (note that spaces aren’t allowed) and title to the landing page:


how to modify a process flow in Sage Enterprise Management (Sage X3)


Click on Processes:

how to modify a process flow in Sage Enterprise Management (Sage X3)


Click on the newly created “Order to Invoice” menu item:


how to modify a process flow in Sage Enterprise Management (Sage X3)


And that is how you modify a current process flow to your specifications within Sage Enterprise Management!

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

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

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