Today I would like to introduce you to SAM 2.0, where we did a lot of improvements over version 1. This blog will highlight the new features and changes.
In the last year we had implementation projects with customers that have different user groups, different roles and need therefore different frontends for them. Because of this we introduced SAM Scenarios, which allows us to deploy different client UI’s with different data model and different data distribution logic on the same middleware.
Hot Deployment of Mobile App
With SAM 2.0, the client user interface based on SAP UI5 can be deployed on the middleware. It is downloaded into the Apache Cordova container during the initial synchronization.
While in the past, the user had to download a new IPA or APK when the client UI changed, in SAM 2.0 the UI is automatically updated when the user is synchronizing. Only in case the core of SAM is changing, an update of the app is required.
SAM Sync Model Creation
The middleware of SAM is built around SAP MobiLink, the in our eyes best middleware technology in the market. In the past we used the SQL Central tool that comes with MobiLink to create the synchronization model and all the filter logic for our customers. This was not ideal, and we have not been happy with it.
In SAM 2.0, the synchronization model of MobiLink can be created and deployed directly on in the SAM Cockpit. Now we have all functionality in one central place and accessible via the web browser.
Enhanced Monitoring and Logging features
We enhanced the monitoring and logging features in the SAM Cockpit, making it much easier now to view synchronizations and their status.
Enhanced Role Concept in the SAM Cockpit
With more functionality in the areas of monitoring and development, the SAM Cockpit became really powerful. At the same time, it can now be used by different roles like administrators, consultants and developers. Because of this, we now allow different user roles in the cockpit and restrict the access to functionality based on the assigned role.
Improved performance on Android
We invested heavily in improving SAM on Android. While Android is in general slower can iOS or Windows devices, we tuned the client in a way that we now reach a great performance even on weaker Android based industrial devices.
Improved Oracle Support
In SAM 2.0 we improved the performance and flexibility of SAM when running on Oracle as consolidated middleware database. Most of the middleware functionality has been moved to stored procedures and functions, making it easily accessible everywhere and allowing us to remove redundant SQL scripts.
In SAM 1.0 we supported the time recording directly on the work or service order via time confirmations. In version 2.0 we also support SAP CATS (cross-application timesheet).
New Checklist Concept
In the past we did a lot of heavy lifting on the client when it came to checklists. When the checklist was for example based on a Notification, we created all the necessary tasks and user status codes on the client. This has changed with SAM 2.0, where all required objects are converted inside SAP into a generic checklist data model. This allows the client to work with much less data and improves the performance on the mobile device. It also allowed us to remove a lot of code and make the app much simpler and easier to enhance.
Checklist creation and upload
It is not easy to create checklists in SAP – no matter which way you go (Notifications, Measurement Points or QM), you always have to jump around between multiple transactions and you need to be an SAP expert to do it.
With SAM 2.0 you can create your checklists with the help of a MS Excel template and upload them to SAP. This way everybody from the business can do it without deep SAP customizing knowledge.
Easy change of look and feel
In SAM 2.0 it is very easy and a task of minutes to change the look and feel of the client application. Colors, logos etc. can be adjusted in a single CSS style sheet.
SAP MobiLink Integration (OEM)
In SAM 2.0, we bundle all required SAP SQL Anywhere, MobiLink and UltraLite components within our solution. Customers are now no longer required to purchase them separately from SAP, but we include them in our subscription.
We will share the details with you over the next weeks in form of blog posts here.