Yes! I'm glad you noticed this change. The servlet (that maxmobile.war) that we used was for downloading the MOBILELOGIN app from your environment. Since this had to occur pre-authentication, we initially exposed this via that unauthenticated servlet. We worked to expose this directly from the REST API without the servlet so that we can avoid the WAR. 

There are quite a few big changes with Maximo Mobile 8.8. We now support building a database for your lookup data. I need to see if we have external documentation on this as it does require some configuration on your part.

We support downloading attachments based on some configuration settings (like type and size of attachments). In 8.7 users would have to access an attachment for it to be available offline. Now that can be automated.

With 7.6.1.3 release in August, you'll be able to utilize a Physical Count application that is based on the Transportation count book functionality. 

In Technician we've added support for flow control (task 20 can't be started until task 10 is completed for example). We support displaying safety plans, including requiring the technician to sign off as reviewing it before they can start work. We added a lot of security permissions so organizations can remove permissions for functionality they don't want to utilize in the mobile app and we'll disable/hide that from the user.

In Inspection we added support for creating an ad-hoc inspection from within the app. We also support capturing GPS coordinates from where the inspection result was recorded. We also support domain based questions where you can tie a Maximo domain (such as WOSTATUS) as a question and as values are added/removed the inspection will be updated. This helps avoid revising the inspection form to add/remove values. We added the ability to do numeric validations such as only allowing a value between 1-10. 

There are some nice quality of life things such as exposing the logs on the login screen so if a user has trouble logging in they can see and share that critical information. This is definitely a non-exhaustive list. I imagine we'll do an external webinar on the new features.

Yes! I'm glad you noticed this change. The servlet (that maxmobile.war) that we used was for downloading the MOBILELOGIN app from your environment. Since this had to occur pre-authentication, we initially exposed this via that unauthenticated servlet. We worked to expose this directly from the REST API without the servlet so that we can avoid the WAR. 

There are quite a few big changes with Maximo Mobile 8.8. We now support building a database for your lookup data. I need to see if we have external documentation on this as it does require some configuration on your part.

We support downloading attachments based on some configuration settings (like type and size of attachments). In 8.7 users would have to access an attachment for it to be available offline. Now that can be automated.

With 7.6.1.3 release in August, you'll be able to utilize a Physical Count application that is based on the Transportation count book functionality. 

In Technician we've added support for flow control (task 20 can't be started until task 10 is completed for example). We support displaying safety plans, including requiring the technician to sign off as reviewing it before they can start work. We added a lot of security permissions so organizations can remove permissions for functionality they don't want to utilize in the mobile app and we'll disable/hide that from the user.

In Inspection we added support for creating an ad-hoc inspection from within the app. We also support capturing GPS coordinates from where the inspection result was recorded. We also support domain based questions where you can tie a Maximo domain (such as WOSTATUS) as a question and as values are added/removed the inspection will be updated. This helps avoid revising the inspection form to add/remove values. We added the ability to do numeric validations such as only allowing a value between 1-10. 

There are some nice quality of life things such as exposing the logs on the login screen so if a user has trouble logging in they can see and share that critical information. This is definitely a non-exhaustive list. I imagine we'll do an external webinar on the new features.

Yes! I'm glad you noticed this change. The servlet (that maxmobile.war) that we used was for downloading the MOBILELOGIN app from your environment. Since this had to occur pre-authentication, we initially exposed this via that unauthenticated servlet. We worked to expose this directly from the REST API without the servlet so that we can avoid the WAR. 

There are quite a few big changes with Maximo Mobile 8.8. We now support building a database for your lookup data. I need to see if we have external documentation on this as it does require some configuration on your part.

We support downloading attachments based on some configuration settings (like type and size of attachments). In 8.7 users would have to access an attachment for it to be available offline. Now that can be automated.

With 7.6.1.3 release in August, you'll be able to utilize a Physical Count application that is based on the Transportation count book functionality. 

In Technician we've added support for flow control (task 20 can't be started until task 10 is completed for example). We support displaying safety plans, including requiring the technician to sign off as reviewing it before they can start work. We added a lot of security permissions so organizations can remove permissions for functionality they don't want to utilize in the mobile app and we'll disable/hide that from the user.

