iOS Push Notifications

Push Notifications are sent when an Alarm or Todo is created or due, or if a Booking has been created, modified or deleted by a different User.

To be able to receive Push notifications you have to go to your iOS device > Settings > Notifications >  farmerswife > enable: Allow Notifications.



In farmerswife enable the Notifications option on the User/ Resource Web Profile:

• Go to Object Manager > search for the User > double-click to open the Modify User window > access the Web Profile Manager, like in the screenshots:
  
  Web User
  

  Advanced User

  
  
  
• Resource Web Profile: Go to Object Manager (or Toolbox > Contacts) > search for the Resource > double-click to open window > access the Web Profile Manager. Resources can only receive Push Notifications if they have a Web User license, thus the Web Access in their profile is enabled.
  
  
  
  

In the Profile Settings, enable the Notifications option:

This example shows an Alarm Push Notification:

Push Notifications are roughly set to every half minute. 

New Event/Booking added:

Event time or title changed:

When moving the Event/Booking to another day shows 2 Notifications:

Event removed and New event added

Event deleted:

To avoid creating multiple events when e.g. creating, moving and changing the name, only one event will be created if the operations are done within the same minute. In the iPhone or iPad a bundled notification will be sent.

On Bookings new bookings show a Notification:

All Notifications can be accessed in your iPhone/ iPad by tabbing on the More icon > Notifications.

NOTE! From 7.1 it's possible to customize the content fo iOS Push Notifications.
The templates can be found in the server > html templates folder: 

The dynamic data in templates are in the following format and should not be changed: < non_editable_key>, for example:

Any text oustide the brackets can be customized and changed.

The below list includes all currently available notifications, which can be sent in FW (in alphabetical order):

1. Booking Start Reminder: Event Start Reminder: <event_time> for <event_type_and_name> (<event_day>)

2. Booking Stop Reminder: Event End Reminder: <event_time> for <event_type_and_name> (<event_day>)

3. Dispatch Due Items: You Have <object_count> <object_or_objects_string> Due To Be Returned

4. Dispatch preparations: Dispatch <number> is now being prepared by <by_user_name>

5. Dispatch is ready: Dispatch <number> is now being prepared by <by_user_name>

6. Dispatch is overdue: Dispatch <number> is due to be returned 

7. Dispatch partly returned: Dispatch <number> was Partially Returned by <by_user_name> 

8. Dispatch request received: New dispatch request <number> created by <by_user_name>

9. Dispatch request declined: Dispatch request <number> was declined by <by_user_name>

10. Dispatch returned: Dispatch <number> was returned 

11. Dispatch was dispatched: Dispatch <number> was dispatched by <by_user_name>

12. Event changed name: 

Event changed title on <event_day>, <event_time> to <event_type_and_name>

<accept_decline>Please, accept or decline</accept_decline>

13. Event accept/decline: Pending accept or decline for event <event_type_and_name> on <event_day>, <event_time>

14. New event added: 

New event added on <event_day>, <event_time> for <event_type_and_name>

<accept_decline>Please, accept or decline</accept_decline>

15. Event changed time: 

Event time changed on <event_day> to <event_time> for <event_type_and_name>

<accept_decline>Please, accept or decline</accept_decline>

16. Invite activated: Web User <recipent> Activated His Invitation

17. Invite email failed: Failed To Sent Web User Invitation Email To <recipent>

18. Invite email sent: Web User Invitation Email Sent To <recipent>

20. Multiple Event Changes: Multiple Event Changes (<total_events>)

21. To-do Alarm for User: To-do Alarm For <assigned_to>: <todo_name>

22. User added To-do: <created_by> Added To-do "<todo_name>"

23. User added To-do related to Contact: <created_by> Added To-do "<todo_name>" Related To Contact <related_to>

24. User assigned you To-do: <modified_by> Assigned You To-do "<todo_name>" Related To Contact <related_to>

25. User completed To-do: <completed_by> Completed To-do "<todo_name>"

26. User completed related To-do: <completed_by> Completed To-do "<todo_name>" Related To Contact <related_to>

27. User declined To-do: <declined_by> Declined To-do "<todo_name>"

28. User declined To-do related to: <declined_by> Declined To-do "<todo_name>" Related To Contact <related_to>

29. User deleted To-do: <removed_by> Deleted To-do "<todo_name>"

30. User deleted To-do related to contact: <removed_by> Deleted To-do "<todo_name>" Related To Contact <related_to>

31. User modified To-do: <modified_by> Modified To-do "<todo_name>"

32. User modified To-do related to Contact: <modified_by> Modified To-do "<todo_name>" Related To Contact <related_to>

33. User unnasiged from To-do related to Contact: <modified_by> Unassigned You From To-do "<todo_name>" Related To Contact <related_to>