NW Scheduler/Publisher - Updates, Support, and Suggestions

[Indapipe]

20 minutes ago, Tortuga said:

each of the SC receives a Task in NWS, after each of them complete the Task, NWS automatically marks the AP box in the Publisher Record.

How would they complete the task? Simply checking the box? In the past I'm pretty sure that just tells NWS that the task has been completed or attended to. But in the case of AP applications, completing that specific task could result in either the application being approved or not approved. How would NWS know which one was the result? That is my query. I realize that you may not have the answer @Tortuga, I'm just putting it out there for everyone.

Edited 2 hours ago by Indapipe

[More4me2do]

The approval can't / shouldn't be done in some cases without dialogue. You have ex pioneers who want to Aux Pioneer during a campaign. You have members of the servant body who want to Aux Pioneer those are all just rubber stamped applications like pushing the paper slip from one SC member to the next to initial it.

 

But then you have applicants that require dialogue. Putting my coders hat on, if a servant wants to Aux pioneer the code could just look for the 3 SC members tasks and check are they completed. But it gets complicated when it is a first time or when someone who has applied in the past but missed the quota. The SC members would have to evaluate and answer the applications ability to fulfill this statement that he signed:

"I have made plans that would enable me to meet the hour requirement"

 

Main advantage I see is the chairman doesn't have to count and read Aux Pioneer slips and the secretary has the publishers marked as Aux Pioneers

Edited 1 hour ago by More4me2do

[Marky]

Claude found some limited documentation regarding the process:

NW Scheduler | NW Publisher app - Me View

Scroll down to "Process Received Auxiliary Pioneer Applications"

Over time, I have seen Claude and ChatGPT gain extensive knowledge of NWS. They many times can give answers even narrowing it down to a specific version of the software. Like everything else I do, I prefer Claude over all the othe AI platforms for most things.

 

Me: New World Scheduler has added the ability for publishers to submit an Auxiliary Pioneer application. Is there any help/support documents from NWS yet that explains how this will be processed by the Congregation Service Committee? How will they approve an application in NWS?

Here is Claude's response:

What's confirmed in NWS help docs

The core principle (unchanged from before, now digitized):
The process is:

1. A publisher submits an Auxiliary Pioneer Application through the NW Publisher app (under Me), rather than filling out a paper S-205b form.
2. This request comes into NW Scheduler, where the Service Committee reviews it and decides to approve or deny it — same as the traditional paper-based process (referencing Organized p. 109).
3. If approved, the Secretary is the one who acts on it in NWS — he ticks "AP" on that publisher's Field Service Report for the relevant month(s). This is what makes the Congregation Field Service Report (S-1) correctly reflect them as an Auxiliary Pioneer.
4. If a publisher is set up as a Continuous Auxiliary Pioneer in Person Spiritual Information, NWS will auto-tick AP for future months without a fresh application each time.

Where this lives in NWS

• The application itself is submitted from NW Publisher app → Me → Auxiliary Pioneer Application.
• Processing/approval isn't a separate "inbox" workflow like Territory or Hospitality Requests. The Service Committee makes its decision outside the software (in their normal meeting/discussion), and then the Secretary manually reflects that decision by ticking AP on the Publisher Record for that month, same as before the app feature existed.
• I could not find a page laying out a dedicated step-by-step "here's exactly how the Service Committee logs their approval/denial decision inside NWS" — the current docs mainly confirm that it routes through the Service Committee and what the Secretary does once approved, not a granular in-app approval workflow (e.g., no visible "Approve/Deny" button described yet, unlike Territory or Hospitality Requests).