In Inspection we added support for creating an ad-hoc inspection from within the app. We also support capturing GPS coordinates from where the inspection result was recorded. We also support domain based questions where you can tie a Maximo domain (such as WOSTATUS) as a question and as values are added/removed the inspection will be updated. This helps avoid revising the inspection form to add/remove values. We added the ability to do numeric validations such as only allowing a value between 1-10. 

There are some nice quality of life things such as exposing the logs on the login screen so if a user has trouble logging in they can see and share that critical information. This is definitely a non-exhaustive list. I imagine we'll do an external webinar on the new features.

Yes! I'm glad you noticed this change. The servlet (that maxmobile.war) that we used was for downloading the MOBILELOGIN app from your environment. Since this had to occur pre-authentication, we initially exposed this via that unauthenticated servlet. We worked to expose this directly from the REST API without the servlet so that we can avoid the WAR. 

There are quite a few big changes with Maximo Mobile 8.8. We now support building a database for your lookup data. I need to see if we have external documentation on this as it does require some configuration on your part.

We support downloading attachments based on some configuration settings (like type and size of attachments). In 8.7 users would have to access an attachment for it to be available offline. Now that can be automated.

With 7.6.1.3 release in August, you'll be able to utilize a Physical Count application that is based on the Transportation count book functionality. 

In Technician we've added support for flow control (task 20 can't be started until task 10 is completed for example). We support displaying safety plans, including requiring the technician to sign off as reviewing it before they can start work. We added a lot of security permissions so organizations can remove permissions for functionality they don't want to utilize in the mobile app and we'll disable/hide that from the user.

In Inspection we added support for creating an ad-hoc inspection from within the app. We also support capturing GPS coordinates from where the inspection result was recorded. We also support domain based questions where you can tie a Maximo domain (such as WOSTATUS) as a question and as values are added/removed the inspection will be updated. This helps avoid revising the inspection form to add/remove values. We added the ability to do numeric validations such as only allowing a value between 1-10. 

There are some nice quality of life things such as exposing the logs on the login screen so if a user has trouble logging in they can see and share that critical information. This is definitely a non-exhaustive list. I imagine we'll do an external webinar on the new features.

Yes I would open a case. To set expectations, this most likely will be a technote & potentially an addition to the readme in a future release. Our documentation should have covered this and we didn't and I apologize for that.

The reason it's most likely going to result in documentation is because this isn't a traditional installation (just an extracting of the zip), it would require users to manually run anything. So even if we added a script to do this, someone would have to know to run it and once you know what to do it isn't too bad.

As you mentioned, all 6 files in the deployment folder related to Maximo Mobile can be removed. They don't need to be removed because they won't impact your EAR build unless you run them but may be easier to just avoid. Those six files are buildmaximomobile-war.cmd, buildmaximomobile-war.sh, buildmaximomobile-war.xml, includemobilemodule.cmd, includemobilemodule.sh, & includemobilemodule.sh

In the applications\maximo\businessobjects\classes\com\ibm\maximo\mobile directory, the admin folder can be deleted with the 5 classes (MobileApp.class, MobileAppRemote.class, MobileAppSet.class, MobileAppSetRemote.class, & MobileService.class). Again, similar to above these won't break anything but aren't utilized anymore. The table & service they were used for are dropped by our scripts.

The maxmobile folder in the applications\maximo\ directory can also be removed. This was used for the WAR that is no longer needed. 

Then most importantly, as you mentioned you should remove the maxmobile references in the deployment-application.xml & application.xml in the applications/maximo/META-INF/ directory. 

Yes! I'm glad you noticed this change. The servlet (that maxmobile.war) that we used was for downloading the MOBILELOGIN app from your environment. Since this had to occur pre-authentication, we initially exposed this via that unauthenticated servlet. We worked to expose this directly from the REST API without the servlet so that we can avoid the WAR. 

There are quite a few big changes with Maximo Mobile 8.8. We now support building a database for your lookup data. I need to see if we have external documentation on this as it does require some configuration on your part.

We support downloading attachments based on some configuration settings (like type and size of attachments). In 8.7 users would have to access an attachment for it to be available offline. Now that can be automated.

With 7.6.1.3 release in August, you'll be able to utilize a Physical Count application that is based on the Transportation count book functionality. 

