Just gauging if anyone else have experienced these before in 763 or 7631

1. COMP workorders not being cleared off
         - Typically by refreshing the query list they disappear or a refresh icon appears and clears them after pressing it
         - Other times adding a work log to the COMP workorder clears them off as well but now and again we've seen some just stuck and only                 way to clear them is to reinstall the app

2. BMXAA9524E - The transaction ID 244712 already exists in the OSLC transaction table with resource ID OSLCWODETAIL for object structure {3}.
        - I know there is a cron taks to purge the OSLCTRANSACTION table but even when making it run more frequently we still see these in the            logs

3. Stuck active timers and cannot start timer on new workorder
       - if someone starts the timer on a workorder and at some point it gets closed and disappears off the device. When they come to start timer            on another workorder they can't because it says you have an active timer on another workorder. But that workorder is closed so they are              not able to stop it. Have to reinstall the app in order to start the timer on another workorder

4. In Maximo systemout logs just showing 

[12/05/20 13:22:25:700 BST] 00000817 SystemOut O
[12/05/20 13:22:40:883 BST] 0000080d SystemOut O
[12/05/20 13:22:55:760 BST] 00000811 SystemOut O
[12/05/20 13:23:10:784 BST] 0000080e SystemOut O
[12/05/20 13:23:25:801 BST] 00000817 SystemOut O
[12/05/20 13:23:40:906 BST] 0000080d SystemOut O

------------------------------
Christopher Kung
------------------------------


#Maximo
#AssetandFacilitiesManagement
#MaximoAnywhere

3 Is (currently) normal, but I do understand the frustration.

The timer only lives in the app's JSON store on the device where the timer was started. Maximo UI and any other user on Maximo Anywhere cannot tell if a timer is running on a device for this workorder.

If the associated work order is no longer present on the device and the timer has not been stopped on the device, the app still sees the active timer and won't let you start a new timer.

If the WO is closed elsewhere, there is no signal back to the device to tell it to stop the timer. Nor is there an option to allow a user to override. I believe that we have an enhancement request open to address this in some way.

(However consider that this means that the user has started to record time on the WO and is not able to complete the labour transaction, so there is potenitally some data loss.)

Until that is done, the options are 1) Train the user community to work in a way that avoids this (I appreciate that this is may be easier said than done and not always be possible/practical and we do all make mistakes) 2) Clear the JSON store. On Android it is sufficient to clear the data for the app. On iOS, an uninstall/reinstall is required.


​

------------------------------
Simon McNab
Maximo Level 2 Support Engineer
IBM
Feltham
2392568728
------------------------------

Original Message:
Sent: Wed May 13, 2020 11:43 AM
From: Christopher Kung
Subject: Anywhere 763 / 7631 Common Issues

Just gauging if anyone else have experienced these before in 763 or 7631

1. COMP workorders not being cleared off
         - Typically by refreshing the query list they disappear or a refresh icon appears and clears them after pressing it
         - Other times adding a work log to the COMP workorder clears them off as well but now and again we've seen some just stuck and only                 way to clear them is to reinstall the app

2. BMXAA9524E - The transaction ID 244712 already exists in the OSLC transaction table with resource ID OSLCWODETAIL for object structure {3}.
        - I know there is a cron taks to purge the OSLCTRANSACTION table but even when making it run more frequently we still see these in the            logs

3. Stuck active timers and cannot start timer on new workorder
       - if someone starts the timer on a workorder and at some point it gets closed and disappears off the device. When they come to start timer            on another workorder they can't because it says you have an active timer on another workorder. But that workorder is closed so they are              not able to stop it. Have to reinstall the app in order to start the timer on another workorder

4. In Maximo systemout logs just showing 

[12/05/20 13:22:25:700 BST] 00000817 SystemOut O
[12/05/20 13:22:40:883 BST] 0000080d SystemOut O
[12/05/20 13:22:55:760 BST] 00000811 SystemOut O
[12/05/20 13:23:10:784 BST] 0000080e SystemOut O
[12/05/20 13:23:25:801 BST] 00000817 SystemOut O
[12/05/20 13:23:40:906 BST] 0000080d SystemOut O

