I’m at M3 TechEd in Stockholm. If you are attending don’t miss checking out the hands-on open lab. There are a lot of experts available to help you and show you what we are working on and how we can help you be successful.
Ole Rasmussen presenting M3 product strategy.
Great location at Elite Hotel at Nacka stand. I came in early.
I’ll be on two tracks, Extensibility and User Experience, see you there 😀.
The conventional way to install Infor Smart Office on client machines is to use Microsoft ClickOnce network deployment to get an isolated, secure, self-updating application that can be installed and run with minimal user interaction.
However, if you want to run Infor Smart Office client in a virtualized desktop environment, the Microsoft ClickOnce deployment is not recommended. Instead, install the Infor Smart Office client using the Windows installer (InforSmartOffice.msi) bundled in the software package.
The Windows installer launch a sequence of user interface screens that lead the user through the installation process and gather necessary information. In this case the user needs to enter the Smart Office server URL and the location of the Smart Office features.
For mass deployment it’s more convenient to have a silent scripted install without user interaction and this is possible if you know the name of the public properties for the Smart Office Windows installer and apply the appropriate MSI Command-Line Options.
The public properties for the Smart Office installation are SERVERURL and FEATURELOCATION as described in the Infor Smart Office Installation Guide [ISOIG].
Here is an example of a silent install using msiexec on the command-line run as administrator.
msiexec.exe /I InforSmartOffice.msi /QN /L*V iso_msi_install.log SERVERURL=httpsUrl_to_isoserver FEATURELOCATION=httpsUrl_to_features Explanation of options and parameters: /I Install option InforSmartOffice.msi Set the location path to the InforSmartOffice.msi file /QN No user interface option /L*V Log all information with Verbose output option iso_msi_install.log EXISTING location path to the log file SERVERURL=https... Smart Office server URL FEATURELOCATION=https... Smart Office feature URL
If you don’t have sufficient administrative privileges to do the installation for all users on the machine you will get a failed installation error code [1925] in the log file.
Important information!
Read the Infor Smart Office Installation Guide [ISOIG] for ISO feature limitations and the Virtualization & Hardware Support Statement regarding Smart Office client support for virtualized environments.
Sometimes when you’re developing a Mashup it happens that the data you’re expecting to appear in a databound control is not showing up. There’s a small developer tool named Snoop that will help you examine the runtime visual tree of a Windows Presentation Foundation (WPF) user interface.
Launch Smart Office and open the Mashup Designer. In this post we use an example from the Help menu named Document found in the Infor Document Management category.
Run the example, save it and search for any Document Type e g CLM_Document. Depending on the available data, it will look something like this in the running Mashup.
Now it’s time to launch the Snoop utlitity tool. It has a slim and narrow window. 
Drag the Snoop hair-cross (marked yellow) and drop it on your Mashup window. A new window will open and present the visual tree representation of the user interface in the left-hand panel and the details of the selected UI element in the right-hand panel. Below the details panel there’s a preview panel to render and show the selected UI element (if actived with the power button).
Press down the CTRL- and SHIFT- key simultaneously while you drag the mouse over the Mashup window. The control beneath the mouse will be selected and decorated with a red border and the corresponding element in the Snoop visual tree view will be highlighted and selected. Navigation can also be done directly in the tree-view by selecting UI element nodes.
Let’s examine the bound data for the document attribute panel. Use the mouse or locate and select the LangAttrList (ListBox) in the visual tree. Scroll down in the Properties list until you find ItemsSource property for the ListBox control.
It’s now possible to drill-down into the data collection with a double-click on the value of ItemsSource, in this example [System.Windows.Data.CompositeCollection]. Now you see that the collection contains 1 item: this[0]. You can continue to drill-down with a double-click on the value this[0] to see the details of the item or navigate back up by clicking the up-arrow button (marked yellow).
In this case the ListBox will apply a template for each document attribute found in a collection item. Select the attrTemplate under the ListBoxItem to show its properties. In most template cases the data will be in the DataContext property of the element. Select the Data Context tab for a dedicated view of the property, in this case the DataContext is a piece of XML.
Note that there’s a Binding Errors column in the properties list that will show an error message if the data binding declaration for a UI element property is wrong and the data source can’t be found.
We’ve only scratched the surface of the Snoop tool functionality but it’s the basics needed to investige why your data is not showing up.
When the Smart Office log (debug mode) contains M3 (MForms) time measurements, a tool area will open up beneath the content area with an overview of where the time is spent for the selected time log entry. The purpose of the overview is to put the time values in context and give a better understanding where to look further for perceived performance issues. Note that the chart values don’t always add up exactly due to rounding errors and measurement precision.
Click on the category Timer under the M3 section to focus on the time measurements. Select the first log line and use the up-/down- arrow keyboard keys to scroll through the list and see how the values change in the overview chart.
Depicted here is the standalone version of the Log Viewer, where Smart Office client dependent functionality have been hidden, therefore a few buttons are missing.
In the Tools context menu (found on any log line) you have export options for the measured times. Selecting an export option extracts all measurements and formats them as comma separated values that can be copied into the Clipboard, exported to Microsoft Excel or opened in the Windows associated text viewer.
Exporting the measurements to Microsoft Excel makes it easy to generate a line chart over the measured times for selected function calls.
In the Smart Office client you control the time measurement by launching:
mforms://timer/on mforms://timer/off
The Smart Office log level setting must also be set to Debug.
Smart Office is using Microsoft ClickOnce Technology to achieve a self-updating client that can be installed and launched with minimal user interaction from a central location. Once in a while it can happen that the ClickOnce installation fails and the brief details provided in the error dialog can be hard to interpret. In verbose log mode you can follow the installation step-by-step.
In ISO 10.2.1.0.223 HF23 and beyond the Log Viewer can enable the verbose Microsoft ClickOnce log from the tool menu. The ClickOnce log file setting is active for the current Windows user on the local machine until deactivated.
The verbose log can be activated manually, from another tool or other Smart Office installation by setting Windows Registry values.
Toggle the activation of the verbose ClickOnce log with the Enable Log menu item. A log will be created at the next launch of Smart Office or by any other application using ClickOnce technology. If ClickOnce log is deactivated with an Enable Log uncheck and the activation was not made by this tool, a warning will be presented to inform and verify the deactivation. The ClickOnce.log file is stored in the temporary path defined in the Windows environment.
If a ClickOnce.log file exists, the log content is copied into the Windows Clipboard.
If a ClickOnce.log file exists, the log is opened in the Windows associated text viewer.
If a ClickOnce.log file exists, the folder location will open in Windows File Explorer.
Runs an analysis of the current ClickOnce log and displays a summary overview highlighting the sessions containing errors.
The Clipboard button copies the selected session to the Windows Clipboard and the View External button opens the selected session in the Windows associated text viewer.
As a Smart Office administrator you have the option to generate a file that modify the Windows Registry to enable/disable the ClickOnce verbose log when targeting another Windows client where the Smart Office installation fails. Windows security applies to the launch of registry files.
Select Enable ClickOnce Log to create the EnableClickOnceVerboseLog.reg file. After the file has been created the Windows File Explorer will open to its location. Verify that the named log file location matches the target client, otherwise change it. The default location is the temporary folder of the Windows environment.
Select Enable ClickOnce Log to create the DisableClickOnceVerboseLog.reg file. After the file has been created the Windows File Explorer will open to its location.
If you have a log file sent to you or copied from another machine, set the Enable Log toggle menu as checked and click on the menu Open Log File Location to get a Windows File Explorer showing the target folder. Ensure that the log file is named ClickOnce.log and copy it to the target folder. Now you can select Analyze ClickOnce Log and see the overview in the tool view.
If you’re moving from the Smart Office client to the H5 client for M3, there are two utility tools that will help you to export and transform the compatible favorites of the Smart Office users. You can find the tools in the latest Smart Office delivery package (v10.2.1.0) under the Additional Files Folder; MangoAdminTool.zip and ISOtoH5FavoritesExportTool.zip. Get the zip archives and extract the tools.
For older Smart Office versions read the chapter Importing User Files in Smart Office 10.2 using the MangoAdminTool in the Infor Smart Office Administration Guide (ISOAG_10.2.1 page 254).
Launch the MangoAdminTool.exe, select and login to the Smart Office server.
Launch the FavoritesMigrationTool.exe, browse and select the UserFiles in the temporary folder with the extracted content from MangoData.zip. The favorites for the selected users will be filtered, excluding all links but the ones with http, https and mforms as scheme.
Windows File Explorer will open and show the location of the created ISOtoH5FavoritesExport.zip. In the same folder there is a transformation report named ISOtoH5FavoritesExportReport.txt as a receipt of what has been done during the operation.
Launch the H5 client and select Administration Tools and Import of Favorites.
Done!
Two of the new features in the improved UI are the side-panels with categories to the left and facts to the right.
Every time the selected session changes, relevant support information are extracted and presented in the Fact area, e g Smart Office version, launch method, Windows related version, feature details, languages timeouts etc. The basic facts often needed in a support case.
To compare fact value changes between sessions in the log file, you select the full log file in the session selector. This will list duplicate facts one for each session.
A click on a listed fact will scroll the originating log line into view and select it. The context menu on a selected fact reveals more options that may help you further.
Copy puts the presented value into the Windows Clipboard.
Copy the log entries from where the fact was extracted into the Windows Clipboard.
Show the log entries from where the fact was extracted in the Windows associated text viewer.
Browse is enabled if the fact value is an URL and the user is allowed to launch external applications in Windows according to the Smart Office settings. It will launch the URL in the Windows associated browser application.
Open file location is enabled if the fact value is an existing file path and the user is allowed to launch external applications in Windows according to the Smart Office settings. It will launch the Windows File Explorer and show the folder.
You can create a category in the category area that will collect the log entries that match any of the aspects defined. If you’re a feature or SDK application developer you can create a category that matches the origin i e the namespace of your assembly. Some entries may appear more than once in the result if many aspects matches.
Select one or many log entries that is representative for the category you wish to create and click on Create Category from in the context menu, it will open the category definition dialog with the values from the selection added as options for the category definition.
Select a category Section from the list of existing ones or type a new section name. Name the category in the Header field. Minimize the number of matching values to get fewer more relevant matches. All log entries that contains ANY of the aspects defined will be part of the category.
Press Save button and you will have your category in the left side-panel for quick content selection.
You can create a Shortcut with a parameterized link on the Canvas to launch the Log Viewer on specific content, for debugging scenarios or targeting a specific feature or SDK application. The base launch link for the Log Viewer is:
internal://log
Add a free-text search parameter to start with all entries matching the search criteria, in this example all entries related to user idle detection.
internal://log?search=idledetect
This can be extended with a session parameter to specify the initial session to select in the log. It can be a value [1..n], last will select the current session, prev will select the previous session and full selects the whole log file. Previous is useful if you examine something that happens during shutdown and you examine the log after a restart.
internal://log?search=idledetect&session=2 internal://log?search=idledetect&session=last internal://log?search=idledetect&session=prev
and you can of course specify a category as initial selection e g your custom category
internal://log?cat=service unavailable internal://log?cat=service%20unavailable internal://log?cat=service unavailable&session=full
Finally you have a sessiontime parameter that may be useful in some special cases. If the sessiontime parameter is present, the session parameter is ignored.
internal://log?search=idledetect&sessiontime=13:10
In case you’re thinking about moving from the Smart Office rich client to the browser based H5 client there’s a small tool that will help you bring along H5 applicable Smart Office Links v10.1.0 and onward. The tool is a local Smart Office application to be installed and run by a Smart Office administrator. It will create a zip file intended to be imported with the H5 administration tool.
You can find the tool named INFOR.ISOH5LETool.lawsonapp in the Smart Office delivery package under the Additional Files folder.
H5 links are only global unlike Smart Office that also support private user links, so ensure that all users share the links to be part of the export before performing the operation. The H5 links also requires a specific source to be defined e g MMS001/MMS001BC. The links with ./. as source will be excluded from export.
Launch Smart Office and select My Local Applications menu item on the Smart Office Canvas. Press the Install button, navigate and select the INFOR.ISOH5LETool.lawsonapp in the file browser dialog. Restart the Smart Office client.
Note that it’s also here you uninstall the tool when the export is finished.
Launch Smart Office and launch any M3 transaction e g MMS001 to ensure everything is running and to get the MUA version number. Launch the tool by pressing CTRL+R on the keyboard and type in the focused Start field:
isoh5://linkexport
The tool will appear and show the links compatible with H5. Now you select the links to convert and export. Finish by pressing the Export button and select a location to store the created zip file. Close the tool and Smart Office.
Launch the H5 client and select Administration Tools and Import of Document Links. Press Upload and select the zip file containing the links. Press Import and then restart the server. Done!
Assume that you encounter an issue running Smart Office or have a log file sent to you. To view the content of the log file you can open it in any text reader and perform a free-text search, but even if you know what to look for it’s time consuming.
Open the improved Smart Office log viewer instead and it will show the log entries related to the current session of the running Smart Office. In the session selector you will see when you started this Smart Office session, number of issues found and the time for the latest log entry. The content in the viewer is only refreshed when you launch the viewer, press the Current button or import a previously saved log file.
In the right side-panel, the Smart Office version and Windows related versions are extracted and presented among other interesting facts.
Start the investigation by expanding the left side-panel and under the General header, click and go through in order; Fatal, Errors, Exceptions and Warnings to make a quick examination and see if there are any relevant log entries in each category.
If you encounter a log entry of interest, select it, open the context menu and click the View Selection in Session Context. The full session will now be visible and you can see what has occurred before and after the selected log entry.
To keep track of log entries you can mark lines with a color or do a strikeout to make them stand out when scrolling through the content. Select the lines to mark and use the context Mark menu to perform the action. To retrieve the marked lines click on the categories under Markers in the left side-panel. The markers will disappear when the log viewer is closed and restarted.
Errors and exception log entries can automatically be marked in the left margin with a colored line, if the Enable Color Markers option is set in the context menu.
The Smart Office log file is renewed every calendar day and the previous one is renamed with the date added as a suffix on the filename. The log files from the last week are stored beside the current log in the client data area.
Open a previous log file by pressing the Import button while holding down the SHIFT- or CTRL- key to add the necessary filter option and set the target directory to the client data area. In the dialog that appears you select the Old Log Files filter and the existing logs from the last week appears.
The S3 Excel add-in has a separate log file that is also located in the client data area. Perform the same operation as when looking for older log files but look for files whose name starts with S3.ExcelAddin.log.
There are a couple of ways for you to share the log content with support or another helpful person.
Takes a snapshot of the Log Viewer window and put it in the Clipboard. This is intended for documentation and communication, but not useful to send in a support request.
Copy the full log of the selected session into the Windows Clipboard.
Open the log file in the Windows associated text viewer.
Create a new mail in Microsoft Outlook with Smart Office support related files zipped in an attachment.
Create a new mail in Microsoft Outlook with the full log file as an attachment.
If you received a help request or a support ticket with a log file attached, you can view it in the Log Viewer to make a quick review of the content and get the basic facts extracted about versions and runtime environment. You can open the log from the Windows Clipboard or the filesystem. Press the Current button to reload the active Smart Office log file.
Reload and show the current Smart Office log file.
Show the log file found in the Windows Clipboard.
Open a log file stored in the file system. Press SHIFT- or CTRL- when the button is pressed to set the client data area as initial directory.
Smart Office enables the user to adjust the overall appearance of its canvas and windows in terms of theme color, wallpaper and color saturation from a pre-defined set of options.
The boundaries for what the user is allowed to adjust is set by the Smart Office administrator in the system profile, application- and user- settings. The final appearance is the combined result of the settings and internal rules.
Once in a while it happens that the appearance is not matching the expectation after an upgrade or settings change. It can be difficult to pin-point and determine what is causing the new appearance.
The Theme Emulator tool will assisst you to sort things out. It will hook into the theme service and regard it as a black box, apply your settings and visualize the result unaware of the internal rules.
The Theme Emulator is launched with the Smart Office link internal://themeulator or via the improved Log Viewer content-area context-menu under Tools.
When the Theme Emulator tool is launched it will show the current applied Smart Office settings in the Preview Settings- and Preview- area. The current values in the system profile, application- and user- settings are listed under Theme Setting Sources.
Changing the Preview Settings is harmless and will only affect the look of the Preview area. Click on the ‘Reset’ button to return to the current settings. The padlock icon next to each user setting show if the setting can be changed by the user or has been locked by the administrator.
A click on a preview icon (document/looking-glass) beside the theme source header will apply the current settings for that source on the Preview.
The Settings… and Profile… button will launch the corresponding administration tool if the current user is a Smart Office administrator.
The Clipboard button captures a snapshot image of the tool window and puts it in the Windows Clipboard. It can be useful for documentation and communication purposes.
The User Theme Disabled checkbox is always read-only in the ‘Preview Settings’ area. It’s not intended to be changed, just show the current property value.
Elaborate with the preview values and compare with the setting sources and you will soon figure out the source and what setting to change to get the wanted appearance.
If you have implemented a feature or SDK application that retrieves the user id from the user context, you should ensure that you use:
ApplicationServices.UserContext.UserId
and NOT the property
ApplicationServices.UserContext.UserName
The UserId and UserName property returned the same value in many system configurations until a few years ago when additional security configuration options were introduced. To be on the safe side and be future proof, the UserName property should be used for display purposes in the user interface and the UserId property used for REST calls and business functions.
An improved user interface for Smart Office Log Viewer was introduced in 10.2.1.0.189 (HF18) to make it easier and more efficient to resolve issues and find relevant information. The benefits and features of the improved user interface will be covered in a series of blog posts.
The main new features are:
The improved user interface consists of:
At the bottom you have the quick access buttons to import- and share- the log file.
On the very first launch after installation the (2) Category- and (4) Facts- areas will be collapsed. You can expand/collapse the areas by dragging the window splitters or click the Verbose toggle button.
• Open the Smart Office About dialog and click on the link.
• Open the Administration Tools folder in the Navigator Widget and launch Log Viewer.
• Launch the Smart Office link internal://log using a Canvas Shortcut or using the Canvas Start field (CTRL+R).
• As a Standalone Windows Application found in LogViewer.zip under Additional Files in the Smart Office installation package.
You can switch to the original user interface by clicking on the Classic button, create a Canvas Shortcut or Navigator Widget Favorites link with the URL internal://log/classic.
You can create one or more categories specific for your feature and define a launch link that will open the Log Viewer with your category selected. How to do this will be covered in an upcoming blog post.
It’s been quite some time since I published on this Blog. I’ll see if I can get the Smart Office Developers to write some more posts. Don’t forget to check out the Infor Technology blog where you can find Lawson Smart Office related posts.
There are a few new features in Smart Office related to the Ming.le feature and the Ming.le integration.
I currently work on Ming.le Homepages so there is not that much time to write posts but we all help out trying to answer your comments and questions. If you like to know more about Homepages, please read Infor Homepages: Your hub across Infor OS.
If you have implemented a feature or SDK application that requests the credentials from the user context when calling services the include-domain-with-user parameter must be true in order to function properly with an environment using ADFS 3.0.
If the user logs in to Smart Office as user@domain or domain\user setting the parameter true ensures that the domain is included in the user name.
If you’re using the MangoHttpClient class for doing REST calls it’s already handled for you so no changes are necessary. The ADFS 3.0 support was introduced in Smart Office 10.2.10.88 (HF12) released in March 4th 2016.
It may be necessary for a ISO feature/application to change one argument when requesting credentials from the Smart Office user context in order to support ADFS 3.0. The parameter includeDomainWithUser should be set to true. This will return the user name including the domain, if the user logged on to Smart Office with a domain, otherwise it will only return the user name.
Existing code that looks like this:
ApplicationServices.UserContext.RequestCredentials(out username, out password);
ApplicationServices.UserContext.RequestCredentials(out username, out password, false);
Should be changed to set includeDomainWithUser argument to true:
ApplicationServices.UserContext.RequestCredentials(out username, out password, true);
There is also a new LDAP Setting described in the Administration Guide (p. 267) ”Add domain after authentication” that you should be aware of.
This setting is used in scenarios where some applications such as IDM requires a domain but the Smart Office server does not require one. When the setting is enabled, a user may log-on without a domain to Smart Office and still be authenticated with domain for the application.
Settings values:
No = Not enabled
Yes (user@domain) = Enabled with the username format “User Principal Name”.
Yes (domain\user) = Enabled with the user nameformat “Down-Level Logon Name”.
M3 has created a Knowledge base article on the search syntax for Search in M3 13.3 and 13.4. M3 Infor Enterprise Search is a great tool which can greatly improve your workflow when used in the way it has been designed to work.
Depending on how you are using Enterprise Search (IES) today, you might have encountered a few instances where it has not retrieved the desired result.
This can in many cases be addressed by altering your search query to be better suited for the Lucene Search Engine which IES is built upon.
In this blog post I’ll do a quick overview of some of the queries from the examples in the Knowledge based article as a introduction but I recommend you to read the full article as it contains even more examples. I just wanted to take some of the material and the references so that it is easier to find if you search for tips on this blog, which I know a lot of our readers do.
Please note that if you are new to Enterprise Search there are available courses and How-to videos at the Sales Portal and the Infor Campus.
This is the simplest form of search with entry of full words. Note that search is always case insensitive. Searching for cheese would give you the following result:
You can enter multiple words in the search field but those values have to be displayed in the list. The default behaviour when using multiple words in search is applying AND for all words. This means that they have to exist in one or more columns. Using OR means one of them must exist in one of the columns which will result on more hits. Use parentheses to combine blocks of AND and OR. Use wild card to enter the first part of a word. Or a ‘?’ to replace a single character. Note that you can’t replace blank space.
Examples:
cheese OR juice
cheese OR (juice 011215) - Combine with ()
chee* - starts with chee
chee*jui?e - ? replace a single character
To limit the search to a specific column, right click on the column and select ‘Add to search’. It will add a column prefix to the search.
ITDS:Cheese
Dates and numeric values are entered in the same date format as the user has in MNS150, the user master. Dates can be entered with 6 or 8 digits.
Intervals
Intervals are done using the following two formats [ x TO y] or { x TO y } or any combination of them. Usage of [] means that the range should be included in the search where as {} means that the range should be excluded.
Examples
STQT:[100 TO 480]
STQT:[* to 0} - find all items with negative quantity
Not conditions and use of ?
Not conditions are a bit special since they must start with another query and then the NOT condition can be introduced. The tip if there is no such natural condition is to start with the company number and then add the NOT search. The company number will search the entire table. An example query in MMS002 of all items that have not been part of a stock take in this year will look like this:
CONO:790 NOT INDT:YEAR(0)
Note the YEAR(0) function that will translate to an interval covering the to and from dates of the current year. There are a number of functions that can be used to create useful Macros that can be saved to favorites, canvas, as menu option or in toolbox area.
Creative usage of the ? allows for a simple search for all records with supplier number. This since ? only finds records with a character in the position. Blanks are omitted. Query SUNO:?* gives you all records with a supplier number in this case. For numeric fields you use the NOT statement like CONO:780 NOT STQT :0.
SUNO:?*
CONO:780 NOT STQT :0
Fuzzy search
The ~ is used for a fuzzy search that is useful for finding spelling errors and similar texts. An example would be a query like ‘min*~’ which would produce hits even if there is no exact match on anything starting with min, for example mild would also be a hit in this case. Not that it cannot be used for numeric values.
The full article covers more examples!
SortBy:x,y,!z Sorts search result in x, y z hierarchy. The ! Prior field name perform a descending sorting (NCR 6670 and 6671)
SearchFields:x;y Limits search to listed fields x, y etc. Increases performance and can eliminate false hits
YEAR(x) Replaces with date range of year relative to current year x=-1 equals last year etc
MONTH(x) Same as YEAR but for month
WEEK(x) Same as YEAR but for week
DATE(x) Similar to YEAR but replaces with specific date
<xxxx> List & list header based replacements to query string. (NCR 6813)
All below are described in NCR 6220
Using the value within you can use the following replacement variables.
<USID> Replaced by logged on user id
<CONO> Replaced by logged on company number
<DIVI> Replaced by logged on Division. Note – same as <CurrentDivison>
<FACI> Replaced by default facility from user master (MNS150)
<CUNO> Replaced by customer no from user master
<LNCD> Replaced by language code from user master
<TIZO> Replaced by time zone from user master
<WHLO> Replaced by warehouse from user master
<DEPT> Replaced by department from user master
<MNVR> Replaced by menu version from user master
<DFMN> Replaced by menu name from user master
<CurrentLanguage> Replaced by currently used language in M3 (in case of switched language during logged in session)
<CurrentDivision> Current division. Note that this is the same as DIVI.
Reserved word for key search only
Stop words in IES has the meaning of words that are not indexed and are automatically removed from the search query. Examples of stop words are “and”, “or” “etc” and other similar types. IES, by default has a set of English based stop words which apart from above examples also includes “a”, “by”, “is”, “as” plus about 20 other words. Unfortunately in many cases when searching ERP type of data you might want to search for “factor a”, the Swedish word for ice “is” etc.
The work around for this is to add a new stop word in the IES admin pages. Make sure it is something never search for like “lksdhja7789”. By doing that the default stop words are not used anymore. Please note that affected tables like MITMAS, MITLAD, OCUSMA, CIDMAS etc need to be re-indexed after this has been done.
Read more examples in the KB.
Infor Smart Office for Lawson applications provides many custom features which are made possible by meta-data retrieved from the Lawson application server in the background. But these features come at a cost of increased network traffic and additional server utilization which could impact performance.
In a post on the Infor Technology Blog, Vince McGowan explains what meta data services are used for and how to disable them. He identifies the background activity and describe the purpose of each so clients can decide whether or not the feature is useful enough to incur the cost. If not, there are settings provided to disable them.
Head over to the Infor Technology blog to read the full article.
See more at: http://blogs.infor.com/technology/2017/01/background-server-calls-made-by-infor-smart-office-for-lawson-applications/
In this blog post I’ll show you some screenshots how you can download a feature fix for Smart Office. In this case it is the fix for Process Server. I’ll show you the steps to download the fix and get the contained ZIP to be able to extract all the content that is in the zip. The zip might contain a feature to be installed or the full zip that contains extra tools for Smart Office.
The new version of the application is available and you can uninstall the previous version and install this new one. In most cases you need to do an upgrade (as described below) but after HF18 and with ProcessServerAndLandmarkAdapters you would want to make a new install at this time. But for HF 19 and later you can go ahead and upgrade.
Special thanks to Noreen for providing all these steps!
If you have Process Server installed running on Landmark we would recommend that you skip HF18 (HF= Hot-Fix), HF19 and wait for HF20 that will be delivered at the end of January 2017 or apply Post Patch for Infor Smart Office 10.2.1 Core HF19 – IPA Update Only available as a CCSS fix (ef_ISO1021_HF19_LPA.zip)
Another important message is that installations done before Smart Office 10.2.1 HF18 must uninstall existing earlier version of Process Server component before applying HF 18 or later. Read more in the Installation Guide section – Configuring Infor Process Automation or ProcessFlow for use with Infor Smart Office.
That means that if you have Process Server feature installed in a pre-HF18 version of Smart Office, version 10.2.1.0.169 or previous versions, then you must uninstall the Process Server application in LCM and install it again. The reason is that the features included have changed. As of HF18 you should only have one Process Server related feature called Infor.PF in the Manage Installation Point tool.
Previously we had Infor.PF10, Infor.LMRK10, Infor.LMRKA10, se below:
Make sure you uninstall en re-install and that you don’t have these old features in the Installation Point Manager. There is also an Manage Application view within the Grid Management pages for MangoServer administration where you can see which applications, features and mashups are installed by accessing the Grid Management UI on the server where the server component for Smart Office (MangoServer) is installed.
But as of HF18 there should only be one new Infor.PF feature and the previous should not be used. There is no need to reconfigure anything but you must uninstall the previous version and install the new version. You get the new .lawsonapp from the hotfix that is downloaded in LCM. In my next post I’ll show you how.
All education sessions. All products. All industries. Customers, partners, employees—all in one location for 2½ days of learning, sharing and networking. Register before January 31 to get the early early bird rate and join us at the Javits Center in New York. For details see the Inforum 2017 website.
We built our headquarters in the center of New York’s Silicon Alley —to let the city shape us, just like we help shape the companies that do business not just here but everywhere. Come see for yourself at Inforum 2016 on July 10-13 in New York City. http://www.inforum2016.com/
Wow… New York. Sweden and Stockholm can’t compare. I know a few colleagues that are traveling and I hope that you all can enjoy this great event. If you like me are unable to go to New York you can still follow online:
Developing for Infor Smart Office 
You must be logged in to post a comment.