In Technician we've added support for flow control (task 20 can't be started until task 10 is completed for example). We support displaying safety plans, including requiring the technician to sign off as reviewing it before they can start work. We added a lot of security permissions so organizations can remove permissions for functionality they don't want to utilize in the mobile app and we'll disable/hide that from the user.

In Inspection we added support for creating an ad-hoc inspection from within the app. We also support capturing GPS coordinates from where the inspection result was recorded. We also support domain based questions where you can tie a Maximo domain (such as WOSTATUS) as a question and as values are added/removed the inspection will be updated. This helps avoid revising the inspection form to add/remove values. We added the ability to do numeric validations such as only allowing a value between 1-10. 

There are some nice quality of life things such as exposing the logs on the login screen so if a user has trouble logging in they can see and share that critical information. This is definitely a non-exhaustive list. I imagine we'll do an external webinar on the new features.

Yes I would open a case. To set expectations, this most likely will be a technote & potentially an addition to the readme in a future release. Our documentation should have covered this and we didn't and I apologize for that.

The reason it's most likely going to result in documentation is because this isn't a traditional installation (just an extracting of the zip), it would require users to manually run anything. So even if we added a script to do this, someone would have to know to run it and once you know what to do it isn't too bad.

As you mentioned, all 6 files in the deployment folder related to Maximo Mobile can be removed. They don't need to be removed because they won't impact your EAR build unless you run them but may be easier to just avoid. Those six files are buildmaximomobile-war.cmd, buildmaximomobile-war.sh, buildmaximomobile-war.xml, includemobilemodule.cmd, includemobilemodule.sh, & includemobilemodule.sh

In the applications\maximo\businessobjects\classes\com\ibm\maximo\mobile directory, the admin folder can be deleted with the 5 classes (MobileApp.class, MobileAppRemote.class, MobileAppSet.class, MobileAppSetRemote.class, & MobileService.class). Again, similar to above these won't break anything but aren't utilized anymore. The table & service they were used for are dropped by our scripts.

The maxmobile folder in the applications\maximo\ directory can also be removed. This was used for the WAR that is no longer needed. 

Then most importantly, as you mentioned you should remove the maxmobile references in the deployment-application.xml & application.xml in the applications/maximo/META-INF/ directory. 

Yes! I'm glad you noticed this change. The servlet (that maxmobile.war) that we used was for downloading the MOBILELOGIN app from your environment. Since this had to occur pre-authentication, we initially exposed this via that unauthenticated servlet. We worked to expose this directly from the REST API without the servlet so that we can avoid the WAR. 

There are quite a few big changes with Maximo Mobile 8.8. We now support building a database for your lookup data. I need to see if we have external documentation on this as it does require some configuration on your part.

We support downloading attachments based on some configuration settings (like type and size of attachments). In 8.7 users would have to access an attachment for it to be available offline. Now that can be automated.

With 7.6.1.3 release in August, you'll be able to utilize a Physical Count application that is based on the Transportation count book functionality. 

In Technician we've added support for flow control (task 20 can't be started until task 10 is completed for example). We support displaying safety plans, including requiring the technician to sign off as reviewing it before they can start work. We added a lot of security permissions so organizations can remove permissions for functionality they don't want to utilize in the mobile app and we'll disable/hide that from the user.

In Inspection we added support for creating an ad-hoc inspection from within the app. We also support capturing GPS coordinates from where the inspection result was recorded. We also support domain based questions where you can tie a Maximo domain (such as WOSTATUS) as a question and as values are added/removed the inspection will be updated. This helps avoid revising the inspection form to add/remove values. We added the ability to do numeric validations such as only allowing a value between 1-10. 

There are some nice quality of life things such as exposing the logs on the login screen so if a user has trouble logging in they can see and share that critical information. This is definitely a non-exhaustive list. I imagine we'll do an external webinar on the new features.

Yes I would open a case. To set expectations, this most likely will be a technote & potentially an addition to the readme in a future release. Our documentation should have covered this and we didn't and I apologize for that.

The reason it's most likely going to result in documentation is because this isn't a traditional installation (just an extracting of the zip), it would require users to manually run anything. So even if we added a script to do this, someone would have to know to run it and once you know what to do it isn't too bad.

