Restoring Dismissed Dashboard Items

Last Updated: Nov 10, 2020 @ 12:33 pm

To restore dismissed dashboard items, simply:

  • Open the right-hand nav menu by tapping the profile image in the top right corner of the app
  • Tap “settings”
  • Tap “Reset Dashboard” and confirm the message that comes up.

Please note that this will restore only items, such as announcements, that are still active in your MP database or on the dashboard stored procedure.

Testing Dashboard Recipes

Testing New Dashboard Recipes

Last Updated: Sep 10, 2019 @ 12:37 pm

The PocketPlatform Dashboard is an awesome tool that can really help you engage with your congregation in many ways. We have provided a significant number of in-app routing options to help your users navigate the app from the dashboard, and we’ve designed it to be easily editable using SQL, which gives you the power to use any information in MinistryPlatform to generate your recipes.

But you need to test those recipes before you make them live to your whole congregation! We’ve put together a quick primer on how to configure a recipe in a testing environment before you make it live to everyone.

Testing Dashboard Recipes

Please Note: Any time you are altering the dashboard, it’s possible to create a situation where the dashboard may fail to load. As such, it’s advisable that you make a backup of the existing SQL before you start working on a new recipe, and always test the dashboard before considering your task complete!


Creating a testing block

Please Note: The content in this Knowledgebase Article assumes that you have good working understanding of SQL and are comfortable editing SQL inside the tools provided by Microsoft. If you need additional assistance or instruction on either of these topics, you can find detailed tutorials at codecademy, w3schools, and Microsoft’s own documentation.

Since the PocketPlatform Dashboard leverages the content and data inside MinistryPlatform, you have a lot of flexibility when designing dashboard recipes to target users within different demographics. For example, you can use your MP data to write a recipe that could present an invitation to Women over the Age of 35. 

(In order to avoid exposing internal database structure, the actual query that would be used to identify demographic information will not be shared here. Please refer to the actual database schema to build your demographic data.)

(Your dashboard may already contain a query that determines demographic data. If that is the case, feel free to use those demographic variables instead of generating new ones.)

The basic structure of a testing block is as follows:

  • Conditional statement that specifies the user IDs that should see this testing block
  • Optional overrides for specific demographic data
  • The actual dashboard recipe

IF @UserID IN (123, 456, 789) -- The user IDs that can see this recipe right now
    BEGIN

    --Overrides for user demographic conditionals.
    SET @UserGenderID = 2;
    SET @UserAge = 36;

    -- Actual recipe starts here
    /* ===========================
    == Show to women over 35
    =========================== */
    IF (@UserGenderID = 2 AND @UserAge > 35)
        BEGIN
        INSERT INTO @Items EXEC [dbo].[my_custom_sproc]
          @DomainID = @DomainID
          ,@OtherValues = @AsNecessary

        END
    -- == E ==
    END

Once the recipe is working as you expect and the dashboard is displaying properly, you can enable this new recipe for your users.

To do so, simply remove the UserID restrictions, as well as any Variable Overrides you may have added.  For our example code, that would look like this:


/* ===========================
== Show to women over 35
=========================== */
IF (@UserGenderID = 2 AND @UserAge > 35)
    BEGIN
    INSERT INTO @Items EXEC [dbo].[my_custom_sproc]
      @DomainID = @DomainID
      ,@OtherValues = @AsNecessary

    END
-- == E ==


Good To Know

  • We’ve created this testing process to cause as little disruption to your users as possible.  If the SQL code is broken or malformed, MSSQL won’t update the Stored Procedure, and if the logic is incorrect or causes an error elsewhere, if won’t prevent the dashboard from loading for users that aren’t in the Included Users List.
  • Please be sure to remove any override variables before activating the new recipe.
  • ALWAYS back up your stored procedure before editing.
  • You may want to consider keeping a “testing section” in your dashboard at all times that would allow you to move testing recipes in and out of a set userbase.
  • Remember to move the recipe out of testing when you’re done!
The PocketPlatform Dashboard

In-App Links: Overview

Last Updated: Oct 27, 2020 @ 7:05 am

Did you know that you can link to just about any screen or view in your app right from The Dashboard? It’s true! With the proper formatting of link URLs you can direct your users to events, sermons, opportunities, General Content Engine posts, and more!

How can I use these URLs?

You can use these URLs anywhere in your dashboard or in “Link” type fields in the PocketPlatform tables in Ministry Platform. A great example would be as a link in a Dashboard announcement or in a CreateTextItem Dashboard Recipe.

Please Note

Each URL may contain at one or two phrases surrounded by curly braces, like {this}. These phrases represent a particular object’s record ID in Ministry Platform. You should be able to see the appropriate record ID by opening that record in Ministry Platform and looking at the title bar. Do not include the curly braces when entering the URL!

Record ID in Ministry Platform

Record ID Example in Ministry Platform

Correct:

[[APP_PREFIX]]sermon_series/10

Incorrect:

[[APP_PREFIX]]sermon_series/{10}


Sermons, Sermon Series, and Sermon Notes


Screen DestinationIn-App URL
Sermon Series[[APP_PREFIX]]sermon_series/{series_id}
Sermon[[APP_PREFIX]]sermon_series/{series_id}/{sermon_id}
Sermon Notes[[APP_PREFIX]]sermon_notes/{sermon_id}*

* Be sure to use the sermon_id and not the custom form id.


Events and Opportunities


Screen DestinationIn-App URL
All Events[[APP_PREFIX]]app/events
Event Detail Page[[APP_PREFIX]]event/{event_id}
All Opportunities[[APP_PREFIX]]app/opportunities
Opportunity Detail View[[APP_PREFIX]]opportunity/{opportunity_id}

Special Use Events and Opportunities

There are some “special use” URL types that are unlikely to be used, but are still available.  Directing users to these URLs without giving them detailed instructions as to where they are going or why could lead to confusion, so be sure you communicate well what the destination is in the originating request!


Screen DestinationIn-App URL
All Groups[[APP_PREFIX]]app/groups
Group[[APP_PREFIX]]group/{group_id}
Group Signup[[APP_PREFIX]]group_signup/{group_id}
Group Inquiry[[APP_PREFIX]]group_inquiry/{group_id}


Groups


Screen DestinationIn-App URL
All Events[[APP_PREFIX]]app/events
Event Detail Page[[APP_PREFIX]]event/{event_id}
All Opportunities[[APP_PREFIX]]app/opportunities
Opportunity Detail View[[APP_PREFIX]]opportunity/{opportunity_id}


Reading Plans


Screen DestinationIn-App URL
Reading Plan Screen[[APP_PREFIX]]reading_plan/{plan_id}
Reading Plan Day Detail[[APP_PREFIX]]reading_plan_day/{plan_day_id}


General Content Engine

The Pocket Platform General Content Engine is a tool that allows you to create general use text and richly formatted posts for use in Pocket Platform.  For more information about the GCE, see KB article: General Content Engine.


Screen DestinationIn-App URL
GCE Post[[APP_PREFIX]]gce/{gce_post_id}


User Profile Screen

Want to make a quick shortcut to the user’s profile screen? Easy enough to do.  Simply use the In-App URL to direct a button or link to the User’s Profile Screen.


Screen DestinationIn-App URL
User Profile[[APP_PREFIX]]profile


Other Links


Screen DestinationIn-App URL
Custom Forms[[APP_PREFIX]]custom_form/{ID}/{form_name}
Connect Card[[APP_PREFIX]]connect_card
GamifiedJourneys[[APP_PREFIX]]journeys
GamifiedJourneyDetail[[APP_PREFIX]]journeys/{ID}/{journey_name}