NW Scheduler/Publisher - Updates, Support, and Suggestions

[Pastore72]

30 minutes ago, Pastore72 said:

Sorry, dear brothers, but are you having the same problem? The maps are no longer visible...

 

stiamo usando openstreetmaps

ok, I saw in the "problems" section that I am aware of the problem, let's hope they solve it quickly, hugs

[Cruzer]

31 minutes ago, Pastore72 said:

Sorry, dear brothers, but are you having the same problem? The maps are no longer visible...

 

stiamo usando openstreetmaps

 

It's a known issue the NWS brothers are working on. You'll see the following alert when you go to report this issue from their website..

 

[Nhoj]

6 hours ago, Marky said:

Sine it just dropped, there is probably no way that all of your shared brothers have updated to #1433. We have started to cease all editing in NWS until all elders and ministerial servants are updated to the current version. Please let us know how it is working for you after all of your brothers have updated.

I only have two people who have sharing enabled and are in #1433, and the data loss I described occurs every time.

[foghorn]

On 2/23/2026 at 8:45 AM, Pastore72 said:

"Last Completed Date" column should show the last closing date of the previous service year.

You may be able to satisfy his needs by the way you set up the S-13 report. (See S-13_02.png) If you make sure to select records for 2 service years, the actual S-13 assignment blocks will show everything he needs to know. He needs to count how many territories have not been worked in last 12 months. So if he has assignment records for current (partial) service year and the previous full year, he can easily make his count.

 

The column marked "Last Completed Date" makes it even simpler for him: The program grabs the 'Completed' date from the last time the territory was turned in, and places it in this column for him. The CO can just examine this one column: If he sees a date that is older than the current date 1 year ago, then he knows the territory has not been worked in last year. (See S-13_01.png)

[Landon1285]

On 12/23/2025 at 5:52 PM, foghorn said:

Here is our standard setup with 6 buttons:

1. At Home = had conversation with someone, no need to work this address again
2. Not Home (1st) = try again another day
3. Not Home (2nd) = Not home 2nd time: this address will now be included in the letter-writing territory
4. Do Not Call = Specifically requested by Householder: do not call, write, or telephone
5. No Tress, Priv Prop = 'No Trespassing' or 'Private Property' sign somewhere on property
6. Vacant = no need to call or write (our territory has high number of vacant properties)

NOTES:

1. The selected address is marked as yellow on map
2. After territory is worked in person and returned, the 'Letter-Writing' function is activated. All addresses marked "Not Home" or "No Tress, Priv Prop" will be included on the list. These territories are available to all the friends to work at any time - they simply select an address, mark it "Letter Sent" and send their letter, then repeat.

So once the letter writing function is activated how can I assign it to individual publishers or the group overseer to share with his group? 

 

Is there some functionality with that? 

[foghorn]

5 hours ago, Landon1285 said:

So once the letter writing function is activated how can I assign it to individual publishers or the group overseer to share with his group? 

Activating the letter writing function actually creates a new territory with LW suffix. It can be assigned just like any other - to an individual or a group.

 

However - this method works very well in our congregation: We don't assign letter-writing territory to individual publishers or groups. Instead, we assign letter-writing territories to the special person called "None" (first name to come up in Person list). Plus - they are assigned as Congregation-wide. This allows all publishers to access them. A user simply opens the letter-writing territory, selects an "Available" address, and immediately marks it "Letter Sent". He proceeds to write and address his letter; then he selects another address, etc. This allows multiple users to write letters at the same time from the same territory.

[Landon1285]

2 minutes ago, foghorn said:

Activating the letter writing function actually creates a new territory with LW suffix. It can be assigned just like any other - to an individual or a group.

 

However - this method works very well in our congregation: We don't assign letter-writing territory to individual publishers or groups. Instead, we assign letter-writing territories to the special person called "None" (first name to come up in Person list). Plus - they are assigned as Congregation-wide. This allows all publishers to access them. A user simply opens the letter-writing territory, selects an "Available" address, and immediately marks it "Letter Sent". He proceeds to write and address his letter; then he selects another address, etc. This allows multiple users to write letters at the same time from the same territory.

Thanks. Right now, we use a Google sheet with some researched names for the congregation.

One day, we can use this on a congregation level, but most just want names and don't want to research.

So I'm going to use this on a group level.

[Pastore72]

Good morning, dear brothers, for a few days a servant of my congregation has been having a problem with nw desktop, I also tried on my PC and nothing the same problem, I also looked at the guide on the site but nothing, in short, after installing the problem and selecting sharing, entering the correct credentials (I am an administrator) it connects but does not go beyond the first screen, the buttons on the left are gray, and if I close the program and reopen it, it makes me choose again what to do, whether to create a new congregation, a demo ..... I also deleted the program several times, and I also deleted his account as a publisher. Do you have any advice? a hug

[Floyd]

A brother sent a request for public speakers but I had a question before approving so I sent a reply. After sending the reply I cannot approve any of the speakers. Do I have to wait for a reply through NWS or does he have to make the request again?

[idezotl]

We haven’t updated quite yet to NWS 8.0 as we were hesitant when seeing “beta” for the mobile version. 
 

Reading some of the latest issues makes me still hesitant. Any suggestions to go ahead and update or maybe wait a little while longer? As far as I know we haven’t had any major glitches lately. 

[foghorn]

1 hour ago, idezotl said:

Any suggestions to go ahead and update or maybe wait a little while longer?

FWIW - we are now on 8.0 #1435 and have experienced no issues. All users have successfully transitioned to a new server without incident. Mobile on Android is working well. 

 

One observation regarding mobile app. If same user opens mobile app after running Win11 app, he has to respond to code sent to his registered e-mail. When he then goes back to Win11, same thing: has to respond to e-mail code.