NW Scheduler/Publisher - Updates, Support, and Suggestions

[Tortuga]

The recent NWS and NWP have not fixed the problem with the Publisher Person PIN in NWP. The field is still empty for everyone. Is anyone else having that problem?

 

 

Edited 13 hours ago by Tortuga

[Indapipe]

2 hours ago, Tortuga said:

The recent NWS and NWP have not fixed the problem with the Publisher Person PIN in NWP. The field is still empty for everyone. Is anyone else having that problem?

 

 

I do see it in my app 4.0.12.

[Tortuga]

1 hour ago, Indapipe said:

I do see it in my app 4.0.12.

Strange. It's been missing through several updates for us.

[carlos]

13 hours ago, Matt S said:

The congregation PIN is used to encrypt your congregation data. If the congregation changes the App PIN, the publishers needs to reconnect using the new congregation PIN, otherwise their phones won't be able to decrypt the data. This publisher hasn't reconnected with the new congregation PIN since your congregation last changed the App PIN. Once they reconnect with the congregation's new PIN their device will be able to decrypt the data again.

 

Thanks, Matthew. This comment is useful.

 

A suggestion: If a message like "The PIN number entered is incorrect" were included in the error message, it would be easier to understand what the issue is. 

 

6 hours ago, Tortuga said:

The recent NWS and NWP have not fixed the problem with the Publisher Person PIN in NWP. The field is still empty for everyone. Is anyone else having that problem?

 

It's happening to us too. 

[Matt S]

6 hours ago, Tortuga said:

The recent NWS and NWP have not fixed the problem with the Publisher Person PIN in NWP. The field is still empty for everyone. Is anyone else having that problem?

 

 

3 hours ago, Indapipe said:

I do see it in my app 4.0.12.

 

2 hours ago, Tortuga said:

Strange. It's been missing through several updates for us.

 

It's not a problem with NWP. You just need to refresh the app data, in your case it would be Persons app data.

 

[Tortuga]

54 minutes ago, Matt S said:

 

 

 

It's not a problem with NWP. You just need to refresh the app data, in your case it would be Persons app data.

 

Do you mean the NWS Admin needs to refresh the app data? 

I have refreshed my NWP app data and it didn't help.

[Tortuga]

The last update radically changed the was the cleaning assignments are displayed in NWP.

 

We schedule the cleaning assignments per meeting in NWS but this is what NWP shows now.

[Matt S]

25 minutes ago, Tortuga said:

Do you mean the NWS Admin needs to refresh the app data? 

I have refreshed my NWP app data and it didn't help.

 

It is not a person by person thing. The instructions in the screenshot I previously posted need to be followed from NWS, not in NWP. The person doing the data refresh would likely need edit access to that data type.

[More4me2do]

18 hours ago, Matt S said:

 

You said you haven't enabled NWS Mobile, and yet a publisher has this problem, so the problem isn't caused by NWS mobile. This screenshot is from NW Publisher, which is unrelated to NWS Mobile.

 

The congregation PIN is used to encrypt your congregation data. If the congregation changes the App PIN, the publishers needs to reconnect using the new congregation PIN, otherwise their phones won't be able to decrypt the data. This publisher hasn't reconnected with the new congregation PIN since your congregation last changed the App PIN. Once they reconnect with the congregation's new PIN their device will be able to decrypt the data again.

 

I get what you are saying but you didn't follow my reaasoning. I know it has nothing to do with Mobile and it is obvious that this screenshot is from NWP.

 

NO pins were changed!!! Out of the blue this error message appeared on an iPhone and it is the first. What you suggested of disconnecting and reconnecting should fix it, but why did this happen in the first place when nothing but updates were happening? Add to that the previous loading error which only could be solved by deleting the local data.

 

So something is not quiet correct in the updates and feature roll out.

 

Now the Mobile feature addition. As long as you stay in the Windows world things are sort of stable in that OS. Now you add the iOS and Android OS to that. It is my understanding that to make these 3 OSs work the encryption had to be changed which in turn effected the decryption. Going by the past record of the major updates, it easier for me to believe that this introduced an error because what else could could have caused it when nothing else was changed?

 

Here is the verification for what I assumed:

Yes. In version 8.1, NW Scheduler upgraded its End-to-End (E2E) encryption algorithms across NWS Desktop, NWS Mobile, and the NWP app to Argon2id + AES-GCM with AAD

 

More likely for me to believe that this is where problem lies.

Edited 2 hours ago by More4me2do

[More4me2do]

4 hours ago, Tortuga said:

Do you mean the NWS Admin needs to refresh the app data? 

I have refreshed my NWP app data and it didn't help.

 

I just had to do this for territories because lots of data was missing like territories that showed in NWS as not completed but were not showing up in the NWP. Go the App section (the icon that looks like phone) on the right side under App Administration select Refresh Selected App Data and from the drop down box select what data you want to refresh.

 

Then after initiating this you get a bunch of warnings do you really want to do this and click yes. It will put the data in the Send App Data box. Go to that box and you will see all the entries of the data that will be resent. Click send.

 

In my case all the missing territory data reappeared.

[Tortuga]

Just now, More4me2do said:

 

I just had to do this for territories because lots of data was missing like territories that showed in NWS as not completed but were not showing up in the NWP. Go the App section (the icon that looks like phone) on the right side under App Administration select Refresh Selected App Data and from the drop down box select what data you want to refresh.

 

Then after initiating this you get a bunch of warnings do you really want to do this and click yes. It will put the data in the Send App Data box. Go to that box and you will see all the entries of the data that will be resent. Click send.

 

In my case all the missing territory data reappeared.

Thanks. I am in View Only mode so I can't do any of that but I shared the information with the Secretary and he will do it. It's hard for me to poke around and figure out what he needs to do because I can't access all of the information. Thanks for the help.

[More4me2do]

20 minutes ago, Tortuga said:

Thanks. I am in View Only mode so I can't do any of that but I shared the information with the Secretary and he will do it. It's hard for me to poke around and figure out what he needs to do because I can't access all of the information. Thanks for the help.

When you are in view mode only you will not be able to see what is in the drop down box, which means what selective refresh areas are available.