Skip to main content
그룹

Program Management

This is a public group to chat about all this related to Program Management!

Hello! I'm tracking down info on the Last Service Date field. It's a roll up that's recalculated nightly with an Apex Job. There is a Last Service Date field on Contact, Program Engagement, Service and Service Session.

 

Our Last Service Dates are totally inconsistent. Sometimes the Program Engagement field will be correct, but missing on Contact. Sometimes missing on both. 

 

I've gone through the steps on this Help Doc. (Except the fields aren't on a Page Layout). I've ensured the Scheduled Apex Job and the Feature Gate settings are correct. 

 

I saw one post where someone thought it was tied to an Attendance Status = Present, but that doesn't seem to be the case, testing on two records. 

 

What might be reasons for the the inconsistencies? Thanks!

답변 4개
  1. 5월 6일 오후 6:23

    I'm a few years late to this conversation, but this post kept coming up as I was trying to troubleshoot a very similar problem. I had a number of Program Enrollments that had Service Deliveries but no 'Last Service Date' even though most of the Program Enrollments in the org had a 'Last Service Date'. It turns out that you need to have a Quantity value entered on the Service Delivery for the 'Last Service Date' to calculate. Hope this answer helps someone else searching the same issue!

0/9000

My client is a non-profit that delivers services for refugees. Sometimes they create a Cohort where it makes sense.  They want a report that lists all the participants in a Cohort with some fields from the Contact record which is not accessible.   I have tried to figure out a custom Rcord Type but have not yet figured out how to make it work.

 

My workaround was to use the Program Engagement object and create formula fields on to the Program Engagement record to pull over the fields from the Contact record.   Not pretty but it works.

 

Does anyone have a better suggestion? This one is pretty clunky if you ask me....#

답변 2개
  1. 2022년 10월 31일 오후 11:07

    Hi Jane,

    If you start with a Report Type of "Program Engagements with Client" that will allow you to filter by Cohort and add all the Contact fields you'd like.

     

    Brad

0/9000

The button is effectively install in Lightning but not displayed?!?

See print screens.

Thanks already for your support.

Very best

 

Capture d’écran 2024-02-12 à 11.42.58.png

 

@Program Management

@Agentforce Nonprofit (Nonprofit Cloud)

답변 3개
0/9000

Hi all,

 

I am curious other SI partners experience creating contact RT for donors & program clients in order to make reporting more efficient and data seperate between Development team and Programs team.

 

Right now, I only have page layouts to distinguish between the two types of contacts but curious about others experience if using RT is a good or bad idea.

 

#PMM #NPSP

답변 3개
  1. Steven Trumble (Strum Consulting) Forum Ambassador
    2023년 11월 20일 오후 2:10

    with lightning record pages (not page layouts) and dynamic forms you can show/hide information based on criteria. 

    So for the donors I only expose all the donation fields if total gifts > 0. 

    For the other sections I only show them when a particular value is selected in a different field. 

0/9000

We've just deployed the OFM and I'm in the process of adding Funding Programs.  For context, we run the same funding programs each year, e.g. core grant fund at 2.5m per annum.  In terms of best practice i'm interested to understand if OFM users create the funding program each year, or if you would create the funding program, leaving off the Total Funding Amount, and use reporting to track disbursments?

TIA

답변 1개
0/9000

Has anyone ever successfully assigned an Intake checklist on creation of an Intake or Program Engagement (rather than the user needing to selection one)? I've tried using a Flow to set the Action Plan Template Group Lookup field on the Program Engagement, but this does not actually cause an Intake Checklist to be created.

 

#Nonprofit

답변 1개
0/9000

New Experience Cloud (formerly known as Community Cloud) Licensing Structure for Nonprofits

 

TLDR (too long didn’t read!):

 

As part of our emerging release, we are excited to launch a new Experience Cloud licensing structure (also known as a SKU), available to nonprofit organizations today. Experience Cloud was formerly known as Community Cloud. This new licensing structure addresses many of the campaign and partner license type roadblocks that may have impacted organizations and their ease of use of Experience Cloud in the past.

 

The Long Version:

 

Whether you are working with donors, volunteers, clients, or recipients of your programs, these stakeholders expect the same type of experiences from your nonprofit as they do from the companies they engage with daily. Think about the healthcare portal you login to to get in touch with your doctor or how you access information from you bank. Nonprofits that make it super easy to engage with their organization retain more donors and volunteers, and make the service experience for program participants easy and engaging.

 

With Experience Cloud, you can create personalized experiences for your stakeholders that are secure, private to your organization only, and consistent with your nonprofit’s branding for one seamless experience.

 

Some examples of the types of experiences you can customize include a donor portal where a donor can login and view their giving history, update their contact information, and even donate quickly and securely without having to get in contact with the development officer. Fundraisers can share impact reports with donors and the board so they can understand where their gifts are being allocated and connect them with staff or other supporters with similar passions. A client can view their service action plan or a volunteer can access a how-to document as a part of their training.

 

Put your stakeholders in the driver seat, streamline self-service, and share proof of your mission’s impact with Experience Cloud.

 

Why a new licensing structure?

  • This new licensing structure allows access to objects and fields that are needed in common nonprofit use cases like opportunities, leads, and campaigns.
  • It ensures the new innovation coming out of Nonprofit Cloud is accessible through Experience Cloud. For example, being able to expose Nonprofit Cloud Case Management (new innovation that was released in April 2020) objects to constituents.
  • This lays the groundwork for future innovations with Experience Cloud!

 

Where can I find out more?

 Check out our pricing guide for all Nonprofit Cloud products and get in touch with your account representative to learn more! 

댓글 41개
0/9000

Does anyone have the implementation instructions for the configuration of Experience Cloud for Nonprofits?

답변 6개
0/9000

Has anyone implemented NPSP Program Management, and used it in conjunction with V4S (Volunteers for Salesforce)?

V4S uses Campaigns (the "old way" of doing programs) to drive volunteer recruitment and onboarding.   My customer's need is more sophisticated: 

- they recruit volunteers directly from institutions (schools, universities, businesses), and need to plan and manage each of these engagements

- the volunteers can also attend classes on things like public speaking, first aid, etc, which are managed as Programs (with sessions, participants and attendance)

- they have a standard set of tasks that need to be completed during volunteer onboarding (such as police checks, passport checks, etc), and they run sessions to train up volunteers before they can go out to the field

- and then the volunteers need to be assigned to actually do the volunteering work, which is managed as Programs

So it seems that recruiting and training can be done with Program Management.  Onboarding can use either Engagement Plans or Sales Process + Path (I'm leaning toward Engagement Plans).  Then V4S manages the volunteering jobs and shifts.

Does that make sense?  Any thoughts?

답변 18개
  1. 2023년 3월 4일 오후 4:44

    I use both V4S and PMM, connecting the two platforms through various objects with lookup fields. We lean more heavily on PMM as it seems more robust and relevant, but certain features of V4S like mass emailing, making mass edits, and volunteer job and hour records have come in very handy when tied to programs/program engagements/contacts, etc...  I agree though, that some features of V4S definitely seem out of date, however.

0/9000
0/9000