That’s exactly what you do… declare the event,
i.e.
Private WithEvents btnLaunchaDifferentTracker As EpiButton
instantiate another button, change the GUID to that button’s GUID
btnLaunchaDifferentTracker = CType(csm.GetNativeControlReference("255944ba- Not the same GUID -c439ff554845"), EpiButton)
btnLaunchaDifferentTracker = True
Create another procedure and change the name to your other dashboard,
Private Sub btnLaunchaDifferentTracker _Click(ByVal Sender As Object, ByVal args As EventArgs ) Handles btnLaunchaDifferentTracker.Click
ProcessCaller.LaunchForm(MESMenu, "MyOtherDashboard")
End Sub
Rob Bucek
Production Control Manager
PH: (715) 284-5376 ext 311
Mobile: (715)896-3119
FAX: (715)284-4084
[cid:
1.234354861@...]<
http://www.dsmfg.com/>
(Click the logo to view our site)<
http://www.dsmfg.com/>
From:
vantage@yahoogroups.com [mailto:
vantage@yahoogroups.com]
Sent: Tuesday, November 04, 2014 2:53 PM
To:
vantage@yahoogroups.com
Subject: [Vantage] Adding multiple dashboards to the MES screen
Hi All,
I am trying to link multiple dashboards to the MES screen. I have successfully added one dashboard, and it launches perfectly. To do this I followed the guide below; however, I want to add a second dashboard to a separate button, but I can't figure out how to do this. I can't just copy the script and change the two ID values. Any ideas how to do this?
Summary: CUST: Can I add a dashboard to one of the MES Blank Buttons.
Book: Support Solutions
Page: 5290ESC
PAGE NO:
5290ESC
PROBLEM DESCRIPTION:
Can I add a dashboard to one of the MES blank buttons?
PROBLEM RESOLUTION:
You certainly can.
This topic gets involved, but by all means, if you have permissions to do customizations, you can assign other V8 (the 8.0 application) programs to the blank buttons.
Launch MES in customization mode. See section below on how to setup shortcut for MES Developer. Log in and navigate to a tab that has a blank button. I will use the Production tab as illustration. Right-click somewhere on the form, and in the context menu, select Customization. The screen looks a little bit different. Now, click once on the target (blank) button. The Customization Tools Dialog box appears.
Creating MES Developer Icon
* Make a copy of your MES icon and rename it to something like MES Developer
* Then right click on it and choose Properties
* In the Target field locate where it shows -MES and change it to -MESC.
Understanding the button and properties. The customization window is in two columns: The list of entities (buttons and fields) on the left, and the corresponding properties on the right.
You may wish to reposition the dialog box so that the desired button to customize can still be seen.
When the blank button is clicked on the MES menu, the button name on the left is highlighted, and its corresponding traits appear on the right. In my example, V8 considers this blank button as "btn99" which is highlighted. All properties of btn99 appear on the right.
So what are the pertinent properties?
" EpiBinding: The message that appears when the button is clicked. Right now, a message simply says "not used". Clear this property field.
" Text: The label of the button. This value is blank because the button is blank. For this example, we will open a custom dashboard that reports booking information. Type Bookings Dashboard. If you can also see the MES menu, you will notice that the label now appears on the button.
Saving the setting. Select File - Save Customization.
Script work
So far, so good. We have cosmetically applied the necessary trait to the button - we have enabled it, given it a label, and made it exist in the MES customization framework. Now, we have to get to the "nitty-gritty" of the script, which serves to assign the button with the desired program.
What is a GUID?
A GUID (pronounced GOO-id) is a unique and long combination of letters and numbers for every visible entity in Vantage. A GUID has been assigned to the button you chose, and it cannot be changed. You will note that this property was grayed out for the button.
What is the menu ID?
The menu ID is the unique ID assigned to a menu item, in the eyes of Vantage. This can be determined in Menu Maintenance.
From System Management - Utilities, select Menu Maintenance. In this case the custom dashboard was added to the Executive Analysis > Tracker tree node and give the menu id of UDJRPTst.
Take note of the Menu ID value. You will need it later.
What does the script portion do?
The purpose of the script portion of the button programming is to assign the GUID, and hence the button, to the menu ID, and hence the the desired Vantage program. We will assign the GUID with the , aka Bookings Dashboard.
Using the Event Wizard to create a Load Event.
Here you add a form load event that will enters a unique procedure, btnLaunchTracker, that ties together both the GUID and the menu ID. The GUID comes from the properties of the button that you clicked. You will need to replace the guid with the one associated to the button that you are modifying. Take note that we also enabled this procedure - in effect, enabling the button.
In the Customization Tools Dialog box, click the Wizards tab then choose the Form Event Wizard. Set the selected event type to "Load" and click the right arrow. You will see the following code in the View/Edit Event handling code window.
Use the Wizard to add a form load event. You will see the following in the wizard:
Private Sub MESMenu_Load(ByVal sender As object, ByVal args As EventArgs) Handles MESMenu.Load
'//
'// Add Event Handler Code
'//
End Sub
Add this line to the Private WithEvents section
Private WithEvents btnLaunchTracker As EpiButton
Add these two lines to the code before the End Sub line
btnLaunchTracker = CType(csm.GetNativeControlReference("255944ba-457e-427a-a6f2-c439ff554845"), EpiButton)
btnLaunchTracker.Enabled = True
At the end the code will be:
Private Sub MESMenu_Load(ByVal sender As object, ByVal args As EventArgs) Handles MESMenu.Load
'//
'// Add Event Handler Code
'//
btnLaunchTracker = CType(csm.GetNativeControlReference("255944ba-457e-427a-a6f2-c439ff554845"), EpiButton)
btnLaunchTracker.Enabled = True
End Sub
NOTE: Now change the guid "255944ba-457e-427a-a6f2-c439ff554845" to the correct one.
Finally click the Update All Event Code button.
Review the existing script.
In the Customization Tools Dialog box, click the Script Editor tab. A script appears that controls the logic for the entire customization. It includes declarations, calls to different logic, this, that, the other. Don't worry about understanding what's there. (I don't understand it all myself.)
However, take note of the last line: End Module. This must remain the last line. Take note of the second to the last line: End Sub. That line must stay where it is, as well. In other words, End Sub and upward must stay together, and End Module must remain the very last line.
So: We are interested in the gap between the last End Sub line and the last End Module line.
Adding to the script. You will be adding a click event to launch the dashboard from a menu ID.
What does the custom script do?
The script enters a unique click event, btnLaunchTracker_Click, that ties together both the GUID and the menu ID. The menu ID comes from the entry for the desired program in Menu Maintenance. It will almost certainly have to be replaced by you.
Copy the following lines and paste them into the script editor.
Private Sub btnLaunchTracker_Click(ByVal Sender As Object, ByVal args As EventArgs ) Handles btnLaunchTracker.Click
ProcessCaller.LaunchForm(MESMenu, "UDJRPTst") '<==== enter your menu Id here
End Sub
When you have completed the above the Script code should look like:
'//**************************************************
'// Custom VB.NET code for MESMenu
'// Created: 8/19/2008 12:51:09 PM
'//**************************************************
Imports System
Imports System.Data
Imports System.Diagnostics
Imports System.Windows.Forms
Imports System.ComponentModel
Imports Microsoft.VisualBasic
Imports Epicor.Mfg.UI
Imports Epicor.Mfg.UI.FrameWork
Imports Epicor.Mfg.UI.ExtendedProps
Imports Epicor.Mfg.UI.FormFunctions
Imports Epicor.Mfg.UI.Customization
Imports Epicor.Mfg.UI.Adapters
Imports Epicor.Mfg.UI.Searches
Imports Epicor.Mfg.BO
Module Script
'// ** Wizard Insert Location - Do Not Remove 'Begin/End Wizard Added Module Level Variables' Comments! **
'// Begin Wizard Added Module Level Variables **
'// End Wizard Added Module Level Variables **
'// Add Custom Module Level Variables Here **
Private WithEvents btnLaunchTracker As EpiButton
Sub InitializeCustomCode()
'// ** Wizard Insert Location - Do not delete 'Begin/End Wizard Added Variable Intialization' lines **
'// Begin Wizard Added Variable Intialization
'// End Wizard Added Variable Intialization
'// Begin Custom Method Calls
'// End Custom Method Calls
End Sub
Sub DestroyCustomCode()
'// ** Wizard Insert Location - Do not delete 'Begin/End Wizard Added Object Disposal' lines **
'// Begin Wizard Added Object Disposal
'// End Wizard Added Object Disposal
'// Begin Custom Code Disposal
'// End Custom Code Disposal
End Sub
Private Sub MESMenu_Load(ByVal sender As object, ByVal args As EventArgs) Handles MESMenu.Load
'//
'// Add Event Handler Code
'//
btnLaunchTracker = CType(csm.GetNativeControlReference("255944ba-457e-427a-a6f2-c439ff554845"), EpiButton)
btnLaunchTracker.Enabled = True
End Sub
Private Sub btnLaunchTracker_Click(ByVal Sender As Object, ByVal args As EventArgs ) Handles btnLaunchTracker.Click
ProcessCaller.LaunchForm(MESMenu, "UDJRPTst")
End Sub
End Module
Save and close.
Close the MES menu; click Yes to the Save message. When you open it, you should have yourself a new button that launches the desired program.
[Non-text portions of this message have been removed]