------------------------------
Christopher Kung
------------------------------


#Maximo
#AssetandFacilitiesManagement
#MaximoAnywhere

Hi Chris,

I haven't got a list of fixed issues for the upcoming 7631 IFIX 2.  So if this is urgent,  I suggest that you open a support ticket and request for​​ a LAFix (Limited Availability) for APAR IJ18538 for item # 1 an # 2

Thanks
May

------------------------------
May On
Tech Support
IBM
------------------------------

Original Message:
Sent: Wed May 13, 2020 11:43 AM
From: Christopher Kung
Subject: Anywhere 763 / 7631 Common Issues

Just gauging if anyone else have experienced these before in 763 or 7631

1. COMP workorders not being cleared off
         - Typically by refreshing the query list they disappear or a refresh icon appears and clears them after pressing it
         - Other times adding a work log to the COMP workorder clears them off as well but now and again we've seen some just stuck and only                 way to clear them is to reinstall the app

2. BMXAA9524E - The transaction ID 244712 already exists in the OSLC transaction table with resource ID OSLCWODETAIL for object structure {3}.
        - I know there is a cron taks to purge the OSLCTRANSACTION table but even when making it run more frequently we still see these in the            logs

3. Stuck active timers and cannot start timer on new workorder
       - if someone starts the timer on a workorder and at some point it gets closed and disappears off the device. When they come to start timer            on another workorder they can't because it says you have an active timer on another workorder. But that workorder is closed so they are              not able to stop it. Have to reinstall the app in order to start the timer on another workorder

4. In Maximo systemout logs just showing 

[12/05/20 13:22:25:700 BST] 00000817 SystemOut O
[12/05/20 13:22:40:883 BST] 0000080d SystemOut O
[12/05/20 13:22:55:760 BST] 00000811 SystemOut O
[12/05/20 13:23:10:784 BST] 0000080e SystemOut O
[12/05/20 13:23:25:801 BST] 00000817 SystemOut O
[12/05/20 13:23:40:906 BST] 0000080d SystemOut O

------------------------------
Christopher Kung
------------------------------


#AssetandFacilitiesManagement
#Maximo
#MaximoAnywhere

1 Something that can be useful in troubleshooting this IBM added a transaction log to see if there are transactions that the app thinks it needs to send to Maximo. If there are pending transactions to send to Maximo it will prevent the WO from being removed from the device. If you open the settings menu->Advanced Settings->Logging and then use the triple dots in the top right corner you can see "View Transaction Log" if you're on a newer version of Anywhere. It's definitely in 7.6.3.1, but not sure if it was in 7.6.3 (might have been added in an IFIX in 7.6.3). This doesn't tell you why it's stuck, but at least helps you figure out that there are stuck transactions. May On's example APAR definitely could be the cause of this. 

2 The purpose of this function is pretty important so I'd be cautious making the cron task run too often. Anywhere generates a unique transaction ID for any changes and then provides that on the requests back to Maximo. This is done to ensure that if the communication is interrupted and the app is unsure whether or not it submitted successfully, the app can resend the transaction and Maximo will ignore it if it's already been processed to avoid duplicating records (such as having a second labor transactions). Seeing this on occasion is normal, but this shouldn't be a common occurrence. 

3 Simon's answer is perfect so skipping that one. 

4 is a dumb Maximo thing (not Anywhere) that we haven't had the patience to investigate. We see it at least in a majority of our customers (I hesitate to say all but it seems like all), including ones without Anywhere. Something writes directly to the console this junk because we remove the Maximo loggers from going to "console" which is when it writes to SystemOut.

------------------------------
Steven Shull
Director of Development
Projetech Inc
Cincinnati OH
------------------------------

Original Message:
Sent: Wed May 13, 2020 11:43 AM
From: Christopher Kung
Subject: Anywhere 763 / 7631 Common Issues

Just gauging if anyone else have experienced these before in 763 or 7631

1. COMP workorders not being cleared off
         - Typically by refreshing the query list they disappear or a refresh icon appears and clears them after pressing it
         - Other times adding a work log to the COMP workorder clears them off as well but now and again we've seen some just stuck and only                 way to clear them is to reinstall the app