As you mentioned, all 6 files in the deployment folder related to Maximo Mobile can be removed. They don't need to be removed because they won't impact your EAR build unless you run them but may be easier to just avoid. Those six files are buildmaximomobile-war.cmd, buildmaximomobile-war.sh, buildmaximomobile-war.xml, includemobilemodule.cmd, includemobilemodule.sh, & includemobilemodule.sh

In the applications\maximo\businessobjects\classes\com\ibm\maximo\mobile directory, the admin folder can be deleted with the 5 classes (MobileApp.class, MobileAppRemote.class, MobileAppSet.class, MobileAppSetRemote.class, & MobileService.class). Again, similar to above these won't break anything but aren't utilized anymore. The table & service they were used for are dropped by our scripts.

The maxmobile folder in the applications\maximo\ directory can also be removed. This was used for the WAR that is no longer needed. 

Then most importantly, as you mentioned you should remove the maxmobile references in the deployment-application.xml & application.xml in the applications/maximo/META-INF/ directory. 

Yes! I'm glad you noticed this change. The servlet (that maxmobile.war) that we used was for downloading the MOBILELOGIN app from your environment. Since this had to occur pre-authentication, we initially exposed this via that unauthenticated servlet. We worked to expose this directly from the REST API without the servlet so that we can avoid the WAR. 

There are quite a few big changes with Maximo Mobile 8.8. We now support building a database for your lookup data. I need to see if we have external documentation on this as it does require some configuration on your part.

We support downloading attachments based on some configuration settings (like type and size of attachments). In 8.7 users would have to access an attachment for it to be available offline. Now that can be automated.

With 7.6.1.3 release in August, you'll be able to utilize a Physical Count application that is based on the Transportation count book functionality. 

In Technician we've added support for flow control (task 20 can't be started until task 10 is completed for example). We support displaying safety plans, including requiring the technician to sign off as reviewing it before they can start work. We added a lot of security permissions so organizations can remove permissions for functionality they don't want to utilize in the mobile app and we'll disable/hide that from the user.

In Inspection we added support for creating an ad-hoc inspection from within the app. We also support capturing GPS coordinates from where the inspection result was recorded. We also support domain based questions where you can tie a Maximo domain (such as WOSTATUS) as a question and as values are added/removed the inspection will be updated. This helps avoid revising the inspection form to add/remove values. We added the ability to do numeric validations such as only allowing a value between 1-10. 

There are some nice quality of life things such as exposing the logs on the login screen so if a user has trouble logging in they can see and share that critical information. This is definitely a non-exhaustive list. I imagine we'll do an external webinar on the new features.

Yes I would open a case. To set expectations, this most likely will be a technote & potentially an addition to the readme in a future release. Our documentation should have covered this and we didn't and I apologize for that.

The reason it's most likely going to result in documentation is because this isn't a traditional installation (just an extracting of the zip), it would require users to manually run anything. So even if we added a script to do this, someone would have to know to run it and once you know what to do it isn't too bad.

As you mentioned, all 6 files in the deployment folder related to Maximo Mobile can be removed. They don't need to be removed because they won't impact your EAR build unless you run them but may be easier to just avoid. Those six files are buildmaximomobile-war.cmd, buildmaximomobile-war.sh, buildmaximomobile-war.xml, includemobilemodule.cmd, includemobilemodule.sh, & includemobilemodule.sh

In the applications\maximo\businessobjects\classes\com\ibm\maximo\mobile directory, the admin folder can be deleted with the 5 classes (MobileApp.class, MobileAppRemote.class, MobileAppSet.class, MobileAppSetRemote.class, & MobileService.class). Again, similar to above these won't break anything but aren't utilized anymore. The table & service they were used for are dropped by our scripts.

The maxmobile folder in the applications\maximo\ directory can also be removed. This was used for the WAR that is no longer needed. 

Then most importantly, as you mentioned you should remove the maxmobile references in the deployment-application.xml & application.xml in the applications/maximo/META-INF/ directory. 

Yes! I'm glad you noticed this change. The servlet (that maxmobile.war) that we used was for downloading the MOBILELOGIN app from your environment. Since this had to occur pre-authentication, we initially exposed this via that unauthenticated servlet. We worked to expose this directly from the REST API without the servlet so that we can avoid the WAR. 

