WHY VINCE SOLUTIONS?

If you have a request that is not supported in M3 standard, or you have requirements that don’t fit the current process, we help rectify that for you. The requirements can include anything from:

H5 SCRIPT

Adding support information into a M3 Panel.
Or need simple added functionality in a M3 panel?
Start using H5 scripting.

WEB APPS

Wanting to simplify the process in M3?
Do you need to integrate information from several systems into on UI?
Start using Vince web apps, who can run in H5, Smart Office or as stand alone.

There are tons of different requests for functionality here where you can simplify and create a more integrated process for your end-users. Solutions will help you achieve this goal. We are the the creative part of Vince’s business development. In a nutshell, we do web development either using M3 as backend or we integrate our web apps between M3 and other stand-alone applications. Everything we do has cloud solutions in mind as we want to contribute to our clients’ “journey”.

Our team is divided into several areas:
Functional designers who have extensive experience in M3 and varying business processes, including master data. They also know how to integrate UI and UX where M3 is a part of the solution. We also have experience integrating other software with M3. We do expect this to become more relevant in the future. M3 is gradually becoming the business engine we predicted for years. We have an experienced web development team that specializes in state of the art UI front-end and back-end development. They are all well-versed with M3 and other software, too. Together, our team have long experience in handling  UI/UX development who help us create web applications. Additionally, we have an application designer who works closely with our CTO to ensure that we are working with the latest cloud technology.

Our web applications can be run in M3’s H5 client, Smart Office or as a standalone web application. We strive to develop solutions and make them available for a future M3 cloud edition environment. By this, we are working with the Infor ION gateway to make sure we are communicating correctly with M3. This again means that we are focusing on the Infor Extensibility toolbox, which includes lots of different tools that work closely with the Infor Software. We do scripting (including H5 scripting), we use parts of Infor’s Software Development Kit, and we also do upgrades of Smart Office Mashups, so they can run in the H5 WebClient. We are also working with Infor OS and widgets. If it helps to make the solutions more robust, we include Infor’s Event Hub and analytics to our solutions. The latest tool we are looking into is extendM3, which makes it possible to perform solutions closely connected to the M3 java code, but securely using safe exit points.

Vince Solutions is here to help you on your journey to the cloud.

Please take a closer look at some of the web applications we have created for our customers. They all include modules we have developed to make our web development as efficient as possible with re-usable components.

Want to know more about H5 Scripting?

WATCH NOW

Want to learn more about how VXL works?

See how VXL can simplify the management of data and transactions in Infor M3

VINCE Web Apps and H5 Script for user friendly workflows in M3

VINCE provides web apps and H5 scripts to ensure your business runs as smoothly as possible. We create web applications which can be tailored to your specific needs and wishes.

Vince web apps in general:

For web applications to be run in Infor’s Smart Office or H5 web client, we use components from Infor’s Software Development Kit. With reusable methods in our UI and UX, we are developing independent components to make it more efficient to do “next development” or project. In theory, Vince Web apps is used as a template where we create a project exactly how you, the customer, want it. However, we always have a starting point from our “template toolbox”. Our customers decide if the UI should have a look and feel close to M3 (in H5-Odin) or if they want something more unique. Whatever your choice, Vince can help you with this. We use the sprint development method, normally 2-week sprints. But we are flexible. All development issues are documented in Jira as user stories. Every project has a web coordinator who is working closely with the customer and our web development team. The development team is led by a single team leader and we have our own UI/UX developer to secure an efficient UI and UX.

3 examples of web applications we developed together with our customers

Case information

This customer has lots of shops across several Nordic countries. Their retail business consists of selling flowers. Items are constantly moved around the shop, numerous promotions are being run, and orders vary from week to week drastically. Therefore, M3’s standard set up of locations is not flexible enough when it comes to picklist handling and picklist reporting. The app is all based on standard M3, so there are no modifications within the software, but we have developed a way to use M3 customize tables (CUGEX1-CUGX3) as a “layer on top” of standard M3. Because of this, we can keep track of customer orders that are ready for picking (status 44). Moreover, in the app, you can plan how to print out and do the picklist across customer orders. This enables the shop manager to plan the pick and pack in a way that proves the most efficient. The application is “workflow-based”, which means there are different steps to follow in the application itself. The application runs within M3’s H5 client due to the close relation to the users which exist in M3. So, the setup of users in M3’s MNS150 is vital for when displaying shop/users. The application is also responsive, so you can run it on handheld devices. We use several list transactions configured in M3’s CMS010/015 to create CMS100MI APIs. The application is using M3 rest APIs for both updates and lists of M3 information. No SQL is used to retrieve data. The application is installed via the H5 admin tool and you can start the app as an H5 favorite.

Some examples from the different steps are shown below.
Planned: Are customer orders in M3 status less than 44.

Registered: Customer orders ready for picking – status 44.

Here you choose which orders to print on a special picking list. CUGEX3 is taking care of the picklist lines – with a “unique” picklist number saved in the table. The document is printed with barcodes and as a PDF.

To do pick reporting, a scanner is used to confirm the barcode on the item that’s picked.

After the picklist is reported and packed, the customer order in M3 gets status 66. From there, it is sent to a transportation system that takes care of printing out the label for delivery. We are working on a rest api interface for this application as of now in Q1 – 2020.

Sales Overview – the layer on top of M3’s customer order entry and order history