2. BMXAA9524E - The transaction ID 244712 already exists in the OSLC transaction table with resource ID OSLCWODETAIL for object structure {3}.
        - I know there is a cron taks to purge the OSLCTRANSACTION table but even when making it run more frequently we still see these in the            logs

3. Stuck active timers and cannot start timer on new workorder
       - if someone starts the timer on a workorder and at some point it gets closed and disappears off the device. When they come to start timer            on another workorder they can't because it says you have an active timer on another workorder. But that workorder is closed so they are              not able to stop it. Have to reinstall the app in order to start the timer on another workorder

4. In Maximo systemout logs just showing 

[12/05/20 13:22:25:700 BST] 00000817 SystemOut O
[12/05/20 13:22:40:883 BST] 0000080d SystemOut O
[12/05/20 13:22:55:760 BST] 00000811 SystemOut O
[12/05/20 13:23:10:784 BST] 0000080e SystemOut O
[12/05/20 13:23:25:801 BST] 00000817 SystemOut O
[12/05/20 13:23:40:906 BST] 0000080d SystemOut O

------------------------------
Christopher Kung
------------------------------


#AssetandFacilitiesManagement
#MaximoAnywhere
#Maximo

1. Typically COMP work orders are "orphaned" by having status changes made elsewhere in the system prior to a COMO status change made on the device in question.  In other words the COMP WO was not COMP on the device until you made the status change.  When you did you discover the WO was change somewhere else before you did so.  In that type of scenario you have a process which allows for the situation to occur.  Think of the old paper method.  When you hand a paper work order to a tech, did you allow others to work on that WO?  Perhaps some but it was a coordinated process you controlled, because you knew you had "Joe" out on that job.  Since we have introduced the electronic work order on devices we seem to have forgotten that we still need to manage the work.  No handheld software will replace the need to mange the work.
2. You should investigate more closely what the transaction is and why you keep seeing duplicates. Is this Labor related? There have been some recent APARs on labor related duplicate transactions I believe.
3."...and at some point it gets closed and disappears...."  This is a revealing phrase and directly related to number 1.  "There appears to be some magic happening in the process which no one is sure of, and things just occur" is how I interpret this.  Back to square one on processionals management. On average how many workorderes are your techs getting on their device? On average how do your techs determine who is doing what work at any given point in time? On average do your techs "compete" for work or is it assigned by a work/ crew supervisor?  I realize that we frail humans make mistakes and that sometimes we forget there is a current work order open in the device.  However good management practices, prevents most of these issues.  As Steven mentioned I too think there is an enhancement in the works to make it easier to a) know there is an open timer on a device and b) prevent the work order from removal when there is a timer open (i.e. someone else changes status to COMP when you are working on same work order.  However that will not stop the status changes on core or other devices from occurring.  Remember, "Last in Wins" except if you change the status to CLOSE.
4. I have not seen that but I trust Steven's analysis.

------------------------------
Bradley K. Downing , MBA
IBM Certified Adv. Deployment Prof. Maximo v7.6.1
IBM
Bakersfield CA
------------------------------

Original Message:
Sent: Wed May 13, 2020 11:43 AM
From: Christopher Kung
Subject: Anywhere 763 / 7631 Common Issues

Just gauging if anyone else have experienced these before in 763 or 7631

1. COMP workorders not being cleared off
         - Typically by refreshing the query list they disappear or a refresh icon appears and clears them after pressing it
         - Other times adding a work log to the COMP workorder clears them off as well but now and again we've seen some just stuck and only                 way to clear them is to reinstall the app

2. BMXAA9524E - The transaction ID 244712 already exists in the OSLC transaction table with resource ID OSLCWODETAIL for object structure {3}.
        - I know there is a cron taks to purge the OSLCTRANSACTION table but even when making it run more frequently we still see these in the            logs

3. Stuck active timers and cannot start timer on new workorder
       - if someone starts the timer on a workorder and at some point it gets closed and disappears off the device. When they come to start timer            on another workorder they can't because it says you have an active timer on another workorder. But that workorder is closed so they are              not able to stop it. Have to reinstall the app in order to start the timer on another workorder

4. In Maximo systemout logs just showing 

[12/05/20 13:22:25:700 BST] 00000817 SystemOut O
[12/05/20 13:22:40:883 BST] 0000080d SystemOut O
[12/05/20 13:22:55:760 BST] 00000811 SystemOut O
[12/05/20 13:23:10:784 BST] 0000080e SystemOut O
[12/05/20 13:23:25:801 BST] 00000817 SystemOut O
[12/05/20 13:23:40:906 BST] 0000080d SystemOut O

------------------------------
Christopher Kung
------------------------------


#MaximoAnywhere
#Maximo
#AssetandFacilitiesManagement

Thanks for all your input and suggestions

regarding APAR IJ18538 , does anyone know if 7.6.4 has this or is planned for a 7.6.4 ifix?

------------------------------
Christopher Kung
------------------------------

Original Message:
Sent: Fri May 15, 2020 09:54 AM
From: Bradley Downing
Subject: Anywhere 763 / 7631 Common Issues

1. Typically COMP work orders are "orphaned" by having status changes made elsewhere in the system prior to a COMO status change made on the device in question.  In other words the COMP WO was not COMP on the device until you made the status change.  When you did you discover the WO was change somewhere else before you did so.  In that type of scenario you have a process which allows for the situation to occur.  Think of the old paper method.  When you hand a paper work order to a tech, did you allow others to work on that WO?  Perhaps some but it was a coordinated process you controlled, because you knew you had "Joe" out on that job.  Since we have introduced the electronic work order on devices we seem to have forgotten that we still need to manage the work.  No handheld software will replace the need to mange the work.
2. You should investigate more closely what the transaction is and why you keep seeing duplicates. Is this Labor related? There have been some recent APARs on labor related duplicate transactions I believe.
3."...and at some point it gets closed and disappears...."  This is a revealing phrase and directly related to number 1.  "There appears to be some magic happening in the process which no one is sure of, and things just occur" is how I interpret this.  Back to square one on processionals management. On average how many workorderes are your techs getting on their device? On average how do your techs determine who is doing what work at any given point in time? On average do your techs "compete" for work or is it assigned by a work/ crew supervisor?  I realize that we frail humans make mistakes and that sometimes we forget there is a current work order open in the device.  However good management practices, prevents most of these issues.  As Steven mentioned I too think there is an enhancement in the works to make it easier to a) know there is an open timer on a device and b) prevent the work order from removal when there is a timer open (i.e. someone else changes status to COMP when you are working on same work order.  However that will not stop the status changes on core or other devices from occurring.  Remember, "Last in Wins" except if you change the status to CLOSE.
4. I have not seen that but I trust Steven's analysis.

------------------------------
Bradley K. Downing , MBA
IBM Certified Adv. Deployment Prof. Maximo v7.6.1
IBM
Bakersfield CA

Original Message:
Sent: Wed May 13, 2020 11:43 AM
From: Christopher Kung
Subject: Anywhere 763 / 7631 Common Issues

Just gauging if anyone else have experienced these before in 763 or 7631

1. COMP workorders not being cleared off
         - Typically by refreshing the query list they disappear or a refresh icon appears and clears them after pressing it
         - Other times adding a work log to the COMP workorder clears them off as well but now and again we've seen some just stuck and only                 way to clear them is to reinstall the app

2. BMXAA9524E - The transaction ID 244712 already exists in the OSLC transaction table with resource ID OSLCWODETAIL for object structure {3}.
        - I know there is a cron taks to purge the OSLCTRANSACTION table but even when making it run more frequently we still see these in the            logs

3. Stuck active timers and cannot start timer on new workorder
       - if someone starts the timer on a workorder and at some point it gets closed and disappears off the device. When they come to start timer            on another workorder they can't because it says you have an active timer on another workorder. But that workorder is closed so they are              not able to stop it. Have to reinstall the app in order to start the timer on another workorder

4. In Maximo systemout logs just showing 

[12/05/20 13:22:25:700 BST] 00000817 SystemOut O
[12/05/20 13:22:40:883 BST] 0000080d SystemOut O
[12/05/20 13:22:55:760 BST] 00000811 SystemOut O
[12/05/20 13:23:10:784 BST] 0000080e SystemOut O
[12/05/20 13:23:25:801 BST] 00000817 SystemOut O
[12/05/20 13:23:40:906 BST] 0000080d SystemOut O

------------------------------
Christopher Kung
------------------------------


#Maximo
#AssetandFacilitiesManagement
#MaximoAnywhere

Hi Chris,

APAR  IJ18538 will be addressed in the upcoming TPAE 7.6.1.2 Fix Pack which is due out around July, 2020

https://www.ibm.com/support/pages/apar/IJ18538

------------------------------
May On
Tech Support
IBM
------------------------------

Original Message:
Sent: Wed May 20, 2020 04:09 AM
From: Christopher Kung
Subject: Anywhere 763 / 7631 Common Issues

Thanks for all your input and suggestions

regarding APAR IJ18538 , does anyone know if 7.6.4 has this or is planned for a 7.6.4 ifix?

------------------------------
Christopher Kung

Original Message:
Sent: Fri May 15, 2020 09:54 AM
From: Bradley Downing
Subject: Anywhere 763 / 7631 Common Issues

1. Typically COMP work orders are "orphaned" by having status changes made elsewhere in the system prior to a COMO status change made on the device in question.  In other words the COMP WO was not COMP on the device until you made the status change.  When you did you discover the WO was change somewhere else before you did so.  In that type of scenario you have a process which allows for the situation to occur.  Think of the old paper method.  When you hand a paper work order to a tech, did you allow others to work on that WO?  Perhaps some but it was a coordinated process you controlled, because you knew you had "Joe" out on that job.  Since we have introduced the electronic work order on devices we seem to have forgotten that we still need to manage the work.  No handheld software will replace the need to mange the work.
2. You should investigate more closely what the transaction is and why you keep seeing duplicates. Is this Labor related? There have been some recent APARs on labor related duplicate transactions I believe.
3."...and at some point it gets closed and disappears...."  This is a revealing phrase and directly related to number 1.  "There appears to be some magic happening in the process which no one is sure of, and things just occur" is how I interpret this.  Back to square one on processionals management. On average how many workorderes are your techs getting on their device? On average how do your techs determine who is doing what work at any given point in time? On average do your techs "compete" for work or is it assigned by a work/ crew supervisor?  I realize that we frail humans make mistakes and that sometimes we forget there is a current work order open in the device.  However good management practices, prevents most of these issues.  As Steven mentioned I too think there is an enhancement in the works to make it easier to a) know there is an open timer on a device and b) prevent the work order from removal when there is a timer open (i.e. someone else changes status to COMP when you are working on same work order.  However that will not stop the status changes on core or other devices from occurring.  Remember, "Last in Wins" except if you change the status to CLOSE.
4. I have not seen that but I trust Steven's analysis.

------------------------------
Bradley K. Downing , MBA
IBM Certified Adv. Deployment Prof. Maximo v7.6.1
IBM
Bakersfield CA

Original Message:
Sent: Wed May 13, 2020 11:43 AM
From: Christopher Kung
Subject: Anywhere 763 / 7631 Common Issues

Just gauging if anyone else have experienced these before in 763 or 7631

1. COMP workorders not being cleared off
         - Typically by refreshing the query list they disappear or a refresh icon appears and clears them after pressing it
         - Other times adding a work log to the COMP workorder clears them off as well but now and again we've seen some just stuck and only                 way to clear them is to reinstall the app

2. BMXAA9524E - The transaction ID 244712 already exists in the OSLC transaction table with resource ID OSLCWODETAIL for object structure {3}.
        - I know there is a cron taks to purge the OSLCTRANSACTION table but even when making it run more frequently we still see these in the            logs

3. Stuck active timers and cannot start timer on new workorder
       - if someone starts the timer on a workorder and at some point it gets closed and disappears off the device. When they come to start timer            on another workorder they can't because it says you have an active timer on another workorder. But that workorder is closed so they are              not able to stop it. Have to reinstall the app in order to start the timer on another workorder

4. In Maximo systemout logs just showing 

[12/05/20 13:22:25:700 BST] 00000817 SystemOut O
[12/05/20 13:22:40:883 BST] 0000080d SystemOut O
[12/05/20 13:22:55:760 BST] 00000811 SystemOut O
[12/05/20 13:23:10:784 BST] 0000080e SystemOut O
[12/05/20 13:23:25:801 BST] 00000817 SystemOut O
[12/05/20 13:23:40:906 BST] 0000080d SystemOut O

------------------------------
Christopher Kung
------------------------------


#Maximo
#AssetandFacilitiesManagement
#MaximoAnywhere

1.  We experienced this exact issue on workorders with lots of tasks on them.  For our case we determined that was around 20 tasks give or take.  We were able to determine that the synchronization process was bombing out due to the si.device.connectivity.timeout setting not being high enough.  We increased it in anywhere administration and refreshed SYSTEM data and that resolved the problem. 

2.  Weve seen this also but it was directly related to 1.  When we fixed 1 it fixed 2.

------------------------------
Victor Chin
------------------------------

Original Message:
Sent: Wed May 13, 2020 11:43 AM
From: Christopher Kung
Subject: Anywhere 763 / 7631 Common Issues

Just gauging if anyone else have experienced these before in 763 or 7631

1. COMP workorders not being cleared off
         - Typically by refreshing the query list they disappear or a refresh icon appears and clears them after pressing it
         - Other times adding a work log to the COMP workorder clears them off as well but now and again we've seen some just stuck and only                 way to clear them is to reinstall the app

2. BMXAA9524E - The transaction ID 244712 already exists in the OSLC transaction table with resource ID OSLCWODETAIL for object structure {3}.
        - I know there is a cron taks to purge the OSLCTRANSACTION table but even when making it run more frequently we still see these in the            logs

3. Stuck active timers and cannot start timer on new workorder
       - if someone starts the timer on a workorder and at some point it gets closed and disappears off the device. When they come to start timer            on another workorder they can't because it says you have an active timer on another workorder. But that workorder is closed so they are              not able to stop it. Have to reinstall the app in order to start the timer on another workorder

4. In Maximo systemout logs just showing 

[12/05/20 13:22:25:700 BST] 00000817 SystemOut O
[12/05/20 13:22:40:883 BST] 0000080d SystemOut O
[12/05/20 13:22:55:760 BST] 00000811 SystemOut O
[12/05/20 13:23:10:784 BST] 0000080e SystemOut O
[12/05/20 13:23:25:801 BST] 00000817 SystemOut O
[12/05/20 13:23:40:906 BST] 0000080d SystemOut O

------------------------------
Christopher Kung
------------------------------


#AssetandFacilitiesManagement
#MaximoAnywhere
#Maximo

interesting.

Can I ask was value you have set for si.device.connectivity.timeout? We also increased this to 60,000 i.e. 1 minute

Thanks

------------------------------
Christopher Kung
------------------------------

Original Message:
Sent: Tue May 26, 2020 04:46 PM
From: Victor Chin
Subject: Anywhere 763 / 7631 Common Issues

1.  We experienced this exact issue on workorders with lots of tasks on them.  For our case we determined that was around 20 tasks give or take.  We were able to determine that the synchronization process was bombing out due to the si.device.connectivity.timeout setting not being high enough.  We increased it in anywhere administration and refreshed SYSTEM data and that resolved the problem. 

2.  Weve seen this also but it was directly related to 1.  When we fixed 1 it fixed 2.

------------------------------
Victor Chin

Original Message:
Sent: Wed May 13, 2020 11:43 AM
From: Christopher Kung
Subject: Anywhere 763 / 7631 Common Issues

Just gauging if anyone else have experienced these before in 763 or 7631

1. COMP workorders not being cleared off
         - Typically by refreshing the query list they disappear or a refresh icon appears and clears them after pressing it
         - Other times adding a work log to the COMP workorder clears them off as well but now and again we've seen some just stuck and only                 way to clear them is to reinstall the app

2. BMXAA9524E - The transaction ID 244712 already exists in the OSLC transaction table with resource ID OSLCWODETAIL for object structure {3}.
        - I know there is a cron taks to purge the OSLCTRANSACTION table but even when making it run more frequently we still see these in the            logs

3. Stuck active timers and cannot start timer on new workorder
       - if someone starts the timer on a workorder and at some point it gets closed and disappears off the device. When they come to start timer            on another workorder they can't because it says you have an active timer on another workorder. But that workorder is closed so they are              not able to stop it. Have to reinstall the app in order to start the timer on another workorder

4. In Maximo systemout logs just showing 

[12/05/20 13:22:25:700 BST] 00000817 SystemOut O
[12/05/20 13:22:40:883 BST] 0000080d SystemOut O
[12/05/20 13:22:55:760 BST] 00000811 SystemOut O
[12/05/20 13:23:10:784 BST] 0000080e SystemOut O
[12/05/20 13:23:25:801 BST] 00000817 SystemOut O
[12/05/20 13:23:40:906 BST] 0000080d SystemOut O

------------------------------
Christopher Kung
------------------------------


#MaximoAnywhere
#AssetandFacilitiesManagement
#Maximo

30000 was good for us.  

One thing to note is that this will not fix previously "corrupted" records.  It will just prevent the problem from occurring in the future.  Thus, having reproduction steps is pretty critical.  We were able to find that as long as the workorder had lots of tasks, it would bomb out on synch and become "corrupted" and stay on the device.   We then tested the exact same scenarios with the property increased and they synched without issue.  

Also note that the system data must be refreshed on the device for the new setting to take effect on the device.

------------------------------
Victor Chin
------------------------------

Original Message:
Sent: Tue May 26, 2020 04:53 PM
From: Christopher Kung
Subject: Anywhere 763 / 7631 Common Issues

interesting.

Can I ask was value you have set for si.device.connectivity.timeout? We also increased this to 60,000 i.e. 1 minute

Thanks

------------------------------
Christopher Kung

Original Message:
Sent: Tue May 26, 2020 04:46 PM
From: Victor Chin
Subject: Anywhere 763 / 7631 Common Issues

1.  We experienced this exact issue on workorders with lots of tasks on them.  For our case we determined that was around 20 tasks give or take.  We were able to determine that the synchronization process was bombing out due to the si.device.connectivity.timeout setting not being high enough.  We increased it in anywhere administration and refreshed SYSTEM data and that resolved the problem. 

2.  Weve seen this also but it was directly related to 1.  When we fixed 1 it fixed 2.

------------------------------
Victor Chin

Original Message:
Sent: Wed May 13, 2020 11:43 AM
From: Christopher Kung
Subject: Anywhere 763 / 7631 Common Issues

Just gauging if anyone else have experienced these before in 763 or 7631

1. COMP workorders not being cleared off
         - Typically by refreshing the query list they disappear or a refresh icon appears and clears them after pressing it
         - Other times adding a work log to the COMP workorder clears them off as well but now and again we've seen some just stuck and only                 way to clear them is to reinstall the app

2. BMXAA9524E - The transaction ID 244712 already exists in the OSLC transaction table with resource ID OSLCWODETAIL for object structure {3}.
        - I know there is a cron taks to purge the OSLCTRANSACTION table but even when making it run more frequently we still see these in the            logs

3. Stuck active timers and cannot start timer on new workorder
       - if someone starts the timer on a workorder and at some point it gets closed and disappears off the device. When they come to start timer            on another workorder they can't because it says you have an active timer on another workorder. But that workorder is closed so they are              not able to stop it. Have to reinstall the app in order to start the timer on another workorder

4. In Maximo systemout logs just showing 

[12/05/20 13:22:25:700 BST] 00000817 SystemOut O
[12/05/20 13:22:40:883 BST] 0000080d SystemOut O
[12/05/20 13:22:55:760 BST] 00000811 SystemOut O
[12/05/20 13:23:10:784 BST] 0000080e SystemOut O
[12/05/20 13:23:25:801 BST] 00000817 SystemOut O
[12/05/20 13:23:40:906 BST] 0000080d SystemOut O

------------------------------
Christopher Kung
------------------------------


#AssetandFacilitiesManagement
#Maximo
#MaximoAnywhere