There are quite a few big changes with Maximo Mobile 8.8. We now support building a database for your lookup data. I need to see if we have external documentation on this as it does require some configuration on your part.

We support downloading attachments based on some configuration settings (like type and size of attachments). In 8.7 users would have to access an attachment for it to be available offline. Now that can be automated.

With 7.6.1.3 release in August, you'll be able to utilize a Physical Count application that is based on the Transportation count book functionality. 

In Technician we've added support for flow control (task 20 can't be started until task 10 is completed for example). We support displaying safety plans, including requiring the technician to sign off as reviewing it before they can start work. We added a lot of security permissions so organizations can remove permissions for functionality they don't want to utilize in the mobile app and we'll disable/hide that from the user.

In Inspection we added support for creating an ad-hoc inspection from within the app. We also support capturing GPS coordinates from where the inspection result was recorded. We also support domain based questions where you can tie a Maximo domain (such as WOSTATUS) as a question and as values are added/removed the inspection will be updated. This helps avoid revising the inspection form to add/remove values. We added the ability to do numeric validations such as only allowing a value between 1-10. 

There are some nice quality of life things such as exposing the logs on the login screen so if a user has trouble logging in they can see and share that critical information. This is definitely a non-exhaustive list. I imagine we'll do an external webinar on the new features.

Yes I would open a case. To set expectations, this most likely will be a technote & potentially an addition to the readme in a future release. Our documentation should have covered this and we didn't and I apologize for that.

The reason it's most likely going to result in documentation is because this isn't a traditional installation (just an extracting of the zip), it would require users to manually run anything. So even if we added a script to do this, someone would have to know to run it and once you know what to do it isn't too bad.

As you mentioned, all 6 files in the deployment folder related to Maximo Mobile can be removed. They don't need to be removed because they won't impact your EAR build unless you run them but may be easier to just avoid. Those six files are buildmaximomobile-war.cmd, buildmaximomobile-war.sh, buildmaximomobile-war.xml, includemobilemodule.cmd, includemobilemodule.sh, & includemobilemodule.sh

In the applications\maximo\businessobjects\classes\com\ibm\maximo\mobile directory, the admin folder can be deleted with the 5 classes (MobileApp.class, MobileAppRemote.class, MobileAppSet.class, MobileAppSetRemote.class, & MobileService.class). Again, similar to above these won't break anything but aren't utilized anymore. The table & service they were used for are dropped by our scripts.

The maxmobile folder in the applications\maximo\ directory can also be removed. This was used for the WAR that is no longer needed. 

Then most importantly, as you mentioned you should remove the maxmobile references in the deployment-application.xml & application.xml in the applications/maximo/META-INF/ directory. 

Yes! I'm glad you noticed this change. The servlet (that maxmobile.war) that we used was for downloading the MOBILELOGIN app from your environment. Since this had to occur pre-authentication, we initially exposed this via that unauthenticated servlet. We worked to expose this directly from the REST API without the servlet so that we can avoid the WAR. 

There are quite a few big changes with Maximo Mobile 8.8. We now support building a database for your lookup data. I need to see if we have external documentation on this as it does require some configuration on your part.

We support downloading attachments based on some configuration settings (like type and size of attachments). In 8.7 users would have to access an attachment for it to be available offline. Now that can be automated.

With 7.6.1.3 release in August, you'll be able to utilize a Physical Count application that is based on the Transportation count book functionality. 

In Technician we've added support for flow control (task 20 can't be started until task 10 is completed for example). We support displaying safety plans, including requiring the technician to sign off as reviewing it before they can start work. We added a lot of security permissions so organizations can remove permissions for functionality they don't want to utilize in the mobile app and we'll disable/hide that from the user.

In Inspection we added support for creating an ad-hoc inspection from within the app. We also support capturing GPS coordinates from where the inspection result was recorded. We also support domain based questions where you can tie a Maximo domain (such as WOSTATUS) as a question and as values are added/removed the inspection will be updated. This helps avoid revising the inspection form to add/remove values. We added the ability to do numeric validations such as only allowing a value between 1-10. 

There are some nice quality of life things such as exposing the logs on the login screen so if a user has trouble logging in they can see and share that critical information. This is definitely a non-exhaustive list. I imagine we'll do an external webinar on the new features.