Cautions for PCC users (v1)

The following cautions are especially important for customers who are familiar with or are currently using the VAS PCCClosed Pocket CowCard product:

  • Worklists were the first PULSE feature that was able to send and receive data back and forth between PULSE and DairyComp 305, and also from our integrated PULSE partner products. While we have designed this 2‑way data flow to work as smoothly as possible, we encourage you to contact VAS Support if you encounter any problems when processing worklist updates.
  • PULSE does not yet support multiple commands in a To-Do list. Each to-do list should contain only one command that must be completed for all animals on the list. For example, create one list for animals that need to be milked, create a separate list for animals that need to go to dry, create a separate list for animals that require a pen move, etc.).
  • To view worklists in PULSE, they must first be sent from DairyComp 305 to PULSE using the \K switch. See Send Worklists from DC305 to PULSE (DC Unlimited only) to learn more about sending worklists to PULSE.
  • PULSE Hospital List items are included in the Hospital List command and not controlled by DC305Closed DairyComp 305 - VAS Dairy Management Software Server Configuration settings (as they are for PCC Hospital Lists). See Create Hospital Lists to learn more.
  • PULSE Hospital Lists event shortcuts are customizable. This differs from PCC, where all events are included and cannot be changed.
    IMPORTANT: Use caution when scheduling follow‑up routines for DC305 to run after a list is processed (i.e., PostProcess lists), especially if all animals on the list must be processed before kicking off the next routine. DC305 does not wait for the entire list to be DONE. It will kick off the follow‑up routines for each animal as it receives notification from the mobile app that the animal is DONE.

    For more information on how to use OnDone and PostProcess routines in DC305, check out the following videos on the VAS website:

< Return to Tips for Using Mobile App Worklists