I use a launchagent that tells nudge to run every 3 hours (or 10800 seconds)

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

    <key>Label</key>

    <string>com.github.macadmins.Nudge</string>

    <key>LimitLoadToSessionType</key>

    <array>

        <string>Aqua</string>

    </array>

    <key>ProgramArguments</key>

    <array>

        <string>/Applications/Utilities/Nudge.app/Contents/MacOS/Nudge</string>

        <!-- <string>-json-url</string> -->

        <!-- <string>https://raw.githubusercontent.com/macadmins/nudge/main/Nudge/example.json</string> -->

        <!-- <string>-demo-mode</string> -->

    </array>

    <key>RunAtLoad</key>

    <true/>

    <key>StartInterval</key>

    <integer>10800</integer>

</dict>

</plist>

Are you guys seeing different behavior/result using config profile vs. json ?
I'm not seeing consistent behavior using config profile. Preference domain is set to com.github.macadmins.Nudge and I have requiredMinimumOSVersion key set to 11.4.0. Not being prompted every hour, with the default LaunchAgent.

Any suggestions?

@WaqasKhan I did see some inconsistencies with it still displaying even though I had the "don't display until downloaded" key set. What you're seeing may be down to your min version number choice. Since 11.4 isn't a production release it may balk at that. Someone correct me if I'm wrong, but that seems like a plausible cause. Try setting it to 11.3.1.

@WaqasKhan I'm using json, just so ease of use when modifying for new os releases. There is another parameter you may need to change and that is targetedOSVersion. If your test machine is running 11.3.1 than that targetedOSVersion would need to be scoped to that version.

To apply customized settings, are you using Application and Custom Settings --> External Application --> Source --> Custom Schema and uploading the customized json file ?

I must be doing something wrong because I can't get the application to Jamf deployed configuration either via plist or json.
It works as expected if I manually add the plist or json to /Library/Preferences.

@WaqasKhan yes. the source is custom schema and the preference domain is com.github.macadmins.Nudge

below is a link to the schema at the nudge repo
https://github.com/macadmins/nudge/tree/main/Schema/jamf

@rickwhois = #timesaverextraordinaire

Much appreciate.

@rickwhois Maybe a stupid question but when I deploy this scheme via custom schema and the preference domain is com.github.macadmins.Nudge and I try to change the right side text for the Nudge screen it doesn't change anything. Any idea's?
Further I just deploy a launchagent and the Nudge PKG version 1.0.1.06092021201805.

@Joostvantwout Are you testing this in demo mode? that wont show you the changes. When I test, I usual scope a test config to just my test machine and make sure the targetosversion of my test machine is in the test config, and then make sure the requiredminimumosversion is newer than whats on the test mac. It should pop up on its own, but you can run it from terminal /Applications/Utilities/Nudge.app/Contents/MacOS/Nudge

The nudge repo is very thorough as well if your looking to make other changes! https://github.com/macadmins/nudge
Hope this helps!

@rickwhois No I'm not testing in Demo mode, testing with launchagent nudge package config profile, Nudge is showing up every 30 minutes like it's supposed to be, requiredminimumosversion is also showing as expected only the "Update device" button doesn't change. I want to change the context of the button as our company needs but looks like it doesn't come through.

Is there maybe a good order to deploy nudge? Maybe first the package then the config or other way around?

@Joostvantwout Are other elements in the updateElements section changing? I don't modify that actionButtonText element, mainly just subHeader & mainContentText. But actionButtonText is listed as a modifiable element so from a functionality stand point it should work. I don't believe there is a preferred order of installation, but whenever I change the config, I don't reinstall nudge and things work fine. I'm not an expert with nudge, I just haven't had many issues with it. You may want to inquire with the helpful folks in the nudge slack channel.

@rickwhois May I ask you for which JSON file you deploy? Maybe you can post it here? :)

@Joostvantwout Sure no prob! It is the exact same as here https://github.com/macadmins/nudge/tree/main/Schema/jamf

I know I posted yesterday and got a response but it looks like JamfNation rolled back and I lost the link.  Looking for the pkg location for Nudge so I can test.

Thanks in advanced

I have this same issue. Using the JSON info in a Jamf Configuration profile. The More Info link to uRL and simple vs regular changes in the Config profile takes on the laptop with Nudge. The Text I edit under "user element" does not reflect the changes made via the JSON config profile. The profile on the computer shows the edited text but Nudge itself does not show the correct text.

Hey I have the same issue here. Did you find a fix for this?

Credit to @fridomac - discovered I was missing the ‘en’ in the preferred language for the ‘update elements’ section. Added ‘en’ in the field and the content text was updated. Thanks @fridomac 

Can anyone confirm what setting to use on the frequency?  Pic shows Once per day but in the typed section, it is showing ongoing.  That would be a ton of backend processes.  

Our Nudge deployment is set up with Nudge.pkg and LaunchAgent.pkg pushed once per computer along with scoping the Nudge JSON configuration profile. Didn't set it up via this Jamf Guide Scripting method. Just started to test and deploy this for the Big Sur machines. It was working perfectly for the testing and we pushed it out to more users and now we are unable to click on the "Update Device" button but able to hit the return key to get the software update pane to open. Posted to macadmins slack to see if others have seen this.

Yes, actionButtonText is modifiable. 

Here is the link for the package source for Nudge

https://github.com/macadmins/nudge/releases/tag/v.1.0.0.05062021124623

I would suggest, Keep it once per day as Keeping frequency ongoing for every 15 mints along with update inventory can increase load on your jamf database

Hi Debra, I this still open ?

@Samstar777 the update button issue not working when clicking on it was resolved by shortening the mainContentText. Added this to the issues list on GitHub.

@debrat I am having the issue of the update button not doing anything. I modified and shortened the mainContextText, but it still doesn't work. Running version 1.1.x -- curious if there is something else I should be trying?

Of note: if i run Nudge in demo-mode, the button works fine.