The customer running this application is in the wholesale and retail business selling building material. All in all, they have around 110 shops based in Norway. The application is built around the process of entry of customer orders in M3 (OIS100). We support a better customer search and entry system, including the creation of customers and customer addresses. This can happen in advance of the customer order entry, so the application can be used in both a back-office customer center and as a front end app out in the shops. We use several list transactions configured in M3’s CMS010/015, which is creating CMS100MI APIs and IES/enterprise search that are used in the “background”. The plan in Q2 is to integrate the application with Infor’s IDM to show the different documents linked to a customer order. Our customer wanted to use M3’s standard OIS100/101 for order entries, so the application is closely linked to OIS100 with the bookmark function. In OIS101, we have added an extend item search using the enterprise search engine to make searching for items more like a seamless experience. Related is also an order history tab, so you can search and follow up the lifecycle of a customer order. The application is using M3 rest APIs for both updates and listings of M3 information. No SQL is used to retrieve data. To do the extended search from OIS101, we are using a H5 script to start the app. The application is installed via H5’s admin tool and you can start the app as an H5 favorite. In the screenshot below, you’ll see that you can search for customers in a related search using parts of their name. Additionally, you can also see if the customer has related addresses created in M3’s OIS002. With a simple click of the button, you can create a customer, and if you want to, a delivery address in the same function.

Linked to OIS101, entry of customer order lines, you have a link via an H5 script which, again, initiates an item search web app where we use IES / extended item search.

You also have an order history tab where we have different kinds of search criteria to find customer orders. Additionally, you can search an item number for a specific customer to locate their order(s). This feature will come in handy when you are working in a shop or are close to your customer. You can also display customer order lines and show invoice information if the customer order is 77. In various areas of the application, you have bookmarks for different M3 functions. Adding bookmarks as a link requires simply adding a URL into the JavaScript code – and it works.

Batch-Order View – the layer on top of M3’s customer batch-order (OIS275)

This application is used by two customers in the wholesales business. Common to them both is they are receiving lots of customer orders via the batch-order entry programs in M3. The two customers wanted to make it easier to handle batch-orders and for one of them, they also needed the ability to make additional changes to the batch-order before they are transferred to actual orders in M3. The application runs in both Smart Office and the H5 client because one of the customers is doing a rollout of H5. So, it was necessary to run the app in two different M3 environments. The application is using the customize table, CUGEX1, where we are saving additional data related to e-com orders. This is related to information not available in M3 standard. With one of the customers, we are also using CUGEX1 to simulate orders upfront of the batch-order. We do check on specific orders if there are available items in stock. Here, we run OIS340MI to simulate a standard M3 availability check and the result is saved in CUGEX1. By doing this, we can show directly in the app if there are available items in stock or not. The main purpose of this feature is to later automate the batch-order entry. But the customer wants a step-by-step action plan to establish the best process in the long-run. To achieve this, MeC and a customized table are part of the solution. We have also established rules on how to “read” a batch-order in MeC, so in some cases, based on some rules, we stop the batch-order in status 05 to be manually handled within the web app. If the batch-order is in status 05 in M3, no integration whatsoever is done to an actual customer order. This means you can then change the order type, warehouse code, line type, delivery method, and joint delivery code before releasing the order directly in the web application. There are lots of bookmark functions in the app, and you are working very close to the standard M3 OIS275. Below some screenshots from the web application:

As you can see, there are also dropdowns for different search criteria. Additionally, the user can save a favorite search, so every time you open the web app, you will get “your search” saved on your user dashboard (cookie saving). You can change the language by simply clicking on one of the many different flags made available in the application framework. You can also set your own filter on how many records appear and the “blue fields” are merely a bookmarks option to M3 functions. One other useful feature is that you can see if the order is also created as an actual order in M3.

Below, you can see the batch-order head information and batch-order lines. If the order is (in MeC) stopped in status 05, you can change warehouse, line type, joint delivery code, and order type before you release it to M3’s OIS100. If the batch-order is “partly released” but M3 validation has stopped it in status 25, you can see the messages created in M3, which is directly linked to the batch-order head. You can also delete batch-order lines if the order is in status 05. If the batch-order status is higher than 05, we disable it to make changes and avoid disrupting M3 data on a customer order level. The save button means that you can work on the batch-order “overtime” and “park it”, so you can continue working with it before you release the order. Below, you can see an order lock symbol. This means that, whenever several users are working on the orders, we lock the order in the web app to avoid conflicting changes (which can happen).

Below, you can see a button called “All My Orders”. This feature takes care of the batch-orders you are working on or have been working on. We make sure the order responsible field in M3 is updated by the user working on the app, so they can filter their orders at a later stage. You can also see an orange flag related to the column, “Full”. An orange flag means that the orderliness does not have availability in stock on all the customer order lines. If there are available units, the symbol will be green and ready for the M3 customer order (just release the order).

Below, you can see a button called “All My Orders”. This feature takes care of the batch-orders you are working on or have been working on. We make sure the order responsible field in M3 is updated by the user working on the app, so they can filter their orders at a later stage. You can also see an orange flag related to the column, “Full”. An orange flag means that the orderliness does not have availability in stock on all the customer order lines. If there are available units, the symbol will be green and ready for the M3 customer order (just release the order).

Any questions?
Please contact our team manager, Espen Johnsen
espen.johnsen@vince.no

Want to know more about our services?